`--check` is what the decisions-guard job runs; the existing tests call `render_catalog()`
directly and never call `main()` at all. So neither the stale-detection comparison nor the
`raise SystemExit(main())` wiring had any coverage.
Two mutations, both witnessed red against the real script:
* disarming `want.strip() != have.strip()` alone -> 3 failed, 3 passed
* replacing `raise SystemExit(main())` with a bare `main()` -> 1 failed, 5 passed, and
only the subprocess case reddens. That mutant prints
`build_decisions_catalog: docs/decisions/README.md is stale` on stderr and exits 0.
The workflow step reads nothing but the exit code, so CI would report green over a
stale catalog — the #751/#719 shape the decision record names.
The subprocess case runs the command DERIVED from pr-checks.yml rather than a restated
copy of it, and runs it twice: once on an untouched copy of the corpus, which must exit 0.
Without that half, any failure of the harness — an import error, a missing file in the
copy — would also exit non-zero and read as the guard firing.
Refs: #785
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>