mindsystem-cc 3.16.1 → 3.17.0

package/README.md

@@ -269,8 +269,8 @@ Replace `<N>` with the phase number you're working on.
 
 **What you'll get:**
 
-- `.planning/milestones/v1.0-DECISIONS.md` — consolidated decisions for future reference
-- `.planning/milestones/v1.0-ROADMAP.md` / `v1.0-REQUIREMENTS.md` — archived detail to keep active docs lean
+- `.planning/milestones/v1.0/` — archived milestone (ROADMAP, REQUIREMENTS, DECISIONS, research)
+- Active docs stay lean; full detail lives in the version folder
 
 **Tip:** Milestone review can be **report-only** (e.g., Flutter structural review) so you stay in control. Create a quality phase, or accept tech debt explicitly — your call.
 

package/agents/ms-plan-writer.md

@@ -294,11 +294,11 @@ Create `.planning/phases/{phase_dir}/EXECUTION-ORDER.md`:
 # Execution Order
 
 ## Wave 1 (parallel)
-- 01-PLAN.md — {description}
-- 02-PLAN.md — {description}
+- {phase}-01-PLAN.md — {description}
+- {phase}-02-PLAN.md — {description}
 
 ## Wave 2 (parallel)
-- 03-PLAN.md — {description} (depends on 01 for {reason})
+- {phase}-03-PLAN.md — {description} (depends on 01 for {reason})
 ```
 
 Rules:

package/commands/ms/audit-milestone.md

@@ -306,26 +306,23 @@ Use AskUserQuestion with options A and B.
 
 1. Determine next phase number (append at end of current phases)
 2. Create phase directory: `.planning/phases/{NN}-code-quality/`
-3. Create `PHASE-FINDINGS.md` with full review findings
-4. Update ROADMAP.md with new phase:
+3. Update ROADMAP.md with new phase:
 
 ```markdown
 ### Phase {N}: Code Quality (Generated)
 **Goal:** Address structural improvements from milestone code review
-
-**Findings to address:**
-[High impact items from review]
+**Scope:** High and Medium items from .planning/TECH-DEBT.md
 
 Plans:
 - [ ] {N}-01: High impact structural fixes
 ```
 
-5. Report:
+4. Report:
 ```markdown
 ## Quality Phase Created
 
 **Phase {N}:** `.planning/phases/{NN}-code-quality/`
-**Findings documented:** `PHASE-FINDINGS.md`
+**Scope source:** `.planning/TECH-DEBT.md`
 
 ---
 
@@ -394,13 +391,15 @@ After code review (all sources now available), generate or update `.planning/TEC
 
 1. **Read existing** `.planning/TECH-DEBT.md` (if exists) — parse active items and dismissed list, note highest `TD-{N}` ID
 2. **Read template** from `@~/.claude/mindsystem/templates/tech-debt.md`
-3. **Collect tech debt** from all sources:
-   - Phase VERIFICATION.md anti-patterns (severity: warning or info — blockers go to `gaps`)
-   - Non-critical gaps from phase verifications
-   - Code review findings (if analyze-only reviewer was used in Step 8)
+3. **Collect tech debt** from all sources with severity mapping:
+   - Integration checker bugs → **Critical**
+   - Unfixed UAT issues (result: `issue`, fix_status ≠ `verified`) → **Critical** (blocker) / **High** (major) / **Medium** (minor) / **Low** (cosmetic)
+   - Code review findings → pass through reviewer severity (**High** / **Medium** / **Low**)
+   - Phase VERIFICATION.md anti-patterns → **Medium** or **Low** (blockers go to `gaps`, not tech debt)
+   - Non-critical gaps from phase verifications → **Medium**
 4. **De-duplicate** against existing active items AND dismissed items (match by location + description similarity)
 5. **Assign `TD-{N}` IDs** continuing from highest existing ID
-6. **Write/update** `.planning/TECH-DEBT.md` following the template format
+6. **Write/update** `.planning/TECH-DEBT.md` — group items under `## Critical`, `## High`, `## Medium`, `## Low` sections per template. Omit empty sections.
 
 ## 9. Commit Audit Report
 
