🧹 코드 상태 개선: 복잡도를 줄이기 위해 run_handoff 리팩터링

[seonghobae]

🎯 무엇을: scripts/ci/noema_review_handoff.py의 run_handoff 함수 내에 중복되는 GitHub API 일시적 오류 처리 로직을 _handle_transient_failure 헬퍼 함수로 추출하여 복잡도를 낮췄습니다.
💡 왜: 기존 함수는 너무 복잡하다는 경고(C901, 복잡도 14)가 있었습니다. 중복된 로직을 분리함으로써 코드 흐름이 간결해지고 복잡도가 12로 감소하여 가독성과 유지보수성이 향상되었습니다.
✅ 검증: 전체 테스트 스위트(pytest)가 정상적으로 통과함을 확인했고, flake8의 복잡도 경고가 해결되었으며 interrogate를 통한 docstring 커버리지가 100%로 유지되는 것을 검증했습니다.
✨ 결과: 인지적 복잡도가 낮아진 더 깔끔한 run_handoff 함수가 되었습니다.

---

PR created automatically by Jules for task 18210960502042871306 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: 57 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: 8e123174-b55a-4b9f-ae41-e656e5287e41

📥 Commits

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

📒 Files selected for processing (1)

• scripts/ci/noema_review_handoff.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 maintainability-only work with no current operational root cause. The patch extracts two existing transient GitHub API error branches into _handle_transient_failure but preserves retry count, redacted diagnostics, backoff, dispatch behavior, and return semantics. It does not address the Noema OIDC producer/consumer envelope defect owned by #834 or any measured handoff outage. With substantive control-plane repairs still open, a separate full review/check/approval lane for a C901 reduction from 14 to 12 has negative leverage. Reconsider after the OIDC path is integrated and runtime-proven.

[google-labs-jules]

RCA/feasibility: closing unmerged as maintainability-only work with no current operational root cause. The patch extracts two existing transient GitHub API error branches into _handle_transient_failure but preserves retry count, redacted diagnostics, backoff, dispatch behavior, and return semantics. It does not address the Noema OIDC producer/consumer envelope defect owned by #834 or any measured handoff outage. With substantive control-plane repairs still open, a separate full review/check/approval lane for a C901 reduction from 14 to 12 has negative leverage. Reconsider after the OIDC path is integrated and runtime-proven.

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