Files
msd-core/tests/no-dead-sdk-refs.test.cjs
Tom Boucher 8442d984b9 fix(#3809): route runtime-loaded markdown through the gsd_run launcher (#3815)
* test(#3809): generalize dead-ref guard into a rule table (failing first)

The #2020 guard hardcoded `sdk/(src|dist|handlers)/` — the three dead paths
that had caused that storm. That proved those three paths were gone and said
nothing about the class, so #3809 reproduced the identical Windows find.exe
storm under a different token and the guard could not see it.

Replaces the single regex with a rule table over the same runtime-loaded
markdown surface, adds `commands/` to the scan set (previously uncovered),
and adds rule B: the runtime shim filename must never appear in command
position, because it is not a PATH command and an agent that meets it falls
back to locating the file.

Rule B's matcher is deliberately lenient — the launcher's own resolver
assignment, `node <path>/<shim>` calls, bare paths, and prose that names the
file all stay unflagged, each pinned by a negative-space row.

This commit is expected to FAIL: 50 offenders across 23 files remain in the
tree. The remediation lands next.

Refs #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(#3809): route every workflow call through the gsd_run launcher

50 places across 23 runtime-loaded workflow, agent, reference, and command
files instructed the agent to run the runtime shim by filename. That filename
is not on PATH under any name -- package.json ships gsd-core, gsd-tools,
gsd_run and gsd-mcp-server -- so the call exited 127, the file-shaped token
sent the agent looking for the file, and on Git Bash for Windows the resulting
`find /` walked the entire drive (7268 CPU-seconds in the report) until
somebody killed it by hand.

CONTEXT.md -> Runtime Launcher Module already makes gsd_run the single entry
point: "Canonical space-safe shell preamble (`gsd_run`) used by every workflow
bash block to invoke the GSD runtime CLI." These sites predate that rule --
they trace to 0e6907050 (docs(#195): migrate workflow markdown off gsd-sdk
query), which swapped one non-PATH token for another.

Two further instances of the same class surfaced during remediation and are
fixed here rather than left for later:

  - references/model-profiles.md prescribed `node <shim> effort sync` with no
    path at all; node resolves a bare filename against cwd, so it fails the
    same way.
  - references/universal-anti-patterns.md rule 25 instructed every agent to
    "use <shim>" when shelling out. That rule did not contain the defect, it
    prescribed it repo-wide.

Five "(or legacy <shim>)" parentheticals left dangling by the substitution are
removed; after the rewrite they offered the non-resolving form as an
alternative.

The guard from the previous commit now passes. Its node-prefix exemption was
tightened to require a path separator, which is what exposed model-profiles.

Fixes #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(#3809): key the guard on the CLI's whole verb roster, not observed usage

Review found the first cut of rule B repeating the very mistake it exists to
prevent. Its verb set held query, commit and effort -- the verbs that happened
to appear in the tree -- so it could not see `<shim> phase add`,
`<shim> state load`, `<shim> verify ...` or twenty-odd other real single-word
subcommands. A guard that only recognises yesterday's offenders is not a guard.

The set is now the CLI's full advertised roster, unioned from the usage banner
and HOST_COMMAND_ROUTERS (which carries verification, planning, uat, stats,
todo and windows, all absent from the banner).

Widening it immediately caught a live offender the first pass had missed:
references/planning-config.md prescribed `node <shim> worktree set-baseref`
with no path. Fixed here.

Also drops the "a hyphen or a dot means subcommand" heuristic, which was
unsound for prose -- it flagged `built-in` and `v1.2`. Detection now keys
entirely on the roster, testing the first dot-segment so that phase.add and
state.patch still match while prose does not. Both false positives are pinned
as negative-space rows.

Guard verified against the pre-fix tree at origin/next: 52 offenders across 25
files, and 0 after this branch's remediation.

Refs #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(#3809): derive the verb roster from the router; repair launcher parity

Standards review caught the guard repeating the defect it exists to prevent.
Its verb list was a hand-copied literal -- and worse, transcribed from an
INSTALLED older binary, so it was missing 22 verbs this tree actually ships
(websearch, windows, state-snapshot, context-predicates and the dispatch-*
family among them). gsd-tools.cjs already carries three hand-maintained
rosters whose drift is a named defect pinned by the parity test in
tests/commands.test.cjs; a hand-copied fourth was that same defect wearing a
guard's clothes.

The roster is now derived from HOST_COMMAND_ROUTERS + TOP_LEVEL_USAGE, lazily
and memoised, with `query` supplemented explicitly -- it dispatches through
the routing hub ahead of the host-router table, so it appears in neither
export, yet 45 of the 50 offenders used it. A parity test pins the derivation.

Two regressions this branch introduced, both caught by the remote runner:

  - runtime-launcher-parity: rewriting a comment in gsd-research-synthesizer.md
    put a `gsd_run` token at line 65 while the canonical preamble sits at 158,
    breaking "exactly ONE preamble, before the first gsd_run call". The comment
    is descriptive and needs no command token at all; it now names none.
  - The #2751 guard's PROSE_ALLOWLIST entry for that same line went stale once
    the line stopped carrying a bare mention. Pruned, exactly as that guard's
    own stale-entry test instructs.

Also corrects git-planning-commit.md, where the first pass rewrote only the
trailing "legacy" clause and left the sentence reading backwards.

Note the #2751 guard and this one are complementary, not duplicates: its regex
requires whitespace immediately after `gsd-tools`, so it cannot match the
`.cjs` form, and this one only matches the `.cjs` form.

Refs #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(#2751): extend the bare-command guard to references/ and commands/

The #2751 guard has only ever scanned agents/ and gsd-core/workflows/. Two
runtime-loaded directories were never in its scan set, and 47 bare
`gsd-tools <verb>` calls had accumulated there unseen -- the same defect that
guard exists to catch, in the rooms it never entered.

  - gsd-core/references/: 37 calls, all rewritten to gsd_run. references are
    fragments inlined into a parent that defines the launcher, which is why 21
    of the 22 files already using gsd_run carry no local preamble.
  - commands/gsd/: 10 operative calls rewritten. The remaining 10 are
    descriptive prose ("resolved inside the workflow via ...") and are
    allowlisted with reasons, bringing PROSE_ALLOWLIST to 15.

commands/ also came under launcher propagation. sync-runtime-launcher.cjs
walked only WORKFLOWS_DIR and AGENTS_DIR, so every preamble under commands/
was a hand-pasted copy nothing propagated and no test checked -- graphify.md
had accumulated five. It now walks COMMANDS_DIR too, which collapses those
five to the canonical one-per-file, and runtime-launcher-parity gains a
(B-commands) arm mirroring (B-agents) exactly so the placement stays honest.

The parity arm keys on shell blocks, so commands/gsd/workstreams.md and
config.md -- which name gsd_run only in inline backtick prose -- are exempt,
as they should be. gsd_run is itself a shipped npm bin, so those inline
instructions resolve from PATH exactly as the gsd-tools form they replace did.

skills/ is deliberately NOT added to either guard's scan set: it is generated
from commands/ and pinned by lint:generated-sync, so guarding the source
guards both, and scanning the mirror would double-report every future
offender. Regenerated here.

Refs #2751, #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* test(#3809): acknowledge the one emitted file this change grows

The emitted-attribution gate failed on the previous sha: gsd-research-synthesizer.md
grew 3 bytes (13847 -> 13850) with no acknowledgment. The substitution SHRANK the
other 19 emitted files, which is why the growth arm was not expected to fire at all.

The 3 bytes are unavoidable. Line 65 is a descriptive comment inside a fenced block;
naming any command there puts a gsd_run token ahead of the file's canonical preamble
at line 158, which runtime-launcher-parity's (B-agents) arm correctly rejects. So the
comment names no command and says where the config is actually loaded instead, which
reads longer than the token it replaced.

Acks only the path the gate reported, per the fragment rules.

Refs #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* revert(#2751): drop the commands/ half — three contracts pin it in place

The remote runner refuted the commands/ extension outright. Reverting it and
keeping the references/ conversion, which passed.

What broke, all of it caused by bringing commands/ under launcher propagation:

  - graphify.md's five per-block preambles are LOAD-BEARING, not accumulated
    drift. tests/graphify-visualization.test.cjs extracts individual Step-3
    shell chains and executes them standalone, so each fenced block needs its
    own definition of gsd_run. Collapsing them to the canonical one-per-file
    produced `bash: gsd_run: command not found`, exit 127, across four tests.
    The "define once per file" contract holds for workflows and agents because
    nothing extracts their blocks in isolation; commands/ is not like that.
  - explore.md broke "the preamble that DEFINES gsd_run must appear before the
    first USE of gsd_run anywhere in the file".
  - tests/gsd-tools-path-refs.test.cjs (#1766) ASSERTS that
    commands/gsd/workstreams.md contains the literal string
    `gsd-tools query workstream.list`. Rewriting it to gsd_run contradicts a
    test that pins the opposite, so the two guards disagree about that file by
    construction.

So commands/ is not a scan-set widening. It needs those contracts reconciled
first, and that is its own change. SCAN_DIRS keeps gsd-core/references/ and
drops commands/, the ten commands/ allowlist entries go with it (back to 5),
and the reasoning is recorded in the guard itself so the next person does not
rediscover it by burning a matrix run.

commands/gsd/import.md keeps its #3809 fix — that one is the .cjs form this
PR exists to remove, and it is untouched by any of the above.

Refs #2751, #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* revert(#3809): restore explore.md's Step 1 preamble placement

Running the launcher sync script processed workflows/ and agents/ too, not
just the commands/ directory the run was aimed at, and it MOVED
gsd-core/workflows/explore.md's preamble from Step 1 down to Step 3.

The script inserts into the first bash block that USES gsd_run. explore.md's
Step 1 block only DEFINES it, and that placement is deliberate -- the file
says so on the line above: "Placed in Step 1 rather than Step 3 so declining
the research offer cannot leave Step 5's commit call unbootstrapped."
tests/explore-command.test.cjs pins it.

explore.md carried no #3809 offender, so reverting it costs this fix nothing.
This was collateral from invoking the sync script at all, not from the
COMMANDS_DIR change, which is why the earlier commands/ revert did not catch it.

Refs #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* chore(#3809): backfill PR number into changeset fragments

pr:0 -> pr:3815 for both fragments now that the PR exists.

Refs #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(#3809): drop the hand-rolled regex escaper CodeQL flagged

CodeQL raised js/incomplete-sanitization (HIGH) on the guard's pattern build:
`SHIM.replace(/\./g, '\\.')` escapes the dot and nothing else, so it does not
escape backslashes. It blocked PR #3815.

The repo already bans this shape -- local/no-adhoc-regex-escape exists exactly
to stop hand-rolled escapers, with the canonical one in src/pattern.cts. Rather
than reach for that helper, the pattern now carries no escaping logic at all:
SHIM is a compile-time constant whose only metacharacter is the dot, so the
regex source is spelled out literally. The generated source string is
byte-identical to what the replace() produced, verified before and after --
0 offenders on this tree, 52 against origin/next, unchanged.

A drift pin asserts SHIM_PATTERN still matches SHIM exactly, and that the dot
is escaped rather than acting as a wildcard, so the two cannot separate.

Refs #3809

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: sim <sim@local>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-08-24 11:47:37 -04:00

316 lines
15 KiB
JavaScript

'use strict';
// Guard: runtime-loaded markdown must not carry a reference an AI runtime will try to
// LOCATE on the filesystem. When a runtime meets a file-shaped token it cannot resolve,
// it falls back to searching for it — and on Git Bash for Windows `find /` maps to the
// drive root, so `find.exe` traverses the whole disk (orphaned processes, handle leak,
// a pegged core until someone reaps it by hand).
//
// The guard is a RULE TABLE, deliberately, because the first version of it was not.
//
// #2020 shipped a guard hardcoded to `sdk/(src|dist|handlers)/` — the three dead paths
// that had caused the storm. That is an instance fix wearing a regression test: it
// proved those three paths were gone and said nothing about the class. Seven weeks
// later #3809 reproduced the identical storm under a different token, and the guard
// was structurally incapable of seeing it. Adding a rule here must stay a one-entry
// change, so the next recurrence is a table row rather than a third incident.
//
// Scope: the markdown a runtime actually loads and resolves references against —
// agents/, gsd-core/workflows/, gsd-core/references/, commands/. Prose mentions inside
// *.cjs sources are out of scope: nothing tries to locate those.
const { describe, test } = require('node:test');
const assert = require('node:assert/strict');
const fc = require('fast-check');
const fs = require('fs');
const path = require('path');
const ROOT = path.join(__dirname, '..');
const SCAN_DIRS = ['agents', 'gsd-core/workflows', 'gsd-core/references', 'commands'];
// ---------------------------------------------------------------------------
// Rule A (#2020) — a dead SDK file-path reference. The SDK package was retired
// by ADR-0174, so these paths never resolve and a runtime will hunt for them.
// ---------------------------------------------------------------------------
const DEAD_SDK_REF = /sdk\/(?:src|dist|handlers)\//;
// ---------------------------------------------------------------------------
// Rule B (#3809) — the runtime shim named in COMMAND position.
//
// The shim filename is not a command on any platform. package.json `bin` ships
// `gsd-core`, `gsd-tools`, `gsd_run`, `gsd-mcp-server`; the .cjs file exists only at
// <runtime-root>/gsd-core/bin/. CONTEXT.md -> Runtime Launcher Module makes `gsd_run`
// the single sanctioned entry point: "Canonical space-safe shell preamble (`gsd_run`)
// used by every workflow bash block to invoke the GSD runtime CLI."
//
// So a workflow that says `<shim> query phase.add` instructs the agent to run something
// that exits 127, after which the file-shaped token sends it looking for the file.
//
// What separates an INVOCATION from the four legitimate ways this filename appears is
// the token that follows it. Being lenient here is the entire point — the guard must
// not flag the launcher's own resolver, a real `node <path>/<shim>` call, a bare path,
// or prose that simply names the file. See the negative-space rows below, each of which
// is a form that exists in the tree today and must keep working.
// ---------------------------------------------------------------------------
// Built at runtime so this line is not itself an invocation the guard would flag.
const SHIM = ['gsd-tools', '.cjs'].join('');
// The pattern is spelled out rather than escaped from SHIM at build time. A
// `SHIM.replace(/\./g, '\\.')` here is a hand-rolled escaper: it handles the dot and
// nothing else, which CodeQL flags as js/incomplete-sanitization (it does not escape
// backslashes) and which local/no-adhoc-regex-escape bans outright — the canonical
// escaper lives in src/pattern.cts. Since SHIM is a compile-time constant whose only
// metacharacter is the dot, the honest fix is to carry no escaping logic at all.
// SHIM_PATTERN and SHIM are pinned to each other by a test below so they cannot drift.
const SHIM_PATTERN = 'gsd-tools\\.cjs';
const SHIM_RE = new RegExp(
// not preceded by a path separator, word char, or hyphen (excludes `<dir>/<shim>`)
`(?<![\\w./\\\\-])${SHIM_PATTERN}` +
// at least one space or tab, then the following token
'[ \\t]+([a-z][a-z0-9.-]*)',
'g',
);
// The verb roster is DERIVED from gsd-tools.cjs's own exports, never hand-copied.
//
// That file already carries three hand-maintained rosters — TOP_LEVEL_USAGE,
// HOST_COMMAND_ROUTERS and SKIP_ROOT_RESOLUTION — whose divergence is a named repo
// defect (DEFECT.GENERATIVE-FIX), pinned by the parity test in tests/commands.test.cjs.
// A hand-copied fourth roster here would be that same defect wearing a guard's clothes,
// and it already was: the first cut of this list was transcribed from an INSTALLED
// older binary and silently missed 22 verbs this tree ships, including `websearch`,
// `windows` and `state-snapshot`. Deriving costs one require and cannot drift.
//
// The require is lazy and memoised: tests/helpers.cjs defers its own built-lib require
// for the same reason, so an unbuilt tree fails one test with an actionable message
// instead of crashing the file before a single test() registers.
let _cliVerbs = null;
function cliVerbs() {
if (_cliVerbs) return _cliVerbs;
const { HOST_COMMAND_ROUTERS, TOP_LEVEL_USAGE } = require('../gsd-core/bin/gsd-tools.cjs');
const listed = TOP_LEVEL_USAGE.match(/Commands: ([\s\S]*?)\n\nGlobal flags:/);
assert.ok(listed, 'TOP_LEVEL_USAGE must contain a "Commands: ...\\n\\nGlobal flags:" block');
_cliVerbs = new Set([
...Object.keys(HOST_COMMAND_ROUTERS),
...listed[1].split(',').map((s) => s.trim()).filter(Boolean),
// `query` dispatches through the Command Routing Hub ahead of the host-router
// table, so it appears in neither export — yet it is the form 45 of the 50 #3809
// offenders used. Verified live in this tree: bare `query` is a usage error while
// `query state-snapshot` dispatches and returns JSON.
'query',
]);
return _cliVerbs;
}
/**
* Subcommand tokens invoked on the bare shim in one line of markdown.
* Returns [] for every legitimate form. Pure — no filesystem access.
*/
function findShimInvocations(line) {
// The canonical launcher's own single source of truth assigns the filename.
if (line.includes('_GSD_SHIM_NAME=')) return [];
const found = [];
let m;
SHIM_RE.lastIndex = 0;
while ((m = SHIM_RE.exec(line)) !== null) {
// `node <path>/<shim> <verb>` is resolvable and fine. `node <shim> <verb>` is NOT —
// node resolves a bare filename against cwd, so it fails exactly like the bare form.
// The exemption therefore requires a real path separator before the shim.
if (/\bnode[ \t]+["']?[^ \t"']*[/\\]$/.test(line.slice(0, m.index))) continue;
// A dotted subcommand is always `<family>.<verb>` and the family is itself a roster
// verb, so testing the first segment covers `phase.add` and `state.patch` without
// resorting to "contains a dot", which also matches prose like `v1.2`.
const token = m[1];
if (cliVerbs().has(token.split('.')[0])) {
found.push(token);
}
}
return found;
}
const RULES = [
{
id: '#2020',
label: 'dead SDK file reference',
remedy: 'the SDK package was retired (ADR-0174) — point at a live path',
scan: (line) => (DEAD_SDK_REF.test(line) ? ['sdk/'] : []),
},
{
id: '#3809',
label: `bare \`${SHIM}\` invocation`,
remedy: 'call the canonical launcher instead: `gsd_run <subcommand>`',
scan: findShimInvocations,
},
];
function walkMd(dir, out = []) {
let entries;
try { entries = fs.readdirSync(dir, { withFileTypes: true }); }
catch { return out; }
for (const e of entries) {
const full = path.join(dir, e.name);
if (e.isDirectory()) walkMd(full, out);
else if (e.isFile() && e.name.endsWith('.md')) out.push(full);
}
return out;
}
/** Offenders for one rule across every runtime-loaded markdown file. */
function scanTree(rule) {
const offenders = [];
for (const rel of SCAN_DIRS) {
for (const file of walkMd(path.join(ROOT, rel))) {
const lines = fs.readFileSync(file, 'utf8').split(/\r?\n/);
lines.forEach((line, i) => {
for (const hit of rule.scan(line)) {
offenders.push(`${path.relative(ROOT, file)}:${i + 1} (${hit})`);
}
});
}
}
return offenders;
}
describe('runtime-loaded markdown carries no unresolvable reference', () => {
for (const rule of RULES) {
test(`${rule.id} — no ${rule.label} in ${SCAN_DIRS.join(', ')}`, () => {
const offenders = scanTree(rule);
assert.deepEqual(
offenders,
[],
`${rule.id}: ${offenders.length} ${rule.label}(s) found. Runtimes resolve these by ` +
`filesystem search — on Git Bash for Windows that is a full-drive find.exe storm.\n` +
`Remedy: ${rule.remedy}.\n${offenders.join('\n')}`,
);
});
}
});
describe('#3809 — what counts as a bare shim invocation', () => {
// Positive space: forms that send an agent hunting for the file.
const INVOCATIONS = [
['inline code in prose', `**Delegate the phase addition to \`${SHIM} query phase.add\`:**`, 'query'],
['command substitution', `- \`ROADMAP=$(${SHIM} query roadmap.analyze)\``, 'query'],
['dotted subcommand', `\`${SHIM} query state.add-roadmap-evolution ...\``, 'query'],
['hyphenated subcommand', `Use \`${SHIM} detect-custom-files\``, 'detect-custom-files'],
['bare verb, no backticks', `# config settings can be fetched via ${SHIM} query config-get`, 'query'],
['commit verb', `via \`${SHIM} commit-to-subrepo\`. File paths are relative`, 'commit-to-subrepo'],
];
for (const [name, line, expected] of INVOCATIONS) {
test(`flags ${name}`, () => {
assert.deepEqual(findShimInvocations(line), [expected]);
});
test(`flags ${name} with a CRLF line ending`, () => {
// A trailing \r must not defeat the match — this repo has a documented
// bug class of regexes that only ever saw \n.
assert.deepEqual(findShimInvocations(`${line}\r`), [expected]);
});
}
// Negative space: every legitimate way the filename appears in the tree today.
// Each row is a real line; flagging any of them would be an over-broad fix.
const LEGITIMATE = [
['the launcher resolver assignment', `_GSD_SHIM_NAME="${SHIM}"; _GSD_RUNTIME_ROOT="\${RUNTIME_DIR:-$(pwd)}"`],
['a node-prefixed invocation', ` node <config-dir>/gsd-core/bin/${SHIM} restore-custom-files \\`],
['a quoted node-prefixed invocation', `node "$GSD_DIR/gsd-core/bin/${SHIM}" query commit`],
['a qualified path with no subcommand', ` "$PREFERRED_CONFIG_DIR/gsd-core/bin/${SHIM}" \\`],
['prose naming the file', `# Resolve ${SHIM} WITHOUT yet knowing GSD_DIR. The running workflow lives`],
['prose whose next token is an English word', `# shim-only install (${SHIM} present, \`gsd-tools\` not on PATH) the bare call exits`],
['prose with a lowercase English word after', `the ${SHIM} file lives under gsd-core/bin`],
['the filename at end of line', `authoritative tool for THIS install is ${SHIM}`],
['prose with a hyphenated English word after', `the ${SHIM} built-in helper does X`],
['prose with a version number after', `the ${SHIM} v1.2 release notes`],
];
for (const [name, line] of LEGITIMATE) {
test(`ignores ${name}`, () => {
assert.deepEqual(findShimInvocations(line), []);
});
}
// `node <shim>` with no directory is NOT exempt: node resolves a bare filename
// against cwd, so it fails exactly like the bare form (found at
// gsd-core/references/model-profiles.md:231).
// The verb roster is the whole advertised command surface, not the subset that happens
// to appear in the tree — a bare verb nobody has written yet must still be caught.
for (const verb of ['phase', 'state', 'verify', 'roadmap', 'milestone', 'worktree']) {
test(`flags the bare verb \`${verb}\`, which appears nowhere in the tree today`, () => {
assert.deepEqual(findShimInvocations(`run \`${SHIM} ${verb} list\``), [verb]);
});
}
test('flags a node-prefixed shim that carries no path', () => {
assert.deepEqual(findShimInvocations(`\`node ${SHIM} effort sync --apply\``), ['effort']);
});
// Boundary: the separator between the filename and the subcommand.
test('zero separating spaces is not an invocation (limit-1)', () => {
assert.deepEqual(findShimInvocations(`\`${SHIM}query\``), []);
});
test('exactly one separating space is an invocation (limit)', () => {
assert.deepEqual(findShimInvocations(`\`${SHIM} query\``), ['query']);
});
test('more than one separating space is still an invocation (limit+1)', () => {
assert.deepEqual(findShimInvocations(`\`${SHIM} query\``), ['query']);
assert.deepEqual(findShimInvocations(`\`${SHIM}\tquery\``), ['query']);
});
// Properties — the matcher is a parser, so pin its two directional invariants.
test('property: a path-qualified or node-prefixed shim is never flagged', () => {
fc.assert(
fc.property(
fc.constantFrom('node ', 'node "', "node '", '/', './', '../', 'gsd-core/bin/', '$DIR/'),
fc.constantFrom('query', 'commit', 'phase.add', 'audit-open', 'from-gsd2'),
(prefix, verb) => {
const line = prefix.endsWith('/')
? ` ${prefix}${SHIM} ${verb}`
: ` ${prefix}gsd-core/bin/${SHIM} ${verb}`;
assert.deepEqual(findShimInvocations(line), []);
},
),
{ numRuns: 200 },
);
});
test('property: a bare shim followed by a subcommand is always flagged', () => {
fc.assert(
fc.property(
fc.constantFrom('', '`', '$(', '- ', 'run ', '**via '),
fc.constantFrom('query', 'commit', 'phase.add', 'audit-open', 'from-gsd2', 'commit-to-subrepo'),
fc.integer({ min: 1, max: 4 }),
(prefix, verb, spaces) => {
const line = `${prefix}${SHIM}${' '.repeat(spaces)}${verb}`;
assert.deepEqual(findShimInvocations(line), [verb]);
},
),
{ numRuns: 300 },
);
});
});
describe('#3809 — the verb roster is derived, not copied', () => {
test('SHIM_PATTERN matches SHIM exactly, so the two cannot drift', () => {
assert.equal(new RegExp(`^${SHIM_PATTERN}$`).test(SHIM), true,
`SHIM_PATTERN (${SHIM_PATTERN}) no longer matches SHIM (${SHIM})`);
// And prove the pattern's dot is escaped rather than a wildcard.
assert.equal(new RegExp(`^${SHIM_PATTERN}$`).test('gsd-toolsXcjs'), false,
'the dot in SHIM_PATTERN must be escaped, not a wildcard');
});
test('covers every command gsd-tools.cjs actually dispatches', () => {
const { HOST_COMMAND_ROUTERS } = require('../gsd-core/bin/gsd-tools.cjs');
const missing = Object.keys(HOST_COMMAND_ROUTERS).filter((v) => !cliVerbs().has(v));
assert.deepEqual(missing, [], `verb(s) dispatched by gsd-tools.cjs but invisible to this guard: ${missing.join(', ')}`);
});
test('recognises verbs that no hand-copied list had', () => {
// These ship in this tree but were absent from the hand-copied first cut.
for (const verb of ['websearch', 'windows', 'state-snapshot', 'context-predicates']) {
assert.equal(cliVerbs().has(verb), true, `roster is missing ${verb}`);
}
});
});