Skip to content

test: guard shipped drift claims in docs - #25

Merged
jaruesink merged 2 commits into
mainfrom
feat/sfe-1043-doc-reality-guard
Aug 1, 2026
Merged

test: guard shipped drift claims in docs#25
jaruesink merged 2 commits into
mainfrom
feat/sfe-1043-doc-reality-guard

Conversation

@jaruesink

Copy link
Copy Markdown
Contributor

What

Add a narrow docs/reality contract for Anvil's shipped Phase 1 drift checks.

Why

SFR-408, SFD-331, and the current Anvil cycle surfaced repeated documentation claims that shipped capabilities were still planned or not implemented. This guard catches that regression with exact file and line evidence while allowing the planned Phase 2 coverage-gap work.

Proof

  • Current README and drift design docs pass the contract.
  • A seeded Command drift detection is planned claim fails with the source file and line.
  • A planned coverage-gap phase is not misclassified.
  • bun run lint
  • bun run format:check
  • bun run typecheck
  • bun test (356 passing)

Tracking

Add a narrow docs/reality contract for shipped Phase 1 drift checks. The guard reports the exact file and line for stale planned or not-yet-implemented claims while allowing the planned Phase 2 coverage-gap work.

Agent-Actor: scout
Agent-Run-Id: anvil-cycle-001-2026-08-01T17-18Z
@coderabbitai

coderabbitai Bot commented Aug 1, 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: 48 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: 06ed4850-865f-4d76-8fa8-d3bd9cbd5612

📥 Commits

Reviewing files that changed from the base of the PR and between 38cfd8f and e4109da.

📒 Files selected for processing (3)
  • .github/workflows/ci.yml
  • scripts/docs-reality-contract.test.ts
  • scripts/docs-reality-contract.ts

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

The self-audit proof reruns PR signal checks through gh during CI. Wire the read-only Actions token into the test step so the checked-in clean proof remains deterministic in pull requests.

Agent-Actor: scout
Agent-Run-Id: anvil-cycle-001-2026-08-01T17-18Z
@jaruesink
jaruesink merged commit 460602c into main Aug 1, 2026
3 checks passed
@jaruesink
jaruesink deleted the feat/sfe-1043-doc-reality-guard branch August 1, 2026 17:34
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