Keep a reproducible path to the finding

What the check reads

The verify-stage warning accepts a supported test selector that resolves, a declared command without a recognized selector, a Reproduces or KnownIssue annotation on a discovered test, or a poc_presence_exemption containing reviewer and rationale. It recognizes pytest node IDs and cargo filters using source declarations. Reproduction steps alone do not satisfy this stronger check, although the general completeness floor accepts them.

proof audit --check known_issue_reproducer_present_and_resolves

An illustrative case

Illustrative case: a Rust test was renamed but the issue still records its old cargo filter. The command text remains plausible while the selector no longer names a declaration. Repair the reference and then run it, checking the test count and result. For a shell or live-service reproducer, keep the environment and prerequisites available as well as the command.

Resolve the finding

1. Follow the issue’s command or test annotation and inspect the selector reported by the audit.
2. Update the reference to a real reproducer. If the observation cannot be made executable, record the specific reviewer-stamped exception.
3. Execute the reproducer, confirm it reached the affected behavior and retain current evidence. Rerun the presence check.

What a clear result means

The check does not execute commands. A non-selector command is accepted structurally; that does not establish available credentials, a working environment or a valid assertion. Even a resolved declaration can skip, fail during setup or test the wrong behavior. Inspect execution output before treating the finding as reproduced.

Continue with one real issue

Known issue reproducer consistent · Known issue complete

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