@polymorphism-tech/morph-spec 4.11.1 → 4.13.0

package/framework/commands/morph-apply.md

@@ -57,9 +57,9 @@ Do NOT proceed until all phases are complete and all gates approved.
 Read all prerequisite files in a single parallel call — every file listed here matters for implementation quality:
 
 ```
-Read: .morph/features/$ARGUMENTS/1-design/spec.md              (→ functional requirements, API contracts)
-    + Read: .morph/features/$ARGUMENTS/1-design/contracts.cs    (or contracts.ts / contracts-vsa.cs → C# interfaces)
-    + Read: .morph/features/$ARGUMENTS/1-design/decisions.md    (→ ADRs, architectural choices)
+Read: .morph/features/$ARGUMENTS/2-design/spec.md              (→ functional requirements, API contracts)
+    + Read: .morph/features/$ARGUMENTS/2-design/contracts.cs    (or contracts.ts / contracts-vsa.cs → C# interfaces)
+    + Read: .morph/features/$ARGUMENTS/2-design/decisions.md    (→ ADRs, architectural choices)
     + Read: .morph/features/$ARGUMENTS/3-plan/plan.md           (→ TDD structure, execution strategy)
     + Read: .morph/features/$ARGUMENTS/4-tasks/tasks.md         (→ task breakdown with T### IDs)
     + Read: .morph/config/config.json                           (→ architecture.style for VSA routing)
@@ -96,7 +96,7 @@ This shows which agents are active for implementation and how tasks can be group
 morph-spec dispatch-agents $ARGUMENTS implement
 ```
 
-The JSON output includes `shouldDispatch`, `agents[]`, and `taskGroups` for multi-agent coordination.
+The JSON output includes `shouldDispatch`, `recommended` (agents by group), and `tasks` (task IDs by group) for multi-agent coordination.
 
 ---
 

package/framework/commands/morph-preflight.md

@@ -117,27 +117,7 @@ docker build --check .
 
 ---
 
-### 4. Blazor .NET 10 Assets
-
-**What it checks:**
-- `RequiresAspNetWebAssets` is `true` (if Blazor + .NET 10)
-- Static web assets configured correctly
-
-**How to check:**
-```bash
-grep -r "RequiresAspNetWebAssets" *.csproj
-```
-
-**Fix:**
-```xml
-<PropertyGroup>
-  <RequiresAspNetWebAssets>true</RequiresAspNetWebAssets>
-</PropertyGroup>
-```
-
----
-
-### 5. Bicep Syntax Validation
+### 4. Bicep Syntax Validation
 
 **What it checks:**
 - `.bicep` files without syntax errors
@@ -151,7 +131,7 @@ az bicep build --file infra/main.bicep --stdout > /dev/null
 
 ---
 
-### 6. Key Vault Configuration
+### 5. Key Vault Configuration
 
 **What it checks:**
 - Key Vault URI configured in `appsettings.json` or environment
@@ -175,7 +155,7 @@ if (!builder.Environment.IsDevelopment())
 
 ---
 
-### 7. Connection Strings Security
+### 6. Connection Strings Security
 
 **What it checks:**
 - Connection strings not hardcoded in code
@@ -199,14 +179,13 @@ grep -rE "(Password=|Pwd=|Secret=)" appsettings*.json | grep -v Development
 ✅ Packages: No version conflicts detected
 ✅ Migrations: No pending model changes
 ✅ Dockerfile: Valid multi-stage build
-✅ Blazor Assets: RequiresAspNetWebAssets=true
 ✅ Bicep: Syntax valid
 ❌ Key Vault: URI not configured in appsettings.Production.json
 ⚠️ Connection Strings: Found password in appsettings.Staging.json
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-📋 Summary: 5 passed, 1 failed, 1 warning
+📋 Summary: 4 passed, 1 failed, 1 warning
 
 ❌ BLOCKED: Fix Key Vault configuration before deploy!
 
@@ -262,7 +241,6 @@ Recommended fixes:
 
 - [azure.md](../../standards/azure.md) - Azure Standards
 - [dotnet10-migration.md](../../standards/dotnet10-migration.md) - Breaking changes .NET 10
