* 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>
353 lines
14 KiB
JavaScript
Executable File
353 lines
14 KiB
JavaScript
Executable File
#!/usr/bin/env node
|
|
'use strict';
|
|
|
|
/**
|
|
* Deterministic verifier for the /gsd-reapply-patches Step 5 "Hunk Verification
|
|
* Gate". For each backed-up patch file, asserts that the user's added lines
|
|
* (computed from a real diff against the pristine baseline, not from the
|
|
* LLM's prose summary) survive into the merged output.
|
|
*
|
|
* Usage:
|
|
* node scripts/verify-reapply-patches.cjs \
|
|
* --patches-dir <path> \ # gsd-local-patches/
|
|
* --config-dir <path> \ # ~/.claude (or runtime equivalent)
|
|
* [--pristine-dir <path>] # gsd-pristine/; if absent, falls back to
|
|
* # treating every significant backup line as
|
|
* # required (over-broad but safe for #2969:
|
|
* # false-positive halts beat silent successes
|
|
* # on lost content)
|
|
* [--json] # emit JSON report instead of human text
|
|
*
|
|
* Exit codes:
|
|
* 0 — every user-added line is present in the merged file (gate passes)
|
|
* 1 — at least one missing line in at least one file (gate fails)
|
|
* 2 — usage / structural error (e.g. patches dir missing)
|
|
*
|
|
* Bug #2969: the Step 5 gate previously trusted Claude's free-text "verified:
|
|
* yes/no" reporting per hunk. The LLM was filling in `yes` even when content
|
|
* had been silently dropped. Moving the check to a deterministic script is the
|
|
* durability fix.
|
|
*/
|
|
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const crypto = require('node:crypto');
|
|
|
|
const SIGNIFICANT_MIN_CHARS = 12;
|
|
const GSD_HOOK_VERSION_LINE_RE = /^(?:\/\/|#)\s*gsd-hook-version:\s*\S+\s*$/i;
|
|
|
|
function parseArgs(argv) {
|
|
const opts = { patchesDir: null, configDir: null, pristineDir: null, json: false };
|
|
for (let i = 0; i < argv.length; i++) {
|
|
const arg = argv[i];
|
|
if (arg === '--patches-dir') opts.patchesDir = argv[++i];
|
|
else if (arg === '--config-dir') opts.configDir = argv[++i];
|
|
else if (arg === '--pristine-dir') opts.pristineDir = argv[++i];
|
|
else if (arg === '--json') opts.json = true;
|
|
else if (arg === '--help' || arg === '-h') {
|
|
process.stdout.write(
|
|
'usage: verify-reapply-patches.cjs --patches-dir <path> --config-dir <path> [--pristine-dir <path>] [--json]\n',
|
|
);
|
|
process.exit(0);
|
|
} else {
|
|
process.stderr.write(`unknown argument: ${arg}\n`);
|
|
process.exit(2);
|
|
}
|
|
}
|
|
return opts;
|
|
}
|
|
|
|
function isSignificantLine(line) {
|
|
const trimmed = line.trim();
|
|
if (trimmed.length < SIGNIFICANT_MIN_CHARS) return false;
|
|
// Pure punctuation / closing brackets carry too little structural info to
|
|
// reliably distinguish a survived hunk from incidental similarity.
|
|
if (/^[\s})\];,]+$/.test(trimmed)) return false;
|
|
// Generic decorative comments like `// ----` similarly fail the test.
|
|
if (/^[\s\-=#*/]+$/.test(trimmed)) return false;
|
|
return true;
|
|
}
|
|
|
|
function normalizeUpstreamOwnedLine(line) {
|
|
const trimmed = line.trim();
|
|
if (!trimmed) return line;
|
|
if (GSD_HOOK_VERSION_LINE_RE.test(trimmed)) {
|
|
const prefix = trimmed.startsWith('#') ? '#' : '//';
|
|
return `${prefix} gsd-hook-version: __GSD_VERSION_TOKEN__`;
|
|
}
|
|
return line;
|
|
}
|
|
|
|
/**
|
|
* Compute the SHA-256 hex digest of a string (UTF-8 encoded).
|
|
*/
|
|
function sha256(content) {
|
|
return crypto.createHash('sha256').update(content, 'utf8').digest('hex');
|
|
}
|
|
|
|
/**
|
|
* Read the `pristine_hashes` map from backup-meta.json in the patches dir.
|
|
* Returns an empty object if backup-meta.json is absent, unreadable, or has no
|
|
* `pristine_hashes` field — callers must treat an empty map as "no recorded
|
|
* hash for any file" (no hash-validation possible, not an error).
|
|
*/
|
|
function readPristineHashes(patchesDir) {
|
|
const metaPath = path.join(patchesDir, 'backup-meta.json');
|
|
try {
|
|
const raw = fs.readFileSync(metaPath, 'utf8');
|
|
const parsed = JSON.parse(raw);
|
|
if (parsed && typeof parsed.pristine_hashes === 'object' && parsed.pristine_hashes !== null) {
|
|
return parsed.pristine_hashes;
|
|
}
|
|
} catch {
|
|
// absent or unreadable — not an error, just no recorded hashes
|
|
}
|
|
return {};
|
|
}
|
|
|
|
/**
|
|
* Walk a directory, returning every file's path relative to the root.
|
|
*/
|
|
function walk(rootDir, relPrefix = '') {
|
|
const out = [];
|
|
if (!fs.existsSync(rootDir)) return out;
|
|
for (const entry of fs.readdirSync(rootDir, { withFileTypes: true })) {
|
|
const rel = relPrefix ? path.join(relPrefix, entry.name) : entry.name;
|
|
const abs = path.join(rootDir, entry.name);
|
|
if (entry.isDirectory()) {
|
|
out.push(...walk(abs, rel));
|
|
} else if (entry.isFile()) {
|
|
out.push(rel);
|
|
}
|
|
}
|
|
return out;
|
|
}
|
|
|
|
/**
|
|
* Compute the set of "user-added" lines: lines present in the backup but
|
|
* absent from the pristine baseline. If no pristine is provided, falls back
|
|
* to using every significant line in the backup (over-broad but safe — favours
|
|
* false-positive failures over silent successes, which is the right side to
|
|
* err on for #2969).
|
|
*/
|
|
function computeUserAddedLines(backupContent, pristineContent) {
|
|
const backupLines = backupContent.split(/\r?\n/);
|
|
if (!pristineContent) {
|
|
return backupLines.filter(isSignificantLine);
|
|
}
|
|
const pristineSet = new Set(
|
|
pristineContent.split(/\r?\n/).map(normalizeUpstreamOwnedLine),
|
|
);
|
|
return backupLines.filter((line) => {
|
|
if (!isSignificantLine(line)) return false;
|
|
return !pristineSet.has(normalizeUpstreamOwnedLine(line));
|
|
});
|
|
}
|
|
|
|
/**
|
|
* Stable reason codes for the per-file result. Tests assert via
|
|
* `assert.equal(result.reason, REASON.X)` rather than regex-matching prose,
|
|
* so the diagnostic surface is a typed enum, not free text.
|
|
*
|
|
* Adding a new reason requires updating the REASON map AND the tests'
|
|
* shape assertion that locks the documented set of codes.
|
|
*/
|
|
const REASON = Object.freeze({
|
|
OK_NO_USER_LINES_VS_PRISTINE: 'ok_no_user_lines_vs_pristine',
|
|
OK_NO_SIGNIFICANT_BACKUP_LINES: 'ok_no_significant_backup_lines',
|
|
// Bug #3657: the on-disk gsd-pristine/ file's SHA-256 does not match the
|
|
// hash recorded in backup-meta.json.pristine_hashes. This means the
|
|
// pristine snapshot was refreshed to a newer GSD version after the backup
|
|
// was captured. Using the wrong-version pristine as the diff baseline would
|
|
// invert the delta (upstream removals appear as "missing user lines").
|
|
// The verifier skips this file rather than false-failing it. A separate
|
|
// re-anchor step (or the git-aware fallback in the workflow) is needed to
|
|
// resolve this file; the guard here ensures the gate does not report spurious
|
|
// failures in the meantime.
|
|
OK_PRISTINE_DRIFT_DETECTED: 'ok_pristine_drift_detected',
|
|
FAIL_INSTALLED_MISSING: 'fail_installed_missing',
|
|
FAIL_INSTALLED_NOT_REGULAR_FILE: 'fail_installed_not_regular_file',
|
|
FAIL_READ_ERROR: 'fail_read_error',
|
|
FAIL_USER_LINES_MISSING: 'fail_user_lines_missing',
|
|
});
|
|
|
|
function verifyFile({ relPath, patchesDir, configDir, pristineDir, pristineHashes }) {
|
|
const backupPath = path.join(patchesDir, relPath);
|
|
const installedPath = path.join(configDir, relPath);
|
|
const result = { file: relPath, status: 'ok', missing: [], reason: null };
|
|
|
|
if (!fs.existsSync(backupPath) || !fs.statSync(backupPath).isFile()) {
|
|
return result; // walked entry no longer exists — non-fatal
|
|
}
|
|
|
|
// Installed path checks: must exist, must be a regular file, must be
|
|
// readable. Anything else is a fail-with-diagnostic, not a crash that
|
|
// aborts the whole gate run and drops structured output.
|
|
let installedStat;
|
|
try {
|
|
installedStat = fs.statSync(installedPath);
|
|
} catch {
|
|
result.status = 'fail';
|
|
result.reason = REASON.FAIL_INSTALLED_MISSING;
|
|
return result;
|
|
}
|
|
if (!installedStat.isFile()) {
|
|
result.status = 'fail';
|
|
result.reason = REASON.FAIL_INSTALLED_NOT_REGULAR_FILE;
|
|
return result;
|
|
}
|
|
|
|
let backupContent;
|
|
let installedContent;
|
|
try {
|
|
backupContent = fs.readFileSync(backupPath, 'utf8');
|
|
installedContent = fs.readFileSync(installedPath, 'utf8');
|
|
} catch {
|
|
result.status = 'fail';
|
|
result.reason = REASON.FAIL_READ_ERROR;
|
|
return result;
|
|
}
|
|
|
|
let pristineContent = null;
|
|
if (pristineDir) {
|
|
const pristinePath = path.join(pristineDir, relPath);
|
|
try {
|
|
const stat = fs.statSync(pristinePath);
|
|
if (stat.isFile()) {
|
|
const candidate = fs.readFileSync(pristinePath, 'utf8');
|
|
// Bug #3657: if backup-meta.json recorded a pristine_hash for this
|
|
// file, validate that the on-disk pristine matches it. A mismatch
|
|
// means the installer refreshed gsd-pristine/ to a newer GSD version
|
|
// after the backup was captured. Using the wrong-version pristine as
|
|
// the diff baseline inverts the delta: upstream removals appear as
|
|
// "user-added lines that must survive", causing FAIL_USER_LINES_MISSING
|
|
// false positives. When the hash is stale, skip the pristine and fall
|
|
// through to over-broad mode (every significant backup line is checked).
|
|
// Over-broad mode never false-fails for a different reason because all
|
|
// backup lines that are genuinely user-added will still be present in a
|
|
// correctly merged install.
|
|
// Normalize to forward slashes so the key lookup matches on Windows
|
|
// where path.join produces backslash-separated relPath values but
|
|
// backup-meta.json stores keys written with forward slashes.
|
|
const hashKey = relPath.replace(/\\/g, '/');
|
|
const recordedHash = pristineHashes && pristineHashes[hashKey];
|
|
if (recordedHash) {
|
|
if (sha256(candidate) === recordedHash) {
|
|
// Hash matches: the on-disk pristine is the correct baseline.
|
|
pristineContent = candidate;
|
|
} else {
|
|
// Hash mismatch: the on-disk gsd-pristine/ was refreshed to a newer
|
|
// GSD version after the backup was captured. Using it as the diff
|
|
// baseline would invert the delta and produce false FAIL_USER_LINES_MISSING
|
|
// reports (Bug #3657). Report the file as ok with a diagnostic code
|
|
// so the gate does not false-fail; a re-anchor or git-aware baseline
|
|
// step is required to verify this file correctly.
|
|
result.reason = REASON.OK_PRISTINE_DRIFT_DETECTED;
|
|
return result;
|
|
}
|
|
} else {
|
|
// No recorded hash for this file (older installer or absent
|
|
// backup-meta) — use the on-disk pristine as-is (pre-fix behaviour).
|
|
pristineContent = candidate;
|
|
}
|
|
}
|
|
} catch {
|
|
// Pristine missing or unreadable — fall through to over-broad mode.
|
|
}
|
|
}
|
|
|
|
const userAdded = computeUserAddedLines(backupContent, pristineContent);
|
|
if (userAdded.length === 0) {
|
|
// Backup and pristine match exactly (or no significant content) — nothing
|
|
// to verify but also nothing to lose. Report as ok with diagnostic code.
|
|
result.reason = pristineContent
|
|
? REASON.OK_NO_USER_LINES_VS_PRISTINE
|
|
: REASON.OK_NO_SIGNIFICANT_BACKUP_LINES;
|
|
return result;
|
|
}
|
|
|
|
for (const line of userAdded) {
|
|
if (!installedContent.includes(line)) {
|
|
result.missing.push(line.trim());
|
|
}
|
|
}
|
|
if (result.missing.length > 0) {
|
|
result.status = 'fail';
|
|
result.reason = REASON.FAIL_USER_LINES_MISSING;
|
|
}
|
|
return result;
|
|
}
|
|
|
|
function main() {
|
|
const opts = parseArgs(process.argv.slice(2));
|
|
if (!opts.patchesDir || !opts.configDir) {
|
|
process.stderr.write('--patches-dir and --config-dir are required\n');
|
|
process.exit(2);
|
|
}
|
|
if (!fs.existsSync(opts.patchesDir)) {
|
|
process.stderr.write(`patches dir not found: ${opts.patchesDir}\n`);
|
|
process.exit(2);
|
|
}
|
|
if (!fs.existsSync(opts.configDir)) {
|
|
process.stderr.write(`config dir not found: ${opts.configDir}\n`);
|
|
process.exit(2);
|
|
}
|
|
|
|
const files = walk(opts.patchesDir).filter((f) => !f.endsWith('backup-meta.json'));
|
|
// Bug #3657: read pristine_hashes from backup-meta.json once and share
|
|
// across all per-file verifications so each can detect drift independently.
|
|
const pristineHashes = readPristineHashes(opts.patchesDir);
|
|
const results = files.map((relPath) =>
|
|
verifyFile({
|
|
relPath,
|
|
patchesDir: opts.patchesDir,
|
|
configDir: opts.configDir,
|
|
pristineDir: opts.pristineDir,
|
|
pristineHashes,
|
|
}),
|
|
);
|
|
|
|
const failures = results.filter((r) => r.status === 'fail');
|
|
|
|
// Bug #3657 (Finding 1): aggregate drifted files into top-level report fields
|
|
// so workflow Step 5a can gate on drift distinctly from failures. Drift is
|
|
// NOT a failure (exit code stays 0) but the workflow now has structured data
|
|
// to decide whether to proceed. Per-file shape is unchanged: each drifted
|
|
// result still has status:'ok' + reason:OK_PRISTINE_DRIFT_DETECTED for
|
|
// backward compat. The new top-level fields are purely additive.
|
|
const driftedResults = results.filter((r) => r.reason === REASON.OK_PRISTINE_DRIFT_DETECTED);
|
|
const drifted = driftedResults.length;
|
|
const drifted_files = driftedResults.map((r) => r.file);
|
|
|
|
if (opts.json) {
|
|
process.stdout.write(
|
|
JSON.stringify({ checked: results.length, failures: failures.length, drifted, drifted_files, results }, null, 2) + '\n',
|
|
);
|
|
} else {
|
|
process.stdout.write(`# Hunk Verification Gate (#2969)\n\n`);
|
|
process.stdout.write(`Checked: ${results.length} file(s)\n`);
|
|
process.stdout.write(`Failures: ${failures.length}\n\n`);
|
|
if (failures.length > 0) {
|
|
process.stdout.write(`## Files with missing user-added content\n\n`);
|
|
for (const r of failures) {
|
|
process.stdout.write(`- ${r.file}\n`);
|
|
if (r.reason) process.stdout.write(` reason: ${r.reason}\n`);
|
|
for (const line of r.missing.slice(0, 5)) {
|
|
process.stdout.write(` missing: ${line}\n`);
|
|
}
|
|
if (r.missing.length > 5) {
|
|
process.stdout.write(` …and ${r.missing.length - 5} more line(s)\n`);
|
|
}
|
|
}
|
|
}
|
|
}
|
|
|
|
process.exit(failures.length > 0 ? 1 : 0);
|
|
}
|
|
|
|
if (require.main === module) {
|
|
main();
|
|
}
|
|
|
|
module.exports = { computeUserAddedLines, isSignificantLine, verifyFile, walk, REASON, readPristineHashes, sha256 };
|