chore: add Cursor Approval Agent policy files

[Aurora Capital (auroracapital)]

Summary

• Add APPROVAL_POLICY.md and .cursor/approval-policies/ routing (force-added)

Test plan

• ROUTING.md present on branch

---

Note

Low Risk
Documentation and policy configuration only; no application runtime, CI workflow, or auth code changes.

Overview
Introduces Cursor Approval Agent governance for desktop-act: a repo-wide default in APPROVAL_POLICY.md and path-based overrides via .cursor/approval-policies/ROUTING.md.

The default policy only auto-approves when automated review is clean, risk is low, CI is green, and the PR does not touch policy/routing files; it blocks auto-approval on weakened CI, guardrail removals, and certain labels. ROUTING maps docs, GitHub workflows, tests, and application runtime paths to dedicated policies (e.g. workflows are never auto-approved; docs/tests have narrower auto-approve rules). Conflict resolution prefers the stricter, more specific rule.

^{Reviewed by Cursor Bugbot for commit 03bc004. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

@auroracapital, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 56 minutes and 5 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 609b717f-907d-4577-b278-cb65d12657be

📥 Commits

Reviewing files that changed from the base of the PR and between 6b24662 and 03bc004.

📒 Files selected for processing (6)

• .cursor/approval-policies/ROUTING.md
• .cursor/approval-policies/ci-policy.md
• .cursor/approval-policies/docs-policy.md
• .cursor/approval-policies/runtime-policy.md
• .cursor/approval-policies/tests-policy.md
• APPROVAL_POLICY.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/approval-agent-policies

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cursor]

Risk: low. Not approved: Cursor Bugbot did not finish within the polling window and no BUGBOT_REVIEW comment is present; this PR adds approval policy/routing files (human review required); submit-pypi failed. PR is already merged — maintainer review still recommended for governance baseline.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}