Files
msd-core/tests/inline-plan-threshold.test.cjs
Tom Boucher 69e7afd0c7 chore(#3212): bounded quantifiers over document content — prohibition with teeth — Phase 4 (#3441)
* 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>
2026-08-14 10:02:28 -04:00

129 lines
4.9 KiB
JavaScript

// allow-test-rule: source-text-is-the-product
// execute-plan.md and planning-config.md are deployed workflow/reference files
// whose text IS the product loaded by agents at runtime. The config-set tests
// use runGsdTools and assert on success/failure (typed). Migration from
// pending-migration-to-typed-ir per #455.
/**
* Tests for workflow.inline_plan_threshold config key and routing logic (#1979).
*
* Verifies:
* 1. The config key is accepted by config-set (VALID_CONFIG_KEYS contains it)
* 2. The key is documented in planning-config.md
* 3. The execute-plan.md routing instruction uses the correct grep pattern
* (matches <task at any indentation, since PLAN.md templates differ)
* 4. The workflow guards threshold=0 to disable inline routing
*/
'use strict';
const { test, describe, beforeEach, afterEach } = require('node:test');
const assert = require('node:assert/strict');
const fs = require('node:fs');
const path = require('node:path');
const { runGsdTools, createTempProject, cleanup } = require('./helpers.cjs');
const repoRoot = path.resolve(__dirname, '..');
const executePlanPath = path.join(repoRoot, 'gsd-core', 'workflows', 'execute-plan.md');
const planningConfigPath = path.join(repoRoot, 'gsd-core', 'references', 'planning-config.md');
describe('inline_plan_threshold config key (#1979)', () => {
let tmpDir;
beforeEach(() => {
tmpDir = createTempProject();
});
afterEach(() => {
cleanup(tmpDir);
});
test('config-set accepts workflow.inline_plan_threshold', () => {
const result = runGsdTools('config-set workflow.inline_plan_threshold 3', tmpDir);
assert.ok(result.success, `config-set should accept workflow.inline_plan_threshold: ${result.error}`);
});
test('config-set accepts threshold=0 to disable inline routing', () => {
const result = runGsdTools('config-set workflow.inline_plan_threshold 0', tmpDir);
assert.ok(result.success, `config-set should accept 0: ${result.error}`);
});
test('planning-config.md documents workflow.inline_plan_threshold', () => {
const content = fs.readFileSync(planningConfigPath, 'utf-8');
assert.match(
content,
/workflow\.inline_plan_threshold/,
'planning-config.md must document workflow.inline_plan_threshold'
);
});
});
describe('execute-plan.md routing instruction (#1979)', () => {
test('grep pattern matches <task at any indentation level', () => {
const content = fs.readFileSync(executePlanPath, 'utf-8');
// The new pattern should use \s* for leading whitespace, not ^ anchor alone
// Must match both "<task type=" (unindented) and " <task type=" (indented)
assert.match(
content,
/TASK_COUNT=\$\(grep -cE '\^\\s\*<task/,
'grep pattern must allow any leading whitespace before <task'
);
});
test('inline routing is guarded by INLINE_THRESHOLD > 0', () => {
const content = fs.readFileSync(executePlanPath, 'utf-8');
assert.match(
content,
/INLINE_THRESHOLD\s*>\s*0.*TASK_COUNT\s*<=\s*INLINE_THRESHOLD/s,
'inline routing must be guarded by INLINE_THRESHOLD > 0 so threshold=0 disables it'
);
});
test('grep pattern does NOT use ^<task alone (would miss indented tasks)', () => {
const content = fs.readFileSync(executePlanPath, 'utf-8');
// The old buggy pattern: grep -c "^<task" with no whitespace allowance
const buggyPattern = /grep -c "\^<task"/;
assert.doesNotMatch(
content,
buggyPattern,
'must not use the buggy "^<task" pattern which misses indented tasks'
);
});
test('grep pattern matches real-world indented task formats', () => {
// Simulate how the grep pattern would behave against sample PLAN.md content
// Extract the pattern from execute-plan.md
const content = fs.readFileSync(executePlanPath, 'utf-8');
// eslint-disable-next-line local/no-unbounded-quantifier -- parses maintainer-authored execute-plan.md workflow, bounded prose, not adversarial input
const patternMatch = content.match(/TASK_COUNT=\$\(grep -cE '([^']+)'/);
assert.ok(patternMatch, 'must find TASK_COUNT grep pattern');
const regexSource = patternMatch[1].replace(/\[\[:space:\]>\]/, '[\\s>]');
const re = new RegExp(regexSource, 'gm');
// Test cases: should match all of these as single tasks
const samples = [
'<task type="auto">',
' <task type="auto">',
' <task type="checkpoint:decision">',
'\t<task type="auto">',
];
for (const sample of samples) {
const matches = sample.match(re);
assert.ok(matches && matches.length > 0, `Pattern must match: ${JSON.stringify(sample)}`);
}
// Non-task lines should not match
const nonMatches = [
'<tasks>',
'</task>',
'// <task comment',
];
for (const sample of nonMatches) {
const matches = sample.match(re);
assert.ok(!matches || matches.length === 0, `Pattern must NOT match: ${JSON.stringify(sample)}`);
}
});
});