Record the 2026-09-19 adversarial mutation-test campaign

[thedavidmeister]

What

audit/mutation-test-scans.json records the 2026-09-19 adversarial-mutation-test campaign. The roh dashboard reads
this file from the default branch, so until now the repo read as never mutation-tested.

One entry:

• commit 5a633508643e345fc72c11133f782214f60db9b5, the tree every before-number was measured at (published 0.1.20,
  0 commits ahead).
• testsAfterCommit 34506fcba245ca2439975009fee2c7163d87ecf9, main with both coverage PRs merged (AMT coverage: g2-clone-tail #98, AMT coverage: g3-entry-points #99).
• Scope: LibICloneableFactoryV4, ICloneableFactoryV4, ICloneableV2 and the test fixtures they rely on, in three
  groups. src/interface/deprecated/ is excluded and the record says so.
• Totals: 299 mutants, 276 killed by the pre-existing suite, 288 killed after, 0 survived, 11 equivalent. Tests 68 → 78.
• Filed: Open-salt NatSpec says the deployer keeps exactly one lever (timing), but the gas forwarded to initialize is a second: a front-runner can pin a degraded init state at the pinned address #95, TestCloneableCallRecorder is an ICloneableV2 that initializes successfully but can be re-initialized by anyone, contradicting TestCloneable's single-conforming-fixture notice #96, ICLONEABLE_FACTORY_V4_OPEN_SALT_DOMAIN NatSpec credits the distinct tags with keeping every other entry point off open-salt addresses, which only the factory's MUST NOT provides #97.

The earlier 2026-08-24 campaign is deliberately NOT recorded. It was partial: two of its four groups' coverage PRs
(#75, #77) closed unmerged, g4 produced no PR or score, and nothing showed any group ran until no new mutant survived.
The 2026-09-19 campaign re-ran that ground on current main and did run to dry.

QA

• Discriminating tests: n/a - the diff is one record file that no code reads; the repo has no test over
  audit/. The checks that stand in for one: the file is valid JSON, and it matches the record template in the
  adversarial-mutation-test README (both trees named, both full 40-char SHAs). reuse lint passes, audit/**/
  already covering the path.
• Mutations applied: n/a - no source change. The mutants this record REPORTS are the campaign's own: 299 probed,
  276 killed by the pre-existing suite, 288 killed after AMT coverage: g2-clone-tail #98 and AMT coverage: g3-entry-points #99, 0 survived, 11 equivalent. The per-mutant
  matrices are in each group's PROGRESS under /home/gildlab/artifacts/factory/amt-2026-09-19/.
• Oracle: every field is measured, not restated. commit is the scanned tree, testsAfterCommit is main with AMT coverage: g2-clone-tail #98
  and AMT coverage: g3-entry-points #99 merged, publishedTag 0.1.20 is the soldeer revision published from that commit, the tallies come from
  the probe logs, and 68 → 78 is forge test at each tree.
• Category check: the dashboard needs the repo's newest campaign recorded at the commit it ran at; covered. The
  2026-08-24 campaign is deliberately left out as partial, and the body says why.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 53 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: 9d0cd140-1a50-4519-8628-066809f54aa4

📥 Commits

Reviewing files that changed from the base of the PR and between 34506fc and fca88b5.

📒 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.}