Known issue sibling disposition

The check is default-on, warning, verify stage. It walks the KnownIssue corpus at close time. A KI with no template_class, no kill_domain, and no isomorphic_sites is out of scope even when it is fixed. A class with no fixed member is also out of scope. That open-time transfer is a different check. Load failure is a fail. Zero KnownIssues is a pass that inspected nothing of this kind.

Completeness asks that the record have evidence and an origin. Review currency asks that review_date is still current. Neither one groups by bug shape. Closing KI-trunc-a while KI-trunc-b stays open in integer_truncation looks like a close in the tracker. The class is not closed.

id: KI-trunc-a
status: fixed
template_class: integer_truncation
isomorphic_sites:
  - "pkg/cast.go:42"

id: KI-trunc-b
status: open
template_class: integer_truncation

Three findings. A fixed KI whose template_class still has an open or reviewed sibling. A fixed KI whose kill_domain still has one. A fixed KI whose isomorphic_sites entries lack #fixed, #na, or #n/a. Withdrawn siblings count as dispositioned. Empty status defaults to open. Markers are case-insensitive and may sit mid-string.

proof known-issue edit KI-trunc-b --set-status fixed
proof audit --check known_issue_sibling_disposition

Either exit clears a sibling finding: mark the sibling fixed, withdraw it, or keep it open only after you have explained why it is a distinct issue. Site findings clear when every listed site carries a marker. Deleting the YAML also silences the hop. It destroys the finding rather than closing the class. Opt-out reports skip, never pass.

The teaching graph is still one fixed KI whose class still has an open sibling, and whose sites have no marker. Read the finding. Then close, withdraw, or mark each site.

status: fixed
template_class: integer_truncation
isomorphic_sites:
  - "pkg/cast.go:42 #fixed"
  - "pkg/narrow.go:18 #na"

Open-time incomplete transfer is a different check. It tracks sites while a KI is still open. This hop fires when a KI is closed. Completeness stays on known issue complete. Review currency stays on known issues reviewed. Prose-vs-field grade stays on known issue severity prose consistent. Do not treat a Salesforce bulletin as this cell. Jama still authors. Proof vs Jama.

Warning severity. A counted finding does not block the audit. The hop does not fetch the tracker, re-run a PoC, or confirm the security claim is true. It does not read dedup_armor: a sibling kept open with a note still warns. It does not require every fixed KI in a class to be cited; the first fixed id, sorted, is the close-time anchor. A class with no fixed member is silent here. A KI with no class, no kill domain, and no sites is silent even when it is fixed. Zero KnownIssues is a silent pass. Load failure is a fail. Opt-out is skip, never pass. A warning is not a waiver: proof waive is a human authorization gate. The hop does not prove the Go. We have not scored this floor against a frozen Jama pack, a GitHub advisory export, or a Salesforce status page. The loss is named, not scored.

The completeness hop stays on known issue complete. The review-date hop stays on known issues reviewed. The residual hop stays on residual kill hygiene. The engagement stays on software correctness audit. Jama still authors.

What is known issue sibling disposition? Same question. Same URL.

Is this known issue complete? No. That hop is whether the record has evidence and an origin. This hop is whether a close left siblings or sites undispositioned. See known issue complete.

Is this known issues reviewed? No. That hop is whether review_date is still current. This hop is whether the class was closed when one member was. See known issues reviewed.

Is this known issue severity prose consistent? No. That hop is whether the title grades one severity and the field records another. This hop is the close-time sibling checklist. See known issue severity prose consistent.

Is this residual kill hygiene? No. That hop warns a closed quantitative hunt kill with empty samples. A residual is not a KnownIssue. See residual kill hygiene.

Is this known issue template transfer? No. That hop is open-time incomplete transfer. This hop fires when a KI is marked fixed. Same-day sites without a class still belong on the open KI, not here.

Is this a Salesforce known issue? No. Ads known issue is that status page. A hosted vendor bulletin is not this cell.

Does a withdrawn sibling fire? No. Withdrawn counts as dispositioned.

Does a note in dedup_armor clear the warning? No. The hop does not read that field. An open sibling still warns.

Does a missing known-issues directory fail? No. Zero KnownIssues is a silent pass. Put a YAML there when you disclose, then close the class when you close one member.

Does a green hop prove the Go? No. The hop does not run the PoC. It does not fetch the tracker. It does not prove the function.

Is Proof a Jama alternative for the shall? No. Jama still authors. Proof vs Jama.