* 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>
248 lines
13 KiB
JavaScript
248 lines
13 KiB
JavaScript
'use strict';
|
|
|
|
// allow-test-rule: source-text-is-the-product. profile-user.md IS the
|
|
// shipped workflow product; the `Display:` line at line 356 IS the
|
|
// user-visible artifact-name message. This test parses the markdown's
|
|
// structured `Display: "..."` line via a regex (not source-grep) to
|
|
// extract the path argument as a typed value, then asserts on the
|
|
// typed value. The .includes() at the end is a structural absence-check
|
|
// against the legacy path literal — the same shape the bug-2470
|
|
// installer-leak test uses to enforce a known-pattern invariant.
|
|
|
|
process.env.GSD_TEST_MODE = '1';
|
|
|
|
/**
|
|
* Bug #2973: /gsd-profile-user --refresh writes dev-preferences.md to the
|
|
* legacy commands/gsd subdirectory, contradicting v1.39.0's skills-only
|
|
* migration claim that "Legacy commands/gsd directory removed
|
|
* (replaced by skills/)".
|
|
*
|
|
* Root cause: the writer at gsd-core/bin/lib/profile-output.cjs
|
|
* fell back to commands/gsd/dev-preferences.md when no --output was passed.
|
|
* The /gsd-profile-user workflow does not pass --output, so every refresh
|
|
* deterministically re-creates the legacy directory.
|
|
*
|
|
* Fix:
|
|
* 1. profile-output.cjs default targets skills/gsd-dev-preferences/SKILL.md
|
|
* 2. profile-user.md confirmation message references the new path
|
|
* 3. install.js migrates any existing legacy file into the new skill
|
|
* location during install (no-op if SKILL.md already exists)
|
|
*
|
|
* This test exercises the runtime behavior of the writer (writes to the
|
|
* skills path) and the structural shape of the workflow message. No
|
|
* source-grep on the .cjs body — assertions go against the writer's
|
|
* actual output and the parsed workflow message.
|
|
*/
|
|
|
|
const { test, describe } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const os = require('node:os');
|
|
|
|
const { cleanup } = require('./helpers.cjs');
|
|
|
|
const ROOT = path.join(__dirname, '..');
|
|
const PROFILE_OUTPUT = path.join(ROOT, 'gsd-core', 'bin', 'lib', 'profile-output.cjs');
|
|
const WORKFLOW = path.join(ROOT, 'gsd-core', 'workflows', 'profile-user.md');
|
|
const INSTALL = path.join(ROOT, 'bin', 'install.js');
|
|
|
|
describe('Bug #2973: dev-preferences default writer path is skills/gsd-dev-preferences/SKILL.md', () => {
|
|
test('exercise the writer in a subprocess with HOME pointed at a tmp dir; assert the artifact lands at the skills path', () => {
|
|
// Subprocess so fs.writeSync(1, ...) in core.cjs goes to a pipe we can
|
|
// capture (the parent process's fd 1 bypasses any in-process stubbing).
|
|
const cp = require('node:child_process');
|
|
const tmpHome = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-2973-'));
|
|
try {
|
|
const analysisPath = path.join(tmpHome, 'analysis.json');
|
|
fs.writeFileSync(analysisPath, JSON.stringify({
|
|
data_source: 'questionnaire',
|
|
dimensions: { rigor: { score: 7 } },
|
|
}));
|
|
const driver = path.join(tmpHome, 'driver.js');
|
|
fs.writeFileSync(driver, `
|
|
const m = require(${JSON.stringify(PROFILE_OUTPUT)});
|
|
m.cmdGenerateDevPreferences(${JSON.stringify(tmpHome)}, { analysis: ${JSON.stringify(analysisPath)} }, false);
|
|
`);
|
|
const result = cp.spawnSync(process.execPath, [driver], {
|
|
env: Object.assign({}, process.env, { HOME: tmpHome, USERPROFILE: tmpHome }),
|
|
encoding: 'utf-8',
|
|
// Bound the subprocess so a regression that hangs the writer
|
|
// (or the dispatcher) cannot deadlock CI (PR #3003 CR feedback).
|
|
// 30s is generous for what should complete in <1s; if it trips,
|
|
// surface that as a clear test failure rather than CI hanging.
|
|
timeout: 30_000,
|
|
});
|
|
assert.equal(result.signal, null,
|
|
`writer subprocess was killed by signal ${result.signal} (likely timeout): ${result.stderr}`);
|
|
assert.equal(result.status, 0, `writer subprocess failed: ${result.stderr}`);
|
|
const parsed = JSON.parse(result.stdout);
|
|
|
|
const expectedPath = path.join(tmpHome, '.claude', 'skills', 'gsd-dev-preferences', 'SKILL.md');
|
|
assert.equal(parsed.command_path, expectedPath,
|
|
`writer emitted ${parsed.command_path}; expected skills path ${expectedPath} (#2973)`);
|
|
assert.equal(fs.existsSync(expectedPath), true,
|
|
`expected SKILL.md at ${expectedPath} after writer ran`);
|
|
const legacyPath = path.join(tmpHome, '.claude', 'commands', 'gsd', 'dev-preferences.md');
|
|
assert.equal(fs.existsSync(legacyPath), false,
|
|
`writer must not create ${legacyPath} (#2973)`);
|
|
} finally {
|
|
cleanup(tmpHome);
|
|
}
|
|
});
|
|
});
|
|
|
|
describe('Bug #2973: profile-user.md confirmation message references the skills path', () => {
|
|
test('the Display message points at $HOME/.claude/skills/gsd-dev-preferences/SKILL.md', () => {
|
|
const md = fs.readFileSync(WORKFLOW, 'utf-8');
|
|
// Match the structured Display: line; capture the path value.
|
|
const m = md.match(/Display:\s*"[^"]*Generated\s*\/gsd-dev-preferences\s*at\s*([^"]+)"/);
|
|
assert.notEqual(m, null, 'expected a Display: "Generated /gsd-dev-preferences at <path>" line');
|
|
const referencedPath = m[1].trim();
|
|
assert.equal(referencedPath, '$HOME/.claude/skills/gsd-dev-preferences/SKILL.md',
|
|
`workflow references ${referencedPath}; expected skills path (#2973)`);
|
|
});
|
|
|
|
test('no occurrence of the legacy commands/gsd/dev-preferences.md path remains in profile-user.md', () => {
|
|
const md = fs.readFileSync(WORKFLOW, 'utf-8');
|
|
assert.equal(md.includes('commands/gsd/dev-preferences.md'), false,
|
|
'profile-user.md still references legacy commands/gsd/dev-preferences.md (#2973)');
|
|
});
|
|
});
|
|
|
|
describe('Bug #2973: installer migrates existing legacy dev-preferences.md to skills/gsd-dev-preferences/SKILL.md', () => {
|
|
test('migrateLegacyDevPreferencesToSkill is exported and writes to the skills path', () => {
|
|
const inst = require(INSTALL);
|
|
// Module exports the migration helper for direct testing.
|
|
// Note: this is the structural assertion — the helper exists with the
|
|
// documented signature. End-to-end install testing is covered by
|
|
// tests/install-*.test.cjs which already exercise legacy preservation.
|
|
assert.equal(typeof inst.migrateLegacyDevPreferencesToSkill, 'function',
|
|
'expected migrateLegacyDevPreferencesToSkill in install.js exports (#2973)');
|
|
});
|
|
|
|
test('migration writes to skills/gsd-dev-preferences/SKILL.md when no skill exists yet', () => {
|
|
const tmpDir = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-2973-mig-'));
|
|
try {
|
|
const inst = require(INSTALL);
|
|
const saved = new Map([['dev-preferences.md', '# my legacy preferences\n']]);
|
|
const migrated = inst.migrateLegacyDevPreferencesToSkill(tmpDir, saved);
|
|
assert.equal(migrated, true, 'expected migration to succeed when no SKILL.md exists');
|
|
const skillFile = path.join(tmpDir, 'skills', 'gsd-dev-preferences', 'SKILL.md');
|
|
assert.equal(fs.existsSync(skillFile), true, `expected SKILL.md at ${skillFile}`);
|
|
assert.equal(fs.readFileSync(skillFile, 'utf-8'), '# my legacy preferences\n');
|
|
} finally {
|
|
cleanup(tmpDir);
|
|
}
|
|
});
|
|
|
|
test('migration is a no-op when a SKILL.md already exists at the new location (do not clobber user-customized skill content)', () => {
|
|
const tmpDir = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-2973-skip-'));
|
|
try {
|
|
const inst = require(INSTALL);
|
|
const skillDir = path.join(tmpDir, 'skills', 'gsd-dev-preferences');
|
|
const skillFile = path.join(skillDir, 'SKILL.md');
|
|
fs.mkdirSync(skillDir, { recursive: true });
|
|
fs.writeFileSync(skillFile, '# user-customized skill\n');
|
|
const saved = new Map([['dev-preferences.md', '# legacy content\n']]);
|
|
const migrated = inst.migrateLegacyDevPreferencesToSkill(tmpDir, saved);
|
|
assert.equal(migrated, false, 'expected migration to skip when SKILL.md exists');
|
|
// Existing content untouched.
|
|
assert.equal(fs.readFileSync(skillFile, 'utf-8'), '# user-customized skill\n');
|
|
} finally {
|
|
cleanup(tmpDir);
|
|
}
|
|
});
|
|
});
|
|
|
|
// ─── #3003 CR follow-up: installRuntimeArtifacts preserves user-owned skills ──
|
|
//
|
|
// Production install() calls installRuntimeArtifacts() without a prior
|
|
// uninstallRuntimeArtifacts(). This means _copyStaged overlays new skills
|
|
// on top of the existing skills/ directory — it does NOT wipe first.
|
|
// As a result, user-owned gsd-dev-preferences/SKILL.md is preserved across
|
|
// a plain install because _copyStaged only cpSync's newly staged skill dirs.
|
|
//
|
|
// NOTE: If callers run uninstallRuntimeArtifacts() before installRuntimeArtifacts()
|
|
// (e.g. full reinstall), gsd-dev-preferences IS wiped by uninstall and NOT
|
|
// restored by install (#3664 production gap — tracked separately).
|
|
|
|
describe('Bug #2973 (#3003 CR): installRuntimeArtifacts preserves user-owned gsd-dev-preferences across install', () => {
|
|
test('user-customized skills/gsd-dev-preferences/SKILL.md survives a plain install (no pre-uninstall)', () => {
|
|
// Production install() does NOT call uninstallRuntimeArtifacts() first.
|
|
// installRuntimeArtifacts → _copyStaged overlays only staged skill dirs;
|
|
// gsd-dev-preferences (not in source) is left untouched.
|
|
const inst = require(INSTALL);
|
|
const { loadSkillsManifest, resolveProfile } = require(path.join(ROOT, 'gsd-core', 'bin', 'lib', 'install-profiles.cjs'));
|
|
const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-2973-wipe-'));
|
|
try {
|
|
const configDir = path.join(tmp, 'config');
|
|
fs.mkdirSync(configDir, { recursive: true });
|
|
|
|
// Set up a minimal source dir (plan-phase only; no dev-preferences).
|
|
const srcDir = path.join(tmp, 'src-commands');
|
|
fs.mkdirSync(srcDir, { recursive: true });
|
|
fs.writeFileSync(path.join(srcDir, 'plan-phase.md'), '---\nname: gsd:plan-phase\ndescription: Plan\n---\n\nPlan body.\n');
|
|
fs.writeFileSync(path.join(configDir, '.gsd-source'), srcDir + '\n');
|
|
|
|
const skillsDir = path.join(configDir, 'skills');
|
|
const userSkillDir = path.join(skillsDir, 'gsd-dev-preferences');
|
|
fs.mkdirSync(userSkillDir, { recursive: true });
|
|
const userContent = '# my customized dev preferences\n\nstack: rust\n';
|
|
fs.writeFileSync(path.join(userSkillDir, 'SKILL.md'), userContent);
|
|
|
|
// Plain install (matching production install() call site).
|
|
const manifest = loadSkillsManifest();
|
|
const resolvedProfile = resolveProfile({ modes: [], manifest });
|
|
inst.installRuntimeArtifacts('claude', configDir, 'global', resolvedProfile);
|
|
|
|
const skillFile = path.join(userSkillDir, 'SKILL.md');
|
|
assert.equal(fs.existsSync(skillFile), true,
|
|
'gsd-dev-preferences/SKILL.md must survive a plain install (#3003 CR)');
|
|
assert.equal(fs.readFileSync(skillFile, 'utf-8'), userContent,
|
|
'user content must be byte-identical after the install');
|
|
} finally {
|
|
cleanup(tmp);
|
|
}
|
|
});
|
|
|
|
test('non-user-owned gsd-* skills are wiped and recreated via uninstall+install cycle', () => {
|
|
// Stale artifacts (e.g. STALE-MARKER.txt left from a previous version)
|
|
// are removed when the caller runs uninstallRuntimeArtifacts() before
|
|
// installRuntimeArtifacts() — the full uninstall+reinstall cycle.
|
|
// uninstallRuntimeArtifacts removes all gsd-* entries; installRuntimeArtifacts
|
|
// then writes fresh ones from source.
|
|
const inst = require(INSTALL);
|
|
const { loadSkillsManifest, resolveProfile } = require(path.join(ROOT, 'gsd-core', 'bin', 'lib', 'install-profiles.cjs'));
|
|
const tmp = fs.mkdtempSync(path.join(os.tmpdir(), 'gsd-2973-wipe-shipped-'));
|
|
try {
|
|
const configDir = path.join(tmp, 'config');
|
|
fs.mkdirSync(configDir, { recursive: true });
|
|
|
|
const srcDir = path.join(tmp, 'src-commands');
|
|
fs.mkdirSync(srcDir, { recursive: true });
|
|
fs.writeFileSync(path.join(srcDir, 'plan-phase.md'), '---\nname: gsd:plan-phase\ndescription: Plan fresh\n---\n\nFresh body.\n');
|
|
fs.writeFileSync(path.join(configDir, '.gsd-source'), srcDir + '\n');
|
|
|
|
const skillsDir = path.join(configDir, 'skills');
|
|
const staleSkillDir = path.join(skillsDir, 'gsd-plan-phase');
|
|
fs.mkdirSync(staleSkillDir, { recursive: true });
|
|
fs.writeFileSync(path.join(staleSkillDir, 'STALE-MARKER.txt'), 'wipe me');
|
|
|
|
const manifest = loadSkillsManifest();
|
|
const resolvedProfile = resolveProfile({ modes: [], manifest });
|
|
|
|
// Full uninstall+install cycle (e.g. --reinstall flow)
|
|
inst.uninstallRuntimeArtifacts('claude', configDir, 'global');
|
|
inst.installRuntimeArtifacts('claude', configDir, 'global', resolvedProfile);
|
|
|
|
assert.equal(fs.existsSync(path.join(staleSkillDir, 'STALE-MARKER.txt')), false,
|
|
'stale shipped-skill content must be wiped by uninstall (preservation is opt-in by name)');
|
|
assert.equal(fs.existsSync(path.join(staleSkillDir, 'SKILL.md')), true,
|
|
'fresh SKILL.md from source must be installed after wipe');
|
|
} finally {
|
|
cleanup(tmp);
|
|
}
|
|
});
|
|
});
|