Files
msd-core/tests/workflow-guard.test.cjs
Tom Boucher 5fd5c81042 test(#3055): add the process seam so a subprocess timeout is expressible as data (#3066)
* test(#3055): add the process seam and route runGsdTools through it

Adds tests/helpers/process-seam.cjs — runNode/runGit/runHook over spawnSync,
each returning a typed discriminated union
{ outcome, exitCode, stdout, stderr, timedOut, signal, killed, code }.
Every call is timeout-bounded; there is no unbounded path.

runGsdTools becomes an adapter over the seam. Its legacy
{ success, output, error, exitCode } shape and retry-once-on-kill behaviour
are preserved byte-identically, so none of its 136 caller files change.

Outcome discrimination was corrected against probed runtime behaviour rather
than assumption: a timeout and a maxBuffer overflow are identical on both
status (null) and signal (SIGTERM), and differ only by code (ETIMEDOUT vs
ENOBUFS). Overflow is therefore classified before timeout. This fixes a live
defect — the previous isKilled() treated an overflow as a kill, retried it for
a second full 60s run, and then reported "host OOM or scheduler contention"
for a child that had merely printed too much.

Also widens the ESLint tests glob from tests/**/*.test.cjs to tests/**/*.cjs,
which brought 31 previously unlinted shared helpers under the same rules their
sibling test files already obey, and fixes the 5 violations that surfaced —
including a bare npm invocation without shell:true in
tests/helpers/emitted-runtime.cjs (DEFECT.WINDOWS-TEST-PORTABILITY), now
routed through the existing portable runNpm helper.

Refs #3051

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

* test(#3055): migrate every local spawn wrapper onto the process seam

Replaces the spawn body of all 25 local runHook/runGuard/runGate definitions
with a call to tests/helpers/process-seam.cjs. Each wrapper keeps its name,
parameter list, return shape and post-processing (JSON parse, ANSI strip, env
sanitising, field extraction) — only the spawn mechanism changes, so no test
assertion moves.

The 4 bash-driven wrappers use the seam's explicit `interpreter` option rather
than a fourth primitive; it is explicit rather than inferred from the file
extension, because guessing an interpreter from a path fails silently when a
script's name does not match its shebang.

Seven wrappers were previously unbounded and now carry an explicit timeout
sized to what each actually runs, not the seam default. Two of those seven
(gsd-write-guard, lint-docs-command-form) were absent from the issue's
inventory entirely and were found by scanning after the migration.

Adds the CONTEXT.md `### Process seam` glossary entry and a CONTRIBUTING.md
reference section covering the three primitives, the discriminated union, and
the two rules the seam enforces.

Scope disclosure recorded in the phase design notes: the issue scoped three
identifier names. A scan for local helpers that spawn AND return the spawn
result finds 113 across 82 names, 71 of them unbounded, plus 122 unbounded
direct git call sites. This change bounds 25 of those. The remaining surface
is the same defect class and is NOT closed by this PR.

Refs #3051

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

* fix(#3055): classify an externally-killed child as KILLED, not EXITED

Blocker found in this branch's own diff, independently confirmed by an
isolated reviewer.

A child killed by an external signal — a genuine bench OOM kill — makes
spawnSync return { status: null, signal: 'SIGKILL' } with NO .error field.
The seam's "no error implies EXITED" rule therefore classified it as a clean
exit, and runGsdTools returned { success: false, exitCode: 1 } without
retrying. That silently defeated the #969 kill-discrimination for precisely
the case it was built for: the old isKilled() fired on `signal != null`,
retried once, then threw a labelled resource-starvation error. A real OOM
would have been reported as an ordinary assertion failure.

Adds a fifth outcome, KILLED, for "no error but a signal is set", and makes
the adapter retry on TIMED_OUT or KILLED — reproducing the old
`killed || signal != null || code === 'ETIMEDOUT'` condition exactly.
SPAWN_FAILED still does not retry (matching the old behaviour, where signal
was null). BUFFER_OVERFLOW still does not retry, which remains a deliberate
divergence: the old code retried it because signal was SIGTERM, burning a
second 60s run on a child that had merely printed too much.

All five outcomes verified against the live runtime rather than assumed:
SIGKILL -> killed, exit 0/7 -> exited, timeout -> timed_out (ETIMEDOUT),
>1MB stdout -> buffer_overflow (ENOBUFS).

Refs #3051

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

* fix(#3055): address standards-review findings on this branch

Three findings from the standards axis of the review, all in this branch's
own diff.

The CONTEXT.md glossary entry this branch introduced was already stale on the
branch's own last commit: it enumerated a 4-member OUTCOME while the code had
5, because the KILLED fix did not update it. That is precisely the drift the
"module changes update Domain-terms" gate exists to catch, so the entry now
lists all five and explains KILLED.

api-coverage-gate-e2e compared an outcome against the raw string 'exited'
rather than OUTCOME.EXITED, the only such outlier; the enum is now imported
and used. A sweep for the other four outcome literals found no further
comparison sites.

Three call sites hand the literal bash flag '-c' to the seam's first
parameter, which the JSDoc described as an absolute script path. Rather than
add a fourth primitive, the contract is corrected to match reality: the
parameter is renamed `target` and documented as the first argv element handed
to the interpreter — normally a script path, but for an interpreter invoked
with an inline program it may be that interpreter's own flag. No behaviour
change.

Refs #3051

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

* test(#3055): assert the cross-platform timeout contract, not the macOS one

The remote runner failed on both Linux lanes (node 22 and node 24, identical)
while the same tests passed locally on macOS. Two assertions encoded a
platform-specific behaviour as a cross-platform guarantee.

When spawnSync times out, macOS preserves the child's partial stdout/stderr;
Linux discards it and returns empty strings. Verified on node v26.5.1 both
ways. The seam passes through whatever spawnSync hands it and cannot
manufacture output that was discarded, so the production code was correct —
the tests were wrong.

Both tests now assert the guarantee the seam actually makes on every
platform: outcome TIMED_OUT, timedOut true, and stdout/stderr always being
strings rather than undefined or a Buffer. The partial-content assertions are
retained behind an explicit process.platform === 'darwin' guard so the macOS
coverage is not lost, and the first test is renamed to say what it now
guarantees.

This is the failure mode the remote matrix exists to catch: local macOS
verification would have shipped it.

Refs #3051

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

* fix(#3055): classify a failed spawn as SPAWN_FAILED, not a timeout

Windows CI caught two defects the Linux matrix could not.

tests/context-predicates-query.test.cjs passes a 32K-char argv value. On
Windows that exceeds the argv limit and spawnSync fails with code
ENAMETOOLONG, signal null, status null. The seam's fallback rule — "otherwise,
status === null implies TIMED_OUT" — swallowed it, so the adapter retried a
spawn that can never succeed and then threw the resource-starvation error. The
old isKilled() returned false for that shape and returned an ordinary failure
result.

TIMED_OUT is now identified positively: code === 'ETIMEDOUT' OR signal is set.
Anything else carrying an error is SPAWN_FAILED, which covers ENAMETOOLONG,
E2BIG, EACCES and ENOENT alike. The signal clause is what keeps a platform
whose timeout errno differs classified correctly, so the greedy catch-all is no
longer needed.

The second defect is a contract regression I introduced and had claimed
otherwise. That same test asserts `typeof r.exitCode === 'number'`, and
toLegacyShape was returning null for BUFFER_OVERFLOW and SPAWN_FAILED, so the
assertion failed on type. The old code returned `err.status ?? 1` on every
non-retried failure path. The adapter now returns 1 again for both, and the
comment claiming "never coerced to exitCode:1, unlike the pre-seam helper" is
retracted: the seam keeps the richer truth (exitCode null plus a distinct
outcome), the legacy adapter keeps the old numeric contract its callers
actually depend on.

Verified on this host: a 4MB argv yields E2BIG -> SPAWN_FAILED; ENOENT ->
SPAWN_FAILED; timeout -> TIMED_OUT; >1MB stdout -> BUFFER_OVERFLOW; SIGKILL ->
KILLED; clean exit -> EXITED.

Refs #3051

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-05 01:06:39 -04:00

185 lines
7.0 KiB
JavaScript

/**
* Tests for gsd-workflow-guard.js PreToolUse hook.
*
* #2304 — Kimi tool vocabulary engages the guard: Kimi CLI registers this
* guard with matcher 'Shell|WriteFile|StrReplaceFile' and forwards its own
* tool vocabulary (tool_name 'Shell', possibly module-qualified). kimi-cli's
* Shell.Params names its field `command` (src/kimi_cli/tools/shell/
* __init__.py), same as Claude's Bash, so only the tool name needs
* normalization. Pre-fix the guard's Bash branch never matched on Kimi and
* the force-add block was silently dormant.
*/
'use strict';
process.env.GSD_TEST_MODE = '1';
const { test, describe, before, after } = require('node:test');
const assert = require('node:assert/strict');
const { execSync } = require('node:child_process');
const fs = require('node:fs');
const os = require('node:os');
const path = require('node:path');
const { runHook: runHookSeam } = require('./helpers/process-seam.cjs');
const { cleanup } = require('./helpers.cjs');
const HOOK_PATH = path.join(__dirname, '..', 'hooks', 'gsd-workflow-guard.js');
function runHook(payload, timeoutMs = 5000) {
const input = JSON.stringify(payload);
const r = runHookSeam(HOOK_PATH, [], { input, timeoutMs });
if (r.exitCode === 0) {
return { exitCode: 0, stdout: r.stdout.trim(), stderr: '' };
}
return {
exitCode: r.exitCode ?? 1,
stdout: r.stdout.trim(),
stderr: r.stderr.trim(),
};
}
describe('#2304: Kimi tool vocabulary engages the workflow guard', () => {
// A repo on a worktree-agent-* branch with the guard enabled: the one
// state where the Bash branch produces an observable block, so a dormant
// guard (silent exit 0) is distinguishable from a working one (exit 2).
let repoDir;
before(() => {
repoDir = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-workflow-guard-'));
execSync(
'git init -q -b worktree-agent-test && git config user.email t@t && git config user.name t',
{ cwd: repoDir, stdio: 'ignore' }
);
fs.mkdirSync(path.join(repoDir, '.planning'));
fs.writeFileSync(
path.join(repoDir, '.planning', 'config.json'),
JSON.stringify({ hooks: { workflow_guard: true } })
);
});
after(() => {
cleanup(repoDir);
});
test('Shell force-add on a worktree-agent branch is blocked like Bash', () => {
const r = runHook({
tool_name: 'Shell',
tool_input: { command: 'git add -f secrets.env' },
cwd: repoDir,
});
assert.equal(r.exitCode, 2, 'Kimi Shell should reach the Bash branch and block');
const output = JSON.parse(r.stdout);
assert.equal(
output.code,
'WORKTREE_AGENT_FORCE_ADD_FORBIDDEN',
'block payload should carry the force-add code'
);
assert.ok(
r.stderr.includes('must not run git add -f'),
'reason must reach stderr — that is what Kimi feeds back to the model on exit 2'
);
});
test('module-qualified kimi_cli.tools.shell:Shell is recognized', () => {
const r = runHook({
tool_name: 'kimi_cli.tools.shell:Shell',
tool_input: { command: 'git add --force secrets.env' },
cwd: repoDir,
});
assert.equal(r.exitCode, 2);
assert.equal(JSON.parse(r.stdout).code, 'WORKTREE_AGENT_FORCE_ADD_FORBIDDEN');
});
test('benign Shell command passes through', () => {
const r = runHook({
tool_name: 'Shell',
tool_input: { command: 'git status' },
cwd: repoDir,
});
assert.equal(r.exitCode, 0);
assert.equal(r.stdout, '');
});
test('Bash (Claude vocabulary) still blocks — normalization is additive', () => {
const r = runHook({
tool_name: 'Bash',
tool_input: { command: 'git add -f secrets.env' },
cwd: repoDir,
});
assert.equal(r.exitCode, 2);
assert.equal(JSON.parse(r.stdout).code, 'WORKTREE_AGENT_FORCE_ADD_FORBIDDEN');
});
test('WriteFile outside .planning/ gets the workflow advisory like Write', () => {
const r = runHook({
tool_name: 'WriteFile',
tool_input: { path: path.join(repoDir, 'src', 'app.js'), content: 'x' },
cwd: repoDir,
});
assert.equal(r.exitCode, 0);
const output = JSON.parse(r.stdout);
assert.ok(
output.hookSpecificOutput?.additionalContext?.includes('WORKFLOW ADVISORY'),
'Kimi WriteFile should reach the write branch and emit the advisory'
);
});
test('StrReplaceFile editing .planning/ passes silently', () => {
const r = runHook({
tool_name: 'StrReplaceFile',
tool_input: { path: path.join(repoDir, '.planning', 'notes.md'), edit: { old: 'a', new: 'b' } },
cwd: repoDir,
});
assert.equal(r.exitCode, 0);
assert.equal(r.stdout, '');
});
// #2547 — normalizeKimiPayload rebuilt old_string/new_string with
// `String(e.old ?? '')`. `??` guards the value, not the dereference, so a
// NULLISH entry threw a TypeError at the top of the handler, before the Bash
// branch ran. The outer `catch { process.exit(0) }` swallowed it, so a Shell
// payload carrying a spurious malformed `edit` field walked straight past the
// force-add hard block. The `edit` field is never read on the Bash path — it
// only has to be present to trigger the crash, which is what makes this
// reachable from a command that has nothing to do with editing.
//
// The boundary is nullish specifically: `('x').old` is a legal property read
// yielding undefined, so a string entry never threw. The `null entry` case is
// the regression (exits 0 against pre-fix code); the rest are controls.
describe('#2547: a spurious malformed edit field does not disarm the force-add block', () => {
for (const [label, edit] of [
['null entry (the #2547 bypass)', [null]],
// `{"toString": null}` is valid JSON whose coercion throws "Cannot
// convert object to primitive value" — the same crash-to-allow reached
// through String() rather than through the property read.
['non-coercible old (the #2547 String() bypass)', [{ old: { toString: null }, new: 'x' }]],
['non-coercible new (the #2547 String() bypass)', [{ old: 'x', new: { toString: null } }]],
['string entry (control — never threw)', ['nope']],
['bare null, not a list (control — normalizes to no edits)', null],
]) {
test(`force-add still blocks with a spurious edit field (${label})`, () => {
const r = runHook({
tool_name: 'Shell',
tool_input: { command: 'git add -f secrets.env', edit },
cwd: repoDir,
});
assert.equal(r.exitCode, 2,
`a spurious malformed edit field (${label}) must not downgrade the force-add ` +
`block to a silent allow. Got exit ${r.exitCode}. stderr: ${r.stderr}`);
assert.equal(JSON.parse(r.stdout).code, 'WORKTREE_AGENT_FORCE_ADD_FORBIDDEN');
});
}
test('benign command with a malformed edit field still passes (no over-block)', () => {
const r = runHook({
tool_name: 'Shell',
tool_input: { command: 'git status', edit: [null] },
cwd: repoDir,
});
assert.equal(r.exitCode, 0, `benign command must stay allowed. stderr: ${r.stderr}`);
assert.equal(r.stdout, '');
});
});
});