🧹 [Code Health] Parallelize stale OpenCode review dismissals

[seonghobae]

🎯 What: Parallelized stale OpenCode review dismissals using ThreadPoolExecutor.
💡 Why: Reduces N+1 query bottlenecks and speeds up execution.
✅ Verification: Verified by running the full test suite.
✨ Result: Improved maintainability and execution speed.

---

PR created automatically by Jules for task 3043096674807592971 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 36 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 51e261c7-c821-47db-b24a-f6ef83740b3f

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb06cd and 1f9d25a.

📒 Files selected for processing (2)

• scripts/ci/pr_review_merge_scheduler.py
• tests/test_pr_review_merge_scheduler.py

---

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

[seonghobae]

RCA/feasibility: closing unmerged. Parallelizing review-dismissal writes changes observable failure semantics: multiple GitHub review mutations may now be in flight when one request fails, creating partial completion and less deterministic rate-limit behavior. The branch has no production latency profile, retry/idempotency/partial-failure acceptance contract, or secondary-rate-limit budget demonstrating that stale-review dismissal is a meaningful bottleneck. It also modifies the pre-#828 scheduler monolith while #828 is changing the exact stale/current-head approval boundary. A full test-suite pass does not validate the new external API concurrency semantics. Revisit only after the scheduler safety architecture integrates and measured telemetry justifies bounded parallel mutation.

[google-labs-jules]

RCA/feasibility: closing unmerged. Parallelizing review-dismissal writes changes observable failure semantics: multiple GitHub review mutations may now be in flight when one request fails, creating partial completion and less deterministic rate-limit behavior. The branch has no production latency profile, retry/idempotency/partial-failure acceptance contract, or secondary-rate-limit budget demonstrating that stale-review dismissal is a meaningful bottleneck. It also modifies the pre-#828 scheduler monolith while #828 is changing the exact stale/current-head approval boundary. A full test-suite pass does not validate the new external API concurrency semantics. Revisit only after the scheduler safety architecture integrates and measured telemetry justifies bounded parallel mutation.

Understood. Acknowledging that this work is now obsolete and stopping work on this task due to observable failure semantics changes, lack of production latency profile/retry contracts, and potential conflict with the #828 scheduler safety architecture changes.