#793 added one small operator-run check and five cold-review rounds found five
false greens in the verification code itself, each introduced by the fix for the
previous one. All five sat outside `docs/guard-inventory.md`'s population and
always would have: a `perl` wrapper inside an `if` is not a file, and the script
holding it is invoked by no workflow or hook.
Records `testing.verification-code-needs-its-own-proof`: the obligation follows
the VERDICT rather than the file, and how it is discharged depends on where the
construct runs. A checker CI can execute keeps the existing contract (an
inventory row, and at MUTATION a declared clause re-applied every run). A checker
CI cannot execute — operator-run, needing gitignored config or a live server —
gets neither, and ships a witnessed negative control recorded in its PR instead.
Extending the manifest to the second class was considered and rejected because it
would reproduce the defect it was meant to close: `scripts/mcp_smoke.py` needs
`.mcp.json` (gitignored) and a cold-built language server, so a row for it would
be a declared mutation that never executes — the exact false green
`testing.mutation-claims-are-executed` exists to abolish. The residual (a recorded
control decays; nothing re-runs it) is stated in the record rather than papered over.
Also folds in the stop-and-subtract trigger (two consecutive rounds of
fix-creates-the-next-defect means delete the layer, not guard it) and the macOS
timeout recipe, whose wrong form was the recommended one.
Every runtime claim in the record was executed rather than read, per its own rule:
`perl -e 'alarm shift; exec @ARGV' 5 /nope` exits 0 (the false green, reproduced)
while the `or die` form exits 2; `[ -x /bin ]` is true; neither `timeout` nor
`gtimeout` is present; `.mcp.json` is ignored at `.gitignore:12`.
Refs: #796
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>