-- [blazor-efcore.md](../../../../framework/standards/blazor-efcore.md) - EF Core patterns
 
 ---
 

package/framework/commands/morph-proposal.md

@@ -1,5 +1,5 @@
 ---
-description: MORPH Spec Pipeline — creates or resumes feature planning through phases 0-6 with mandatory approval pauses. Use whenever the user wants to plan, spec, or design a new feature, or when they say /morph-proposal. This is the primary entry point for all MORPH-SPEC feature work.
+description: MORPH Spec Pipeline — creates or resumes feature planning through phases 0-8 with mandatory approval pauses. Use whenever the user wants to plan, spec, or design a new feature, or when they say /morph-proposal. This is the primary entry point for all MORPH-SPEC feature work.
 argument-hint: <feature-name>
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
@@ -65,7 +65,7 @@ Fill every section of the template. In particular:
 - **Risks**: table with likelihood, impact, mitigation
 - **Dependencies**: checklist of prerequisites
 - **Estimated Effort**: broken down by phase (in hours)
-- **Questions & Clarifications**: seed 3-6 questions for the clarify phase — these become input for phase 3
+- **Questions & Clarifications**: seed 3-6 questions for the clarify phase — these become input for phase 4
 
 ### Step 5: Register state
 
@@ -83,15 +83,15 @@ morph-spec state mark-output {feature-name} proposal
 ```
 TaskCreate: "Phase 0: Proposal"     → description: "Define feature scope and approach"          → activeForm: "Proposal"
 TaskCreate: "Phase 1: Setup"        → description: "Load context, detect agents, confirm stack"  → activeForm: "Setup"
-TaskCreate: "Phase 2: Design"       → description: "Schema analysis, spec, contracts, decisions" → activeForm: "Design"
-TaskCreate: "Phase 3: Clarify"      → description: "Resolve ambiguities and edge cases"          → activeForm: "Clarify"
-TaskCreate: "Phase 4: Plan"         → description: "Implementation plan with TDD and file paths" → activeForm: "Plan"
-TaskCreate: "Phase 5: Tasks"        → description: "Break spec into T001-T00N with dependencies" → activeForm: "Tasks"
+TaskCreate: "Phase 3: Design"       → description: "Schema analysis, spec, contracts, decisions" → activeForm: "Design"
+TaskCreate: "Phase 4: Clarify"      → description: "Resolve ambiguities and edge cases"          → activeForm: "Clarify"
+TaskCreate: "Phase 5: Plan"         → description: "Implementation plan with TDD and file paths" → activeForm: "Plan"
+TaskCreate: "Phase 6: Tasks"        → description: "Break spec into T001-T00N with dependencies" → activeForm: "Tasks"
 ```
 
 If `ui-designer` is among the activated agents, also create:
 ```
-TaskCreate: "Phase 1.5: UI/UX"     → description: "Design system, mockups, components, flows"   → activeForm: "UI/UX"
+TaskCreate: "Phase 2: UI/UX"       → description: "Design system, mockups, components, flows"   → activeForm: "UI/UX"
 ```
 
 Wire dependencies (addBlockedBy) matching the phase sequence:
@@ -135,13 +135,13 @@ Summary: load project context, confirm stack, list active agents, update state.
 
 ---
 
-## 4. PHASE 1.5: UI/UX (conditional)
+## 4. PHASE 2: UI/UX (conditional)
 
 Check if `ui-designer` is in `activeAgents`:
 - **Yes:** Invoke the `morph-phase-uiux` skill. **MANDATORY PAUSE** after generating UI deliverables.
-- **No:** Skip to PHASE 2.
+- **No:** Skip to PHASE 3.
 
