* test(#3884): failing-first coverage for strict argv and absence-signalling --pick ADR-3473 §8.4 says failure is a value. Three families currently encode failure as success, and this commit pins each one RED before the fix lands. Measured on this tree, 2026-08-26: gsd-tools generate-slug "test" --pick nonexistent -> empty stdout, exit 0 (#3365) gsd-tools audit-open --pick nonexistent_field -> dumps the entire human-readable audit report, exit 0 gsd-tools generate-slug "Hello World" --raw --pick bogus -> prints "hello-world", another field's value, exit 0 gsd-tools query state.planned-phase 3 (positional, no --phase) -> exit 0; STATE.md's "Phase: 2 of 5 (Widget Support)" is overwritten to "Phase: null - READY TO EXECUTE" and the frontmatter gains a corrupted current_phase_name (#3358) tests/pick-flag.test.cjs:27 previously asserted the #3365 defect as the contract ("returns empty string for missing field", success === true). That assertion is replaced by the required behavior rather than deleted. The new parseNamedArgs block calls the spec-object signature that does not exist yet, so it fails today by construction. The 11 existing behavior-lock tests are left untouched here; they are corrected in the implementation commit. C1/C4 assert at the consumer's output - STATE.md's bytes - per ADR-3180 Decision 4(b). A unit assertion on the parser would have passed throughout this defect's life. Design: .gsd/phase/feat-3884-failure-is-a-value/40-design.md Test matrix: .gsd/phase/feat-3884-failure-is-a-value/50-test-matrix.md Refs #3884 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * enhance(#3884): failure is a value — strict argv, and --pick that signals absence Implements ADR-3473 §8.4. Absence, emptiness and failure stop being interchangeable ways to say "I could not answer". parseNamedArgs (src/command-arg-projection.cts) Takes a spec object with a REQUIRED `positionals: number | 'rest'` and returns the hub's Result shape instead of a bare Record. Declaring the positional arity is what makes #3358's call site unrepresentable rather than merely detectable: an unrecognized flag or a token past the declared boundary is now InvalidArgs, naming the offending token and listing the accepted flags. The legacy positional-array call shape throws a TypeError — an internal invariant violation per ADR-3473 Decision 2, so a stale hand-written .cjs call site fails loudly instead of destructuring undefined off a Result. parseNamedArgsOrExit projects a failure onto the caller's error(); it is a projection over the one parser, not a second parser. Measured before, against a STATE.md with a populated phase-2 block: query state.planned-phase 3 (positional, no --phase) -> exit 0; "Phase: 2 of 5 (Widget Support)" overwritten to "Phase: null - READY TO EXECUTE", frontmatter gains a corrupted current_phase_name After: exit 1, `unexpected positional argument "3"`, STATE.md byte-identical. The flag form is unchanged and still updates STATE.md. --pick <field> (gsd-core/bin/gsd-tools.cjs) extractField returns {found,value}, and the pick block no longer shares one catch between "output was not JSON" and "field was absent". An absent field exits 1 with pick_field_absent, naming the field and the keys that do exist; non-JSON output exits 1 with pick_output_not_json instead of dumping the command's entire output. A field that is PRESENT with value null, '', 0 or false still prints at exit 0 — that is an answer, not a failure, and it is what keeps `--pick count` printing 0 on a fresh project. Measured before: `audit-open --pick nonexistent_field` printed the whole human-readable audit report at exit 0, and `generate-slug X --raw --pick bogus` printed "hello-world" — a different field's value, confidently, at exit 0. ADR-3409 Decision 7 explicitly deferred this contract fix to #3473; this is it. The sub-issue's "returns 0 when the count is zero OR absent" wording is superseded by the ADR rule it implements: zero prints 0, absence exits non-zero. Defaulting absence to 0 would demote "could not answer" to "the answer is zero" — the hazard docs/how-to/resolve-unreachable-guard-findings.md already warns against. Guard ledger (ADR-3473 Decision 6) scripts/lint-unreachable-guard-drift.cjs Detector A is RETIRED. Its premise — that a `--pick ... || echo` arm can never fire — is now false, so the shape it forbade is the correct idiom and keeping it would forbid the fix. Detector B (glob-consuming cat/ls, a nullglob mechanism this change does not touch) is retained in full, as are the shared scanner, the escape-marker parser and the baseline. Net: -1 detector, 0 added. The file is not deleted. Call-site audit 45 prompt-layer --pick invocations, every one a plain X=$(...) assignment — none in an if test, && chain, or a pipeline whose status is consumed, and no shell block in workflows/commands/agents/references sets -e. Of the 13 (command, field) pairs the prompt layer reads, 10 are always present; the 3 sometimes-absent ones each sit behind a prior found/existence check. No ADR-3409-class "field the command never produces" remains. Design: .gsd/phase/feat-3884-failure-is-a-value/40-design.md Test matrix: .gsd/phase/feat-3884-failure-is-a-value/50-test-matrix.md Refs #3884 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3884): escape untrusted tokens in diagnostics, and cover five unpinned rows Two review findings, both fixed here rather than recorded as limits. 1. A newline in an untrusted token forged a second stderr line. Before, plain-text mode: $ gsd-tools query state.planned-phase $'foo\nError: forged second line' Error: unexpected positional argument "foo Error: forged second line" After: Error: unexpected positional argument "foo\nError: forged second line" --json-errors mode was never affected — io.error runs that payload through JSON.stringify. Plain-text mode writes 'Error: ' + message verbatim, and the three new InvalidArgs reasons plus the two new --pick diagnostics all interpolate a token that comes straight from argv. Fixed with ONE shared helper, formatDiagnosticToken (src/io.cts), applied at every interpolation site — not a copy per site. It is deliberately NOT applied inside error() itself: several callers in this tree emit intentional multi-line diagnostics, and escaping newlines there would mangle them. The available-top-level-keys list needed the same treatment for a reason the review did not anticipate: `frontmatter get <file>` reads an ARBITRARY user document and echoes that document's own keys into the diagnostic. Verified reachable — a frontmatter key containing a newline reaches the key list — so formatKeyForDiagnosticList is guarding a live path, not a hypothetical one. Ordinary keys still render plain and unquoted; a fix that merely dropped the key would also have passed a "one line" assertion, so the test pins the escaped key's presence too. 2. Five behavior-table rows were implemented but nothing pinned them: B7 a dotted path that dies partway B9 bracket syntax on a non-array B10 a negative array index, in and out of range B14 a JSON root that is not an object B17 an @file: payload over 50KB B17 is the load-bearing one. output() writes @file:<path> instead of inline JSON past 50000 characters, and --pick resolves that BEFORE parsing; with no test, a future reordering of those two steps turns every large result into a false pick_output_not_json. The fixture seeds 1200 phase directories and measures the payload at 62474 characters, asserting the spill actually happened rather than assuming it. Refs #3884 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3884): correct the strict-argv surface against a full verification run The first full run came back with 90 failures across 12 files, none in the new tests. They were the argv surface telling me what it actually is. Ten root causes; each classified before anything was changed. I over-implemented, and that is reverted. ADR-3473 §8.4 says parseNamedArgs rejects "unrecognized and positional tokens". It says nothing about a value flag whose value is missing. Making that an error was my design decision, not the rule, and it broke a deliberately recorded contract: `--prd` with no value resolving to null (tests/init.test.cjs emptyPrdValueIsFalsyAndTreatedAsAbsent, row B5; tests/section-manifest-init-facts.test.cjs "flag-shaped value"). The "requires a value" branch is deleted outright rather than kept behind an option — an unused strictness mode is speculative generality. Unknown-flag and unexpected-positional rejection, which is what §8.4 actually mandates, is unchanged. --wave needed a third flag kind the original design did not anticipate. `--wave N` is documented (commands/gsd/execute-phase.md:4,48) and the shipped workflow reconstructs and passes it (execute-phase.md:84), while #2932 records token-PRESENCE semantics: the CLI cares only that the flag appeared, and the value belongs to the workflow layer. That is neither a boolean flag nor a value flag, so `optionalValueFlags` now exists — presence-only in `data`, and the validation cursor consumes a following non-flag token so it is not reported as a stray positional. Every other declared boolean flag was checked against every argument-hint and prose usage in commands/, workflows/, agents/ and docs/; `--wave` is the only one of this shape. Five tests were pinning forms that never worked. tests/adr857-core-without-capabilities.test.cjs passed `init plan-phase --phase 01-stub`, but the documented form is positional (docs/CLI-TOOLS.md:776) and the handler reads args[2] — which for that form is the literal string "--phase". Measured on the pre-fix build against a real .planning/phases/01-stub/ directory: init plan-phase 01-stub -> phase_found=true init plan-phase --phase 01-stub -> phase_found=false The test asserted only exit 0 and key presence, so it had been green while proving nothing about phase resolution. Corrected to the documented form and strengthened to assert phase_found === true. Same class in state.test.cjs (`--plan-count`, a flag that does not exist; the real one is `--plans`), milestone-archive.test.cjs (`init new-milestone --json`, silently ignored), and concurrency-safety.test.cjs (a bare positional field name whose OR-assertion passed because a whole-document dump happens to contain the substring it looked for). Six handlers had no argv validation at all — the same #3358 shape this phase exists to close, found while fixing the rest: init verify-work / phase-op / review / todos / remove-workspace read args[2] with nothing checking the rest, and validate health read --repair/--backfill through a bare args.includes() scan that bypassed the parser entirely. All now go through the seam, so the flag has one owner. tests/init-debug.test.cjs rows C4/C5 asserted that an unrecognized flag must NOT fail. That is the behavior §8.4 removes, and Decision 8 says a caller's local expectation does not override §8, so they are inverted and renamed — a test still called "ignores an unrecognized flag" while asserting rejection would be its own defect. Row C6's point is its PWNED canary; that assertion is kept verbatim and only its exit-status expectation changed, because the hostile token is now rejected rather than absorbed. The blast-radius estimate in 40-design.md is corrected rather than quietly left wrong. get_impact reported MEDIUM / 8 symbols upstream, and that was accurate for what the graph can see — parseNamedArgs's callers. It cannot see that those callers' handlers accept argv shapes wider than the code reading args[2] suggests, which is where the real surface was. Refs #3884 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3884): withdraw the validate-health tightening, finish the A2/A3 revert Second full run: 46 failures, down from 90. Four causes, two of them mine. Reverted `validate health` entirely — it was scope creep, and it broke a real flag. ~30 of the 46 read `unknown flag "--json"; accepted: --repair, --backfill`. The previous commit routed `validate health` through the parser on the reasoning that a flag should have one owner. That was wrong twice over: §8.4 names parseNamedArgs and count queries, and `validate health` was never a parseNamedArgs call site — it read its flags, just not through the parser, so it had no silent-drop defect to fix. Tightening it omitted `--json`, which the health-diagnostic suites use heavily. The handler is now byte-for-behaviour back to its pre-branch form. `validate context` stays converted: it genuinely was a call site, and its `--json` is now declared rather than read by a second `args.includes` scan. The five handlers that had NO validation at all — init verify-work / phase-op / review / todos / remove-workspace — stay fixed. Those read args[2] with nothing checking the rest, which is the #3358 shape this phase owns. Finished the A2/A3 revert. Three tests still encoded the deleted "a value flag with a missing value is an error" rule, including one added by the previous commit for that rule. All three now assert the reverted null contract, and the ones whose titles said "rejected" are renamed — a test named for a contract it no longer asserts is its own defect. `--wave=` and `--wave --weird` are correctly rejected. Neither is documented in commands/gsd/execute-phase.md, gsd-core/workflows/execute-phase.md or docs/, and neither is emitted by the shipped prompt layer, so both are unrecognized tokens that §8.4 mandates rejecting. `doesNotConsumeFollowingFlagAsWaveValue` keeps the property it exists for — asserted directly now, at the parser, that `--wave` does not swallow a following flag as its value — and only its exit-status expectation changed. A contradiction inside this branch, surfaced by the audit and resolved the safe way. Two pre-existing #3573 tests call `state begin-phase '2'` and `state planned-phase '2'` with a bare positional, relying on the old permissive parser to ignore it. This branch's own #3358 regression test requires that exact argv to be REJECTED. The two are mutually exclusive. Widening the router to accept a bare positional — mirroring complete-phase — would have silently re-opened #3358, and was verified to do exactly that: with the widened router, `query state.planned-phase 3` returned exit 0 and wrote current_phase_name again. It is reverted. docs/CLI-TOOLS.md:116 and docs/COMMANDS.md:2192 document only the `--phase N` form for both verbs, so the two #3573 tests move to it. Their assertions were never about the call shape — only that total_phases survives the resync — and both still pass. complete-phase is untouched: its bare positional IS documented, and it keeps the dynamic boundary and the negative-space note that record why. The audit that produced this is in the PR body: for every handler whose declaration changed, the flags it reads anywhere in its body, the flags the shipped surface documents, and the shapes the suite passes, compared. The `--json` miss was a pattern, not an accident — declaring a handler's flags from its parseNamedArgs call alone misses whatever it reads elsewhere. Refs #3884 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(#3884): backfill the changeset PR number Refs #3884 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
321 lines
17 KiB
JavaScript
321 lines
17 KiB
JavaScript
'use strict';
|
|
|
|
/**
|
|
* Prod-shape integration tests for `src/init.cts`'s `buildSectionManifestField`
|
|
* seam (compiled into `gsd-core/bin/lib/init.cjs`) — #2994 (epic #1671 Phase
|
|
* 6.3), `.gsd/phase/chore-2994-fragment-model-workflows/50-test-matrix.md`
|
|
* sections B (compound-fact folding), D (flag value shapes), and E (the
|
|
* `null` vs `[]` distinction).
|
|
*
|
|
* Every test drives the REAL CLI (`runGsdTools`, spawns `gsd-tools.cjs`) —
|
|
* never a direct `require()` of `cmdInit*`, since `buildSectionManifestField`
|
|
* itself is not exported and the whole point of this suite is proving the
|
|
* flag/config plumbing that only exists at the CLI seam (`init-command-router.cjs`'s
|
|
* `parseNamedArgs` calls) actually reaches `section_manifest`.
|
|
*
|
|
* Group E uses the `GSD_SECTION_MANIFEST` env override
|
|
* (`gsd-core/bin/lib/init.cjs`'s `_sectionManifestCandidatePath`) to point the
|
|
* CLI at a temp fixture manifest instead of the shipped
|
|
* `gsd-core/workflows/section-manifest.json` — this is the ONLY way to
|
|
* exercise "workflow absent from the manifest" today, because every
|
|
* `cmdInit*` this repo currently wires (#2994's own completion) already has
|
|
* an explicit key in the shipped artifact; Groups B and D deliberately do NOT
|
|
* override it, driving the shipped manifest directly per the matrix's own
|
|
* "drive from the shipped artifact wherever possible" rule.
|
|
*/
|
|
|
|
const { describe, test, beforeEach, afterEach } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
|
|
const { runGsdTools, cleanup, createTempDir, createTempProject } = require('./helpers.cjs');
|
|
const { seedPhase } = require('./fixtures/index.cjs');
|
|
|
|
function writeConfig(tmpDir, config) {
|
|
fs.mkdirSync(path.join(tmpDir, '.planning'), { recursive: true });
|
|
fs.writeFileSync(path.join(tmpDir, '.planning', 'config.json'), JSON.stringify(config, null, 2));
|
|
}
|
|
|
|
function runInitJson(argv, cwd, env = {}) {
|
|
const result = runGsdTools(argv, cwd, env);
|
|
assert.ok(result.success, `Command failed: ${result.error}`);
|
|
return JSON.parse(result.output);
|
|
}
|
|
|
|
// ─── Group E: the null vs [] distinction (matrix rows E1/E2/E3/E5/E6) ──────
|
|
|
|
describe('section_manifest: null (degraded) vs [] (computed, nothing applicable) — matrix §E', () => {
|
|
let tmpDir;
|
|
let manifestDir;
|
|
|
|
beforeEach(() => {
|
|
tmpDir = createTempProject('section-manifest-e-');
|
|
manifestDir = createTempDir('section-manifest-e-manifest-');
|
|
});
|
|
|
|
afterEach(() => {
|
|
cleanup(tmpDir);
|
|
cleanup(manifestDir);
|
|
});
|
|
|
|
test('a manifest with no "quick" key degrades section_manifest to null (row E1)', () => {
|
|
const manifestPath = path.join(manifestDir, 'manifest.json');
|
|
fs.writeFileSync(manifestPath, JSON.stringify({ workflows: {} }));
|
|
|
|
const output = runInitJson(['init', 'quick', 'desc'], tmpDir, { GSD_SECTION_MANIFEST: manifestPath });
|
|
assert.equal(output.section_manifest, null, 'an absent workflow key must degrade to null, never []');
|
|
});
|
|
|
|
test('a manifest with an explicit empty "quick" section list yields a computed [] (row E2)', () => {
|
|
const manifestPath = path.join(manifestDir, 'manifest.json');
|
|
fs.writeFileSync(manifestPath, JSON.stringify({ workflows: { quick: [] } }));
|
|
|
|
const output = runInitJson(['init', 'quick', 'desc'], tmpDir, { GSD_SECTION_MANIFEST: manifestPath });
|
|
assert.notEqual(output.section_manifest, null, 'a present (even empty) workflow key must NOT degrade to null');
|
|
assert.deepEqual(output.section_manifest.included, []);
|
|
assert.deepEqual(output.section_manifest.excluded, []);
|
|
assert.deepEqual(output.section_manifest.read, []);
|
|
});
|
|
|
|
test('null and the computed [] shape are DIFFERENT values, not interchangeable (row E3)', () => {
|
|
const absentKeyManifest = path.join(manifestDir, 'absent.json');
|
|
fs.writeFileSync(absentKeyManifest, JSON.stringify({ workflows: {} }));
|
|
const emptyListManifest = path.join(manifestDir, 'empty.json');
|
|
fs.writeFileSync(emptyListManifest, JSON.stringify({ workflows: { quick: [] } }));
|
|
|
|
const degraded = runInitJson(['init', 'quick', 'desc'], tmpDir, { GSD_SECTION_MANIFEST: absentKeyManifest });
|
|
const computed = runInitJson(['init', 'quick', 'desc'], tmpDir, { GSD_SECTION_MANIFEST: emptyListManifest });
|
|
|
|
assert.equal(degraded.section_manifest, null);
|
|
assert.notEqual(computed.section_manifest, null);
|
|
assert.notDeepEqual(degraded.section_manifest, computed.section_manifest, 'null must never compare equal to the computed {included:[],excluded:[],...} shape');
|
|
});
|
|
|
|
test('a section list where every when= evaluates false is still the computed [] shape, not null (row E2, second case)', () => {
|
|
// "Applicable" is a FACTS question, not a shape question: a real section
|
|
// whose gating flag was simply never passed on this invocation must still
|
|
// be the computed {included:[],...} object, never collapse to null.
|
|
const manifestPath = path.join(manifestDir, 'manifest.json');
|
|
fs.writeFileSync(manifestPath, JSON.stringify({
|
|
workflows: {
|
|
quick: [{ id: 'discussion-phase', when: 'flag:--discuss', read: 'gsd-core/workflows/quick/steps/discussion-phase.md' }],
|
|
},
|
|
}));
|
|
|
|
const output = runInitJson(['init', 'quick', 'desc'], tmpDir, { GSD_SECTION_MANIFEST: manifestPath });
|
|
assert.notEqual(output.section_manifest, null);
|
|
assert.deepEqual(output.section_manifest.included, []);
|
|
assert.deepEqual(output.section_manifest.excluded, ['discussion-phase']);
|
|
});
|
|
|
|
test('a missing manifest file degrades to null without throwing (row E5)', () => {
|
|
const neverCreatedPath = path.join(manifestDir, 'does-not-exist.json');
|
|
assert.equal(fs.existsSync(neverCreatedPath), false, 'sanity: file must not exist');
|
|
|
|
const result = runGsdTools(['init', 'quick', 'desc'], tmpDir, { GSD_SECTION_MANIFEST: neverCreatedPath });
|
|
assert.ok(result.success, `a missing manifest file must not crash the command: ${result.error}`);
|
|
const output = JSON.parse(result.output);
|
|
assert.equal(output.section_manifest, null);
|
|
});
|
|
|
|
test('a malformed-JSON manifest file degrades to null without throwing (row E6)', () => {
|
|
const manifestPath = path.join(manifestDir, 'malformed.json');
|
|
fs.writeFileSync(manifestPath, '{ this is not valid JSON');
|
|
|
|
const result = runGsdTools(['init', 'quick', 'desc'], tmpDir, { GSD_SECTION_MANIFEST: manifestPath });
|
|
assert.ok(result.success, `a malformed manifest file must not crash the command: ${result.error}`);
|
|
const output = JSON.parse(result.output);
|
|
assert.equal(output.section_manifest, null);
|
|
});
|
|
});
|
|
|
|
// ─── Group B: compound-fact folding lives in init.cts, never the grammar ──
|
|
|
|
describe('compound-fact folding at the init seam — matrix §B', () => {
|
|
let tmpDir;
|
|
|
|
beforeEach(() => {
|
|
tmpDir = createTempProject('section-manifest-b-');
|
|
});
|
|
|
|
afterEach(() => {
|
|
cleanup(tmpDir);
|
|
});
|
|
|
|
// B1-B4: cmdInitQuick folds --full into --discuss/--research/--validate BEFORE
|
|
// buildSectionManifestField evaluates flag:--discuss/flag:--research/flag:--validate.
|
|
describe('cmdInitQuick folds --full into each mode fact (rows B1-B4)', () => {
|
|
test('--discuss alone includes discussion-phase (row B1, baseline)', () => {
|
|
const output = runInitJson(['init', 'quick', 'desc', '--discuss'], tmpDir);
|
|
assert.ok(output.section_manifest.included.includes('discussion-phase'));
|
|
});
|
|
|
|
test('--full alone (no --discuss) STILL includes discussion-phase — the fold this PR exists to prove (row B2)', () => {
|
|
const output = runInitJson(['init', 'quick', 'desc', '--full'], tmpDir);
|
|
assert.ok(
|
|
output.section_manifest.included.includes('discussion-phase'),
|
|
'--full must imply --discuss for section-gating purposes, folded in cmdInitQuick before evaluation',
|
|
);
|
|
assert.ok(output.section_manifest.included.includes('research-phase'), '--full must also imply --research');
|
|
assert.ok(output.section_manifest.included.includes('plan-checker-loop'), '--full must also imply --validate (plan-checker-loop)');
|
|
assert.ok(output.section_manifest.included.includes('quick-verification'), '--full must also imply --validate (quick-verification)');
|
|
});
|
|
|
|
test('neither --discuss nor --full excludes discussion-phase (row B3)', () => {
|
|
const output = runInitJson(['init', 'quick', 'desc'], tmpDir);
|
|
assert.ok(output.section_manifest.excluded.includes('discussion-phase'));
|
|
});
|
|
|
|
test('--full AND --discuss together still include discussion-phase exactly once, no double-counting (row B4)', () => {
|
|
const output = runInitJson(['init', 'quick', 'desc', '--full', '--discuss'], tmpDir);
|
|
const occurrences = output.section_manifest.included.filter((id) => id === 'discussion-phase');
|
|
assert.equal(occurrences.length, 1, 'discussion-phase must appear exactly once in included, never duplicated by the fold');
|
|
});
|
|
});
|
|
|
|
// B5-B6: cmdInitAutonomous folds --converge OR --cross-ai into one plan_strategy_converge fact.
|
|
describe('cmdInitAutonomous folds --converge OR --cross-ai (rows B5-B6)', () => {
|
|
test('--converge alone drives state:plan-strategy-converge sections into included (row B5)', () => {
|
|
const output = runInitJson(['init', 'autonomous', '--converge'], tmpDir);
|
|
assert.equal(output.plan_strategy_converge, true);
|
|
assert.ok(output.section_manifest.included.includes('converge-fail-fast'));
|
|
assert.ok(output.section_manifest.included.includes('converge-banner'));
|
|
});
|
|
|
|
test('--cross-ai alone (the documented alias, no --converge) ALSO drives inclusion (row B6)', () => {
|
|
const output = runInitJson(['init', 'autonomous', '--cross-ai'], tmpDir);
|
|
assert.equal(output.plan_strategy_converge, true);
|
|
assert.ok(output.section_manifest.included.includes('converge-fail-fast'));
|
|
assert.ok(output.section_manifest.included.includes('converge-loop'));
|
|
});
|
|
|
|
test('neither flag excludes every converge-* section', () => {
|
|
const output = runInitJson(['init', 'autonomous'], tmpDir);
|
|
assert.equal(output.plan_strategy_converge, false);
|
|
for (const id of ['converge-fail-fast', 'converge-banner', 'converge-dispatch-bg', 'converge-dispatch-inline', 'converge-loop']) {
|
|
assert.ok(output.section_manifest.excluded.includes(id), `expected "${id}" excluded when neither --converge nor --cross-ai is set`);
|
|
}
|
|
});
|
|
});
|
|
|
|
// B7: cmdInitUpdate folds --next OR --rc into one next_channel fact.
|
|
describe('cmdInitUpdate folds --next OR --rc (row B7)', () => {
|
|
test('--rc alone (not --next) drives channel-banner into included', () => {
|
|
const output = runInitJson(['init', 'update', '--rc'], tmpDir);
|
|
assert.equal(output.next_channel, true);
|
|
assert.ok(output.section_manifest.included.includes('channel-banner'));
|
|
});
|
|
|
|
test('--next alone also drives channel-banner into included (the other half of the OR)', () => {
|
|
const output = runInitJson(['init', 'update', '--next'], tmpDir);
|
|
assert.equal(output.next_channel, true);
|
|
assert.ok(output.section_manifest.included.includes('channel-banner'));
|
|
});
|
|
|
|
test('neither flag excludes channel-banner', () => {
|
|
const output = runInitJson(['init', 'update'], tmpDir);
|
|
assert.equal(output.next_channel, false);
|
|
assert.ok(output.section_manifest.excluded.includes('channel-banner'));
|
|
});
|
|
});
|
|
|
|
// B8: cmdInitDiscussPhaseAssumptions folds --auto OR consolidated auto-mode config.
|
|
describe('cmdInitDiscussPhaseAssumptions folds --auto flag OR config auto-mode (row B8)', () => {
|
|
test('no --auto flag, but config workflow._auto_chain_active=true, still includes auto-advance-dispatch', () => {
|
|
writeConfig(tmpDir, { workflow: { _auto_chain_active: true } });
|
|
const output = runInitJson(['init', 'discuss-phase-assumptions', '99'], tmpDir);
|
|
assert.ok(output.section_manifest.included.includes('auto-advance-dispatch'));
|
|
});
|
|
|
|
test('no --auto flag, but config workflow.auto_advance=true, still includes auto-advance-dispatch (the other config source)', () => {
|
|
writeConfig(tmpDir, { workflow: { auto_advance: true } });
|
|
const output = runInitJson(['init', 'discuss-phase-assumptions', '99'], tmpDir);
|
|
assert.ok(output.section_manifest.included.includes('auto-advance-dispatch'));
|
|
});
|
|
|
|
test('--auto flag present with no config also includes auto-advance-dispatch', () => {
|
|
const output = runInitJson(['init', 'discuss-phase-assumptions', '99', '--auto'], tmpDir);
|
|
assert.ok(output.section_manifest.included.includes('auto-advance-dispatch'));
|
|
});
|
|
|
|
test('neither --auto nor either config key excludes auto-advance-dispatch', () => {
|
|
const output = runInitJson(['init', 'discuss-phase-assumptions', '99'], tmpDir);
|
|
assert.ok(output.section_manifest.excluded.includes('auto-advance-dispatch'));
|
|
});
|
|
});
|
|
});
|
|
|
|
// ─── Group D: flag value shapes — token presence, not value truthiness ────
|
|
|
|
describe('flag value shapes drive section_manifest by truthiness, not semantic value — matrix §D', () => {
|
|
let tmpDir;
|
|
|
|
beforeEach(() => {
|
|
tmpDir = createTempProject('section-manifest-d-');
|
|
seedPhase(tmpDir, '01-sample', { '01-CONTEXT.md': '# Phase Context\n' });
|
|
});
|
|
|
|
afterEach(() => {
|
|
cleanup(tmpDir);
|
|
});
|
|
|
|
test('absent boolean flag (--reviews never passed) does not mark reviews-prerequisite present (row D1)', () => {
|
|
const output = runInitJson(['init', 'plan-phase', '1'], tmpDir);
|
|
assert.ok(output.section_manifest.excluded.includes('reviews-prerequisite'));
|
|
assert.ok(!output.section_manifest.included.includes('reviews-prerequisite'));
|
|
});
|
|
|
|
test('empty-string value flag (--prd "") excludes prd-express-gate — an empty value is not a branch selection (row D2)', () => {
|
|
const output = runInitJson(['init', 'plan-phase', '1', '--prd', ''], tmpDir);
|
|
assert.ok(output.section_manifest.excluded.includes('prd-express-gate'));
|
|
});
|
|
|
|
test('string-"0" value flag (--prd "0") INCLUDES prd-express-gate — token-presence semantics, not value truthiness (row D3)', () => {
|
|
const output = runInitJson(['init', 'plan-phase', '1', '--prd', '0'], tmpDir);
|
|
assert.ok(output.section_manifest.included.includes('prd-express-gate'), '--prd "0" is a non-empty string and must be treated as present');
|
|
});
|
|
|
|
test('whitespace-only value flag (--prd " ") includes prd-express-gate, asserted deliberately (row D4)', () => {
|
|
const output = runInitJson(['init', 'plan-phase', '1', '--prd', ' '], tmpDir);
|
|
assert.ok(output.section_manifest.included.includes('prd-express-gate'));
|
|
});
|
|
|
|
test('duplicate flag tokens (--prd a --prd b) resolve to a single membership, no crash (row D5)', () => {
|
|
const result = runGsdTools(['init', 'plan-phase', '1', '--prd', 'a', '--prd', 'b'], tmpDir);
|
|
assert.ok(result.success, `duplicate --prd tokens must not crash the command: ${result.error}`);
|
|
const output = JSON.parse(result.output);
|
|
assert.ok(output.section_manifest.included.includes('prd-express-gate'));
|
|
const occurrences = output.section_manifest.included.filter((id) => id === 'prd-express-gate');
|
|
assert.equal(occurrences.length, 1, 'must be a single membership, not one entry per duplicate token');
|
|
});
|
|
|
|
test('flag-shaped value (--prd --reviews) does not crash and deterministically excludes prd-express-gate (row D6)', () => {
|
|
// parseNamedArgs treats a token starting with "--" as the NEXT flag, never
|
|
// as this flag's value — so --prd here resolves to null (absent), not the
|
|
// literal string "--reviews".
|
|
//
|
|
// Corrected after the first full verification run: the original choice of
|
|
// `--weird` here predates ADR-3473 §8.4's strict unrecognized-flag
|
|
// rejection (this file is from #2994/epic #1671, before #3358's strict
|
|
// parseNamedArgs) and is itself an unrecognized flag for `plan-phase` —
|
|
// it now correctly fails with exit 1 / "unknown flag --weird" instead of
|
|
// proving the "flag-shaped value" point this test exists for. Swapped for
|
|
// `--reviews`, a real declared plan-phase boolean flag, matching the same
|
|
// substitution already used by the sibling row
|
|
// tests/init.test.cjs:emptyPrdValueIsFalsyAndTreatedAsAbsent (row B5).
|
|
const result = runGsdTools(['init', 'plan-phase', '1', '--prd', '--reviews'], tmpDir);
|
|
assert.ok(result.success, `a flag-shaped value must not crash the command: ${result.error}`);
|
|
const output = JSON.parse(result.output);
|
|
assert.ok(output.section_manifest.excluded.includes('prd-express-gate'), '--prd immediately followed by another --flag token must resolve to absent, per parseNamedArgs');
|
|
});
|
|
|
|
test('unicode / very long value does not crash and is included as present (row D7)', () => {
|
|
const longUnicodeValue = `产品需求文档-🚀-${'x'.repeat(2000)}`;
|
|
const result = runGsdTools(['init', 'plan-phase', '1', '--prd', longUnicodeValue], tmpDir);
|
|
assert.ok(result.success, `a unicode/very-long --prd value must not crash the command: ${result.error}`);
|
|
const output = JSON.parse(result.output);
|
|
assert.ok(output.section_manifest.included.includes('prd-express-gate'));
|
|
});
|
|
});
|