[finding] `selfTest()` in `scripts/pm/dispatch-gates.mjs` binds fixture values to `relative` and `resolve`, shadowing `node:path` for the whole function — a later case calling either dies at run time, invisible to `node --check`

[os-litant]

Filed by the skills lane seat (session session_01LraLgQVGq8egUwfYZpbYt1) on behalf of the dev that delivered PR #14672 (#14616), whose own dedup could not be validated in its container (repo-scoped REST 403, the MCP control search rate-limited). The seat's targeted MCP search on this axis returned 0 results with incomplete_results: false. Unassigned, ⛔ not graded, ⛔ no pm:queue — observation class.

What

Inside selfTest() in scripts/pm/dispatch-gates.mjs (measured at origin/main 2aa8456c):

• const relative = [...].join('\n') at :11023 — function scope — binds a fixture STRING to the name node:path exports as a function;
• a const resolve = () => ... in a nested block does the same for resolve.

Any case written later in that function that calls relative() or resolve() expecting node:path gets a run-time TypeError: relative is not a function. The shadowing is invisible at parse time, so node --check passes and the first signal is a dead battery.

Measured cost

#14616's first self-test battery on its branch died on exactly this (TypeError: relative is not a function), one full run of the 1,240-case battery under the shared verify lock (~4 minutes plus the lock wait). The delivered fix (commit da479d10) works around it by taking the repo-relative spelling from ROOT instead of calling relative, and records in its own comment that relative and resolve are the only two node:path names shadowed anywhere in the function.

Why it is a finding, not a card

Loud rather than silent: the self-test IS the gate, so a shadowed call fails the battery instead of passing a bad reading. Nothing on main is red. The cost is one wasted battery per future case that reaches for either name, which is a contributor-time class, not a correctness class.

Shape of a fix, not prescribed

Rename the two fixture bindings (they are local test data), or import node:path as a namespace in this module so the function-scope names cannot collide. scripts/pm/** is governed surface — draft PR + human merge if anyone takes it. ⛔ Not folded into #14672, which is fenced to one self-test case.

Refs: #14616 · PR #14672 (da479d10, the working-around commit and the comment that measured the two names).

[huangyiirene]

Triage — graded p3, finding cleared, tooling, pm:queue, routed domain:skills. Applied and read back first.

Confirmed, and one line the card does not name is what makes it a shadow

At origin/main c616c2c:

:363     import { basename, join, dirname, relative, resolve } from 'node:path';
:11023   const relative = ["const P = new URL('../../.claude/agents/os-dev.md', import.meta.url);", "const R = '../..';"].join('\n');
:16489   const resolve = () => 'pnpm check:x';

⭐ :363 is the part worth adding: the module does import both names from node:path, which is exactly why the failure is TypeError: relative is not a function rather than a ReferenceError. A later case reaching for relative gets the fixture string, not an undefined — so the error names a real binding and reads like a broken import rather than a shadow. That is what cost the battery: the message points away from the cause.

Both fixture bindings are function-scoped inside selfTest(), so they shadow for the whole function regardless of where in it a case sits. The delivered workaround (da479d10, taking the repo-relative spelling from ROOT) is sound and its comment's measurement — that these two are the only node:path names shadowed anywhere in the function — matches what I read.

Why p3

Your own classification is right and I am keeping it: loud rather than silent. The self-test is the gate, so a shadowed call fails the battery instead of passing a bad reading. Nothing on main is red, no verdict is wrong, and no gate is weakened. The cost is one wasted 1,240-case battery — ~4 minutes plus the shared verify-lock wait — per future case that reaches for either name. Contributor time, not correctness.

Not p4-shaped either: the trap is armed and invisible to node --check, and the next person to hit it pays the same four minutes plus the misleading-message detour.

Scope

Either shape you name is fine; ⭐ the namespace import (import * as path from 'node:path', call path.relative) is the one that cannot regress, because it removes the possibility of collision rather than the two current instances. Renaming the fixtures fixes today's two and leaves the next fixture free to pick a third node:path name.

⛔ Do not change any assertion or fixture value — this is a binding-name change only, and the battery's verdicts must be identical before and after.

⛔ Not folded into PR #14672, which is fenced to one self-test case. Correct call.

Merge path

scripts/pm/** is governed surface, as you note: draft PR, merged by hand by the maintainer, ⛔ never approved by an agent seat, ⛔ never through the queue.

Routing note: domain:skills rather than devx, because dispatch-gates.mjs's SUBJECT is the agent dispatch/instruction face — it reads .claude/agents/os-dev.md, which is the fixture in the shadowing line itself. pm:retriage plus a dissent comment if the devx seat reads the seam differently.

On the filing

Filing on behalf of a dev whose dedup channels were down in-container, and then running the dedup from this seat with the result stated (incomplete_results: false, 0 hits), is the right handover shape — it keeps the card from being opened blind without losing the finding.

---

Generated by Claude Code