Skip to content

v0.6.2

Choose a tag to compare

@github-actions github-actions released this 23 Sep 19:00
· 83 commits to main since this release
6dcc32a

The gate telling a contributor their guard does not bite, when the mutation had
not touched a single file. Found by the agent, in a run of the release it was
shipped in, reading its own tool after the answer contradicted its evidence.

Fixed

  • A mutation that changes nothing is refused as a no-op, not reported as a
    guard that does not bite.
    apply_mutation runs sed only over the files a
    suite's suite_mutate_glob lists, so a mutation aimed at a file outside that
    list, or an expression that matches no line, left the tree untouched. The
    mutated run then passed for the gate's own reason and cmd_verify printed
    THE GUARD DOES NOT BITE, which is a verdict about the contributor's test
    from a mutation that never happened. sysknife's review run hit it on
    2026-09-23 with a sed aimed at CONTRIBUTING.md while the shell suite mutates
    *.sh *.py sysknife-* Makefile *.yml, and read the gate to find out why the
    answer contradicted its own reproduction. apply_mutation now counts the
    files it changed and the caller refuses at zero, naming the glob. xargs -r
    also stops an empty file list leaving sed reading stdin.

    The case that was supposed to cover this asserted the old message, so it
    passed while the gate conflated the two findings. It now requires the accurate
    one and fails on the other, and a second case reproduces the real shape: a
    file that exists, a sed that matches it, and a suite that does not mutate it.