docs(pm-skill): Enterprise cloud-lane cards take their dispatch order from cloud/ROADMAP.md, and the director re-reads the table weekly (#31635)

<!-- claude-projects-attribution: {"github_login":"zhuangjianguo"} -->
_Requested by **Steedos** · [project
thread](https://claude.ai/code/project/chan_018ETKaNwMZCNRYD7D8Q9Ubb?thread=cmsg_018ETKaNwMZCNRYD7D8Q9UbbB7efidz8HPtTbEjf8TCaSE)_

Fixes #31574

Clause-②: no
Metadata-protocol: none

## 维护者速读

- 改了什么:企业版相关卡在云车道的派发次序改为以 `cloud/ROADMAP.md`
的档位与行序为准,席位不在单卡上另调;总监席每周复读该表,把三类不一致列给您。
- 为什么改:落实您在 cloud#3835 第 6 项的原话;该表已写明「席位按表读、不逐卡改序」,但车队规则里没有一条让它生效。
- 风险与回滚:只改两份席位规则文件各 4 行,不动代码、门禁与 workflow;回滚即还原本 PR。
- 先看:`.claude/skills/pm-dispatch/references/execution-duties.md`
新增两行(取卡全序之下);`references/lanes/director.md` 职责四新增两行。
- 两分钟验证:`pnpm check:pm-skill-ratchet && pnpm
check:pm-skill-id-lint`,预期两份文件仍在上限内(188/188、86/86)且全绿。
- 需要你做的:无,席位落地。

## What changes

- `references/execution-duties.md`: the rule lives here once, right
under the pick order (`取卡全序` / `标签序`) every execution seat reads each
fire. An Enterprise card in the cloud lane is picked in the tier and row
order of `cloud/ROADMAP.md`; a seat does not reorder on a single card; a
priority change is an edit to that table, made by or for the maintainer,
with the ruling linked; the pointer is that file's "Maintaining this
file" section. No rows are copied.
- `references/lanes/director.md` (duty four): the director re-reads the
table on the week's first sitting and lists for the maintainer a closed
card still shown as in development, an open Enterprise card missing from
the table, and a table order that disagrees with card priorities. Once
the cloud drift-check script exists, the re-read runs it. It is a
report, not a gate: no CI check, workflow or script is added.
- `seat-lifecycle.md` L57 (epic order = the roadmap table, cloud:
`cloud/ROADMAP.md`) already agrees and is left as is; it orders epics,
the new line orders cards.
- Both files sat at their line ceilings. Four lines restated elsewhere
pay for the four new ones:
- execution-duties.md, card-assignee line: survives at
`.claude/agents/os-dev.md:36,38`, `AGENTS.md:403-404`,
`references/project-forms.md:31`.
- execution-duties.md, gate-list line: survives at
`.claude/agents/os-dev.md:139,145,160,169`.
- director.md, missing-pieces line: survives at
`references/execution-duties.md:21`, `SKILL.md:201`, `AGENTS.md:289`,
`references/lanes/director.md:39`.
- director.md, seat-post liveness pointer: survives at
`references/dispatch-runbook.md:39,41`,
`references/triage-duties.md:82`.
- No line was re-wrapped; every new line is at most 120 bytes.

## Tests

No code changed. The 17 derived gates ran at `0ed89549`, all exit 0;
`dispatch-gates --ran` accounts for 17 of 17, 0 NOT MEASURED.

## Verification

<details><summary>Gate run at 0ed8954</summary>

```text
node scripts/check-closing-keyword-parity.mjs :: exit 0
node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0
node scripts/check-comment-mask-corpus.mjs :: exit 0
node scripts/pm/check-harness-current.mjs --self-test :: exit 0
pnpm --filter @objectstack/lint run check:doc-formula-expressions :: exit 0
pnpm check:agent-test-spelling :: exit 0
pnpm check:cross-package-test-inputs :: exit 0
pnpm check:doc-authoring :: exit 0
pnpm check:driver-memory-census :: exit 0
pnpm check:gitlink-declared :: exit 0
pnpm check:nul-bytes :: exit 0
pnpm check:pm-governed-merges :: exit 0
pnpm check:pm-skill-id-lint :: exit 0
pnpm check:pm-skill-ratchet :: exit 0
pnpm check:refd-timer-probe :: exit 0
pnpm check:skill-frame-sync :: exit 0
pnpm check:watch-hint-literal :: exit 0
```

</details>

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01QsR2jUgp6H6apgXDP8SsuZ

---
_Generated by [Claude
Code](https://claude.ai/code/session_01QsR2jUgp6H6apgXDP8SsuZ)_

Co-authored-by: Claude <noreply@anthropic.com>

Author: objectstack-fleet[bot]

.claude/skills/pm-dispatch/references/execution-duties.md

@@ -53,6 +53,8 @@
 - 开放 = 未派发(无 `pm:dispatched`、无 assignee);在飞的 P0/P1 不挡任何候选,只余取卡全序。
 - 取卡全序:维护者直派插队卡(出处三件)> 契约面卡(判据见 `references/lanes/spec.md`)> 标签序。
 - 标签序:`priority:p0` > `pm:blocking` > 功能点位次 > `target:` 板上项 > p1 > p2 > p3 > 无级。
+- 云车道企业版卡:取卡序 = `cloud/ROADMAP.md` 的档位与行序,⛔ 席位不在单卡上另调顺序。
+- 改序即改该表,由维护者或代其改并链裁决;改法见其「Maintaining this file」,⛔ 不抄表行。
 - `pm:blocking` 级内先按解锁扇出(从 `Blocked-by:` 反向索引现算,⛔ 扇出数不落标签)。
 - 全序每级现读/现算,零逐卡维护;无级/缺 `Path:` 轮报记分诊缺口。
 - 同级先非车队卡(作者非 `Bot` 且首行非席位签名),再 `Bug`、卡龄;⛔ 不升级、不越 p0。
@@ -68,7 +70,6 @@
 ## 认领(先认领后动工)
 
 - 归属 = session ID,⛔ 不认作者字段;`Account:` 派生自 assignee,不等即半态、持卡席下笔补正。
-- 卡 assignee 归 PM,dev 恒不写;PR 派认领账号,交棒同笔改;在飞 PR = `head:claude/` 正文点名本卡。
 - 部分落地(PR 带 `Refs #N (item k)`,⛔ 不 `Fixes`)即一笔释放:`Release:`+回 `pm:queue`+清 assignee。
 - `Release:` 行点名已落与余项;余项整落 `ui/**` 外他席树 ⇒ 点名其改标,拆分加 `pm:retriage`。
 - 派发原子对一笔 `label-write`:① `--assign` @me 加 `pm:dispatched` 摘 `pm:queue`,`--comment-file` 带②。
@@ -138,7 +139,6 @@
 - 多仓项目线程不加载仓 `settings.json` deny,此行即唯一防线;两数 = 写预算与 `mcp_calls`。
 - 清单、路径、行号在派发那一刻从树上取,⛔ 不从卡片/上次派发/记忆抄。
 - 建包单:派发令点名目录与 npm 名,dev 动笔前先测同类包先例;命名规则见 AGENTS.md 角色表。
-- 门禁清单取 `dispatch-gates --commands --repo 仓` 逐条跑,退出码先落盘,`--ran` 对账;被拒即手推。
 - 派发令里关于代码的危害断言必须有读数(点名 call site / 路径 / 迁移)。
 - 搬自任何工件(含己文)本轮未亲测计数/零命中/文件面:重测或注「未验证」点名来源。
 - PM 测不了的危害 ⇒ 写成给 dev 的问题,⛔ 不写成栅栏;人工地板栅栏关于流程,免测量。

.claude/skills/pm-dispatch/references/lanes/director.md

@@ -56,7 +56,6 @@
 - 线程有 `Ruling:`/RULED 的卡再入箱,该行逐 id 各一句变化;缺行 ⇒ 拒入,`pm:retriage` 回立卡者。
 - 一次只开一批:维护者对批 N 回字(一字即可)后,新到才合成批 N+1;续批至清零才收工。
 - 受管 PR 待人批前核五件:席位记录、速读、现 head PASS、`pr_request_reviewers` 请审、绿 head。
-- 缺件即补;⛔ 不入批、不求聊天「同意」;批准与合并恒是维护者的点击,⛔ 不代。
 - 呈报前逐卡逐仓重跑 `git grep -n -iE 'TERMS' origin/main -- AGENTS.md docs/adr packages/spec/src`。
 - 以协议为准:消费面对齐协议 ⇒ 荐对齐呈批,协议没有的能力荐删;⛔ 不自裁。
 - 协议是否正确由本席按①读协议原文与主流平台分析,有误即荐改动呈批,⛔ 不自裁。
@@ -75,7 +74,8 @@
 - 外部需求行三数现查并贴查询;非车队 = 作者 `user.type` 非 `Bot` 且正文首行非席位签名。
 - ① 窗内非车队开卡数;② 窗内关卡中非车队所开占比;③ open 无 `pm:*` 非车队卡逐张带龄。
 - 查法:①② 取 `since` 窗起全态列表,本地 `created_at`/`closed_at` 落窗才计;③ 取 open;皆排 PR。
-- 座位贴与在飞活性复查归本摘要,见 `../dispatch-runbook.md` 巡查常设项与 `../triage-duties.md`。
+- 每周首场复读 `cloud/ROADMAP.md`呈维护者:已关仍标开发中、open 企业版卡缺行、表序逆卡级。
+- 云仓表漂移检查脚本落地后复读即跑它;是呈报非门禁,⛔ 不加 CI 检查、workflow、脚本。
 - 发版板 `target:<major>` 主仓归本席;判据二元,⛔ 不做优先级渐变:不修它,RC 能不能发。
 - 判阻塞四类:① 用户今天就撞的已发布面缺陷;② 公开契约 declared≠enforced。
 - ③ 存量数据/迁移形状(发布后修不回);④ 发布说明里要为它道歉的。