* fix(#3019): query --help reaches handler instead of short-circuiting to top-level usage The query argv parser in sdk/src/cli.ts harvested -h/--help as a global flag and main() short-circuited dispatch when args.help was true. Net effect: every `gsd-sdk query <anything> --help` printed top-level USAGE instead of contextual subcommand help. There was no path for users to discover what arguments a query subcommand accepts — they had to trigger "required" errors by trial and error. Two-layer fix: 1. sdk/src/cli.ts (parseCliArgsQueryPermissive) - Push -h / --help onto queryArgv instead of consuming them silently, so the registered handler / gsd-tools.cjs fallback gets to interpret the flag and render contextual help. - Only honor the global help flag when there is NO real subcommand to dispatch to (i.e. queryArgv contains only help flags). Preserves `gsd-sdk query --help` → top-level USAGE while letting `gsd-sdk query phase add --help` reach the handler. 2. get-shit-done/bin/gsd-tools.cjs - Render top-level usage on --help / -h / -? / --usage instead of erroring with "Unknown flag". The discovery hint in the usage text points users at the working method (run without args → error names required arguments) and references #3019 for tracking subcommand- level help printers. - --version remains rejected (no discovery use-case). #1818 anti-hallucination invariant preserved: the destructive command NEVER executes when --help is present. The new shape returns success:true + usage on stdout instead of the old success:false + error on stderr — both satisfy "destructive command did not run", and the new shape also restores discoverability. Tests: - sdk/src/cli.test.ts: 4 new vitest cases covering #3019 — query argv parser keeps --help with subcommand, parses -h short flag, preserves bare `query --help` top-level behavior, preserves --help position when intermixed with other query flags. - tests/bug-3019-help-passthrough.test.cjs: 5 node:test cases on the fallback — bare gsd-tools (no args) errors with usage; --help renders usage on stdout exit 0; -h same; subcommand --help renders usage; usage hint mentions discovery method (without prose substring matching — parses into typed sections). - tests/bug-1818-unknown-flags.test.cjs: rewritten to assert the new invariant ("destructive command did not run" + "usage was rendered") instead of the old shape ("--help is rejected with non-zero exit"). Each destructive test seeds a sentinel artifact (phase dir, slug output) and asserts it survives. Verification: - 47/47 vitest pass on sdk/src/cli.test.ts - 5/5 pass on tests/bug-3019-help-passthrough.test.cjs - 8/8 pass on tests/bug-1818-unknown-flags.test.cjs (rewritten) - 6763/6763 pass on full node:test suite - lint-no-source-grep clean (0 violations) Closes #3019 * fix(#3019): SDK fallback forwards plain-text help, broader usage list (CR) CodeRabbit on PR #3026 (4 findings — 1 Major outside-diff, 2 inline, 1 nitpick): 1. **Major outside-diff** — sdk/src/cli.ts:442-454. The fallback path that delegates to gsd-tools.cjs called parseCliQueryJsonOutput (JSON.parse) on stdout. Now that gsd-tools renders plain-text usage on --help, JSON.parse threw "Unexpected token 'U'". Wrapped the parse in try/catch — on parse failure, forward the plain stdout verbatim so subcommand help reaches the user. Regression test: tests/bug-3019-help-passthrough.test.cjs spawns the built SDK and asserts `gsd-sdk query phase --help` exits 0, stdout contains the gsd-tools usage, and stderr does NOT contain a JSON-parse error. 2. .changeset/help-passthrough.md:3 — `pr: TBD` → `pr: 3026`. 3. gsd-tools.cjs:346 (TOP_LEVEL_USAGE): - Removed self-referencing `#3019` link (immediately stale after this PR merges). - Expanded Commands list from 17 → all 47 dispatcher cases: agent-skills, audit-open, audit-uat, check-commit, commit, … phase, phases, roadmap, milestone, validate, progress, intel, graphify, learnings, etc. — the bulk of the surface that was previously unreachable via --help discovery. 4. Nitpick: `isUsageOutput` was duplicated in bug-1818 and bug-3019-help-passthrough tests. Moved to tests/helpers.cjs with structural-comment, removed both duplicates. Verification: 47/47 vitest pass, 14/14 regression tests pass, 6764/6764 full suite, lint clean. * test(#3019): use t.skip() instead of bare return when SDK not built (CR) CodeRabbit follow-up on PR #3026: The integration test guarded against missing sdk/dist/cli.js with a bare `return;` — node:test counts that as a passing test (0 assertions exercised, 0 failures). On a CI checkout that hasn't run the SDK build, the #3026 regression test silently green-lit and no signal ever surfaced that the integration check was skipped. Switched to `t.skip(...)` via the test context parameter so the omission shows up in the test report. The unit-level fix (sdk/src/cli.ts) is still covered by vitest, so the skip only affects the end-to-end spawn-built-SDK check. Verification: 6/6 pass when SDK is built; 5 pass + 1 skip when not.
120 lines
5.4 KiB
JavaScript
120 lines
5.4 KiB
JavaScript
/**
|
|
* Regression test for bug #1818, updated for #3019.
|
|
*
|
|
* Original #1818 invariant: gsd-tools must NOT silently ignore --help/-h
|
|
* and proceed with a destructive command — that turned AI-agent
|
|
* hallucinations into accidental data loss (e.g. `phases clear --help`
|
|
* deleting phase dirs because the flag was dropped).
|
|
*
|
|
* #3019 update: the same destructive-protection invariant still holds,
|
|
* but the response shape changed. Previously --help → non-zero error
|
|
* exit. Now --help → render top-level usage and exit 0 WITHOUT running
|
|
* the command. Both shapes satisfy the original invariant ("the
|
|
* destructive command did not execute"); the new shape also restores
|
|
* subcommand discoverability for `gsd-sdk query <subcommand> --help`.
|
|
*
|
|
* The tests therefore assert two things:
|
|
* 1. The destructive command did NOT run (anti-hallucination invariant).
|
|
* 2. The output contains the top-level usage (#3019 discoverability).
|
|
*
|
|
* --version remains rejected — it's never a valid gsd-tools flag and has
|
|
* no discovery use-case.
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
const { describe, test, beforeEach, afterEach } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const { runGsdTools, createTempProject, cleanup, isUsageOutput } = require('./helpers.cjs');
|
|
|
|
describe('unknown flag guard (bug #1818, updated for #3019)', () => {
|
|
let tmpDir;
|
|
|
|
beforeEach(() => {
|
|
tmpDir = createTempProject();
|
|
});
|
|
|
|
afterEach(() => {
|
|
cleanup(tmpDir);
|
|
});
|
|
|
|
// ── --help renders usage and does NOT run the destructive command ────────
|
|
|
|
test('phases clear --help renders usage and does NOT clear phase dirs', () => {
|
|
// Create a sentinel phase dir so we can assert it survives.
|
|
const phaseDir = path.join(tmpDir, '.planning', 'phases', 'phase-99');
|
|
fs.mkdirSync(phaseDir, { recursive: true });
|
|
fs.writeFileSync(path.join(phaseDir, 'PLAN.md'), 'sentinel');
|
|
|
|
const result = runGsdTools(['phases', 'clear', '--help'], tmpDir);
|
|
assert.strictEqual(result.success, true, 'help renders, no error exit');
|
|
assert.ok(isUsageOutput(result.output), `expected top-level usage, got: ${result.output}`);
|
|
// Anti-hallucination invariant: the destructive command did NOT run.
|
|
assert.ok(fs.existsSync(phaseDir), 'phase dir must survive — clear must not have executed');
|
|
assert.ok(fs.existsSync(path.join(phaseDir, 'PLAN.md')));
|
|
});
|
|
|
|
test('generate-slug hello --help renders usage and does NOT emit a slug', () => {
|
|
const ok = runGsdTools(['generate-slug', 'hello'], tmpDir);
|
|
assert.strictEqual(ok.success, true, 'control: generate-slug works without --help');
|
|
// The control output is just the slug; the help output is the usage.
|
|
const slugOut = ok.output;
|
|
assert.ok(slugOut && !isUsageOutput(slugOut), `control should not be usage: ${slugOut}`);
|
|
|
|
const result = runGsdTools(['generate-slug', 'hello', '--help'], tmpDir);
|
|
assert.strictEqual(result.success, true);
|
|
assert.ok(isUsageOutput(result.output), 'help renders top-level usage');
|
|
assert.notEqual(result.output, slugOut, 'help output must differ from the slug — generate-slug must not have run');
|
|
});
|
|
|
|
test('phase complete --help renders usage and does NOT mark a phase complete', () => {
|
|
const result = runGsdTools(['phase', 'complete', '--help'], tmpDir);
|
|
assert.strictEqual(result.success, true);
|
|
assert.ok(isUsageOutput(result.output));
|
|
// success:true + isUsageOutput is sufficient: if the destructive path
|
|
// had executed it would have emitted a phase-resolution error to stderr
|
|
// (success:false), not the usage to stdout (success:true).
|
|
});
|
|
|
|
test('state load --help renders usage', () => {
|
|
const result = runGsdTools(['state', 'load', '--help'], tmpDir);
|
|
assert.strictEqual(result.success, true);
|
|
assert.ok(isUsageOutput(result.output));
|
|
});
|
|
|
|
// ── -h shorthand: same shape ─────────────────────────────────────────────
|
|
|
|
test('phases clear -h renders usage and does NOT clear phase dirs', () => {
|
|
const phaseDir = path.join(tmpDir, '.planning', 'phases', 'phase-42');
|
|
fs.mkdirSync(phaseDir, { recursive: true });
|
|
const result = runGsdTools(['phases', 'clear', '-h'], tmpDir);
|
|
assert.strictEqual(result.success, true);
|
|
assert.ok(isUsageOutput(result.output));
|
|
assert.ok(fs.existsSync(phaseDir), 'phase dir must survive');
|
|
});
|
|
|
|
test('generate-slug hello -h renders usage', () => {
|
|
const result = runGsdTools(['generate-slug', 'hello', '-h'], tmpDir);
|
|
assert.strictEqual(result.success, true);
|
|
assert.ok(isUsageOutput(result.output));
|
|
});
|
|
|
|
// ── --version is still rejected — no discovery use-case ──────────────────
|
|
|
|
test('generate-slug hello --version is rejected', () => {
|
|
const result = runGsdTools(['generate-slug', 'hello', '--version'], tmpDir);
|
|
assert.strictEqual(result.success, false);
|
|
assert.match(result.error, /--version/);
|
|
});
|
|
|
|
// ── current-timestamp --help: same as the others ─────────────────────────
|
|
|
|
test('current-timestamp --help renders usage', () => {
|
|
const result = runGsdTools(['current-timestamp', '--help'], tmpDir);
|
|
assert.strictEqual(result.success, true);
|
|
assert.ok(isUsageOutput(result.output));
|
|
});
|
|
});
|