@@ -432,7 +431,7 @@ Read `~/.claude/mindsystem/references/routing/audit-result-routing.md` and follo
 - [ ] Code review completed (or skipped if config says "skip")
 - [ ] If analyze-only reviewer: YAML findings parsed and added to report
 - [ ] If analyze-only reviewer: Binary decision presented (quality phase vs tech debt)
-- [ ] If quality phase chosen: Phase directory created with PHASE-FINDINGS.md
+- [ ] If quality phase chosen: Phase directory created, ROADMAP updated with TECH-DEBT.md scope
 - [ ] MILESTONE-AUDIT.md committed to git
 - [ ] Results presented with actionable next steps
 </success_criteria>

package/commands/ms/complete-milestone.md

@@ -91,18 +91,24 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 
 4. **Archive milestone:**
 
-   - Create `.planning/milestones/v{{version}}-ROADMAP.md`
+   - Create `.planning/milestones/v{{version}}/` directory
+   - Create `.planning/milestones/v{{version}}/ROADMAP.md`
    - Extract full phase details from ROADMAP.md
    - Fill milestone-archive.md template
    - Update ROADMAP.md to one-line summary with link
 
 5. **Archive requirements:**
 
-   - Create `.planning/milestones/v{{version}}-REQUIREMENTS.md`
+   - Create `.planning/milestones/v{{version}}/REQUIREMENTS.md`
    - Mark all v1 requirements as complete (checkboxes checked)
    - Note requirement outcomes (validated, adjusted, dropped)
    - Delete `.planning/REQUIREMENTS.md` (fresh one created for next milestone)
 
+5.5. **Archive research:**
+
+   - If `.planning/research/` exists, move to `.planning/milestones/v{{version}}/research/`
+   - Skip silently if no research directory exists
+
 6. **Update PROJECT.md:**
 
    - Add "Current State" section with shipped version
@@ -128,8 +134,9 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 <success_criteria>
 
 - Raw artifacts cleaned from phase directories (CONTEXT, DESIGN, RESEARCH, SUMMARY, UAT, VERIFICATION, EXECUTION-ORDER)
-- Milestone archived to `.planning/milestones/v{{version}}-ROADMAP.md`
-- Requirements archived to `.planning/milestones/v{{version}}-REQUIREMENTS.md`
+- Milestone archived to `.planning/milestones/v{{version}}/ROADMAP.md`
+- Requirements archived to `.planning/milestones/v{{version}}/REQUIREMENTS.md`
+- Research archived to `.planning/milestones/v{{version}}/research/` (if existed)
 - `.planning/REQUIREMENTS.md` deleted (fresh for next milestone)
 - ROADMAP.md collapsed to one-line entry
 - PROJECT.md updated with current state

package/commands/ms/new-milestone.md

@@ -64,7 +64,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
 3. **Strategic assessment (silent — do not output this step):**
    - Check for previous milestone artifacts using calculated version:
      - `.planning/knowledge/*.md` (subsystem knowledge files — persist across milestones)
-     - `.planning/milestones/v{VERSION}-MILESTONE-AUDIT.md` (if exists)
+     - `.planning/milestones/v{VERSION}/MILESTONE-AUDIT.md` (if exists)
      - `.planning/TECH-DEBT.md` (if exists)
    - Identify: outstanding tech debt, untested assumptions, high-impact gaps, unaddressed requirements
    - This is background analysis — synthesize silently, surface through suggestions in step 4

package/commands/ms/plan-phase.md

@@ -67,6 +67,10 @@ Check for and read `.planning/phases/XX-name/{phase}-CONTEXT.md` - contains rese
 **Load design specs if exists (created by /ms:design-phase):**
 Check for and read `.planning/phases/XX-name/{phase}-DESIGN.md` - contains visual/UX specifications including layouts, components, flows, and verification criteria.
 
