Files
msd-core/tests/gsd-researcher-flow-diagram.test.cjs
Tom Boucher aab01f43e9 refactor(tests): consolidate Phase Lifecycle Module — 20 files → 4 (#3741)
* chore(tests): lint rule — cap test files per production module at 2

Adds scripts/lint-test-file-count.cjs with a ratcheted allowlist
(scripts/lint-test-file-count.allowlist.json) capturing today's
30 violating clusters as a ceiling. New entries blocked at PR time;
reductions ratchet automatically.

Wires into .github/workflows/test.yml as a new step in lint-tests.

Refs #3737

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* refactor(tests): consolidate Phase Lifecycle Module — 20 files → 4

- Merge 10 CJS bug-fix test files into tests/phase.test.cjs
- Merge sdk/src/phase-runner-types.test.ts + sdk/src/phase-prompt.test.ts
  into sdk/src/phase-runner.test.ts (97 → 152 tests, 0 failures)
- Rename 4 mis-attributed test files out of phase cluster:
    phase-researcher-app-aware    → gsd-researcher-app-aware
    phase-researcher-flow-diagram → gsd-researcher-flow-diagram
    feat-3023-phase-type-models   → feat-3023-model-phase-types
    phase-6-cjs-sdk-seam-contracts → cjs-sdk-bridge-seam-contracts
- Fix phasePlanIndex (#3430): non-canonical plan filename warning now
  surfaces in data.warnings[] as "Ignored noncanonical plan files: ..."
  instead of a separate singular data.warning field
- Update allowlist: phase ceiling 20 → 4 (closes #3740)
- Add Phase Lifecycle Module glossary entry to CONTEXT.md

Closes #3740

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix(phase-roadmap-mutation): replaceInCurrentMilestone handles active milestone inside <details> block

When the active milestone is wrapped in a <details> block (e.g. user
collapsed it, or milestone transition), the after-</details> slice is
empty or contains only footer text — the pattern never matches and the
replacement is silently dropped.

Fix: when after.replace() produces no change, fall back to replacing
inside the last <details>...</details> block. Shipped-milestone blocks
are untouched because only the last <details> block is targeted.

Closes #2641

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix(changeset): add required type/pr frontmatter to 3740 fragment

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-20 20:57:06 -04:00

110 lines
3.8 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.
/**
* Phase Researcher Flow Diagram Tests (#2139)
*
* Validates that gsd-phase-researcher enforces data-flow architecture
* diagrams instead of file-listing diagrams. Also validates that the
* research template includes the matching directive.
*/
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, '..', 'get-shit-done', 'templates');
// ─── Phase Researcher: System Architecture Diagram Directive ─────────────────
describe('phase-researcher: System Architecture Diagram directive', () => {
const researcherPath = path.join(AGENTS_DIR, 'gsd-phase-researcher.md');
const content = fs.readFileSync(researcherPath, 'utf-8');
test('contains System Architecture Diagram section', () => {
assert.ok(
content.includes('### System Architecture Diagram'),
'gsd-phase-researcher.md must contain "### System Architecture Diagram"'
);
});
test('requires data flow through conceptual components', () => {
assert.ok(
content.includes('data flow through conceptual components'),
'Directive must require "data flow through conceptual components"'
);
});
test('explicitly prohibits file listings in diagrams', () => {
assert.ok(
content.includes('not file listings'),
'Directive must explicitly state "not file listings"'
);
});
test('includes key requirements for flow diagrams', () => {
const requirements = [
'entry points',
'processing stages',
'decision points',
'external dependencies',
'arrows',
];
for (const req of requirements) {
assert.ok(
content.toLowerCase().includes(req),
`Directive must mention "${req}"`
);
}
});
test('directs file-to-implementation mapping to Component Responsibilities table', () => {
assert.ok(
content.includes('Component Responsibilities table'),
'Directive must redirect file mapping to Component Responsibilities table'
);
});
test('diagram section comes before Recommended Project Structure', () => {
const diagramPos = content.indexOf('### System Architecture Diagram');
const structurePos = content.indexOf('### Recommended Project Structure');
assert.ok(diagramPos !== -1, 'System Architecture Diagram section must exist');
assert.ok(structurePos !== -1, 'Recommended Project Structure section must exist');
assert.ok(
diagramPos < structurePos,
'System Architecture Diagram must come before Recommended Project Structure'
);
});
});
// ─── Research Template: System Architecture Diagram Section ───────────────────
describe('research template: System Architecture Diagram section', () => {
const templatePath = path.join(TEMPLATES_DIR, 'research.md');
const content = fs.readFileSync(templatePath, 'utf-8');
test('contains System Architecture Diagram section', () => {
assert.ok(
content.includes('### System Architecture Diagram'),
'Research template must contain "### System Architecture Diagram"'
);
});
test('includes flow diagram requirements', () => {
assert.ok(
content.includes('data flow through conceptual components'),
'Research template must include flow diagram directive'
);
assert.ok(
content.includes('not file listings'),
'Research template must prohibit file listings in diagrams'
);
});
});