ship: v0.2 P4 hardening + adversarial suite + E2E #13
Reference in New Issue
Block a user
Delete Branch "phase/04-hardening-e2e"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
REQ-17/32/34: adversarial suite (11 attacks — hallucinated citations flagged, weak band pinned at 0.82, fabricated reports fail the anchored export gate, SSRF redirect attacks die, mid-loop pause/resume/cancel over HTTP); E2E happy path on the REAL stack (live binding -> dev_bridge -> engine, 3 user actions, defaults only); export round-trip (markdown citation links, JSON validates into the backend CitationLedger model); opt-in keyed live tier (G-004). Verify found 5 P1 honesty gaps in the suite itself — all fixed. Gates: 126 backend + 97 frontend. Tag target v0.2.4.