+**Load tech debt if quality/cleanup phase:**
+If phase name or roadmap goal contains "quality", "cleanup", "refactor", or "tech debt":
+Check for and read `.planning/TECH-DEBT.md` — prioritized issues for scope selection during task breakdown.
+
 **Load codebase context if exists:**
 Check for `.planning/codebase/` and load relevant documents based on phase type.
 

package/mindsystem/references/plan-format.md

@@ -160,15 +160,15 @@ Execution order lives in a single `EXECUTION-ORDER.md` file alongside the plans.
 # Execution Order
 
 ## Wave 1 (parallel)
-- 01-PLAN.md — Database schema and Prisma client
-- 02-PLAN.md — Environment configuration
+- 03-01-PLAN.md — Database schema and Prisma client
+- 03-02-PLAN.md — Environment configuration
 
 ## Wave 2 (parallel)
-- 03-PLAN.md — Auth endpoints (depends on schema from 01)
-- 04-PLAN.md — User profile CRUD (depends on schema from 01)
+- 03-03-PLAN.md — Auth endpoints (depends on schema from 01)
+- 03-04-PLAN.md — User profile CRUD (depends on schema from 01)
 
 ## Wave 3
-- 05-PLAN.md — Protected route middleware (depends on auth from 03)
+- 03-05-PLAN.md — Protected route middleware (depends on auth from 03)
 ```
 
 **Rules:**

package/mindsystem/templates/milestone-archive.md

@@ -112,8 +112,8 @@ _For current project status, see .planning/ROADMAP.md_
 
 **Archive location:**
 
-- Save to `.planning/milestones/v{VERSION}-{NAME}.md`
-- Example: `.planning/milestones/v1.0-mvp.md`
+- Save to `.planning/milestones/v{VERSION}/ROADMAP.md`
+- Example: `.planning/milestones/v1.0/ROADMAP.md`
 
 **After archiving:**
 

package/mindsystem/templates/tech-debt.md

@@ -6,11 +6,11 @@ Template for `.planning/TECH-DEBT.md` — single source of truth for all tech de
 
 ## Usage
 
-Created and updated by `/ms:audit-milestone`. Items persist across milestones. Users reference items manually via `/ms:adhoc` (small fixes) or `/ms:insert-phase` (larger remediation).
+Created and updated by `/ms:audit-milestone`. Items persist across milestones. Users reference items manually via `/ms:adhoc` (small fixes) or `/ms:insert-phase` (larger remediation). Loaded automatically by `/ms:plan-phase` for quality/cleanup phases.
 
 **Item IDs** use `TD-{N}` format — monotonically increasing, never reused. New items continue from highest existing ID.
 
-**Sources:** Phase verifications (anti-patterns, non-critical gaps), code review findings.
+**Sources:** Phase verifications (anti-patterns, non-critical gaps), code review findings, integration checker bugs, unfixed UAT issues.
 
 ---
 
@@ -23,17 +23,14 @@ Created and updated by `/ms:audit-milestone`. Items persist across milestones. U
 > Single source of truth for tech debt. Updated by `/ms:audit-milestone`.
 > Address items via `/ms:adhoc` (1-2 tasks) or `/ms:insert-phase` (larger work).
 
-## Active Items
+## {Severity}
+<!-- Sections in order: Critical, High, Medium, Low. Omit empty sections. -->
 
 ### TD-{N}: {Title}
-- **Phase:** {source phase, e.g. 03-chat}
-- **Source:** {verification | code-review | anti-pattern}
-- **Severity:** {blocker | warning | info}
 - **Location:** {file:line or component}
-- **Impact:** {what this causes}
-- **Suggested fix:** {how to address}
-- **Related files:** {other affected files}
-- **Identified:** v{milestone} | {YYYY-MM-DD}
+- **Impact:** {what this causes and why it matters}
+- **Fix:** {how to address}
+- <sub>Phase {source phase} | {verification | integration-check | code-review} | v{milestone}</sub>
 
 ---
 
@@ -50,9 +47,19 @@ Created and updated by `/ms:audit-milestone`. Items persist across milestones. U
 ## Guidelines
 
 **Severity levels:**
-- `blocker` — Prevents future work or degrades reliability. Rare in tech debt (blockers usually go to `gaps`).
-- `warning` — Indicates incomplete or fragile code. Common for TODOs, missing validation, stubs.
-- `info` — Notable but low impact. Style issues, minor inconsistencies, improvement opportunities.
+- `Critical` — Breaks behavior or risks data loss. Integration checker bugs (broken cross-phase wiring, failed E2E flows) always map here.
+- `High` — Causes cascading changes if left unaddressed. Fragile patterns that spread to new code, missing abstractions forcing workarounds.
+- `Medium` — Contained friction. TODOs, missing validation, incomplete error handling. Impact stays local.
+- `Low` — Won't compound. Style inconsistencies, minor naming issues, improvement opportunities.
+
+**Severity mapping from sources:**
+- Integration checker bugs → Critical
+- Unfixed UAT issues → Critical (blocker) / High (major) / Medium (minor) / Low (cosmetic)
+- Code review findings → pass through reviewer severity (High/Medium/Low)
+- Phase verification anti-patterns → Medium or Low (blockers go to `gaps`, not tech debt)
+- Non-critical verification gaps → Medium
+
+**Empty sections:** Omit severity sections with no items. Keep only sections that contain entries.
 
 **De-duplication:** Match by location + description similarity. An item in Dismissed is never re-added as Active — if the same issue recurs, note it as a new item referencing the original.
 

package/mindsystem/workflows/complete-milestone.md

@@ -23,13 +23,15 @@ This is the ritual that separates "development" from "shipped."
 When a milestone completes, this workflow:
 
 1. Cleans up raw phase artifacts (CONTEXT, DESIGN, RESEARCH, SUMMARY, UAT, VERIFICATION, EXECUTION-ORDER deleted)
-2. Extracts full milestone details to `.planning/milestones/v[X.Y]-ROADMAP.md`
-3. Archives requirements to `.planning/milestones/v[X.Y]-REQUIREMENTS.md`
-4. Archives milestone context to `.planning/milestones/v[X.Y]-CONTEXT.md`
-5. Updates ROADMAP.md to replace milestone details with one-line summary
-6. Deletes REQUIREMENTS.md (fresh one created for next milestone)
-7. Performs full PROJECT.md evolution review
-8. Routes to `/ms:new-milestone` for next milestone
+2. Creates `.planning/milestones/v[X.Y]/` directory for all archive files
+3. Extracts full milestone details to `.planning/milestones/v[X.Y]/ROADMAP.md`
+4. Archives requirements to `.planning/milestones/v[X.Y]/REQUIREMENTS.md`
+5. Archives milestone context to `.planning/milestones/v[X.Y]/CONTEXT.md`
+6. Archives research files to `.planning/milestones/v[X.Y]/research/` (if exists)
+7. Updates ROADMAP.md to replace milestone details with one-line summary
+8. Deletes REQUIREMENTS.md (fresh one created for next milestone)
+9. Performs full PROJECT.md evolution review
+10. Routes to `/ms:new-milestone` for next milestone
 
 Knowledge files in `.planning/knowledge/` persist across milestones (maintained by phase-level consolidation in execute-phase).
 
@@ -428,7 +430,11 @@ Extract completed milestone details and create archive file.
 
 **Process:**
 
-1. Create archive file path: `.planning/milestones/v[X.Y]-ROADMAP.md`
+1. Create milestone directory and archive file:
+   ```bash
+   mkdir -p .planning/milestones/v[X.Y]
+   ```
+   Archive file path: `.planning/milestones/v[X.Y]/ROADMAP.md`
 
 2. Read `~/.claude/mindsystem/templates/milestone-archive.md` template
 
@@ -453,7 +459,7 @@ Extract completed milestone details and create archive file.
    - {{DECISIONS_FROM_PROJECT}} — Key decisions from PROJECT.md
    - {{ISSUES_RESOLVED_DURING_MILESTONE}} — From summaries
 
-6. Write filled template to `.planning/milestones/v[X.Y]-ROADMAP.md`
+6. Write filled template to `.planning/milestones/v[X.Y]/ROADMAP.md`
 
 7. Delete ROADMAP.md (fresh one created for next milestone):
    ```bash
