* 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>
275 lines
12 KiB
JavaScript
275 lines
12 KiB
JavaScript
/**
|
|
* Regression test for perf #316 — acquireStateLock allocates a fresh
|
|
* SharedArrayBuffer on every retry iteration.
|
|
*
|
|
* The fix: hoist the sleep buffer allocation to once before the retry loop.
|
|
* The buffer is never mutated and never escapes — Atomics.wait(buf,0,0,delay)
|
|
* always sees 0 whether the buffer is fresh or reused, so the behavior is
|
|
* identical.
|
|
*
|
|
* Observable invariant (POST-FIX): exactly ONE SharedArrayBuffer is allocated
|
|
* per acquireStateLock call, regardless of retry count.
|
|
*
|
|
* RED (pre-fix): sabCount >= 2 when >= 1 retry occurs.
|
|
* GREEN (post-fix): sabCount === 1.
|
|
*
|
|
* Strategy: two Worker threads run in parallel.
|
|
* Worker A (lock holder): writes the lock file with the current process pid,
|
|
* sleeps 400ms via Atomics.wait, then removes the lock.
|
|
* Worker B (writer): installs a counting SharedArrayBuffer stub, then calls
|
|
* writeStateMd — which calls acquireStateLock and retries until A releases.
|
|
* Reports sabCount via postMessage.
|
|
*
|
|
* Using Worker threads (not child processes) avoids the node --test subprocess-
|
|
* detection hang that occurs with spawn() inside a test runner worker context.
|
|
*
|
|
* Total test wall-time: ~400-600ms.
|
|
*/
|
|
|
|
const { test, describe, beforeEach, afterEach } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
const os = require('os');
|
|
const { Worker } = require('worker_threads');
|
|
const { cleanup } = require('./helpers.cjs');
|
|
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
// Constants
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
|
|
const STATE_CJS_PATH = path.join(
|
|
__dirname, '..', 'gsd-core', 'bin', 'lib', 'state.cjs'
|
|
);
|
|
|
|
const MINIMAL_STATE_MD = [
|
|
'# Project State',
|
|
'',
|
|
'**Status:** Planning',
|
|
'**Current Phase:** 01',
|
|
].join('\n') + '\n';
|
|
|
|
// Worker A: holds the lock file for holdMs, then removes it.
|
|
// workerData: { lockPath, holdMs }
|
|
const HOLDER_WORKER_CODE = `
|
|
const { parentPort, workerData } = require('worker_threads');
|
|
const fs = require('fs');
|
|
// Write pid to lock file so acquireStateLock sees a live pid and retries.
|
|
fs.writeFileSync(workerData.lockPath, String(process.pid));
|
|
parentPort.postMessage({ pid: process.pid });
|
|
// Synchronous sleep — blocks this worker thread for holdMs ms.
|
|
const buf = new Int32Array(new SharedArrayBuffer(4));
|
|
Atomics.wait(buf, 0, 0, workerData.holdMs);
|
|
// Release the lock.
|
|
try { fs.unlinkSync(workerData.lockPath); } catch { /* already gone */ }
|
|
parentPort.postMessage({ done: true });
|
|
`;
|
|
|
|
// Worker B: stubs global.SharedArrayBuffer with a counting call-through wrapper,
|
|
// then calls writeStateMd (triggering acquireStateLock), and reports sabCount.
|
|
// workerData: { stateCjsPath, statePath, content, tmpDir }
|
|
const WRITER_WORKER_CODE = `
|
|
const { parentPort, workerData } = require('worker_threads');
|
|
const fs = require('fs');
|
|
const RealSAB = global.SharedArrayBuffer;
|
|
let sabCount = 0;
|
|
// Stub: increments sabCount, calls through so Atomics.wait gets a real SAB-backed buffer.
|
|
function StubSAB(...args) {
|
|
sabCount++;
|
|
return new RealSAB(...args);
|
|
}
|
|
StubSAB.prototype = RealSAB.prototype;
|
|
global.SharedArrayBuffer = StubSAB;
|
|
|
|
// Lock-attempt counter: stubs fs.openSync to count atomic-create attempts
|
|
// (state.cjs's acquireStateLock uses fs.openSync(..., O_CREAT|O_EXCL|O_WRONLY)
|
|
// to atomically create the lock file). Each call with O_CREAT|O_EXCL flags
|
|
// is one retry-loop iteration. >=2 attempts proves the SUT entered the retry
|
|
// path — without this witness, a no-retry success would yield sabCount === 1
|
|
// from BOTH pre-fix and post-fix code (the SAB is allocated unconditionally
|
|
// post-fix, and exactly once for the single successful open pre-fix), giving
|
|
// a false-pass against the bug. The 1000ms holdMs + 200ms SUT retry delay
|
|
// guarantees >=4 attempts even on the slowest CI runners.
|
|
const realOpenSync = fs.openSync.bind(fs);
|
|
let lockAttempts = 0;
|
|
fs.openSync = function(filePath, flags, mode) {
|
|
if (typeof filePath === 'string' && filePath.endsWith('.lock') &&
|
|
typeof flags === 'number' &&
|
|
(flags & fs.constants.O_CREAT) && (flags & fs.constants.O_EXCL)) {
|
|
lockAttempts++;
|
|
}
|
|
return realOpenSync(filePath, flags, mode);
|
|
};
|
|
|
|
// Delete cache entry to ensure a fresh require picks up the stubbed constructor.
|
|
// (The inline "new SharedArrayBuffer(4)" in acquireStateLock reads the global at
|
|
// call time, so even a cached require would use our stub — but deleting avoids
|
|
// any module-level SAB allocations from a prior require contaminating sabCount.)
|
|
delete require.cache[workerData.stateCjsPath];
|
|
const { writeStateMd } = require(workerData.stateCjsPath);
|
|
|
|
let callErr = null;
|
|
try {
|
|
writeStateMd(workerData.statePath, workerData.content, workerData.tmpDir);
|
|
} catch (e) {
|
|
callErr = (e && e.message) ? e.message : String(e);
|
|
}
|
|
parentPort.postMessage({ sabCount, lockAttempts, callErr });
|
|
`;
|
|
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
// Helpers
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
|
|
function makeTempDir() {
|
|
const dir = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-316-'));
|
|
fs.mkdirSync(path.join(dir, '.planning'), { recursive: true });
|
|
return dir;
|
|
}
|
|
|
|
function removeTempDir(dir) {
|
|
try { cleanup(dir); } catch { /* ignore */ }
|
|
}
|
|
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
// Test
|
|
// ─────────────────────────────────────────────────────────────────────────────
|
|
|
|
describe('perf #316: acquireStateLock hoists sleep buffer — exactly one SAB per call', () => {
|
|
let tmpDir;
|
|
let statePath;
|
|
let lockPath;
|
|
|
|
beforeEach(() => {
|
|
tmpDir = makeTempDir();
|
|
statePath = path.join(tmpDir, '.planning', 'STATE.md');
|
|
lockPath = statePath + '.lock';
|
|
fs.writeFileSync(statePath, MINIMAL_STATE_MD, 'utf-8');
|
|
});
|
|
|
|
afterEach(() => {
|
|
try { fs.unlinkSync(lockPath); } catch { /* already gone */ }
|
|
removeTempDir(tmpDir);
|
|
});
|
|
|
|
test(
|
|
'sabCount === 1 after a call that undergoes >= 1 retry (post-fix assertion)',
|
|
{ timeout: 8000 },
|
|
async () => {
|
|
// ── Worker A: hold the lock for 1000ms ─────────────────────────────────
|
|
// state.cjs retry delay = 200ms + 0-50ms jitter; 1000ms hold guarantees
|
|
// >=4 retries even on the slowest CI worker (~200ms spawn + 4 retry
|
|
// intervals ~1000ms ≈ hold duration). The lockAttempts assertion below
|
|
// proves the retry path was exercised end-to-end.
|
|
const holdMs = 1000;
|
|
let holderWorker;
|
|
let resolveLockWritten;
|
|
const lockWritten = new Promise((resolve) => { resolveLockWritten = resolve; });
|
|
const holderDone = new Promise((resolve, reject) => {
|
|
holderWorker = new Worker(HOLDER_WORKER_CODE, {
|
|
eval: true,
|
|
workerData: { lockPath, holdMs },
|
|
});
|
|
holderWorker.on('message', (msg) => {
|
|
if (msg.pid !== undefined) resolveLockWritten();
|
|
if (msg.done) resolve();
|
|
});
|
|
holderWorker.on('error', (err) => {
|
|
resolveLockWritten(); // unblock so the assert below fires immediately
|
|
reject(err);
|
|
});
|
|
holderWorker.on('exit', (code) => {
|
|
resolveLockWritten(); // unblock if Worker A exits before posting
|
|
if (code !== 0) reject(new Error('Holder worker exit code: ' + code));
|
|
});
|
|
});
|
|
// Suppress unhandled-rejection warnings on holderDone — we always observe
|
|
// it later via `await holderDone`, which re-throws the original error.
|
|
holderDone.catch(() => {});
|
|
|
|
// Deterministic synchronization: await Worker A's {pid} message, which
|
|
// it posts AFTER fs.writeFileSync returns (single-thread source order
|
|
// within the worker). By the time the parent receives this message,
|
|
// the lock file exists on disk and is visible across threads (workers
|
|
// share the same OS file table). The MessagePort buffers messages
|
|
// posted before the listener attaches, so there is no listener-race.
|
|
// Ref: https://nodejs.org/api/worker_threads.html#event-message_1
|
|
// The 5000ms safety timeout catches a hung holder; nominal latency <50ms.
|
|
let lockWrittenTimer;
|
|
const lockWrittenTimeout = new Promise((_, reject) => {
|
|
lockWrittenTimer = setTimeout(
|
|
() => reject(new Error('Holder worker did not post pid within 5000ms')),
|
|
5000
|
|
);
|
|
});
|
|
try {
|
|
await Promise.race([lockWritten, lockWrittenTimeout]);
|
|
} finally {
|
|
clearTimeout(lockWrittenTimer);
|
|
}
|
|
assert.ok(fs.existsSync(lockPath), 'Worker A must have written the lock file');
|
|
|
|
// ── Worker B: call writeStateMd, measure SAB allocations ───────────────
|
|
const writeResult = await new Promise((resolve, reject) => {
|
|
const writer = new Worker(WRITER_WORKER_CODE, {
|
|
eval: true,
|
|
workerData: {
|
|
stateCjsPath: STATE_CJS_PATH,
|
|
statePath,
|
|
content: MINIMAL_STATE_MD,
|
|
tmpDir,
|
|
},
|
|
});
|
|
writer.on('message', resolve);
|
|
writer.on('error', reject);
|
|
writer.on('exit', (code) => {
|
|
if (code !== 0) reject(new Error('Writer worker exit code: ' + code));
|
|
});
|
|
});
|
|
|
|
// Wait for Worker A to finish releasing
|
|
await holderDone;
|
|
|
|
// ── Assertions ─────────────────────────────────────────────────────────
|
|
assert.ok(
|
|
writeResult.callErr === null,
|
|
'writeStateMd must succeed once the lock is released — error: ' + writeResult.callErr
|
|
);
|
|
|
|
assert.ok(
|
|
writeResult.sabCount >= 1,
|
|
'at least one SharedArrayBuffer must be allocated (the sleep buffer must exist)'
|
|
);
|
|
|
|
// PROOF OF RETRY-PATH COVERAGE (Contract 4 of test-rigor):
|
|
// The sabCount === 1 invariant below only discriminates pre-fix from
|
|
// post-fix when the SUT actually entered the retry loop. Without this
|
|
// witness, a no-retry success path yields sabCount === 1 under BOTH
|
|
// pre-fix and post-fix code (one SAB for the single successful open).
|
|
// lockAttempts counts atomic-create attempts (fs.openSync with
|
|
// O_CREAT|O_EXCL); >=2 means at least one failed-then-retried.
|
|
assert.ok(
|
|
writeResult.lockAttempts >= 2,
|
|
'SUT must have entered the retry path (>=1 failed lock attempt before success). ' +
|
|
'Got lockAttempts: ' + writeResult.lockAttempts + '. The 1000ms holdMs + 200ms ' +
|
|
'SUT retry delay guarantees >=2 attempts on any CI runner.'
|
|
);
|
|
|
|
// THE KEY INVARIANT:
|
|
// POST-FIX: sabCount === 1 (buffer allocated once, before the retry loop)
|
|
// PRE-FIX: sabCount === lockAttempts (new buffer on EVERY iteration,
|
|
// both successful and failed)
|
|
// Combined with lockAttempts >= 2 above, sabCount === 1 strictly proves
|
|
// the buffer is hoisted (post-fix). Pre-fix code would observe sabCount
|
|
// equal to the iteration count, never 1.
|
|
assert.strictEqual(
|
|
writeResult.sabCount,
|
|
1,
|
|
'post-fix: exactly one SharedArrayBuffer must be allocated per acquireStateLock call ' +
|
|
'(buffer hoisted before retry loop). Got: ' + writeResult.sabCount +
|
|
' across ' + writeResult.lockAttempts + ' lock attempts.'
|
|
);
|
|
}
|
|
);
|
|
});
|