Files
msd-core/tests/gsd-researcher-app-aware.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

184 lines
7.3 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.
/**
* Phase Researcher Application-Aware Tests (#1988)
*
* Validates that gsd-phase-researcher maps capabilities to architectural
* tiers before diving into framework-specific research. Also validates
* that gsd-planner and gsd-plan-checker consume the Architectural
* Responsibility Map downstream.
*/
const { test, describe } = require('node:test');
const assert = require('node:assert/strict');
const fs = require('fs');
const path = require('path');
const AGENTS_DIR = path.join(__dirname, '..', 'agents');
const TEMPLATES_DIR = path.join(__dirname, '..', 'gsd-core', 'templates');
// ─── Phase Researcher: Architectural Responsibility Mapping ─────────────────
describe('phase-researcher: Architectural Responsibility Mapping', () => {
const researcherPath = path.join(AGENTS_DIR, 'gsd-phase-researcher.md');
const content = fs.readFileSync(researcherPath, 'utf-8');
test('contains Architectural Responsibility Mapping step', () => {
assert.ok(
content.includes('Architectural Responsibility Map'),
'gsd-phase-researcher.md must contain "Architectural Responsibility Map"'
);
});
test('Architectural Responsibility Mapping step comes after Step 1 and before Step 2', () => {
const step1Pos = content.indexOf('## Step 1:');
// Look for the step heading specifically (not the output format section)
const stepARMPos = content.indexOf('## Step 1.5:');
const step2Pos = content.indexOf('## Step 2:');
assert.ok(step1Pos !== -1, 'Step 1 must exist');
assert.ok(stepARMPos !== -1, 'Step 1.5 Architectural Responsibility Mapping step must exist');
assert.ok(step2Pos !== -1, 'Step 2 must exist');
assert.ok(
stepARMPos > step1Pos,
'Step 1.5 (Architectural Responsibility Mapping) must come after Step 1'
);
assert.ok(
stepARMPos < step2Pos,
'Step 1.5 (Architectural Responsibility Mapping) must come before Step 2'
);
});
test('step is a pure reasoning step with no tool calls', () => {
// Extract the ARM section content (between the ARM heading and the next ## Step heading)
// eslint-disable-next-line local/no-unbounded-quantifier -- parses maintainer-authored agent markdown, bounded prose, not adversarial input
const armHeadingMatch = content.match(/## Step 1\.5[^\r\n]*Architectural Responsibility Map/);
assert.ok(armHeadingMatch, 'Must have a Step 1.5 heading for Architectural Responsibility Mapping');
const armStart = content.indexOf(armHeadingMatch[0]);
const nextStepMatch = content.indexOf('## Step 2:', armStart);
const armSection = content.substring(armStart, nextStepMatch);
// Should not contain tool invocation patterns
const toolPatterns = [
/```bash/,
/node "\$HOME/,
/gsd-tools\.cjs/,
/WebSearch/,
/Context7/,
/mcp__/,
];
for (const pattern of toolPatterns) {
assert.ok(
!pattern.test(armSection),
`Architectural Responsibility Mapping step must be pure reasoning (no tool calls), but found: ${pattern}`
);
}
});
test('mentions standard architectural tiers', () => {
const armStart = content.indexOf('Architectural Responsibility Map');
const nextStep = content.indexOf('## Step 2:', armStart);
const armSection = content.substring(armStart, nextStep);
// Should reference standard tiers
const tiers = ['browser', 'frontend', 'API', 'database'];
const foundTiers = tiers.filter(tier =>
armSection.toLowerCase().includes(tier.toLowerCase())
);
assert.ok(
foundTiers.length >= 3,
`Must mention at least 3 standard architectural tiers, found: ${foundTiers.join(', ')}`
);
});
test('specifies output format as a table in RESEARCH.md', () => {
const armStart = content.indexOf('Architectural Responsibility Map');
const nextStep = content.indexOf('## Step 2:', armStart);
const armSection = content.substring(armStart, nextStep);
assert.ok(
armSection.includes('|') && armSection.includes('Capability'),
'ARM step must specify a table output format with Capability column'
);
});
});
// ─── Planner: Architectural Responsibility Map Sanity Check ─────────────────
describe('planner: Architectural Responsibility Map sanity check', () => {
const plannerPath = path.join(AGENTS_DIR, 'gsd-planner.md');
const content = fs.readFileSync(plannerPath, 'utf-8');
test('references Architectural Responsibility Map', () => {
assert.ok(
content.includes('Architectural Responsibility Map'),
'gsd-planner.md must reference the Architectural Responsibility Map'
);
});
test('includes sanity check against the map', () => {
// Must mention checking/verifying plan tasks against the responsibility map
assert.ok(
content.includes('sanity check') || content.includes('sanity-check'),
'gsd-planner.md must include a sanity check against the Architectural Responsibility Map'
);
});
});
// ─── Plan Checker: Architectural Tier Verification Dimension ────────────────
describe('plan-checker: Architectural Tier verification dimension', () => {
const checkerPath = path.join(AGENTS_DIR, 'gsd-plan-checker.md');
const content = fs.readFileSync(checkerPath, 'utf-8');
test('has verification dimension for architectural tier', () => {
assert.ok(
content.includes('Architectural Responsibility Map') ||
content.includes('Architectural Tier'),
'gsd-plan-checker.md must have a verification dimension for architectural tier mapping'
);
});
test('verification dimension checks plans against the map', () => {
// Should have a dimension that references tier/responsibility checking
assert.ok(
content.includes('tier owner') || content.includes('tier mismatch') || content.includes('responsibility map'),
'plan-checker verification dimension must check for tier mismatches against the responsibility map'
);
});
});
// ─── Research Template: Architectural Responsibility Map Section ─────────────
describe('research template: Architectural Responsibility Map section', () => {
const templatePath = path.join(TEMPLATES_DIR, 'research.md');
const content = fs.readFileSync(templatePath, 'utf-8');
test('mentions Architectural Responsibility Map section', () => {
assert.ok(
content.includes('Architectural Responsibility Map'),
'Research template must include an Architectural Responsibility Map section'
);
});
test('template includes tier table format', () => {
const armStart = content.indexOf('Architectural Responsibility Map');
assert.ok(armStart !== -1, 'ARM section must exist');
const sectionEnd = content.indexOf('##', armStart + 10);
const section = content.substring(armStart, sectionEnd !== -1 ? sectionEnd : armStart + 500);
assert.ok(
section.includes('|') && (section.includes('Tier') || section.includes('tier')),
'Research template ARM section must include a table format with Tier column'
);
});
});