* 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>
279 lines
12 KiB
JavaScript
279 lines
12 KiB
JavaScript
// allow-test-rule: source-text-is-the-product
|
|
// STATE.md is the product surface; assertions on its text content test the
|
|
// deployed contract (date field written by the subprocess SUT).
|
|
|
|
'use strict';
|
|
|
|
/**
|
|
* Bug #474 — clock seam: subprocess date-stamping must be deterministic.
|
|
*
|
|
* Tests in this file verify that:
|
|
* 1. state.cjs date-stamping is routed through realClock (not bare new Date()),
|
|
* so GSD_NOW_MS pins the written date deterministically in subprocess tests.
|
|
* 2. installer-migrations.cjs lock-loop timeout fires deterministically via
|
|
* the clock seam (in-process, using makeFakeClock — no subprocess needed).
|
|
*/
|
|
|
|
const { describe, it, test, before, after } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
const { runGsdTools, cleanup } = require('./helpers.cjs');
|
|
const { createFixture } = require('./fixtures/index.cjs');
|
|
const { makeFakeClock } = require('./helpers/clock.cjs');
|
|
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
// §1 Subprocess date-pin: state advance-plan writes the pinned date
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
|
|
/**
|
|
* Why advance-plan?
|
|
* cmdStateAdvancePlan captures `const today = new Date().toISOString().split('T')[0]`
|
|
* and writes it to "Last Activity" via stateReplaceFieldIfTemplate.
|
|
* The fixture below has Last Activity = 2024-01-10 (an ISO date, treated as a
|
|
* handler-generated template default by isStateTemplateDefault), so the field IS
|
|
* overwritten — making this the simplest single-subcommand probe of the bug.
|
|
*/
|
|
|
|
// A fixed historical instant far in the past — will NEVER match today's real date.
|
|
const PINNED_MS = Date.parse('2020-06-15T12:00:00.000Z');
|
|
const PINNED_DATE = '2020-06-15';
|
|
|
|
// A minimal STATE.md that satisfies advance-plan's parser:
|
|
// - Current Plan: 1 (not on last plan → normal-advance branch)
|
|
// - Total Plans in Phase: 3
|
|
// - Last Activity: 2024-01-10 (ISO date → isStateTemplateDefault returns true → will be replaced)
|
|
const ADVANCE_FIXTURE = [
|
|
'# Project State',
|
|
'',
|
|
'**Current Plan:** 1',
|
|
'**Total Plans in Phase:** 3',
|
|
'**Status:** Executing',
|
|
'**Last Activity:** 2024-01-10',
|
|
].join('\n') + '\n';
|
|
|
|
describe('bug-474: state date-stamping is pinned by GSD_NOW_MS', () => {
|
|
let tmpDir;
|
|
|
|
before(() => {
|
|
// AAA — Arrange: create a temp project with the advance fixture
|
|
tmpDir = createFixture();
|
|
fs.writeFileSync(path.join(tmpDir, '.planning', 'STATE.md'), ADVANCE_FIXTURE);
|
|
});
|
|
|
|
after(() => {
|
|
cleanup(tmpDir);
|
|
});
|
|
|
|
test('state advance-plan writes pinned date (not real today) when GSD_NOW_MS is set', () => {
|
|
// AAA — Act: run advance-plan with a pinned historical timestamp
|
|
const result = runGsdTools('state advance-plan', tmpDir, {
|
|
GSD_TEST_MODE: '1',
|
|
GSD_NOW_MS: String(PINNED_MS),
|
|
});
|
|
|
|
assert.ok(result.success, `advance-plan failed unexpectedly: ${result.error}`);
|
|
|
|
// AAA — Assert: the written STATE.md must contain the pinned date
|
|
const written = fs.readFileSync(path.join(tmpDir, '.planning', 'STATE.md'), 'utf-8');
|
|
|
|
// Must contain the pinned historical date (2020-06-15)
|
|
assert.ok(
|
|
written.includes(PINNED_DATE),
|
|
`Expected STATE.md to contain pinned date ${PINNED_DATE}.\nActual STATE.md:\n${written}`,
|
|
);
|
|
|
|
// Must NOT contain today's real date — that would mean the seam is bypassed
|
|
const realToday = new Date().toISOString().split('T')[0];
|
|
assert.ok(
|
|
!written.includes(realToday),
|
|
`Expected STATE.md NOT to contain real today (${realToday}) when time is pinned.\nActual STATE.md:\n${written}`,
|
|
);
|
|
});
|
|
});
|
|
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
// §2 realClock GSD_NOW_MS invalid-input hardening
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
|
|
/**
|
|
* Verify that malformed / out-of-range GSD_NOW_MS values fall back to the real
|
|
* clock instead of crashing with RangeError (issue #474 hardening).
|
|
*
|
|
* Each invalid input must:
|
|
* a) not throw from realClock.nowIso(), and
|
|
* b) produce a valid parseable ISO string (i.e. fell back to Date.now()).
|
|
*
|
|
* A valid pinned value must produce the expected date string.
|
|
*/
|
|
|
|
describe('bug-474: realClock GSD_NOW_MS invalid-input hardening', () => {
|
|
const realClock = require('../gsd-core/bin/lib/clock.cjs').realClock;
|
|
|
|
// Save and restore env so these tests cannot bleed into neighbouring tests.
|
|
let savedTestMode;
|
|
let savedNowMs;
|
|
|
|
before(() => {
|
|
savedTestMode = process.env.GSD_TEST_MODE;
|
|
savedNowMs = process.env.GSD_NOW_MS;
|
|
process.env.GSD_TEST_MODE = '1';
|
|
});
|
|
|
|
after(() => {
|
|
if (savedTestMode === undefined) {
|
|
delete process.env.GSD_TEST_MODE;
|
|
} else {
|
|
process.env.GSD_TEST_MODE = savedTestMode;
|
|
}
|
|
if (savedNowMs === undefined) {
|
|
delete process.env.GSD_NOW_MS;
|
|
} else {
|
|
process.env.GSD_NOW_MS = savedNowMs;
|
|
}
|
|
});
|
|
|
|
// AAA matrix: each invalid value must NOT crash and must fall back to the real clock.
|
|
const INVALID_INPUTS = [
|
|
['empty string', ''],
|
|
['whitespace only', ' '],
|
|
['alphabetic', 'abc'],
|
|
['scientific notation', '1e30'],
|
|
['decimal float', '12.5'],
|
|
['integer > 8.64e15', '99999999999999999999'],
|
|
];
|
|
|
|
for (const [label, value] of INVALID_INPUTS) {
|
|
test(`GSD_NOW_MS='${value}' (${label}) falls back to real clock — no crash, valid ISO`, () => {
|
|
// AAA — Arrange
|
|
process.env.GSD_NOW_MS = value;
|
|
|
|
// AAA — Act + Assert: must not throw
|
|
assert.doesNotThrow(
|
|
() => realClock.nowIso(),
|
|
`realClock.nowIso() must not throw for GSD_NOW_MS='${value}'`,
|
|
);
|
|
|
|
// AAA — Assert: result is a valid ISO string (fell back to real clock)
|
|
const iso = realClock.nowIso();
|
|
assert.ok(
|
|
!Number.isNaN(Date.parse(iso)),
|
|
`realClock.nowIso() must return a valid ISO date for GSD_NOW_MS='${value}', got: ${iso}`,
|
|
);
|
|
});
|
|
}
|
|
|
|
test('GSD_NOW_MS valid decimal integer pins the clock', () => {
|
|
// AAA — Arrange: a known historical epoch
|
|
process.env.GSD_NOW_MS = String(PINNED_MS);
|
|
|
|
// AAA — Act
|
|
const tod = realClock.today();
|
|
|
|
// AAA — Assert
|
|
assert.strictEqual(tod, PINNED_DATE, `realClock.today() must return pinned date ${PINNED_DATE}`);
|
|
});
|
|
});
|
|
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
// §3 In-process lock-loop: installer-migrations timeout fires deterministically
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
|
|
/**
|
|
* This test exercises acquireInstallMigrationLock's EEXIST retry loop via a
|
|
* makeFakeClock. The approach:
|
|
* - Write a lock file held by PID 1 (init/launchd — always alive on any OS)
|
|
* so neither isSameProcess nor isDeadProcess is true; stale-lock reclamation
|
|
* is NOT triggered, and the loop must reach the timeout check.
|
|
* - Use TIMEOUT_MS = 500 (non-zero) so the loop must retry at least once before
|
|
* the injected clock trips the deadline. A zero timeout would fire on the
|
|
* very first check without exercising clock.sleep() at all.
|
|
* - The fake clock's sleep(ms) ADVANCES its internal now by ms (confirmed from
|
|
* helpers/clock.cjs implementation), so the loop drives itself to termination
|
|
* purely through the injected clock without any wall-clock delay.
|
|
* - Post-throw assertions on clock.sleepCalls and clock.now() prove the seam:
|
|
* if the loop reverted to raw Date.now()/sleepSync, sleepCalls would be 0.
|
|
*/
|
|
|
|
describe('bug-474: installer-migrations lock-loop timeout is deterministic via clock seam', () => {
|
|
test('makeFakeClock nowIso() and today() derive from pinned now()', () => {
|
|
// AAA — Arrange
|
|
const clock = makeFakeClock(PINNED_MS);
|
|
|
|
// AAA — Act
|
|
const iso = clock.nowIso();
|
|
const tod = clock.today();
|
|
|
|
// AAA — Assert
|
|
assert.strictEqual(iso, '2020-06-15T12:00:00.000Z', 'nowIso() must return ISO string of pinned epoch');
|
|
assert.strictEqual(tod, PINNED_DATE, 'today() must return YYYY-MM-DD of pinned epoch');
|
|
});
|
|
|
|
test('makeFakeClock advance() shifts nowIso() and today()', () => {
|
|
// AAA — Arrange: start at PINNED_MS, advance by 24 h
|
|
const clock = makeFakeClock(PINNED_MS);
|
|
const ONE_DAY_MS = 24 * 60 * 60 * 1000;
|
|
|
|
// AAA — Act
|
|
clock.advance(ONE_DAY_MS);
|
|
|
|
// AAA — Assert
|
|
assert.strictEqual(clock.today(), '2020-06-16', 'today() must reflect advanced time');
|
|
});
|
|
|
|
test('acquireInstallMigrationLock timeout path fires deterministically via makeFakeClock', (t) => {
|
|
// AAA — Arrange
|
|
const os = require('os');
|
|
const { acquireInstallMigrationLock } = require('../gsd-core/bin/lib/installer-migrations.cjs');
|
|
const configDir = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-474-lock-'));
|
|
|
|
t.after(() => {
|
|
cleanup(configDir);
|
|
});
|
|
|
|
const LOCK_NAME = 'gsd-install-migration.lock';
|
|
const lockPath = path.join(configDir, LOCK_NAME);
|
|
|
|
// Write a lock file held by process.ppid (the parent process, always alive
|
|
// and never equal to process.pid on every platform). pid 1 was used
|
|
// previously but isPidAlive(1) returns false on Windows (no init/launchd
|
|
// pid-1 concept), so the lock was treated as stale, reclaimed, and
|
|
// acquireInstallMigrationLock succeeded instead of throwing — failing the
|
|
// timeout assertion on windows-latest,22 (#474). process.ppid is a live,
|
|
// non-self process on all platforms, so the lock is correctly seen as held
|
|
// and the timeout path throws deterministically cross-platform.
|
|
fs.writeFileSync(
|
|
lockPath,
|
|
JSON.stringify({ pid: process.ppid, acquiredAt: new Date().toISOString() }) + '\n',
|
|
);
|
|
|
|
// TIMEOUT_MS is non-zero so the first EEXIST iteration does NOT immediately
|
|
// trip the deadline. The loop must call clock.sleep() at least once; that
|
|
// sleep() advances the fake clock past TIMEOUT_MS, causing the next check to
|
|
// throw. This proves the seam: if the loop used raw Date.now()/sleepSync,
|
|
// clock.sleepCalls would remain 0.
|
|
const TIMEOUT_MS = 500;
|
|
const clock = makeFakeClock(0);
|
|
|
|
// AAA — Act + Assert: timeout error thrown with no real wall-clock delay
|
|
assert.throws(
|
|
() => acquireInstallMigrationLock(configDir, { timeoutMs: TIMEOUT_MS }, clock),
|
|
/lock|held/i,
|
|
'Expected acquireInstallMigrationLock to throw with "lock"/"held" in message on timeout',
|
|
);
|
|
|
|
// AAA — Assert seam was actually exercised through the injected clock:
|
|
// If the loop used raw sleepSync instead of clock.sleep(), sleepCalls would be 0.
|
|
assert.ok(
|
|
clock.sleepCalls.length > 0,
|
|
'loop must retry via injected clock.sleep() — proves seam wiring, not raw wall clock',
|
|
);
|
|
|
|
// The injected clock must have advanced past TIMEOUT_MS through its own sleep() calls.
|
|
assert.ok(
|
|
clock.now() >= TIMEOUT_MS,
|
|
`injected clock advanced past timeout deterministically: clock.now()=${clock.now()} must be >= TIMEOUT_MS=${TIMEOUT_MS}`,
|
|
);
|
|
});
|
|
});
|