@@ -462,13 +468,13 @@ Extract completed milestone details and create archive file.
 
 8. Verify archive exists:
    ```bash
-   ls .planning/milestones/v[X.Y]-ROADMAP.md
+   ls .planning/milestones/v[X.Y]/ROADMAP.md
    ```
 
 9. Confirm roadmap archive complete:
 
    ```
-   ✅ v[X.Y] roadmap archived to milestones/v[X.Y]-ROADMAP.md
+   ✅ v[X.Y] roadmap archived to milestones/v[X.Y]/ROADMAP.md
    ✅ ROADMAP.md deleted (fresh one for next milestone)
    ```
 
@@ -487,7 +493,7 @@ Archive requirements and prepare for fresh requirements in next milestone.
    cat .planning/REQUIREMENTS.md
    ```
 
-2. Create archive file: `.planning/milestones/v[X.Y]-REQUIREMENTS.md`
+2. Create archive file: `.planning/milestones/v[X.Y]/REQUIREMENTS.md`
 
 3. Transform requirements for archive:
    - Mark all v1 requirements as `[x]` complete
@@ -531,7 +537,7 @@ Archive requirements and prepare for fresh requirements in next milestone.
 
 6. Confirm:
    ```
-   ✅ Requirements archived to milestones/v[X.Y]-REQUIREMENTS.md
+   ✅ Requirements archived to milestones/v[X.Y]/REQUIREMENTS.md
    ✅ REQUIREMENTS.md deleted (fresh one needed for next milestone)
    ```
 
@@ -544,13 +550,13 @@ Archive requirements and prepare for fresh requirements in next milestone.
 Move the milestone audit file to the archive (if it exists):
 
 ```bash
