docs(release): document live dev-lead next/ring channels + staged-rollout runbook (#499)

[don-petry]

Brings the release docs in line with reality after the dev-lead v1.4.0 rollout: the Phase-2 next/ring0/ring1 channels are now live for dev-lead (previously documented as future state).

• versioning.md — mark next/ring channels live for dev-lead; add a Ring channels table (current ring→repo assignment: .github-private→next, .github→ring0, TalkTerm→ring1, rest→stable), the next→ring0→ring1→stable order, and the check_dev_lead_stub channel rule. Notes pr-review is still stable-only (pending [Phase 2] Add next + per-ring channel tags (blue/green green channel) #499).
• runbook.md — new §2c Staged canary / ring rollout: cut once, advance channel tags ring-by-ring with verify+soak between each, gated at every ring, rollback-at-any-stage. Notes the automated/health-gated version is [Phase 2] Replace PUT-contents clobber deploy with versioned, ring-staged, health-gated promotion #501.

Moves #499 toward closure (docs criterion). Refs #500, #501.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added staged canary and ring rollout procedures to the release runbook
  • Updated release-channel documentation to clarify versioning, agent ring assignments, and the promotion sequence through release channels

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

[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 59 minutes and 40 seconds. 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: 8e719113-4523-40dc-b804-b7d401631dc8

📥 Commits

Reviewing files that changed from the base of the PR and between 5845b8f and 4d772cf.

📒 Files selected for processing (2)

• docs/release/runbook.md
• docs/release/versioning.md

📝 Walkthrough

Walkthrough

Two release documentation files are updated. docs/release/versioning.md is revised to mark dev-lead ring channels (next, ring0, ring1) as live under Phase 1 and adds a ring assignment table with advancement order, pinning, and compliance audit rules. docs/release/runbook.md gains a new §2c describing the cut-once/ring-promote/rollback command sequence.

Changes

Ring rollout documentation

Layer / File(s)	Summary
dev-lead ring channel definitions and semantics docs/release/versioning.md	Marks <agent>/next and <agent>/ring0, <agent>/ring1 channels as live for dev-lead under Phase 1; adds ring assignment table (next, ring0, ring1, stable); specifies advancement order, caller pinning semantics, and compliance audit acceptance criteria (rejects @main and frozen refs); notes pr-review remains stable-only with ring channels pending.
Staged canary rollout procedure in runbook docs/release/runbook.md	Adds §2c with a cut-once immutable target, sequential git tag -f + forced-push promotion through next → ring0 → ring1 → stable, human-gated advancement, soak/validation requirements per ring, rollback as a single reverse tag move, and a pointer to §4 verification.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• petry-projects/.github-private#558: Introduced the per-agent channel-tag cut/promote/rollback runbook and initial ring channel guidance in docs/release/versioning.md that this PR directly extends.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: updating release documentation to reflect live dev-lead next/ring channels and adding a staged-rollout runbook procedure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/dev-lead-ring-channel-docs

---

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

[gemini-code-assist]

Code Review

This pull request documents a staged canary and ring rollout process for dev-lead releases, detailing the ring channels (next, ring0, ring1, stable) and their respective consumers. Feedback on the runbook suggests replacing the automated bash loop with explicit, step-by-step manual commands to prevent accidental, unattended promotions across rings, which would violate the intended soaking and gating requirements.

[don-petry]

Dev-Lead — waiting on PR blockers (intent: review-changes)

PR: #867
No changes were committed, but the PR still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews). The retry cron will re-attempt automatically. Next attempt after: 2026-06-21T12:43:55Z

[don-petry]

Note

@don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically.
Next attempt after: 2026-06-21T12:43:55Z

[don-petry]

Dev-Lead — fix-reviews (applied)

Changes committed and 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-21T13:19:19Z.

[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-21T13:35:13Z.

[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-21T16:06:28Z.

[donpetry-bot]

Automated review — APPROVED ✓

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

Summary

Docs-only PR (2 files, +90/-3) updating release documentation: versioning.md marks dev-lead next/ring0/ring1 channels as live and adds a canonical ring-membership table (host-relative next; ring0 spans .github+.github-private; ring1 = TalkTerm, bmad-bgreat-suite; stable = rest), with the check_dev_lead_stub channel rule; runbook.md adds §2c documenting the staged cut-once / ring-by-ring promotion + rollback sequence. No code, configs, workflows, or scripts touched.

Linked issue analysis

No formal closingIssuesReferences; PR refs #499/#500/#501 and advances #499 (docs criterion). Content aligns with the stated intent: documents the live dev-lead ring channels and the staged-rollout procedure. Ring membership matches the canonical #500 model. No linked-issue gate to block on.

Findings

No blocking findings. The one prior review thread (gemini-code-assist, medium: the original for-loop could promote all rings unattended) is RESOLVED and OUTDATED — the loop was replaced with explicit per-ring git tag -f + push --force blocks, each ending in a '# → verify (§4) + soak' gate, confirmed in the current diff. CodeRabbit review DISMISSED; SonarCloud quality gate passed (0 new issues). Codex was unavailable (usage limit) — non-blocking. MCP secret-scanning tool not exposed in this run; docs-only change carries no credential surface. Triage assessment (low-risk docs) confirmed.

CI status

All required checks green. SUCCESS: CI (Lint, ShellCheck, Secret scan/gitleaks, Agent Security Scan, Compile agentic workflows), CodeQL (actions+python), AgentShield, SonarCloud, holdout-guard, Test-Deletion Guard, unit-tests, dependency-audit (detect), review, dev-lead/dispatch. SKIPPED (non-blocking): dependabot-automerge, ecosystem audit sub-jobs, dev-lead/ci-relay. No failures. mergeStateStatus BLOCKED only on the pending org-leads team review (REVIEW_REQUIRED).

---

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