* 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>
430 lines
17 KiB
JavaScript
430 lines
17 KiB
JavaScript
'use strict';
|
|
|
|
/**
|
|
* Regression test for issue #4 (open-gsd/gsd-core):
|
|
* bin/lib/phase.cjs cmdPhaseComplete — non-idempotent and unclamped.
|
|
*
|
|
* Root cause (pre-fix):
|
|
* cmdPhaseComplete blindly increments "Completed Phases" by 1 on every call
|
|
* (parseInt(completedRaw, 10) + 1) and recomputes Progress without a clamp.
|
|
* Double-calling yields Completed Phases +2 (not +1), and Progress can exceed 100%.
|
|
*
|
|
* Fix: derive completed_phases from ROADMAP Complete-row count (idempotent) and
|
|
* clamp percent to 100. This mirrors the SDK fix in phase-lifecycle.ts
|
|
* (commit deriving from ROADMAP, referenced as "PR #3520" in issue #4).
|
|
*
|
|
* Note on test structure: phase-command-router.cjs delegates to the SDK when
|
|
* the SDK dist is present, so the CJS path is exercised by calling
|
|
* cmdPhaseComplete directly (bypassing the router), which is the actual
|
|
* function containing the bug.
|
|
*
|
|
* References:
|
|
* - ADR-3524 (docs/adr/3524-cjs-sdk-hard-seam.md) — architectural foundation
|
|
* - /tmp/adr-3524-review-findings.md — architectural justification
|
|
* - Issue #4 (open-gsd/gsd-core)
|
|
*/
|
|
|
|
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 os = require('node:os');
|
|
|
|
const { cleanup } = require('./helpers.cjs');
|
|
|
|
// ── Load cmdPhaseComplete directly from phase.cjs (bypass the SDK router) ────
|
|
// phase-command-router.cjs delegates to SDK when available; we must test the
|
|
// CJS implementation directly since that is where the bug lives.
|
|
const phaseModule = require('../gsd-core/bin/lib/phase.cjs');
|
|
const { cmdPhaseComplete } = phaseModule;
|
|
|
|
// ── Fixture builder ──────────────────────────────────────────────────────────
|
|
|
|
/**
|
|
* Creates a minimal fixture project with:
|
|
* - ROADMAP.md with a 4-column progress table (Phase | Plans | Status | Completed)
|
|
* - REQUIREMENTS.md with a phase-scoped REQ-ID and Traceability row
|
|
* - STATE.md with Completed Phases: 0 and Total Phases: 2 (Progress 0%)
|
|
* - Phase 01 directory with one plan+summary (to satisfy phase complete guard)
|
|
* - Phase 02 directory (next phase)
|
|
*/
|
|
function createFixture(prefix = 'gsd-4-regression-') {
|
|
const tmpDir = fs.mkdtempSync(path.join(os.tmpdir(), prefix));
|
|
const planningDir = path.join(tmpDir, '.planning');
|
|
const phasesDir = path.join(planningDir, 'phases');
|
|
fs.mkdirSync(phasesDir, { recursive: true });
|
|
|
|
// ROADMAP.md: Phase 01 not yet complete, Phase 02 not started
|
|
// 4-column progress table: Phase | Plans Complete | Status | Completed
|
|
const roadmap = [
|
|
'# Roadmap',
|
|
'',
|
|
'- [ ] Phase 01: Foundation',
|
|
'- [ ] Phase 02: API',
|
|
'',
|
|
'### Phase 01: Foundation',
|
|
'**Goal:** Build the foundation',
|
|
'**Requirements:** REQ-1',
|
|
'**Plans:** 1 plans',
|
|
'',
|
|
'### Phase 02: API',
|
|
'**Goal:** Build the API',
|
|
'',
|
|
'## Progress',
|
|
'',
|
|
'| Phase | Plans Complete | Status | Completed |',
|
|
'|-------|----------------|--------|-----------|',
|
|
'| 01. Foundation | 0/1 | Not started | - |',
|
|
'| 02. API | 0/1 | Not started | - |',
|
|
'',
|
|
].join('\n');
|
|
fs.writeFileSync(path.join(planningDir, 'ROADMAP.md'), roadmap);
|
|
|
|
const requirements = [
|
|
'# Requirements',
|
|
'',
|
|
'## Functional Requirements',
|
|
'',
|
|
'- [ ] **REQ-1** Foundation must be complete.',
|
|
'',
|
|
'## Traceability',
|
|
'',
|
|
'| Requirement | Phase | Status |',
|
|
'|-------------|-------|--------|',
|
|
'| REQ-1 | Phase 01 | Pending |',
|
|
'',
|
|
].join('\n');
|
|
fs.writeFileSync(path.join(planningDir, 'REQUIREMENTS.md'), requirements);
|
|
|
|
// STATE.md: Completed Phases: 0, Total Phases: 2, Progress: 0%
|
|
// Uses body-field format (bold **Field:** value) so the CJS handler's
|
|
// stateExtractField/stateReplaceField path is exercised.
|
|
const state = [
|
|
'# State',
|
|
'',
|
|
'**Current Phase:** 01',
|
|
'**Current Phase Name:** Foundation',
|
|
'**Status:** In progress',
|
|
'**Current Plan:** 01-01',
|
|
'**Last Activity:** 2025-01-01',
|
|
'**Last Activity Description:** Working on phase 1',
|
|
'**Completed Phases:** 0',
|
|
'**Total Phases:** 2',
|
|
'**Progress:** 0%',
|
|
'',
|
|
].join('\n');
|
|
fs.writeFileSync(path.join(planningDir, 'STATE.md'), state);
|
|
|
|
// Phase 01 directory with a PLAN and SUMMARY so phase complete guard passes
|
|
const phase01Dir = path.join(phasesDir, '01-foundation');
|
|
fs.mkdirSync(phase01Dir, { recursive: true });
|
|
fs.writeFileSync(path.join(phase01Dir, '01-01-PLAN.md'), '# Plan 1\nDo the work.\n');
|
|
fs.writeFileSync(path.join(phase01Dir, '01-01-SUMMARY.md'), '# Summary 1\nDone.\n');
|
|
|
|
// Phase 02 directory (needed for "next phase" detection)
|
|
fs.mkdirSync(path.join(phasesDir, '02-api'), { recursive: true });
|
|
|
|
return tmpDir;
|
|
}
|
|
|
|
function readStateMd(tmpDir) {
|
|
return fs.readFileSync(path.join(tmpDir, '.planning', 'STATE.md'), 'utf8');
|
|
}
|
|
|
|
function roadmapCompletionSnapshot(roadmapContent) {
|
|
const snapshot = {
|
|
phaseCheckboxes: [],
|
|
progressRows: [],
|
|
};
|
|
|
|
for (const line of roadmapContent.split(/\r?\n/)) {
|
|
let match = line.match(/^- \[([ x])\] Phase ([^:]+): (.*)$/);
|
|
if (match) {
|
|
snapshot.phaseCheckboxes.push({
|
|
checked: match[1] === 'x',
|
|
phase: match[2].trim(),
|
|
title: match[3].replace(/\s+\(completed [^)]+\)$/, '').trim(),
|
|
});
|
|
continue;
|
|
}
|
|
|
|
match = line.match(/^\|\s*(\d+[A-Z]?(?:\.\d+)*)\.?\s*([^|]*)\|\s*([^|]*)\|\s*([^|]*)\|\s*([^|]*)\|$/i);
|
|
if (match) {
|
|
snapshot.progressRows.push({
|
|
phase: match[1].trim(),
|
|
title: match[2].trim(),
|
|
plans: match[3].trim(),
|
|
status: match[4].trim(),
|
|
completed: match[5].trim(),
|
|
});
|
|
}
|
|
}
|
|
|
|
return snapshot;
|
|
}
|
|
|
|
function extractField(stateContent, fieldName) {
|
|
const escaped = fieldName.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
|
|
const boldMatch = stateContent.match(new RegExp(`\\*\\*${escaped}:\\*\\*[ \\t]*(.+)`, 'i'));
|
|
if (boldMatch) return boldMatch[1].trim();
|
|
const plainMatch = stateContent.match(new RegExp(`^${escaped}:[ \\t]*(.+)`, 'im'));
|
|
return plainMatch ? plainMatch[1].trim() : null;
|
|
}
|
|
|
|
function extractFrontmatterField(stateContent, fieldName) {
|
|
// Extract from YAML frontmatter block
|
|
const fmMatch = stateContent.match(/^---\r?\n([\s\S]*?)\r?\n---/);
|
|
if (!fmMatch) return null;
|
|
const fm = fmMatch[1];
|
|
// Handle both scalar and nested (progress.completed_phases)
|
|
const parts = fieldName.split('.');
|
|
if (parts.length === 1) {
|
|
const m = fm.match(new RegExp(`^${parts[0]}:\\s*(.+)`, 'm'));
|
|
return m ? m[1].trim() : null;
|
|
}
|
|
// Nested: e.g. "progress.completed_phases"
|
|
const sectionMatch = fm.match(new RegExp(`^${parts[0]}:\\s*\\n([\\s\\S]*?)(?=\\n[a-z]|$)`, 'm'));
|
|
if (!sectionMatch) return null;
|
|
const sectionContent = sectionMatch[1];
|
|
const fieldMatch = sectionContent.match(new RegExp(`^\\s+${parts[1]}:\\s*(.+)`, 'm'));
|
|
return fieldMatch ? fieldMatch[1].trim() : null;
|
|
}
|
|
|
|
// Capture stdout from cmdPhaseComplete (it calls output() which writes to stdout)
|
|
function capturePhaseComplete(cwd, phaseNum) {
|
|
const { execFileSync } = require('child_process');
|
|
const TOOLS = path.join(__dirname, '..', 'gsd-core', 'bin', 'gsd-tools.cjs');
|
|
// We invoke gsd-tools directly for the full CJS path, but with GSD_DISABLE_SDK_BRIDGE=1
|
|
// to force the CJS implementation. Since no env var disables bridge, we call cmdPhaseComplete
|
|
// directly and redirect output capture.
|
|
const chunks = [];
|
|
const origWrite = process.stdout.write.bind(process.stdout);
|
|
process.stdout.write = (chunk) => { chunks.push(chunk); return true; };
|
|
try {
|
|
cmdPhaseComplete(cwd, phaseNum, false);
|
|
} finally {
|
|
process.stdout.write = origWrite;
|
|
}
|
|
return chunks.join('');
|
|
}
|
|
|
|
// ── T1: Double invocation must NOT double-increment Completed Phases ─────────
|
|
|
|
describe('issue #4 (CJS): cmdPhaseComplete — idempotency (blind-increment bug)', () => {
|
|
let tmpDir;
|
|
|
|
beforeEach(() => {
|
|
tmpDir = createFixture();
|
|
});
|
|
|
|
afterEach(() => {
|
|
cleanup(tmpDir);
|
|
});
|
|
|
|
test('T1: double invocation does NOT double-increment Completed Phases in STATE.md body', () => {
|
|
// First call — legitimate completion
|
|
capturePhaseComplete(tmpDir, '1');
|
|
|
|
const stateAfter1 = readStateMd(tmpDir);
|
|
const completedAfter1Body = extractField(stateAfter1, 'Completed Phases');
|
|
const completedAfter1Fm = extractFrontmatterField(stateAfter1, 'progress.completed_phases');
|
|
// After first call: Completed Phases in the body should be 1
|
|
// (derived from ROADMAP: 1 Complete row after marking phase 01 complete)
|
|
// OR the YAML frontmatter completed_phases should be 1
|
|
const completedAfter1 = completedAfter1Body || completedAfter1Fm;
|
|
assert.equal(
|
|
completedAfter1,
|
|
'1',
|
|
`After first call: completed_phases should be 1.\n` +
|
|
`Body field: ${completedAfter1Body}, FM field: ${completedAfter1Fm}\n\n` +
|
|
`STATE:\n${stateAfter1}`,
|
|
);
|
|
|
|
// Second call on the same phase — must be idempotent
|
|
capturePhaseComplete(tmpDir, '1');
|
|
|
|
const stateAfter2 = readStateMd(tmpDir);
|
|
const completedAfter2Body = extractField(stateAfter2, 'Completed Phases');
|
|
const completedAfter2Fm = extractFrontmatterField(stateAfter2, 'progress.completed_phases');
|
|
const completedAfter2 = completedAfter2Body || completedAfter2Fm;
|
|
|
|
// Pre-fix: completedAfter2 would be "2" (blind increment: 1+1=2)
|
|
// Post-fix: must remain "1" (derived from ROADMAP)
|
|
assert.equal(
|
|
completedAfter2,
|
|
'1',
|
|
`T1 FAILED: Completed Phases was double-incremented.\n` +
|
|
`After first call: ${completedAfter1}, after second call: ${completedAfter2}.\n` +
|
|
`This is the #4 non-idempotency bug — blind parseInt+1 instead of deriving from ROADMAP.\n\n` +
|
|
`STATE after second call (body: ${completedAfter2Body}, fm: ${completedAfter2Fm}):\n${stateAfter2}`,
|
|
);
|
|
});
|
|
|
|
test('rolls back ROADMAP when STATE write fails during phase completion', (t) => {
|
|
const roadmapPath = path.join(tmpDir, '.planning', 'ROADMAP.md');
|
|
const reqPath = path.join(tmpDir, '.planning', 'REQUIREMENTS.md');
|
|
const statePath = path.join(tmpDir, '.planning', 'STATE.md');
|
|
const originalRoadmap = fs.readFileSync(roadmapPath, 'utf8');
|
|
const originalReq = fs.readFileSync(reqPath, 'utf8');
|
|
const originalState = fs.readFileSync(statePath, 'utf8');
|
|
const originalWriteFileSync = fs.writeFileSync;
|
|
|
|
t.mock.method(fs, 'writeFileSync', function injectedStateWriteFailure(target, ...args) {
|
|
const targetPath = String(target);
|
|
const isStatePublish = targetPath === statePath || targetPath === `${statePath}.tmp.${process.pid}`;
|
|
if (isStatePublish) {
|
|
const err = new Error('injected STATE.md write failure');
|
|
err.code = 'EIO';
|
|
throw err;
|
|
}
|
|
return originalWriteFileSync.call(this, target, ...args);
|
|
});
|
|
|
|
assert.throws(
|
|
() => capturePhaseComplete(tmpDir, '1'),
|
|
/injected STATE\.md write failure/,
|
|
);
|
|
|
|
const roadmapAfter = fs.readFileSync(roadmapPath, 'utf8');
|
|
const reqAfter = fs.readFileSync(reqPath, 'utf8');
|
|
const stateAfter = fs.readFileSync(statePath, 'utf8');
|
|
|
|
assert.deepEqual(
|
|
roadmapCompletionSnapshot(roadmapAfter),
|
|
roadmapCompletionSnapshot(originalRoadmap),
|
|
'ROADMAP.md should roll back to its original completion state',
|
|
);
|
|
assert.equal(reqAfter, originalReq, 'REQUIREMENTS.md should roll back when STATE.md write fails');
|
|
assert.equal(stateAfter, originalState, 'STATE.md should remain unchanged after injected write failure');
|
|
});
|
|
|
|
test('rolls back ROADMAP when REQUIREMENTS write fails during phase completion', (t) => {
|
|
const roadmapPath = path.join(tmpDir, '.planning', 'ROADMAP.md');
|
|
const reqPath = path.join(tmpDir, '.planning', 'REQUIREMENTS.md');
|
|
const originalRoadmap = fs.readFileSync(roadmapPath, 'utf8');
|
|
const originalReq = fs.readFileSync(reqPath, 'utf8');
|
|
const originalWriteFileSync = fs.writeFileSync;
|
|
|
|
t.mock.method(fs, 'writeFileSync', function injectedRequirementsWriteFailure(target, ...args) {
|
|
const targetPath = String(target);
|
|
if (targetPath === reqPath || targetPath === `${reqPath}.tmp.${process.pid}`) {
|
|
const err = new Error('injected REQUIREMENTS.md write failure');
|
|
err.code = 'EIO';
|
|
throw err;
|
|
}
|
|
return originalWriteFileSync.call(this, target, ...args);
|
|
});
|
|
|
|
assert.throws(
|
|
() => capturePhaseComplete(tmpDir, '1'),
|
|
/injected REQUIREMENTS\.md write failure/,
|
|
);
|
|
|
|
assert.deepEqual(
|
|
roadmapCompletionSnapshot(fs.readFileSync(roadmapPath, 'utf8')),
|
|
roadmapCompletionSnapshot(originalRoadmap),
|
|
'ROADMAP.md should roll back when the REQUIREMENTS write fails',
|
|
);
|
|
assert.equal(fs.readFileSync(reqPath, 'utf8'), originalReq, 'REQUIREMENTS.md should be unchanged');
|
|
});
|
|
|
|
test('reports rollback failure when restoring an earlier planning file fails', (t) => {
|
|
const roadmapPath = path.join(tmpDir, '.planning', 'ROADMAP.md');
|
|
const reqPath = path.join(tmpDir, '.planning', 'REQUIREMENTS.md');
|
|
const originalWriteFileSync = fs.writeFileSync;
|
|
let requirementsWriteFailed = false;
|
|
|
|
t.mock.method(fs, 'writeFileSync', function injectedRollbackFailure(target, ...args) {
|
|
const targetPath = String(target);
|
|
if (targetPath === reqPath || targetPath === `${reqPath}.tmp.${process.pid}`) {
|
|
requirementsWriteFailed = true;
|
|
const err = new Error('injected REQUIREMENTS.md write failure');
|
|
err.code = 'EIO';
|
|
throw err;
|
|
}
|
|
if (requirementsWriteFailed && (targetPath === roadmapPath || targetPath === `${roadmapPath}.tmp.${process.pid}`)) {
|
|
const err = new Error('injected ROADMAP.md rollback failure');
|
|
err.code = 'EIO';
|
|
throw err;
|
|
}
|
|
return originalWriteFileSync.call(this, target, ...args);
|
|
});
|
|
|
|
assert.throws(
|
|
() => capturePhaseComplete(tmpDir, '1'),
|
|
/injected REQUIREMENTS\.md write failure[\s\S]*WARNING: rollback failed while restoring[\s\S]*injected ROADMAP\.md rollback failure/,
|
|
);
|
|
});
|
|
});
|
|
|
|
// ── T2: Progress percent must never exceed 100% ──────────────────────────────
|
|
|
|
describe('issue #4 (CJS): cmdPhaseComplete — progress percent clamp', () => {
|
|
let tmpDir;
|
|
|
|
afterEach(() => {
|
|
cleanup(tmpDir);
|
|
});
|
|
|
|
test('T2: Progress percent never exceeds 100 after double invocation', () => {
|
|
tmpDir = createFixture();
|
|
|
|
// Pre-load STATE.md with Completed Phases: 1, Total Phases: 1 (already 100%)
|
|
// so that a blind +1 on a second call would yield 200%
|
|
let stateContent = readStateMd(tmpDir);
|
|
stateContent = stateContent.replace('**Completed Phases:** 0', '**Completed Phases:** 1');
|
|
stateContent = stateContent.replace('**Total Phases:** 2', '**Total Phases:** 1');
|
|
stateContent = stateContent.replace('**Progress:** 0%', '**Progress:** 100%');
|
|
fs.writeFileSync(path.join(tmpDir, '.planning', 'STATE.md'), stateContent);
|
|
|
|
// Also update ROADMAP to show just 1 phase total
|
|
const roadmap = [
|
|
'# Roadmap',
|
|
'',
|
|
'- [ ] Phase 01: Foundation',
|
|
'',
|
|
'### Phase 01: Foundation',
|
|
'**Goal:** Build the foundation',
|
|
'**Plans:** 1 plans',
|
|
'',
|
|
'## Progress',
|
|
'',
|
|
'| Phase | Plans Complete | Status | Completed |',
|
|
'|-------|----------------|--------|-----------|',
|
|
'| 01. Foundation | 0/1 | Not started | - |',
|
|
'',
|
|
].join('\n');
|
|
fs.writeFileSync(path.join(tmpDir, '.planning', 'ROADMAP.md'), roadmap);
|
|
|
|
// First call
|
|
capturePhaseComplete(tmpDir, '1');
|
|
// Second call — this is the problematic one
|
|
capturePhaseComplete(tmpDir, '1');
|
|
|
|
const stateAfterBoth = readStateMd(tmpDir);
|
|
|
|
// Check body Progress field
|
|
const progressStr = extractField(stateAfterBoth, 'Progress');
|
|
const fmPercent = extractFrontmatterField(stateAfterBoth, 'progress.percent');
|
|
|
|
// Try to extract numeric percent from either source
|
|
const bodyPercentMatch = progressStr && progressStr.match(/(\d+)%/);
|
|
const bodyPercent = bodyPercentMatch ? parseInt(bodyPercentMatch[1], 10) : null;
|
|
const fmPercentNum = fmPercent ? parseInt(fmPercent, 10) : null;
|
|
|
|
// At least one of body or frontmatter percent must exist and be ≤ 100
|
|
const anyPercent = bodyPercent ?? fmPercentNum;
|
|
assert.ok(
|
|
anyPercent !== null,
|
|
`T2: Could not find any percent value in STATE.md\n\nSTATE:\n${stateAfterBoth}`,
|
|
);
|
|
assert.ok(
|
|
anyPercent <= 100,
|
|
`T2 FAILED: Progress percent exceeds 100.\n` +
|
|
`Body Progress: "${progressStr}" (${bodyPercent}%), FM percent: ${fmPercentNum}%\n` +
|
|
`This is the #4 unclamped-percent bug — (N+1)/total can exceed 100.\n\n` +
|
|
`STATE:\n${stateAfterBoth}`,
|
|
);
|
|
});
|
|
});
|