Files
msd-core/sdk/src/query/mvp.test.ts
Tom Boucher 2d32ad82be fix(plan-phase): remove agent: directive that caused OpenCode subagent dispatch (#3156) (#3206)
* feat(roadmap): parse **Mode:** field on phase sections

Adds a 'mode' field to roadmap.get-phase and roadmap.analyze outputs.
Recognizes '**Mode:** mvp' lines in phase sections; lowercased + trimmed.
Forward-compat: unrecognized values preserved verbatim, no enum check.

Foundation for --mvp flag in plan-phase (PRD: vertical-mvp-slice).

* feat(plan-phase): parse --mvp flag and resolve MVP_MODE

Resolution order: CLI flag → ROADMAP **Mode:** field → workflow.mvp_mode
config → false. Walking Skeleton gate fires for new-project Phase 1.
Wires MVP_MODE + WALKING_SKELETON into gsd-planner subagent prompt.

Per PRD vertical-mvp-slice Phase 1 (Q1, Q2, Q4).

* docs(planner): add vertical-slice planning reference

New reference loaded by gsd-planner when MVP_MODE=true. Defines slice
ordering, Walking Skeleton rules, and anti-patterns. Referenced from
plan-phase workflow MVP_MODE wiring.

* docs(planner): add SKELETON.md template

Template emitted by gsd-planner under WALKING_SKELETON=true. Captures
architectural decisions and out-of-scope list for new-project Phase 1.

* chore(inventory): register new planner references

Added planner-mvp-mode.md and skeleton-template.md to INVENTORY.md and
INVENTORY-MANIFEST.json. References now: 53.

* feat(gsd-planner): add MVP Mode Detection section

Mode-switched branch in the existing planner agent (per Q4: single agent).
Vertical-slice decomposition rules, Walking Skeleton handling, and
TDD-mode compatibility. Heavy guidance lives in references/planner-mvp-mode.md.

* test(plan-phase): add --mvp resolution-chain integration cases

Validates roadmap.get-phase --pick mode and confirms workflow.mvp_mode
default is unset in fresh projects.

* docs(changelog): announce --mvp vertical-slice planning (#2826)

* feat(mvp-phase): add /gsd mvp-phase slash command

Standalone command for vertical MVP planning. Frontmatter only;
heavyweight workflow at get-shit-done/workflows/mvp-phase.md follows
in next commit. Mirrors discuss-phase/edit-phase command shape.

* docs(planner): add user-story-template reference

Defines the canonical 'As a / I want to / So that' format and the
ROADMAP.md / PLAN.md emit rules. Used by mvp-phase workflow and
gsd-planner agent under MVP_MODE.

* docs(planner): add SPIDR splitting reference

Defines size signals, the five SPIDR axes (Spike/Paths/Interfaces/Data/Rules),
the interactive workflow, and anti-patterns. Per PRD Q3 decision: full
interactive flow, not lightweight check. Used by mvp-phase workflow.

* fix(mvp-phase): trim description to fit 100-char budget

* feat(mvp-phase): add mvp-phase workflow

Standalone workflow: phase validation -> user story prompts (As a / I want to /
So that) -> SPIDR splitting check -> ROADMAP write (Mode + Goal) -> delegation
to plan-phase. Per PRD Phase 2 (Q3 full SPIDR; Phase-2-A/B/C/D decisions).

Plan-phase auto-detects MVP via Phase 1's resolution chain, so no flags
are needed when delegating.

* feat(gsd-planner): emit user-story header in PLAN.md under MVP mode

Extends the MVP Mode Detection section (added in Phase 1) so the planner
sources the user story from ROADMAP **Goal:** and emits the bolded
**As a** / **I want to** / **so that** form as the first content under
the phase header in PLAN.md. References user-story-template.md.

* test(mvp-phase): integration smoke test for ROADMAP mutation

Validates roadmap.get-phase output after a workflow-spec'd ROADMAP write:
mode=mvp and goal=full user story. Catches schema drift between workflow
emit and parser expectation. Includes a long-story case (>120 chars) to
confirm SPIDR-rejected stories still parse correctly.

* chore(inventory): register mvp-phase command + 2 new references

Adds /gsd mvp-phase to commands list, mvp-phase workflow to workflows list,
and user-story-template.md + spidr-splitting.md to references. References
count: 53 -> 55.

* docs(changelog): announce /gsd mvp-phase command (#2826)

* fix(mvp-phase): add TEXT_MODE plain-text fallback for non-Claude runtimes (#2012)

* docs(executor): add MVP+TDD gate reference

Defines the runtime gate semantics for execute-phase when both
MVP_MODE and TDD_MODE are true: pre-task verification of failing-test
commit, end-of-phase review escalation from advisory to blocking,
behavior-adding task definition. Loaded conditionally by
execute-phase workflow and gsd-executor agent.

* feat(execute-phase): MVP+TDD runtime gate + blocking review

Resolves MVP_MODE in Step 1 (CLI flag -> roadmap mode -> config -> false).
Adds per-task gate that halts before behavior-adding tasks run if no
failing-test commit exists for the plan. Escalates end-of-phase TDD
review from advisory to blocking when both MVP_MODE and TDD_MODE active.

Also updates INVENTORY-MANIFEST.json to register execute-mvp-tdd.md
(added by Task 1) so manifest-sync tests pass.

Per PRD vertical-mvp-slice Phase 3a (decisions Phase-3-A, Phase-3-Split).

* feat(gsd-executor): add MVP+TDD Gate section

Mirrors the planner's MVP Mode Detection pattern from Phase 1.
Instructs halt-and-report when the runtime gate trips, references
execute-mvp-tdd.md for full semantics. No agent changes outside the
new section.

* test(execute-phase): add MVP+TDD resolution-chain integration cases

Validates roadmap.get-phase --pick mode and confirms workflow.mvp_mode
default is unset in fresh projects. Mirrors the Phase 1 plan-phase
resolution-chain integration test.

* chore(inventory): register execute-mvp-tdd reference

Bumps References count 55 -> 56. Registers execute-mvp-tdd.md.
Adds "init" to PROSE_ALLOWLIST in registry integration test so
bare `gsd-sdk query init` prose examples in plan docs don't
trigger the unregistered-handler guard (real commands are all
init.<subcommand>).

* docs(changelog): announce MVP+TDD runtime gate in execute-phase (#2826)

* docs(verifier): add verify-mvp-mode reference

Defines UAT framing under MVP mode: user-flow walk-through first,
technical checks deferred, coverage check as goal-backward narrowing
to the user story's outcome clause. Loaded conditionally by
verify-work workflow and gsd-verifier agent.

* feat(verify-work): MVP-mode UAT framing — user flow first

Resolves MVP_MODE from phase mode field. Under MVP mode, generates UAT
in three ordered sections: user-flow walk-through (derived from user
story), technical checks (deferred), coverage check (goal-backward).
Falls back to standard UAT generation when mode is null/absent.
User-story-format guard refuses to verify a mode:mvp phase with a
non-user-story goal.

Also updates docs/INVENTORY.md (56 references) and
docs/INVENTORY-MANIFEST.json to register verify-mvp-mode.md added
in Task 1.

Per PRD vertical-mvp-slice Phase 3b (decisions Phase-3-B,
Phase-3-Verify-Structure).

* feat(gsd-verifier): add MVP Mode Verification section

Narrows goal-backward verification to the user-story [outcome] clause
when phase mode is mvp. References verify-mvp-mode.md. Preserves
existing goal-backward methodology for non-MVP phases. User-story-format
guard refuses to verify a mode:mvp phase with a non-user-story goal.

* docs(changelog): announce MVP-mode UAT framing in verify-work (#2826)

* feat(new-project): add Vertical MVP vs Horizontal Layers mode prompt

Asks user at project init how to structure the project. Vertical MVP
emits **Mode:** mvp on every initial roadmap phase (per-phase mode
preserved per PRD Q1). Horizontal Layers falls back to standard
template — no behavioral change for existing flows.

Per PRD vertical-mvp-slice Phase 4 (decision Phase-4-Persistence).

* feat(progress): add MVP-mode user-flow display

When phase has **Mode:** mvp, progress renders user-flow status from
PLAN.md task names alongside standard task progress. Tasks that aren't
user-flow-shaped (technical-sounding) are filtered out of the user-flow
sub-block. Falls back to standard display when mode is null/absent.

Per PRD vertical-mvp-slice Phase 4 (decision Phase-4-Progress).

* feat(stats): add MVP phase count summary

Reads roadmap.analyze (which surfaces mode per phase from Phase 1) and
emits 'Phases: N total | M MVP | K standard' summary line. Suppressed
when MVP_COUNT == 0 to avoid clutter on non-MVP projects.

Per PRD vertical-mvp-slice Phase 4.

* feat(graphify): add MVP-mode visual differentiation

MVP-mode phases render with #22c55e fill color AND ' (MVP)' label
suffix — two-channel signaling for color-blind and grayscale renders.
Standard phases unchanged.

Per PRD vertical-mvp-slice Phase 4 (PRD Q5: distinct visual treatment).

* docs(changelog): announce Phase 4 discovery & progress (#2826)

* chore(release): bump dev to 1.50.0-canary.0 for first 1.50.0 canary

Sets the base version that .github/workflows/canary.yml derives the canary
tag from (strips suffix → base 1.50.0 → next available v1.50.0-canary.N).

This kicks off the 1.50.0 release train, opened by the MVP/TDD/UAT vertical
slice landed across PRs #2867, #2874, #2878, #2880, #2883.

* docs: add CANARY stream README + v1.50.0-canary.1 release notes

- docs/CANARY.md — explains the dev→@canary stream policy, install/rollback
  paths, and when (not) to install canary builds
- docs/RELEASE-v1.50.0-canary.1.md — release notes for the first 1.50.0
  canary cut: vertical MVP/TDD/UAT slice (#2867 + #2874 + #2878 + #2880 +
  #2883), opening the 1.50.0 train under PRD #2826
- docs/README.md — index entry + quick link for the canary stream

* fix(ci/canary): publish gate checks dev branch, not main

Four publish-step `if:` conditions in .github/workflows/canary.yml were
checking `github.ref == 'refs/heads/main'`. Those steps (Tag and push,
Publish to npm, Publish SDK to npm, Verify publish) therefore always
skipped on every workflow_dispatch invocation since canary runs from dev,
never main.

The workflow's own header comment is unambiguous: `dev → @canary`. The
gate was a copy-paste from release.yml (which correctly targets main for
the @next/@latest streams) that was never corrected for the canary stream.

This is why the 1.50.0-canary.1 publish hadn't materialized despite three
green workflow runs. With the gate corrected, the next dispatch will
actually publish.

* ci(release-sdk): make release-sdk.yml dispatchable from the dev branch

The workflow lives on main only, so the GitHub Actions "Use workflow
from" dropdown doesn't list dev — meaning dev → @dev publishes can't be
triggered from the dev branch directly. Add the file to dev so an
operator can dispatch it with branch=dev and tag=dev.

Per project release-stream policy: dev branch publishes canary (@dev).
This is the stream that needs the file most, since main never publishes
@dev itself (main does @next / @latest).

File is byte-identical to main's release-sdk.yml — straight propagation,
no behavioral change. Tracking issues #2925, #2929.

* docs(mvp): canary-prep concept cleanup — CONTEXT.md, mvp-concepts index, --prd interaction (#3176)

* chore(mvp): concept cleanup + cross-ref index for v1.50.0-canary.2 prep

- CONTEXT.md gains 7 MVP domain terms (MVP Mode, User Story, Walking
  Skeleton, Vertical Slice, Behavior-Adding Task, MVP+TDD Gate, SPIDR
  Splitting) so the project glossary matches the shipped surface.
- New get-shit-done/references/mvp-concepts.md indexes the six MVP
  reference files and concept-to-file map so agents and contributors
  can find the right canonical doc without grepping.
- plan-phase.md Walking Skeleton block now documents that --mvp and
  --prd compose orthogonally on Phase 1; no precedence needed.
- INVENTORY/INVENTORY-MANIFEST refreshed for the new reference (58 -> 59).

No behavior change. Canary-prep cleanup ahead of v1.50.0-canary.2.

Surfaced for follow-up (not in this PR):
- MVP_MODE resolution shell block duplicated across plan-phase,
  execute-phase, verify-work workflows (needs a shared workflow-include
  mechanism; structural change).
- Behavior-Adding Task predicate is prose-only; no shared utility.
- User Story regex hardcoded in verify-work; would benefit from a
  central definition consumed by the verifier and the mvp-phase command.

* chore(changeset): set PR number for mvp concept cleanup

* feat(mvp): centralize resolution surfaces + fix SDK roadmap mode parity (#3178)

Three new SDK query verbs replace the architectural duplication surfaced by
the v1.50.0-canary.2 review against dev tip 12c4e565:

  phase.mvp-mode <N> [--cli-flag]
    Single canonical precedence resolver (CLI flag -> ROADMAP **Mode:** mvp
    -> workflow.mvp_mode config -> false). Replaces 4-8 lines of bash that
    were duplicated across plan-phase.md, execute-phase.md, verify-work.md,
    and progress.md. Returns {active, source, roadmap_mode, config_mvp_mode,
    cli_flag_present}.

  task.is-behavior-adding <plan-file> | --task-content <xml>
    Behavior-Adding Task predicate (tdd="true" + <behavior> block + non-test
    source files in <files>). Replaces prose-only specification in
    references/execute-mvp-tdd.md; gsd-executor agent now invokes the verb
    instead of re-inlining the three checks. Returns {is_behavior_adding,
    checks, reason}.

  user-story.validate <text> | --story <text>
    Owns the canonical User Story regex /^As a .+, I want to .+, so that .+\.$/
    previously hardcoded in verify-work.md prose. Consumed by gsd-verifier
    (phase-goal guard) and /gsd-mvp-phase (interactive-prompt validation).
    Returns {valid, slots: {role, capability, outcome}, errors[]}.

Bug fix bundled: sdk/src/query/roadmap.ts searchPhaseInContent now extracts
the mode field from **Mode:**, restoring parity with roadmap.cjs:120-123.
Without this, roadmap.get-phase --pick mode returned null on the native
dispatch path even when the phase had **Mode:** mvp set, causing MVP_MODE
to silently fall through to the config/false branch in every consuming
workflow. The original PRs Phase 1 (#2885) shipped the CJS parser but the
SDK port omitted the field; this fix brings them back to parity.

Workflows + agents updated to call the verbs:
  - plan-phase.md, execute-phase.md, verify-work.md, progress.md call
    phase.mvp-mode (one line replaces the duplicated bash chains).
  - execute-phase.md MVP+TDD gate calls task.is-behavior-adding.
  - verify-work.md goal guard calls user-story.validate.
  - mvp-phase.md interactive prompt validates via user-story.validate.
  - gsd-executor agent references task.is-behavior-adding instead of prose.
  - gsd-verifier agent references user-story.validate instead of inlined regex.

Tests: 24 new vitest tests in sdk/src/query/mvp.test.ts cover all three
verbs + the regression. Two existing contract tests (progress, verify)
updated to assert on the new verb shape. All 60 existing MVP contract
tests pass; golden integration suite (38 + 42 tests) passes.

Closes #3177

* fix(canary.2): unblock release gates for v1.50.0-canary.2

Run 25451329660 (Release SDK Bundle on dev, 2026-05-06T17:41) failed at the
test-suite step with 3 deterministic content/structure gate failures, all
attributable to the MVP umbrella integration in #3178 and the docs sweep
in #3180.

Failure 1: /gsd-mvp-phase undocumented in workflows/help.md
  - tests/bug-2954-help-md-slash-command-stubs.test.cjs requires every
    shipped commands/gsd/<X>.md to have a /gsd-<X> mention in help.md
  - PR #3180 updated docs/COMMANDS.md but missed help.md (which the AI
    agents load in-product)
  - Fix: add a /gsd-mvp-phase entry to help.md right before /gsd-plan-phase

Failures 2 + 3: execute-phase.md (1727) and plan-phase.md (1714) over XL budget (1700)
  - PR #3178 added MVP-mode verb calls (phase.mvp-mode, task.is-behavior-adding,
    user-story.validate) to both workflow files, pushing them past 1700 lines
  - Fix: bump XL_BUDGET 1700 -> 1800 with inline comment pointing at the
    structural follow-up (extract MVP bodies to <workflow>/modes/mvp.md per
    the discuss-phase/modes/ precedent)
  - The structural extract is the right long-term fix but is bigger than
    canary unblock scope; will land in a follow-up after canary cycles

Local verification:
  $ node --test tests/bug-2954-help-md-slash-command-stubs.test.cjs                 tests/workflow-size-budget.test.cjs
  tests 111  pass 111  fail 0

After this lands, re-trigger Release SDK Bundle on dev for v1.50.0-canary.2.

* chore(changeset): set PR number for canary.2 unblock

* fix(codex): generate-claude-md writes to AGENTS.md on Codex runtime

When config.runtime === 'codex' or GSD_RUNTIME=codex, override the
output target to AGENTS.md regardless of claude_md_path, so Codex
projects no longer have GSD sections written to CLAUDE.md by mistake.

Fixes both the CJS (gsd-tools) and SDK (profile-output.ts) paths.
Explicit --output flags are still honoured in both paths.

Closes #3163

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

* fix(plan-phase): remove agent: directive that caused OpenCode subagent dispatch

On OpenCode, any command with `agent: <name>` in its frontmatter is
auto-dispatched to a subagent context where the Agent tool is unavailable.
plan-phase.md and mvp-phase.md both carried `agent: gsd-planner`, causing
them to run inside gsd-planner's subagent context with no ability to spawn
researcher/planner/checker subagents — the orchestrator fell back to inline
execution for all three phases.

Fix: remove `agent: gsd-planner` from both command files so they run in the
main agent context. Also replace the stale `Task` tool in allowed-tools with
`Agent` (the correct dispatcher tool name post-#3168 rename).

Adds a structural regression test that parses YAML frontmatter of every
commands/gsd/*.md file and asserts no command carries an `agent:` directive.

Closes #3156

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

* fix(mvp): address CodeRabbit workflow and contract findings

* fix(execute-phase): use registered state.update query command

---------

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

336 lines
14 KiB
TypeScript

/**
* Tests for the three MVP-mode query handlers in `mvp.ts`:
* - `phase.mvp-mode` — precedence chain resolver
* - `task.is-behavior-adding` — three-check predicate
* - `user-story.validate` — regex validator
*
* Plus the regression for the SDK roadmap-port mode-extraction bug
* (`searchPhaseInContent` previously omitted the `mode` field).
*/
import { describe, it, expect } from 'vitest';
import { mkdtempSync, rmSync, mkdirSync, writeFileSync } from 'node:fs';
import { tmpdir } from 'node:os';
import { join } from 'node:path';
import {
phaseMvpMode,
taskIsBehaviorAdding,
userStoryValidate,
USER_STORY_REGEX,
} from './mvp.js';
import { roadmapGetPhase } from './roadmap.js';
function tmpProject(): string {
const dir = mkdtempSync(join(tmpdir(), 'gsd-mvp-test-'));
mkdirSync(join(dir, '.planning'), { recursive: true });
return dir;
}
function writeRoadmap(dir: string, body: string): void {
writeFileSync(join(dir, '.planning', 'ROADMAP.md'), body);
}
function writeConfig(dir: string, config: Record<string, unknown>): void {
writeFileSync(join(dir, '.planning', 'config.json'), JSON.stringify(config));
}
function writeWorkstreamConfig(dir: string, workstream: string, config: Record<string, unknown>): void {
const wsDir = join(dir, '.planning', 'workstreams', workstream);
mkdirSync(wsDir, { recursive: true });
writeFileSync(join(wsDir, 'config.json'), JSON.stringify(config));
}
// ─── roadmap.get-phase mode field regression ────────────────────────────────
describe('roadmap.get-phase: mode field (regression)', () => {
it('extracts **Mode:** mvp from a phase section', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `# Roadmap\n\n## Phase 1: Walking Skeleton\n\n**Mode:** mvp\n**Goal:** Ship the walking skeleton.\n\n**Success Criteria**:\n1. Stack works end-to-end\n`);
const result = await roadmapGetPhase(['1'], dir);
const data = result.data as { found: boolean; mode?: string | null };
expect(data.found).toBe(true);
expect(data.mode).toBe('mvp');
} finally {
rmSync(dir, { recursive: true, force: true });
}
});
it('returns mode=null when **Mode:** absent', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `# Roadmap\n\n## Phase 2: Standard\n\n**Goal:** Generic phase.\n`);
const result = await roadmapGetPhase(['2'], dir);
const data = result.data as { found: boolean; mode?: string | null };
expect(data.found).toBe(true);
expect(data.mode).toBeNull();
} finally {
rmSync(dir, { recursive: true, force: true });
}
});
it('preserves unrecognized mode verbatim (lowercased) for forward-compat', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `# Roadmap\n\n## Phase 3: Future\n\n**Mode:** Spike\n**Goal:** Try a spike.\n`);
const result = await roadmapGetPhase(['3'], dir);
const data = result.data as { found: boolean; mode?: string | null };
expect(data.mode).toBe('spike');
} finally {
rmSync(dir, { recursive: true, force: true });
}
});
});
// ─── phase.mvp-mode ─────────────────────────────────────────────────────────
describe('phase.mvp-mode', () => {
it('rejects missing phase argument', async () => {
await expect(phaseMvpMode([], '/tmp')).rejects.toThrow(/Usage: phase.mvp-mode/);
});
it('CLI flag wins over roadmap and config', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `## Phase 1: X\n\n**Goal:** Test.\n`);
writeConfig(dir, { workflow: { mvp_mode: false } });
const result = await phaseMvpMode(['1', '--cli-flag'], dir);
expect(result.data.active).toBe(true);
expect(result.data.source).toBe('cli_flag');
expect(result.data.cli_flag_present).toBe(true);
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('roadmap **Mode:** mvp activates when CLI flag absent', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `## Phase 1: X\n\n**Mode:** mvp\n**Goal:** Test.\n`);
writeConfig(dir, { workflow: { mvp_mode: false } });
const result = await phaseMvpMode(['1'], dir);
expect(result.data.active).toBe(true);
expect(result.data.source).toBe('roadmap');
expect(result.data.roadmap_mode).toBe('mvp');
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('roadmap mode is normalized before comparison (MVP/whitespace still activates)', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `## Phase 1: X\n\n**Mode:** MVP \n**Goal:** Test.\n`);
writeConfig(dir, { workflow: { mvp_mode: false } });
const result = await phaseMvpMode(['1'], dir);
expect(result.data.active).toBe(true);
expect(result.data.source).toBe('roadmap');
expect(result.data.roadmap_mode).toBe('mvp');
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('config workflow.mvp_mode=true activates when CLI and roadmap absent', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `## Phase 1: X\n\n**Goal:** Test.\n`);
writeConfig(dir, { workflow: { mvp_mode: true } });
const result = await phaseMvpMode(['1'], dir);
expect(result.data.active).toBe(true);
expect(result.data.source).toBe('config');
expect(result.data.config_mvp_mode).toBe(true);
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('workstream config overrides root config when workstream is provided', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `## Phase 1: X\n\n**Goal:** Test.\n`);
writeConfig(dir, { workflow: { mvp_mode: false } });
writeWorkstreamConfig(dir, 'alpha', { workflow: { mvp_mode: true } });
const result = await phaseMvpMode(['1'], dir, 'alpha');
expect(result.data.active).toBe(true);
expect(result.data.source).toBe('config');
expect(result.data.config_mvp_mode).toBe(true);
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('all three signals absent → active=false, source=none', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `## Phase 1: X\n\n**Goal:** Test.\n`);
writeConfig(dir, { workflow: {} });
const result = await phaseMvpMode(['1'], dir);
expect(result.data.active).toBe(false);
expect(result.data.source).toBe('none');
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('non-mvp roadmap mode does not activate (forward-compat preservation)', async () => {
const dir = tmpProject();
try {
writeRoadmap(dir, `## Phase 1: X\n\n**Mode:** spike\n**Goal:** Test.\n`);
writeConfig(dir, { workflow: {} });
const result = await phaseMvpMode(['1'], dir);
expect(result.data.active).toBe(false);
expect(result.data.roadmap_mode).toBe('spike');
} finally { rmSync(dir, { recursive: true, force: true }); }
});
});
// ─── task.is-behavior-adding ────────────────────────────────────────────────
describe('task.is-behavior-adding', () => {
it('rejects when neither path nor --task-content given', async () => {
await expect(taskIsBehaviorAdding([], '/tmp')).rejects.toThrow(/Usage:/);
});
it('rejects nonexistent file path', async () => {
await expect(taskIsBehaviorAdding(['/tmp/__nope__.md'], '/tmp')).rejects.toThrow(/not found/);
});
it('all three checks pass → is_behavior_adding=true', async () => {
const result = await taskIsBehaviorAdding([
'--task-content',
`<task tdd="true">\n<behavior>User can log in</behavior>\n<files>\nsrc/auth.ts\nsrc/auth.test.ts\n</files>\n</task>`,
], '/tmp');
expect(result.data.is_behavior_adding).toBe(true);
expect(result.data.checks).toEqual({
tdd_true: true,
has_behavior_block: true,
has_source_files: true,
});
expect(result.data.reason).toBeNull();
});
it('tdd="false" → not behavior-adding', async () => {
const result = await taskIsBehaviorAdding([
'--task-content',
`<task tdd="false">\n<behavior>User can log in</behavior>\n<files>src/auth.ts</files>\n</task>`,
], '/tmp');
expect(result.data.is_behavior_adding).toBe(false);
expect(result.data.checks.tdd_true).toBe(false);
expect(result.data.reason).toMatch(/tdd="true" frontmatter absent/);
});
it('empty <behavior> block → not behavior-adding', async () => {
const result = await taskIsBehaviorAdding([
'--task-content',
`<task tdd="true">\n<behavior> </behavior>\n<files>src/a.ts</files>\n</task>`,
], '/tmp');
expect(result.data.is_behavior_adding).toBe(false);
expect(result.data.checks.has_behavior_block).toBe(false);
});
it('only test files in <files> → not behavior-adding', async () => {
const result = await taskIsBehaviorAdding([
'--task-content',
`<task tdd="true">\n<behavior>X</behavior>\n<files>\nsrc/a.test.ts\nsrc/b.spec.js\n</files>\n</task>`,
], '/tmp');
expect(result.data.is_behavior_adding).toBe(false);
expect(result.data.checks.has_source_files).toBe(false);
});
it('only docs in <files> → not behavior-adding', async () => {
const result = await taskIsBehaviorAdding([
'--task-content',
`<task tdd="true">\n<behavior>X</behavior>\n<files>\ndocs/X.md\nconfig.json\n</files>\n</task>`,
], '/tmp');
expect(result.data.is_behavior_adding).toBe(false);
expect(result.data.checks.has_source_files).toBe(false);
});
it('reads from a file path on disk', async () => {
const dir = tmpProject();
try {
const file = join(dir, 'plan.md');
writeFileSync(file, `<task tdd="true">\n<behavior>X</behavior>\n<files>src/a.ts</files>\n</task>`);
const result = await taskIsBehaviorAdding([file], dir);
expect(result.data.is_behavior_adding).toBe(true);
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('rejects task file path outside project scope', async () => {
const dir = tmpProject();
try {
await expect(taskIsBehaviorAdding(['/tmp/outside-plan.md'], dir))
.rejects
.toThrow(/outside project scope/);
} finally { rmSync(dir, { recursive: true, force: true }); }
});
it('config-only files in <files> are excluded from behavior-adding', async () => {
const result = await taskIsBehaviorAdding([
'--task-content',
`<task tdd="true">\n<behavior>Update settings</behavior>\n<files>\nconfig/app.yaml\n.env.local\nsettings.toml\n</files>\n</task>`,
], '/tmp');
expect(result.data.is_behavior_adding).toBe(false);
expect(result.data.checks.has_source_files).toBe(false);
});
it('files under tests/ are excluded from behavior-adding source-file detection', async () => {
const result = await taskIsBehaviorAdding([
'--task-content',
`<task tdd="true">\n<behavior>Adjust tests only</behavior>\n<files>\ntests/user-flow.spec.ts\ntest/helpers.ts\n</files>\n</task>`,
], '/tmp');
expect(result.data.is_behavior_adding).toBe(false);
expect(result.data.checks.has_source_files).toBe(false);
});
});
// ─── user-story.validate ────────────────────────────────────────────────────
describe('user-story.validate', () => {
it('rejects empty input', async () => {
await expect(userStoryValidate([], '/tmp')).rejects.toThrow(/Usage:/);
});
it('canonical user story is valid + slots extracted', async () => {
const result = await userStoryValidate([
'As a solo developer, I want to log in, so that I can see my dashboard.',
], '/tmp');
expect(result.data.valid).toBe(true);
expect(result.data.slots).toEqual({
role: 'solo developer',
capability: 'log in',
outcome: 'I can see my dashboard',
});
expect(result.data.errors).toEqual([]);
});
it('--story flag form parses single argument', async () => {
const result = await userStoryValidate([
'--story',
'As a user, I want to bulk-import contacts, so that onboarding takes seconds.',
], '/tmp');
expect(result.data.valid).toBe(true);
expect(result.data.slots?.role).toBe('user');
});
it('missing terminal period flagged', async () => {
const result = await userStoryValidate([
'As a user, I want to X, so that Y',
], '/tmp');
expect(result.data.valid).toBe(false);
expect(result.data.errors.some(e => /period/.test(e))).toBe(true);
});
it('missing "I want to" phrase flagged', async () => {
const result = await userStoryValidate([
'As a user, I would like X, so that Y.',
], '/tmp');
expect(result.data.valid).toBe(false);
expect(result.data.errors.some(e => /I want to/.test(e))).toBe(true);
});
it('missing "As a " prefix flagged', async () => {
const result = await userStoryValidate([
'A user wants X, I want to log in, so that Y.',
], '/tmp');
expect(result.data.valid).toBe(false);
expect(result.data.errors.some(e => /As a/.test(e))).toBe(true);
});
it('USER_STORY_REGEX is exported and matches the canonical shape', () => {
expect(USER_STORY_REGEX.test('As a X, I want to Y, so that Z.')).toBe(true);
expect(USER_STORY_REGEX.test('As a X, I want to Y, so that Z')).toBe(false);
expect(USER_STORY_REGEX.test('As X, I want to Y, so that Z.')).toBe(false);
});
});