-> **Task lifecycle:** `TaskUpdate` the "Phase 1: Setup" task → `completed`. `TaskUpdate` the "Phase 1.5: UI/UX" task → `in_progress` (if UI/UX), or the "Phase 2: Design" task → `in_progress` (if skipping UI/UX).
+> **Task lifecycle:** `TaskUpdate` the "Phase 1: Setup" task → `completed`. `TaskUpdate` the "Phase 2: UI/UX" task → `in_progress` (if UI/UX), or the "Phase 3: Design" task → `in_progress` (if skipping UI/UX).
 
 After approval:
 ```bash
@@ -151,9 +151,9 @@ morph-spec phase advance {feature-name}
 
 ---
 
-## 5. PHASE 2: DESIGN
+## 5. PHASE 3: DESIGN
 
-> **Task lifecycle:** `TaskUpdate` the completing phase task (UI/UX or Setup) → `completed`. `TaskUpdate` the "Phase 2: Design" task → `in_progress`.
+> **Task lifecycle:** `TaskUpdate` the completing phase task (UI/UX or Setup) → `completed`. `TaskUpdate` the "Phase 3: Design" task → `in_progress`.
 
 Invoke the `morph-phase-design` skill.
 
@@ -171,9 +171,9 @@ morph-spec phase advance {feature-name}
 
 ---
 
-## 6. PHASE 3: CLARIFY (interactive)
+## 6. PHASE 4: CLARIFY (interactive)
 
-> **Task lifecycle:** `TaskUpdate` the "Phase 2: Design" task → `completed`. `TaskUpdate` the "Phase 3: Clarify" task → `in_progress`.
+> **Task lifecycle:** `TaskUpdate` the "Phase 3: Design" task → `completed`. `TaskUpdate` the "Phase 4: Clarify" task → `in_progress`.
 
 Invoke the `morph-phase-clarify` skill.
 
@@ -183,9 +183,9 @@ Summary: identify ambiguities in spec.md, generate 3-7 targeted questions (build
 
 ---
 
-## 7. PHASE 4: PLAN
+## 7. PHASE 5: PLAN
 
-> **Task lifecycle:** `TaskUpdate` the "Phase 3: Clarify" task → `completed`. `TaskUpdate` the "Phase 4: Plan" task → `in_progress`.
+> **Task lifecycle:** `TaskUpdate` the "Phase 4: Clarify" task → `completed`. `TaskUpdate` the "Phase 5: Plan" task → `in_progress`.
 
 Invoke the `morph-phase-plan` skill.
 
@@ -203,9 +203,9 @@ morph-spec phase advance {feature-name}
 
 ---
 
-## 8. PHASE 5: TASKS
+## 8. PHASE 6: TASKS
 
-> **Task lifecycle:** `TaskUpdate` the "Phase 4: Plan" task → `completed`. `TaskUpdate` the "Phase 5: Tasks" task → `in_progress`.
+> **Task lifecycle:** `TaskUpdate` the "Phase 5: Plan" task → `completed`. `TaskUpdate` the "Phase 6: Tasks" task → `in_progress`.
 
 Invoke the `morph-phase-tasks` skill.
 
@@ -225,7 +225,7 @@ morph-spec phase advance {feature-name}
 
 ## 9. Planning Complete
 
-> **Task lifecycle:** `TaskUpdate` the "Phase 5: Tasks" task → `completed`.
+> **Task lifecycle:** `TaskUpdate` the "Phase 6: Tasks" task → `completed`.
 
 After task approval:
 

package/framework/commands/morph-status.md

@@ -58,13 +58,13 @@ The `morph-spec state list` command automatically generates a formatted dashboar
 ║                    MORPH-SPEC PROJECT STATUS                   ║
 ╠════════════════════════════════════════════════════════════════╣
 ║ Project: {PROJECT_NAME}                                        ║
-║ Type: blazor-server                                            ║
+║ Type: dotnet-nextjs                                            ║
 ╠════════════════════════════════════════════════════════════════╣
 ║ FEATURES                                                       ║
 ╠════════════════════════════════════════════════════════════════╣
 ║ 📝 {feature-1}                                                 ║
 ║    Phase: implement        │ Tasks: 5/12                       ║
-║    Agents: blazor-builder ef-modeler hangfire-orchestrator     ║
+║    Agents: ef-modeler hangfire-orchestrator                    ║
 ╠════════════════════════════════════════════════════════════════╣
 ║ 📝 {feature-2}                                                 ║
 ║    Phase: design           │ Tasks: 0/0                        ║

package/framework/commands/morph-troubleshoot.md

@@ -1,12 +1,12 @@
 ---
-description: Find solutions for common .NET/Blazor/Azure development errors with root-cause analysis
+description: Find solutions for common .NET/Next.js development errors with root-cause analysis
 argument-hint: "[error-message]"
 allowed-tools: Read, Bash, Glob, Grep
 ---
 
 # Troubleshoot - Find Solutions for Errors
 
-Find solutions for common .NET/Blazor/Azure development errors and problems.
+Find solutions for common .NET/Next.js development errors and problems.
 
 ## Usage
 
@@ -17,11 +17,10 @@ Find solutions for common .NET/Blazor/Azure development errors and problems.
 ## Examples
 
 ```bash
