pm-dispatch: 调度策略四项(维护者 2026-08-13)—— 被依赖卡提权标签、bug 提权、紧急卡 fable 直接分诊、跨车道简单依赖直接接手

[hotlong]

维护者在 skills 席聊中提出四项调度策略意见并指示与 #8428 一起处理(2026-08-13,原话逐字,未翻译):

被依赖的卡片是不是应该通过label标注提高优先级。项目经理处理任务清单时,bug 是不是应该提高优先级。

对于比较紧急的卡片,是否应该使用 fable 5 子agent直接分诊;如果当前任务依赖其他赛道的任务,如果判断简单,是否可以直接接手而不必持续等待。

和我刚才几个意见一起。

四项的 PM 解释(skills 席落地口径;维护者可在 PR 评审时逐条否决)

① 被依赖卡提权标签。 新标签 pm:blocking = 「本 open 卡有 open 的下游依赖者」。⛔ 不手工维护 —— 从卡身 Blocked-by: 引用的反向索引机械推导(分诊简报已为决策箱指标现算这个索引,写标签只是把算出的结果缓存到列表页可见的地方);分诊轮 sweep 时写入/摘除,依赖者全关即摘。消费查询:排序规则(下条)+ 列表页扫描。种子入 scripts/pm/ensure-pm-labels.sh(该文件的既有不变量:每个种子标签必须有具名消费查询)。

② bug 提权 + 队列全序。 车道队列取卡顺序成文(现状是 FIFO/自由裁量):priority:p0 > pm:blocking > type Bug > 其余按卡龄。理由:p0 是维护者显式裁定;blocking 卡住别的车道的吞吐,一张挡多张;bug 是已坏的不变量,先于增强。

③ 紧急卡 fable 直接分诊。 紧急卡(维护者点名、或 p0 嫌疑)⇒ 座位可立即起一个 claude-fable-5 分诊子代理,不等分诊 Routine 的班次节奏。授权面 = 分诊(定级/路由/标签/分诊评论既有格式),⛔ 不写码不认领。产出落卡上,与 Routine 分诊同格式同效力。

④ 跨车道简单依赖直接接手。 本车道卡被他车道卡挡住、且该阻塞项判断简单(机械、规格清楚、S 级)⇒ 被挡座位可直接接手做掉,⛔ 不持续等待。纪律不减:在他车道卡上走完整认领(assign + 会话 ID + 分支评论)、尊重该车道热文件串行队、完工后卡上留收单注记。边界:凡带设计判断/语义权衡的,仍归属地车道 —— 本条只覆盖「等一周 vs 做十分钟」的形状。

落地位置与约束

