Skip to content

docs(agents): describe pre mode and RC promotion for any line - #8868

Open
bokelley wants to merge 1 commit into
mainfrom
docs/playbook-rc-any-line
Open

bokelley wants to merge 1 commit into
mainfrom
docs/playbook-rc-any-line

Conversation

@bokelley

@bokelley bokelley commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Summary

.agents/playbook.md § Pre mode still says main uses "tag": "rc" and produces 3.2.0-rc.N, and that RC promotion cuts 3.2.0-rc.0. Neither is true now: main is in 3.3 beta pre mode, and #8865 makes npm run promote:rc derive X.Y.0-rc.0 from package.json.

This PR rewrites that paragraph for any line and keeps the 3.2 history (the 3.2.1 GA over the withdrawn 3.2.0, and the original beta entry commands). It is split out of #8865 because .agents/** is human-gated in Ladon.

Merge after #8865. The new text describes #8865's behavior. No changeset is needed, since this is agent-policy text and not protocol surface.

🤖 Generated with Claude Code

The playbook still said `main` is in 3.2 RC pre mode and that RC
promotion cuts `3.2.0-rc.0`. Main is in 3.3 beta pre mode, and the
promotion now derives `X.Y.0-rc.0` from package.json.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@aao-secretariat aao-secretariat Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ladon verdict: Escalate to human review

Escalate — gated path requires human/CODEOWNERS review.

This PR modifies .agents/playbook.md, which is under a hard, deterministic approval gate (.agents/**). gated_paths is true and review_decision is REVIEW_REQUIRED (not APPROVED), so per decision-table row 2 the outcome must be escalate until a human/CODEOWNERS approval satisfies the gate.

On the merits, this is an editorial-only documentation change (11 net lines, one file) generalizing the pre-mode/prerelease prose to line-based X.Y.0 form and noting main is in 3.3 beta pre mode. The reviewer verified the claims against repo state (.changeset/pre.json tag beta, package.json at 3.3.0-beta.5) and found no Critical/High/Medium findings. No schema, wire-shape, or changeset surface is touched.

The escalation is purely the path gate, not any code concern.

Escalation reasons

  • .agents/playbook.md is under the .agents/** gated-path rule; review_decision is REVIEW_REQUIRED. Human/CODEOWNERS approval is required before this can merge.

Why human review

  • Gated path: .agents/playbook.md matches .agents/** and review_decision is REVIEW_REQUIRED (not APPROVED) — human/CODEOWNERS approval required.
  • This PR touches a path under a hard, non-overridable approval gate (.agents/playbook.md (modified) matches .agents/**) and the current GitHub review decision is 'REVIEW_REQUIRED', not APPROVED. This is a hard gate enforced in code — Ladon cannot auto-approve until a human/CODEOWNERS approval is recorded, regardless of how clean the diff is.

@aao-secretariat aao-secretariat Bot added the ladon/needs-human-review Ladon has escalated this PR for human review. label Nov 9, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ladon/needs-human-review Ladon has escalated this PR for human review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant