Both are the same species the milestone is about — a coverage claim resting on source-text
presence rather than on the guard actually running or the clause actually being reached.
MEDIUM, `test_build_catalog_check_path.py`. `_ci_check_command()` grepped the whole
workflow for the command text. So it matched a step that had been COMMENTED OUT, and it
was not scoped to the `decisions-guard` job at all — a match anywhere in the file would
do. Commenting out a step is the ordinary way a check gets switched off during an incident
and never switched back, and the subprocess proof would have stayed green over a guard CI
no longer runs. `guard-ships-with-mutation-proof`: the guard being WIRED is not the guard
RUNNING.
Now the extractor finds the job by key, stops at the next top-level job, strips comment
lines before matching, and asserts exactly one active step. `test_the_extractor_rejects_a_
COMMENTED_OUT_step` pins it. Witnessed against the real workflow: commenting the step out
reddens 2 of 7, deleting it reddens the same 2.
LOW, `test_worktree_ownership_guard.py`. The docstring claimed the three mutations covered
every clause the pair hangs on. They did not: the detection clause is `(commit|merge)`, and
every payload in the file used `commit`, so `merge` could be dropped and the file stayed
green. That is the more damaging half to lose — the mechanism exists for the
plumbing-merge path (`process.foreign-worktree-plumbing-merge`).
Adds a merge deny case and a fourth mutation, narrow by construction: the mutant must stop
denying a merge WHILE STILL denying a commit, so a mutation that merely broke the regex
cannot pass for it. Witnessed: dropping `merge` from the real hook reddens exactly those 2.
The docstring now also states which clauses are NOT mutated (the `git -C`/`cd` redirection
extraction, the marker hook's argument parsing) rather than implying the file is exhaustive.
The review's third finding — the inventory calling both husky files thin dispatchers — was
raised against ad0bed458..7bd7b4c8 and had already been corrected in fdc91056f.
Refs: #785
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>