Keep sibling defects visible when one issue closes

What the check reads

The default-on verify-stage advisory warning groups records by template_class and kill_domain. A fixed member can trigger findings for open or reviewed siblings, and each isomorphic_sites entry on the fixed issue needs #fixed, #na or #n/a. A sibling can legitimately stay open as distinct: dedup_armor must name the other issue’s exact ID and explain the difference in at least three additional words.

proof audit --check known_issue_sibling_disposition

An illustrative case

Illustrative case: two parsers share a boundary-handling class. One is fixed; the other still fails for a different input route. Closing the second merely to clear the warning would lose a real defect. Explain why it remains distinct and retain its own reproducer, owner and status. For listed sites, attach the evidence behind each fixed or not-applicable disposition.

Resolve the finding

1. Inspect the fixed issue’s template class, kill domain and site list.
2. Investigate unresolved siblings. Fix, withdraw or explicitly differentiate each one according to the evidence.
3. Record per-site dispositions and rerun the check, leaving genuinely distinct issues open.

What a clear result means

The check reads grouping fields, explanatory text and markers. It does not discover every sibling or verify the evidence behind #fixed. Clearing the checklist means recorded sites have dispositions; it does not establish closure of an entire defect class or prove that no related sink was missed.

Continue with one real issue

Known issue template transfer · 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.