-/morph-troubleshoot blazor.web.js 404
 /morph-troubleshoot DbContext second operation
-/morph-troubleshoot Azure.Identity NU1605
 /morph-troubleshoot Include returns empty
 /morph-troubleshoot PendingModelChanges
+/morph-troubleshoot next/navigation error
 ```
 
 ## 3-Level Workflow
@@ -60,13 +59,11 @@ site:github.com/dotnet/aspnetcore {error}
 site:github.com/dotnet/efcore {error}
 
 # Stack Overflow
-site:stackoverflow.com [blazor] {error}
 site:stackoverflow.com [entity-framework-core] {error}
-site:stackoverflow.com [azure] {error}
+site:stackoverflow.com [next.js] {error}
 
 # Microsoft Documentation
 site:learn.microsoft.com {error}
-site:learn.microsoft.com/azure {error}
 ```
 
 **WebSearch usage example:**
@@ -80,9 +77,8 @@ If the user asks about a SignalR error:
 
 | Category | Description |
 |-----------|-----------|
-| `blazor` | Blazor Server/WASM, components, lifecycle, rendering |
 | `efcore` | Entity Framework Core, DbContext, migrations, queries |
-| `azure` | Azure services, deploy, identity, Key Vault |
+| `nextjs` | Next.js App Router, pages, components, routing |
 | `auth` | Authentication, authorization, tokens, claims |
 | `deploy` | Deployment, CI/CD, pipelines, containers |
 
@@ -118,13 +114,10 @@ When finding a solution, present in the following format:
 
 | Error | Quick Fix |
 |------|----------------|
-| `blazor.web.js 404` | `<RequiresAspNetWebAssets>true</RequiresAspNetWebAssets>` |
 | `PendingModelChangesWarning` | `dotnet ef migrations add <Name>` before update |
 | `DbContext second operation` | Use `IDbContextFactory` for background tasks |
 | `Include()` empty | Use `HasMany(x => x.Nav)` instead of `HasMany<T>()` |
-| `Azure.Identity NU1605` | Specify explicit version in .csproj |
-| `Key Vault won't load` | Don't condition on environment (IsDevelopment) |
-| `DefaultAzureCredential slow` | Disable unused credentials |
+| `next/navigation error` | Check App Router vs Pages Router usage |
 
 ---
 

package/framework/hooks/README.md

@@ -15,14 +15,11 @@ framework/hooks/
 │   │   ├── protect-spec-files.js    # Block edits to approved spec artifacts
 │   │   └── enforce-phase-writes.js  # Enforce writes to correct phase dir
 │   ├── post-tool-use/
-│   │   ├── dispatch.js              # Dispatch on CLI commands (auto-checkpoint)
-│   │   └── context-refresh.js       # Auto-refresh context on structural git commits
+│   │   └── dispatch.js              # Dispatch on CLI commands (auto-checkpoint)
 │   ├── stop/
 │   │   └── validate-completion.js   # Advisory: warn about incomplete work
 │   ├── pre-compact/
 │   │   └── save-morph-context.js    # Snapshot state before compaction
-│   └── notification/
-│       └── approval-reminder.js     # Remind about pending approvals
 ├── shared/                          # Reusable utilities for all hooks
 │   ├── state-reader.js              # Read-only state.json accessor
 │   ├── phase-utils.js               # Phase constants and path utilities
@@ -51,11 +48,9 @@ framework/hooks/
 | **PreToolUse** (Write\|Edit) | enforce-phase-writes.js | Block | Ensures writes go to current phase directory |
 | **PreToolUse** (Bash) | _(prompt-type inline guard)_ | Block | Blocks `rm -rf .morph/` and direct state edits via Claude's reasoning |
 | **PostToolUse** (Bash) | dispatch.js | Dispatch | Triggers checkpoints on task completion |
