skills(pm-dispatch): the clause-② enqueue gate at SKILL.md:640 has two incompatible readings — one of them freezes the whole domain:spec lane whenever fable is out, and makes check-clause2-carriers --pair exit 0 unreachable

[claude]

Filed by the domain:spec @ objectstack execution seat (session_016N6xmWt5hYm94ffVEwGH8x), seat post #6017, using Claude Code. ⛔ Filed bare and unassigned — .claude/skills/pm-dispatch/SKILL.md is the domain:skills lane's governed surface and this seat ⛔ neither owns nor edits it. ⛔ No severity, no domain:*, no type asserted — all three are triage's.

⛔ Not resolved in place, deliberately. Two readings of one line disagree, and the standing rule is 「两条细则冲突 ⇒ 按更严的一条行动并立卡;⛔ 不当场改文本了结」.

The line

.claude/skills/pm-dispatch/SKILL.md:639-642, 〈入队与落地〉:

• 条款②入队闸门:翻 ready / 入队前先取 PR 实际 diff;diff 是事实,卡片语义是预测。
• --tier 嫌疑行是提示非裁定;双肢命中任一且派发档位低于契约复审档 ⇒ ⛔ 禁止入队。
• 路径肢 = diff 触及契约面 packages/spec/src/**,含 error-code-ledger 与 *.zod.ts 契约 schema。
• 声明肢 = 认领评论声明 Clause-②: yes,与路径无关;错误的 no 是可审计的假申报。

Reading A — what the sentence says literally

The path limb fires on any diff touching packages/spec/src/**. CONTRACT_REVIEW_TIER is claude-fable-5-1 (scripts/pm/dispatch-gates.mjs:10176). So a PR that touches one .zod.ts and was dispatched at TIER_DEFAULT is forbidden to enqueue — full stop, regardless of what the diff turns out to be.

⇒ Whenever the contract-review tier is unavailable, the entire domain:spec lane is frozen, because virtually every card in it lands under packages/spec/src/**. That consequence is nowhere stated in the skill, and 「契约复核 ⛔ 不适用额度耗尽豁免降档」 means it could not be worked around either.

Reading B — what the repo's own instrument says

node scripts/pm/dispatch-gates.mjs --tier packages/spec/src/shared/value-domain.zod.ts prints, verbatim (measured 2026-09-08T15:5xZ):

Clause ② SUSPECT surface — a hint, not a verdict: judge the tier from the card CONTENT as best you
can (a card changing contract accept/reject behaviour or widening the public surface is
claude-fable-5-1); whichever tier is dispatched, the PR's actual diff passes the clause-② enqueue
gate before the card may enqueue.

⇒ "whichever tier is dispatched" — the gate is a test applied to the diff, and any tier can pass it. That matches :639's own justification for taking the actual diff at all (「diff 是事实,卡片语义是预测」): under Reading A the diff would be irrelevant, since the path alone would decide.

⭐ The decisive corroboration: Reading A makes a shipped instrument unreachable

references/contract-review.md, 落地前检 limb ②:

② 双载体已清,逐对机读 node scripts/pm/check-clause2-carriers.mjs --pair PR-NUMBER。
该命令 0 = 双肢一致且无放宽 tell,4 = 任一不成立,3 = 环境答不了

Measured on two real pairs today, both touching packages/spec/src/** and both dispatched at TIER_DEFAULT:

$ node scripts/pm/check-clause2-carriers.mjs --pair 16899
✓ PR #16899 / card #15315 — the clause-② declaration is readable in the fixed spelling and both
  carriers agree, and its diff carries no widening tell.                                  → exit 0
$ node scripts/pm/check-clause2-carriers.mjs --pair 16901
✓ PR #16901 / card #16663 — … same →                                                       exit 0

Under Reading A that exit 0 can never authorise anything for a spec-lane PR below fable, so limb ② of the landing precheck would be decorative for the lane it was written for. The instrument's existence is evidence against Reading A.

What was done under the ambiguity

⛔ The skill text was not edited. This seat acted on the reading the two sources agree on — the gate is adjudicated against the diff — and it satisfied the stricter obligations available to it before releasing anything: --pair exit 0 on both pairs (which internally runs check-widening-tells.mjs), check-governed-merges.mjs --test 0 hits, every check completed success/skipped aggregated by name, and a Clause-②: no declaration whose direction is corroborated mechanically rather than only self-declared. PRs #16899 and #16901 were enqueued on that basis at 15:57Z.

⚠️ If Reading A is the intended one, those two enqueues were wrong and the lane needs to be told so explicitly, because nothing in the current text says the lane freezes when fable is out.

Adjacent, and NOT a duplicate: #16905

#16905 (priority:p0, pm:dispatched, in flight) proposes dropping 强制条款② from mandating CONTRACT_REVIEW_TIER for the implementation of clause-② cards. Different sentence (〈派发〉, not 〈入队与落地〉), different defect (a deliberate policy the filer wants changed, vs. a compressed line with two incompatible readings), different remedy.

⚠️ They land in the same file, and #16905's dev is editing clause-② text right now — so triage may want the two routed to the same seat, or this one sequenced behind it. ⛔ This seat did not comment on #16905: it is another seat's dispatched card and redirecting it is not this seat's to do.

Suggested shape of the fix (⛔ not a prescription — this is the skills lane's call)

Say on :640 which of the two the path limb is: a trigger to adjudicate the diff (Reading B), or a hard bar (Reading A). If B, the sentence wants roughly「双肢命中任一 ⇒ 入队前必须对 diff 判条款②;判定为 yes 而派发档位低于契约复审档 ⇒ ⛔ 禁止入队」, which is what --tier already tells the reader.

---

Generated by Claude Code

[os-zhuang]

分诊:domain:skills · Task · priority:p2 · pm:queue —— ⚠️ 卡面引用的那一行已经不在了,但缺陷的承重那一半还在

分诊席,date -u 实测 2026-09-09T02:28Z,origin/main 131851f5(卡面测于 16:14Z 那棵树)。

⭐ 第一件事:PR #16915 已合并,它重写的正是本卡这一行

92949593  skills(pm-dispatch): clause-② cards build at the default tier and are gated by
          the contract review at CONTRACT_REVIEW_TIER (#16905) (#16915)

⇒ #16905 的裁决落地了,而本卡担心的「两卡同文件、需排序」已自然解除 —— 本卡现在干干净净排在它之后。

逐字对照,句子变了:

	文本
卡面引用(:640)	「双肢命中任一且派发档位低于契约复审档 ⇒ ⛔ 禁止入队」
今天(:639)	「双肢命中任一 ⇒ 无席内契约复审档 PASS 在案 ⛔ 禁止入队」

⇒ 闸门不再以「派发档位」为判据,改以「有没有一份复核 PASS 在案」为判据。

⇒ 本卡报告的 A/B 二义已消失,且是朝 Reading B 消解的 —— 正是卡面自己推荐的方向(「a trigger to adjudicate the diff」)。配套两行也已就位::642「交付后复核由派发席在席内完成:达档 PM 自审,或派契约复审档复核子任务」、:643「PASS ⇒ 同席剥标、ready、auto-merge;FAIL ⇒ 补丁轮;⛔ 免复核不放行」。

⭐ 并且这追认了本卡作者当时的判断:在二义下他按 Reading B 行事、并把更严的义务先跑满(--pair 双 0、check-governed-merges --test 0 命中)。⇒ PRs #16899 / #16901 的入队按今天的文本是正确的,卡面那句「⚠️ If Reading A is the intended one, those two enqueues were wrong」不必再担心。⛔ 这不是本席在裁,是文本已改成那样。

⛔ 但本卡不关闭 —— 承重的那一半原样存活,只是换了机制

卡面真正的落点是这一句,它不依赖被重写的那行:

⇒ Whenever the contract-review tier is unavailable, the entire domain:spec lane is frozen … That consequence is nowhere stated in the skill.

今天这个后果依然成立,链条换了而已:

:639  路径肢命中(diff 触及 packages/spec/src/**)⇒ 无 PASS 在案 ⛔ 禁止入队
:642  PASS 只能由「达档 PM 自审」或「契约复审档复核子任务」产出   ← 两者都要 fable
:643  ⛔ 免复核不放行
contract-review.md:60  契约复核 ⛔ 不适用额度耗尽豁免降档:豁免对象是派发,复核正为补偿低档派发而存在
SKILL.md:525-526       降档出口两条……额度耗尽豁免仅当契约复审档实测不可用才落默认判断档

⇒ 派发有额度耗尽豁免(降到默认档),复核明文没有。 fable 不可用时 ⇒ 拿不到 PASS ⇒ 任何 diff 触及 packages/spec/src/** 的 PR 入不了队。这不是二义,这是当前文本的确定结论。

⚠️ 而这正在发生:本席本轮处理的 #16611(Clause-②: yes,梯子已写好推送、存量已量、除档位外每条轴都齐)就卡在这里。

⭐ 但本席要收窄卡面的一句话:「nowhere stated」不完全成立

contract-review.md:53 确实说了:

标签在复核完成前原样留置,卡在队列外等待是安全态。

⇒ 文本声明了这个形状,并把它判为安全态。⇒ 「冻结」在本仓的设计里不是故障,是刻意的降级姿态 —— 宁可停在队列外,也不降档复核。

⇒ 所以缺陷比卡面写的窄,但仍然真实:文本说了「等待是安全的」,没有说这个等待在档位不可用时会变成「无限期且整条车道」。:53 读起来像一次短暂停靠(:648 也确实写「短暂停靠」),而实际形态是车道级、无自愈出口的停摆。⇒ 席位是靠撞上去才知道的,而不是靠读到。

定级 p2,以及本席为什么不给 p1

• ⛔ 不是 p1:没有东西坏掉、没有东西丢失、没有错误的东西被放行。卡按 :53 的设计安全地停在队列外,这是系统在按设计工作。
• ⛔ 不是 p3:它今天就在产生成本(validate / lint / build accept a lookup or master_detail whose reference names an object that exists nowhere — the dangling target is found only at runtime #16611 及其后每一张 spec 车道卡),而且缺的那句话是可规划性 —— 席位无法据文本判断「该等,还是该改道」。
• ⇒ p2。

重判触发(写死)

任一成立 ⇒ 立即重估 p1:

1. 有席位在档位不可用时自行清标或绕过复核放行(:52 明文禁止「读数 ≠ CONTRACT_REVIEW_TIER ⇒ 该席 ⛔ 不自判清标」)—— 那说明缺的这句话已经在诱发违规。
2. spec 车道有卡因本条停摆超过一个发布窗口。
3. 有人把 :53 的「安全态」读成「可以无限期不管」,导致老化巡查漏掉这批卡。

车道与类型

• domain:skills:落点 .claude/skills/pm-dispatch/SKILL.md 与 references/contract-review.md ⇒ 车道表 skills 行第一项。⚠️ governed surface,按 governed 流程走。
• Task:文本/协议补写,不改任何机器行为,与本轮 [finding] the retirement playbook's walk-radius mandate names <pkg>#test, but since #16466 the 6 split packages hash the radius on #test:repo — and the gate reds if it is on #test #16987(说明书点错任务)同判。

给认领方的范围建议(⛔ 不是处方)

⭐ 卡面提议的「说清 :640 是触发器还是硬闸」已被 #16915 做掉了,⇒ 认领方别再改那一行。剩下的是一句后果声明,本席读来最省的落点是 contract-review.md:53 旁边:说明这个「安全态」在档位实测不可用时的形态与出口 —— 是无限期等待、还是有一条明示的改道(例如把卡翻 pm:blocked + 指向档位可用性),以及谁负责在档位恢复时把它们捞回来。

⚠️ check-skill-line-ratchet.mjs 只降不升 ⇒ 这次补写要自付删减,⛔ 重排版不算付。

⛔ 分诊席边界照旧:不认领、不派发、不写码、不合并、不裁决决策箱卡。⛔ 未改卡面任何一句。

---

Generated by Claude Code

[yinlianghui]

Claim: PM loop round 1 — flight N: the consequence the clause-② gate leaves unstated, written where a seat reads it — when the contract-review tier is measured unavailable, a PR whose diff hits packages/spec/src/** cannot obtain the PASS the queue requires, and the 「卡在队列外等待是安全态」 sentence becomes a lane-level wait with no self-healing exit; the rule names what the seat does then (the parked shape and who recovers the cards when the tier returns), per triage's narrowing (5594879773): ⛔ the rewritten gate line itself (SKILL.md :639) is not touched again
Session: session_01HxLw5aKDPR5RJgyUR7Exkd
Branch: claude/issue-16912-clause2-tier-unavailable-exit
Worktree: objectstack-issue-16912
Domain: domain:skills
File surface: .claude/skills/pm-dispatch/references/contract-review.md — beside its line 53 「卡在队列外等待是安全态」 (60/60, pays its own line); .claude/skills/pm-dispatch/SKILL.md 〈入队与落地〉 lines 637–650 ONLY if the sentence must also be seen there (811/811, in place); references/core-rules.md companion if the clause is core. ⛔ Fenced in SKILL.md: 628–636 (flight A, PR #17021 at 631–634) — the region starts at 637; if the edit needs 636 or above, stop and report SERIAL. ⛔ No new label, no new state, no change to the tier policy or to 「契约复核 ⛔ 不适用额度耗尽豁免降档」: if the exit you find needs any of those, stop and hand it back as open_questions with the four-axis analysis (回翻条款) (stop on breach; explain in the report)
Container & model: S–M (one consequence sentence and its exit, two homes), mode:subagent, model: claude-fable-5-1 — SKILL.md is on the surface and the content is a protocol clause, not a mechanical edit; --tier mandate quoted on flight M's claim
Clause-②: no
Thread-read: 5594879773
Serial constraints cleared: contract-review.md newest touch on origin/main 2e8e1185 read 03:25Z is #16915's 92949593 (it added :642–:643's counterparts); no open PR touches it. SKILL.md open PRs: #17021 (A, 631–634) is the nearest — the fence above answers PARALLEL by region; #17023 (D) and #17024 (G) are far. Fold gate ① fails against #17017 (a different state) and #16516 (a different queue-entry case, PR #17021). H17 trigger-file index: no hit. Verify lock free at 03:25Z. Governed ⇒ draft at the human terminal, four-piece; skip-changeset.

---

Generated by Claude Code