* 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>
144 lines
6.4 KiB
JavaScript
144 lines
6.4 KiB
JavaScript
'use strict';
|
|
|
|
// allow-test-rule: source-text-is-the-product
|
|
// Reads gsd-core/workflows/fast.md whose deployed text IS the product —
|
|
// the workflow markdown is executed verbatim by LLM runtimes.
|
|
|
|
/**
|
|
* #3805 — fast.md log_to_state appends a schema-blind 4-column row to the
|
|
* 5-column "Quick Tasks Completed" table created by quick.md Step 7.
|
|
*
|
|
* quick.md Step 7 creates the table with 5 columns:
|
|
* | # | Description | Date | Commit | Directory |
|
|
*
|
|
* Before this fix, fast.md's log_to_state step appended a hardcoded 4-cell
|
|
* row unconditionally:
|
|
* echo "| $(date +%Y-%m-%d) | fast | $TASK | ✅ |" >> .planning/STATE.md
|
|
*
|
|
* This produces malformed Markdown when the existing table has a different
|
|
* column count.
|
|
*
|
|
* Covers:
|
|
* - fast.md does NOT contain the hardcoded 4-cell echo template
|
|
* - fast.md log_to_state step reads/introspects the existing table header
|
|
* before appending (schema-aware insertion)
|
|
* - fast.md log_to_state step matches the 5-column schema from quick.md
|
|
* Step 7 when that table is present
|
|
* - fast.md log_to_state step skips (does not corrupt) the STATE.md write
|
|
* when the table schema is unrecognized
|
|
*/
|
|
|
|
const { test, describe } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
|
|
const REPO_ROOT = path.join(__dirname, '..');
|
|
const FAST_MD_PATH = path.join(REPO_ROOT, 'gsd-core', 'workflows', 'fast.md');
|
|
|
|
// The 5-column schema defined in quick.md Step 7 (non-validate mode).
|
|
// Column count is 5: # | Description | Date | Commit | Directory
|
|
// Named constant for traceability — mirrors quick.md Step 7's table header.
|
|
const QUICK_MD_STEP7_COL_COUNT = 5;
|
|
const QUICK_MD_STEP7_COLUMNS = ['#', 'Description', 'Date', 'Commit', 'Directory'];
|
|
|
|
describe('bug #3805: fast.md log_to_state must be schema-aware', () => {
|
|
let fastMdContent;
|
|
|
|
test('fast.md workflow file exists and is readable', () => {
|
|
assert.ok(fs.existsSync(FAST_MD_PATH), `fast.md not found at ${FAST_MD_PATH}`);
|
|
fastMdContent = fs.readFileSync(FAST_MD_PATH, 'utf-8');
|
|
});
|
|
|
|
test('fast.md log_to_state step does NOT hardcode a 4-cell row template', () => {
|
|
// The old broken template: | date | fast | task | ✅ |
|
|
// This regex matches the exact hardcoded pattern that ignores table schema.
|
|
// A 4-cell row has exactly 4 pipe-delimited fields plus the surrounding pipes.
|
|
const hardcoded4CellPattern = /echo\s+["'][|][^|]*[|][^|]*[|][^|]*[|][^|]*[|]\s*["']/;
|
|
const match = fastMdContent.match(hardcoded4CellPattern);
|
|
assert.ok(
|
|
!match,
|
|
[
|
|
'fast.md log_to_state still contains the hardcoded 4-cell row template:',
|
|
` "${match?.[0]}"`,
|
|
'This appends a malformed row to the 5-column Quick Tasks Completed table',
|
|
'created by quick.md Step 7.',
|
|
`Expected table schema (${QUICK_MD_STEP7_COL_COUNT} cols): | ${QUICK_MD_STEP7_COLUMNS.join(' | ')} |`,
|
|
].join('\n')
|
|
);
|
|
});
|
|
|
|
test('fast.md log_to_state step reads the existing table header (schema introspection)', () => {
|
|
// The fix must inspect the existing STATE.md table header before appending.
|
|
// Acceptable signals: reading STATE.md content, grepping for the header line,
|
|
// or parsing columns from the header row.
|
|
const hasHeaderRead =
|
|
// Reads STATE.md to inspect it (awk/sed/grep on the file for header detection)
|
|
/grep.*Quick Tasks Completed.*STATE\.md/.test(fastMdContent) ||
|
|
/awk.*Quick Tasks Completed/.test(fastMdContent) ||
|
|
/sed.*Quick Tasks Completed/.test(fastMdContent) ||
|
|
// Reads the header line explicitly (head -n, sed -n, awk NR==)
|
|
/head\s+-n/.test(fastMdContent) && /STATE\.md/.test(fastMdContent) ||
|
|
// Counts pipe separators / columns from existing header
|
|
/col.*count|column.*count|count.*col|NF|awk.*\|/.test(fastMdContent) ||
|
|
// References schema detection in prose
|
|
/schema|header|column\s+count|existing.*table/.test(fastMdContent);
|
|
|
|
assert.ok(
|
|
hasHeaderRead,
|
|
[
|
|
'fast.md log_to_state step does not appear to introspect the existing table schema.',
|
|
'The step must read the STATE.md table header to detect column count before appending.',
|
|
'quick.md Step 7 uses schema-aware matching — fast.md must follow the same discipline.',
|
|
].join('\n')
|
|
);
|
|
});
|
|
|
|
test('fast.md log_to_state step references the 5-column quick.md schema', () => {
|
|
// The fix must handle the 5-col schema: | # | Description | Date | Commit | Directory |
|
|
// Test that all 5 column names appear in the log_to_state step's context.
|
|
// Extract the log_to_state step content to scope the check.
|
|
const logToStateMatch = fastMdContent.match(/<step name="log_to_state">([\s\S]*?)<\/step>/);
|
|
assert.ok(logToStateMatch, 'fast.md must contain a <step name="log_to_state"> element');
|
|
|
|
const stepContent = logToStateMatch[1];
|
|
|
|
// All 5 column names from quick.md Step 7 must be referenced in the step.
|
|
for (const col of QUICK_MD_STEP7_COLUMNS) {
|
|
assert.ok(
|
|
stepContent.toLowerCase().includes(col.toLowerCase()),
|
|
[
|
|
`fast.md log_to_state step does not reference column "${col}"`,
|
|
`Expected all 5 columns from quick.md Step 7: ${QUICK_MD_STEP7_COLUMNS.join(', ')}`,
|
|
`(${QUICK_MD_STEP7_COL_COUNT}-column schema)`,
|
|
].join('\n')
|
|
);
|
|
}
|
|
});
|
|
|
|
test('fast.md log_to_state step skips STATE.md write on unrecognized schema', () => {
|
|
// The fix must not blindly append when the table schema is unknown.
|
|
// Check for a guard that skips or logs rather than corrupting the file.
|
|
const logToStateMatch = fastMdContent.match(/<step name="log_to_state">([\s\S]*?)<\/step>/);
|
|
assert.ok(logToStateMatch, 'fast.md must contain a <step name="log_to_state"> element');
|
|
|
|
const stepContent = logToStateMatch[1];
|
|
|
|
// Must have a skip/guard path for unrecognized schemas
|
|
const hasSkipGuard =
|
|
/skip/i.test(stepContent) ||
|
|
/unrecognized|unknown|mismatch/i.test(stepContent) ||
|
|
/else\b/.test(stepContent) ||
|
|
/warn|log/i.test(stepContent);
|
|
|
|
assert.ok(
|
|
hasSkipGuard,
|
|
[
|
|
'fast.md log_to_state step does not appear to guard against unrecognized table schemas.',
|
|
'When the existing STATE.md table does not match an expected schema,',
|
|
'the step must skip the write (with a brief log) rather than append a malformed row.',
|
|
].join('\n')
|
|
);
|
|
});
|
|
});
|