mirror of
https://github.com/glittercowboy/get-shit-done
synced 2026-05-13 18:46:38 +02:00
* 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
78 lines
3.2 KiB
JavaScript
78 lines
3.2 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.
|
|
|
|
/**
|
|
* Bug #2399: commit_docs:true is ignored in plan-phase
|
|
*
|
|
* The plan-phase workflow generates plan artifacts but never commits them even
|
|
* when commit_docs is true. A step between 13b and 14 must commit the PLAN.md
|
|
* files and updated STATE.md when commit_docs is set.
|
|
*/
|
|
|
|
const { describe, test } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
|
|
const PLAN_PHASE_PATH = path.join(__dirname, '..', 'get-shit-done', 'workflows', 'plan-phase.md');
|
|
|
|
describe('plan-phase commit_docs support (#2399)', () => {
|
|
test('plan-phase.md exists', () => {
|
|
assert.ok(fs.existsSync(PLAN_PHASE_PATH), 'get-shit-done/workflows/plan-phase.md must exist');
|
|
});
|
|
|
|
test('plan-phase.md has a commit step for plan artifacts', () => {
|
|
const content = fs.readFileSync(PLAN_PHASE_PATH, 'utf-8');
|
|
// Must contain a commit call that references PLAN.md files
|
|
assert.ok(
|
|
content.includes('PLAN.md') && content.includes('commit'),
|
|
'plan-phase.md must include a commit step that references PLAN.md files'
|
|
);
|
|
});
|
|
|
|
test('plan-phase.md commit step is gated on commit_docs', () => {
|
|
const content = fs.readFileSync(PLAN_PHASE_PATH, 'utf-8');
|
|
// The commit step must be conditional on commit_docs
|
|
assert.ok(
|
|
content.includes('commit_docs'),
|
|
'plan-phase.md must reference commit_docs to gate the plan commit step'
|
|
);
|
|
});
|
|
|
|
test('plan-phase.md commit step references STATE.md', () => {
|
|
const content = fs.readFileSync(PLAN_PHASE_PATH, 'utf-8');
|
|
// Should commit STATE.md alongside PLAN.md files
|
|
assert.ok(
|
|
content.includes('STATE.md'),
|
|
'plan-phase.md commit step should include STATE.md to capture planning completion state'
|
|
);
|
|
});
|
|
|
|
test('plan-phase.md has a step 13c that commits plan artifacts', () => {
|
|
const content = fs.readFileSync(PLAN_PHASE_PATH, 'utf-8');
|
|
const step13b = content.indexOf('## 13b.');
|
|
const step14 = content.indexOf('## 14.');
|
|
// Look for the step 13c section (or any commit step between 13b and 14)
|
|
const step13c = content.indexOf('## 13c.');
|
|
|
|
assert.ok(step13b !== -1, '## 13b. section must exist');
|
|
assert.ok(step14 !== -1, '## 14. section must exist');
|
|
assert.ok(step13c !== -1, '## 13c. step must exist (commit plans step)');
|
|
assert.ok(
|
|
step13c > step13b && step13c < step14,
|
|
`Step 13c (at ${step13c}) must appear between step 13b (at ${step13b}) and step 14 (at ${step14})`
|
|
);
|
|
});
|
|
|
|
test('plan-phase.md uses gsd-sdk query commit for the plan commit', () => {
|
|
const content = fs.readFileSync(PLAN_PHASE_PATH, 'utf-8');
|
|
// Must use gsd-sdk query commit (not raw git) so commit_docs guard in gsd-tools is respected
|
|
assert.ok(
|
|
content.includes('gsd-sdk query commit') || content.includes('gsd-tools') || content.includes('gsd-sdk'),
|
|
'plan-phase.md plan commit step must use gsd-sdk query commit (not raw git commit)'
|
|
);
|
|
});
|
|
});
|