Retire bug-dependent exceptions after a fix

What the check reads

The verify-stage error covers known-issue MC/DC row exemptions, known-issue reachability annotations and obligation_deferrals carrying ki_ref. It uses the shared KnownIssue tripwire evaluation, so the linked status and reproducer evidence determine whether the disposition still has a basis. A closed issue or changed tripwire can invalidate the exception. Read the recorded polarity: a green characterization can mean the bug is present.

proof audit --check mcdc_known_issue_disposition_stale

An illustrative case

Illustrative case: a bug makes a required positive row unreachable, so the team records a KI-linked exemption. The implementation is repaired and the original defect no longer reproduces. Keeping the exemption would hide the newly testable row. Replace it with an ordinary witness of the corrected behavior and retain the original reproducer as regression evidence where useful.

Resolve the finding

1. Identify whether the finding concerns a positive-row exemption, a violation-row reachability annotation or an obligation deferral.
2. Check whether the bug was actually fixed or whether evidence became stale, broken or incorrectly classified.
3. For a verified fix, remove the obsolete disposition and supply the appropriate normal witness or satisfying requirement. Re-evaluate before accepting closure.

What a clear result means

The repair depends on the disposition type; deleting every annotation is not a universal fix. Reopening an issue solely to preserve an exception would misstate the evidence. This error checks consistency of the recorded basis, not completeness of the wider defect-class investigation or automatic merge enforcement.

Continue with one real issue

Known issue sibling disposition · Problem reports reviewed

Bring one finding, its requirement and the current evidence to scope a walkthrough of what your reviewer can establish and what still needs work.