* feat(#3415): ship local/no-unbounded-quantifier, burn down ReDoS class Phase 4 of epic #3212 (ADR-3212 §5/§7, the final phase). New rule flags an unbounded */+/{n,} quantifier over a broad character class ([\s\S], dotAll ., or a 1-2-unit negated class like [^\n]/[^)\n] — the exact #2128-fixed shape) applied to a regex whose match target is data-flow-traced to readFileSync content. eslint-rules/lib/readfilesync-trace.cjs extracts the data-flow tracer shared with no-crlf-fragile-split (Phase 2) rather than a second copy — no-crlf-fragile-split refactored onto it with zero behavior change, parity-tested. Real triage, not 798 mechanical edits: the ADR's census (2026-08-08) screened every unbounded quantifier in the tree unscoped. Correctly scoped to readFileSync-derived content (matching Phase 2's own G2/G3 scoping), the rule found 162 real hits across two detection waves — the second wave (93) surfaced only after a genuine off-by-one bug in this rule's own first draft was caught while writing its RuleTester tests and fixed (the bug silently missed every directly-quantified [\s\S]* with no gap before the quantifier — exactly the class this rule exists to catch). 3 hits landed in production src/ (commands.cts, milestone.cts, roadmap.cts) and were each empirically timed against adversarial input (matching #2128's own measured-not-assumed precedent) — all confirmed linear-time/benign, left unbounded with a measured-evidence comment rather than mechanically bounded. The remaining 159 are test-file fixture parsing (test-author-controlled, fixed-size content, not adversarial input) — each suppressed with a specific, non-generic reason. Zero functional behavior changed anywhere in this diff. tests/no-pending-3212-markers.test.cjs locks the epic's own closing invariant (ADR §7: "assert zero pending #3212 markers remain") — ground truth confirmed trivially true today (no phase left any such marker behind), now regression-locked going forward. Design: .gsd/phase/chore-3415-prohibition-with-teeth/40-design.md Test matrix: .gsd/phase/chore-3415-prohibition-with-teeth/50-test-matrix.md Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * fix(#3415): correct rule category mislabel, add CI test-scope entry An orthogonal Standards-axis review found eslint-rules/no-unbounded-quantifier.cjs mistakenly carried meta.docs.category: 'Portability', copied from a sibling rule without realizing what that implied: docs/contributing/cross-platform- portability-rules.md governs an ADR-1703 rule family under a hard "zero escape hatches" contract (tests/portability-rule-disable-ban.test.cjs's PROTECTED_RULES bans eslint-disable for those rules entirely). This rule is not part of that family — it's ADR-3212 (ReDoS/CWE-1333), a different epic — and its eslint-disable-next-line suppressions (159 of them, added earlier this same phase after empirical benign-verification) are an intentional, correct design, not a bypass. Corrected to category: 'Best Practices', matching the actual precedent (no-adhoc-regex-escape.cjs, Phase 1 of the same epic, which is also correctly outside PROTECTED_RULES), and the rule's own docstring now states this explicitly so a future reader doesn't have to re-derive it. Also registers a new scripts/ci-test-scope.cjs bucket so editing this rule or the shared eslint-rules/lib/readfilesync-trace.cjs helper re-runs their own test suites under targeted CI selection — was previously unregistered and invisible to that fast-path (this PR's own gsd-test checkpoint runs the full suite regardless, so this only affects future narrowly-scoped PRs). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * fix(#3415): bound no-unbounded-quantifier's own scanner (CWE-1333, ironic) Security review found the rule meant to catch algorithmic-complexity bugs had one of its own: hasUnboundedBroadQuantifier's negated-class inner scan walked from each `[^` occurrence to the next `]` (or EOF) with no bound, while the outer loop only ever advanced by one character — O(n²) total work on a pattern with many unclosed `[^` runs. Runs unconditionally inside checkPattern on any `new RegExp('literal string')` argument in any linted file, before the (cheap) readFileSync data-flow gate — so a single crafted string literal, no valid regex syntax required, could make `npm run lint` / CI hang. Empirically confirmed both the bug and the fix: pre-fix, n=4000/8000/ 16000/32000 chars took 30.8/115.6/463.8/1874.3ms (~4x work per 2x n, quadratic); extrapolated, the 300000-char repro from the finding would run ~165s. Post-fix (bail the inner scan once units exceeds the rule's own 1-2-unit scope, rather than continuing to hunt for a closing `]`), the same 300000-char input runs in 8.7ms via the real rule module, independently reconfirmed at 18ms via a fresh Linter.verify() call. New regression row in tests/no-unbounded-quantifier.rule.test.cjs asserts the RuleTester run on a 50000-char adversarial pattern completes and returns a defined result — no wall-clock assertion (CLAUDE.md Clock Seams / local/no-elapsed-assertion). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * fix(#3415): triage 3 new sites, re-raise ceiling after upstream batch next merged 12 more PRs during this PR's review. Two consequences: - tests/edit-phase.test.cjs (fix #3262, unrelated) added 3 new content.match(/<tag>([\s\S]*?)<\/tag>/) reads of this repo's own workflow .md content — the same Class A pattern as the ~159 sites already triaged elsewhere in this PR. Suppressed with the same established reason. - lint-allow-test-rule-refs' ratchet ceiling needed re-raising again (301 -> 303) for the same reason as the two prior bumps: organic growth from unrelated, already-reviewed PRs landing concurrently, not a defect in this branch's own diff. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
165 lines
7.1 KiB
JavaScript
165 lines
7.1 KiB
JavaScript
// allow-test-rule: source-text-is-the-product
|
|
// Workflow .md / agent .md / command .md / reference .md files — their text
|
|
// IS what the runtime loads. Testing text content tests the deployed contract.
|
|
// Per CONTRIBUTING.md exception matrix.
|
|
|
|
/**
|
|
* Tests for bug #1587: parallel agents for dependent plans
|
|
*
|
|
* Validates that:
|
|
* 1. gsd-planner.md assign_waves step explicitly checks files_modified overlap
|
|
* and mandates a later wave for any plan that shares files with a prior plan.
|
|
* 2. execute-phase.md has a pre-spawn intra-wave files_modified overlap check
|
|
* and directs sequential execution when overlap is detected.
|
|
*/
|
|
|
|
const { test, describe } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
|
|
const PLANNER_AGENT_PATH = path.join(__dirname, '..', 'agents', 'gsd-planner.md');
|
|
const EXECUTE_PHASE_PATH = path.join(
|
|
__dirname,
|
|
'..',
|
|
'gsd-core',
|
|
'workflows',
|
|
'execute-phase.md'
|
|
);
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// gsd-planner.md — wave assignment must account for files_modified overlap
|
|
// ---------------------------------------------------------------------------
|
|
|
|
describe('gsd-planner agent: files_modified wave ordering', () => {
|
|
test('planner agent file exists', () => {
|
|
assert.ok(fs.existsSync(PLANNER_AGENT_PATH), 'agents/gsd-planner.md should exist');
|
|
});
|
|
|
|
test('assign_waves step checks files_modified overlap', () => {
|
|
const content = fs.readFileSync(PLANNER_AGENT_PATH, 'utf-8');
|
|
// The assign_waves step must mention files_modified overlap as a wave-bumping condition
|
|
assert.ok(
|
|
content.includes('files_modified'),
|
|
'assign_waves step should reference files_modified'
|
|
);
|
|
// Must state that overlap forces a later wave (not just "same plan or sequential")
|
|
assert.ok(
|
|
content.includes('files_modified overlap') ||
|
|
content.includes('files_modified') &&
|
|
(content.includes('later wave') || content.includes('strictly later wave')),
|
|
'assign_waves step should explicitly require a later wave when files_modified overlap exists'
|
|
);
|
|
});
|
|
|
|
test('assign_waves step contains explicit overlap → later-wave rule', () => {
|
|
const content = fs.readFileSync(PLANNER_AGENT_PATH, 'utf-8');
|
|
// Look for the assign_waves step block
|
|
const assignWavesMatch = content.match(
|
|
// eslint-disable-next-line local/no-unbounded-quantifier -- parses this repo's own agent .md content, fixed-size author-controlled content
|
|
/<step name="assign_waves">([\s\S]*?)<\/step>/
|
|
);
|
|
assert.ok(assignWavesMatch, 'assign_waves step should exist in gsd-planner.md');
|
|
|
|
const stepContent = assignWavesMatch[1];
|
|
|
|
// Must mention files_modified as a wave-ordering factor inside the step
|
|
assert.ok(
|
|
stepContent.includes('files_modified'),
|
|
'assign_waves step body must reference files_modified as a wave-assignment factor'
|
|
);
|
|
});
|
|
|
|
test('assign_waves step treats files_modified overlap same as depends_on dependency', () => {
|
|
const content = fs.readFileSync(PLANNER_AGENT_PATH, 'utf-8');
|
|
const assignWavesMatch = content.match(
|
|
// eslint-disable-next-line local/no-unbounded-quantifier -- parses this repo's own agent .md content, fixed-size author-controlled content
|
|
/<step name="assign_waves">([\s\S]*?)<\/step>/
|
|
);
|
|
assert.ok(assignWavesMatch, 'assign_waves step should exist');
|
|
|
|
const stepContent = assignWavesMatch[1];
|
|
|
|
// The step must bump the wave when files_modified overlap exists
|
|
assert.ok(
|
|
stepContent.includes('overlap') || stepContent.includes('shared file'),
|
|
'assign_waves step must handle file overlap as a wave-bumping condition'
|
|
);
|
|
});
|
|
|
|
test('planner has validation step or quality gate for wave/files_modified consistency', () => {
|
|
const content = fs.readFileSync(PLANNER_AGENT_PATH, 'utf-8');
|
|
// Either a validation step or the quality_gate checklist must assert no same-wave overlap
|
|
const hasValidationStep =
|
|
content.includes('validate_waves') ||
|
|
content.includes('wave_validation') ||
|
|
content.includes('files_modified overlap');
|
|
const hasQualityGateCheck =
|
|
content.includes('files_modified') && content.includes('same wave');
|
|
assert.ok(
|
|
hasValidationStep || hasQualityGateCheck,
|
|
'planner should validate that no two plans in the same wave share files_modified entries'
|
|
);
|
|
});
|
|
});
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// execute-phase.md — pre-spawn intra-wave overlap safety net
|
|
// ---------------------------------------------------------------------------
|
|
|
|
describe('execute-phase workflow: intra-wave files_modified overlap check', () => {
|
|
test('execute-phase workflow file exists', () => {
|
|
assert.ok(fs.existsSync(EXECUTE_PHASE_PATH), 'workflows/execute-phase.md should exist');
|
|
});
|
|
|
|
test('execute_waves step contains intra-wave files_modified overlap check', () => {
|
|
const content = fs.readFileSync(EXECUTE_PHASE_PATH, 'utf-8');
|
|
// The workflow must mention checking files_modified overlap before spawning
|
|
assert.ok(
|
|
content.includes('files_modified') &&
|
|
(content.includes('overlap') || content.includes('intra-wave')),
|
|
'execute-phase workflow should check for files_modified overlap within a wave before spawning'
|
|
);
|
|
});
|
|
|
|
test('overlap detection is placed before agent spawning', () => {
|
|
const content = fs.readFileSync(EXECUTE_PHASE_PATH, 'utf-8');
|
|
// Overlap check keyword must appear before the Task( spawn call
|
|
const overlapIdx = content.indexOf('intra-wave') !== -1
|
|
? content.indexOf('intra-wave')
|
|
: content.indexOf('files_modified overlap');
|
|
const spawnIdx = content.indexOf('Spawn executor agents');
|
|
assert.ok(overlapIdx !== -1, 'overlap check text should exist in execute-phase.md');
|
|
assert.ok(spawnIdx !== -1, '"Spawn executor agents" heading should exist');
|
|
assert.ok(
|
|
overlapIdx < spawnIdx,
|
|
'overlap check should appear before the "Spawn executor agents" section'
|
|
);
|
|
});
|
|
|
|
test('workflow warns and switches to sequential when overlap detected', () => {
|
|
const content = fs.readFileSync(EXECUTE_PHASE_PATH, 'utf-8');
|
|
// Must log a warning and force sequential execution for overlapping plans
|
|
assert.ok(
|
|
content.includes('sequentially') || content.includes('sequential'),
|
|
'workflow should direct sequential execution when overlap is detected'
|
|
);
|
|
assert.ok(
|
|
content.includes('overlap') && content.includes('warn'),
|
|
'workflow should log a warning when files_modified overlap is detected in a wave'
|
|
);
|
|
});
|
|
|
|
test('overlap check covers all plans in the wave, not just adjacent pairs', () => {
|
|
const content = fs.readFileSync(EXECUTE_PHASE_PATH, 'utf-8');
|
|
// Must describe comparing all plans in the wave (set-intersection language)
|
|
assert.ok(
|
|
content.includes('all plans in') ||
|
|
content.includes('all plans within') ||
|
|
content.includes('each pair') ||
|
|
content.includes('any two plans'),
|
|
'overlap check should cover all plan pairs in the wave, not just adjacent ones'
|
|
);
|
|
});
|
|
});
|