[finding] dispatch-gates --ran silently discards an explicit NOT-MEASURED claim when the same command also carries a run line — and a cap-kill exit (124/143) reads as RUN

[claude]

What was measured

scripts/pm/dispatch-gates.mjs --ran has two channels for declaring a gate family unmeasured, and one silently eats the other.

All four readings taken 2026-09-13T17:45Z at origin/main 6a3bcd8174, same derivation each time (--repo objectstack-ai/objectstack packages/spec/src/system/metrics.zod.ts, 70 derived families), same single command node packages/lint/scripts/check-reference-carrier-shape.mjs. Only the record's spelling differs between runs — so these are four readings of one instrument, not four instruments.

record contents	verdict line
A <cmd> :: exit 124	70 derived, **1 run**, **0 NOT-MEASURED**, 69 UNRUN
B <cmd> :: exit 3	70 derived, 0 run, **1 NOT-MEASURED**, 69 UNRUN
C NOT-MEASURED <cmd> :: cap-killed at the container foreground ceiling	70 derived, 0 run, **1 NOT-MEASURED**, 69 UNRUN
D both the A line and the C line	70 derived, **1 run**, **0 NOT-MEASURED**, 69 UNRUN

B is the discriminating control for A — same command, same derivation, only the recorded code differs, and the classification flips. C is the control for D — the claim channel demonstrably works when it is the only line present.

The defect

D is the finding. A runner that does the most honest thing available — record the real exit code and explicitly declare the family unmeasured with a stated reason — has its declaration discarded without a word and gets a false green. The most careful record produces the least truthful total.

The cause is a short-circuit, not a missing feature. In parseRunRecord's reconciliation loop the run-line branch returns before the claim map is ever consulted:

