Known issue reproducer present and resolves

The check is default-on at warning, verify stage. An active KI passes when at least one of these holds: a reproducer_command whose pytest node id or cargo filter resolves to a real test, a runnable command that names no selector (a live-proxy curl, a shell reproducer), a // Reproduces: <KI> annotation on a real test, or a reviewer-stamped poc_presence_exemption. A selector that resolves to no test is stale. It does not count.

This hop does not ask whether every KnownIssue has some evidence kind. That is known issue complete, which still accepts reproduction_steps prose. It does not ask whether a high-stakes KI carries severity_basis: reproducer and a resolving manifest. That is high severity reproducer grade, an error. A complete KI with only prose still fails here. Completeness is not this floor.

id: KI-R1
status: active
reproduction_steps: "run the auth config test"
reproducer_command: cargo test --lib aws_auth_config_must_not

The suite can still be green. The filter matched no fn. The command ran zero tests and reported success by doing nothing. Zero active KnownIssues is a silent pass. That pass inspected nothing. Opt-out is skip, never pass.

printf '%s\n' 'cargo test --lib aws_auth_config_must_not_reject_empty' > repro-cmd.txt
proof known-issue edit KI-R1 --set-reproducer-command-file ./repro-cmd.txt
proof audit --check known_issue_reproducer_present_and_resolves

Attach a resolving selector, a runnable command, or an annotation. Do not leave the KI on prose so the hop stays quiet. A finding you cannot rerun is still a finding.

The teaching graph is still one active KI next to one unresolved selector. Read the finding. Then attach a resolving command, or stamp a genuine design-only waiver.

printf '%s\n' 'cargo test --lib aws_auth_config_must_not_reject_empty' > repro-cmd.txt
proof known-issue edit KI-R1 --set-reproducer-command-file ./repro-cmd.txt
proof audit --check known_issue_reproducer_present_and_resolves --verbose
proof help known-issue

Close a prose-only finding by adding a selector that resolves, a runnable command with no selector, or a // Reproduces: annotation on a real test. Close a stale-selector finding by matching a real def, class, or fn. A cargo phrase embedded in prose is not a selector. The hop does not run the command. It does not inspect the implementation. Completeness stays on known issue complete. High-stakes grade stays on high severity reproducer grade. Do not treat Salesforce's bulletin as this cell. Jama still authors. Proof vs Jama.

Warning severity. A counted warning does not block advancement. Zero active KnownIssues is a pass that inspected nothing. Opt-out is project.checks.known_issue_reproducer_present_and_resolves.enabled false. The hop reports skip, never pass, so a silenced check does not count toward the audit pass total. Presence plus resolvability is the floor. The hop does not execute the reproducer. It does not ask whether the witness proves the headline versus a tripwire of a sub-fact. A capability-gap MC/DC ignore still needs a failing public-API tripwire; do not use poc_presence_exemption to skip that. The hop does not inspect the implementation. We have not scored this floor against a frozen Jama pack, a Salesforce bulletin, or a Jira export. The loss is named, not scored.

The quality-floor hop stays on known issue complete. The high-stakes hop stays on high severity reproducer grade. The engagement stays on software correctness audit. Jama still authors.

What is known issue reproducer present and resolves? Same question. Same URL.

Is this known issue complete? No. That hop is whether every active KI has some evidence kind, including prose. This hop is whether that evidence is runnable and resolves. See known issue complete.

Is this high severity reproducer grade? No. That hop is whether a high-stakes KI is graded by an executed witness. This hop is every active KI, any severity. See high severity reproducer grade.

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

Does a missing known-issues directory fail? No. Zero active KnownIssues is a silent pass. Put a YAML there when the behavior is confirmed, then bind a resolving test before you leave it active.

Does a prose-only KI fail the merge? No. The check keeps warning severity. A counted warning does not block advancement. Opt-out is skip, not pass.

Does a resolving selector prove the finding? No. The hop checks presence and resolvability. It does not run the command. Whether the witness proves the claim stays with the reviewer.

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