feat(automation): run naruon hourly NVIDIA NIM review repair

[seonghobae]

Buyer-visible gap

A paying buyer of naruon (the email workspace) would feel live platform pull requests never receiving hourly NVIDIA NIM review repair. Existing heartbeats scan Clearfolio, DiskSage, and fast-mlsirm against main. Live ContextualWisdomLab/naruon#1388, #1387, #1386, #1383, #1382, and #1380 target protected develop.

Bounded change

• Add naruon-hourly-review-repair.yml at minute 11, base_branch: develop, one dispatch, two-hour same-head retry, job-scoped id-token: write.
• Keep NVIDIA_NIM_API_KEY on the worker. Never COPILOT_GITHUB_TOKEN.
• Machine-checkable contracts, APA 7th doctoring, ADR/CHANGELOG/ARCHITECTURE update.

Verification

Local exact-tree evidence: 1122 passed twice, scripts/ci statement/branch coverage 100%, interrogate 100%.

Refs ContextualWisdomLab/naruon#1388, ContextualWisdomLab/naruon#1380.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 11 minutes

Limit details: You’ve used the included review currently available.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 64217b3d-db34-4633-b79d-f61af58ee8da

📥 Commits

Reviewing files that changed from the base of the PR and between 9e9f59f and 04199d4.

📒 Files selected for processing (10)

• .github/workflows/hourly-nvidia-nim-review-repair.yml
• .github/workflows/naruon-hourly-review-repair.yml
• AGENTS.md
• ARCHITECTURE.md
• CHANGELOG.md
• CLAUDE.md
• docs/automation/hourly-review-repair.md
• docs/doctoring/naruon-hourly-review-caller.md
• tests/test_hourly_scheduler_runtime_budget.py
• tests/test_naruon_hourly_review_caller.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]

Rebased onto current main 9e9f59f3; resolved shared hourly-contract conflicts while preserving naruon paths. Caller tests passed (6 passed); actionlint passed on both changed workflows; diff check passed. Project #1 is In Progress.

[seonghobae]

Superseded by #1143, the current-main naruon hourly review-repair caller. #1143 preserves the bounded central scheduler contract on protected develop, adds current contract/doctoring coverage, and has auto-merge armed. Closing this older caller prevents duplicate hourly schedules.