feat(pr-bot): auto-close prs stale 2 days after a change request

[plind-junior]

add a daily scheduled stale-pr-reaper that closes an open pr whose author left CodeRabbit's change request unaddressed — no new commit for 2 days. it complements the 3-strikes close: strikes fires when the author keeps pushing failing commits, this fires when they go silent.

the decision (should_close_stale) lives in pr_bot.py as pure stdlib and is scoped to the pr head commit via each review's commit_id, so a push after the review moves head off the reviewed sha and resets the clock. the owner and bots are exempt, matching the strikes exemption.

the reaper reads only api metadata and runs from the trusted default branch — no pr head code runs. scheduled workflows only fire from the default branch, so it activates once it reaches main.

What changed

Why

What might break

VEP

Tests

• make check passes locally (lint + mypy + pytest)
• New / changed behaviour has a test
• CHANGELOG.md updated under ## [Unreleased]

[coderabbitai]

Warning

Review limit reached

@plind-junior, you've reached your PR review limit, so we couldn't start this review.

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

Plan: Pro Plus

Run ID: e353d69d-4a4c-4065-8ac4-ae9cf5ef6211

📥 Commits

Reviewing files that changed from the base of the PR and between bfb6b0a and 30f6905.

📒 Files selected for processing (4)

• .github/workflows/stale-pr-reaper.yml
• CHANGELOG.md
• src/vouch/pr_bot.py
• tests/test_pr_bot.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/coderabbit-merge-gate

---

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