Skip to content

Remove audit/audits.json: invented today, read by nothing, already stale #150

Description

@thedavidmeister

audit/audits.json was invented by an agent today, is read by nothing, and already contains a falsehood. Remove it.

Where it came from

Issue #88 asked for a record that the Protofire-audited commit had drifted behind main. The remedy chosen was a new manifest file, landed in PR #137 (merge 76d5689, 2026-08-18 13:24). Nobody asked for the file, and no other repo has one.

It has no reader

An org-wide code search for audits.json returns exactly one hit: the README.md line the same PR added to point at it. No tooling, no CI gate, no health scan, no test.

It is already wrong

Its scope array lists src/lib/LibStackPointer.sol. That file was deleted from this repo earlier the same day, in the "dead across the whole org" removal. A hand-maintained list of paths, checked by nothing, in a repo whose paths move, was stale within hours of being written.

The convention it is not

The audit-directory convention in this org is audit/mutation-test-scans.json plus audit/protofire/ — present here, in rain.deploy and in rain.math.binary, written by the adversarial-mutation-test skill, and actually consumed: the org health check reads its newest entry to answer which release was last audited. audits.json copies that shape for a purpose nothing depends on.

The same class of invention happened in rain.extrospection the same afternoon, as audit/README.md in PR #126 — closed for the same reason, so audits.json does not stand as a precedent for the next agent to copy.

Ask

Remove audit/audits.json and the README.md line pointing at it. Leave audit/mutation-test-scans.json and audit/protofire/ alone.

Reopen or replace #88 if the drift it names is still worth tracking — the issue recorded it better than the file did.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions