* feat(#2982): extend no-source-grep lint to catch var-binding readFileSync.includes() The base lint (scripts/lint-no-source-grep.cjs) only catches readFileSync(...).<text-method>() chained directly. The much more common var-binding form escapes it: const src = fs.readFileSync(p, 'utf8'); // 50 lines later if (src.includes('foo')) {} // ← still grep, lint missed it Scan of the test suite found ~141 files using this pattern. Implementation built TDD per #2982 with structured-IR assertions: scripts/lint-no-source-grep-extras.cjs - detectVarBindingViolations(src) — pure detector, two passes: pass 1 collects vars bound from readFileSync, pass 2 finds any <var>.<includes|startsWith|endsWith|match|search>( on those vars. - detectWrappedAssertOkMatch(src) — flags assert.ok(<expr>.match(...)) which escapes the assert.match rule. - VIOLATION enum exposes stable codes for tests to assert on. scripts/lint-no-source-grep.cjs - Wires the new detectors into the existing per-file check; one additional violation row per file with the first 3 sample tokens. tests/bug-2982-lint-var-binding.test.cjs - 13 tests, all assertions on typed VIOLATION enum / structured records. Covers all 5 text-match methods, multi-var, no-bind, string literal (must NOT trigger), wrapped assert.ok(.match), and assert.match (must NOT double-flag). Migration backlog (#2974 expanded scope): - 42 files annotated `// allow-test-rule: source-text-is-the-product` (legitimate — they read .md/.json/.yml files whose deployed text IS the product) - 3 files annotated `// allow-test-rule: pending-migration-to-typed-ir [#2974]` (read .cjs/.js source — clear migration debt) - 95 files annotated `pending-migration-to-typed-ir [#2974]` with `Per-file review may reclassify as source-text-is-the-product during migration` (mixed — manual review under #2974) After this lands the lint reports 0 violations on main; new violations in PRs surface immediately. Closes #2982 Refs #2974 * test(#2982): fix truncated test name per CR The label ended with a bare '(' from a copy-paste mishap. Now reads 'does NOT flag .matchAll(...) — matchAll is not match, so assert.ok(.matchAll(...)) is not flagged'. * chore(#2982): add changeset fragment for PR #2985 * chore(#2982): add changeset fragment for PR #2985
81 lines
3.6 KiB
JavaScript
81 lines
3.6 KiB
JavaScript
// allow-test-rule: pending-migration-to-typed-ir [#2974]
|
|
// Tracked in #2974 for migration to typed-IR assertions per CONTRIBUTING.md
|
|
// "Prohibited: Raw Text Matching on Test Outputs". Per-file review may
|
|
// reclassify some entries as source-text-is-the-product during migration.
|
|
|
|
/**
|
|
* Regression test for #2015: worktree executor creates branch from master
|
|
* instead of the current feature branch HEAD.
|
|
*
|
|
* The worktree_branch_check in execute-phase.md and quick.md used
|
|
* `git reset --soft {EXPECTED_BASE}` as the recovery action when the
|
|
* worktree was created from the wrong base. `reset --soft` moves the HEAD
|
|
* pointer but leaves the working tree files from main/master unchanged —
|
|
* the executor then works against stale code and its commits contain an
|
|
* enormous diff (the entire feature branch) as deletions.
|
|
*
|
|
* Fix: use `git reset --hard {EXPECTED_BASE}` in the worktree_branch_check.
|
|
* In a fresh worktree with no user changes, --hard is safe and correct.
|
|
*/
|
|
|
|
const { describe, test } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
|
|
const EXECUTE_PHASE_PATH = path.join(__dirname, '..', 'get-shit-done', 'workflows', 'execute-phase.md');
|
|
const QUICK_PATH = path.join(__dirname, '..', 'get-shit-done', 'workflows', 'quick.md');
|
|
|
|
describe('worktree_branch_check must use reset --hard not reset --soft (#2015)', () => {
|
|
|
|
test('execute-phase.md worktree_branch_check does not use reset --soft', () => {
|
|
const content = fs.readFileSync(EXECUTE_PHASE_PATH, 'utf-8');
|
|
|
|
// Extract the worktree_branch_check block
|
|
const blockMatch = content.match(/<worktree_branch_check>([\s\S]*?)<\/worktree_branch_check>/);
|
|
assert.ok(blockMatch, 'execute-phase.md must contain a <worktree_branch_check> block');
|
|
|
|
const block = blockMatch[1];
|
|
assert.ok(
|
|
!block.includes('reset --soft'),
|
|
'worktree_branch_check must not use reset --soft (leaves working tree files unchanged). Use reset --hard instead.'
|
|
);
|
|
});
|
|
|
|
test('execute-phase.md worktree_branch_check uses reset --hard for base correction', () => {
|
|
const content = fs.readFileSync(EXECUTE_PHASE_PATH, 'utf-8');
|
|
const blockMatch = content.match(/<worktree_branch_check>([\s\S]*?)<\/worktree_branch_check>/);
|
|
assert.ok(blockMatch, 'execute-phase.md must contain a <worktree_branch_check> block');
|
|
|
|
const block = blockMatch[1];
|
|
assert.ok(
|
|
block.includes('reset --hard'),
|
|
'worktree_branch_check must use reset --hard to correctly reset both HEAD and working tree to the expected base'
|
|
);
|
|
});
|
|
|
|
test('quick.md worktree_branch_check does not use reset --soft', () => {
|
|
const content = fs.readFileSync(QUICK_PATH, 'utf-8');
|
|
const blockMatch = content.match(/<worktree_branch_check>([\s\S]*?)<\/worktree_branch_check>/);
|
|
assert.ok(blockMatch, 'quick.md must contain a <worktree_branch_check> block');
|
|
|
|
const block = blockMatch[1];
|
|
assert.ok(
|
|
!block.includes('reset --soft'),
|
|
'quick.md worktree_branch_check must not use reset --soft. Use reset --hard instead.'
|
|
);
|
|
});
|
|
|
|
test('quick.md worktree_branch_check uses reset --hard for base correction', () => {
|
|
const content = fs.readFileSync(QUICK_PATH, 'utf-8');
|
|
const blockMatch = content.match(/<worktree_branch_check>([\s\S]*?)<\/worktree_branch_check>/);
|
|
assert.ok(blockMatch, 'quick.md must contain a <worktree_branch_check> block');
|
|
|
|
const block = blockMatch[1];
|
|
assert.ok(
|
|
block.includes('reset --hard'),
|
|
'quick.md worktree_branch_check must use reset --hard to correctly reset both HEAD and working tree'
|
|
);
|
|
});
|
|
});
|