* 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>
191 lines
6.7 KiB
JavaScript
191 lines
6.7 KiB
JavaScript
/**
|
|
* Regression test for #3610: fresh `npx @opengsd/gsd-core@latest --codex`
|
|
* hard-aborts when the target ~/.codex/hooks/ contains the bundled GSD
|
|
* hook files (`gsd-check-update-worker.js`, `gsd-prompt-guard.js`, …)
|
|
* left over from a previous version. The installer-migration report
|
|
* classifies them as "GSD-looking file is not proven manifest-managed
|
|
* and needs explicit user choice" and `assertInstallerMigrationsUnblocked`
|
|
* throws.
|
|
*
|
|
* The files in question are NOT user-owned — they are the GSD bundled
|
|
* hooks shipped under `hooks/gsd-*` in the npm package. The fix adds a
|
|
* `bundled-gsd-hook` classification to `classifyPromptUserAction` so the
|
|
* resolver removes them (the installer then writes the fresh bundled
|
|
* versions in their place).
|
|
*
|
|
* Because this classification is unambiguous (these are not user files),
|
|
* it must apply regardless of whether stdin is a TTY — the reporter's
|
|
* `npx ... --codex` run was interactive and the existing non-TTY
|
|
* resolver gate at install.js:8069 skipped the safe-default pass.
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
process.env.GSD_TEST_MODE = '1';
|
|
|
|
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 crypto = require('node:crypto');
|
|
|
|
const {
|
|
runInstallerMigrations,
|
|
} = require('../gsd-core/bin/lib/installer-migrations.cjs');
|
|
const {
|
|
assertInstallerMigrationsUnblocked,
|
|
resolveInstallerMigrationPromptsForNonTty,
|
|
classifyPromptUserAction,
|
|
} = require('../gsd-core/bin/lib/installer-migration-report.cjs');
|
|
const { createTempDir, cleanup } = require('./helpers.cjs');
|
|
|
|
function writeFile(root, relPath, content) {
|
|
const fullPath = path.join(root, relPath);
|
|
fs.mkdirSync(path.dirname(fullPath), { recursive: true });
|
|
fs.writeFileSync(fullPath, content, 'utf8');
|
|
}
|
|
|
|
function writeManifest(root, files) {
|
|
fs.writeFileSync(
|
|
path.join(root, 'gsd-file-manifest.json'),
|
|
JSON.stringify(
|
|
{
|
|
version: '1.41.2',
|
|
timestamp: '2026-05-10T00:00:00.000Z',
|
|
mode: 'full',
|
|
files,
|
|
},
|
|
null,
|
|
2,
|
|
),
|
|
'utf8',
|
|
);
|
|
}
|
|
|
|
// Reporter's exact list of blocked files from the v1.42.2 → v1.42.0 upgrade
|
|
// abort. Each is a real `hooks/gsd-*` file shipped under hooks/ in the npm
|
|
// package (verified by `ls hooks/`).
|
|
const BUNDLED_HOOK_RELPATHS = [
|
|
'hooks/gsd-check-update-worker.js',
|
|
'hooks/gsd-check-update.js',
|
|
'hooks/gsd-context-monitor.js',
|
|
'hooks/gsd-phase-boundary.sh',
|
|
'hooks/gsd-prompt-guard.js',
|
|
'hooks/gsd-read-guard.js',
|
|
'hooks/gsd-read-injection-scanner.js',
|
|
'hooks/gsd-session-state.sh',
|
|
'hooks/gsd-statusline.js',
|
|
'hooks/gsd-update-banner.js',
|
|
'hooks/gsd-validate-commit.sh',
|
|
'hooks/gsd-workflow-guard.js',
|
|
];
|
|
|
|
describe('bug #3610: classifyPromptUserAction recognizes bundled GSD hooks', () => {
|
|
test('classifies hooks/gsd-*.js as bundled-gsd-hook → remove', () => {
|
|
const result = classifyPromptUserAction({
|
|
relPath: 'hooks/gsd-prompt-guard.js',
|
|
});
|
|
assert.ok(result, 'classifier returned null for a bundled GSD hook (.js)');
|
|
assert.strictEqual(result.category, 'bundled-gsd-hook');
|
|
assert.strictEqual(
|
|
result.choice,
|
|
'remove',
|
|
'bundled hook must default to remove so the installer can write the fresh bundled version',
|
|
);
|
|
});
|
|
|
|
test('classifies hooks/gsd-*.sh as bundled-gsd-hook → remove', () => {
|
|
const result = classifyPromptUserAction({
|
|
relPath: 'hooks/gsd-validate-commit.sh',
|
|
});
|
|
assert.ok(result);
|
|
assert.strictEqual(result.category, 'bundled-gsd-hook');
|
|
assert.strictEqual(result.choice, 'remove');
|
|
});
|
|
|
|
test('does NOT classify non-gsd hooks (preserves user-owned hook files)', () => {
|
|
// A user's custom hook that happens to live under hooks/ must NOT be
|
|
// auto-classified as bundled — the existing block-then-choose flow
|
|
// continues to apply, preserving the user's control over their files.
|
|
const result = classifyPromptUserAction({
|
|
relPath: 'hooks/my-custom-hook.js',
|
|
});
|
|
assert.strictEqual(
|
|
result,
|
|
null,
|
|
'non-gsd-prefixed hook must NOT auto-classify (would clobber user files)',
|
|
);
|
|
});
|
|
|
|
test('does NOT classify deeper paths under hooks/gsd-* (e.g. hooks/lib/) as bundled-gsd-hook', () => {
|
|
// The bundled GSD distribution has hooks/lib/ (helper modules). Those
|
|
// are managed differently — verify the classifier limits itself to
|
|
// top-level hooks/gsd-<name>.<ext> files, not nested directories.
|
|
const result = classifyPromptUserAction({
|
|
relPath: 'hooks/gsd-helpers/index.js',
|
|
});
|
|
assert.strictEqual(result, null);
|
|
});
|
|
});
|
|
|
|
describe('bug #3610: fresh upgrade with leftover bundled hooks does not throw', () => {
|
|
let configDir;
|
|
|
|
beforeEach(() => {
|
|
configDir = createTempDir('gsd-3610-');
|
|
});
|
|
|
|
afterEach(() => {
|
|
cleanup(configDir);
|
|
});
|
|
|
|
test('end-to-end: 12 leftover bundled hooks + empty manifest → resolver clears all blockers', () => {
|
|
// Recreate the reporter's environment: 12 bundled `gsd-*` hook files
|
|
// present at target, but the manifest has not yet seeded their baseline
|
|
// entries (first-time-baseline scan).
|
|
for (const rel of BUNDLED_HOOK_RELPATHS) {
|
|
writeFile(configDir, rel, '#!/usr/bin/env node\n// stale 1.42.0 hook\n');
|
|
}
|
|
writeManifest(configDir, {});
|
|
|
|
const result = runInstallerMigrations({
|
|
configDir,
|
|
runtime: 'codex',
|
|
scope: 'global',
|
|
baselineScan: true,
|
|
});
|
|
|
|
// Precondition: all 12 leftover hooks classify as prompt-user blockers.
|
|
const blockedPaths = (result.blocked || []).map((a) => a.relPath).sort();
|
|
assert.deepStrictEqual(
|
|
blockedPaths,
|
|
[...BUNDLED_HOOK_RELPATHS].sort(),
|
|
'precondition: every leftover hooks/gsd-* should be a prompt-user blocker',
|
|
);
|
|
|
|
// Resolve through the safe-default classifier (passing isTty=false to
|
|
// exercise the same code path the bundled-hook classification will hit
|
|
// regardless of TTY once the fix removes the gate).
|
|
const resolved = resolveInstallerMigrationPromptsForNonTty(result, { isTty: false });
|
|
|
|
assert.strictEqual(
|
|
resolved.resolutions.length,
|
|
BUNDLED_HOOK_RELPATHS.length,
|
|
'every bundled hook should produce a safe-default resolution entry',
|
|
);
|
|
|
|
for (const entry of resolved.resolutions) {
|
|
assert.strictEqual(entry.category, 'bundled-gsd-hook');
|
|
assert.strictEqual(entry.choice, 'remove');
|
|
assert.strictEqual(entry.resolvedActionType, 'backup-and-remove');
|
|
}
|
|
|
|
assert.strictEqual(
|
|
(resolved.result.blocked || []).length,
|
|
0,
|
|
'no blockers should remain after bundled-hook classification fires',
|
|
);
|
|
assert.doesNotThrow(() => assertInstallerMigrationsUnblocked(resolved.result));
|
|
});
|
|
});
|