* chore(#604): rename get-shit-done/ runtime directory to gsd-core/ Renames the installed runtime directory `get-shit-done/` to `gsd-core/` so the on-disk name matches the package (`@opengsd/gsd-core`), repo, and binary (`gsd-tools`). The npm package name and binary are unchanged; npx/npm consumers are unaffected. Mechanical (bulk, ~90% of the diff): - `git mv get-shit-done gsd-core` - Swept path/identifier references across the repo via `perl -pe 's/get-shit-done(?!-\w)/gsd-core/g'`. The negative lookahead preserves the five legitimate slug variants that are NOT the directory: get-shit-done-{OLD,cc,classic,cli,redux} (old package/repo names). - Build/manifest wiring: package.json (bin, files, coverage globs), tsconfig.build.json (outDir), ~86 .gitignore build-output entries, stryker.config.mjs, scan-ignore files, install.js path strings. - Frozen (not rewritten): CHANGELOG.md history; translated docs (README.<locale>.md and docs/{ja-JP,ko-KR,pt-BR,zh-CN}/). New logic (review here): - src/installer-migrations/003-rename-get-shit-done-to-gsd-core.cts: a proper ADR-0008 installer migration. On upgrade it walks the legacy `~/.claude/get-shit-done/` tree, classifies each file via the prior install manifest, and emits remove-managed / backup-and-remove for managed files while PRESERVING unknown user-added files. Symlink-safe (skips a symlinked root and symlinked entries; bounds-checks every path under configDir). The framework rolls back on install failure. Emptied dirs may remain (framework has no recursive dir-removal primitive) — documented. - scripts/lint-legacy-dir-name.cjs: CI regression guard forbidding the bare `get-shit-done` directory token (split token to avoid self-match; case- insensitive; `(?!-\w)` lookahead allows the slug variants; allowlists CHANGELOG, translated docs, and `gsd-allow-legacy-name` marker lines). Wired into the lint-tests CI job. - Restored scripts/lint-package-identity-drift.cjs detection regexes (the mechanical sweep had wrongly rewritten the old-name patterns it exists to detect) and marked them as intentional legacy references. - TDD tests for the migration and the guard; do.md slash-command guard regex tightened so a `/gsd-core/bin` path segment is not mistaken for a command; changeset + docs/installer-migrations.md row added. Breaking: the installed runtime path moves `~/.claude/get-shit-done/` -> `~/.claude/gsd-core/`. Migration 003 removes the stale legacy dir's managed files (preserving user files) on upgrade. Users with custom hooks/configs hardcoding the old path must update them. Closes #604 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): unsweep pending changesets + allowlist injection-example docs CI fixes for the rename PR: - Do not sweep pending .changeset/*.md (ephemeral release-note fragments, like CHANGELOG); reverted those body edits so 5 pre-existing malformed fragments (missing type/pr) no longer enter the PR diff and trip docs-lint. Allowlisted .changeset/ in the legacy-name guard accordingly. - Allowlisted TEST-EXAMPLES.md and docs/explanation/security-model.md in prompt-injection-scan.sh: they contain intentional injection examples / security-model prose; the path-reference rewrites are kept. CodeQL alerts on this PR are pre-existing (alert lines unchanged by this PR; none in the new migration/guard) and are out of scope for the rename. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): resolve CodeQL alerts surfaced on this PR The rename diff touched files carrying pre-existing CodeQL findings; per the no-pre-existing-dismissal rule, fixing every surfaced alert rather than waving them off. All behavior-preserving: - scripts/ci-test-scope.cjs: build the config-path match from string .includes() instead of a RegExp over an arg-derived value (js/regex-injection). - src/profile-output.cts: escape backslashes before pipe-escaping desc/safeName so the table-cell escape is complete (js/incomplete-sanitization). - tests/{bug-2643,bug-2808,docs-parity-live-registry}: two-pass HTML-comment strip so a bare/unclosed `<!--` cannot survive (js/incomplete-multi-character-sanitization). - tests/inline-plan-threshold: drop the no-op `\s`->`\s` identity replace, keep the meaningful POSIX-class conversion (js/identity-replacement). Verified: build:lib green; the touched test files + ci-test-scope + profile-output suites pass; lint:legacy-name clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): correctly resolve remaining CodeQL alerts (regex-injection + sanitization) The prior commit's fixes for two alerts were ineffective: - ci-test-scope.cjs js/regex-injection: the alert is the CLI-arg-derived `file` reaching static regex `.test(file)` calls (not the config rule). Removed ALL regex over file/t — startsWith/includes/=== string checks + an isWindowsHint helper — so there is no regex sink for the tainted value. - js/incomplete-multi-character-sanitization (3 test files): a single `.replace(/<!--...-->/g,'')` can let `<!--` re-form. Replaced with a fixpoint loop (replace until stable) plus a final bare-opener strip. Verified: no regex over file/t remains; ci-test-scope + the 3 test suites pass; lint:legacy-name clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): make ci-test-scope + comment-strippers regex-free to clear CodeQL CodeQL flags the regex PATTERNS syntactically (regex-injection on the --files arg split; incomplete-multi-character-sanitization on the <!--...--> replace), so loop fixes do not satisfy it. Made these paths regex-free: - ci-test-scope.cjs splitFiles: char-by-char separator tokenizer (no /[,\\s]+/). - 3 test files: indexOf/slice HTML-comment stripper (no .replace(/<!--/)). Behavior preserved; ci-test-scope + the 3 suites pass; guard clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): unblock security base64 scan on the large rename diff The security job hit its 10m timeout: base64-scan.sh choked on the binary test fixture tests/feat-3594-parser-property-style.test.cjs (embedded NUL/ non-UTF8 bytes -> thousands of bogus blobs + "ignored null byte" warnings), and the ~800-file rename diff is slow to scan regardless. - scripts/base64-scan.sh: skip binary-by-content files (grep -Iq .) — they can't carry base64-obfuscated *text* and feeding NUL bytes through the per-line scanner is pathologically slow. collect_files already filtered binary *extensions*; this catches binary *content* in text extensions. - .github/workflows/security-scan.yml: raise the security job timeout 10m->30m to accommodate very large diffs (the scan itself is unchanged). Verified locally: scan skips the fixture, 0 "ignored null byte" warnings, 0 findings, exit 0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): sweep get-shit-done refs introduced by merging next The branch was updated with next (#614/#384/#618 etc.), which reference the get-shit-done/ dir (still named that on next). Swept the stale references in the merged files to gsd-core so the rename stays consistent and lint:legacy-name passes: - commands/gsd/discuss-phase.md (runtime-launcher shim paths) - src/core.cts (getAgentsDir layout comments) - tests/bug-384-agents-runtime-aware.test.cjs (require path to runtime lib) Verified: guard 0 violations; build green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): exclude gsd-core/ path segments from bug-3683 command cross-ref invariant The #614 runtime-launcher shim added to discuss-phase.md references `${_GSD_RUNTIME_ROOT}/gsd-core/bin/...`. bug-3683's REF_PATTERN excluded path-y refs only via lookbehind, but `}` precedes `/gsd-core/` in the shim, so it mis-read the directory path as a dangling `/gsd-core` command ref (same class as the #604 bug-2954 fix). Added a trailing `(?![\w-]*\/)` so `/gsd-<x>/...` path segments are not treated as slash-command references. Verified locally on BOTH platforms before pushing: - mac (node 26) full suite: 0 failures - gsd-test-runner (linux, node22 image) full suite: 0 failures - bug-3683 + bug-2954 pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): lazily resolve findProjectRoot in gsd-tools (harden flaky CI) CI intermittently failed state.test's gsd-tools subprocess with "findProjectRoot is not a function" (flip-flopping across legs; not reproducible on mac full suite, gsd-test linux full suite, test:unit, or state.test x8). findProjectRoot is a re-export from core.cjs (sourced from project-root.cjs); binding it via destructure at module-load can be undefined under a load-ordering edge. Resolve it lazily at call time via a small wrapper so the lookup happens after core.cjs is fully initialized. Verified green on BOTH platforms before pushing: - mac (node 26) full suite: 0 failures - gsd-test-runner (linux, node22) full suite: 0 failures - state.test.cjs: 106/106; gsd-tools loads cleanly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#604): allowlist verification-patterns.md placeholder examples in secret scan The rename git-mv'd references/verification-patterns.md into gsd-core/, pulling it into the secret-scan diff. It documents stub/placeholder RED-FLAG env-var examples (illustrative Stripe test-key / database-URL / API-key placeholders) — not real credentials. Added it to .secretscanignore with the strict annotation, mirroring the existing gsd-core/workflows/plan-phase.md exception. Verified locally: secret-scan-lint --strict OK; secret-scan --diff origin/next exits 0 with 0 findings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
395 lines
16 KiB
JavaScript
395 lines
16 KiB
JavaScript
'use strict';
|
|
|
|
// allow-test-rule: source-text-is-the-product
|
|
// Reads .md/.json/.yml product files whose deployed text IS what the
|
|
// runtime loads — testing text content tests the deployed contract.
|
|
|
|
/**
|
|
* Tests for /gsd-edit-phase (#2617)
|
|
*
|
|
* Covers:
|
|
* - Command file and workflow file existence
|
|
* - Single-field edit instructions
|
|
* - Full-phase regeneration from clarified intent
|
|
* - Invalid depends_on blocks with clear error
|
|
* - Guarded edit of in_progress phase without --force
|
|
* - --force override of status guard
|
|
* - Invalid phase number produces clear error
|
|
* - Diff + confirmation before writing
|
|
* - Phase number and position are preserved
|
|
*/
|
|
|
|
const { describe, test } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
|
|
const ROOT = path.resolve(__dirname, '..');
|
|
|
|
// #2790: edit-phase.md was consolidated into phase.md as the --edit flag.
|
|
// The COMMAND_PATH here now points to the consolidated command.
|
|
const COMMAND_PATH = path.join(ROOT, 'commands', 'gsd', 'phase.md');
|
|
const WORKFLOW_PATH = path.join(ROOT, 'gsd-core', 'workflows', 'edit-phase.md');
|
|
|
|
// ─── File existence ──────────────────────────────────────────────────────────
|
|
|
|
describe('edit-phase: file existence', () => {
|
|
test('commands/gsd/phase.md exists (absorbed edit-phase in #2790)', () => {
|
|
assert.ok(fs.existsSync(COMMAND_PATH), 'commands/gsd/phase.md should exist (consolidates edit-phase)');
|
|
});
|
|
|
|
test('gsd-core/workflows/edit-phase.md exists', () => {
|
|
assert.ok(fs.existsSync(WORKFLOW_PATH), 'gsd-core/workflows/edit-phase.md should exist');
|
|
});
|
|
});
|
|
|
|
// ─── Command file structure ───────────────────────────────────────────────────
|
|
|
|
describe('edit-phase: command file structure', () => {
|
|
test('consolidated phase.md has correct name frontmatter (#2790)', () => {
|
|
const content = fs.readFileSync(COMMAND_PATH, 'utf-8');
|
|
assert.ok(/^name:\s*gsd:phase/m.test(content), 'name should be gsd:phase (consolidated)');
|
|
});
|
|
|
|
test('command file has description frontmatter', () => {
|
|
const content = fs.readFileSync(COMMAND_PATH, 'utf-8');
|
|
assert.ok(/^description:/m.test(content), 'should have description frontmatter');
|
|
});
|
|
|
|
test('command file references edit-phase workflow', () => {
|
|
const content = fs.readFileSync(COMMAND_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('edit-phase.md'),
|
|
'command file should reference edit-phase workflow'
|
|
);
|
|
});
|
|
|
|
test('command file documents --force flag (passed through --edit)', () => {
|
|
const content = fs.readFileSync(COMMAND_PATH, 'utf-8');
|
|
assert.ok(content.includes('--edit') || content.includes('--force'), 'command file should document --edit flag (which supports --force)');
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: single-field edit ─────────────────────────────────────────────
|
|
|
|
describe('edit-phase workflow: single-field edit', () => {
|
|
test('workflow instructs presenting current field values before editing', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const showsCurrentValues = (
|
|
/current\s+value/i.test(content) ||
|
|
/present.*current/i.test(content) ||
|
|
/display.*current/i.test(content) ||
|
|
/current_value/i.test(content)
|
|
);
|
|
assert.ok(showsCurrentValues, 'workflow must present current field values before editing');
|
|
});
|
|
|
|
test('workflow supports editing specific fields individually', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const supportsIndividualFields = (
|
|
/specific\s+field/i.test(content) ||
|
|
/individual\s+field/i.test(content) ||
|
|
/edit.*field/i.test(content)
|
|
);
|
|
assert.ok(supportsIndividualFields, 'workflow must support editing individual fields');
|
|
});
|
|
|
|
test('workflow covers title, goal, depends_on, requirements, success_criteria fields', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
assert.ok(/\btitle\b/i.test(content), 'workflow should mention title field');
|
|
assert.ok(/\bgoal\b/i.test(content), 'workflow should mention goal field');
|
|
assert.ok(/depends_on/i.test(content), 'workflow should mention depends_on field');
|
|
assert.ok(/requirements/i.test(content), 'workflow should mention requirements field');
|
|
assert.ok(/success_criteria/i.test(content), 'workflow should mention success_criteria field');
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: full-phase regeneration ───────────────────────────────────────
|
|
|
|
describe('edit-phase workflow: full-phase regeneration', () => {
|
|
test('workflow supports regenerating all fields from clarified intent', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const supportsRegen = (
|
|
/regenerate/i.test(content) ||
|
|
/rewrite.*all/i.test(content) ||
|
|
/all.*from.*clarified/i.test(content) ||
|
|
/clarified.*intent/i.test(content)
|
|
);
|
|
assert.ok(supportsRegen, 'workflow must support full regeneration from clarified intent');
|
|
});
|
|
|
|
test('workflow prompts user for clarified intent during full regeneration', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const promptsClarifiedIntent = (
|
|
/clarified?\s+intent/i.test(content) ||
|
|
/revised\s+intent/i.test(content) ||
|
|
/describe.*revised/i.test(content)
|
|
);
|
|
assert.ok(
|
|
promptsClarifiedIntent,
|
|
'workflow must prompt user for clarified intent during full regeneration'
|
|
);
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: invalid depends_on ────────────────────────────────────────────
|
|
|
|
describe('edit-phase workflow: depends_on validation', () => {
|
|
test('workflow validates depends_on references against existing phases', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const validatesDepends = (
|
|
/validate.*depends/i.test(content) ||
|
|
/depends.*valid/i.test(content) ||
|
|
/invalid.*depends/i.test(content) ||
|
|
/depends_on.*valid/i.test(content)
|
|
);
|
|
assert.ok(validatesDepends, 'workflow must validate depends_on references');
|
|
});
|
|
|
|
test('workflow blocks write when depends_on references invalid phase', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const blocksInvalidRef = (
|
|
/invalid.*phase/i.test(content) &&
|
|
/exit|block|error/i.test(content)
|
|
);
|
|
assert.ok(blocksInvalidRef, 'workflow must block write for invalid depends_on references');
|
|
});
|
|
|
|
test('workflow validates that depends_on does not reference the phase itself', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const preventsCircular = (
|
|
/not reference itself/i.test(content) ||
|
|
/circular/i.test(content) ||
|
|
/self-reference/i.test(content) ||
|
|
/itself/i.test(content)
|
|
);
|
|
assert.ok(preventsCircular, 'workflow must prevent self-referencing depends_on');
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: status guard ───────────────────────────────────────────────────
|
|
|
|
describe('edit-phase workflow: in-progress/completed status guard', () => {
|
|
test('workflow checks phase status before allowing edit', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const checksStatus = (
|
|
/disk_status/i.test(content) ||
|
|
/phase.*status/i.test(content) ||
|
|
/status.*check/i.test(content)
|
|
);
|
|
assert.ok(checksStatus, 'workflow must check phase status before allowing edit');
|
|
});
|
|
|
|
test('workflow refuses to edit in_progress phases without --force', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const refusesInProgress = (
|
|
/in.progress/i.test(content) &&
|
|
/--force/i.test(content)
|
|
);
|
|
assert.ok(refusesInProgress, 'workflow must refuse in_progress edits without --force');
|
|
});
|
|
|
|
test('workflow refuses to edit completed phases without --force', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const refusesCompleted = (
|
|
/completed/i.test(content) &&
|
|
/--force/i.test(content)
|
|
);
|
|
assert.ok(refusesCompleted, 'workflow must refuse completed phase edits without --force');
|
|
});
|
|
|
|
test('workflow allows edit with --force flag override', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const forcePath = content.match(/--force[\s\S]{0,300}/i);
|
|
assert.ok(forcePath, 'workflow must handle --force flag');
|
|
const forceSection = forcePath[0];
|
|
const allowsForce = (
|
|
/proceed|continue|allow|override/i.test(forceSection) ||
|
|
/force.*was.*passed/i.test(content) ||
|
|
/force.*passed/i.test(content)
|
|
);
|
|
assert.ok(allowsForce, 'workflow must allow editing when --force is passed');
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: invalid phase number ──────────────────────────────────────────
|
|
|
|
describe('edit-phase workflow: invalid phase number', () => {
|
|
test('workflow produces clear error when phase number does not exist', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const handlesNotFound = (
|
|
/not.*found/i.test(content) ||
|
|
/phase.*not.*found/i.test(content) ||
|
|
/does not exist/i.test(content)
|
|
);
|
|
assert.ok(handlesNotFound, 'workflow must error clearly when phase number does not exist');
|
|
});
|
|
|
|
test('workflow errors on missing phase number argument', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const handlesNoArg = (
|
|
/no.*argument/i.test(content) ||
|
|
/required/i.test(content) ||
|
|
/phase number required/i.test(content)
|
|
);
|
|
assert.ok(handlesNoArg, 'workflow must error when phase number argument is missing');
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: diff + confirmation ───────────────────────────────────────────
|
|
|
|
describe('edit-phase workflow: diff and confirmation', () => {
|
|
test('workflow shows diff of changes before writing', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const showsDiff = (
|
|
/diff/i.test(content) ||
|
|
/proposed.*change/i.test(content) ||
|
|
/show.*change/i.test(content)
|
|
);
|
|
assert.ok(showsDiff, 'workflow must show a diff of changes before writing');
|
|
});
|
|
|
|
test('workflow asks for confirmation before writing', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const asksConfirmation = (
|
|
/confirm/i.test(content) ||
|
|
/apply.*change/i.test(content) ||
|
|
/y\/n/i.test(content) ||
|
|
/yes.*no/i.test(content)
|
|
);
|
|
assert.ok(asksConfirmation, 'workflow must ask for confirmation before writing');
|
|
});
|
|
|
|
test('workflow exits without writing if user declines', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const handlesDecline = (
|
|
/says.*n/i.test(content) ||
|
|
/user says.*n/i.test(content) ||
|
|
/if.*user.*n/i.test(content) ||
|
|
/exit.*without.*writing/i.test(content) ||
|
|
/without writing/i.test(content)
|
|
);
|
|
assert.ok(handlesDecline, 'workflow must exit without writing if user declines confirmation');
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: phase number and position preservation ────────────────────────
|
|
|
|
describe('edit-phase workflow: phase number and position preservation', () => {
|
|
test('workflow preserves phase number when writing back', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const preservesNumber = (
|
|
/number.*preserved/i.test(content) ||
|
|
/preserve.*number/i.test(content) ||
|
|
/position.*preserved/i.test(content) ||
|
|
/number and position/i.test(content)
|
|
);
|
|
assert.ok(preservesNumber, 'workflow must preserve phase number and position');
|
|
});
|
|
|
|
test('anti_patterns block renumbering', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const antiPatterns = content.match(/<anti_patterns>([\s\S]*?)<\/anti_patterns>/i);
|
|
assert.ok(antiPatterns, 'workflow should have anti_patterns section');
|
|
assert.ok(
|
|
/renumber|number.*preserved|preserve.*number/i.test(antiPatterns[1]),
|
|
'anti_patterns must prohibit renumbering'
|
|
);
|
|
});
|
|
|
|
test('workflow writes phase back in place (replaces section, not full file)', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const inPlace = (
|
|
/in.*place/i.test(content) ||
|
|
/replace.*section/i.test(content) ||
|
|
/section.*replace/i.test(content) ||
|
|
/replace.*old.*section/i.test(content)
|
|
);
|
|
assert.ok(inPlace, 'workflow must write phase back in place (section replacement)');
|
|
});
|
|
});
|
|
|
|
// ─── Workflow: STATE.md update ────────────────────────────────────────────────
|
|
|
|
describe('edit-phase workflow: STATE.md roadmap evolution', () => {
|
|
test('workflow updates STATE.md Roadmap Evolution after edit', () => {
|
|
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
|
|
const updatesState = (
|
|
/state\.add-roadmap-evolution/i.test(content) ||
|
|
/Roadmap Evolution/i.test(content)
|
|
);
|
|
assert.ok(updatesState, 'workflow must update STATE.md Roadmap Evolution after edit');
|
|
});
|
|
});
|
|
|
|
// ─── Docs registration ────────────────────────────────────────────────────────
|
|
|
|
describe('edit-phase: documentation registration', () => {
|
|
test('INVENTORY.md routes edit-phase workflow through consolidated /gsd-phase --edit (#2790)', () => {
|
|
// #2790 absorbed /gsd-edit-phase into /gsd-phase as the --edit flag. The
|
|
// workflow file (edit-phase.md) survives, but its "Invoked by" column must
|
|
// point at the consolidated command surface, not the deleted standalone.
|
|
const inventory = fs.readFileSync(
|
|
path.join(ROOT, 'docs', 'INVENTORY.md'),
|
|
'utf-8'
|
|
);
|
|
// Locate the edit-phase.md row in the Workflows table and assert the
|
|
// "Invoked by" column documents /gsd-phase --edit (not the deleted form).
|
|
const rowMatch = inventory.match(/^\|\s*`edit-phase\.md`\s*\|[^|]*\|\s*([^|]+?)\s*\|$/m);
|
|
assert.ok(rowMatch, 'docs/INVENTORY.md must contain an edit-phase.md workflow row');
|
|
const invokedBy = rowMatch[1];
|
|
assert.ok(
|
|
/\/gsd-phase\s+--edit/.test(invokedBy),
|
|
`edit-phase.md row must list "/gsd-phase --edit" as caller; got: "${invokedBy}"`
|
|
);
|
|
assert.ok(
|
|
!/\/gsd-edit-phase\b/.test(invokedBy),
|
|
`edit-phase.md row must not still cite the deleted /gsd-edit-phase command; got: "${invokedBy}"`
|
|
);
|
|
});
|
|
|
|
test('INVENTORY.md contains edit-phase.md workflow', () => {
|
|
const inventory = fs.readFileSync(
|
|
path.join(ROOT, 'docs', 'INVENTORY.md'),
|
|
'utf-8'
|
|
);
|
|
assert.ok(
|
|
inventory.includes('edit-phase.md'),
|
|
'docs/INVENTORY.md must contain edit-phase.md workflow row'
|
|
);
|
|
});
|
|
|
|
test('INVENTORY-MANIFEST.json contains /gsd-phase in commands (#2790: edit-phase absorbed into phase.md)', () => {
|
|
// #2790: /gsd-edit-phase was absorbed into /gsd-phase as the --edit flag.
|
|
// The manifest now records /gsd-phase instead of /gsd-edit-phase.
|
|
const manifest = JSON.parse(
|
|
fs.readFileSync(path.join(ROOT, 'docs', 'INVENTORY-MANIFEST.json'), 'utf-8')
|
|
);
|
|
assert.ok(
|
|
manifest.families.commands.includes('/gsd-phase'),
|
|
'INVENTORY-MANIFEST.json must list /gsd-phase in commands (absorbed /gsd-edit-phase via #2790)'
|
|
);
|
|
});
|
|
|
|
test('INVENTORY-MANIFEST.json contains edit-phase.md in workflows', () => {
|
|
const manifest = JSON.parse(
|
|
fs.readFileSync(path.join(ROOT, 'docs', 'INVENTORY-MANIFEST.json'), 'utf-8')
|
|
);
|
|
assert.ok(
|
|
manifest.families.workflows.includes('edit-phase.md'),
|
|
'INVENTORY-MANIFEST.json must list edit-phase.md in workflows'
|
|
);
|
|
});
|
|
|
|
test('docs/COMMANDS.md documents /gsd-phase (absorbed /gsd-edit-phase via --edit flag, #2790)', () => {
|
|
const commands = fs.readFileSync(
|
|
path.join(ROOT, 'docs', 'COMMANDS.md'),
|
|
'utf-8'
|
|
);
|
|
assert.ok(
|
|
commands.includes('/gsd-phase'),
|
|
'docs/COMMANDS.md must document /gsd-phase (which absorbed /gsd-edit-phase via --edit flag in #2790)'
|
|
);
|
|
});
|
|
});
|