Context
PR #22 made stable verdict paths authoritative and added explicit legacy migration behavior: #22
This follow-up came from the final review triage: #22 (comment)
Why deferred
The gate is already correct and fail-closed. These changes improve operator-facing clarity without changing evidence validity, so they were kept out of the correctness-focused feature diff.
Scope
- Distinguish current, superseded, orphaned, and reviews-disabled legacy states in migration notices.
- Explicitly report replacement of an existing stable destination during legacy recovery.
- Point missing-verdict violations at the canonical requirement-ID JSON path.
- Add behavioral tests for each diagnostic state without weakening the gate.
Context
PR #22 made stable verdict paths authoritative and added explicit legacy migration behavior: #22
This follow-up came from the final review triage: #22 (comment)
Why deferred
The gate is already correct and fail-closed. These changes improve operator-facing clarity without changing evidence validity, so they were kept out of the correctness-focused feature diff.
Scope