🧹 [코드 상태 개선] pr_review_merge_scheduler의 self_test 함수 리팩토링

[seonghobae]

🎯 무엇을:scripts/ci/pr_review_merge_scheduler.py에 있는 지나치게 길고 복잡했던 self_test 함수를 _test_split_repo, _test_inspect_pr 등 6개의 작은 헬퍼 함수로 분리하여 리팩토링했습니다.
💡 왜: 코드의 복잡도를 낮추고 테스트 로직을 모듈화하여, 유지보수성과 가독성을 크게 높이기 위함입니다.
✅ 검증:pytest를 통해 모든 기존 테스트가 완벽히 통과함을 확인했고, black 포맷팅과 interrogate 100% Docstring 커버리지 테스트, bandit 보안 분석을 모두 통과했습니다.
✨ 결과: 기존의 테스트 기능을 완벽하게 보존하면서 CI 스케줄러 자체 테스트 코드의 품질을 획기적으로 향상시켰습니다.

---

PR created automatically by Jules for task 15265663168741647970 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:42 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: 56b69e7f-62b7-45c0-9faf-6b8e65c01b8d

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb06cd and 0dae1ba.

📒 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 superseded by the scheduler safety restructuring in #828. This PR expands/refactors the old monolithic scheduler self_test on protected-main shape (+462/-154) without addressing a distinct production defect. #828 is actively replacing that module with an auditable approval-policy facade plus delegated core while changing merge authorization semantics; self-test organization must follow that final architecture. Merging this branch now would create large avoidable reconciliation churn on the exact security writer. Reassess self-test decomposition after #828 reaches protected main and its exact-head/runtime contracts are stable.

[google-labs-jules]

RCA/feasibility: closing unmerged as superseded by the scheduler safety restructuring in #828. This PR expands/refactors the old monolithic scheduler self_test on protected-main shape (+462/-154) without addressing a distinct production defect. #828 is actively replacing that module with an auditable approval-policy facade plus delegated core while changing merge authorization semantics; self-test organization must follow that final architecture. Merging this branch now would create large avoidable reconciliation churn on the exact security writer. Reassess self-test decomposition after #828 reaches protected main and its exact-head/runtime contracts are stable.

Understood. Acknowledging that this work is superseded by #828 and stopping work on this task to avoid merge conflicts.