RFC 0010: v2 — apply peer-review findings

- Lead Summary with structural-integrity framing
- Call out local SQLite / embedded log / object store as substrate options
- Cite enabling work by PR number (#5, #7) rather than contested RFC IDs
- Soften PII/PHI claims to "declare redaction intent"; defer forensic
  attestation to a follow-up RFC
- transform verdict retains original payload in write-restricted store
- escalate is async with pending-human-review marker + Policy-set timeout
- New goal: stage plugins are passive I/O; no payload mutation
- Define empty-evidence stamp in Proposal
- Drop "in different costumes" metaphor; tighten throat-clearing
- Anchor "seam" terminology with a definition
- Expand Unresolved Questions: supply chain, ToCToU, multi-analyst conflict,
  contract-RFC location

Author: david-steeves