ci: schedule hourly approved-PR steward

[seonghobae]

Summary

Adds an hourly pull-request stewardship workflow at minute 17 of every hour (UTC), with manual dispatch support.

The steward is intentionally fail-closed:

• considers only non-draft PRs from trusted authors in the same organization repository;
• updates trusted branches that are behind main, then waits for fresh evidence;
• requires GitHub's aggregate review decision to be APPROVED;
• requires every configured required check to pass;
• binds the squash merge to the exact reviewed and checked head SHA;
• relies on repository rulesets and branch protection as the final authority;
• uses least-privilege permissions and a concurrency guard.

It does not repeatedly rerun genuine failures or bypass requested changes. Those remain inputs to the interactive review/fix loop.

The cron is deliberately offset from the top of the hour to reduce scheduled-run congestion.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 36 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: c79949cf-1a31-4317-8823-378e76e553b0

📥 Commits

Reviewing files that changed from the base of the PR and between 5bab73e and f2aa6b3.

📒 Files selected for processing (1)

• .github/workflows/hourly-pr-steward.yml

---

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

[seonghobae]

@coderabbitai review

Please review the exact current head of the fail-closed hourly PR steward. It updates only trusted same-repository branches, waits for fresh evidence after branch updates, requires aggregate approval and every required check, and binds auto-merge to the reviewed head SHA.

[coderabbitai]

@seonghobae I will review the current head of #40. I will verify the trust boundary, post-update evidence gate, approval and required-check gates, and head-SHA binding.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[seonghobae]

Superseded by #42. The exact fail-closed hourly steward workflow has been integrated unchanged into the commercial-hardening branch so the repository maintains one protected current-head validation stream instead of duplicating CI, security scans, and review requests for the same release candidate.