-# Move audit to milestones folder (if exists)
-[ -f .planning/v[X.Y]-MILESTONE-AUDIT.md ] && mv .planning/v[X.Y]-MILESTONE-AUDIT.md .planning/milestones/
+# Move audit to milestone folder (if exists)
+[ -f .planning/v[X.Y]-MILESTONE-AUDIT.md ] && mv .planning/v[X.Y]-MILESTONE-AUDIT.md .planning/milestones/v[X.Y]/MILESTONE-AUDIT.md
 ```
 
 Confirm:
 ```
-✅ Audit archived to milestones/v[X.Y]-MILESTONE-AUDIT.md
+✅ Audit archived to milestones/v[X.Y]/MILESTONE-AUDIT.md
 ```
 
 (Skip silently if no audit file exists — audit is optional)
@@ -562,18 +568,35 @@ Confirm:
 Archive the milestone context file (if it exists):
 
 ```bash
-[ -f .planning/MILESTONE-CONTEXT.md ] && mv .planning/MILESTONE-CONTEXT.md .planning/milestones/v[X.Y]-CONTEXT.md
+[ -f .planning/MILESTONE-CONTEXT.md ] && mv .planning/MILESTONE-CONTEXT.md .planning/milestones/v[X.Y]/CONTEXT.md
 ```
 
 If archived:
 ```
