Origin: filed by the domain:devx execution seat (#6023, session session_01Vbw3RPgdtqesx4azk9SbW8, 2026-09-06T09:15Z) from an open question raised by the #14944 Q1 B dev (PR #16271 report). Unlabelled for domain on purpose — .claude/skills/pm-dispatch/** is the domain:skills lane's per the domain table; routing is triage's.
What
.claude/skills/pm-dispatch/SKILL.md, the /pm-dispatch [args] table (line ~60 on origin/main 8adb9e84a): | batch:<n> | 同时在飞的 dev 上限 | 3 |. The maintainer's dispatch cap moved 3 → 5 on 2026-09-03 (recorded in #14944's ruling 5548762263: "The nominal cap of 5 (the 2026-09-03 ruling) is unchanged"), and the execution seats run at 5 (this seat's claims read "Live devs after this claim: N/5"). The table still says 3.
Two readings are possible and the text does not say which: (A) 3 is the per-invocation default when no batch: argument is passed and 5 is the maintainer's ceiling — then the table is right and a sentence should say the ceiling is 5; (B) the default should follow the cap — then the cell is stale and reads 5. Either way one line changes; today a reader of the table cannot tell which number a seat is expected to run at.
Executable criterion
The arg table's batch row and the cap ruling agree in one reading, stated in the row itself (default vs ceiling), on the governed skill surface (draft PR, human merge). Provenance: #14944 ruling 5548762263 and the 2026-09-03 cap decision it cites. Note the pm-dispatch skill files are at line-ratchet headroom 0 (check:pm-skill-ratchet), so the change is an in-place edit of the existing row, not a new line.
Refs #14944 · PR #16271 (the depth-hold text that sits beside the batch cap).
Generated by Claude Code
Origin: filed by the
domain:devxexecution seat (#6023, sessionsession_01Vbw3RPgdtqesx4azk9SbW8, 2026-09-06T09:15Z) from an open question raised by the #14944 Q1 B dev (PR #16271 report). Unlabelled for domain on purpose —.claude/skills/pm-dispatch/**is thedomain:skillslane's per the domain table; routing is triage's.What
.claude/skills/pm-dispatch/SKILL.md, the/pm-dispatch [args]table (line ~60 onorigin/main8adb9e84a):| batch:<n> | 同时在飞的 dev 上限 | 3 |. The maintainer's dispatch cap moved 3 → 5 on 2026-09-03 (recorded in #14944's ruling5548762263: "The nominal cap of 5 (the 2026-09-03 ruling) is unchanged"), and the execution seats run at 5 (this seat's claims read "Live devs after this claim: N/5"). The table still says 3.Two readings are possible and the text does not say which: (A)
3is the per-invocation default when nobatch:argument is passed and5is the maintainer's ceiling — then the table is right and a sentence should say the ceiling is 5; (B) the default should follow the cap — then the cell is stale and reads5. Either way one line changes; today a reader of the table cannot tell which number a seat is expected to run at.Executable criterion
The arg table's
batchrow and the cap ruling agree in one reading, stated in the row itself (default vs ceiling), on the governed skill surface (draft PR, human merge). Provenance: #14944 ruling5548762263and the 2026-09-03 cap decision it cites. Note the pm-dispatch skill files are at line-ratchet headroom 0 (check:pm-skill-ratchet), so the change is an in-place edit of the existing row, not a new line.Refs #14944 · PR #16271 (the depth-hold text that sits beside the
batchcap).Generated by Claude Code