* 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
7.2 KiB
JavaScript
165 lines
7.2 KiB
JavaScript
// allow-test-rule: source-text-is-the-product
|
|
// The workflow .md IS the product: its text is loaded and interpreted at
|
|
// runtime by the agent host. Structural assertions (step existence, flag
|
|
// references in the initialize step) verify the deployed dispatch contract.
|
|
// Pure-function assertions on parseCodeReviewFlags / resolveCodeReviewWorkflow
|
|
// are IR-level (not raw-text-match) per CONTRIBUTING.md L554.
|
|
|
|
/**
|
|
* Regression tests for #3727 — /gsd-code-review N --fix silently no-ops.
|
|
*
|
|
* Root cause: code-review.md `initialize` step parses only --depth and
|
|
* --files flags. --fix, --all, and --auto are never parsed, so no dispatch
|
|
* to code-review-fix.md ever occurs.
|
|
*
|
|
* Fix: add parseCodeReviewFlags() to code-review-flags.cjs (typed IR), wire
|
|
* it into the workflow initialize step, and add a dispatch_fix step that
|
|
* delegates to code-review-fix.md when flags.fix is true.
|
|
*/
|
|
|
|
'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 ROOT = path.resolve(__dirname, '..');
|
|
const FLAGS_LIB = path.join(ROOT, 'gsd-core', 'bin', 'lib', 'code-review-flags.cjs');
|
|
const WORKFLOW_PATH = path.join(ROOT, 'gsd-core', 'workflows', 'code-review.md');
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Stage 2 seam: typed IR from parseCodeReviewFlags and resolveCodeReviewWorkflow
|
|
// These functions are the production code under test — not text-matching on
|
|
// the .md source.
|
|
// ---------------------------------------------------------------------------
|
|
|
|
const { parseCodeReviewFlags, resolveCodeReviewWorkflow } = require(FLAGS_LIB);
|
|
|
|
describe('#3727 — parseCodeReviewFlags: typed IR for code-review argv', () => {
|
|
test('code-review workflow parses --fix flag and dispatches gsd-code-fixer', () => {
|
|
// This is the invariant being violated: --fix must be captured into the IR
|
|
// and must route to the fixer workflow, not be silently dropped.
|
|
const flags = parseCodeReviewFlags(['2', '--fix']);
|
|
assert.strictEqual(flags.fix, true,
|
|
'--fix must set flags.fix = true');
|
|
const workflow = resolveCodeReviewWorkflow(flags);
|
|
assert.strictEqual(workflow, 'code-review-fix.md',
|
|
'--fix must dispatch to code-review-fix.md, not code-review.md');
|
|
});
|
|
|
|
test('--fix absent: dispatch stays on code-review.md (review-only)', () => {
|
|
// Counter-test (Stage 5 contract 6): omitting --fix must NOT dispatch fixer.
|
|
const flags = parseCodeReviewFlags(['2']);
|
|
assert.strictEqual(flags.fix, false,
|
|
'Without --fix, flags.fix must be false');
|
|
const workflow = resolveCodeReviewWorkflow(flags);
|
|
assert.strictEqual(workflow, 'code-review.md',
|
|
'Without --fix, dispatch must stay on code-review.md');
|
|
});
|
|
|
|
test('--all implies --fix', () => {
|
|
const flags = parseCodeReviewFlags(['3', '--all']);
|
|
assert.strictEqual(flags.fix, true,
|
|
'--all must imply flags.fix = true');
|
|
assert.strictEqual(flags.all, true,
|
|
'--all must set flags.all = true');
|
|
const workflow = resolveCodeReviewWorkflow(flags);
|
|
assert.strictEqual(workflow, 'code-review-fix.md',
|
|
'--all must dispatch to code-review-fix.md');
|
|
});
|
|
|
|
test('--auto implies --fix', () => {
|
|
const flags = parseCodeReviewFlags(['3', '--auto']);
|
|
assert.strictEqual(flags.fix, true,
|
|
'--auto must imply flags.fix = true');
|
|
assert.strictEqual(flags.auto, true,
|
|
'--auto must set flags.auto = true');
|
|
const workflow = resolveCodeReviewWorkflow(flags);
|
|
assert.strictEqual(workflow, 'code-review-fix.md',
|
|
'--auto must dispatch to code-review-fix.md');
|
|
});
|
|
|
|
test('--fix --all --auto all set simultaneously', () => {
|
|
const flags = parseCodeReviewFlags(['1', '--fix', '--all', '--auto']);
|
|
assert.strictEqual(flags.fix, true);
|
|
assert.strictEqual(flags.all, true);
|
|
assert.strictEqual(flags.auto, true);
|
|
assert.strictEqual(resolveCodeReviewWorkflow(flags), 'code-review-fix.md');
|
|
});
|
|
|
|
test('--depth flag is still parsed alongside --fix (no regression)', () => {
|
|
const flags = parseCodeReviewFlags(['2', '--depth=deep', '--fix']);
|
|
assert.strictEqual(flags.fix, true);
|
|
assert.strictEqual(flags.depth, 'deep');
|
|
assert.strictEqual(resolveCodeReviewWorkflow(flags), 'code-review-fix.md');
|
|
});
|
|
|
|
test('--files flag is still parsed alongside --fix (no regression)', () => {
|
|
const flags = parseCodeReviewFlags(['2', '--files=src/foo.ts,src/bar.ts', '--fix']);
|
|
assert.strictEqual(flags.fix, true);
|
|
assert.strictEqual(flags.files, 'src/foo.ts,src/bar.ts');
|
|
});
|
|
|
|
test('empty argv returns all-false IR', () => {
|
|
const flags = parseCodeReviewFlags([]);
|
|
assert.strictEqual(flags.fix, false);
|
|
assert.strictEqual(flags.all, false);
|
|
assert.strictEqual(flags.auto, false);
|
|
assert.strictEqual(flags.depth, '');
|
|
assert.strictEqual(flags.files, '');
|
|
});
|
|
});
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Docs-parity: the workflow .md must contain the dispatch_fix step and
|
|
// reference code-review-flags.cjs in the initialize step.
|
|
// These are structural invariants on the deployed product text.
|
|
// Source-text-is-the-product exemption applies (see file header).
|
|
// ---------------------------------------------------------------------------
|
|
|
|
describe('#3727 — code-review.md structural dispatch contract', () => {
|
|
const src = fs.readFileSync(WORKFLOW_PATH, 'utf8');
|
|
|
|
test('initialize step references code-review-flags.cjs for flag parsing', () => {
|
|
const initStart = src.indexOf('<step name="initialize">');
|
|
const initEnd = src.indexOf('</step>', initStart);
|
|
assert.ok(initStart !== -1, 'workflow must have an initialize step');
|
|
const initSection = src.slice(initStart, initEnd);
|
|
assert.ok(
|
|
initSection.includes('code-review-flags.cjs'),
|
|
'initialize step must reference code-review-flags.cjs to parse --fix/--all/--auto flags'
|
|
);
|
|
});
|
|
|
|
test('workflow has a <step name="dispatch_fix"> step', () => {
|
|
assert.ok(
|
|
src.includes('<step name="dispatch_fix">'),
|
|
'code-review.md must have a dispatch_fix step (missing = --fix is silently no-op)'
|
|
);
|
|
});
|
|
|
|
test('dispatch_fix step delegates to code-review-fix.md when fix flag is true', () => {
|
|
const stepStart = src.indexOf('<step name="dispatch_fix">');
|
|
const stepEnd = src.indexOf('</step>', stepStart);
|
|
assert.ok(stepStart !== -1, 'dispatch_fix step must exist');
|
|
const stepSection = src.slice(stepStart, stepEnd);
|
|
assert.ok(
|
|
stepSection.includes('code-review-fix.md'),
|
|
'dispatch_fix step must reference code-review-fix.md workflow'
|
|
);
|
|
});
|
|
|
|
test('dispatch_fix step references gsd-code-fixer agent (via code-review-fix.md chain)', () => {
|
|
// The dispatch step must show that fixing will occur, either directly or
|
|
// by loading code-review-fix.md (which in turn spawns gsd-code-fixer).
|
|
const stepStart = src.indexOf('<step name="dispatch_fix">');
|
|
const stepEnd = src.indexOf('</step>', stepStart);
|
|
const stepSection = src.slice(stepStart, stepEnd);
|
|
assert.ok(
|
|
stepSection.includes('gsd-code-fixer') || stepSection.includes('code-review-fix.md'),
|
|
'dispatch_fix step must reference gsd-code-fixer agent or code-review-fix.md workflow'
|
|
);
|
|
});
|
|
});
|