Files
msd-core/tests/perf-407-planning-lock-buffer-alloc.test.cjs
Tom Boucher 463cffd894 chore(#604): rename get-shit-done/ runtime directory to gsd-core/ (#615)
* 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>
2026-06-02 18:35:29 -04:00

210 lines
9.2 KiB
JavaScript

/**
* Regression test for perf #407 — withPlanningLock 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 withPlanningLock call, regardless of retry count.
*
* RED (pre-fix): sabCount >= 2 when >= 1 retry occurs.
* GREEN (post-fix): sabCount === 1.
*
* Strategy: deterministic clock-seam approach (no real workers, no wall-clock).
* 1. Spy on the SharedArrayBuffer constructor BEFORE requiring the module
* (clock.cjs allocates its module-level _realSleepBuf at load time).
* 2. Pre-create the lock file so the first acquire attempt sees EEXIST.
* 3. Inject a fake clock whose sleep() side-effect unlinks the lock file
* after the first call — so attempt #1 sees contention → clock.sleep()
* (which releases the lock) → attempt #2 acquires.
* 4. Assert: fn ran, sleep was called >= 1 time (retry path exercised),
* and sabCount === 1 (the hoist invariant).
*
* This approach is fully synchronous and deterministic: no Atomics.wait, no
* setTimeout, no worker scheduling races, no wall-clock dependence.
*/
'use strict';
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 { cleanup } = require('./helpers.cjs');
// ─────────────────────────────────────────────────────────────────────────────
// Constants
// ─────────────────────────────────────────────────────────────────────────────
const PLANNING_WORKSPACE_CJS_PATH = path.join(
__dirname, '..', 'gsd-core', 'bin', 'lib', 'planning-workspace.cjs'
);
const CLOCK_CJS_PATH = path.join(
__dirname, '..', 'gsd-core', 'bin', 'lib', 'clock.cjs'
);
// ─────────────────────────────────────────────────────────────────────────────
// Helpers
// ─────────────────────────────────────────────────────────────────────────────
function makeTempDir() {
const dir = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-407-'));
fs.mkdirSync(path.join(dir, '.planning'), { recursive: true });
return dir;
}
function removeTempDir(dir) {
try { cleanup(dir); } catch { /* ignore */ }
}
/**
* Install a counting spy on the global SharedArrayBuffer constructor.
* Returns { getCount(), restore() }.
* Must be installed BEFORE requiring any module that allocates SABs at load time.
*/
function spySAB() {
const RealSAB = global.SharedArrayBuffer;
let count = 0;
function SpySAB(...args) {
count++;
return new RealSAB(...args);
}
SpySAB.prototype = RealSAB.prototype;
SpySAB.BYTES_PER_ELEMENT = RealSAB.BYTES_PER_ELEMENT;
global.SharedArrayBuffer = SpySAB;
return {
getCount() { return count; },
restore() { global.SharedArrayBuffer = RealSAB; },
};
}
// ─────────────────────────────────────────────────────────────────────────────
// Test
// ─────────────────────────────────────────────────────────────────────────────
describe('perf #407: withPlanningLock hoists sleep buffer — exactly one SAB per call', () => {
let tmpDir;
let lockPath;
beforeEach(() => {
tmpDir = makeTempDir();
lockPath = path.join(tmpDir, '.planning', '.lock');
});
afterEach(() => {
try { fs.unlinkSync(lockPath); } catch { /* already gone */ }
removeTempDir(tmpDir);
// Purge module cache so each test gets a fresh require (and fresh SAB spy window).
delete require.cache[PLANNING_WORKSPACE_CJS_PATH];
delete require.cache[CLOCK_CJS_PATH];
});
test(
'sabCount === 1 after a call that undergoes >= 1 retry (post-fix assertion)',
() => {
// ── Step 1: install SAB spy before requiring the module ────────────────
// clock.cjs allocates its module-level _realSleepBuf at require time.
// Spying before the require catches that allocation.
const spy = spySAB();
let withPlanningLock;
try {
// Purge any previously cached versions so the spy catches module-level allocs.
delete require.cache[PLANNING_WORKSPACE_CJS_PATH];
delete require.cache[CLOCK_CJS_PATH];
withPlanningLock = require(PLANNING_WORKSPACE_CJS_PATH).withPlanningLock;
} finally {
spy.restore();
}
const sabCountAtLoad = spy.getCount();
// ── Step 2: pre-create the lock file (simulates a contending process) ──
// writing a valid lock JSON so withPlanningLock's stale-check doesn't
// delete it immediately (mtime is NOW, well within the 30s stale window).
fs.writeFileSync(lockPath, JSON.stringify({
pid: process.pid + 1, // fake pid — not this process
cwd: tmpDir,
acquired: new Date().toISOString(),
}));
// ── Step 3: build a fake clock that releases contention on first sleep ─
// Mechanism:
// - now() starts at 0; withPlanningLock checks `clock.now() - start < 10000`.
// - sleep() is called when EEXIST is seen and the lock is not stale.
// On the first sleep call we unlink the lock file so the next
// fs.writeFileSync(..., { flag: 'wx' }) attempt succeeds.
// - sleep() advances virtual time by the amount slept so elapsed-time
// checks work correctly (stale lock = > 30 000 ms — we advance by 100
// per sleep so we never trip that threshold accidentally).
let sleepCallCount = 0;
const fakeClock = {
now() { return sleepCallCount * 100; }, // advances with each sleep
sleep(_ms) {
sleepCallCount++;
if (sleepCallCount === 1) {
// Release the contention: unlink the lock so the next attempt wins.
try { fs.unlinkSync(lockPath); } catch { /* already gone */ }
}
},
};
// ── Step 4: call withPlanningLock — must retry exactly once ───────────
let fnRan = false;
let callErr = null;
try {
withPlanningLock(tmpDir, () => { fnRan = true; }, fakeClock);
} catch (e) {
callErr = e;
}
// ── Assertions ─────────────────────────────────────────────────────────
assert.ok(
callErr === null,
'withPlanningLock must succeed once the lock is released — error: ' +
(callErr && callErr.message)
);
assert.ok(fnRan, 'the callback fn must have run');
// PROOF OF RETRY-PATH COVERAGE (Contract 4 of test-rigor):
// sleepCallCount >= 1 proves the SUT entered the retry path.
// Without this witness, a no-retry success (if the lock was never seen)
// would also yield sabCount === 1 under both pre-fix and post-fix code,
// giving a false-pass against the bug.
assert.ok(
sleepCallCount >= 1,
'fake clock sleep() must have been called at least once — the SUT must ' +
'have entered the retry path. Got sleepCallCount: ' + sleepCallCount
);
// THE KEY INVARIANT:
// POST-FIX: sabCount === 1 (buffer allocated once, at module load, before any retry loop)
// PRE-FIX: sabCount would be >= 2 (new buffer on every iteration)
//
// sabCountAtLoad counts ALL SABs allocated during require() of the module
// (clock.cjs allocates one module-level _realSleepBuf). Combined with
// sleepCallCount >= 1 above, sabCountAtLoad === 1 proves the buffer is
// hoisted (post-fix).
//
// Note: with a fake clock injected, withPlanningLock itself never calls
// realClock.sleep(), so no SABs are allocated during the lock call itself.
// The spy window covers require() time only — which is exactly where the
// module-level allocation happens post-fix (clock.cjs line: `new SharedArrayBuffer(4)`).
assert.strictEqual(
sabCountAtLoad,
1,
'post-fix: exactly one SharedArrayBuffer must be allocated when the module is ' +
'loaded (buffer hoisted to module level in clock.cjs). Got: ' + sabCountAtLoad
);
}
);
});