feat(automation): run hourly bounded review repair

[seonghobae]

Summary

Hourly bounded review-repair workflow caller for fast-mlsirm (privileged implementation remains in org .github control plane). Surgical re-apply of draft #558 with re-rendered CHANGELOG fragments (prior tip failed fragment contract only).

Evidence

• Local: pytest tests/test_hourly_review_repair_workflow.py tests/test_changelog_fragment_contract.py — 12 passed

Product gates

Merge when python (aggregate + 3.12/3.14), rust, package, fuzz are green.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 24 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4358e97f-f8fb-44fa-ad80-652a9846d2ef

📥 Commits

Reviewing files that changed from the base of the PR and between 3b297cd and 5ccf115.

📒 Files selected for processing (5)

• .github/workflows/hourly-review-repair.yml
• CHANGELOG.md
• docs/changelog.d/hourly-review-repair-caller.md
• docs/doctoring/hourly-review-repair-caller.md
• tests/test_hourly_review_repair_workflow.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]

Draft-state correction after live dependency RCA. Exact product head remains d5746dd888f029c7a462391eaa33f82474f9861b; protected product main is now bf51cc1849c6258d54b8e2f8c67be8ce02575114, so this branch is ahead 1 / behind 3. More importantly, the caller pins central commit 2f16cca4aae2d11ccc928f8e03fdcbd97a96d5a2; fresh compare against ContextualWisdomLab/.github protected main 6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba is diverged (ahead 59 / behind 33), so that pinned implementation is not protected-central authority. Central #782 remains open on a later head. This PR's own doctoring says it must remain Draft until the accepted central implementation reaches protected central main and the product pin is reconciled to that immutable commit. I therefore converted #763 back to Draft rather than allowing CI success to masquerade as deployable activation. Reconcile product main only after the central dependency lands; no weakening or unmerged-central pin is acceptable.