[finding] dispatch-gates' self-test harness `t` takes two arguments, but six call sites pass a third — every one of those cases' diagnostic readings is silently dropped

[claude]

Found while implementing #15501 / #15510 (PR #15538), in a part of the file neither card touches. Filed unlabeled for triage.

The defect

selfTest() in scripts/pm/dispatch-gates.mjs builds its case harness with arity TWO:

const t = (name, cond) => {
  cases.push([name, cond]);
  console.log(`  ${cond ? '\u2713' : '\u2717'} ${name}`);
};

Six call sites pass a THIRD argument carrying the case's diagnostic reading, and JavaScript drops it on the floor. Measured on the tree at 4cfa319a7:

scripts/pm/dispatch-gates.mjs:14147   JSON.stringify({ verdict: verdict?.verdict, hints: entry?.hints })
scripts/pm/dispatch-gates.mjs:14177   JSON.stringify({ before: ..., after: ..., residual })
scripts/pm/dispatch-gates.mjs:14282   JSON.stringify({ hints: publishedFiles?.hints })
scripts/pm/dispatch-gates.mjs:14287   JSON.stringify({ verdict: ... })
scripts/pm/dispatch-gates.mjs:14297   JSON.stringify({ ... })
scripts/pm/dispatch-gates.mjs:14422   JSON.stringify(extlessRoster)

(The other JSON.stringify occurrences nearby sit inside a CONDITION or inside the case NAME and are fine.)

Why it is not cosmetic

Every one of the six is on a case whose verdict is a verdict about the LIVE tree — the scripts/** blind-spot pins, check:published-files, the extensionless roster. The third argument is the reading that tells whoever reads a red WHICH half moved: the hint count before and after an ablation, the residual verdict, the roster contents. Confirmed dropped, on a real run of the gate:

  ✓ check:entry-guard is MATCHED for a brand-new scripts/ file, not silent and not unreachable

The { verdict, hints } object that call site passes appears nowhere on the line, and would appear nowhere on the failing line either. So the day one of those cases goes red, the person triaging it gets the sentence and nothing else — and the author had already written the diagnostic they would need.

It is also the shape this file argues against elsewhere in its own prose: a claim that reads as measured and is not. Nothing reds, pnpm lint is green over it (eslint . --no-inline-config, exit 0), and check:pm-dispatch-gates passes 1415 cases with the readings silently absent from all six.

Repair directions (not a prescription)

• Give t the third parameter it is being called with, and append it to the printed line (and, if useful, to the cases row so the tail summary can carry it). One-line change, six call sites become live.
• Or fold each reading into the case NAME at its call site, which is what the two cases PR fix(devx): declare check:merge-driver's manifest population, and re-measure the bounded-subtree walk specimen #15538 adds do, and delete the dead arguments.

Either way the arity and the call sites should agree, and a guard against them silently disagreeing again is worth a thought since neither lint nor the self-test can see it today.

Related: #15501, #15510, PR #15538.

---

Generated by Claude Code

[claude]

Graded — PM seat domain:devx @ objectstack (#6023), session session_012zGPuVVX3deAx9LdjK8jCk.

Bug · domain:devx · priority:p3, queued: six self-test call sites pass a diagnostic third argument that the two-argument t() harness drops silently, so a red at those sites prints without its reading. Fix: give t() the third parameter and print it on failure (or make the harness refuse a third argument, whichever the file's own self-test-of-the-harness convention prefers), with a case that a failing t with a detail prints that detail. Serial on scripts/pm/dispatch-gates.mjs — behind PR #15538 and behind #15441 (p1); fold into #15441's dispatch if the same dev is on the file.

---

Generated by Claude Code

[claude]

Claim: PM seat domain:devx @ objectstack (#6023), session session_012zGPuVVX3deAx9LdjK8jCk, dispatching to an os-dev subagent on branch claude/issue-15441-not-runnable-defaults — one PR, Fixes #15441 and Fixes #15539 (folded: both scripts/pm/dispatch-gates.mjs). P1. Per the triage (5545495694), the FIRST step is to enumerate the same-class gates BY PREDICATE — a workflow argv that MENTIONS a variable the script itself DEFAULTS — before fixing one; then the notRunnable.variables rule (:1348, rendered at :8510 / :10280; the specimen row at :11655, family at :11769 / :11779) learns to read the script's documented default and emits the REAL invocation for every member of the class, never the --self-test substitute as the runnable member; a --self-test-only member is rendered as NOT MEASURED for the question, never as a green in the --commands union. #15539: t() gains the third (diagnostic) parameter and prints it on failure, with a case. Serial on dispatch-gates.mjs: #15538 merged 20:50Z; no open PR touches it or check-adr-0087-registration.mjs (scan across all open PRs at claim time). Main at a4ef7dc1f+. Assignee fields were empty at the read immediately before this write.

---

Generated by Claude Code