Files
msd-core/tests/bug-571-doc-writer-fix-mode-edit-only.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

201 lines
8.7 KiB
JavaScript

/**
* Regression tests for bug #571
*
* gsd-doc-writer in fix mode used the Write tool (whole-file replace) instead
* of the Edit tool (surgical replacement) when correcting specific failing
* claims. When the target doc was generated but not yet committed, Write could
* truncate the file to a single line with no git recovery path.
*
* Fix 1 (agent): Add Edit to the tools frontmatter and rewrite fix_mode
* instructions to mandate Edit and explicitly forbid Write on existing files.
* Fix 2 (workflow): Add a post-fix line-count guard in fix_loop that detects
* >90% shrinkage and restores the file from existing_content.
*/
'use strict';
// allow-test-rule: source-text-is-the-product
// Agent .md files are the installed AI agents — their frontmatter and body IS
// what the runtime loads. Checking text content IS checking the deployed contract.
const { test, describe } = require('node:test');
const assert = require('node:assert/strict');
const fs = require('fs');
const path = require('path');
const AGENTS_DIR = path.join(__dirname, '..', 'agents');
const WORKFLOWS_DIR = path.join(__dirname, '..', 'gsd-core', 'workflows');
const AGENT_PATH = path.join(AGENTS_DIR, 'gsd-doc-writer.md');
const WORKFLOW_PATH = path.join(WORKFLOWS_DIR, 'docs-update.md');
// ─── Agent fix: Edit in tools frontmatter ────────────────────────────────────
describe('bug #571: gsd-doc-writer agent', () => {
const content = fs.readFileSync(AGENT_PATH, 'utf-8');
test('agent file exists', () => {
assert.ok(fs.existsSync(AGENT_PATH), 'agents/gsd-doc-writer.md must exist');
});
test('tools frontmatter includes Edit', () => {
const toolsMatch = content.match(/^tools:\s*(.+)$/m);
assert.ok(toolsMatch, 'gsd-doc-writer.md must have a tools: frontmatter line');
assert.ok(
toolsMatch[1].includes('Edit'),
'tools: frontmatter must include Edit so fix mode can make surgical replacements (#571)'
);
});
// ─── fix_mode instructions ────────────────────────────────────────────────
describe('fix_mode block', () => {
const fixStart = content.indexOf('<fix_mode>');
const fixEnd = content.indexOf('</fix_mode>', fixStart);
assert.ok(fixStart !== -1 && fixEnd !== -1, '<fix_mode> block must be present and complete');
const fixBlock = content.slice(fixStart, fixEnd);
test('fix_mode mandates Edit for corrections', () => {
assert.ok(
fixBlock.includes('Edit'),
'fix_mode must instruct the agent to use the Edit tool for surgical corrections (#571)'
);
});
test('fix_mode explicitly forbids Write on existing files', () => {
assert.ok(
fixBlock.includes('NEVER use the Write tool') || fixBlock.includes('NEVER call Write'),
'fix_mode must explicitly forbid Write on existing files — Write replaces the whole file (#571)'
);
});
test('fix_mode mentions unrecoverable data loss risk of Write', () => {
assert.ok(
fixBlock.includes('untracked') || fixBlock.includes('context window') || fixBlock.includes('permanently destroyed'),
'fix_mode must explain WHY Write is forbidden — unrecoverable data loss for untracked files (#571)'
);
});
});
// ─── critical_rules ───────────────────────────────────────────────────────
describe('critical_rules block', () => {
const rulesStart = content.indexOf('<critical_rules>');
const rulesEnd = content.indexOf('</critical_rules>', rulesStart);
assert.ok(rulesStart !== -1 && rulesEnd !== -1, '<critical_rules> block must be present and complete');
const rulesBlock = content.slice(rulesStart, rulesEnd);
test('critical_rules forbids Write in fix mode', () => {
assert.ok(
rulesBlock.includes('fix mode') && (rulesBlock.includes('NEVER call Write') || rulesBlock.includes('NEVER use the Write')),
'critical_rules must explicitly forbid Write in fix mode (#571)'
);
});
test('critical_rules Edit rule appears before success_criteria', () => {
const rulesIdx = content.indexOf('<critical_rules>');
const successIdx = content.indexOf('<success_criteria>');
assert.ok(rulesIdx !== -1 && successIdx !== -1, 'both <critical_rules> and <success_criteria> must exist');
assert.ok(
rulesIdx < successIdx,
'<critical_rules> must appear before <success_criteria> (#571)'
);
});
});
});
// ─── Workflow fix: post-fix truncation guard in fix_loop ─────────────────────
describe('bug #571: docs-update workflow fix_loop', () => {
const content = fs.readFileSync(WORKFLOW_PATH, 'utf-8');
test('workflow file exists', () => {
assert.ok(fs.existsSync(WORKFLOW_PATH), 'gsd-core/workflows/docs-update.md must exist');
});
describe('fix_loop step', () => {
const loopStart = content.indexOf('<step name="fix_loop">');
const loopEnd = content.indexOf('</step>', loopStart);
assert.ok(loopStart !== -1 && loopEnd !== -1, 'fix_loop step must be present and complete');
const loopBlock = content.slice(loopStart, loopEnd);
test('fix_loop captures pre-fix line count', () => {
assert.ok(
loopBlock.includes('PRE_FIX_LINES') || loopBlock.includes('pre-fix line'),
'fix_loop must capture the pre-fix line count to detect truncation (#571)'
);
});
test('fix_loop checks post-fix line count', () => {
assert.ok(
loopBlock.includes('POST_FIX_LINES') || loopBlock.includes('post-fix line'),
'fix_loop must check the post-fix line count to detect truncation (#571)'
);
});
test('fix_loop restores file on truncation detection', () => {
assert.ok(
loopBlock.includes('Restore') || loopBlock.includes('restore'),
'fix_loop must restore the file from existing_content when truncation is detected (#571)'
);
});
test('fix_loop truncation threshold is >90% shrinkage', () => {
assert.ok(
loopBlock.includes('90%') || loopBlock.includes('10%'),
'fix_loop must use a >90% shrinkage threshold (10% of original) to detect truncation (#571)'
);
});
test('fix_loop logs a WARNING on truncation', () => {
assert.ok(
loopBlock.includes('WARNING') || loopBlock.includes('corrupted'),
'fix_loop must log a WARNING when truncation is detected and restored (#571)'
);
});
// Structural ordering: PRE check → fix agent runs → POST check → restore
// These ensure the guard is wired in the right sequence, not just present.
test('PRE_FIX_LINES is captured before POST_FIX_LINES (correct ordering)', () => {
const preIdx = loopBlock.indexOf('PRE_FIX_LINES');
const postIdx = loopBlock.indexOf('POST_FIX_LINES');
assert.ok(preIdx !== -1 && postIdx !== -1, 'both PRE_FIX_LINES and POST_FIX_LINES must be present (#571)');
assert.ok(
preIdx < postIdx,
'PRE_FIX_LINES must appear before POST_FIX_LINES — pre-capture must happen before post-check (#571)'
);
});
test('restore instruction appears after POST_FIX_LINES check (correct ordering)', () => {
const postIdx = loopBlock.indexOf('POST_FIX_LINES');
// Find the restore instruction — it follows the threshold comparison
const restoreIdx = loopBlock.indexOf('existing_content', postIdx);
assert.ok(
restoreIdx !== -1 && restoreIdx > postIdx,
'restore-from-existing_content instruction must appear after the POST_FIX_LINES check (#571)'
);
});
test('fix_loop doc path is quoted in shell snippets', () => {
// Unquoted paths break on filenames with spaces or shell metacharacters.
// Verify the bash snippets use quoted "{doc_path}" not bare {doc_path}.
assert.ok(
loopBlock.includes('< "{doc_path}"') || loopBlock.includes("<\"{doc_path}\""),
'shell redirections must quote {doc_path} to handle paths with spaces (#571)'
);
});
test('corrupted doc is still re-verified (not silently skipped)', () => {
// The restored doc must be included in step 2 re-verification so its
// failures are counted and reported. It should only be excluded from
// receiving another fix attempt, not from verification.
const restoreIdx = loopBlock.indexOf('existing_content', loopBlock.indexOf('POST_FIX_LINES'));
const reVerifyIdx = loopBlock.indexOf('re-verify', restoreIdx);
assert.ok(
reVerifyIdx !== -1,
'fix_loop must include re-verification after truncation restore (corrupted docs still have failures) (#571)'
);
});
});
});