-✅ Context archived to milestones/v[X.Y]-CONTEXT.md
+✅ Context archived to milestones/v[X.Y]/CONTEXT.md
 ```
 
 (Skip silently if no context file exists)
 
 </step>
 
+<step name="archive_research">
+
+Archive research files to milestone (if research directory exists):
+
+```bash
+[ -d .planning/research ] && mv .planning/research .planning/milestones/v[X.Y]/research
+```
+
+If archived:
+```
+✅ Research archived to milestones/v[X.Y]/research/
+```
+
+(Skip silently if no research directory exists)
+
+</step>
+
 <step name="update_state">
 
 Update STATE.md to reflect milestone completion.
@@ -645,28 +668,27 @@ git push origin v[X.Y]
 Commit milestone completion including archive files and deletions.
 
 ```bash
-# Stage archive files (new)
-git add .planning/milestones/v[X.Y]-ROADMAP.md
-git add .planning/milestones/v[X.Y]-REQUIREMENTS.md
-git add .planning/milestones/v[X.Y]-MILESTONE-AUDIT.md 2>/dev/null || true
-git add .planning/milestones/v[X.Y]-CONTEXT.md 2>/dev/null || true
+# Stage archive directory (covers ROADMAP, REQUIREMENTS, AUDIT, CONTEXT, research)
+git add .planning/milestones/v[X.Y]/
 
 # Stage updated files
 git add .planning/MILESTONES.md
 git add .planning/PROJECT.md
 git add .planning/STATE.md
 
-# Stage deletions (raw artifacts cleaned from phase directories)
+# Stage deletions (raw artifacts cleaned from phase directories, research dir removed)
 git add -u .planning/
 
 # Commit with descriptive message
 git commit -m "$(cat <<'EOF'
 chore: complete v[X.Y] milestone
 
-Archived:
-- milestones/v[X.Y]-ROADMAP.md
-- milestones/v[X.Y]-REQUIREMENTS.md
-- milestones/v[X.Y]-MILESTONE-AUDIT.md (if audit was run)
+Archived to milestones/v[X.Y]/:
+- ROADMAP.md
+- REQUIREMENTS.md
+- MILESTONE-AUDIT.md (if audit was run)
+- CONTEXT.md (if milestone context existed)
+- research/ (if research existed)
 
 Cleaned:
 - Raw phase artifacts (CONTEXT, DESIGN, RESEARCH, SUMMARY, UAT, VERIFICATION, EXECUTION-ORDER)
@@ -675,6 +697,7 @@ Cleaned:
 Deleted (fresh for next milestone):
 - ROADMAP.md
 - REQUIREMENTS.md
+- .planning/research/ (archived to milestone)
 
 Updated:
 - MILESTONES.md (new entry)
@@ -699,9 +722,10 @@ Shipped:
 - [N] phases ([M] plans, [P] tasks)
 - [One sentence of what shipped]
 
-Archived:
-- milestones/v[X.Y]-ROADMAP.md
-- milestones/v[X.Y]-REQUIREMENTS.md
+Archived to milestones/v[X.Y]/:
+- ROADMAP.md
+- REQUIREMENTS.md
+- research/ (if existed)
 
 Summary: .planning/MILESTONES.md
 Tag: v[X.Y]
@@ -777,8 +801,10 @@ Milestone completion is successful when:
 - [ ] All shipped requirements moved to Validated in PROJECT.md
 - [ ] Key Decisions updated with outcomes
 - [ ] ROADMAP.md reorganized with milestone grouping
-- [ ] Roadmap archive created (milestones/v[X.Y]-ROADMAP.md)
-- [ ] Requirements archive created (milestones/v[X.Y]-REQUIREMENTS.md)
+- [ ] Milestone directory created (milestones/v[X.Y]/)
+- [ ] Roadmap archive created (milestones/v[X.Y]/ROADMAP.md)
+- [ ] Requirements archive created (milestones/v[X.Y]/REQUIREMENTS.md)
+- [ ] Research archived to milestone (milestones/v[X.Y]/research/) if .planning/research/ existed
 - [ ] REQUIREMENTS.md deleted (fresh for next milestone)
 - [ ] STATE.md updated with fresh project reference
 - [ ] Git tag created (v[X.Y])