-| **PostToolUse** (Bash) | context-refresh.js | Inject context | Detects `git commit` with structural changes → instructs Claude to update `.morph/context/README.md` and `.morph/config/config.json` |
 | **PostToolUseFailure** | handle-tool-failure.js | Logging | Appends structured JSON to .morph/logs/tool-failures.log |
 | **Stop** | validate-completion.js | Advisory | Warns about incomplete tasks/missing outputs/pending gates |
 | **PreCompact** | save-morph-context.js | Snapshot | Saves state to .morph/memory/ before compaction |
-| **Notification** | approval-reminder.js | Advisory | Reminds about pending approval gates |
 
 ## Design Principles
 

package/framework/hooks/claude-code/post-tool-use/agent-complete.js

@@ -0,0 +1,122 @@
+#!/usr/bin/env node
+
+/**
+ * PostToolUse Hook: Agent Completion Tracker
+ *
+ * Event: PostToolUse | Matcher: Agent
+ *
+ * Detects when morph-spec subagents complete (dispatched via the Agent tool)
+ * and injects status notifications:
+ *   - Partial: shows which agents are still pending
+ *   - Complete: instructs to run validate-feature
+ *
+ * Only tracks tier 1-3 agents (not validators: morph-validator-*).
+ *
+ * Fail-open: exits 0 on any error.
+ */
+
+import { readStdin } from '../../shared/stdin-reader.js';
+import { stateExists, getActiveFeature, getFeature, getFeaturePhase } from '../../shared/state-reader.js';
+import { pass, injectContext } from '../../shared/hook-response.js';
+import { logHookActivity } from '../../shared/activity-logger.js';
+import { subagentTypeToAgentId } from '../../shared/dispatch-helpers.js';
+
+try {
+  if (!stateExists()) pass();
+
+  const payload = await readStdin();
+  if (!payload) pass();
+
+  const subagentType = payload?.tool_input?.subagent_type || '';
+  if (!subagentType) pass();
+
+  // Only track morph-* agents (not external subagents)
+  if (!subagentType.startsWith('morph-')) pass();
+
+  // Skip validators (tier 4) — they have their own tracking
+  if (subagentType.startsWith('morph-validator-')) pass();
+
+  const result = buildAgentCompleteContext(subagentType);
+  if (result) {
+    logHookActivity('agent-complete', 'PostToolUse', result.type);
+    injectContext(result.text);
+  }
+
+  pass();
+} catch {
+  // Fail-open
+  process.exit(0);
+}
+
+/**
+ * Build the agent completion notification context.
+ *
+ * @param {string} subagentType - e.g. 'morph-nextjs-expert'
+ * @returns {{ text: string, type: string }|null}
+ */
+function buildAgentCompleteContext(subagentType) {
+  // Get active feature
+  const active = getActiveFeature();
+  if (!active) return null;
+
+  const { name: featureName, feature } = active;
+
+  // Only track during implement phase
+  const phase = getFeaturePhase(featureName);
+  if (phase !== 'implement') return null;
+
+  // Get dispatch log
+  const dispatchLog = feature.dispatchLog;
+  if (!Array.isArray(dispatchLog) || dispatchLog.length === 0) return null;
+
+  // Get the most recent dispatch entry
+  const latestDispatch = dispatchLog[dispatchLog.length - 1];
+  const agents = latestDispatch?.agents;
+  if (!Array.isArray(agents) || agents.length === 0) return null;
+
+  // Find the completing agent in the dispatch
+  const agentId = subagentTypeToAgentId(subagentType);
+  let matchedAgent = agents.find(a => a.subagentType === subagentType);
+  if (!matchedAgent && agentId) {
+    matchedAgent = agents.find(a => a.id === agentId);
+  }
+
+  if (!matchedAgent) return null;
+
+  // Mark this agent as completed (in-memory for evaluation only)
+  // Check which agents are still pending (no completedAt)
+  const pendingAgents = agents.filter(a => {
+    if (a === matchedAgent) return false; // The one just completed
+    return !a.completedAt;
+  });
+
+  const totalAgents = agents.length;
+  const completedCount = totalAgents - pendingAgents.length;
+
+  if (pendingAgents.length === 0) {
+    // All agents complete
+    return {
+      type: 'all_complete',
+      text: [
+        '✅ ALL MORPH-SPEC AGENTS COMPLETE',
+        '════════════════════════════════════════',
+        `All ${totalAgents} dispatched agents have completed their tasks.`,
+        '',
+        'NEXT STEP:',
+        `  morph-spec validate-feature ${featureName} --phase implement`,
+      ].join('\n'),
+    };
+  }
+
+  // Partial completion
+  const remainingList = pendingAgents
+    .map(a => a.title || a.id || 'unknown')
+    .join(', ');
+
+  const agentTitle = matchedAgent.title || matchedAgent.id || subagentType;
+
+  return {
+    type: 'partial_complete',
+    text: `✅ Agent '${agentTitle}' completed (${completedCount}/${totalAgents}). Remaining: ${remainingList}`,
+  };
+}

