ops: add hourly central PR review autofix caller

[seonghobae]

Summary

• schedule a fast-mlsirm-specific PR review-feedback sweep every hour at minute 37
• reuse the pinned organization pr-review-fix-scheduler.yml workflow instead of copying autofix implementation into this repository
• bound each sweep to one dispatch and one-hour same-head retry spacing
• preserve least-privilege caller permissions and add repository contract tests

Scope boundary

The organization PR review/merge scheduler already sweeps the queue more frequently than hourly. This thin caller adds the explicitly requested hourly cadence for actionable review-feedback fixes. It does not create unreviewed product code when the PR queue is empty; product work remains issue- and PR-driven under the same review/check/merge gates.

Security

• central reusable workflow pinned to commit 5983b41ace75040c1d81818171ca7d0f3653254e
• no local runner steps or duplicated agent implementation
• at most one autofix dispatch per hourly sweep
• no contents-write or pull-requests-write permission in the caller
• existing central same-head and same-repository validation remains authoritative

Validation

• contract tests pin cadence, target repository, central workflow identity, dispatch bounds, and permissions
• full repository CI/security/SAST gates remain required before merge

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 877150c8-d5b4-4845-af7a-cd47e02d5a73

📥 Commits

Reviewing files that changed from the base of the PR and between 9baf11e and 8efbf56.

📒 Files selected for processing (2)

• .github/workflows/hourly-pr-review-fix.yml
• tests/test_hourly_pr_review_fix_workflow.py

---

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

[seonghobae]

Blocked on ContextualWisdomLab/.github#706. The current pinned reusable-workflow revision checks out privileged scheduler code from mutable main, while GitHub's reusable-workflow context belongs to the caller. #706 changes the central workflow to check out job.workflow_repository at immutable job.workflow_sha and adds a regression contract. Keep this caller draft until #706 merges, then pin the caller to that exact merge SHA, remove the obsolete canonical_ref input, rebase on current main, and rerun all same-head checks.

[seonghobae]

Closing this caller rather than leaving an insecure or permanently blocked workflow in the queue. Its required central hardening PR ContextualWisdomLab/.github#706 was closed without merge, so there is no immutable safe revision to pin. The organization scheduler already covers this repository more frequently than hourly; duplicating the caller would add operational surface without product value. Reopen only after the reusable workflow checks out job.workflow_repository at immutable job.workflow_sha and a reviewed merge SHA is available.