Context
PR #22 introduced canonical stable verdict files and fail-closed stable-path authority: #22
This follow-up came from the final review triage: #22 (comment)
Why deferred
Current callers pass the authority map correctly, and distinct-requirement writer isolation satisfies the approved concurrency contract. This is forward-looking robustness rather than a defect in the shipped behavior.
Scope
- Use temp-file-plus-rename for stable verdict writes and migrations to avoid torn reads.
- Make the stable-file authority map a required verdictViolations argument so future callers cannot silently disable the invariant.
- Add focused tests for atomic replacement failure modes and required authority propagation.
- Preserve the existing fail-closed behavior and per-requirement concurrency guarantees.
Context
PR #22 introduced canonical stable verdict files and fail-closed stable-path authority: #22
This follow-up came from the final review triage: #22 (comment)
Why deferred
Current callers pass the authority map correctly, and distinct-requirement writer isolation satisfies the approved concurrency contract. This is forward-looking robustness rather than a defect in the shipped behavior.
Scope