fix(proof): the PR-mined theme SET is live data, not a determinism signal

[jaruesink]

main is red and alpha.12 did not publish. This unblocks both.

The cause is not in #41's change. After normalization, the single surviving difference was one added row in the PR-mining table:

first differing line 346:
  checked-in="| Documentation | <normalized> comments | ..."
  fresh="| Error Handling | <normalized> comments | ..."

Anvil mines its own PR history. A code review on #41 pushed a fifth theme over its threshold, the rows shifted, and Documentation was compared against a freshly inserted Error Handling. The same commit's branch build was green minutes earlier — the two runs disagreed purely on live GitHub state.

normalizeVolatileReportFields already normalized the counts inside each row, on the reasoning that PR churn shouldn't force a hand refresh. It did not normalize which rows exist, so the very next review reintroduced the chore it was written to end.

The line, drawn deliberately

• rows changing → churn, normalizes away
• the table vanishing entirely → mining itself broke, still fails loudly
• a real scoring change → still caught, asserted by a third test, so normalizing live data has not blinded the proof to the deterministic surface it protects

Diagnosis method

Verified against the actual divergence rather than by refreshing the packet — which docs/releasing.md explicitly discourages. Every other differing line (dates, artifact paths, PR/comment/candidate counts) already normalized cleanly, and no Stage D, Low-Yield, or scoring line moved, which is what confirms #41 was not the cause.

Verify

lint · format:check · release:pin --check (alpha.12) · typecheck · 501 pass / 0 fail · verify:self-audit-proof — all green.

🤖 Generated with Claude Code

[coderabbitai]

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: 40 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: 3bd64867-dd24-4cc2-aa8e-2ba1f8f10e7e

📥 Commits

Reviewing files that changed from the base of the PR and between c1a4fc4 and 37c32a3.

📒 Files selected for processing (2)

• scripts/verify-self-audit-proof.test.ts
• scripts/verify-self-audit-proof.ts

---

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