Skip to content

fix(audit): a CLAUDE.md that imports AGENTS.md is a healthy mirror (0.1.0-alpha.8) - #37

Merged
jaruesink merged 1 commit into
mainfrom
fix/shim-mirror-and-release-pin
Aug 8, 2026
Merged

fix(audit): a CLAUDE.md that imports AGENTS.md is a healthy mirror (0.1.0-alpha.8)#37
jaruesink merged 1 commit into
mainfrom
fix/shim-mirror-and-release-pin

Conversation

@jaruesink

Copy link
Copy Markdown
Contributor

Found by running anvil across four active repos.

The shim is not drift

robinhood-trader scored CRITICAL partly on drifted=1. That family is the sanctioned shimCLAUDE.md is @AGENTS.md plus three imports (10 lines) against a 291-line AGENTS.md.

The shim exists precisely so Claude can carry extras Codex must not receive, so the two differ on purpose. Reporting it as drift asks the maintainer to repair a working cross-tool contract. agent-instructions-doctor already recognises the form; anvil now does too.

Mirror Sync Health on robinhood-trader: ❌ drifted=1 → ✅ healthy=1.

release:pin missed two pins on its first real release

This release was the first use of release:pin, and it exercised a bug in it. The prose rewrite was guarded on nearby keywords (packet|anvil|@lambdacurry), so it silently skipped:

-  prints 
- …collect outside-Lambda-Curry first-run proof on pinned 

Neither line says "anvil". I counted every backticked version across the ten governed docs: 16 occurrences, all this package's own. PINNED_DOCS is an explicit allowlist of proof-lane docs — the allowlist is the guard, and the keyword filter only cost correctness. Removed, and verified the resulting diff touches nothing but version strings.

Releases 0.1.0-alpha.8. Suite 384 pass, plus the 2 known npm-on-PATH failures.

Running anvil across four active repos put robinhood-trader at CRITICAL,
partly on drifted=1. That family is the sanctioned shim: CLAUDE.md is
`@AGENTS.md` plus three imports (10 lines) against a 291-line AGENTS.md. The
shim exists so Claude can carry extras Codex must not receive, so the two
differ on purpose — reporting it as drift asks the maintainer to repair a
working cross-tool contract. agent-instructions-doctor already recognizes the
form; anvil now does too.

Also fixes release:pin, which this release exercised for the first time and
which missed two pins. The prose rewrite was guarded on nearby keywords
(packet/anvil/@lambdacurry) and so skipped "`--version` prints `X`" and
"first-run proof on pinned `X`", because neither line says "anvil". Counting
every backticked version across the ten governed docs found 16, all this
package's own — PINNED_DOCS is an explicit allowlist of proof-lane docs, so
the allowlist is the guard and the keyword filter only cost correctness.

Releases 0.1.0-alpha.8.
@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 10 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: c0cc1aca-2381-4b6e-9ce0-937da54e2d4e

📥 Commits

Reviewing files that changed from the base of the PR and between fd8576a and c5b06e1.

📒 Files selected for processing (12)
  • README.md
  • docs-site/public/llms-full.txt
  • docs-site/src/content/docs/reference/cli.md
  • docs/byok-trust-model.md
  • docs/first-user-proof-packet.md
  • docs/first-user-proof.md
  • docs/getting-started.md
  • docs/proofs/current-outside-tester-send-packet.md
  • package.json
  • scripts/audit-scoping.test.ts
  • scripts/audit.ts
  • scripts/release-pin.ts

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

@jaruesink
jaruesink merged commit 44e4577 into main Aug 8, 2026
3 checks passed
@jaruesink
jaruesink deleted the fix/shim-mirror-and-release-pin branch August 8, 2026 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant