⚡ Bolt: Concurrent PR state checks to avoid N+1 gh CLI delays

[xbmc4lyfe]

💡 What: Refactored _filter_to_still_open_prs in ralph_loop/cli.py to use concurrent.futures.ThreadPoolExecutor(max_workers=10) with executor.map to perform gh pr view checks concurrently. Added an explicit check to return immediately if pr_numbers is empty to prevent ValueError on 0 workers.
🎯 Why: Sequential subprocess calls to the GitHub CLI ('gh') were a significant performance bottleneck (N+1 delay) when a high number of PRs needed their state checked in a fan-out.
📊 Impact: Reduces network/subprocess IO wait times linearly depending on the amount of open PRs (capped at 10x speedup), significantly speeding up the initialization phase.
🔬 Measurement: Can be verified by running the tool in a multi-directory mode where multiple PRs are open. Execution logs and telemetry ci_waits will show reduced total seconds.

---

PR created automatically by Jules for task 13481887089860976639 started by @xbmc4lyfe

[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

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

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

Your organization has run out of usage credits. Purchase more in the billing tab.

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

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4bd8e9d1-cf5f-42c2-b72b-a2b6af116448

📥 Commits

Reviewing files that changed from the base of the PR and between 7b35ed2 and 77dfca5.

📒 Files selected for processing (2)

• .jules/bolt.md
• ralph_loop/cli.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt-concurrent-gh-pr-checks-13481887089860976639

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch bolt-concurrent-gh-pr-checks-13481887089860976639

---

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