ci: remove the CodeRabbit/PastaClaw AI review gate

[QuantumExplorer]

Issue being fixed or feature implemented

The AI Review workflow (CodeRabbit or PastaClaw review) fails by construction on every pull request until one of the two review bots happens to submit a review. Its only step lists the PR's reviews and calls core.setFailed when neither coderabbitai nor thepastaclaw appears, so a brand-new PR is red for reasons that have nothing to do with its contents, and stays red for as long as the bots are backed up or rate-limited. Example: run 30975227954 on #4291, which has no reviews yet.

What was done?

Deleted .github/workflows/pr-ai-review.yml. Nothing else in the repository referenced the workflow, the job, or its concurrency group.

How Has This Been Tested?

Verified the check is not enforced anywhere, so removing the workflow cannot leave PRs waiting on a permanently pending status context:

• v4.2-dev branch protection has an empty required_status_checks.checks/contexts.
• The single active repository ruleset (Block deletions, require PR) contains no required_status_checks rule.

Also grepped the tree for pr-ai-review, ai-review, and PastaClaw review; the only matches were inside the deleted file.

Breaking Changes

None.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 52 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: d6297d41-ef47-49c0-8ab7-0ec59879acf9

📥 Commits

Reviewing files that changed from the base of the PR and between 163b9cd and 079f9a5.

📒 Files selected for processing (1)

• .github/workflows/pr-ai-review.yml

---

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

[thepastaclaw]

🕓 Ready for review — 1 ahead in queue (commit 079f9a5)
Queue position: 2/2