🟡 P1: v2/nice-to-have features get weird phase numbers (14.5, 15.5, etc.)

[mmorris35]

Problem

Nice-to-have features from the brief become phases with decimal numbers that look broken:

## Phase 14.5 (v2): Prometheus metrics
## Phase 15.5 (v2): Hybrid search
## Phase 16.5 (v2): Embedding caching
## Phase 17.5 (v2): Quantized INT8 model

Expected Behavior

Nice-to-have features should be grouped cleanly:

Option A - Single deferred section:

## Future Enhancements (v2)

These features are deferred until after MVP:

### Prometheus metrics
- Requirements TBD based on MVP learnings

### Hybrid search
- Requirements TBD based on MVP learnings

Option B - Numbered but separate:

## Phase 10: Future Enhancements

### 10.1: Prometheus metrics (v2 - Deferred)
### 10.2: Hybrid search (v2 - Deferred)

Impact

Moderate - The decimal phase numbers look like a bug to users. Creates confusion about plan structure.

[mmorris35]

Staging Verification (2026-02-14)

Status: NOT FIXED on staging

Re-generated the corporate-buzzword-bingo plan using DevPlan Staging MCP. v2 features still use X.5 phase numbering:

## Phase 9.5 (v2): WebSocket support for real-time bingo announcements
## Phase 10.5 (v2): Buzzword frequency analytics per meeting
## Phase 11.5 (v2): Custom buzzword lists per team
## Phase 12.5 (v2): Slack integration for /bingo slash command

This is unchanged from previous behavior.

Test artifacts: test-projects/corporate-buzzword-bingo/DEVELOPMENT_PLAN.md (lines 496-604)

[mmorris35]

Fix Verified

Root Cause

generateDeferredPhases() used X.5 numbering (e.g., Phase 9.5, Phase 10.5) for nice-to-have features. This created confusing phase numbers that didn't fit the integer phase scheme.

Fix

Completely rewrote generateDeferredPhases() to use clean v2 Roadmap heading with v2.1, v2.2, etc. numbering. These are clearly separated from MVP phases and have proper status/prerequisite info.

Verification (production MCP output for brief with 4 nice-to-have features):

## v2 Roadmap (Post-MVP Features)

### v2.1: WebSocket support for real-time bingo announcements
### v2.2: Buzzword frequency analytics per meeting
### v2.3: Custom buzzword lists per team
### v2.4: Slack integration for /bingo slash command

• No Phase X.5 anywhere ✅
• Clean v2.N numbering ✅
• Clear separation from MVP phases ✅

317/317 tests pass. Deployed to production.