🧹 [code health improvement] Refactor rest_pr_node to reduce complexity

[seonghobae]

🎯 What: Extracted dictionary node building logic into _build_files_node and _build_status_check_rollup_node.
💡 Why: To improve maintainability and readability by breaking a moderately complex function's large dictionary return statement into smaller, well-named helper functions.
✅ Verification: Ran pytest test suite and docstring interrogate coverage checks to ensure behavior remained unchanged and doc coverage stayed at 100%.
✨ Result: Reduced cognitive complexity and line length inside rest_pr_node.

---

PR created automatically by Jules for task 11285044998213271148 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: 32 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: e9d2bbc8-217d-4835-b006-e69d7f0018b2

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb06cd and 3172cd1.

📒 Files selected for processing (1)

• scripts/ci/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 as non-defect refactoring on the implementation shape currently being replaced by #828. This patch only extracts two dictionary builders from rest_pr_node; it changes no scheduler correctness, security, latency, or API-boundary behavior and provides no measured operational gain. #828 is the authoritative merge-authorization safety writer and moves the scheduler into a facade/core architecture, so carrying this readability-only old-layout change adds reconciliation and review cost with no control-plane risk reduction. Reassess only on the integrated post-#828 core if complexity remains material.

[google-labs-jules]

RCA/feasibility: closing unmerged as non-defect refactoring on the implementation shape currently being replaced by #828. This patch only extracts two dictionary builders from rest_pr_node; it changes no scheduler correctness, security, latency, or API-boundary behavior and provides no measured operational gain. #828 is the authoritative merge-authorization safety writer and moves the scheduler into a facade/core architecture, so carrying this readability-only old-layout change adds reconciliation and review cost with no control-plane risk reduction. Reassess only on the integrated post-#828 core if complexity remains material.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.