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

[seonghobae]

Buyer-perceivable gap

A paying buyer of appguardrail (SAST / assurance / Strix-finding collector) would feel live pull requests targeting protected develop never receiving hourly NVIDIA NIM review repair. Existing heartbeats scan Clearfolio, DiskSage, and fast-mlsirm against main. Live heads such as ContextualWisdomLab/appguardrail#964, ContextualWisdomLab/appguardrail#967, ContextualWisdomLab/appguardrail#970, and ContextualWisdomLab/appguardrail#971 never enter those callers.

What this PR does

• Adds a thin minute-41 caller for ContextualWisdomLab/appguardrail with base_branch: develop.
• One dispatch, 50-PR scan, two-hour same-head retry, non-cancelling single-flight group.
• Workflow token stays contents: read; job-scoped id-token: write for OIDC. Maps only PR_REVIEW_MERGE_TOKEN and OPENCODE_APPROVE_TOKEN.
• Never receives NVIDIA_NIM_API_KEY and never introduces COPILOT_GITHUB_TOKEN. Model execution stays in the central worker.
• APA 7th doctoring plus ADR/CHANGELOG/ARCHITECTURE updates.

Verification

Local 2× coverage run -m pytest tests && coverage report --show-missing plus interrogate: 1122 passed, coverage 100%, interrogate 100%.

Closes no issue. GitHub Project #1 is the live tracker.

[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: 39 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: e4816e10-e033-470f-95d5-e3644e6b8c9a

📥 Commits

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

📒 Files selected for processing (8)

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