docs(pm-dispatch): release board protocol — target:<major> as a standing release-readiness axis - #6087
Merged
Conversation
维护者痛点:「想发版时,哪些优先,始终没有渠道知道」;历次一次性标注均因无生产 者/无消费者/无所有者而腐烂。本次把发版轴接进常设机器:二元判据四类(已发布面 缺陷/契约撒谎/存量数据/道歉级含首小时体验);分诊座位唯一生产(同 domain:* 纪律);三处消费者(维护者标签查询、step 3 批次优先、step 9 第四健康指标); 与发现分诊轮同节奏的鲜度复查;发版时刻 = 清板三选一(修/摘/明示接受留痕)。 存量 309 条已于 2026-08-06 全量清过(46 条上板),此后只有增量。 按 #5925-7 裁决的零混装纪律,本件不含任何搬移;瘦身另行纯搬移 PR。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GcjbQLUQKysMU9uXB34iyv
claude
Bot
added
the
skip-changeset
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
size/s
documentation
os-zhuang
marked this pull request as ready for review
August 7, 2026 02:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the release board protocol (
target:<major>) to the PM dispatch skill — a standing release-readiness axis, ruled by the maintainer on 2026-08-06 after the v17 release-triage sweep.Maintainer's original pain point (quoted verbatim, untranslated per language policy): 「我想发版本了,不可能清单上这么多问题都处理,那哪些优先,我始终没有渠道知道。」 Previous one-shot sweeps rotted because the label had no producer, no consumer, and no owner. This PR wires all three into the standing machinery:
priority:p0; ordering not exemptiontarget:<major>No moves, no rewording of existing text (+35/−1) — per the #5925-7 ruling the slimming split ships as its own pure-move PR, next in this serial chain.
Authorization (Guardrails exception clause)
Maintainer-directed work, same session chain as #6029: the release-board mechanism was proposed by the PM and approved by the maintainer in conversation (2026-08-06, 「扫」 directive + acceptance of the six-point continuous-iteration design; PM session
session_01GcjbQLUQKysMU9uXB34iyv). Walkthrough belongs to the maintainer; this session does not self-approve or self-queue without it.Verification
Docs-only (
.claude/internal tooling,skip-changesetlabel path). Markdown structure self-checked; the board itself is already live (objectstack 43 / objectui 3 graded 2026-08-06, queries linked from #4604-adjacent reporting).🤖 Generated with Claude Code
https://claude.ai/code/session_01GcjbQLUQKysMU9uXB34iyv
Generated by Claude Code