Check closure evidence across declared platforms

What the check reads

The verify-stage advisory warning uses project.build_targets and evidence config tokens. It skips when no targets or fewer than two distinct platforms are declared. Platform identity uses os, arch and privilege; transport and build variants alone do not create another platform. A KnownIssue enters scope when some evidence row says known_issue_not_reproduced. Its platforms declaration narrows relevant targets rather than creating extra work.

proof audit --check known_issue_platform_coverage

An illustrative case

Illustrative case: a project declares Linux x86_64 and macOS arm64, but the only non-reproduction was recorded on macOS. The report names the missing Linux target. If the affected behavior is genuinely Linux-only, record that reachability boundary and run there. Do not infer a fix from an unrelated host that could not exercise the path.

Resolve the finding

1. Read the reported observed and missing platform sets alongside the declared support matrix.
2. Run the reproducer on each relevant missing target and retain platform-stamped evidence.
3. Correct a platform declaration only when implementation or deployment evidence supports it, then rerun the check.

What a clear result means

This is coverage advice over declared targets and recorded observations. It does not require another platform when the only observation is that a defect still reproduces. A passing result cannot establish completeness of an undeclared support matrix or prove that every test exercised its target path.

Continue with one real issue

Known issue closure platform bound · Build matrix 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.