L09-06 — Qualify intake under adversarial client data #73

Outcome

Test malformed attachments, embedded commands, conflicting specifications, privacy boundaries, and incomplete scans.

Parent and boundary

Parent: #10. Owner: proposed Intake module. This issue owns one bounded slice of Intake; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

• Every case resolves to typed candidate, explicit unknown, or blocked/review state.
• Failure case: No injection expands file/network/execution authority; no unsupported claim is displayed as fact.

Required proof

Held-out client-request corpus and security/evidence report. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap.