docs(pm-dispatch): one patrol routine per seat, not per project - #28739

domain:skills#2 · marchtian · session_017ihL2g7RyXa8ErM6GAkHyc

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: ba301e3691ab0e71abff8951b53bb3fa57052a4d
Local-runs: none
Scope: .claude/skills/pm-dispatch/SKILL.md + references/seat-lifecycle.md 〈座位贴协议〉, references/project-forms.md 〈席位是读出来的〉, references/seat-post-protocol.md (:9, :66), references/execution-duties.md (:157), references/cross-repo-coordination.md (:13), references/dispatch-runbook.md 〈巡查常设项〉

Inputs read: card #28699 body + comments 6559597861, 6560370830, 6560553542; PR #28739 body, file list (1 file, +1/-1), net diff origin/main...ba301e36; check-runs on the head at 2026-11-01T16:26Z. The dispatch order and the dev report's gate table were not used as evidence; the tree and the check-runs were.

① Derived judgments

• Accept-set: none changes. The diff is one rules line in an internal skill (metadata.internal: true, lives in .claude/, never in the published skills/ dir); no schema, no code, no consumer. Right.
• Public surface: none. Governed path .claude/** is hit, so the face is rules and the tier is CONTRACT_REVIEW_TIER by path; the PR stays draft under the governed-surface guard (check-run Governed Surface Queue Guard: success). Right.
• Unit of the patrol routine: 「每席一个」 is scoped by the line's own subject 「项目席唤醒」, so it reads as one routine per project seat, director excepted, triage included (project-forms.md:26 「坐席即建巡查 routine…分诊席加每小时裸卡轮;总监席不建」). Routine 席 is untouched: the line never governed it and execution-duties.md:157 keeps the two wake paths apart. Right.
• Line budget on the head, measured: SKILL.md 319 → 319 lines; line 72 is 115 bytes (118 on main), under the 120-byte cap scripts/pm/check-skill-line-ratchet.mjs documents. Right.
• Dedupe of the old unit: git grep 每项目一个 -- .claude has zero hits on the head. Right as stated, but see ④ for the sibling phrase it does not cover.

② Semver level

• Nothing is published by .claude/**; skip-changeset is on the PR and check-run Check Changeset: success. Right.
• Clause-②: no on the PR body: no declared capability is added, narrowed or removed; the line restates an operating rule for seats, not a spec. Right.

③ Boundary flags

The report lists three deviations and open_questions: [].

• Flag 1 (attribution HTML comment as the PR body's first line): answered — .claude/agents/os-dev.md:321 names exactly this as the harness exception (keep it, report it, Fixes #n follows); Fixes #28699 follows after the harness's second line, and check-run PR-body guards: success. Accepted.
• Flag 2 (PR body ends with the 🤖 Generated with line, not the AGENTS.md session-URL footer): answered — AGENTS.md:430 names the session-URL form for PR bodies, and the same section makes body prose the durable attribution; the body carries Session: session_017ihL2g7RyXa8ErM6GAkHyc in prose. Not a tree defect, no gate reads it. should-fix (PR body only): replace the tail line with the AGENTS.md form on the next body edit; ⛔ not a second footer.
• Flag 3 (「每席」 instead of a literal 「每席位线程」): answered — 「每席位线程一个」 would be 124 bytes and red under the ratchet; 「每席」 is the word project-forms.md:25 (「每席开一条席位线程」), project-forms.md:36, seat-post-protocol.md:9 and dispatch-runbook.md:134 already use for the same unit, so it is the house term, not a shortening. Accepted.
• Claim-side note, not a dev flag: the claim ran the dev on opus against a MANDATORY CONTRACT_REVIEW_TIER path and named this skill-face review as the compensation. This record is that review; nothing else is owed on it.
• No open_questions to escalate.

④ Design judgment

hits file: .claude/skills/pm-dispatch/SKILL.md (line 72). Scenario it is accepted against: the card's measured reach — one fleet project seated on three lanes (pm-dispatch ui skills plus a spec seat), each seat an hourly patrol bound to its own seat thread; the skill has no separate eval prompt, so that measurement is the scenario.

Read against the cited code on this head:

• seat-lifecycle.md:41 「坐席即建自绑巡查 routine、存根记 Patrol:、发 seat-online;收班同笔删它」: creation, record and deletion all keyed to the act of taking a seat. Per seat.
• project-forms.md:25-26 「每席开一条席位线程」 then 「坐席即建巡查 routine…总监席不建」: one thread per seat, one routine on seating, director excepted. Per seat.
• seat-post-protocol.md:9 (多席车道每席一贴) and :66 「项目席巡查默认每小时(总监席无),现值只记存根 Patrol: TRIGGER_ID · CRON」: the routine's id lives on the seat's own stub. Per seat.
• cross-repo-coordination.md:13, dispatch-runbook.md:134: a lane splits into seats, each with its own post and thread. Per seat.

Attempts to break it:

• Single-seat project: 「每席一个」 and 「每项目一个」 coincide; nothing regresses.
• One account, two seats in one project: a routine fires into one session and each seat is its own thread (project-forms.md:25), so 「自建自绑」 is only satisfiable per seat; the old per-project reading left every seat but one unwoken, which is the failure the card measured. The new line is the only one of the two the references can execute.
• Director: excepted on the line and in project-forms.md:26, seat-post-protocol.md:66. Coherent.
• Triage seat: builds one plus the hourly bare-card round (project-forms.md:26); 「每席」 includes it. Coherent.
• Epic PM (seat-lifecycle.md 〈Epic 子树车道〉): a dedicated session that never doubles as a domain:* seat; a per-seat routine does not collide with it.
• Ratchet / frame / prose gates: the line is 115 bytes, the file is net 0, the decision frame is untouched (check-run Type Check · source gates, which runs check:skill-frame-sync: success); Lint · repo & tooling gates (check:pm-skill-ratchet, check:pm-skill-id-lint, check:pm-governed-prose): success; Lint · PM dispatch-gates: success. Every check-run on the head is completed and none concluded failure (success or skipped, the skips being path-filtered families the diff does not reach).

Findings:

• should-fix (outside this PR's surface; the card's Wanted says 「no other change」, so not a FAIL here — file a follow-up card in the skills lane): references/dispatch-runbook.md:39 「## 巡查常设项(每项目巡查与总监席摘要)」 and :44 「跨账户复审:每项目巡查跑 is:pr is:open label:needs:contract-review…」 still name the patrol by the project. The card's dedupe grep was 「每项目一个」, which does not match 「每项目巡查」. After this PR the skill says per seat and its runbook heading says per project; two lines, 「每项目巡查」→「每席巡查」, net 0. While there, :45's dedupe 「已有他账户的认领即跳过」 is keyed to the account, so two seats of one account in one project would both pass it; worth one word on the same card.
• No must-fix. The line holds against every text it cites and the scenario it is accepted against.

Implemented-by: claude/issue-28699-patrol-per-seat
Reviewed-by: session_017ihL2g7RyXa8ErM6GAkHyc

VERDICT: PASS

domain:skills#2 · marchtian · session_017ihL2g7RyXa8ErM6GAkHyc

维护者速读(席位终稿 · head ba301e3691ab0e71abff8951b53bb3fa57052a4d)

• 改了什么:SKILL.md:72 一个词:项目席的巡查 routine 从「每项目一个」改为「每席一个」。
• 为什么改:feat(pm): a project seat's patrol is part of seating, recorded on the stub, and its absence is a half-state reading #28687 合并后,references 已写明坐一个席位就建一个巡查;SKILL.md 还写每项目一个,一个项目坐多个席位时两处自相矛盾。实际做法(本项目 spec/devx/skills 三席各一个巡查)与 references 一致。
• 风险与回滚:只改一个词,行数不变,无代码。回滚 = revert。
• 先看:.claude/skills/pm-dispatch/SKILL.md 第 72 行。
• 两分钟验证:git grep 每项目一个 -- .claude 无命中。
• 需要你做的:批准本 PR(规则变更以你的批准为裁决)。契约复审 PASS:6560664363(Head-sha: ba301e3691ab0e71abff8951b53bb3fa57052a4d)。

席位意见:ACCEPT. 与 references 四处同口径;复审提出的 runbook 同类措辞已另立 #28740。

席位核对

• 形态: 1 file, .claude/skills/pm-dispatch/SKILL.md +1/−1, 319 → 319 lines, line 72 115 bytes. skip-changeset, Clause-②: no, Metadata-protocol: none on body and claim (6560370830).
• 前提实测: origin/main fa494d0538 SKILL.md:72 read 「每项目一个」; on the head git grep 每项目一个 -- .claude has 0 hits (record 6560664363 ①).
• 门禁 check-runs on ba301e36: all completed, every non-skipped run success (record 6560664363 ④). Dev's local dispatch-gates --commands: 20/20 exit 0, --ran 0 NOT-MEASURED.
• 复审: CONTRACT_REVIEW_TIER PASS 6560664363. Execution ran on opus under the one-line-class exit named in the claim; this record is the compensating skill-face review.
• 接受的偏差: the dev's three flags, as answered in 6560664363 ③. The PR body's closing line is the 🤖 form, not the AGENTS.md session-URL footer; the session id is in the body prose. Accepted as is (the relay does not patch PR bodies).
• 范围外去向: review should-fix (dispatch-runbook.md 〈巡查常设项〉 「每项目巡查」 and the account-keyed review dedupe) → filed pm-dispatch(runbook): 〈巡查常设项〉 still names the patrol per project, and its cross-account review dedupe is keyed to the account #28740. Skills-docs: none — internal tooling.
• 落地条款: Tier S by the register, plus the card-level condition used for pm-dispatch: a project seat can sit with no hourly patrol routine and nothing notices — make the patrol a step of seat-online, record it in the seat post, and flag an on-duty lane's unclaimed pm:queue card #28642/pm-dispatch(mailbox): name when a seat MUST ring another — unblocked card, main-red anchor, release blocker, a question for triage, serial order, a relayed ruling — and close the seats with no mailbox #28675 (the maintainer's approval is the ruling for a rule change). The PR stays draft with needs-user-decision until an authorised approver acts; then the seat clears the label, flips ready and enqueues.