package/mindsystem/workflows/execute-phase.md

@@ -91,7 +91,7 @@ If validation passes, proceed with wave execution.
 <step name="read_execution_order">
 Read EXECUTION-ORDER.md and parse wave structure:
 
-Parse `## Wave N` headers with `- XX-PLAN.md` items under each. Build wave groups:
+Parse `## Wave N` headers with `- {phase}-XX-PLAN.md` items under each. Build wave groups:
 
 ```
 waves = {

package/mindsystem/workflows/plan-phase.md

@@ -74,7 +74,7 @@ ls .planning/codebase/*.md 2>/dev/null
 | database, schema, models | ARCHITECTURE.md, STACK.md |
 | testing, tests | TESTING.md, CONVENTIONS.md |
 | integration, external API | INTEGRATIONS.md, STACK.md |
-| refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
+| refactor, cleanup, quality, tech debt | CONCERNS.md, ARCHITECTURE.md |
 | setup, config | STACK.md, STRUCTURE.md |
 | (default) | STACK.md, ARCHITECTURE.md |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mindsystem-cc",
-  "version": "3.16.1",
+  "version": "3.17.0",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "mindsystem-cc": "bin/install.js"

package/scripts/validate-execution-order.sh

@@ -40,12 +40,14 @@ if [ "$DISK_COUNT" -eq 0 ]; then
 fi
 
 # --- Parse EXECUTION-ORDER.md for plan filenames ---
-ORDER_PLANS=$(grep -oE '[0-9]+-PLAN\.md' "$EXEC_ORDER" | sort -u)
+# Pattern matches phase-prefixed names like 03-01-PLAN.md, 16-01-PLAN.md, 72.1-01-PLAN.md
+ORDER_PLANS=$(grep -oE '[0-9][0-9.]*-[0-9]+-PLAN\.md' "$EXEC_ORDER" | sort -u)
 ORDER_COUNT=$(echo "$ORDER_PLANS" | grep -c . 2>/dev/null || echo 0)
 
 # --- Check 1: Every disk plan is listed in EXECUTION-ORDER.md ---
 ERRORS=""
 while IFS= read -r plan; do
+  [ -z "$plan" ] && continue
   if ! echo "$ORDER_PLANS" | grep -qx "$plan"; then
     ERRORS="${ERRORS}  Missing from EXECUTION-ORDER.md: $plan\n"
   fi
@@ -53,6 +55,7 @@ done <<< "$DISK_PLANS"
 
 # --- Check 2: Every plan in EXECUTION-ORDER.md exists on disk ---
 while IFS= read -r plan; do
+  [ -z "$plan" ] && continue
   if ! echo "$DISK_PLANS" | grep -qx "$plan"; then
     ERRORS="${ERRORS}  Listed in EXECUTION-ORDER.md but file missing: $plan\n"
   fi
@@ -75,7 +78,7 @@ while IFS= read -r line; do
     WAVE_COUNT=$((WAVE_COUNT + 1))
     WAVE_FILES[$CURRENT_WAVE]=""
   elif [ -n "$CURRENT_WAVE" ]; then
-    PLAN_FILE=$(echo "$line" | grep -oE '[0-9]+-PLAN\.md' || true)
+    PLAN_FILE=$(echo "$line" | grep -oE '[0-9][0-9.]*-[0-9]+-PLAN\.md' || true)
     if [ -n "$PLAN_FILE" ] && [ -f "$PHASE_DIR/$PLAN_FILE" ]; then
       # Extract **Files:** lines from plan
       FILE_PATHS=$(grep -E '^\*\*Files:\*\*' "$PHASE_DIR/$PLAN_FILE" | sed 's/\*\*Files:\*\*//g' | tr ',' '\n' | sed 's/`//g; s/^[[:space:]]*//; s/[[:space:]]*$//' | grep -v '^$' || true)