• 排序全序与三条新规入 .claude/skills/pm-dispatch/ 文本:SKILL.md 仅骨架行(⚠️ 686/686 顶格,增行须同 PR 等量抵扣),细则入 references/(dispatch-runbook.md 或就近既有节)。
• pm:blocking 种子 + 消费查询具名,改 scripts/pm/ensure-pm-labels.sh(先例:该文件 target: 家族的 rider 纪律)。
• ⛔ 技能文本不引 issue 号(check:pm-skill-id-lint);决策帧多副本改动跑 check:skill-frame-sync。
• 热文件区域申报(与 [finding] pm-dispatch: shift-end is coupled to in-flight-zero, so one slow cloud card holds the seat (and the maintainer) hostage for hours — define "hot handover" instead #8428 并行的依据):本卡区域 = SKILL.md 队列/分诊/派发节 + references 对应节 + scripts/pm/ensure-pm-labels.sh;[finding] pm-dispatch: shift-end is coupled to in-flight-zero, so one slow cloud card holds the seat (and the maintainer) hostage for hours — define "hot handover" instead #8428 区域 = SKILL.md 波次收工点块 + references/seat-post-protocol.md。两区不相交。
• model: claude-fable-5 强制(pm-dispatch-edit 卡);ADR-class 三件套:draft PR、⛔ 不自动合并/入队/ready,维护者人工处理。

[hotlong]

Claim — skills seat (#7623), session session_01139NJ9Wg5pFeZi1Zh8WLg6, branch claude/issue-8433-dispatch-priority-rules, mode:subagent, model: claude-fable-5 (mandatory — pm-dispatch-edit card), size M. Promotion authority: the four items are the maintainer's own opinions, instructed 「和我刚才几个意见一起」(together with #8428, dispatched in parallel under the disjoint region declaration in the card body).

Gates (derived at claim time from SKILL.md + dispatch-runbook.md + ensure-pm-labels.sh): check:doc-authoring, check:doc-formula-expressions, check:nul-bytes, check:pm-skill-id-lint, check:pm-skill-ratchet, check:skill-frame-sync.

Merge path: ADR-class terminal three-piece — draft PR, ⛔ no auto-merge/queue/ready-flip by the seat; the maintainer handles.

---

Generated by Claude Code

[hotlong]

Re-dispatch with a recorded downgrade — skills seat (#7623), session session_01139NJ9Wg5pFeZi1Zh8WLg6, branch claude/issue-8433-dispatch-priority-rules, mode:subagent, size M.

Container & model: model: opus — DOWNGRADED from the mandated claude-fable-5. Reason, as the quota-exhaustion exemption requires: the fable tier is exhausted account-level right now. Two consecutive dev agents on this lane died on it today; harness text verbatim: 「You've reached your Fable 5 limit.」 The exemption ruled by the maintainer in seat chat 2026-08-13 (「fable 如果用完了,可以用 opus」) applies — floor is opus, ⛔ never lower. Card #8451 carries the ruling and the measured instance; it is queued to write this into the skill text.

Prior attempts on this card left no work: the first agent was killed by a container restart before any edit, the second by the fable wall while still reading. The worktree is clean; this dispatch starts from a verified-clean base.

Scope, gates, region declaration and the ADR-class merge path are unchanged from the original claim above.

---

Generated by Claude Code

[hotlong]

Released — 收单注记 for the next seat. Maintainer instruction in seat chat, 2026-08-13, verbatim: 「8433 我让新项目经理处理,你下班吧」. Assignee removed, the seat's dispatched agent stopped, worktree torn down. This card is FREE — claim it normally.

State: zero work exists. Three dispatch attempts, all killed by infrastructure before producing anything:

1. claude-fable-5 agent — container restart, died before any edit;
2. claude-fable-5 agent — account-level Fable 5 limit, died while still reading;
3. opus agent (downgraded under the quota exemption, pm-dispatch: fable 强制条款需要额度耗尽豁免 —— 「fable 如果用完了,可以用 opus」(维护者 2026-08-13) #8451) — stopped by the seat on this stand-down, had only begun reading.

No branch was pushed, no PR opened, claude/issue-8433-dispatch-priority-rules exists only as a local name that is now gone. Start clean from current origin/main.

What the successor needs that is not obvious from the card body:

• Region discipline still binds. Your region = SKILL.md queue/triage/dispatch sections + the matching references/ sections + scripts/pm/ensure-pm-labels.sh. ⛔ SKILL.md's 波次收工点 block and references/seat-post-protocol.md belong to PR docs(pm-dispatch): 收班 = 状态 flush + 看护显式移交 — decouple shift-end from in-flight-zero #8453 (open draft, reviewed ACCEPT, awaiting the maintainer's hand-merge) — rebase around it. ⛔ SKILL.md's Model tiering section belongs to pm-dispatch: fable 强制条款需要额度耗尽豁免 —— 「fable 如果用完了,可以用 opus」(维护者 2026-08-13) #8451 (queued, undispatched), which was deliberately serialized behind this card because its text abuts item 3's model wording.
• SKILL.md is at 686/686, shrink-only. Every added line must be funded by an equal removal in the same PR; the funding should be accounted line-by-line in the PR body.
• Model: this is a pm-dispatch-edit card ⇒ claude-fable-5 mandated. If fable is still exhausted, the maintainer's exemption (pm-dispatch: fable 强制条款需要额度耗尽豁免 —— 「fable 如果用完了,可以用 opus」(维护者 2026-08-13) #8451) allows opus — floor is opus, never lower — with the downgrade and its reason recorded in the claim comment's Container & model line.
• Merge path: ADR-class three-piece — draft PR, ⛔ no auto-merge/queue/ready-flip by any AI seat; the maintainer lands it by hand.
• One item carries an open interpretation the maintainer may want to correct at review: item 2's ordering places pm:blocking ahead of type Bug. The rationale is on the card; it is the PM's reading, not the maintainer's words.

---

Generated by Claude Code