feat(automation): run pg-erd-cloud hourly NVIDIA NIM review repair

[seonghobae]

Buyer-perceivable gap

Hourly NVIDIA NIM review repair never scanned ContextualWisdomLab/pg-erd-cloud. Live ERD pull requests such as ContextualWisdomLab/pg-erd-cloud#916 (control-character insertion), #918, and #919 target protected main and stalled while Clearfolio, DiskSage, and fast-mlsirm received heartbeats.

Change

• Thin scheduled caller at minute 13, base_branch: main, one dispatch, two-hour same-head retry.
• Job-scoped id-token: write so the reusable scheduler can mint the OpenCode App fallback from GitHub OIDC.
• Maps only PR_REVIEW_MERGE_TOKEN and OPENCODE_APPROVE_TOKEN. Never NVIDIA_NIM_API_KEY on the caller. Never COPILOT_GITHUB_TOKEN.
• Independent pull_request / push / compileall path contracts.
• Local 2× pytest + coverage + interrogate at 100% on this head.

Do not self-approve. Merge remains subject to two-approval + last-pusher ruleset. GitHub review/Checks wait is not a blocker.

Refs ContextualWisdomLab/pg-erd-cloud#916, ContextualWisdomLab/pg-erd-cloud#918, and ContextualWisdomLab/pg-erd-cloud#919.

[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: 40 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

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: e781f95c-94ae-4de2-92ac-d322c63e9aa9

📥 Commits

Reviewing files that changed from the base of the PR and between c47afc2 and 9f47dcc.

📒 Files selected for processing (8)

• .github/workflows/hourly-nvidia-nim-review-repair.yml
• .github/workflows/pg-erd-cloud-hourly-review-repair.yml
• AGENTS.md
• ARCHITECTURE.md
• CHANGELOG.md
• CLAUDE.md
• docs/doctoring/pg-erd-cloud-hourly-review-caller.md
• tests/test_pg_erd_cloud_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.}