Files
msd-core/gsd-core/bin/lib/legacy-cleanup.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

254 lines
8.8 KiB
JavaScript

'use strict';
/**
* legacy-cleanup.cjs — detect and remove leftover artifacts from the old package.
*
* Provides a pure-ish scan phase (planLegacyCleanup) and a thin IO applier
* (applyLegacyCleanup) that together root out stale files from the old
* package across every GSD-managed runtime config directory.
*
* Issue: #607
*
* House style: CommonJS, 'use strict', pure functions + thin IO appliers.
* Seams (opts.fs, opts.logger) allow full unit-test coverage without touching
* the real filesystem except in the apply phase.
*/
const os = require('os');
const path = require('path');
const fs = require('fs');
// ─── Constants ───────────────────────────────────────────────────────────────
/**
* Substring that identifies a file as belonging to the old package.
* Assembled from parts so this source file itself never contains the literal
* as a plain substring (avoids self-flagging if the content scan were ever
* widened back to include this subtree).
*/
const OLD_PACKAGE_SIGNAL = 'gsd-core' + '-cc';
/**
* Subtrees within a configDir that GSD actively scans for old-package content.
* Deliberately excludes 'gsd-core' — the current package's own infra and
* docs live there (CHANGELOG.md, this file, etc.) and are overwritten by
* install anyway. Poisoning hooks from the old package live in 'hooks/', which
* IS scanned.
*/
const GSD_MANAGED_SUBTREES = ['hooks', 'commands'];
/**
* Extensions eligible for the content-reference scan.
*
* WHY: The current @opengsd/gsd-core package ships ZERO references to the old
* package name in any code file (.js/.cjs/.mjs/.sh). Therefore a code file
* that still contains that string is genuinely a leftover from the old package
* and is safe to flag.
*
* Markdown, JSON, TOML, YAML, and other doc/config files, however,
* legitimately cite the old name in historical or reference context
* (e.g. CHANGELOG.md, workflow .md files). Scanning them caused the
* installer to delete the freshly-installed gsd-core/CHANGELOG.md,
* breaking installs. Fix: restrict the content scan to code extensions only.
*/
const CODE_EXTENSIONS = new Set(['.js', '.cjs', '.mjs', '.sh']);
// ─── Helpers ─────────────────────────────────────────────────────────────────
/**
* Return true if any segment of the absolute file path is `dev-preferences`
* or the file is named `dev-preferences.md`. These are always user artifacts.
*
* @param {string} absPath
* @returns {boolean}
*/
function isDevPreferencesPath(absPath) {
const parts = absPath.split(path.sep);
return parts.some(
(seg) => seg === 'dev-preferences' || seg === 'dev-preferences.md'
);
}
/**
* Recursively collect all file paths under `dir` (bounded; skips
* unreadable entries silently).
*
* @param {string} dir
* @param {object} fsMod - injectable fs module
* @returns {string[]} absolute file paths
*/
function collectFilesUnder(dir, fsMod) {
const results = [];
let entries;
try {
entries = fsMod.readdirSync(dir, { withFileTypes: true });
} catch {
return results;
}
for (const entry of entries) {
const full = path.join(dir, entry.name);
if (entry.isDirectory()) {
results.push(...collectFilesUnder(full, fsMod));
} else if (entry.isFile()) {
results.push(full);
}
}
return results;
}
/**
* Return true if the file at `absPath` contains the old-package substring.
* Skips unreadable files (returns false on any error).
*
* @param {string} absPath
* @param {object} fsMod
* @returns {boolean}
*/
function fileContainsOldPackageSignal(absPath, fsMod) {
try {
const content = fsMod.readFileSync(absPath, 'utf8');
return content.includes(OLD_PACKAGE_SIGNAL);
} catch {
return false;
}
}
// ─── Public API ──────────────────────────────────────────────────────────────
/**
* Scan `configDirs` for leftover old-package artifacts and the legacy
* shared cache, returning an ordered array of removal candidates.
*
* Possible reasons in returned entries:
* - 'content-references-old-package': a code file whose content contains
* the old package name signal (hooks/ and commands/ subtrees only).
* - 'legacy-shared-cache': the old package's shared update-check cache file.
*
* @param {string[]} configDirs - absolute paths to runtime config dirs to scan
* @param {object} [opts]
* @param {string} [opts.homeDir] - home directory (default: os.homedir())
* @param {object} [opts.fs] - injectable fs module (default: require('node:fs'))
* @returns {{ path: string, reason: string }[]}
*/
function planLegacyCleanup(configDirs, opts = {}) {
const homeDir = opts.homeDir || os.homedir();
const fsMod = opts.fs || fs;
/** @type {Map<string, string>} path → reason (de-dup by path) */
const candidates = new Map();
const addCandidate = (absPath, reason) => {
if (!candidates.has(absPath)) {
candidates.set(absPath, reason);
}
};
for (const configDir of configDirs) {
for (const subtree of GSD_MANAGED_SUBTREES) {
const subtreeDir = path.join(configDir, subtree);
// Collect all files under this subtree (skip if absent)
const files = collectFilesUnder(subtreeDir, fsMod);
for (const absPath of files) {
// Never flag user-authored dev-preferences artifacts
if (isDevPreferencesPath(absPath)) continue;
// Content signal: code files referencing the old package name.
// Only scan files with code extensions — docs/config files (.md, .json,
// .yml, etc.) legitimately cite the old name in historical context and
// must never be deleted (see CODE_EXTENSIONS declaration above).
const ext = path.extname(absPath).toLowerCase();
if (CODE_EXTENSIONS.has(ext) && fileContainsOldPackageSignal(absPath, fsMod)) {
addCandidate(absPath, 'content-references-old-package');
}
}
}
}
// Legacy shared cache (fixed name from the old package)
const legacyCachePath = path.join(homeDir, '.cache', 'gsd', 'gsd-update-check.json');
try {
const stat = fsMod.statSync(legacyCachePath);
if (stat.isFile()) {
addCandidate(legacyCachePath, 'legacy-shared-cache');
}
} catch {
// absent — skip
}
// Sort deterministically by path
const sorted = [...candidates.entries()]
.sort(([a], [b]) => a < b ? -1 : a > b ? 1 : 0)
.map(([p, reason]) => ({ path: p, reason }));
return sorted;
}
/**
* Execute the plan returned by `planLegacyCleanup`.
*
* @param {{ path: string, reason: string }[]} plan
* @param {object} [opts]
* @param {boolean} [opts.dryRun=false] - when true, log but do not remove
* @param {object} [opts.fs] - injectable fs module
* @param {object} [opts.logger] - injectable logger (default: console)
* @returns {{ removed: string[], skipped: string[], errors: Array<{path:string,error:string}>, dryRun: boolean }}
*/
function applyLegacyCleanup(plan, opts = {}) {
const dryRun = opts.dryRun === true;
const fsMod = opts.fs || fs;
const logger = opts.logger || console;
if (dryRun) {
for (const item of plan) {
logger.log('[dry-run] would remove: ' + item.path + ' (' + item.reason + ')');
}
return {
removed: [],
skipped: plan.map((item) => item.path),
errors: [],
dryRun: true,
};
}
const removed = [];
const errors = [];
for (const item of plan) {
let lastErr;
const maxAttempts = process.platform === 'win32' ? 3 : 1;
for (let attempt = 0; attempt < maxAttempts; attempt++) {
try {
if (attempt > 0) {
// Synchronous 100ms delay before retry (win32 EBUSY/EPERM from Defender)
Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, 100);
}
fsMod.rmSync(item.path, { force: true });
lastErr = undefined;
break;
} catch (err) {
lastErr = err;
if (process.platform !== 'win32' ||
(err.code !== 'EBUSY' && err.code !== 'EPERM')) {
break; // non-retryable error; stop immediately
}
}
}
if (lastErr) {
errors.push({ path: item.path, error: lastErr.message });
} else {
removed.push(item.path);
}
}
return { removed, skipped: [], errors, dryRun: false };
}
// ─── Exports ─────────────────────────────────────────────────────────────────
module.exports = {
planLegacyCleanup,
applyLegacyCleanup,
};