* 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>
165 lines
6.3 KiB
JavaScript
165 lines
6.3 KiB
JavaScript
/**
|
|
* Bug #2851: plan-phase.md §13e calls bare `gsd-tools` — incomplete fix of #2245
|
|
*
|
|
* Workflow bodies should not call `gsd-tools` as an unguarded bare command.
|
|
* Use the resolver snippets for SDK calls, or an explicit local CJS path when
|
|
* a command intentionally targets the checked-in legacy script:
|
|
*
|
|
* node "$HOME/.claude/gsd-core/bin/gsd-tools.cjs" <subcommand> [args]
|
|
*
|
|
* Some workflow markdown files leaked the bare `gsd-tools <subcommand>` form,
|
|
* which fails with `command not found` at runtime.
|
|
*
|
|
* This test parses every markdown file in gsd-core/workflows/ structurally:
|
|
* it tokenizes the content into fenced code blocks, then on each shell-block
|
|
* line checks whether `gsd-tools` appears as a bare command (not preceded by
|
|
* `node `, not part of the filename `gsd-tools.cjs`, not inside a comment).
|
|
*
|
|
* Per project rule: this test does NOT use grep/regex .includes() on raw file
|
|
* content as the assertion surface. Instead, it splits into code-fenced blocks
|
|
* and tokenizes each line — only command-position tokens count as violations.
|
|
*/
|
|
'use strict';
|
|
|
|
const { describe, test } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
|
|
const WORKFLOWS_DIR = path.join(__dirname, '..', 'gsd-core', 'workflows');
|
|
|
|
/**
|
|
* Extract shell-fenced code blocks from a markdown file.
|
|
* Returns an array of { startLine, lines } where lines are the contents
|
|
* between the ```bash / ```sh / ```shell fence markers.
|
|
*/
|
|
function extractShellBlocks(content) {
|
|
const allLines = content.split('\n');
|
|
const blocks = [];
|
|
let inBlock = false;
|
|
let blockLang = null;
|
|
let blockStart = 0;
|
|
let blockLines = [];
|
|
|
|
for (let i = 0; i < allLines.length; i++) {
|
|
const line = allLines[i];
|
|
const fenceOpen = line.match(/^```(\w+)?/);
|
|
if (!inBlock && fenceOpen) {
|
|
inBlock = true;
|
|
blockLang = (fenceOpen[1] || '').toLowerCase();
|
|
blockStart = i + 2; // 1-indexed line number of first content line
|
|
blockLines = [];
|
|
continue;
|
|
}
|
|
if (inBlock && /^```\s*$/.test(line)) {
|
|
if (['bash', 'sh', 'shell', 'zsh', ''].includes(blockLang)) {
|
|
blocks.push({ startLine: blockStart, lines: blockLines });
|
|
}
|
|
inBlock = false;
|
|
blockLang = null;
|
|
blockLines = [];
|
|
continue;
|
|
}
|
|
if (inBlock) {
|
|
blockLines.push(line);
|
|
}
|
|
}
|
|
return blocks;
|
|
}
|
|
|
|
/**
|
|
* Check a single shell-block line for a bare `gsd-tools` command-position token.
|
|
* Returns true if the line is a violation.
|
|
*/
|
|
function lineHasBareGsdTools(line) {
|
|
// Strip leading whitespace and any prompt prefix ($ , > , # )
|
|
let l = line.replace(/^\s*[$>]\s*/, '');
|
|
// Skip pure comment lines
|
|
if (/^\s*#/.test(l)) return false;
|
|
// Strip inline comment (# preceded by whitespace, not inside a string)
|
|
// Conservative: only strip if # appears after whitespace and outside quotes —
|
|
// we just look for the first ` #` outside of quoted context. For our needs,
|
|
// splitting on `^[^"']*?(\s#)` is good enough.
|
|
const hashIdx = l.search(/(?:^|[^"'\w])#/);
|
|
if (hashIdx > 0) l = l.slice(0, hashIdx);
|
|
|
|
// Unwrap command-substitution forms so the substituted command is in
|
|
// command position. `$(cmd …)` and `` `cmd …` `` both run the inner string
|
|
// as a fresh command, so a bare `gsd-tools` inside them is just as broken
|
|
// as one at the start of the line. Iterate until stable for nested forms.
|
|
let prev;
|
|
do {
|
|
prev = l;
|
|
l = l.replace(/\$\(([^()]*)\)/g, ' $1 ').replace(/`([^`]*)`/g, ' $1 ');
|
|
} while (l !== prev);
|
|
|
|
// Tokenize on whitespace, semicolons, pipes, and && / ||
|
|
// Then walk tokens — a violation is a token that starts with `gsd-tools`
|
|
// followed by a word boundary (so `gsd-tools.cjs` does NOT match), and the
|
|
// preceding token is NOT `node`.
|
|
const segments = l.split(/(?:\s*(?:&&|\|\||;|\|)\s*)/);
|
|
for (const seg of segments) {
|
|
const tokens = seg.trim().split(/\s+/).filter(Boolean);
|
|
if (tokens.length === 0) continue;
|
|
// Skip env var assignments at the start (FOO=bar gsd-tools …, tmp=1 gsd-tools …).
|
|
// POSIX shell variable names are [A-Za-z_][A-Za-z0-9_]*; lowercase is valid.
|
|
let cmdIdx = 0;
|
|
while (cmdIdx < tokens.length && /^[A-Za-z_][A-Za-z0-9_]*=/.test(tokens[cmdIdx])) {
|
|
cmdIdx++;
|
|
}
|
|
if (cmdIdx >= tokens.length) continue;
|
|
const cmd = tokens[cmdIdx];
|
|
// Match `gsd-tools` exactly (no extension), as command position.
|
|
if (cmd === 'gsd-tools') return true;
|
|
}
|
|
return false;
|
|
}
|
|
|
|
describe('bug-2851: workflow files must not call bare `gsd-tools` (#2245 sweep regression)', () => {
|
|
test('no gsd-core/workflows/*.md file contains a bare gsd-tools command', () => {
|
|
const files = fs.readdirSync(WORKFLOWS_DIR).filter((f) => f.endsWith('.md'));
|
|
assert.ok(files.length > 0, 'expected workflow files to exist');
|
|
|
|
const violations = [];
|
|
for (const f of files) {
|
|
const full = path.join(WORKFLOWS_DIR, f);
|
|
const content = fs.readFileSync(full, 'utf-8');
|
|
const blocks = extractShellBlocks(content);
|
|
for (const blk of blocks) {
|
|
for (let i = 0; i < blk.lines.length; i++) {
|
|
if (lineHasBareGsdTools(blk.lines[i])) {
|
|
violations.push(`${f}:${blk.startLine + i}: ${blk.lines[i].trim()}`);
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|
|
assert.deepStrictEqual(
|
|
violations,
|
|
[],
|
|
'Bare `gsd-tools` invocations found in workflow shell blocks. ' +
|
|
'Use a resolver snippet or `node "$HOME/.claude/gsd-core/bin/gsd-tools.cjs" <subcommand>` instead.\n' +
|
|
violations.join('\n'),
|
|
);
|
|
});
|
|
|
|
test('plan-phase.md §13e gap-analysis uses canonical absolute-path invocation', () => {
|
|
const planPhase = fs.readFileSync(path.join(WORKFLOWS_DIR, 'plan-phase.md'), 'utf-8');
|
|
const blocks = extractShellBlocks(planPhase);
|
|
let foundGapAnalysisCall = false;
|
|
for (const blk of blocks) {
|
|
for (const line of blk.lines) {
|
|
if (/gap-analysis/.test(line) && !/^\s*#/.test(line)) {
|
|
foundGapAnalysisCall = true;
|
|
assert.match(
|
|
line,
|
|
/\bnode\s+["']?\$HOME\/\.claude\/gsd-core\/bin\/gsd-tools\.cjs["']?\s+gap-analysis\b/,
|
|
`gap-analysis call must use canonical absolute-path invocation, got: ${line.trim()}`,
|
|
);
|
|
}
|
|
}
|
|
}
|
|
assert.ok(foundGapAnalysisCall, 'expected at least one gap-analysis invocation in plan-phase.md');
|
|
});
|
|
});
|