Files
msd-core/tests/run-with-timeout.test.cjs
Tom Boucher 455ad49ae3 feat(#2296): config-gated provider escalation on quota-exceeded (#2458)
* test(#2296): failing-first coverage for provider escalation on quota-exceeded

Covers the provider-escalation ladder layered onto EXEC.CLASSIFY: back-compat
(no escalation block without --failure-class), cap boundaries at
min(max_escalations, list length) at limit-1/limit/limit+1, opt-in gating,
malformed/hostile provider_escalation config, the --failure-class CLI negative
matrix, config-key registration, and a fast-check budget-limit property.

Red until the resolver, CLI flag, and manifest key land.

Refs #2296

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

* feat(#2296): config-gated provider escalation on quota-exceeded

The dynamic_routing tier ladder escalates within one provider, which does not
help when that provider is what ran out of quota. Add an opt-in provider ladder
layered on the existing EXEC.CLASSIFY seam.

- model-resolver: resolveProviderEscalation walks dynamic_routing.provider_escalation
  capped at min(max_escalations, list length), reporting from/to/attempted/exhausted.
  Invalid entries are dropped (ADR 227 shape validation). Stays a leaf module —
  the quota-class policy decision is the caller's, per the CONTEXT.md contract.
- agent-command-router: export a frozen AGENT_FAILURE_CLASSES so the new CLI
  validator cannot drift from the classifier that produces the values.
- resolve-execution: --failure-class flag; emits an escalation block ONLY when
  passed, so the existing JSON contract is byte-identical for every caller.
- config-schema.manifest: register dynamic_routing.provider_escalation.
- execute-phase step 7.1: auto-escalate, honor Retry-After, fail loudly naming
  every model tried once the ladder is spent.

Refs #2296

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

* fix(#2296): extract quota recovery to a reference fragment; regen goldens

The step 7.1a addition pushed gsd-core/workflows/execute-phase.md from 93390 to
95111 LF bytes, past the frozen ADR-857 Phase 6 ceiling (hard <93600, margin
<=93400) asserted by tests/fix-2285-claude-orchestration-wiring.test.cjs. The
base sat 10 bytes under the margin, so no inline wording would have fit.

That gate's own rationale is that optional-feature detail belongs in a fragment,
not the host loop. Moved BOTH the new provider-escalation branch and the
pre-existing manual recovery prompt into
gsd-core/references/execute-phase-quota-recovery.md, leaving step 7.1 as a
one-line pointer. execute-phase.md is now 92880 bytes — 510 SMALLER than base.

Also regenerates the fixtures that legitimately moved because three shipped
files changed (gsd-tools.cjs, config-schema.manifest.json, execute-phase.md):
golden-install-parity + install-tree for all 16 runtimes, INVENTORY.md +
INVENTORY-MANIFEST.json for the new reference, and the workflow size baseline.

Refs #2296

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

* test(#2351): make the C1 orphan-reaping test load-independent

tests/run-with-timeout.test.cjs C1 asserted the child heartbeat file exists
after a 1s group-kill window, but the child only wrote it on the first 100ms
setInterval tick. Nothing synchronized the two: on a loaded container the group
is SIGKILLed before that tick lands, the file never appears, and the assertion
fails for a reason unrelated to reaping. Observed failing on both linux-node22
and linux-node24.

The behavior actually under test is the FREEZE assertion (heartbeat stops
advancing => descendant was reaped, not orphaned). That is unaffected by
sampling once more at t=0.

Child now writes its first heartbeat synchronously at startup before arming the
interval, and the kill window widens 1s -> 3s to cover child boot under load.
Both remove the timing dependency; neither weakens what the test proves.

Refs #2296

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

* chore(#2296): backfill pr:2458 in .changeset/rapid-jays-bark.md

* chore(#2296): regenerate fixtures after rebase onto #2402

The rebase conflicted on the generated golden-install-parity fixtures and
workflow-size-baseline.json because #2402 (b6e6a22fc) regenerated the same
artifacts. Conflict resolution picked a side to unblock the rebase; a true
regeneration on the combined tree then produced further drift, confirming the
resolved content was stale and would have dropped #2402's fixture changes.

Regenerated goldens, install-tree, size baseline, and INVENTORY-MANIFEST from
the merged tree. docs/INVENTORY.md keeps BOTH new reference rows.

execute-phase.md is 92782 LF bytes with both #2402's and this PR's extractions
applied — under the frozen ceiling (hard <93600, margin <=93400).

Refs #2296

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

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-20 14:59:30 -04:00

291 lines
14 KiB
JavaScript

'use strict';
/**
* #2351 — `gsd_run run-with-timeout`: a portable, coreutils-independent
* wall-clock cap for a spawned command, plus the parity guard that keeps
* hardcoded GNU `timeout` from reappearing in workflow/agent/reference markdown.
*
* Root cause it fixes: workflow gates hardcoded `timeout <n> <cmd>`. `timeout`
* is GNU coreutils; stock macOS ships neither it nor `gtimeout`, so the call
* exited 127 ("command not found") and a passing build/test was misreported as
* a FAILURE. The verb replaces every such call with a Node-based cap that keeps
* GNU `timeout`'s exit-code contract (124 on timeout) on every platform.
*
* These are behavioral tests driven through the real CLI entrypoint
* (spawnSync of gsd-tools.cjs), never source-text assertions. The parity block
* consumes the lint module's typed findings, not grepped text.
*/
const { describe, test } = require('node:test');
const assert = require('node:assert/strict');
const { spawnSync } = require('node:child_process');
const os = require('node:os');
const path = require('node:path');
const fs = require('node:fs');
const { setTimeout: sleep } = require('node:timers/promises');
const { createTempDir, cleanup } = require('./helpers.cjs');
const ROOT = path.join(__dirname, '..');
const GSD_TOOLS = path.join(ROOT, 'gsd-core', 'bin', 'gsd-tools.cjs');
const NODE = process.execPath;
// run-with-timeout intercepts before gsd-tools' cwd/workstream resolution, so it
// needs no project fixture — run from a neutral temp dir to prove independence.
function runVerb(args, opts = {}) {
return spawnSync(NODE, [GSD_TOOLS, 'run-with-timeout', ...args], {
cwd: os.tmpdir(),
encoding: 'utf8',
timeout: 30000, // test-harness backstop; the verb's own cap is what we assert
...opts,
});
}
// A guaranteed-hanging child, cross-platform (no reliance on `sleep`).
const HANG = [NODE, '-e', 'setTimeout(() => {}, 60000)'];
// A guaranteed-fast child.
const OK = [NODE, '-e', 'process.exit(0)'];
describe('#2351 run-with-timeout — exit-code contract', () => {
test('passes a fast zero-exit command through as exit 0', () => {
const r = runVerb(['5', '--', ...OK]);
assert.equal(r.status, 0);
});
test('passes a non-zero exit code through unchanged', () => {
const r = runVerb(['5', '--', NODE, '-e', 'process.exit(7)']);
assert.equal(r.status, 7);
});
test('exits 124 when the wall-clock budget is exceeded (matches GNU timeout)', () => {
const start = Date.now();
const r = runVerb(['1', '--', ...HANG]);
assert.equal(r.status, 124, 'a timed-out command must exit 124');
// Sanity: the cap actually fired promptly, not the 30s harness backstop.
assert.ok(Date.now() - start < 15000, 'timeout should fire near the 1s budget');
});
test('exits 127 when the command is not found (matches GNU timeout)', () => {
const r = runVerb(['5', '--', 'this-command-does-not-exist-2351']);
assert.equal(r.status, 127);
});
test('runs without a timer when <seconds> is 0 — a slow child is NOT killed', () => {
// Proves 0 = no timer (not "timer fired at 0ms"): a child that outlives any
// mis-armed timer must still exit 0. A wrongly-armed 0ms timer would give 124.
const r = runVerb(['0', '--', NODE, '-e', 'setTimeout(() => process.exit(0), 1500)']);
assert.equal(r.status, 0, '<seconds> 0 must run untimed');
});
test('a budget past the 32-bit setTimeout ceiling does not spuriously time out', () => {
// secs*1000 > 2**31-1 → Node clamps setTimeout to 1ms → an immediate false 124
// unless the delay is capped. The fast child must still exit 0, with no warning.
const r = runVerb(['3000000', '--', ...OK]);
assert.equal(r.status, 0, 'oversized budget must not fire an immediate timeout');
assert.doesNotMatch(r.stderr || '', /TimeoutOverflowWarning/, 'delay must be clamped');
});
});
describe('#2351 run-with-timeout — argument handling (negative matrix)', () => {
test('missing <seconds> is a usage error (exit 2), not a crash', () => {
const r = runVerb([]);
assert.equal(r.status, 2);
assert.match(r.stderr, /missing <seconds>/);
assert.doesNotMatch(r.stderr, /at Object|at Module|\.cjs:\d+/, 'no stack trace in usage error');
});
test('non-numeric <seconds> is a usage error (exit 2)', () => {
const r = runVerb(['not-a-number', '--', ...OK]);
assert.equal(r.status, 2);
assert.match(r.stderr, /invalid <seconds>/);
});
test('blank / whitespace <seconds> is a usage error — never a silent unbounded run', () => {
for (const blank of ['', ' ']) {
const r = runVerb([blank, '--', ...OK]);
assert.equal(r.status, 2, `blank seconds ${JSON.stringify(blank)} must error, not disable the timer`);
assert.match(r.stderr, /invalid <seconds>/);
}
});
test('missing <command> is a usage error (exit 2)', () => {
const r = runVerb(['5']);
assert.equal(r.status, 2);
assert.match(r.stderr, /missing <command>/);
});
test('a trailing `s` on the duration is accepted (GNU-style unit)', () => {
const r = runVerb(['5s', '--', ...OK]);
assert.equal(r.status, 0);
});
test('the `--` separator is optional', () => {
const r = runVerb(['5', ...OK]);
assert.equal(r.status, 0);
});
test("the wrapped command's argv is opaque — gsd-tools flags are NOT consumed", (t) => {
// --raw / --cwd / --pick are gsd-tools' own global flags. They must reach the
// wrapped command verbatim, not be stripped by the dispatcher. Use a script
// FILE, not `node -e` — node parses leading --flags after -e as its OWN options
// ("bad option", exit 9); after a script path it treats them as argv.
const dir = createTempDir('rwt-argv');
t.after(() => cleanup(dir));
const script = path.join(dir, 'argcheck.js');
fs.writeFileSync(script,
'process.exit(process.argv.slice(2).join(",") === "--raw,--cwd,x,--pick,y" ? 0 : 3);');
const r = runVerb(['5', '--', NODE, script, '--raw', '--cwd', 'x', '--pick', 'y']);
assert.equal(r.status, 0, 'wrapped --raw/--cwd/--pick must be passed through untouched');
});
test('the `query` meta-prefix form is accepted', () => {
const r = spawnSync(NODE, [GSD_TOOLS, 'query', 'run-with-timeout', '5', '--', ...OK], {
cwd: os.tmpdir(), encoding: 'utf8', timeout: 30000,
});
assert.equal(r.status, 0);
});
});
describe('#2351 run-with-timeout — kill semantics (POSIX process groups)', () => {
const posix = process.platform !== 'win32';
test('a timed-out command whose descendant traps SIGTERM is still reaped — no orphan/hang (C1)', { skip: !posix }, async (t) => {
// The HIGH-severity regression: the direct child exits on SIGTERM fast, but a
// descendant that IGNORES SIGTERM survives holding the inherited stdio. The
// whole process group must be SIGKILL-reaped, or a captured/piped gate hangs
// on the orphan. A node parent spawns the trapping child in the SAME process
// group (spawn WITHOUT `detached` → the child inherits the parent's pgid,
// deterministically, on every platform). We deliberately avoid `bash … &`:
// bash job-control can move a backgrounded job into its own process group,
// which no group-kill (nor GNU `timeout`) can reach. The parent exits fast on
// SIGTERM; the child ignores it and must still be reaped.
//
// Liveness is detected by a HEARTBEAT the child rewrites every 100ms — NOT
// `kill(pid, 0)`: a SIGKILL'd orphan lingers as a zombie until reaped, and a
// container's PID 1 reaps slowly, so `kill(pid,0)` reads a dead child as
// "alive". A reaped child stops ticking; a genuine orphan keeps ticking.
//
// The child writes its FIRST heartbeat synchronously at startup, before
// arming the interval, and the kill window is 3s rather than 1s. Both are
// load-independence requirements, not cosmetics: with the first write
// deferred to the interval's initial 100ms tick inside a 1s window, a loaded
// CI container can group-kill before that tick ever lands, and the existence
// check below then fails for a reason that has nothing to do with reaping —
// the behavior under test is the FREEZE assertion further down, which is
// unaffected by writing one extra sample at t=0.
const dir = createTempDir('rwt-c1');
t.after(() => cleanup(dir));
const parentFile = path.join(dir, 'parent.js');
const hbFile = path.join(dir, 'heartbeat');
fs.writeFileSync(parentFile, [
'const cp = require("child_process");',
"const childCode = 'const fs=require(\"fs\");const hb=process.argv[1];const tick=()=>fs.writeFileSync(hb,String(Date.now()));process.on(\"SIGTERM\",()=>{});tick();setInterval(tick,100);';",
'cp.spawn(process.execPath, ["-e", childCode, process.argv[2]], { stdio: "ignore" });',
'process.on("SIGTERM", () => process.exit(0));',
'setInterval(() => {}, 1000);',
].join('\n'));
const r = runVerb(['3', '--', NODE, parentFile, hbFile], { timeout: 20000 });
assert.equal(r.status, 124, 'must report a timeout (124), not hang');
assert.ok(fs.existsSync(hbFile), 'child heartbeat should exist');
await sleep(300); // let any in-flight write settle after the SIGKILL
const first = fs.readFileSync(hbFile, 'utf8');
await sleep(600); // >> the 100ms heartbeat interval
const second = fs.readFileSync(hbFile, 'utf8');
assert.equal(second, first, 'descendant must be reaped (heartbeat frozen), not orphaned and still ticking');
});
test('a command killed by a signal exits 128+signum (bash convention)', { skip: !posix }, () => {
const r = runVerb(['10', '--', 'bash', '-c', 'kill -TERM $$']);
assert.equal(r.status, 143, 'self-SIGTERM (15) → 128+15 = 143');
});
});
describe('#2351 run-with-timeout — coreutils independence (the regression)', () => {
// The whole point: no dependency on GNU `timeout`/`gtimeout`. Prove it by
// scrubbing PATH so neither could be found, and driving the child by absolute
// path. Before #2351 the gates called `timeout …` directly and exited 127 here.
const scrubbedEnv = { ...process.env, PATH: '' };
test('a real zero-exit command passes even with an empty PATH (no coreutils)', () => {
const r = runVerb(['5', '--', ...OK], { env: scrubbedEnv });
assert.equal(r.status, 0, 'must pass (exit 0), not 127, when coreutils is absent');
});
test('a genuine timeout is still detected (exit 124) with an empty PATH', () => {
const r = runVerb(['1', '--', ...HANG], { env: scrubbedEnv });
assert.equal(r.status, 124);
});
});
describe('#2351 parity guard — no hardcoded timeout in workflow/agent/reference/command md', () => {
const { findRawTimeoutInvocations, scan, DEFAULT_ROOTS } = require('../scripts/lint-portable-timeout.cjs');
// Decoy fixtures sourced from the issue report (an author independent of the
// detector), per the fixture-provenance rule (#2371): the exact bug forms the
// guard must catch.
const BUG_FORMS = [
'timeout 300 bash -c "$BUILD_CMD" 2>&1',
'timeout "$TEST_GATE_TIMEOUT" bash -c "$TEST_CMD" 2>&1',
'timeout "$TEST_GATE_TIMEOUT" bash -c "$AUDIT_TEST_CMD" 2>&1 | tail -20',
'echo "$TASK_PROMPT" | timeout "${CROSS_AI_TIMEOUT}s" ${CROSS_AI_CMD} > out 2>err',
'timeout 120 "$FALLOW_BIN" audit --format json --quiet',
'REVIEW_OUTPUT=$(echo "$X" | timeout 120 ${REVIEW_CMD} 2>/tmp/e.log)',
'timeout 30s bash "$probe"',
'gtimeout 60 bash -c "x"',
// GNU long options / no-space short opt / arithmetic budget (review #2351 C3)
'timeout --kill-after=5 30 bash -c x',
'timeout --foreground 30 bash -c x',
'timeout --signal=KILL 30 bash -c x',
'timeout -k5 30 bash -c x',
'timeout $((60*5)) bash -c x',
'cmd && timeout 30 bash x',
];
// Forms that must NEVER be flagged: the approved verb, portable capability
// probes, config keys, the agy flag, prose, and variable names.
const CLEAN_FORMS = [
'gsd_run run-with-timeout 300 -- bash -c "$BUILD_CMD"',
'echo "$X" | gsd_run run-with-timeout "${CROSS_AI_TIMEOUT}" -- ${CROSS_AI_CMD}',
'_AGY_KILLER="$(command -v timeout 2>/dev/null || command -v gtimeout 2>/dev/null || true)"',
'"$_AGY_KILLER" 600 agy --print-timeout 540s "$@" -p "$PROMPT"',
'TEST_GATE_TIMEOUT=$(gsd_run query config-get workflow.test_gate_timeout || echo "600")',
'echo "⚠ test gate timed out after ${TEST_GATE_TIMEOUT}s"',
'# bound the build with a 5-minute timeout',
'const TIMEOUT = 300;',
// prose mentions of "timeout <n>" mid-sentence must not be flagged (review #2351 C4)
'increase the timeout 30 seconds if the runner is slow',
'# we replaced timeout 300 with the run-with-timeout verb',
'sometimeout 30 is not the timeout command',
];
for (const form of BUG_FORMS) {
test(`flags a bare timeout invocation: ${form.slice(0, 42)}…`, () => {
const findings = findRawTimeoutInvocations(form);
assert.equal(findings.length, 1, `should flag: ${form}`);
assert.equal(findings[0].line, 1);
});
}
for (const form of CLEAN_FORMS) {
test(`does not flag a portable/unrelated form: ${form.slice(0, 42)}…`, () => {
assert.deepEqual(findRawTimeoutInvocations(form), [], `should NOT flag: ${form}`);
});
}
test('multi-line input reports the correct line numbers', () => {
const text = ['clean line', 'gsd_run run-with-timeout 5 -- true', 'timeout 30 bash x'].join('\n');
const findings = findRawTimeoutInvocations(text);
assert.equal(findings.length, 1);
assert.equal(findings[0].line, 3);
});
test('every shipped workflow/agent/reference/command surface is clean (regression)', () => {
// Would have returned 10 offenders before the #2351 conversions landed.
const offenders = scan(DEFAULT_ROOTS);
assert.deepEqual(
offenders,
[],
`hardcoded timeout still present:\n${offenders.map((o) => `${o.file}:${o.line} ${o.snippet}`).join('\n')}`,
);
});
});