* 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>
199 lines
8.0 KiB
JavaScript
199 lines
8.0 KiB
JavaScript
// allow-test-rule: docs-parity
|
|
// Verifies that issue #22 drift-guard surfacing changes are present:
|
|
// - new-project workflow mentions plan_review.source_grounding
|
|
// - CONFIGURATION.md documents both new config keys
|
|
// - COMMANDS.md mentions gsd-tools intel api-surface
|
|
|
|
const { describe, test } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
|
|
const ROOT = path.join(__dirname, '..');
|
|
|
|
const NEW_PROJECT_PATH = path.join(ROOT, 'gsd-core', 'workflows', 'new-project.md');
|
|
const SETTINGS_PATH = path.join(ROOT, 'gsd-core', 'workflows', 'settings.md');
|
|
const CONFIGURATION_PATH = path.join(ROOT, 'docs', 'CONFIGURATION.md');
|
|
const COMMANDS_PATH = path.join(ROOT, 'docs', 'COMMANDS.md');
|
|
const USER_GUIDE_PATH = path.join(ROOT, 'docs', 'USER-GUIDE.md');
|
|
const ARCHITECTURE_PATH = path.join(ROOT, 'docs', 'ARCHITECTURE.md');
|
|
|
|
describe('feat-22-surfacing-docs', () => {
|
|
// ── A1: new-project workflow ─────────────────────────────────────────────
|
|
|
|
test('new-project workflow mentions source_grounding', () => {
|
|
const content = fs.readFileSync(NEW_PROJECT_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('source_grounding'),
|
|
'new-project.md must mention source_grounding'
|
|
);
|
|
});
|
|
|
|
test('new-project workflow has Drift Guard question', () => {
|
|
const content = fs.readFileSync(NEW_PROJECT_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('Drift Guard'),
|
|
'new-project.md must include a "Drift Guard" question header'
|
|
);
|
|
});
|
|
|
|
test('new-project workflow wires source_grounding into config-new-project call', () => {
|
|
const content = fs.readFileSync(NEW_PROJECT_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('"plan_review":{"source_grounding":'),
|
|
'new-project.md config-new-project call must include plan_review.source_grounding'
|
|
);
|
|
});
|
|
|
|
test('new-project workflow has Drift Guard default-yes option', () => {
|
|
const content = fs.readFileSync(NEW_PROJECT_PATH, 'utf-8');
|
|
// Both question blocks (auto and interactive) should have the yes option
|
|
const count = (content.match(/Yes \(Recommended\).*catches hallucinated names/g) || []).length;
|
|
assert.ok(
|
|
count >= 1,
|
|
'new-project.md must have at least one Drift Guard "Yes (Recommended)" option'
|
|
);
|
|
});
|
|
|
|
// ── A2: settings workflow ────────────────────────────────────────────────
|
|
|
|
test('settings workflow mentions source_grounding in read_current step', () => {
|
|
const content = fs.readFileSync(SETTINGS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('plan_review.source_grounding'),
|
|
'settings.md must mention plan_review.source_grounding in the read_current step'
|
|
);
|
|
});
|
|
|
|
test('settings workflow has Drift Guard AskUserQuestion toggle', () => {
|
|
const content = fs.readFileSync(SETTINGS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('Drift Guard'),
|
|
'settings.md must include a "Drift Guard" question header'
|
|
);
|
|
});
|
|
|
|
test('settings workflow update_config includes plan_review.source_grounding', () => {
|
|
const content = fs.readFileSync(SETTINGS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('"source_grounding": true/false'),
|
|
'settings.md update_config block must include source_grounding: true/false'
|
|
);
|
|
});
|
|
|
|
test('settings workflow mentions source_grounding_authority', () => {
|
|
const content = fs.readFileSync(SETTINGS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('source_grounding_authority'),
|
|
'settings.md must mention source_grounding_authority'
|
|
);
|
|
});
|
|
|
|
test('settings confirm table includes Plan Drift Guard row', () => {
|
|
const content = fs.readFileSync(SETTINGS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('Plan Drift Guard'),
|
|
'settings.md confirm table must include a "Plan Drift Guard" row'
|
|
);
|
|
});
|
|
|
|
// ── B1: CONFIGURATION.md ─────────────────────────────────────────────────
|
|
|
|
test('CONFIGURATION.md documents plan_review.source_grounding', () => {
|
|
const content = fs.readFileSync(CONFIGURATION_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('`plan_review.source_grounding`'),
|
|
'CONFIGURATION.md must document plan_review.source_grounding'
|
|
);
|
|
});
|
|
|
|
test('CONFIGURATION.md documents plan_review.source_grounding_authority', () => {
|
|
const content = fs.readFileSync(CONFIGURATION_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('`plan_review.source_grounding_authority`'),
|
|
'CONFIGURATION.md must document plan_review.source_grounding_authority'
|
|
);
|
|
});
|
|
|
|
test('CONFIGURATION.md documents grep as default authority', () => {
|
|
const content = fs.readFileSync(CONFIGURATION_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('`grep`') && content.includes('source_grounding_authority'),
|
|
'CONFIGURATION.md must document grep as the default source_grounding_authority'
|
|
);
|
|
});
|
|
|
|
test('CONFIGURATION.md lists all five authority enum values', () => {
|
|
const content = fs.readFileSync(CONFIGURATION_PATH, 'utf-8');
|
|
const authorities = ['grep', 'intel', 'treesitter', 'lsp', 'scip'];
|
|
const missing = authorities.filter(a => !content.includes(a));
|
|
assert.deepStrictEqual(
|
|
missing,
|
|
[],
|
|
`CONFIGURATION.md must list all authority values; missing: ${missing.join(', ')}`
|
|
);
|
|
});
|
|
|
|
// ── B2: COMMANDS.md ───────────────────────────────────────────────────────
|
|
|
|
test('COMMANDS.md mentions intel api-surface', () => {
|
|
const content = fs.readFileSync(COMMANDS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('intel api-surface'),
|
|
'COMMANDS.md must document the gsd-tools intel api-surface command'
|
|
);
|
|
});
|
|
|
|
test('COMMANDS.md documents api-surface gating on intel.enabled', () => {
|
|
const content = fs.readFileSync(COMMANDS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('intel.enabled'),
|
|
'COMMANDS.md intel api-surface section must mention the intel.enabled gate'
|
|
);
|
|
});
|
|
|
|
test('COMMANDS.md mentions API-SURFACE.md output', () => {
|
|
const content = fs.readFileSync(COMMANDS_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('API-SURFACE.md'),
|
|
'COMMANDS.md must mention the API-SURFACE.md output file'
|
|
);
|
|
});
|
|
|
|
// ── B3: USER-GUIDE.md ─────────────────────────────────────────────────────
|
|
|
|
test('USER-GUIDE.md has Plan Drift Guard subsection', () => {
|
|
const content = fs.readFileSync(USER_GUIDE_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('### Plan Drift Guard'),
|
|
'USER-GUIDE.md must have a "### Plan Drift Guard" subsection'
|
|
);
|
|
});
|
|
|
|
test('USER-GUIDE.md mentions needs-acknowledgement behavior', () => {
|
|
const content = fs.readFileSync(USER_GUIDE_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('needs-acknowledgement'),
|
|
'USER-GUIDE.md drift guard section must describe needs-acknowledgement behavior'
|
|
);
|
|
});
|
|
|
|
test('USER-GUIDE.md explains drift guard works without intel', () => {
|
|
const content = fs.readFileSync(USER_GUIDE_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('without intel') || content.includes('Works without intel'),
|
|
'USER-GUIDE.md must explain that the drift guard works without intel'
|
|
);
|
|
});
|
|
|
|
// ── B4: ARCHITECTURE.md ───────────────────────────────────────────────────
|
|
|
|
test('ARCHITECTURE.md links to ADR 22', () => {
|
|
const content = fs.readFileSync(ARCHITECTURE_PATH, 'utf-8');
|
|
assert.ok(
|
|
content.includes('adr/22-plan-drift-guard.md') || content.includes('ADR 22'),
|
|
'ARCHITECTURE.md must link to ADR 22 (adr/22-plan-drift-guard.md)'
|
|
);
|
|
});
|
|
});
|