Restore audit/mutation-test-scans.json (my removal in #30 was wrong)

[thedavidmeister]

Reverts the deletion I made in 578de9f (part of #30).

I was wrong

I removed audit/mutation-test-scans.json on the stated grounds that it was off-convention and that "no other repo in the org carries this filename". That claim is false. The file is an established convention:

• rainlanguage/raindex → audit/mutation-test-scans.json
• S01-Issuer/st0x.atomic-bridge → audit/mutation-test-scans.json

…both with the same schema (timestamp, commit, publishedTag, commitsAheadOfTag, scope, tool, skillVersion, summary).

How the error happened

A gh search code for the exact filename token returned empty, silently, and I treated that emptiness as evidence of absence rather than verifying against a known repo. Searching adversarial-mutation instead surfaces all three files immediately. Same failure mode as the raw-NUL/grep trap in rain-org-health earlier today: a tool that returns nothing is not the same as a thing that isn't there.

Why it matters

It's the durable record of the mutation run behind the LibCtPop test hardening — and the org-health dashboard is being taught to read exactly this file to show each repo's last adversarial-mutation run, so deleting it also destroyed the signal it's meant to surface.

Restored verbatim as originally authored; no other change.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@thedavidmeister, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3d54e91a-5e65-478c-b414-7f881ed1faa5

📥 Commits

Reviewing files that changed from the base of the PR and between 63f1a40 and d6b0bf4.

📒 Files selected for processing (1)

• audit/mutation-test-scans.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch restore-mutation-scans

---

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

[thedavidmeister]

Reviewed d6b0bf4: APPROVE

Restores audit/mutation-test-scans.json, reverting my own wrong deletion in 578de9f (#30).

Verified:

• The convention is real, checked against known repos rather than a search result: rainlanguage/raindex and S01-Issuer/st0x.atomic-bridge both carry audit/mutation-test-scans.json with the same schema (timestamp, commit, publishedTag, commitsAheadOfTag, scope, tool, skillVersion, summary).
• The file is restored VERBATIM as originally authored — diff is a pure re-add of the deleted blob, no other change.
• All checks green on this SHA (rainix legal/static/test, CodeRabbit); mergeStateStatus CLEAN. Legal passes, so REUSE covers the path.
• rain-org-health#105 reads exactly this file to surface each repo's newest mutation run, so restoring it also restores the signal my deletion destroyed.

Root cause of the original error, recorded so it is not repeated: a gh search code for the exact filename token returned EMPTY SILENTLY, and I treated absence of results as absence of the thing. Searching adversarial-mutation finds all three files immediately. A search returning nothing is unverified, not negative.

Note: automated review, not human approval — merging on the maintainer's explicit instruction.