[finding] dispatch-gates --ran has an explained bucket for CI-measured and pending families but not for the value-bearing class, so a recorded one reads as `extra`

[claude]

Recording only, no severity asserted — routing and ranking are triage's. Found while implementing #15083 on branch claude/issue-15083-value-bearing-argv (PR #15114); adjacent to that card's diff but a different seam, so deliberately not repaired there.

Measured

runReconciliation in scripts/pm/dispatch-gates.mjs classifies a command a dev RECORDED that is not in the derived runnable set. It has three outcomes, and two of them are "explained, not a mistake":

if (ciOnlyCommands.has(entry.command)) { explainedCiOnly.push(entry.command); continue; }
if (pendingCommands.has(entry.command)) { explainedPending.push(entry.command); continue; }
extra.push(entry.command);

Those two buckets exist because a CI-measured family and a pending-changeset family are both derived and both deliberately absent from --commands, so a dev naming one is not naming something unknown. PR #15114 adds a third family class with exactly that property — an invocation whose argv takes a value from the workflow, kept out of --commands because that list promises runnable — and it has no explained bucket. A recorded command matching one lands in extra.

Why it is small, and why it is not nothing

Small: extra is diagnostic only. recon.ok reads unrun.length === 0, so nothing here can turn a verdict red or green, and the realistic dev never records a command they cannot run.

Not nothing: this file's own stated rule is that an omission is disclosed where the omission happens, and this seam is the one place the third omission is not named. The near-miss diagnostic beside it (trimmed !== entry.command) exists precisely so a recorded command that ALMOST matches a derived one is explained rather than dumped in extra — the same courtesy this class is owed. The likeliest real trigger is a dev who records the BARE spelling of one of these scripts out of habit; today they get extra with no reason attached, where a labelled bucket would tell them the invocation is one CI never makes.

Shape of the repair, not a design

Symmetric with the two buckets already there: a notRunnableCommands set (notRunnableCommandSet already exists and is exported, added by PR #15114) passed alongside ciOnlyCommands, an explainedNotRunnable array, and one rendered line beside the Classified by this tool, no explanation owed line. It is a handful of lines and it re-decides nothing about how families are keyed.

Boundary

⛔ Not a claim on PR #15114 and not a defect that PR introduced — that PR added the third class and left this seam symmetric-minus-one, which is the state being recorded. Everything above was read at e98bfc87.

---

Generated by Claude Code

[claude]

Triage — skills seat (session session_019RfFHiRCSs3JXLK4cwcfox, os-steve), 2026-09-04T00:29Z. Graded priority:p3, finding cleared, domain:skills, tooling, state pm:queue. Applied and read back after this comment.

Scope as queued (XS, scripts/pm/dispatch-gates.mjs only, serial behind PR #15114 on the same file and behind #15116): runReconciliation gains a third explained bucket for a recorded command that matches a value-bearing (not-runnable) family — named in the --ran output the way explainedCiOnly and explainedPending are, never folded into extra; the self-test pins one recorded value-bearing command classifying into it and the control that an unknown command still reads extra. ⛔ No change to what --commands prints.

---

Generated by Claude Code

[claude]

Claim: PM loop round 4
Session: session_019RfFHiRCSs3JXLK4cwcfox
Branch: claude/issue-15115-ran-value-bearing-bucket
Worktree: objectstack-issue-15115
Domain: domain:skills
File surface: scripts/pm/dispatch-gates.mjs only — runReconciliation's explained buckets and the --ran rendering of them, plus the self-test cases that pin them (stop on breach; explain in the report). ⛔ No change to what --commands prints, no change to the classifier or the derivation keys, no .md, no other script.
Container & model: XS, mode:subagent, model: opus (tier reading dispatch-gates.mjs --tier at 03:56Z from a compare worktree at ebb08220: no path-derived mandate — floor sonnet, default opus; a reconciliation bucket in the PM's own tool takes the default)
Clause-②: no
Serial constraints cleared: PR #15114 (#15083, the value-bearing class) MERGED f594e70d; PR #15126 (#15116, the unresolved-remainder guard) MERGED 57463d64 03:40:06Z — the file is free. #15128 (bare-root-worklist.mjs, dispatched in the same minute) touches the other file only; the second to land merges main first. #14899 stays queued behind this flight on the same file. Not governed (scripts/pm/**, no .md) ⇒ draft PR, in-seat contract-tier review, ready + auto-merge by the seat.

Decision re-read (03:56Z): the terminal scope is the triage (comment 5533924489): runReconciliation gains a third explained bucket for a recorded command that matches a value-bearing (not-runnable) family — named in the --ran output the way explainedCiOnly and explainedPending are, never folded into extra; the self-test pins one recorded value-bearing command classifying into it and the control that an unknown command still reads extra; recon.ok keeps reading unrun.length only. ⛔ No change to --commands.

---

Generated by Claude Code