Context
PR #22 introduced stable, one-file-per-requirement verdict storage and an explicit prune migration: #22
This follow-up came from the final review triage: #22 (comment)
Why deferred
REQ-012 intentionally keeps check non-mutating and makes migration explicit. Rewriting the entire existing evidence tree inside the feature PR would have obscured the implementation diff, so the repository remains partially migrated and emits legacy migration notices.
Scope
- Run the explicit 2119 prune migration in a dedicated reviewable change.
- Verify the selected current evidence and remove remaining legacy duplicates.
- Re-home the REQ-003.7.3 test annotation to a live filename or record-validation requirement.
- Run the full suite, RFC 2119 check, and repository gate against the canonicalized evidence tree.
Context
PR #22 introduced stable, one-file-per-requirement verdict storage and an explicit prune migration: #22
This follow-up came from the final review triage: #22 (comment)
Why deferred
REQ-012 intentionally keeps check non-mutating and makes migration explicit. Rewriting the entire existing evidence tree inside the feature PR would have obscured the implementation diff, so the repository remains partially migrated and emits legacy migration notices.
Scope