docs: record the report spec and both sweeps

Sweep A over 92 real messages after task 1 changed parse.py: 1685
indicators, 92 bodies, 0 crashes, 0 empty parses, no address from a raw
source in the IOC output and no recipient address in any generated body.

What it measured is the limit the spec already accepts. Subject is
published verbatim, and 14 of the 92 messages carried the recipient's
local part inside it because the kit personalises the lure. None carried
it in the From display name, and the envelope recipient was cut from the
boundary Received line in every message. That is the whitelist governing
which headers travel rather than what is inside one, which the spec's
"attacker-controlled free text is published unfiltered" section states
outright and names the sweep as the cover for.

personalised-subject.eml pins all three behaviours, the accepted one
included, so the number cannot drift unnoticed. The for-clause test is
mutation-checked: stop cutting the clause and all three fail.

Sweep B, 12 hand-picked public targets and none from the corpus: 12 of 12,
0 failures, all five RIRs parseable, IPv6 live, the label walk and the
multi-part suffix both correct.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LByBnw83xr9YP85nskzkyE

0 files changed, 0 insertions, 0 deletions