package/framework/hooks/claude-code/post-tool-use/validator-feedback.js

@@ -24,12 +24,11 @@ import { parseTaskDoneCommand } from '../../shared/dispatch-helpers.js';
 
 // Standard IDs referenced in remediation messages
 const STANDARD_REFS = {
-  'di': 'backend/dotnet/core.md#dependency-injection',
-  'async': 'backend/dotnet/async.md#cancellation-token-pattern',
-  'security': 'core/architecture.md#security-patterns',
-  'packages': 'backend/dotnet/program-cs-checklist.md#nuget-packages',
+  'di': 'dependency injection best practices',
+  'async': 'async/await and CancellationToken patterns',
+  'security': 'security best practices',
+  'packages': 'NuGet package compatibility',
   'design-system': 'frontend/design-system/naming.md#css-class-conventions',
-  'blazor': 'frontend/blazor/pitfalls.md#dbcontext-in-blazor',
 };
 
 try {
@@ -142,6 +141,5 @@ function getRefKey(ruleOrValidator) {
   if (lower.includes('security') || lower.includes('sql') || lower.includes('xss')) return 'security';
   if (lower.includes('package') || lower.includes('nuget')) return 'packages';
   if (lower.includes('design') || lower.includes('css') || lower.includes('naming')) return 'design-system';
-  if (lower.includes('blazor') || lower.includes('dbcontext')) return 'blazor';
   return null;
 }

package/framework/hooks/claude-code/pre-compact/save-morph-context.js

@@ -26,9 +26,9 @@ import { logHookActivity } from '../../shared/activity-logger.js';
 import { buildRichContext, DECISIONS_MAX_CHARS, MAX_PENDING_TASKS } from '../../shared/compact-restore.js';
 
 const PHASE_POSITIONS = {
-  proposal: 1, setup: 1,
+  proposal: 1,
   uiux: 2, design: 2,
-  clarify: 3,
+  plan: 3,
   tasks: 4,
   implement: 5, sync: 5,
 };
@@ -39,7 +39,7 @@ const NEXT_STEP_HINT = {
   design:    (n) => `Approve design gate: morph-spec approve ${n} design`,
   uiux:      (n) => `Approve UI gate: morph-spec approve ${n} uiux`,
   tasks:     (n) => `Approve tasks gate: morph-spec approve ${n} tasks`,
-  implement: (n) => `Continue implementation: morph-spec task next ${n}`,
+  implement: (n) => `Continue implementation: morph-spec task start ${n} <next-task-id>`,
 };
 
 try {
@@ -77,11 +77,16 @@ try {
       const { name: activeName, feature: activeFeature } = active;
       const activePhase = derivePhaseForFeature(activeName);
       let decisionsContent = '';
-      const decisionsPath = join(cwd, `.morph/features/${activeName}/1-design/decisions.md`);
+      const decisionsPath = join(cwd, `.morph/features/${activeName}/2-design/decisions.md`);
       if (existsSync(decisionsPath)) {
         try { decisionsContent = readFileSync(decisionsPath, 'utf-8'); } catch { /* ignore */ }
       }
-      snapshot.richContext = buildRichContext(activeFeature, activePhase, decisionsContent);
+      let specContent = '';
+      const specPath2 = join(cwd, `.morph/features/${activeName}/2-design/spec.md`);
+      if (existsSync(specPath2)) {
+        try { specContent = readFileSync(specPath2, 'utf-8'); } catch { /* ignore */ }
+      }
+      snapshot.richContext = buildRichContext(activeFeature, activePhase, decisionsContent, specContent);
     } catch { /* fail-open: richContext is optional */ }
   }
   // ─────────────────────────────────────────────────────────────────────────
@@ -132,7 +137,7 @@ try {
     lines.push('Next pending tasks:');
     for (const t of pending) lines.push(`  [${t.id}] ${t.title}`);
     if (taskList.filter(t => t.status === 'pending').length > MAX_PENDING_TASKS) {
-      lines.push(`  ... (use morph-spec task next ${name} for full list)`);
+      lines.push(`  ... (see tasks.md for full list)`);
     }
   }
 
@@ -164,7 +169,7 @@ try {
   }
 
   // Key decisions (truncated to stay within context budget)
-  const decisionsPath = join(cwd, `.morph/features/${name}/1-design/decisions.md`);
+  const decisionsPath = join(cwd, `.morph/features/${name}/2-design/decisions.md`);
   if (existsSync(decisionsPath)) {
     try {
       const raw = readFileSync(decisionsPath, 'utf-8');

package/framework/hooks/claude-code/pre-tool-use/enforce-phase-writes.js

@@ -7,8 +7,8 @@
  *
  * Ensures writes to .morph/features/{feature}/ go to the current phase's subfolder:
  *   proposal → only 0-proposal/
- *   design, clarify → only 1-design/
- *   uiux → only 2-ui/
+ *   uiux → only 1-ui/
+ *   design, clarify → only 2-design/
  *   tasks → only 4-tasks/
  *   implement → 5-implement/ + any source code (unrestricted)
  *

package/framework/hooks/claude-code/pre-tool-use/protect-spec-files.js

@@ -6,9 +6,9 @@
  * Event: PreToolUse | Matcher: Write|Edit
  *
  * Blocks Write/Edit to spec artifacts after their approval gate has passed:
- *   - 1-design/spec.md, contracts.cs, etc. → blocked if 'design' gate approved
+ *   - 2-design/spec.md, contracts.cs, etc. → blocked if 'design' gate approved
  *   - 4-tasks/tasks.md → blocked if 'tasks' gate approved
- *   - 2-ui/design-system.md, etc. → blocked if 'uiux' gate approved
+ *   - 1-ui/design-system.md, etc. → blocked if 'uiux' gate approved
  *
  * Fail-open: exits 0 on any error.
  */

package/framework/hooks/claude-code/pre-tool-use/task-tracking-guard.js

@@ -36,23 +36,18 @@ try {
   const phase = feature.phase || derivePhaseForFeature(name);
   if (phase !== 'implement') pass();
 
-  // Check if any task is in_progress
-  // Method 1: tasks.inProgress counter (v3 state format)
+  // Check if any task is in_progress (read directly from taskList)
+  if (feature.taskList?.some(t => t.status === 'in_progress')) pass();
+  // Fallback: legacy counter check
   if (feature.tasks?.inProgress > 0) pass();
 
-  // Method 2: taskList array (v2 state format)
-  if (feature.taskList) {
-    const hasActive = feature.taskList.some(t => t.status === 'in_progress');
-    if (hasActive) pass();
-  }
-
   // No task in_progress — inject advisory warning
   approve(
     `[morph-spec] WARNING: No active task tracking detected during implement phase.\n` +
     `Before writing code, start a task:\n` +
-    `  morph-spec task next ${name}        # see what's next\n` +
     `  morph-spec task start ${name} <id>   # mark it in progress\n` +
-    `Task tracking ensures validators run, checkpoints fire, and progress is recorded.`
+    `Task tracking ensures validators run, checkpoints fire, and progress is recorded.\n` +
+    `If a task is more complex than expected, use: morph-spec task expand ${name} <id> --into "T00Xa: Sub" "T00Xb: Sub"`
   );
 } catch {
   // Fail-open