Files
msd-core/tests/enh-2792-namespace-skills.test.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

257 lines
11 KiB
JavaScript

'use strict';
// allow-test-rule: source-text-is-the-product
// commands/gsd/*.md files ARE what the runtime loads — testing their
// frontmatter content tests the deployed system-prompt contract.
const { describe, test } = require('node:test');
const assert = require('node:assert/strict');
const fs = require('node:fs');
const path = require('node:path');
const COMMANDS_DIR = path.join(__dirname, '..', 'commands', 'gsd');
const NAMESPACE_SKILLS = [
{ file: 'ns-workflow.md', name: 'gsd-workflow' },
{ file: 'ns-project.md', name: 'gsd-project' },
{ file: 'ns-review.md', name: 'gsd-quality' },
{ file: 'ns-context.md', name: 'gsd-context' },
{ file: 'ns-manage.md', name: 'gsd-manage' },
{ file: 'ns-ideate.md', name: 'gsd-ideate' },
];
// Route targets named in any namespace body. The cross-reference test below
// asserts that every one of these resolves to a surviving command file or to
// a known consolidated parent (which absorbs flag-form invocations of folded
// skills, e.g. `gsd-map-codebase --fast` for the former `gsd-scan`).
const FLAG_FORM_PARENTS = new Set([
'gsd-code-review', // --fix absorbs former gsd-code-review-fix
'gsd-map-codebase', // --fast absorbs scan, --query absorbs intel
]);
/**
* Parse the leading YAML frontmatter block of a markdown file into a
* shallow `{ key: value }` map plus the trailing body. Splits on `\r?\n`
* for CRLF tolerance and uses trimmed-line equality for the `---`
* delimiters so whitespace-padded delimiter lines are accepted.
*/
function parseFrontmatter(content) {
const lines = content.split(/\r?\n/);
let openIdx = -1;
let closeIdx = -1;
for (let i = 0; i < lines.length; i += 1) {
if (lines[i].trim() === '---') {
if (openIdx === -1) openIdx = i;
else { closeIdx = i; break; }
}
}
assert.ok(openIdx !== -1 && closeIdx !== -1, 'frontmatter block must be delimited by --- on its own lines');
const fm = {};
for (const line of lines.slice(openIdx + 1, closeIdx)) {
const m = line.match(/^([A-Za-z][A-Za-z0-9_-]*):\s*(.*)$/);
if (!m) continue;
const [, key, raw] = m;
const value = raw.trim().replace(/^["']|["']$/g, '');
fm[key] = value;
}
fm._body = lines.slice(closeIdx + 1).join('\n');
return fm;
}
function readNamespaceFile(file) {
const filePath = path.join(COMMANDS_DIR, file);
assert.ok(fs.existsSync(filePath), `${file} must exist at ${filePath}`);
return { filePath, ...parseFrontmatter(fs.readFileSync(filePath, 'utf-8')) };
}
// ── Frontmatter contract ───────────────────────────────────────────────
describe('Namespace skill files exist with correct name', () => {
for (const { file, name } of NAMESPACE_SKILLS) {
test(`${file} — name field is hyphen-form ${name}`, () => {
const fm = readNamespaceFile(file);
assert.strictEqual(
fm.name,
name,
`name: in ${file} must be ${name} (hyphen form per #2858), got: ${fm.name}`,
);
});
}
});
describe('Namespace skill descriptions are keyword-tag format', () => {
for (const { file } of NAMESPACE_SKILLS) {
test(`${file} — description ≤ 60 chars`, () => {
const fm = readNamespaceFile(file);
assert.ok(
fm.description.length <= 60,
`${file} description must be ≤ 60 chars, got ${fm.description.length}: ${fm.description}`,
);
});
test(`${file} — description contains a pipe separator`, () => {
const fm = readNamespaceFile(file);
assert.ok(
fm.description.includes('|'),
`${file} description must contain | pipe separator, got: ${fm.description}`,
);
});
test(`${file} — description does not start with prose ("Use " / "This skill")`, () => {
const { description } = readNamespaceFile(file);
assert.ok(
!description.startsWith('Use ') && !description.startsWith('This skill'),
`${file} description must not start with "Use " or "This skill", got: ${description}`,
);
});
}
});
// ── allowed-tools must include Skill ──────────────────────────────────
describe('Namespace skills permit Skill execution', () => {
for (const { file } of NAMESPACE_SKILLS) {
test(`${file} — allowed-tools includes Skill`, () => {
const filePath = path.join(COMMANDS_DIR, file);
const raw = fs.readFileSync(filePath, 'utf-8');
const lines = raw.split(/\r?\n/);
const startIdx = lines.findIndex((l) => l.trim() === 'allowed-tools:');
assert.ok(startIdx !== -1, `${file} must declare an allowed-tools block`);
const tools = [];
for (let i = startIdx + 1; i < lines.length; i += 1) {
const m = lines[i].match(/^\s+-\s+(\S+)/);
if (!m) break;
tools.push(m[1]);
}
assert.ok(
tools.includes('Skill'),
`${file} body invokes the Skill tool but allowed-tools does not include Skill (got: ${tools.join(', ')})`,
);
});
}
});
// ── Body contains routing table ───────────────────────────────────────
describe('Namespace skill bodies carry a routing table', () => {
for (const { file } of NAMESPACE_SKILLS) {
test(`${file} — body contains "| User wants" table header`, () => {
const fm = readNamespaceFile(file);
const lines = fm._body.split('\n');
const hasHeader = lines.some((l) => l.includes('| User wants'));
assert.ok(hasHeader, `${file} body must contain a routing table starting with "| User wants"`);
});
test(`${file} — body has at least one Invoke target`, () => {
const fm = readNamespaceFile(file);
const hasInvoke = /\bgsd-[a-z-]+/i.test(fm._body);
assert.ok(hasInvoke, `${file} body must reference at least one gsd-* sub-skill`);
});
}
});
// ── Context guard contract on gsd-health ──────────────────────────────
// Asserts the `--context` surface promised by #2792 is wired through to
// both the command frontmatter and the workflow body. The classifier
// itself is covered by tests/context-utilization.test.cjs and the SDK
// CLI by tests/validate-context.test.cjs.
describe('gsd-health --context flag is wired into command + workflow', () => {
const HEALTH_CMD = path.join(COMMANDS_DIR, 'health.md');
const HEALTH_WORKFLOW = path.join(__dirname, '..', 'gsd-core', 'workflows', 'health.md');
test('commands/gsd/health.md argument-hint advertises --context', () => {
const raw = fs.readFileSync(HEALTH_CMD, 'utf-8');
const fm = parseFrontmatter(raw);
assert.ok(
fm['argument-hint'] && fm['argument-hint'].includes('--context'),
`health.md argument-hint must include --context, got: ${fm['argument-hint']}`,
);
});
test('commands/gsd/health.md body documents the three-state utilization table', () => {
const raw = fs.readFileSync(HEALTH_CMD, 'utf-8');
const body = parseFrontmatter(raw)._body.toLowerCase();
assert.ok(body.includes('healthy'), 'body must name the healthy state');
assert.ok(body.includes('warning'), 'body must name the warning state');
assert.ok(body.includes('critical'), 'body must name the critical state');
assert.ok(
body.includes('60%') && body.includes('70%'),
'body must reference the 60% and 70% threshold boundaries',
);
});
test('gsd-core/workflows/health.md has a context_check step', () => {
const raw = fs.readFileSync(HEALTH_WORKFLOW, 'utf-8');
assert.match(
raw,
/<step name="context_check">/,
'workflow must define a <step name="context_check"> branch',
);
});
test('workflow context_check invokes gsd-sdk query validate.context', () => {
const raw = fs.readFileSync(HEALTH_WORKFLOW, 'utf-8');
// Extract just the context_check step's body so a stray reference
// elsewhere in the file can't satisfy this assertion.
const stepMatch = raw.match(/<step name="context_check">([\s\S]*?)<\/step>/);
assert.ok(stepMatch, 'context_check step must be a closed <step>...</step> block');
const stepBody = stepMatch[1];
// After #3797 architectural fix, callsites use gsd_run
assert.match(
stepBody,
/gsd_run\s+query\s+validate\.context/,
'context_check must call `gsd_run query validate.context`',
);
assert.match(stepBody, /--tokens-used/, 'context_check must pass --tokens-used');
assert.match(stepBody, /--context-window/, 'context_check must pass --context-window');
});
});
// ── Cross-reference: every routed sub-skill must exist ─────────────────
// This is the regression guard the original PR lacked. Without it,
// post-#2790 consolidations can quietly invalidate router targets again.
describe('Namespace router targets resolve to surviving skills', () => {
// Build the post-consolidation surviving set once.
const surviving = new Set();
for (const f of fs.readdirSync(COMMANDS_DIR)) {
if (!f.endsWith('.md')) continue;
const base = f.replace(/\.md$/, '');
if (base.startsWith('ns-')) continue; // namespace routers themselves
surviving.add(`gsd-${base}`);
// The PR #2858 rename canonicalized extract_learnings → extract-learnings.
// Until #2790 rebases onto current main, accept either source filename
// as resolving to the canonical hyphenated identifier.
if (base === 'extract_learnings') surviving.add('gsd-extract-learnings');
}
for (const { file } of NAMESPACE_SKILLS) {
test(`${file} — every routing target resolves`, () => {
const fm = readNamespaceFile(file);
// Extract every gsd-<name> token that appears in a table-row right column.
// Strip flag suffixes (`gsd-foo --bar` → `gsd-foo`) before resolving.
const targets = new Set();
for (const line of fm._body.split('\n')) {
// Only consider markdown table data rows: lines that start with `|`
// and have content between pipes. Skip header / separator rows.
if (!line.startsWith('|') || /^\|[\s\-:|]+\|?\s*$/.test(line)) continue;
const cells = line.split('|').map((c) => c.trim()).filter(Boolean);
if (cells.length < 2) continue;
for (const m of cells[cells.length - 1].matchAll(/\bgsd-[a-z][a-z0-9-]*/g)) {
targets.add(m[0]);
}
}
assert.ok(targets.size > 0, `${file} routing table must reference at least one gsd-* target`);
const unresolved = [...targets].filter(
(t) => !surviving.has(t) && !FLAG_FORM_PARENTS.has(t),
);
assert.deepStrictEqual(
unresolved,
[],
`${file} routes to skills that don't exist in commands/gsd/: ${unresolved.join(', ')}`,
);
});
}
});