⚡ Bolt: [performance improvement] Parallelize GitHub CLI PR state checks

[xbmc4lyfe]

💡 What: Replaced sequential _pr_is_still_open calls with concurrent execution using concurrent.futures.ThreadPoolExecutor in _filter_to_still_open_prs and the respawn block of _supervise_fan_out.
🎯 Why: To resolve an N+1 performance bottleneck. Subprocess calls to the gh CLI are slow, and executing them sequentially delayed the entire supervisor fan-out cycle linearly based on the number of open PRs.
📊 Impact: Reduces cycle/respawn check times by running I/O bound subprocess commands in parallel. Cycle latency changes from O(N) to roughly O(N/threads), maintaining prompt responsiveness across many PRs.
🔬 Measurement: Verify the optimization by running the supervisor with multiple open PRs and observing the vastly decreased latency in fan-out spawn decisions and respawns. Tests pass cleanly.

---

PR created automatically by Jules for task 9630556251184987536 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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f2f7104c-8c8f-4a88-82b9-30461651e939

📥 Commits

Reviewing files that changed from the base of the PR and between 7b35ed2 and 4216d43.

📒 Files selected for processing (2)

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

📜 Recent review details

🧰 Additional context used

🪛 Ruff (0.15.14)

ralph_loop/cli.py

[warning] 784-784: Function definition does not bind loop variable exc

(B023)

🔇 Additional comments (5)

ralph_loop/cli.py (4)

784-784: Static analysis false positive.

The Ruff B023 warning about loop variable binding is a false positive. The exc variable on this line is bound in the except CommandError as exc: clause on line 783, not captured from the outer loop. The exc loop variable at line 789 (for pr, still_open, exc in results:) is in a separate scope and doesn't create a closure issue.

---

4-4: LGTM!

---

547-576: LGTM!

---

770-822: LGTM!

.jules/bolt.md (1)

1-3: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• Performance
  • Improved system responsiveness by parallelizing GitHub PR status checks, reducing respawn cycle time when managing multiple pull requests.

Walkthrough

This PR parallelizes GitHub PR state checks across two code paths using concurrent.futures.ThreadPoolExecutor. A bottleneck where sequential gh subprocess calls checked PR liveness is replaced with concurrent execution, reducing respawn/fan-out cycle time while preserving result ordering and error handling semantics.

Changes

Parallel PR state checks

Layer / File(s)	Summary
Performance documentation and concurrency import .jules/bolt.md, ralph_loop/cli.py	Bottleneck documented: sequential gh subprocess calls during PR "still open" checks. concurrent.futures imported to enable thread-based parallelization.
Concurrent filter for open PRs ralph_loop/cli.py (lines 547–562)	_filter_to_still_open_prs refactored to parallelize _pr_is_still_open checks via ThreadPoolExecutor.map, retaining the original behavior of keeping PRs when open-state checks raise CommandError.
Concurrent respawn eligibility checks ralph_loop/cli.py (lines 770–822)	Fan-out supervisor respawn logic updated to concurrently check whether respawn_candidates are still open, then drop closed PRs and respawn confirmed-open ones while preserving backoff behavior across respawns.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐰 Sequential checks were oh-so-slow,
So threads now race to ebb and flow—
gh calls run together, quick as can be,
Respawn cycles fast and fancy and free! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: parallelizing GitHub CLI PR state checks for performance improvement, which is the core objective of the changeset.
Description check	✅ Passed	The description is directly related to the changeset, explaining the what, why, and impact of using ThreadPoolExecutor to parallelize PR state checks.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

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

✨ Simplify code

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

---

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