Compared testing.md against the twenty suite names a real receipt records (receipts/29705cb.json). Seventeen match their just target exactly, so a failed entry tells you what to re-run. Three do not, and the doc never bridged them: lifecycle-oracle -> just oracle (there is no just lifecycle-oracle) unit-debug -> zig build test unit-releasesafe -> zig build test -Doptimize=ReleaseSafe Mapping taken from scripts/admit, which is the authority. Without it, someone reading a red receipt searches for a target that does not exist. Also states the consequence the doc left implicit: the everyday "zig build test" is two of the twenty admission suites, and units are graded in both build modes because ReleaseSafe and Debug differ in safety checks and undefined-behaviour handling, not just speed -- so a bug can appear in one and not the other. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>