audit: green main - the #76 record as the new ledger gate requires it

[thedavidmeister]

main is red. This is the fix, and it is two fields of one JSON record.

What happened

rainix merged #385, which
adds a mutation-ledger gate to the shared static job, at 12:02:46Z. #115's
last PR run started at 12:01 and had no such step - its static job ran
no-submodules, agent-context-cap, snapshots-append-only and the rest, and
passed. The push run on main at 12:05 picked the composite up from @main,
ran the new gate, and failed on the record #115 had just added. Nothing about
the record changed between the two runs; the gate arrived between them.

Both of its errors are about naming, not about the measurement:

ERROR: audit/mutation-test-scans.json[1].tool is "mutation-probe (adversarial-mutation-test 4e59ec0c)",
  expected the string "adversarial-mutation-test" - the audit skill's gate reads this field to
  recognise its own evidence
ERROR: audit/mutation-test-scans.json[1].testsAfterCommit is null - expected a 40-character
  lowercase-hex git commit

The fix

tool is not free text: the audit skill's Pass-2 gate matches it against one
constant to decide whether a record is its own evidence, and #115 wrote the
probe binary and its rev in there instead. The field takes the constant, and the
probe identity moves into notes, where it stays on the record and is read by
people rather than matched by a gate.

testsAfterCommit was null to say "no test changed, so no post-scan test tree
exists". The gate's own module doc says the field is "validated WHEN PRESENT and
never required", with a test named an_omitted_tests_after_commit_is_legal, and
its reason for that is exactly this case: the alternative to absence is to
invent a SHA, "which is the fabricated evidence this gate exists to catch". So
the key goes. null was the right meaning in the wrong encoding.

Nothing else moves. The 28/28 and 23/28 results, the commit the scan is recorded
against, and its summary are untouched.

QA

• Discriminating tests: n/a - the diff is two fields of a JSON record that no
  code in this repo reads. Its consumers live elsewhere (the audit skill's
  Pass-2 gate, roh-scan, and now this gate), and the gate is the discriminating
  test: it fails on the tree main is on now and passes on this one.
• Mutations applied: n/a - no executable line in this repo changed. The
  equivalent evidence is that the check was run both ways rather than reasoned
  about: nix run github:rainlanguage/rainix#rainix-static -- mutation-ledger
  (rainix e8be950, the merge of #385) prints both ERROR lines above on
  main's tree and mutation-ledger: clean on this one.
• Oracle: the gate binary itself, plus its source at
  rainix-static/src/mutation_ledger.rs read for what each field means -
  TOOL, and the module doc on why testsAfterCommit is optional - rather than
  guessing a shape from the error text. The value of every other field is audit: the #76 claims, measured - 23/28 killed, zero new #115's
  measurement, unchanged.
• Category check: the ask is a green main. Both reported errors are fixed, no
  third was introduced (mutation-ledger: clean), the record still says what it
  measured, and pre-commit run --all-files rewrites nothing. audit: the #76 claims, measured - 23/28 killed, zero new #115 stays merged
  and [RLH-36] [INFO] README/NatSpec claims with no pinning test (residue): the packed-collision motivating example, 'a Foo is ALWAYS 4 words' with populated members, deterministic boundary lengths, pointer non-determinism, bytes1[] as a word list #76 stays closed - this corrects how that record is written, not what it
  found.

Suite: unchanged at 77 passed / 0 failed / 0 skipped across 9 suites; src/ and
test/ are not touched by this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V8ViHcKLVk2YoS2joH4HdN

[coderabbitai]

Warning

Review limit reached

Next included review available in 46 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: e8bd6df9-db41-42e6-a6a6-958d0f1c9d17

📥 Commits

Reviewing files that changed from the base of the PR and between eaa6025 and 4b352d6.

📒 Files selected for processing (1)

• audit/mutation-test-scans.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}