• scripts/pm/dispatch-gates.mjs:12032 — if (ranClaims.has(command)) {
• :12045 — if (recorded.code === EXIT_PREREQUISITE_NOT_MET) — exit 3 is the only code that leaves this branch as NOT-MEASURED
• :12055 — ran.push(command) — every other recorded code, 124 / 143 / 141 included, falls through to run
• :12058 — const claim = unmeasuredClaims.get(command) — unreachable for any command that appears in ran.list

Why this is a defect and not the documented design

The module's own docblock at :11788-11799 anticipates exactly this case and argues the opposite way round:

a gate cap-killed at the container's foreground ceiling (exit 143) was written off as NOT MEASURED, and on re-running to completion it was green. So the claim parses only with a stated reason … a marked line without one leaves its family UNRUN, which is the direction that costs a rerun instead of a false green.

The stated principle is prefer the direction that costs a rerun. Reading A/D does the reverse: a family that never reached a verdict line is counted as run, which is the false-green direction the whole module exists to prevent. Whatever the right classification for a cap-kill is — UNRUN and NOT-MEASURED are both defensible — run is not one of the candidates.

Reproduction

node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack \
  packages/spec/src/system/metrics.zod.ts | head -1 > /tmp/cmd
CMD=$(cat /tmp/cmd)
{ printf '%s :: exit 124\n' "$CMD"
  printf 'NOT-MEASURED %s :: cap-killed at the foreground ceiling\n' "$CMD"; } > /tmp/both.list
node scripts/pm/dispatch-gates.mjs --ran /tmp/both.list --repo objectstack-ai/objectstack \
  packages/spec/src/system/metrics.zod.ts | grep -i reconciliation
# reads: 1 run, 0 NOT-MEASURED   — the claim line is gone with no diagnostic

How it surfaced

On PR #17635 (#15939's gate card), the round's check:pm-dispatch-gates was killed by its own timeout at 560s under the container's foreground cap and recorded exit 124. Its reconciliation read 82 derived, 81 run, 1 NOT-MEASURED, 0 UNRUN — the 1 is a different, exit-3 family, and the cap-killed one sits inside the 81 run. The round declared it in prose instead, which is why it was caught at all. ⛔ A round that trusted the tool's total would not have known.

Dedupe — checked, and these are neighbours, not duplicates

• [finding] check:pm-dispatch-gates runs 11m27s and buffers all output to the end — a foreground run is SIGTERMed at the container cap with zero diagnostic #14281 (closed) — check:pm-dispatch-gates runs 11m27s and is SIGTERMed at the container cap with zero diagnostic. That is the symptom on one gate. This card is about the reconciler's classification of any such kill, on any family.
• [finding] dispatch-gates' reconciliation line enumerates what sits OUTSIDE the runnable total and omits two blocks it printed itself — the WIDE-population block and the artifact rosters #16398 (closed) — the reconciliation line enumerates what sits OUTSIDE the runnable total and omits two blocks. Same line, different defect: that was about what the line enumerates, this is about which bucket a family lands in.
• [finding] dispatch-gates offers the bare check-partof-closing-keyword command as runnable — it takes PR_BODY through env:, not argv, so the NOT-MEASURED bucket never sees it #15761 (closed) — a command whose input arrives by env: never reaches the NOT-MEASURED bucket. Adjacent, but a derivation-side problem, not a record-side one.
• dispatch-gates --ran's headline "0 NOT-MEASURED" is the runner's claim, not a measurement — a seat whose gates exited 3 still gets a green tick #17204 is cited in the module's own docblock as the four-delivery 0 NOT-MEASURED measurement; this card is consistent with it and does not restate it.

Suggested direction — for the triaging seat, not a ruling

The failure is that two channels disagree and the loser is silent. The cheapest honest fix is the ordering the module's own principle implies: let an explicit NOT-MEASURED … :: <reason> claim win over a run line for the same command, or — if a record carrying both is considered malformed — refuse the record and say so, rather than picking one and discarding the other quietly. ⛔ Either way the fix belongs with the seat that owns this file; nothing here should be read as pre-deciding it.

_{Filed by the epic PM for #15939, session_015c5G6TmpMKgnusmTpD7Ntt, 2026-09-13T17:45Z. Surfaced by the #17635 round; re-measured and re-framed here rather than relayed — the round's own account named only the exit-3 half and did not know the claim channel existed.}

---

Generated by Claude Code

[claude]

Triage (skills-lane self-triage; session session_01DAcomhvR9kKizeYgg89Vo8, the skills seat), 2026-09-14T00:07Z: class (a) — reproducible, four readings of one instrument on the card (same command, only the record's spelling differs). Lands in scripts/pm/dispatch-gates.mjs (the --ran record parser: an explicit NOT-MEASURED claim must survive a run line on the same command, and a cap-kill exit 124/143 must read as KILLED, never RUN); domain:skills; Bug; priority:p2 — a killed run reading as RUN is a false green on the gate ledger every landing record cites. pm:queue; finding removed — 定级即离标. ⚠️ scripts/pm/dispatch-gates.mjs is a Restart-touch: trigger file of hold #14290 (patrol anchor #9857, H17 index): the dispatch order names that hold and its rider clause. Default tier.

---

Generated by Claude Code

[claude]

Release — skills seat (session session_01DAcomhvR9kKizeYgg89Vo8), 2026-09-14T01:16Z: the claim pair written at 2026-09-14T01:12Z is returned to pm:queue (assignee cleared) before any dispatch — the maintainer's word in this seat's chat at 2026-09-14T01:15Z, verbatim 「18085 优先」, takes the slot (cap 2, #18055 in flight). Readings taken for the dispatch order, kept here so the next claim does not redo them (on origin/main d438b3a9, a full worktree): the card's reading D reproduces — a record carrying BOTH <cmd> :: exit 124 and NOT-MEASURED <cmd> :: cap-killed… reconciles as 71 derived, 1 run, 0 NOT-MEASURED, 70 UNRUN; reading A (exit 124 alone) the same; reading C (the claim alone) 0 run, 1 NOT-MEASURED. The loop at :12035–:12061 still classifies every recorded code other than EXIT_PREREQUISITE_NOT_MET as run; main computes conflicts at :12022 and renders them at :12246 (self-test :23806 「claimed BOTH ways reads as run and the contradiction is reported」) — whether that contradiction line actually prints for reading D was not read (the card's own reproduction filters on reconciliation only); the cap-kill-reads-as-RUN half stands regardless. scripts/pm/dispatch-gates.mjs is hold #14290's Restart-touch: file (its Restart-when: closed #16132 has since fired — #16132 is closed — so that hold is due back in its own lane's queue; riders #12797 / #12808 are closed). Next claim: name #14290 in the order; no fold.

---

Generated by Claude Code