* 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>
262 lines
10 KiB
JavaScript
262 lines
10 KiB
JavaScript
/**
|
|
* Tests for verification overrides reference document (#1747)
|
|
*
|
|
* Verifies that the verification-overrides.md reference exists, documents
|
|
* the YAML frontmatter override format, and is referenced by gsd-verifier.md.
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
const { test, describe } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
|
|
const ROOT = path.resolve(__dirname, '..');
|
|
|
|
describe('verification overrides reference (#1747)', () => {
|
|
|
|
// ── Reference document ────────────────────────────────────────────────────
|
|
|
|
describe('gsd-core/references/verification-overrides.md', () => {
|
|
const refPath = path.join(ROOT, 'gsd-core', 'references', 'verification-overrides.md');
|
|
let content;
|
|
|
|
test('file exists', () => {
|
|
assert.ok(fs.existsSync(refPath), 'verification-overrides.md should exist');
|
|
content = fs.readFileSync(refPath, 'utf-8');
|
|
});
|
|
|
|
test('contains Override Format section', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('## Override Format'),
|
|
'should contain an "Override Format" section'
|
|
);
|
|
});
|
|
|
|
test('contains Matching Rules section', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('## Matching Rules'),
|
|
'should contain a "Matching Rules" section'
|
|
);
|
|
});
|
|
|
|
test('contains Verifier Behavior section', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('## Verifier Behavior'),
|
|
'should contain a "Verifier Behavior" section'
|
|
);
|
|
});
|
|
|
|
test('documents YAML frontmatter overrides block with must_have field', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('overrides:') && content.includes('must_have:') && content.includes('reason:'),
|
|
'should document the YAML frontmatter format with overrides, must_have, and reason fields'
|
|
);
|
|
});
|
|
|
|
test('does not use criterion field (must use must_have)', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
// criterion: as a YAML field name should not appear; must_have: is the correct field
|
|
const lines = content.split('\n');
|
|
const criterionLines = lines.filter((l) => /^\s+criterion:/.test(l));
|
|
assert.strictEqual(
|
|
criterionLines.length,
|
|
0,
|
|
'should use must_have field, not criterion field'
|
|
);
|
|
});
|
|
|
|
test('documents required accepted_by field', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('accepted_by'),
|
|
'should document the accepted_by field'
|
|
);
|
|
});
|
|
|
|
test('documents required accepted_at field', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('accepted_at'),
|
|
'should document the accepted_at field'
|
|
);
|
|
});
|
|
|
|
test('marks accepted_by as required (not optional)', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
// The field table should list accepted_by as required, not optional
|
|
assert.ok(
|
|
content.includes('accepted_by') && content.includes('Required'),
|
|
'accepted_by should be described as a required field'
|
|
);
|
|
});
|
|
|
|
test('marks accepted_at as required (not optional)', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('accepted_at') && content.includes('Required'),
|
|
'accepted_at should be described as a required field'
|
|
);
|
|
});
|
|
|
|
test('describes fuzzy matching behavior', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('fuzzy matching') || content.includes('fuzzy-match'),
|
|
'should describe fuzzy matching for pairing overrides with must-haves'
|
|
);
|
|
});
|
|
|
|
test('describes case-insensitive matching', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.toLowerCase().includes('case-insensitive'),
|
|
'should describe case-insensitive matching'
|
|
);
|
|
});
|
|
|
|
test('describes 80% word overlap matching threshold', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('80%'),
|
|
'should describe 80% word overlap matching threshold'
|
|
);
|
|
});
|
|
|
|
test('does not use a threshold lower than 80%', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
// 60% threshold is too loose — should not appear as the matching threshold
|
|
assert.ok(
|
|
!content.includes('60% token overlap') && !content.includes('60% word overlap'),
|
|
'should not describe a 60% matching threshold (too loose — use 80%)'
|
|
);
|
|
});
|
|
|
|
test('documents PASSED (override) status', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('PASSED (override)'),
|
|
'should document the PASSED (override) status marker'
|
|
);
|
|
});
|
|
|
|
test('includes example VERIFICATION.md', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('## Example VERIFICATION.md'),
|
|
'should include an example VERIFICATION.md section'
|
|
);
|
|
});
|
|
|
|
test('documents When to Use guidance', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('## When to Use'),
|
|
'should contain a "When to Use" section'
|
|
);
|
|
});
|
|
|
|
test('documents When NOT to Use guardrails', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('When NOT to Use') || content.includes('NOT appropriate'),
|
|
'should contain guardrails explaining when overrides are not appropriate'
|
|
);
|
|
});
|
|
|
|
test('documents overrides_applied counter field', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('overrides_applied'),
|
|
'should document the overrides_applied counter field in frontmatter'
|
|
);
|
|
});
|
|
|
|
test('documents re-verification carryforward behavior', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('carry forward') || content.includes('carryforward') || content.includes('Re-verification') || content.includes('re-verification'),
|
|
'should document that overrides carry forward during re-verification'
|
|
);
|
|
});
|
|
|
|
test('documents milestone audit surfacing', () => {
|
|
content = content || fs.readFileSync(refPath, 'utf-8');
|
|
assert.ok(
|
|
content.includes('gsd-audit-milestone') || content.includes('audit-milestone') || content.includes('milestone'),
|
|
'should document that overrides are surfaced during milestone audit'
|
|
);
|
|
});
|
|
});
|
|
|
|
// ── Verifier agent reference ──────────────────────────────────────────────
|
|
|
|
describe('agents/gsd-verifier.md references overrides', () => {
|
|
const verifierPath = path.join(ROOT, 'agents', 'gsd-verifier.md');
|
|
let verifierContent;
|
|
|
|
test('gsd-verifier.md exists', () => {
|
|
assert.ok(fs.existsSync(verifierPath), 'gsd-verifier.md should exist');
|
|
verifierContent = fs.readFileSync(verifierPath, 'utf-8');
|
|
});
|
|
|
|
test('references verification-overrides.md in required_reading', () => {
|
|
verifierContent = verifierContent || fs.readFileSync(verifierPath, 'utf-8');
|
|
assert.ok(
|
|
verifierContent.includes('verification-overrides.md'),
|
|
'gsd-verifier.md should reference verification-overrides.md'
|
|
);
|
|
});
|
|
|
|
test('required_reading block is between </role> and <project_context>', () => {
|
|
verifierContent = verifierContent || fs.readFileSync(verifierPath, 'utf-8');
|
|
const roleEnd = verifierContent.indexOf('</role>');
|
|
const projectCtx = verifierContent.indexOf('<project_context>');
|
|
// Use regex to find the actual XML tag (on its own line), not backtick-escaped prose mentions
|
|
const reqMatch = verifierContent.match(/^<required_reading>/m);
|
|
const reqReading = reqMatch ? reqMatch.index : -1;
|
|
assert.ok(roleEnd > -1, '</role> tag should exist');
|
|
assert.ok(projectCtx > -1, '<project_context> tag should exist');
|
|
assert.ok(reqReading > -1, '<required_reading> tag should exist');
|
|
assert.ok(
|
|
reqReading > roleEnd && reqReading < projectCtx,
|
|
'<required_reading> should appear between </role> and <project_context>'
|
|
);
|
|
});
|
|
|
|
test('verifier includes Step 3b for override check before FAIL', () => {
|
|
verifierContent = verifierContent || fs.readFileSync(verifierPath, 'utf-8');
|
|
assert.ok(
|
|
verifierContent.includes('Step 3b'),
|
|
'gsd-verifier.md should include a Step 3b override check'
|
|
);
|
|
});
|
|
|
|
test('verifier Step 3b uses must_have field (not criterion)', () => {
|
|
verifierContent = verifierContent || fs.readFileSync(verifierPath, 'utf-8');
|
|
// Find the Step 3b section
|
|
const step3bStart = verifierContent.indexOf('## Step 3b');
|
|
assert.ok(step3bStart > -1, 'Step 3b section should exist');
|
|
const step3bEnd = verifierContent.indexOf('\n## Step 4', step3bStart);
|
|
const step3bSection = verifierContent.slice(step3bStart, step3bEnd > -1 ? step3bEnd : undefined);
|
|
assert.ok(
|
|
step3bSection.includes('must_have'),
|
|
'Step 3b should reference the must_have field'
|
|
);
|
|
});
|
|
|
|
test('verifier frontmatter template includes overrides_applied', () => {
|
|
verifierContent = verifierContent || fs.readFileSync(verifierPath, 'utf-8');
|
|
assert.ok(
|
|
verifierContent.includes('overrides_applied'),
|
|
'gsd-verifier.md frontmatter template should include overrides_applied counter'
|
|
);
|
|
});
|
|
});
|
|
});
|