chore(coderabbit): drop the inert auto_approve block

[yakimoto]

auto_approve is not a key in CodeRabbit's live v2 schema (https://storage.googleapis.com/coderabbit_public_assets/schema.v2.json, verified 2026-08-02). The block that occupied this space in .coderabbit.yaml never did anything, and removing it changes no behaviour.

The real control satisfying branch protection is the branch protection rule itself requiring a review — not config in this file. This PR also replaces the surrounding comments, which previously asserted (incorrectly) that this block was what satisfied branch protection, with an accurate note.

---

Note

Low Risk
Documentation-only config cleanup with no application or CI logic changes.

Overview
Removes the auto_approve section from .coderabbit.yaml and replaces the old comments (which claimed it satisfied branch protection) with a short note that auto_approve is not in CodeRabbit’s v2 schema, so the removed block was never active.

No runtime or review behavior changes—branch protection still depends on GitHub’s required-review rules, not this config.

^{Reviewed by Cursor Bugbot for commit 64c631b. Configure here.}

---

Summary by cubic

Removed the inert auto_approve block from .coderabbit.yaml, which is not part of CodeRabbit’s v2 schema and had no effect. Updated comments to clarify that branch protection is enforced by GitHub’s required review, not this config.

^{Written for commit 64c631b. Summary will update on new commits.}

Note

Remove inert auto_approve block from CodeRabbit config

Removes the reviews.auto_approve section from .coderabbit.yaml and replaces it with a comment noting that auto_approve is not recognized by the current schema.

^{Macroscope summarized 64c631b.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_646d0736-cc9b-49f8-b527-2925bc304edd)

[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: 9 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: CHILL

Plan: Pro Plus

Run ID: 46c6f10c-4d21-4cdb-a5df-efd27b1f8596

📥 Commits

Reviewing files that changed from the base of the PR and between e8228c4 and 64c631b.

📒 Files selected for processing (1)

• .coderabbit.yaml

---

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

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔍 Verify the schema claim before relying on it across repos

The justification rests entirely on auto_approve not existing in CodeRabbit's live v2 schema. The file header still points at https://coderabbit.ai/integrations/schema.v2.json while the comment cites a different URL (storage.googleapis.com/coderabbit_public_assets/schema.v2.json). Worth confirming both URLs resolve to the same schema so the recorded justification stays accurate for future readers; otherwise the comment could mislead someone who re-adds the key.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[macroscopeapp]

Approvability

Verdict: Approved 64c631b

Removes an inert configuration block from .coderabbit.yaml that was never functional (not part of CodeRabbit's schema). The author owns this file, and the change has no runtime impact.

^{You can customize Macroscope's approvability policy. Learn more.}