pr-review: dogfood ring-0 on @pr-review/next (self-host canary)

[don-petry]

Why

Enabling the downstream-impact pass (#748 / #815) should roll out ring-by-ring, not fleet-wide at once. Per docs/initiatives/agentic-release-strategy.md §5, Ring 0 = .github-private self-host runs @pr-review/next; a release only reaches @pr-review/stable (the fleet) after the ring-0 soak proves healthy.

Today the self-host trigger pins @pr-review/stable, so there is no canary — there's no way to dogfood a new pr-review version on this repo before everyone gets it.

What

Repin pr-review-trigger.yml (this repo's own review caller) from @pr-review/stable → @pr-review/next (workflow + agent_ref). That makes .github-private the ring-0 canary: its own PR reviews run next first.

This is the code half of enabling downstream-impact via the ring approach; the tag operations are the other half (below).

⚠️ Merge ordering (the next tag must exist first)

@pr-review/next must resolve, or self-host reviews break. These tag ops are OrgAdmin/automation-gated (an agent on GITHUB_TOKEN is 403-blocked by the pr-review/** ruleset), so they're yours:

# 1. Immutable release at current main (carries DOWNSTREAM_IMPACT_ENABLED)
scripts/cut-release.sh pr-review 1.7.0 --ref origin/main --push
# 2. Point ring-0 (next) at it
git tag -f pr-review/next pr-review/v1.7.0 && git push -f origin pr-review/next
# 3. THEN merge this PR
# 4. Dogfood on .github-private PRs; verify the “Downstream impact” annotation
# 5. After a healthy soak, promote to the fleet:
git tag -f pr-review/stable pr-review/v1.7.0 && git push -f origin pr-review/stable

Live test (after this lands on next)

Open a PR here touching a mapped shared surface (e.g. a comment-only edit to scripts/lib/ci-status.sh, which pr-review.yml's surface_sources lists). The verdict should then carry a Downstream impact section naming consumer repos. I'll drive and verify that once next is cut.

🤖 Generated with Claude Code

https://claude.ai/code/session_014djuNDBa3GASVDLQPXXg9L

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Review limit reached

@don-petry, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 1 hour. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a2c79a2e-1cd6-4acd-8fbf-9b754a3107a7

📥 Commits

Reviewing files that changed from the base of the PR and between 648b80b and a42e92c.

📒 Files selected for processing (1)

• .github/workflows/pr-review-trigger.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/pr-review-ring0-next-dogfood

---

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 and usage tips.}

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[don-petry]

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning

Issues addressed: 0
Files changed: none
Skipped (informational): SonarCloud quality gate passed with no new issues — no actionable fixes required
```
The PR is clean from the bot's perspective. No changes needed.

[donpetry-bot]

Superseded by automated re-review at a42e92cc504e1fa8b0d9b6ebfe0b9928acf88ca9 — click to expand prior review.

Review — fix requested (cycle 1/3)

The automated review identified the following issues. Please address each one:

Findings to fix

Automated review — NEEDS HUMAN REVIEW

Risk: LOW
Reviewed commit: dcf3e0570588209d796218939eaf5fe5eccbeefb
Review mode: triage-approved (single reviewer)

Summary

Repins this repo's own pr-review trigger (.github/workflows/pr-review-trigger.yml) from @pr-review/stable to @pr-review/next for both the reusable 'uses:' and 'agent_ref:', making .github-private the ring-0 canary per docs/initiatives/agentic-release-strategy.md §5. The functional change is correct: the pr-review/next tag already exists and resolves to ceab48a (== pr-review/v1.7.0), so the merge-ordering precondition the PR flagged is already satisfied and self-host reviews will resolve. CI is fully green. One maintainability defect: the file's header comment block (lines 3-17) was not updated and now contradicts the change.

Linked issue analysis

No formal linked/closing issue (closingIssuesReferences empty). The PR references initiative work #748/#815 (downstream-impact pass) as context; this change is the ring-0 enablement step for that initiative. Scope matches the stated intent.

Findings

1. (MEDIUM, maintainability) Stale, self-contradicting header comment.
The uses:/agent_ref: were repinned to pr-review/next, but the explanatory
header block (lines 3-17 of .github/workflows/pr-review-trigger.yml) still
describes the old behavior and now contradicts the code:

• Line 6: "invokes the reusable pinned to pr-review.yml@pr-review/stable, passing agent_ref: pr-review/stable" — no longer true.
• Lines 8-9: "this repo's PRs are always reviewed by the known-good stable release" — now runs next.
• Lines 16-17: "To promote a new pr-review version, move the pr-review/stable channel tag … This file never changes." — this very PR changes the file, and ring-0 dogfooding means it now tracks next, not stable.
  This is a deliberately-documented "thin stub" whose comments advertise invariants;
  leaving them inverted will mislead future maintainers about which channel self-host
  runs on. Recommend updating the header to describe the ring-0/next behavior.

2. (informational) Merge-ordering precondition — already satisfied.
The PR body warns that pr-review/next must resolve first or self-host reviews
break. Verified via git ls-remote: pr-review/next -> ceab48a, identical to
pr-review/v1.7.0. The gated tag ops appear already done, so no merge-order
hazard remains at this SHA. (Worth a human confirming the soak/promotion plan.)

CI status

All required checks green: CI (Lint, ShellCheck, Compile agentic workflows, gitleaks secret scan, Agent Security Scan), CodeQL (actions + python), SonarCloud (Quality Gate passed, 0 new issues), unit-tests, bats, validate-agent-profiles, AgentShield, holdout-guard. Advisory bots non-actionable: codex & coderabbit rate-limited, gemini unsupported file type, dev-lead reported no changes needed. mergeStateStatus=BLOCKED only because org-leads review is required (reviewDecision=REVIEW_REQUIRED).

---

Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.

Additional tasks

1. Resolve all unresolved review thread comments from other reviewers
2. Ensure all CI checks pass after your changes
3. Rebase on the target branch if behind
4. Do NOT modify files unrelated to the findings above

The review cascade will automatically re-review after new commits are pushed.

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[donpetry-bot]

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-20T17:58:05Z.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[donpetry-bot]

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-20T19:11:07Z.

[donpetry-bot]

Automated review — APPROVED ✓

Risk: MEDIUM
Reviewed commit: a42e92cc504e1fa8b0d9b6ebfe0b9928acf88ca9
Review mode: triage-approved (single reviewer)

Summary

Repins the self-host ring-0 trigger stub (.github/workflows/pr-review-trigger.yml) from @pr-review/stable to @pr-review/next for both the reusable 'uses:' ref and the 'agent_ref' input, plus header-comment updates. 1 file, +15/-9 (mostly comments). This makes .github-private the ring-0 canary that dogfoods the 'next' channel before fleet promotion, per docs/initiatives/agentic-release-strategy.md §5.

Linked issue analysis

No formal closing issue (closingIssuesReferences empty). This is a rollout/enablement step referencing #748/#815 (downstream-impact pass) and #497/#506 (self-hosting circular-dependency break). The PR's intent — establish a canary channel before fleet rollout — is consistent with the referenced initiative and is fully addressed by the single-line repin.

Findings

No blocking findings.

• Allowed-input scope: pr-review-trigger.yml is a thin trigger stub; changing the channel-tag pin is the documented promotion mechanism (the header itself states the file changes only when the ring-0 channel changes). Within allowed scope. ✓
• Security: no new permissions, secrets, or untrusted code paths. Moving between two same-repo channel tags preserves the existing pinning model (stable was already a mutable channel tag), so no new GitHub Actions security smell.
• Operational caveat (non-blocking, author-owned): per the PR body, the pr-review/next tag must be cut/advanced BEFORE this merges or self-host reviews 403/fail to resolve. These tag ops are OrgAdmin/automation-gated and explicitly owned by the author; nothing in this diff can enforce that ordering, so it is flagged for awareness only.

CI status

All required checks green; remaining are expected SKIPs (dependency-audit ecosystems, dependabot-automerge, dev-lead/ci-relay). Notable passes: shellcheck, ShellCheck, Lint, CodeQL (actions+python), Agent Security Scan, AgentShield, Secret scan (gitleaks), gh-aw-compile, Compile agentic workflows, validate-agent-profiles, unit-tests, bats, SonarCloud. mergeStateStatus=BLOCKED only due to REVIEW_REQUIRED (this review).

---

Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.