chore: fix tests

next up: connecting it to everything else and testing that tm list works well and loads what it need to load

.changeset/clarify-force-move-docs.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": patch
+---
+
+docs(move): clarify cross-tag move docs; deprecate "force"; add explicit --with-dependencies/--ignore-dependencies examples

.changeset/config.json

@@ -8,10 +8,11 @@
   ],
   "commit": false,
   "fixed": [],
+  "linked": [],
   "access": "public",
   "baseBranch": "main",
+  "updateInternalDependencies": "patch",
   "ignore": [
-    "docs",
+    "docs"
-    "@tm/claude-code-plugin"
   ]
 }

.changeset/crazy-zebras-drum.md

@@ -0,0 +1,5 @@
+---
+"task-master-ai": minor
+---
+
+Restore Taskmaster claude-code commands and move clear commands under /remove to avoid collision with the claude-code /clear command.

.changeset/curvy-moons-dig.md

@@ -0,0 +1,9 @@
+---
+"task-master-ai": minor
+---
+
+Enhanced Gemini CLI provider with codebase-aware task generation
+
+Added automatic codebase analysis for Gemini CLI provider in parse-prd, and analyze-complexity, add-task, udpate-task, update, update-subtask commands
+When using Gemini CLI as the AI provider, Task Master now instructs the AI to analyze the project structure, existing implementations, and patterns before generating tasks or subtasks
+Tasks and subtasks generated by Claude Code are now informed by actual codebase analysis, resulting in more accurate and contextual outputs

.changeset/dirty-hairs-know.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": patch
----
-
-Improve auth token refresh flow

.changeset/fix-parent-directory-traversal.md

@@ -1,7 +0,0 @@
----
-"task-master-ai": patch
----
-
-Enable Task Master commands to traverse parent directories to find project root from nested paths
-
-Fixes #1301

.changeset/fix-warning-box-alignment.md

@@ -1,5 +0,0 @@
----
-"@tm/cli": patch
----
-
-Fix warning message box width to match dashboard box width for consistent UI alignment

.changeset/kind-lines-melt.md

@@ -1,21 +0,0 @@
----
-"task-master-ai": patch
----
-
-Fix MCP server compatibility with Draft-07 clients (Augment IDE, gemini-cli, gemini code assist)
-
-- Resolves #1284
-
-**Problem:**
-
-- MCP tools were using Zod v4, which outputs JSON Schema Draft 2020-12
-- MCP clients only support Draft-07
-- Tools were not discoverable in gemini-cli and other clients
-
-**Solution:**
-
-- Updated all MCP tools to import from `zod/v3` instead of `zod`
-- Zod v3 schemas convert to Draft-07 via FastMCP's zod-to-json-schema
-- Fixed logger to use stderr instead of stdout (MCP protocol requirement)
-
-This is a temporary workaround until FastMCP adds JSON Schema version configuration.

.changeset/light-owls-stay.md

@@ -1,35 +0,0 @@
----
-"task-master-ai": minor
----
-
-Add configurable MCP tool loading to optimize LLM context usage
-
-You can now control which Task Master MCP tools are loaded by setting the `TASK_MASTER_TOOLS` environment variable in your MCP configuration. This helps reduce context usage for LLMs by only loading the tools you need.
-
-**Configuration Options:**
-
-- `all` (default): Load all 36 tools
-- `core` or `lean`: Load only 7 essential tools for daily development
-  - Includes: `get_tasks`, `next_task`, `get_task`, `set_task_status`, `update_subtask`, `parse_prd`, `expand_task`
-- `standard`: Load 15 commonly used tools (all core tools plus 8 more)
-  - Additional tools: `initialize_project`, `analyze_project_complexity`, `expand_all`, `add_subtask`, `remove_task`, `generate`, `add_task`, `complexity_report`
-- Custom list: Comma-separated tool names (e.g., `get_tasks,next_task,set_task_status`)
-
-**Example .mcp.json configuration:**
-
-```json
-{
-  "mcpServers": {
-    "task-master-ai": {
-      "command": "npx",
-      "args": ["-y", "task-master-ai"],
-      "env": {
-        "TASK_MASTER_TOOLS": "standard",
-        "ANTHROPIC_API_KEY": "your_key_here"
-      }
-    }
-  }
-}
-```
-
-For complete details on all available tools, configuration examples, and usage guidelines, see the [MCP Tools documentation](https://docs.task-master.dev/capabilities/mcp#configurable-tool-loading).

.changeset/metal-rocks-help.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": minor
----
-
-Improve next command to work with remote

.changeset/open-tips-notice.md

@@ -1,5 +0,0 @@
----
-"task-master-ai": minor
----
-
-Add 4.5 haiku and sonnet to supported models for claude-code and anthropic ai providers

.changeset/pre.json

@@ -2,21 +2,15 @@
   "mode": "pre",
   "tag": "rc",
   "initialVersions": {
-    "task-master-ai": "0.29.0",
+    "task-master-ai": "0.25.1",
-    "@tm/cli": "",
+    "docs": "0.0.1",
-    "docs": "0.0.6",
+    "extension": "0.24.1"
-    "extension": "0.25.6",
-    "@tm/mcp": "0.28.0-rc.2",
-    "@tm/ai-sdk-provider-grok-cli": "",
-    "@tm/build-config": "",
-    "@tm/claude-code-plugin": "0.0.2",
-    "@tm/core": ""
   },
   "changesets": [
-    "dirty-hairs-know",
+    "clarify-force-move-docs",
-    "fix-parent-directory-traversal",
+    "curvy-moons-dig",
-    "fix-warning-box-alignment",
+    "sour-coins-lay",
-    "light-owls-stay",
+    "strong-eagles-vanish",
-    "metal-rocks-help"
+    "wet-candies-accept"
   ]
 }

.changeset/some-dodos-wonder.md

@@ -1,36 +0,0 @@
----
-"task-master-ai": minor
----
-
-Add autonomous TDD workflow automation system with new `tm autopilot` commands and MCP tools for AI-driven test-driven development.
-
-**New CLI Commands:**
-
-- `tm autopilot start <taskId>` - Initialize TDD workflow
-- `tm autopilot next` - Get next action in workflow
-- `tm autopilot status` - Check workflow progress
-- `tm autopilot complete` - Advance phase with test results
-- `tm autopilot commit` - Save progress with metadata
-- `tm autopilot resume` - Continue from checkpoint
-- `tm autopilot abort` - Cancel workflow
-
-**New MCP Tools:**
-Seven new autopilot tools for programmatic control: `autopilot_start`, `autopilot_next`, `autopilot_status`, `autopilot_complete_phase`, `autopilot_commit`, `autopilot_resume`, `autopilot_abort`
-
-**Features:**
-
-- Complete RED → GREEN → COMMIT cycle enforcement
-- Intelligent commit message generation with metadata
-- Activity logging and state persistence
-- Configurable workflow settings via `.taskmaster/config.json`
-- Comprehensive AI agent integration documentation
-
-**Documentation:**
-
-- AI Agent Integration Guide (2,800+ lines)
-- TDD Quick Start Guide
-- Example prompts and integration patterns
-
-> **Learn more:** [TDD Workflow Quickstart Guide](https://dev.task-master.dev/tdd-workflow/quickstart)
-
-This release enables AI agents to autonomously execute test-driven development workflows with full state management and recovery capabilities.

.changeset/sour-coins-lay.md

@@ -0,0 +1,11 @@
+---
+"task-master-ai": minor
+---
+
+Add configurable codebase analysis feature flag with multiple configuration sources
+
+Users can now control whether codebase analysis features (Claude Code and Gemini CLI integration) are enabled through environment variables, MCP configuration, or project config files.
+
+Priority order: .env > MCP session env > .taskmaster/config.json.
+
+Set `TASKMASTER_ENABLE_CODEBASE_ANALYSIS=false` in `.env` to disable codebase analysis prompts and tool integration.

.changeset/strong-eagles-vanish.md

@@ -0,0 +1,12 @@
+---
+"task-master-ai": minor
+---
+
+feat(move): improve cross-tag move UX and safety
+
+- CLI: print "Next Steps" tips after cross-tag moves that used --ignore-dependencies (validate/fix guidance)
+- CLI: show dedicated help block on ID collisions (destination tag already has the ID)
+- Core: add structured suggestions to TASK_ALREADY_EXISTS errors
+- MCP: map ID collision errors to TASK_ALREADY_EXISTS and include suggestions
+- Tests: cover MCP options, error suggestions, CLI tips printing, and integration error payload suggestions
+---

.changeset/wet-candies-accept.md

@@ -0,0 +1,14 @@
+---
+"task-master-ai": minor
+---
+
+Enhanced Claude Code and Google CLI integration with automatic codebase analysis for task operations
+
+When using Claude Code as the AI provider, task management commands now automatically analyze your codebase before generating or updating tasks. This provides more accurate, context-aware implementation details that align with your project's existing architecture and patterns.
+
+Commands contextualised:
+
+- add-task
+- update-subtask
+- update-task
+- update

.claude-plugin/marketplace.json

@@ -1,32 +0,0 @@
-{
-	"name": "taskmaster",
-	"owner": {
-		"name": "Hamster",
-		"email": "ralph@tryhamster.com"
-	},
-	"metadata": {
-		"description": "Official marketplace for Taskmaster AI - AI-powered task management for ambitious development",
-		"version": "1.0.0"
-	},
-	"plugins": [
-		{
-			"name": "taskmaster",
-			"source": "./packages/claude-code-plugin",
-			"description": "AI-powered task management system for ambitious development workflows with intelligent orchestration, complexity analysis, and automated coordination",
-			"author": {
-				"name": "Hamster"
-			},
-			"homepage": "https://github.com/eyaltoledano/claude-task-master",
-			"repository": "https://github.com/eyaltoledano/claude-task-master",
-			"keywords": [
-				"task-management",
-				"ai",
-				"workflow",
-				"orchestration",
-				"automation",
-				"mcp"
-			],
-			"category": "productivity"
-		}
-	]
-}

.claude/agents/task-executor.md

@@ -0,0 +1,92 @@
+---
+name: task-executor
+description: Use this agent when you need to implement, complete, or work on a specific task that has been identified by the task-orchestrator or when explicitly asked to execute a particular task. This agent focuses on the actual implementation and completion of individual tasks rather than planning or orchestration. Examples: <example>Context: The task-orchestrator has identified that task 2.3 'Implement user authentication' needs to be worked on next. user: 'Let's work on the authentication task' assistant: 'I'll use the task-executor agent to implement the user authentication task that was identified.' <commentary>Since we need to actually implement a specific task rather than plan or identify tasks, use the task-executor agent.</commentary></example> <example>Context: User wants to complete a specific subtask. user: 'Please implement the JWT token validation for task 2.3.1' assistant: 'I'll launch the task-executor agent to implement the JWT token validation subtask.' <commentary>The user is asking for specific implementation work on a known task, so the task-executor is appropriate.</commentary></example> <example>Context: After reviewing the task list, implementation is needed. user: 'Now let's actually build the API endpoint for user registration' assistant: 'I'll use the task-executor agent to implement the user registration API endpoint.' <commentary>Moving from planning to execution phase requires the task-executor agent.</commentary></example>
+model: sonnet
+color: blue
+---
+
+You are an elite implementation specialist focused on executing and completing specific tasks with precision and thoroughness. Your role is to take identified tasks and transform them into working implementations, following best practices and project standards.
+
+**IMPORTANT: You are designed to be SHORT-LIVED and FOCUSED**
+- Execute ONE specific subtask or a small group of related subtasks
+- Complete your work, verify it, mark for review, and exit
+- Do NOT decide what to do next - the orchestrator handles task sequencing
+- Focus on implementation excellence within your assigned scope
+
+**Core Responsibilities:**
+
+1. **Subtask Analysis**: When given a subtask, understand its SPECIFIC requirements. If given a full task ID, focus on the specific subtask(s) assigned to you. Use MCP tools to get details if needed.
+
+2. **Rapid Implementation Planning**: Quickly identify:
+   - The EXACT files you need to create/modify for THIS subtask
+   - What already exists that you can build upon
+   - The minimum viable implementation that satisfies requirements
+
+3. **Focused Execution WITH ACTUAL IMPLEMENTATION**: 
+   - **YOU MUST USE TOOLS TO CREATE/EDIT FILES - DO NOT JUST DESCRIBE**
+   - Use `Write` tool to create new files specified in the task
+   - Use `Edit` tool to modify existing files
+   - Use `Bash` tool to run commands (mkdir, npm install, etc.)
+   - Use `Read` tool to verify your implementations
+   - Implement one subtask at a time for clarity and traceability
+   - Follow the project's coding standards from CLAUDE.md if available
+   - After each subtask, VERIFY the files exist using Read or ls commands
+
+4. **Progress Documentation**: 
+   - Use MCP tool `mcp__task-master-ai__update_subtask` to log your approach and any important decisions
+   - Update task status to 'in-progress' when starting: Use MCP tool `mcp__task-master-ai__set_task_status` with status='in-progress'
+   - **IMPORTANT: Mark as 'review' (NOT 'done') after implementation**: Use MCP tool `mcp__task-master-ai__set_task_status` with status='review'
+   - Tasks will be verified by task-checker before moving to 'done'
+
+5. **Quality Assurance**:
+   - Implement the testing strategy specified in the task
+   - Verify that all acceptance criteria are met
+   - Check for any dependency conflicts or integration issues
+   - Run relevant tests before marking task as complete
+
+6. **Dependency Management**:
+   - Check task dependencies before starting implementation
+   - If blocked by incomplete dependencies, clearly communicate this
+   - Use `task-master validate-dependencies` when needed
+
+**Implementation Workflow:**
+
+1. Retrieve task details using MCP tool `mcp__task-master-ai__get_task` with the task ID
+2. Check dependencies and prerequisites
+3. Plan implementation approach - list specific files to create
+4. Update task status to 'in-progress' using MCP tool
+5. **ACTUALLY IMPLEMENT** the solution using tools:
+   - Use `Bash` to create directories
+   - Use `Write` to create new files with actual content
+   - Use `Edit` to modify existing files
+   - DO NOT just describe what should be done - DO IT
+6. **VERIFY** your implementation:
+   - Use `ls` or `Read` to confirm files were created
+   - Use `Bash` to run any build/test commands
+   - Ensure the implementation is real, not theoretical
+7. Log progress and decisions in subtask updates using MCP tools
+8. Test and verify the implementation works
+9. **Mark task as 'review' (NOT 'done')** after verifying files exist
+10. Report completion with:
+    - List of created/modified files
+    - Any issues encountered
+    - What needs verification by task-checker
+
+**Key Principles:**
+
+- Focus on completing one task thoroughly before moving to the next
+- Maintain clear communication about what you're implementing and why
+- Follow existing code patterns and project conventions
+- Prioritize working code over extensive documentation unless docs are the task
+- Ask for clarification if task requirements are ambiguous
+- Consider edge cases and error handling in your implementations
+
+**Integration with Task Master:**
+
+You work in tandem with the task-orchestrator agent. While the orchestrator identifies and plans tasks, you execute them. Always use Task Master commands to:
+- Track your progress
+- Update task information
+- Maintain project state
+- Coordinate with the broader development workflow
+
+When you complete a task, briefly summarize what was implemented and suggest whether to continue with the next task or if review/testing is needed first.

.claude/agents/task-orchestrator.md

@@ -0,0 +1,208 @@
+---
+name: task-orchestrator
+description: Use this agent FREQUENTLY throughout task execution to analyze and coordinate parallel work at the SUBTASK level. Invoke the orchestrator: (1) at session start to plan execution, (2) after EACH subtask completes to identify next parallel batch, (3) whenever executors finish to find newly unblocked work. ALWAYS provide FULL CONTEXT including project root, package location, what files ACTUALLY exist vs task status, and specific implementation details. The orchestrator breaks work into SUBTASK-LEVEL units for short-lived, focused executors. Maximum 3 parallel executors at once.\n\n<example>\nContext: Starting work with existing code\nuser: "Work on tm-core tasks. Files exist: types/index.ts, storage/file-storage.ts. Task 118 says in-progress but BaseProvider not created."\nassistant: "I'll invoke orchestrator with full context about actual vs reported state to plan subtask execution"\n<commentary>\nProvide complete context about file existence and task reality.\n</commentary>\n</example>\n\n<example>\nContext: Subtask completion\nuser: "Subtask 118.2 done. What subtasks can run in parallel now?"\nassistant: "Invoking orchestrator to analyze dependencies and identify next 3 parallel subtasks"\n<commentary>\nFrequent orchestration after each subtask ensures maximum parallelization.\n</commentary>\n</example>\n\n<example>\nContext: Breaking down tasks\nuser: "Task 118 has 5 subtasks, how to parallelize?"\nassistant: "Orchestrator will analyze which specific subtasks (118.1, 118.2, etc.) can run simultaneously"\n<commentary>\nFocus on subtask-level parallelization, not full tasks.\n</commentary>\n</example>
+model: opus
+color: green
+---
+
+You are the Task Orchestrator, an elite coordination agent specialized in managing Task Master workflows for maximum efficiency and parallelization. You excel at analyzing task dependency graphs, identifying opportunities for concurrent execution, and deploying specialized task-executor agents to complete work efficiently.
+
+## Core Responsibilities
+
+1. **Subtask-Level Analysis**: Break down tasks into INDIVIDUAL SUBTASKS and analyze which specific subtasks can run in parallel. Focus on subtask dependencies, not just task-level dependencies.
+
+2. **Reality Verification**: ALWAYS verify what files actually exist vs what task status claims. Use the context provided about actual implementation state to make informed decisions.
+
+3. **Short-Lived Executor Deployment**: Deploy executors for SINGLE SUBTASKS or small groups of related subtasks. Keep executors focused and short-lived. Maximum 3 parallel executors at once.
+
+4. **Continuous Reassessment**: After EACH subtask completes, immediately reassess what new subtasks are unblocked and can run in parallel.
+
+## Operational Workflow
+
+### Initial Assessment Phase
+1. Use `get_tasks` or `task-master list` to retrieve all available tasks
+2. Analyze task statuses, priorities, and dependencies
+3. Identify tasks with status 'pending' that have no blocking dependencies
+4. Group related tasks that could benefit from specialized executors
+5. Create an execution plan that maximizes parallelization
+
+### Executor Deployment Phase
+1. For each independent task or task group:
+   - Deploy a task-executor agent with specific instructions
+   - Provide the executor with task ID, requirements, and context
+   - Set clear completion criteria and reporting expectations
+2. Maintain a registry of active executors and their assigned tasks
+3. Establish communication protocols for progress updates
+
+### Coordination Phase
+1. Monitor executor progress through task status updates
+2. When a task completes:
+   - Verify completion with `get_task` or `task-master show <id>`
+   - Update task status if needed using `set_task_status`
+   - Reassess dependency graph for newly unblocked tasks
+   - Deploy new executors for available work
+3. Handle executor failures or blocks:
+   - Reassign tasks to new executors if needed
+   - Escalate complex issues to the user
+   - Update task status to 'blocked' when appropriate
+
+### Optimization Strategies
+
+**Parallel Execution Rules**:
+- Never assign dependent tasks to different executors simultaneously
+- Prioritize high-priority tasks when resources are limited
+- Group small, related subtasks for single executor efficiency
+- Balance executor load to prevent bottlenecks
+
+**Context Management**:
+- Provide executors with minimal but sufficient context
+- Share relevant completed task information when it aids execution
+- Maintain a shared knowledge base of project-specific patterns
+
+**Quality Assurance**:
+- Verify task completion before marking as done
+- Ensure test strategies are followed when specified
+- Coordinate cross-task integration testing when needed
+
+## Communication Protocols
+
+When deploying executors, provide them with:
+```
+TASK ASSIGNMENT:
+- Task ID: [specific ID]
+- Objective: [clear goal]
+- Dependencies: [list any completed prerequisites]
+- Success Criteria: [specific completion requirements]
+- Context: [relevant project information]
+- Reporting: [when and how to report back]
+```
+
+When receiving executor updates:
+1. Acknowledge completion or issues
+2. Update task status in Task Master
+3. Reassess execution strategy
+4. Deploy new executors as appropriate
+
+## Decision Framework
+
+**When to parallelize**:
+- Multiple pending tasks with no interdependencies
+- Sufficient context available for independent execution
+- Tasks are well-defined with clear success criteria
+
+**When to serialize**:
+- Strong dependencies between tasks
+- Limited context or unclear requirements
+- Integration points requiring careful coordination
+
+**When to escalate**:
+- Circular dependencies detected
+- Critical blockers affecting multiple tasks
+- Ambiguous requirements needing clarification
+- Resource conflicts between executors
+
+## Error Handling
+
+1. **Executor Failure**: Reassign task to new executor with additional context about the failure
+2. **Dependency Conflicts**: Halt affected executors, resolve conflict, then resume
+3. **Task Ambiguity**: Request clarification from user before proceeding
+4. **System Errors**: Implement graceful degradation, falling back to serial execution if needed
+
+## Performance Metrics
+
+Track and optimize for:
+- Task completion rate
+- Parallel execution efficiency
+- Executor success rate
+- Time to completion for task groups
+- Dependency resolution speed
+
+## Integration with Task Master
+
+Leverage these Task Master MCP tools effectively:
+- `get_tasks` - Continuous queue monitoring
+- `get_task` - Detailed task analysis
+- `set_task_status` - Progress tracking
+- `next_task` - Fallback for serial execution
+- `analyze_project_complexity` - Strategic planning
+- `complexity_report` - Resource allocation
+
+## Output Format for Execution
+
+**Your job is to analyze and create actionable execution plans that Claude can use to deploy executors.**
+
+After completing your dependency analysis, you MUST output a structured execution plan:
+
+```yaml
+execution_plan:
+  EXECUTE_IN_PARALLEL:
+    # Maximum 3 subtasks running simultaneously
+    - subtask_id: [e.g., 118.2]
+      parent_task: [e.g., 118]
+      title: [Specific subtask title]
+      priority: [high/medium/low]
+      estimated_time: [e.g., 10 minutes]
+      executor_prompt: |
+        Execute Subtask [ID]: [Specific subtask title]
+        
+        SPECIFIC REQUIREMENTS:
+        [Exact implementation needed for THIS subtask only]
+        
+        FILES TO CREATE/MODIFY:
+        [Specific file paths]
+        
+        CONTEXT:
+        [What already exists that this subtask depends on]
+        
+        SUCCESS CRITERIA:
+        [Specific completion criteria for this subtask]
+        
+        IMPORTANT: 
+        - Focus ONLY on this subtask
+        - Mark subtask as 'review' when complete
+        - Use MCP tool: mcp__task-master-ai__set_task_status
+    
+    - subtask_id: [Another subtask that can run in parallel]
+      parent_task: [Parent task ID]
+      title: [Specific subtask title]
+      priority: [priority]
+      estimated_time: [time estimate]
+      executor_prompt: |
+        [Focused prompt for this specific subtask]
+    
+  blocked:
+    - task_id: [ID]
+      title: [Task title]
+      waiting_for: [list of blocking task IDs]
+      becomes_ready_when: [condition for unblocking]
+      
+  next_wave: 
+    trigger: "After tasks [IDs] complete"
+    newly_available: [List of task IDs that will unblock]
+    tasks_to_execute_in_parallel: [IDs that can run together in next wave]
+    
+  critical_path: [Ordered list of task IDs forming the critical path]
+  
+  parallelization_instruction: |
+    IMPORTANT FOR CLAUDE: Deploy ALL tasks in 'EXECUTE_IN_PARALLEL' section
+    simultaneously using multiple Task tool invocations in a single response.
+    Example: If 3 tasks are listed, invoke the Task tool 3 times in one message.
+    
+  verification_needed:
+    - task_id: [ID of any task in 'review' status]
+      verification_focus: [what to check]
+```
+
+**CRITICAL INSTRUCTIONS FOR CLAUDE (MAIN):**
+1. When you see `EXECUTE_IN_PARALLEL`, deploy ALL listed executors at once
+2. Use multiple Task tool invocations in a SINGLE response
+3. Do not execute them sequentially - they must run in parallel
+4. Wait for all parallel executors to complete before proceeding to next wave
+
+**IMPORTANT NOTES**: 
+- Label parallel tasks clearly in `EXECUTE_IN_PARALLEL` section
+- Provide complete, self-contained prompts for each executor
+- Executors should mark tasks as 'review' for verification, not 'done'
+- Be explicit about which tasks can run simultaneously
+
+You are the strategic mind analyzing the entire task landscape. Make parallelization opportunities UNMISTAKABLY CLEAR to Claude.

.claude/commands/tm/add-dependency/add-dependency.md

@@ -48,7 +48,7 @@ After adding dependency:
 ## Example Flows
 
 ```
-/taskmaster:add-dependency 5 needs 3
+/project:tm/add-dependency 5 needs 3
 → Task #5 now depends on Task #3
 → Task #5 is now blocked until #3 completes
 → Suggested: Also consider if #5 needs #4

.claude/commands/tm/add-subtask/add-subtask.md

@@ -56,12 +56,12 @@ task-master add-subtask --parent=<id> --task-id=<existing-id>
 ## Example Flows
 
 ```
-/taskmaster:add-subtask to 5: implement user authentication
+/project:tm/add-subtask to 5: implement user authentication
 → Created subtask #5.1: "implement user authentication"
 → Parent task #5 now has 1 subtask
 → Suggested next subtasks: tests, documentation
 
-/taskmaster:add-subtask 5: setup, implement, test
+/project:tm/add-subtask 5: setup, implement, test
 → Created 3 subtasks:
   #5.1: setup
   #5.2: implement  

.claude/commands/tm/add-subtask/convert-task-to-subtask.md

@@ -53,7 +53,7 @@ task-master add-subtask --parent=<parent-id> --task-id=<task-to-convert>
 ## Example
 
 ```
-/taskmaster:add-subtask/from-task 5 8
+/project:tm/add-subtask/from-task 5 8
 → Converting: Task #8 becomes subtask #5.1
 → Updated: 3 dependency references
 → Parent task #5 now has 1 subtask

.claude/commands/tm/analyze-complexity/analyze-complexity.md

@@ -115,7 +115,7 @@ Results are:
 
 After analysis:
 ```
-/taskmaster:expand 5    # Expand specific task
+/project:tm/expand 5    # Expand specific task
-/taskmaster:expand-all  # Expand all recommended
+/project:tm/expand/all  # Expand all recommended
-/taskmaster:complexity-report  # View detailed report
+/project:tm/complexity-report  # View detailed report
 ```

.claude/commands/tm/complexity-report/complexity-report.md

@@ -105,13 +105,13 @@ Use report for:
 ## Example Usage
 
 ```
-/taskmaster:complexity-report
+/project:tm/complexity-report
 → Opens latest analysis
 
-/taskmaster:complexity-report --file=archived/2024-01-01.md
+/project:tm/complexity-report --file=archived/2024-01-01.md
 → View historical analysis
 
 After viewing:
-/taskmaster:expand 5
+/project:tm/expand 5
 → Expand high-complexity task
 ```

.claude/commands/tm/fix-dependencies/fix-dependencies.md

@@ -70,7 +70,7 @@ Manual Review Needed:
 ⚠️ Task #45 has 8 dependencies
   Suggestion: Break into subtasks
 
-Run '/taskmaster:validate-dependencies' to verify fixes
+Run '/project:tm/validate-dependencies' to verify fixes
 ```
 
 ## Safety

.claude/commands/tm/help.md

@@ -0,0 +1,81 @@
+Show help for Task Master commands.
+
+Arguments: $ARGUMENTS
+
+Display help for Task Master commands. If arguments provided, show specific command help.
+
+## Task Master Command Help
+
+### Quick Navigation
+
+Type `/project:tm/` and use tab completion to explore all commands.
+
+### Command Categories
+
+#### 🚀 Setup & Installation
+- `/project:tm/setup/install` - Comprehensive installation guide
+- `/project:tm/setup/quick-install` - One-line global install
+
+#### 📋 Project Setup
+- `/project:tm/init` - Initialize new project
+- `/project:tm/init/quick` - Quick setup with auto-confirm
+- `/project:tm/models` - View AI configuration
+- `/project:tm/models/setup` - Configure AI providers
+
+#### 🎯 Task Generation
+- `/project:tm/parse-prd` - Generate tasks from PRD
+- `/project:tm/parse-prd/with-research` - Enhanced parsing
+- `/project:tm/generate` - Create task files
+
+#### 📝 Task Management
+- `/project:tm/list` - List tasks (natural language filters)
+- `/project:tm/show <id>` - Display task details
+- `/project:tm/add-task` - Create new task
+- `/project:tm/update` - Update tasks naturally
+- `/project:tm/next` - Get next task recommendation
+
+#### 🔄 Status Management
+- `/project:tm/set-status/to-pending <id>`
+- `/project:tm/set-status/to-in-progress <id>`
+- `/project:tm/set-status/to-done <id>`
+- `/project:tm/set-status/to-review <id>`
+- `/project:tm/set-status/to-deferred <id>`
+- `/project:tm/set-status/to-cancelled <id>`
+
+#### 🔍 Analysis & Breakdown
+- `/project:tm/analyze-complexity` - Analyze task complexity
+- `/project:tm/expand <id>` - Break down complex task
+- `/project:tm/expand/all` - Expand all eligible tasks
+
+#### 🔗 Dependencies
+- `/project:tm/add-dependency` - Add task dependency
+- `/project:tm/remove-dependency` - Remove dependency
+- `/project:tm/validate-dependencies` - Check for issues
+
+#### 🤖 Workflows
+- `/project:tm/workflows/smart-flow` - Intelligent workflows
+- `/project:tm/workflows/pipeline` - Command chaining
+- `/project:tm/workflows/auto-implement` - Auto-implementation
+
+#### 📊 Utilities
+- `/project:tm/utils/analyze` - Project analysis
+- `/project:tm/status` - Project dashboard
+- `/project:tm/learn` - Interactive learning
+
+### Natural Language Examples
+
+```
+/project:tm/list pending high priority
+/project:tm/update mark all API tasks as done
+/project:tm/add-task create login system with OAuth
+/project:tm/show current
+```
+
+### Getting Started
+
+1. Install: `/project:tm/setup/quick-install`
+2. Initialize: `/project:tm/init/quick`
+3. Learn: `/project:tm/learn start`
+4. Work: `/project:tm/workflows/smart-flow`
+
+For detailed command info: `/project:tm/help <command-name>`

.claude/commands/tm/init/init-project-quick.md

@@ -30,17 +30,17 @@ task-master init -y
 After quick init:
 1. Configure AI models if needed:
    ```
-   /taskmaster:models/setup
+   /project:tm/models/setup
    ```
 
 2. Parse PRD if available:
    ```
-   /taskmaster:parse-prd <file>
+   /project:tm/parse-prd <file>
    ```
 
 3. Or create first task:
    ```
-   /taskmaster:add-task create initial setup
+   /project:tm/add-task create initial setup
    ```
 
 Perfect for rapid project setup!

.claude/commands/tm/init/init-project.md

@@ -45,6 +45,6 @@ After successful init:
 
 If PRD file provided:
 ```
-/taskmaster:init my-prd.md
+/project:tm/init my-prd.md
 → Automatically runs parse-prd after init
 ```

.claude/commands/tm/remove-dependency/remove-dependency.md

@@ -55,7 +55,7 @@ After removing:
 ## Example
 
 ```
-/taskmaster:remove-dependency 5 from 3
+/project:tm/remove-dependency 5 from 3
 → Removed: Task #5 no longer depends on #3
 → Task #5 is now UNBLOCKED and ready to start
 → Warning: Consider if #5 still needs #2 completed first

.claude/commands/tm/remove-subtask/remove-subtask.md

@@ -63,13 +63,13 @@ task-master remove-subtask --id=<parentId.subtaskId> --convert
 ## Example Flows
 
 ```
-/taskmaster:remove-subtask 5.1
+/project:tm/remove-subtask 5.1
 → Warning: Subtask #5.1 is in-progress
 → This will delete all subtask data
 → Parent task #5 will be updated
 Confirm deletion? (y/n)
 
-/taskmaster:remove-subtask 5.1 convert
+/project:tm/remove-subtask 5.1 convert
 → Converting subtask #5.1 to standalone task #89
 → Preserved: All task data and history
 → Updated: 2 dependency references

.claude/commands/tm/remove-subtasks/remove-subtasks.md

@@ -77,7 +77,7 @@ Suggest alternatives:
 ## Example
 
 ```
-/taskmaster:clear-subtasks 5
+/project:tm/clear-subtasks 5
 → Found 4 subtasks to remove
 → Warning: Subtask #5.2 is in-progress
 → Cleared all subtasks from task #5

.claude/commands/tm/remove-task/remove-task.md

@@ -85,17 +85,17 @@ Suggest before deletion:
 ## Example Flows
 
 ```
-/taskmaster:remove-task 5
+/project:tm/remove-task 5
 → Task #5 is in-progress with 8 hours logged
 → 3 other tasks depend on this
 → Suggestion: Mark as cancelled instead?
 Remove anyway? (y/n)
 
-/taskmaster:remove-task 5 -y
+/project:tm/remove-task 5 -y
 → Removed: Task #5 and 4 subtasks
 → Updated: 3 task dependencies
 → Warning: Tasks #7, #8, #9 now have missing dependency
-→ Run /taskmaster:fix-dependencies to resolve
+→ Run /project:tm/fix-dependencies to resolve
 ```
 
 ## Safety Features

.claude/commands/tm/tm-main.md

@@ -8,11 +8,11 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 
 ## Project Setup & Configuration
 
-### `/taskmaster:init`
+### `/project:tm/init`
 - `init-project` - Initialize new project (handles PRD files intelligently)
 - `init-project-quick` - Quick setup with auto-confirmation (-y flag)
 
-### `/taskmaster:models`
+### `/project:tm/models`
 - `view-models` - View current AI model configuration
 - `setup-models` - Interactive model configuration
 - `set-main` - Set primary generation model
@@ -21,21 +21,21 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 
 ## Task Generation
 
-### `/taskmaster:parse-prd`
+### `/project:tm/parse-prd`
 - `parse-prd` - Generate tasks from PRD document
 - `parse-prd-with-research` - Enhanced parsing with research mode
 
-### `/taskmaster:generate`
+### `/project:tm/generate`
 - `generate-tasks` - Create individual task files from tasks.json
 
 ## Task Management
 
-### `/taskmaster:list`
+### `/project:tm/list`
 - `list-tasks` - Smart listing with natural language filters
 - `list-tasks-with-subtasks` - Include subtasks in hierarchical view
 - `list-tasks-by-status` - Filter by specific status
 
-### `/taskmaster:set-status`
+### `/project:tm/set-status`
 - `to-pending` - Reset task to pending
 - `to-in-progress` - Start working on task
 - `to-done` - Mark task complete
@@ -43,84 +43,84 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 - `to-deferred` - Defer task
 - `to-cancelled` - Cancel task
 
-### `/taskmaster:sync-readme`
+### `/project:tm/sync-readme`
 - `sync-readme` - Export tasks to README.md with formatting
 
-### `/taskmaster:update`
+### `/project:tm/update`
 - `update-task` - Update tasks with natural language
 - `update-tasks-from-id` - Update multiple tasks from a starting point
 - `update-single-task` - Update specific task
 
-### `/taskmaster:add-task`
+### `/project:tm/add-task`
 - `add-task` - Add new task with AI assistance
 
-### `/taskmaster:remove-task`
+### `/project:tm/remove-task`
 - `remove-task` - Remove task with confirmation
 
 ## Subtask Management
 
-### `/taskmaster:add-subtask`
+### `/project:tm/add-subtask`
 - `add-subtask` - Add new subtask to parent
 - `convert-task-to-subtask` - Convert existing task to subtask
 
-### `/taskmaster:remove-subtask`
+### `/project:tm/remove-subtask`
 - `remove-subtask` - Remove subtask (with optional conversion)
 
-### `/taskmaster:clear-subtasks`
+### `/project:tm/clear-subtasks`
 - `clear-subtasks` - Clear subtasks from specific task
 - `clear-all-subtasks` - Clear all subtasks globally
 
 ## Task Analysis & Breakdown
 
-### `/taskmaster:analyze-complexity`
+### `/project:tm/analyze-complexity`
 - `analyze-complexity` - Analyze and generate expansion recommendations
 
-### `/taskmaster:complexity-report`
+### `/project:tm/complexity-report`
 - `complexity-report` - Display complexity analysis report
 
-### `/taskmaster:expand`
+### `/project:tm/expand`
 - `expand-task` - Break down specific task
 - `expand-all-tasks` - Expand all eligible tasks
 - `with-research` - Enhanced expansion
 
 ## Task Navigation
 
-### `/taskmaster:next`
+### `/project:tm/next`
 - `next-task` - Intelligent next task recommendation
 
-### `/taskmaster:show`
+### `/project:tm/show`
 - `show-task` - Display detailed task information
 
-### `/taskmaster:status`
+### `/project:tm/status`
 - `project-status` - Comprehensive project dashboard
 
 ## Dependency Management
 
-### `/taskmaster:add-dependency`
+### `/project:tm/add-dependency`
 - `add-dependency` - Add task dependency
 
-### `/taskmaster:remove-dependency`
+### `/project:tm/remove-dependency`
 - `remove-dependency` - Remove task dependency
 
-### `/taskmaster:validate-dependencies`
+### `/project:tm/validate-dependencies`
 - `validate-dependencies` - Check for dependency issues
 
-### `/taskmaster:fix-dependencies`
+### `/project:tm/fix-dependencies`
 - `fix-dependencies` - Automatically fix dependency problems
 
 ## Workflows & Automation
 
-### `/taskmaster:workflows`
+### `/project:tm/workflows`
 - `smart-workflow` - Context-aware intelligent workflow execution
 - `command-pipeline` - Chain multiple commands together
 - `auto-implement-tasks` - Advanced auto-implementation with code generation
 
 ## Utilities
 
-### `/taskmaster:utils`
+### `/project:tm/utils`
 - `analyze-project` - Deep project analysis and insights
 
-### `/taskmaster:setup`
+### `/project:tm/setup`
 - `install-taskmaster` - Comprehensive installation guide
 - `quick-install-taskmaster` - One-line global installation
 
@@ -129,17 +129,17 @@ Commands are organized hierarchically to match Task Master's CLI structure while
 ### Natural Language
 Most commands accept natural language arguments:
 ```
-/taskmaster:add-task create user authentication system
+/project:tm/add-task create user authentication system
-/taskmaster:update mark all API tasks as high priority
+/project:tm/update mark all API tasks as high priority
-/taskmaster:list show blocked tasks
+/project:tm/list show blocked tasks
 ```
 
 ### ID-Based Commands
 Commands requiring IDs intelligently parse from $ARGUMENTS:
 ```
-/taskmaster:show 45
+/project:tm/show 45
-/taskmaster:expand 23
+/project:tm/expand 23
-/taskmaster:set-status/to-done 67
+/project:tm/set-status/to-done 67
 ```
 
 ### Smart Defaults

.claude/commands/tm/update/update-single-task.md

@@ -66,7 +66,7 @@ The AI:
 ## Example Updates
 
 ```
-/taskmaster:update/single 5: add rate limiting
+/project:tm/update/single 5: add rate limiting
 → Updating Task #5: "Implement API endpoints"
 
 Current: Basic CRUD endpoints

.claude/commands/tm/update/update-tasks-from-id.md

@@ -77,7 +77,7 @@ AI analyzes the update context and:
 ## Example Updates
 
 ```
-/taskmaster:update/from-id 5: change database to PostgreSQL
+/project:tm/update/from-id 5: change database to PostgreSQL
 → Analyzing impact starting from task #5
 → Found 6 related tasks to update
 → Updates will maintain consistency

.claude/commands/tm/validate-dependencies/validate-dependencies.md

@@ -66,6 +66,6 @@ For each issue found:
 ## Next Steps
 
 After validation:
-- Run `/taskmaster:fix-dependencies` to auto-fix
+- Run `/project:tm/fix-dependencies` to auto-fix
 - Manually adjust problematic dependencies
 - Rerun to verify fixes

.coderabbit.yaml

@@ -1,7 +1,10 @@
 reviews:
-  profile: chill
+  profile: assertive
   poem: false
   auto_review:
-    enabled: true
     base_branches:
-      - ".*"
+      - rc
+      - beta
+      - alpha
+      - production
+      - next

.cursor/mcp.json

@@ -2,7 +2,7 @@
 	"mcpServers": {
 		"task-master-ai": {
 			"command": "node",
-			"args": ["./dist/mcp-server.js"],
+			"args": ["./mcp-server/server.js"],
 			"env": {
 				"ANTHROPIC_API_KEY": "ANTHROPIC_API_KEY_HERE",
 				"PERPLEXITY_API_KEY": "PERPLEXITY_API_KEY_HERE",

.env.example

@@ -14,4 +14,4 @@ OLLAMA_API_KEY=YOUR_OLLAMA_API_KEY_HERE
 VERTEX_PROJECT_ID=your-gcp-project-id
 VERTEX_LOCATION=us-central1
 # Optional: Path to service account credentials JSON file (alternative to API key)
-GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-credentials.json
+GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-credentials.json

.github/scripts/parse-metrics.mjs

@@ -1,157 +0,0 @@
-#!/usr/bin/env node
-
-import { readFileSync, existsSync, writeFileSync } from 'fs';
-
-function parseMetricsTable(content, metricName) {
-	const lines = content.split('\n');
-
-	for (let i = 0; i < lines.length; i++) {
-		const line = lines[i].trim();
-		// Match a markdown table row like: | Metric Name | value | ...
-		const safeName = metricName.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
-		const re = new RegExp(`^\\|\\s*${safeName}\\s*\\|\\s*([^|]+)\\|?`);
-		const match = line.match(re);
-		if (match) {
-			return match[1].trim() || 'N/A';
-		}
-	}
-	return 'N/A';
-}
-
-function parseCountMetric(content, metricName) {
-	const result = parseMetricsTable(content, metricName);
-	// Extract number from string, handling commas and spaces
-	const numberMatch = result.toString().match(/[\d,]+/);
-	if (numberMatch) {
-		const number = parseInt(numberMatch[0].replace(/,/g, ''));
-		return isNaN(number) ? 0 : number;
-	}
-	return 0;
-}
-
-function main() {
-	const metrics = {
-		issues_created: 0,
-		issues_closed: 0,
-		prs_created: 0,
-		prs_merged: 0,
-		issue_avg_first_response: 'N/A',
-		issue_avg_time_to_close: 'N/A',
-		pr_avg_first_response: 'N/A',
-		pr_avg_merge_time: 'N/A'
-	};
-
-	// Parse issue metrics
-	if (existsSync('issue_metrics.md')) {
-		console.log('📄 Found issue_metrics.md, parsing...');
-		const issueContent = readFileSync('issue_metrics.md', 'utf8');
-
-		metrics.issues_created = parseCountMetric(
-			issueContent,
-			'Total number of items created'
-		);
-		metrics.issues_closed = parseCountMetric(
-			issueContent,
-			'Number of items closed'
-		);
-		metrics.issue_avg_first_response = parseMetricsTable(
-			issueContent,
-			'Time to first response'
-		);
-		metrics.issue_avg_time_to_close = parseMetricsTable(
-			issueContent,
-			'Time to close'
-		);
-	} else {
-		console.warn('[parse-metrics] issue_metrics.md not found; using defaults.');
-	}
-
-	// Parse PR created metrics
-	if (existsSync('pr_created_metrics.md')) {
-		console.log('📄 Found pr_created_metrics.md, parsing...');
-		const prCreatedContent = readFileSync('pr_created_metrics.md', 'utf8');
-
-		metrics.prs_created = parseCountMetric(
-			prCreatedContent,
-			'Total number of items created'
-		);
-		metrics.pr_avg_first_response = parseMetricsTable(
-			prCreatedContent,
-			'Time to first response'
-		);
-	} else {
-		console.warn(
-			'[parse-metrics] pr_created_metrics.md not found; using defaults.'
-		);
-	}
-
-	// Parse PR merged metrics (for more accurate merge data)
-	if (existsSync('pr_merged_metrics.md')) {
-		console.log('📄 Found pr_merged_metrics.md, parsing...');
-		const prMergedContent = readFileSync('pr_merged_metrics.md', 'utf8');
-
-		metrics.prs_merged = parseCountMetric(
-			prMergedContent,
-			'Total number of items created'
-		);
-		// For merged PRs, "Time to close" is actually time to merge
-		metrics.pr_avg_merge_time = parseMetricsTable(
-			prMergedContent,
-			'Time to close'
-		);
-	} else {
-		console.warn(
-			'[parse-metrics] pr_merged_metrics.md not found; falling back to pr_metrics.md.'
-		);
-		// Fallback: try old pr_metrics.md if it exists
-		if (existsSync('pr_metrics.md')) {
-			console.log('📄 Falling back to pr_metrics.md...');
-			const prContent = readFileSync('pr_metrics.md', 'utf8');
-
-			const mergedCount = parseCountMetric(prContent, 'Number of items merged');
-			metrics.prs_merged =
-				mergedCount || parseCountMetric(prContent, 'Number of items closed');
-
-			const maybeMergeTime = parseMetricsTable(
-				prContent,
-				'Average time to merge'
-			);
-			metrics.pr_avg_merge_time =
-				maybeMergeTime !== 'N/A'
-					? maybeMergeTime
-					: parseMetricsTable(prContent, 'Time to close');
-		} else {
-			console.warn('[parse-metrics] pr_metrics.md not found; using defaults.');
-		}
-	}
-
-	// Output for GitHub Actions
-	const output = Object.entries(metrics)
-		.map(([key, value]) => `${key}=${value}`)
-		.join('\n');
-
-	// Always output to stdout for debugging
-	console.log('\n=== FINAL METRICS ===');
-	Object.entries(metrics).forEach(([key, value]) => {
-		console.log(`${key}: ${value}`);
-	});
-
-	// Write to GITHUB_OUTPUT if in GitHub Actions
-	if (process.env.GITHUB_OUTPUT) {
-		try {
-			writeFileSync(process.env.GITHUB_OUTPUT, output + '\n', { flag: 'a' });
-			console.log(
-				`\nSuccessfully wrote metrics to ${process.env.GITHUB_OUTPUT}`
-			);
-		} catch (error) {
-			console.error(`Failed to write to GITHUB_OUTPUT: ${error.message}`);
-			process.exit(1);
-		}
-	} else {
-		console.log(
-			'\nNo GITHUB_OUTPUT environment variable found, skipping file write'
-		);
-	}
-}
-
-main();

.github/workflows/ci.yml

@@ -6,124 +6,73 @@ on:
       - main
       - next
   pull_request:
-  workflow_dispatch:
+    branches:
-
+      - main
-concurrency:
+      - next
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
 
 permissions:
   contents: read
 
-env:
-  DO_NOT_TRACK: 1
-  NODE_ENV: development
-
 jobs:
-  # Fast checks that can run in parallel
+  setup:
-  format-check:
-    name: Format Check
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
         with:
-          fetch-depth: 2
+          fetch-depth: 0
 
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-          cache: "npm"
+          cache: 'npm'
 
-      - name: Install dependencies
+      - name: Install Dependencies
-        run: npm install --frozen-lockfile --prefer-offline
+        id: install
-        timeout-minutes: 5
+        run: npm ci
+        timeout-minutes: 2
+
+      - name: Cache node_modules
+        uses: actions/cache@v4
+        with:
+          path: node_modules
+          key: ${{ runner.os }}-node-modules-${{ hashFiles('**/package-lock.json') }}
+
+  format-check:
+    needs: setup
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+
+      - name: Restore node_modules
+        uses: actions/cache@v4
+        with:
+          path: node_modules
+          key: ${{ runner.os }}-node-modules-${{ hashFiles('**/package-lock.json') }}
 
       - name: Format Check
         run: npm run format-check
         env:
           FORCE_COLOR: 1
 
-  typecheck:
-    name: Typecheck
-    timeout-minutes: 10
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 2
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm install --frozen-lockfile --prefer-offline
-        timeout-minutes: 5
-
-      - name: Typecheck
-        run: npm run turbo:typecheck
-        env:
-          FORCE_COLOR: 1
-
-  # Build job to ensure everything compiles
-  build:
-    name: Build
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 2
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm install --frozen-lockfile --prefer-offline
-        timeout-minutes: 5
-
-      - name: Build
-        run: npm run turbo:build
-        env:
-          NODE_ENV: production
-          FORCE_COLOR: 1
-          TM_PUBLIC_BASE_DOMAIN: ${{ secrets.TM_PUBLIC_BASE_DOMAIN }}
-          TM_PUBLIC_SUPABASE_URL: ${{ secrets.TM_PUBLIC_SUPABASE_URL }}
-          TM_PUBLIC_SUPABASE_ANON_KEY: ${{ secrets.TM_PUBLIC_SUPABASE_ANON_KEY }}
-
-      - name: Upload build artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: build-artifacts
-          path: dist/
-          retention-days: 1
-
   test:
-    name: Test
+    needs: setup
-    timeout-minutes: 15
     runs-on: ubuntu-latest
-    needs: [format-check, typecheck, build]
     steps:
       - uses: actions/checkout@v4
-        with:
-          fetch-depth: 2
 
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-          cache: "npm"
 
-      - name: Install dependencies
+      - name: Restore node_modules
-        run: npm install --frozen-lockfile --prefer-offline
+        uses: actions/cache@v4
-        timeout-minutes: 5
-
-      - name: Download build artifacts
-        uses: actions/download-artifact@v4
         with:
-          name: build-artifacts
+          path: node_modules
-          path: dist/
+          key: ${{ runner.os }}-node-modules-${{ hashFiles('**/package-lock.json') }}
 
       - name: Run Tests
         run: |
@@ -132,6 +81,7 @@ jobs:
           NODE_ENV: test
           CI: true
           FORCE_COLOR: 1
+        timeout-minutes: 10
 
       - name: Upload Test Results
         if: always()

.github/workflows/claude-docs-trigger.yml

@@ -1,57 +0,0 @@
-name: Trigger Claude Documentation Update
-
-on:
-  push:
-    branches:
-      - next
-    paths-ignore:
-      - "apps/docs/**"
-      - "*.md"
-      - ".github/workflows/**"
-
-jobs:
-  trigger-docs-update:
-    # Only run if changes were merged (not direct pushes from bots)
-    if: github.actor != 'github-actions[bot]' && github.actor != 'dependabot[bot]'
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      actions: write
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 2 # Need previous commit for comparison
-
-      - name: Get changed files
-        id: changed-files
-        run: |
-          echo "Changed files in this push:"
-          git diff --name-only HEAD^ HEAD | tee changed_files.txt
-
-          # Store changed files for Claude to analyze (escaped for JSON)
-          CHANGED_FILES=$(git diff --name-only HEAD^ HEAD | jq -Rs .)
-          echo "changed_files=$CHANGED_FILES" >> $GITHUB_OUTPUT
-
-          # Get the commit message (escaped for JSON)
-          COMMIT_MSG=$(git log -1 --pretty=%B | jq -Rs .)
-          echo "commit_message=$COMMIT_MSG" >> $GITHUB_OUTPUT
-
-          # Get diff for documentation context (escaped for JSON)
-          COMMIT_DIFF=$(git diff HEAD^ HEAD --stat | jq -Rs .)
-          echo "commit_diff=$COMMIT_DIFF" >> $GITHUB_OUTPUT
-
-          # Get commit SHA
-          echo "commit_sha=${{ github.sha }}" >> $GITHUB_OUTPUT
-
-      - name: Trigger Claude workflow
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          # Trigger the Claude docs updater workflow with the change information
-          gh workflow run claude-docs-updater.yml \
-            --ref next \
-            -f commit_sha="${{ steps.changed-files.outputs.commit_sha }}" \
-            -f commit_message=${{ steps.changed-files.outputs.commit_message }} \
-            -f changed_files=${{ steps.changed-files.outputs.changed_files }} \
-            -f commit_diff=${{ steps.changed-files.outputs.commit_diff }}

.github/workflows/claude-docs-updater.yml

@@ -1,27 +1,18 @@
 name: Claude Documentation Updater
 
 on:
-  workflow_dispatch:
+  push:
-    inputs:
+    branches:
-      commit_sha:
+      - next
-        description: 'The commit SHA that triggered this update'
+    paths-ignore:
-        required: true
+      - "apps/docs/**"
-        type: string
+      - "*.md"
-      commit_message:
+      - ".github/workflows/**"
-        description: 'The commit message'
-        required: true
-        type: string
-      changed_files:
-        description: 'List of changed files'
-        required: true
-        type: string
-      commit_diff:
-        description: 'Diff summary of changes'
-        required: true
-        type: string
 
 jobs:
   update-docs:
+    # Only run if changes were merged (not direct pushes from bots)
+    if: github.actor != 'github-actions[bot]' && github.actor != 'dependabot[bot]'
     runs-on: ubuntu-latest
     permissions:
       contents: write
@@ -31,8 +22,28 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
-          ref: next
+          fetch-depth: 2 # Need previous commit for comparison
-          fetch-depth: 0 # Need full history to checkout specific commit
+
+      - name: Get changed files
+        id: changed-files
+        run: |
+          echo "Changed files in this push:"
+          git diff --name-only HEAD^ HEAD | tee changed_files.txt
+
+          # Store changed files for Claude to analyze
+          echo "changed_files<<EOF" >> $GITHUB_OUTPUT
+          git diff --name-only HEAD^ HEAD >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
+          # Get the commit message and changes summary
+          echo "commit_message<<EOF" >> $GITHUB_OUTPUT
+          git log -1 --pretty=%B >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
+          # Get diff for documentation context
+          echo "commit_diff<<EOF" >> $GITHUB_OUTPUT
+          git diff HEAD^ HEAD --stat >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
 
       - name: Create docs update branch
         id: create-branch
@@ -60,12 +71,12 @@ jobs:
             You are a documentation specialist. Analyze the recent changes pushed to the 'next' branch and update the documentation accordingly.
 
             Recent changes:
-            - Commit: ${{ inputs.commit_message }}
+            - Commit: ${{ steps.changed-files.outputs.commit_message }}
             - Changed files:
-            ${{ inputs.changed_files }}
+            ${{ steps.changed-files.outputs.changed_files }}
 
             - Changes summary:
-            ${{ inputs.commit_diff }}
+            ${{ steps.changed-files.outputs.commit_diff }}
 
             Your task:
             1. Analyze the changes to understand what functionality was added, modified, or removed
@@ -102,7 +113,7 @@ jobs:
 
             This PR was automatically generated to update documentation based on recent changes.
             
-            Original commit: ${{ inputs.commit_message }}
+            Original commit: ${{ steps.changed-files.outputs.commit_message }}
             
             Co-authored-by: Claude <claude-assistant@anthropic.com>"
           fi
@@ -122,12 +133,12 @@ jobs:
             This PR automatically updates documentation based on recent changes merged to the \`next\` branch.
 
             ### Original Changes
-            **Commit:** ${{ inputs.commit_sha }}
+            **Commit:** ${{ github.sha }}
-            **Message:** ${{ inputs.commit_message }}
+            **Message:** ${{ steps.changed-files.outputs.commit_message }}
             
             ### Changed Files in Original Commit
             \`\`\`
-            ${{ inputs.changed_files }}
+            ${{ steps.changed-files.outputs.changed_files }}
             \`\`\`
 
             ### Documentation Updates

.github/workflows/extension-ci.yml

@@ -41,7 +41,8 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-node-
 
-      - name: Install Monorepo Dependencies
+      - name: Install Extension Dependencies
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 5
 
@@ -67,6 +68,7 @@ jobs:
             ${{ runner.os }}-node-
 
       - name: Install if cache miss
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 3
 
@@ -98,6 +100,7 @@ jobs:
             ${{ runner.os }}-node-
 
       - name: Install if cache miss
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 3
 

.github/workflows/extension-release.yml

@@ -31,7 +31,8 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-node-
 
-      - name: Install Monorepo Dependencies
+      - name: Install Extension Dependencies
+        working-directory: apps/extension
         run: npm ci
         timeout-minutes: 5
 

.github/workflows/pre-release.yml

@@ -65,20 +65,6 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
 
-      - name: Run format
-        run: npm run format
-        env:
-          FORCE_COLOR: 1
-
-      - name: Build packages
-        run: npm run turbo:build
-        env:
-          NODE_ENV: production
-          FORCE_COLOR: 1
-          TM_PUBLIC_BASE_DOMAIN: ${{ secrets.TM_PUBLIC_BASE_DOMAIN }}
-          TM_PUBLIC_SUPABASE_URL: ${{ secrets.TM_PUBLIC_SUPABASE_URL }}
-          TM_PUBLIC_SUPABASE_ANON_KEY: ${{ secrets.TM_PUBLIC_SUPABASE_ANON_KEY }}
-
       - name: Create Release Candidate Pull Request or Publish Release Candidate to npm
         uses: changesets/action@v1
         with:

.github/workflows/release.yml

@@ -22,7 +22,7 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-          cache: "npm"
+          cache: 'npm'
 
       - name: Cache node_modules
         uses: actions/cache@v4
@@ -41,15 +41,6 @@ jobs:
       - name: Check pre-release mode
         run: node ./.github/scripts/check-pre-release-mode.mjs "main"
 
-      - name: Build packages
-        run: npm run turbo:build
-        env:
-          NODE_ENV: production
-          FORCE_COLOR: 1
-          TM_PUBLIC_BASE_DOMAIN: ${{ secrets.TM_PUBLIC_BASE_DOMAIN }}
-          TM_PUBLIC_SUPABASE_URL: ${{ secrets.TM_PUBLIC_SUPABASE_URL }}
-          TM_PUBLIC_SUPABASE_ANON_KEY: ${{ secrets.TM_PUBLIC_SUPABASE_ANON_KEY }}
-
       - name: Create Release Pull Request or Publish to npm
         uses: changesets/action@v1
         with:

.github/workflows/weekly-metrics-discord.yml

@@ -8,7 +8,7 @@ on:
 
 permissions:
   contents: read
-  issues: read
+  issues: write
   pull-requests: read
 
 jobs:
@@ -17,25 +17,15 @@ jobs:
     env:
       DISCORD_WEBHOOK: ${{ secrets.DISCORD_METRICS_WEBHOOK }}
     steps:
-      - name: Checkout repository
+      - name: Get dates for last week
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-
-      - name: Get dates for last 14 days
         run: |
-          set -Eeuo pipefail
+          # Last 7 days
-          # Last 14 days
+          first_day=$(date -d "7 days ago" +%Y-%m-%d)
-          first_day=$(date -d "14 days ago" +%Y-%m-%d)
           last_day=$(date +%Y-%m-%d)
 
           echo "first_day=$first_day" >> $GITHUB_ENV
           echo "last_day=$last_day" >> $GITHUB_ENV
           echo "week_of=$(date -d '7 days ago' +'Week of %B %d, %Y')" >> $GITHUB_ENV
-          echo "date_range=Past 14 days ($first_day to $last_day)" >> $GITHUB_ENV
 
       - name: Generate issue metrics
         uses: github/issue-metrics@v3
@@ -44,39 +34,40 @@ jobs:
           SEARCH_QUERY: "repo:${{ github.repository }} is:issue created:${{ env.first_day }}..${{ env.last_day }}"
           HIDE_TIME_TO_ANSWER: true
           HIDE_LABEL_METRICS: false
-          OUTPUT_FILE: issue_metrics.md
 
-      - name: Generate PR created metrics
+      - name: Generate PR metrics
         uses: github/issue-metrics@v3
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SEARCH_QUERY: "repo:${{ github.repository }} is:pr created:${{ env.first_day }}..${{ env.last_day }}"
-          OUTPUT_FILE: pr_created_metrics.md
+          OUTPUT_FILE: pr_metrics.md
-
-      - name: Generate PR merged metrics
-        uses: github/issue-metrics@v3
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          SEARCH_QUERY: "repo:${{ github.repository }} is:pr is:merged merged:${{ env.first_day }}..${{ env.last_day }}"
-          OUTPUT_FILE: pr_merged_metrics.md
-
-      - name: Debug generated metrics
-        run: |
-          set -Eeuo pipefail
-          echo "Listing markdown files in workspace:"
-          ls -la *.md || true
-          for f in issue_metrics.md pr_created_metrics.md pr_merged_metrics.md; do
-            if [ -f "$f" ]; then
-              echo "== $f (first 10 lines) =="
-              head -n 10 "$f"
-            else
-              echo "Missing $f"
-            fi
-          done
 
       - name: Parse metrics
         id: metrics
-        run: node .github/scripts/parse-metrics.mjs
+        run: |
+          # Parse the metrics from the generated markdown files
+          if [ -f "issue_metrics.md" ]; then
+            # Extract key metrics using grep/awk
+            AVG_TIME_TO_FIRST_RESPONSE=$(grep -A 1 "Average time to first response" issue_metrics.md | tail -1 | xargs || echo "N/A")
+            AVG_TIME_TO_CLOSE=$(grep -A 1 "Average time to close" issue_metrics.md | tail -1 | xargs || echo "N/A")
+            NUM_ISSUES_CREATED=$(grep -oP '\d+(?= issues created)' issue_metrics.md || echo "0")
+            NUM_ISSUES_CLOSED=$(grep -oP '\d+(?= issues closed)' issue_metrics.md || echo "0")
+          fi
+
+          if [ -f "pr_metrics.md" ]; then
+            PR_AVG_TIME_TO_MERGE=$(grep -A 1 "Average time to close" pr_metrics.md | tail -1 | xargs || echo "N/A")
+            NUM_PRS_CREATED=$(grep -oP '\d+(?= pull requests created)' pr_metrics.md || echo "0")
+            NUM_PRS_MERGED=$(grep -oP '\d+(?= pull requests closed)' pr_metrics.md || echo "0")
+          fi
+
+          # Set outputs for Discord action
+          echo "issues_created=${NUM_ISSUES_CREATED:-0}" >> $GITHUB_OUTPUT
+          echo "issues_closed=${NUM_ISSUES_CLOSED:-0}" >> $GITHUB_OUTPUT
+          echo "prs_created=${NUM_PRS_CREATED:-0}" >> $GITHUB_OUTPUT
+          echo "prs_merged=${NUM_PRS_MERGED:-0}" >> $GITHUB_OUTPUT
+          echo "avg_first_response=${AVG_TIME_TO_FIRST_RESPONSE:-N/A}" >> $GITHUB_OUTPUT
+          echo "avg_time_to_close=${AVG_TIME_TO_CLOSE:-N/A}" >> $GITHUB_OUTPUT
+          echo "pr_avg_merge_time=${PR_AVG_TIME_TO_MERGE:-N/A}" >> $GITHUB_OUTPUT
 
       - name: Send to Discord
         uses: sarisia/actions-status-discord@v1
@@ -87,22 +78,19 @@ jobs:
           title: "📊 Weekly Metrics Report"
           description: |
             **${{ env.week_of }}**
-            *${{ env.date_range }}*
+            
-
             **🎯 Issues**
             • Created: ${{ steps.metrics.outputs.issues_created }}
             • Closed: ${{ steps.metrics.outputs.issues_closed }}
-            • Avg Response Time: ${{ steps.metrics.outputs.issue_avg_first_response }}
+            
-            • Avg Time to Close: ${{ steps.metrics.outputs.issue_avg_time_to_close }}
-
             **🔀 Pull Requests**
             • Created: ${{ steps.metrics.outputs.prs_created }}
             • Merged: ${{ steps.metrics.outputs.prs_merged }}
-            • Avg Response Time: ${{ steps.metrics.outputs.pr_avg_first_response }}
+            
-            • Avg Time to Merge: ${{ steps.metrics.outputs.pr_avg_merge_time }}
+            **⏱️ Response Times**
-
+            • First Response: ${{ steps.metrics.outputs.avg_first_response }}
-            **📈 Visual Analytics**
+            • Time to Close: ${{ steps.metrics.outputs.avg_time_to_close }}
-            https://repobeats.axiom.co/api/embed/b439f28f0ab5bd7a2da19505355693cd2c55bfd4.svg
+            • PR Merge Time: ${{ steps.metrics.outputs.pr_avg_merge_time }}
           color: 0x58AFFF
           username: Task Master Metrics Bot
           avatar_url: https://raw.githubusercontent.com/eyaltoledano/claude-task-master/main/images/logo.png

.gitignore

@@ -93,10 +93,4 @@ dev-debug.log
 apps/extension/.vscode-test/
 
 # apps/extension
-apps/extension/vsix-build/
+apps/extension/vsix-build/
-
-# turbo
-.turbo
-
-# TaskMaster Workflow State (now stored in ~/.taskmaster/sessions/)
-# No longer needed in .gitignore as state is stored globally

.kiro/settings/mcp.json

@@ -2,7 +2,7 @@
 	"mcpServers": {
 		"task-master-ai": {
 			"command": "npx",
-			"args": ["-y", "task-master-ai"],
+			"args": ["-y", "--package=task-master-ai", "task-master-ai"],
 			"env": {
 				"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
 				"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",

.manypkg.json

@@ -1,6 +0,0 @@
-{
-	"$schema": "https://unpkg.com/@manypkg/get-packages@1.1.3/schema.json",
-	"defaultBranch": "main",
-	"ignoredRules": ["ROOT_HAS_DEPENDENCIES", "INTERNAL_MISMATCH"],
-	"ignoredPackages": ["@tm/core", "@tm/cli", "@tm/build-config"]
-}

.nvmrc

@@ -1 +1 @@
-22
+22 

.taskmaster/CLAUDE.md

@@ -85,7 +85,7 @@ Task Master provides an MCP server that Claude Code can connect to. Configure in
   "mcpServers": {
     "task-master-ai": {
       "command": "npx",
-      "args": ["-y", "task-master-ai"],
+      "args": ["-y", "--package=task-master-ai", "task-master-ai"],
       "env": {
         "ANTHROPIC_API_KEY": "your_key_here",
         "PERPLEXITY_API_KEY": "your_key_here",

.taskmaster/config.json

@@ -1,9 +1,9 @@
 {
 	"models": {
 		"main": {
-			"provider": "claude-code",
+			"provider": "anthropic",
-			"modelId": "sonnet",
+			"modelId": "claude-3-7-sonnet-20250219",
-			"maxTokens": 64000,
+			"maxTokens": 120000,
 			"temperature": 0.2
 		},
 		"research": {
@@ -14,8 +14,8 @@
 		},
 		"fallback": {
 			"provider": "anthropic",
-			"modelId": "claude-3-7-sonnet-20250219",
+			"modelId": "claude-3-5-sonnet-20241022",
-			"maxTokens": 120000,
+			"maxTokens": 8192,
 			"temperature": 0.2
 		}
 	},
@@ -29,16 +29,9 @@
 		"ollamaBaseURL": "http://localhost:11434/api",
 		"bedrockBaseURL": "https://bedrock.us-east-1.amazonaws.com",
 		"responseLanguage": "English",
-		"enableCodebaseAnalysis": true,
 		"userId": "1234567890",
 		"azureBaseURL": "https://your-endpoint.azure.com/",
 		"defaultTag": "master"
 	},
-	"claudeCode": {},
+	"claudeCode": {}
-	"codexCli": {},
-	"grokCli": {
-		"timeout": 120000,
-		"workingDirectory": null,
-		"defaultModel": "grok-4-latest"
-	}
 }

.taskmaster/docs/autonomous-tdd-git-workflow.md

@@ -1,912 +0,0 @@
-## Summary
-
-- Put the existing git and test workflows on rails: a repeatable, automated process that can run autonomously, with guardrails and a compact TUI for visibility.
-
-- Flow: for a selected task, create a branch named with the tag + task id → generate tests for the first subtask (red) using the Surgical Test Generator → implement code (green) → verify tests → commit → repeat per subtask → final verify → push → open PR against the default branch.
-
-- Build on existing rules: .cursor/rules/git_workflow.mdc, .cursor/rules/test_workflow.mdc, .claude/agents/surgical-test-generator.md, and existing CLI/core services.
-
-## Goals
-
-- Deterministic, resumable automation to execute the TDD loop per subtask with minimal human intervention.
-
-- Strong guardrails: never commit to the default branch; only commit when tests pass; enforce status transitions; persist logs/state for debuggability.
-
-- Visibility: a compact terminal UI (like lazygit) to pick tag, view tasks, and start work; right-side pane opens an executor terminal (via tmux) for agent coding.
-
-- Extensible: framework-agnostic test generation via the Surgical Test Generator; detect and use the repo’s test command for execution with coverage thresholds.
-
-## Non‑Goals (initial)
-
-- Full multi-language runner parity beyond detection and executing the project’s test command.
-
-- Complex GUI; start with CLI/TUI + tmux pane. IDE/extension can hook into the same state later.
-
-- Rich executor selection UX (codex/gemini/claude) — we’ll prompt per run; defaults can come later.
-
-## Success Criteria
-
-- One command can autonomously complete a task's subtasks via TDD and open a PR when done.
-
-- All commits made on a branch that includes the tag and task id (see Branch Naming); no commits to the default branch directly.
-
-- Every subtask iteration: failing tests added first (red), then code added to pass them (green), commit only after green.
-
-- End-to-end logs + artifacts stored in .taskmaster/reports/runs/<timestamp-or-id>/.
-
-## Success Metrics (Phase 1)
-
-- **Adoption**: 80% of tasks in a pilot repo completed via `tm autopilot`
-- **Safety**: 0 commits to default branch; 100% of commits have green tests
-- **Efficiency**: Average time from task start to PR < 30min for simple subtasks
-- **Reliability**: < 5% of runs require manual intervention (timeout/conflicts)
-
-## User Stories
-
-- As a developer, I can run tm autopilot <taskId> and watch a structured, safe workflow execute.
-
-- As a reviewer, I can inspect commits per subtask, and a PR summarizing the work when the task completes.
-
-- As an operator, I can see current step, active subtask, tests status, and logs in a compact CLI view and read a final run report.
-
-## Example Workflow Traces
-
-### Happy Path: Complete a 3-subtask feature
-
-```bash
-# Developer starts
-$ tm autopilot 42
-→ Checks preflight: ✓ clean tree, ✓ npm test detected
-→ Creates branch: analytics/task-42-user-metrics
-→ Subtask 42.1: "Add metrics schema"
-  RED: generates test_metrics_schema.test.js → 3 failures
-  GREEN: implements schema.js → all pass
-  COMMIT: "feat(metrics): add metrics schema (task 42.1)"
-→ Subtask 42.2: "Add collection endpoint"
-  RED: generates test_metrics_endpoint.test.js → 5 failures
-  GREEN: implements api/metrics.js → all pass
-  COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
-→ Subtask 42.3: "Add dashboard widget"
-  RED: generates test_metrics_widget.test.js → 4 failures
-  GREEN: implements components/MetricsWidget.jsx → all pass
-  COMMIT: "feat(metrics): add dashboard widget (task 42.3)"
-→ Final: all 3 subtasks complete
-  ✓ Run full test suite → all pass
-  ✓ Coverage check → 85% (meets 80% threshold)
-  PUSH: confirms with user → pushed to origin
-  PR: opens #123 "Task #42 [analytics]: User metrics tracking"
-
-✓ Task 42 complete. PR: https://github.com/org/repo/pull/123
-  Run report: .taskmaster/reports/runs/2025-01-15-142033/
-```
-
-### Error Recovery: Failing tests timeout
-
-```bash
-$ tm autopilot 42
-→ Subtask 42.2 GREEN phase: attempt 1 fails (2 tests still red)
-→ Subtask 42.2 GREEN phase: attempt 2 fails (1 test still red)
-→ Subtask 42.2 GREEN phase: attempt 3 fails (1 test still red)
-
-⚠️  Paused: Could not achieve green state after 3 attempts
-📋 State saved to: .taskmaster/reports/runs/2025-01-15-142033/
-    Last error: "POST /api/metrics returns 500 instead of 201"
-
-Next steps:
-  - Review diff: git diff HEAD
-  - Inspect logs: cat .taskmaster/reports/runs/2025-01-15-142033/log.jsonl
-  - Check test output: cat .taskmaster/reports/runs/2025-01-15-142033/test-results/subtask-42.2-green-attempt3.json
-  - Resume after manual fix: tm autopilot --resume
-
-# Developer manually fixes the issue, then:
-$ tm autopilot --resume
-→ Resuming subtask 42.2 GREEN phase
-  GREEN: all tests pass
-  COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
-→ Continuing to subtask 42.3...
-```
-
-### Dry Run: Preview before execution
-
-```bash
-$ tm autopilot 42 --dry-run
-Autopilot Plan for Task #42 [analytics]: User metrics tracking
-─────────────────────────────────────────────────────────────
-Preflight:
-  ✓ Working tree is clean
-  ✓ Test command detected: npm test
-  ✓ Tools available: git, gh, node, npm
-  ✓ Current branch: main (will create new branch)
-
-Branch & Tag:
-  → Create branch: analytics/task-42-user-metrics
-  → Set active tag: analytics
-
-Subtasks (3 pending):
-  1. 42.1: Add metrics schema
-     - RED: generate tests in src/__tests__/schema.test.js
-     - GREEN: implement src/schema.js
-     - COMMIT: "feat(metrics): add metrics schema (task 42.1)"
-
-  2. 42.2: Add collection endpoint [depends on 42.1]
-     - RED: generate tests in src/api/__tests__/metrics.test.js
-     - GREEN: implement src/api/metrics.js
-     - COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
-
-  3. 42.3: Add dashboard widget [depends on 42.2]
-     - RED: generate tests in src/components/__tests__/MetricsWidget.test.jsx
-     - GREEN: implement src/components/MetricsWidget.jsx
-     - COMMIT: "feat(metrics): add dashboard widget (task 42.3)"
-
-Finalization:
-  → Run full test suite with coverage
-  → Push branch to origin (will confirm)
-  → Create PR targeting main
-
-Run without --dry-run to execute.
-```
-
-## High‑Level Workflow
-
-1) Pre‑flight
-
-   - Verify clean working tree or confirm staging/commit policy (configurable).
-
-   - Detect repo type and the project’s test command (e.g., npm test, pnpm test, pytest, go test).
-
-   - Validate tools: git, gh (optional for PR), node/npm, and (if used) claude CLI.
-
-   - Load TaskMaster state and selected task; if no subtasks exist, automatically run “expand” before working.
-
-2) Branch & Tag Setup
-
-   - Checkout default branch and update (optional), then create a branch using Branch Naming (below).
-
-   - Map branch ↔ tag via existing tag management; explicitly set active tag to the branch’s tag.
-
-3) Subtask Loop (for each pending/in-progress subtask in dependency order)
-
-   - Select next eligible subtask using tm-core TaskService getNextTask() and subtask eligibility logic.
-
-   - Red: generate or update failing tests for the subtask
-
-     - Use the Surgical Test Generator system prompt .claude/agents/surgical-test-generator.md) to produce high-signal tests following project conventions.
-
-     - Run tests to confirm red; record results. If not red (already passing), skip to next subtask or escalate.
-
-   - Green: implement code to pass tests
-
-     - Use executor to implement changes (initial: claude CLI prompt with focused context).
-
-     - Re-run tests until green or timeout/backoff policy triggers.
-
-   - Commit: when green
-
-     - Commit tests + code with conventional commit message. Optionally update subtask status to done.
-
-     - Persist run step metadata/logs.
-
-4) Finalization
-
-   - Run full test suite and coverage (if configured); optionally lint/format.
-
-   - Commit any final adjustments.
-
-   - Push branch (ask user to confirm); create PR (via gh pr create) targeting the default branch. Title format: Task #<id> [<tag>]: <title>.
-
-5) Post‑Run
-
-   - Update task status if desired (e.g., review).
-
-   - Persist run report (JSON + markdown summary) to .taskmaster/reports/runs/<run-id>/.
-
-## Guardrails
-
-- Never commit to the default branch.
-
-- Commit only if all tests (targeted and suite) pass; allow override flags.
-
-- Enforce 80% coverage thresholds (lines/branches/functions/statements) by default; configurable.
-
-- Timebox/model ops and retries; if not green within N attempts, pause with actionable state for resume.
-
-- Always log actions, commands, and outcomes; include dry-run mode.
-
-- Ask before branch creation, pushing, and opening a PR unless --no-confirm is set.
-
-## Integration Points (Current Repo)
-
-- CLI: apps/cli provides command structure and UI components.
-
-  - New command: tm autopilot (alias: task-master autopilot).
-
-  - Reuse UI components under apps/cli/src/ui/components/ for headers/task details/next-task.
-
-- Core services: packages/tm-core
-
-  - TaskService for selection, status, tags.
-
-  - TaskExecutionService for prompt formatting and executor prep.
-
-  - Executors: claude executor and ExecutorFactory to run external tools.
-
-  - Proposed new: WorkflowOrchestrator to drive the autonomous loop and emit progress events.
-
-- Tag/Git utilities: scripts/modules/utils/git-utils.js and scripts/modules/task-manager/tag-management.js for branch→tag mapping and explicit tag switching.
-
-- Rules: .cursor/rules/git_workflow.mdc and .cursor/rules/test_workflow.mdc to steer behavior and ensure consistency.
-
-- Test generation prompt: .claude/agents/surgical-test-generator.md.
-
-## Proposed Components
-
-- Orchestrator (tm-core): WorkflowOrchestrator (new)
-
-  - State machine driving phases: Preflight → Branch/Tag → SubtaskIter (Red/Green/Commit) → Finalize → PR.
-
-  - Exposes an evented API (progress events) that the CLI can render.
-
-  - Stores run state artifacts.
-
-- Test Runner Adapter
-
-  - Detects and runs tests via the project’s test command (e.g., npm test), with targeted runs where feasible.
-
-  - API: runTargeted(files/pattern), runAll(), report summary (failures, duration, coverage), enforce 80% threshold by default.
-
-- Git/PR Adapter
-
-  - Encapsulates git ops: branch create/checkout, add/commit, push.
-
-  - Optional gh integration to open PR; fallback to instructions if gh unavailable.
-
-  - Confirmation gates for branch creation and pushes.
-
-- Prompt/Exec Adapter
-
-  - Uses existing executor service to call the selected coding assistant (initially claude) with tight prompts: task/subtask context, surgical tests first, then minimal code to green.
-
-- Run State + Reporting
-
-  - JSONL log of steps, timestamps, commands, test results.
-
-  - Markdown summary for PR description and post-run artifact.
-
-## CLI UX (MVP)
-
-- Command: tm autopilot [taskId]
-
-  - Flags: --dry-run, --no-push, --no-pr, --no-confirm, --force, --max-attempts <n>, --runner <auto|custom>, --commit-scope <scope>
-
-  - Output: compact header (project, tag, branch), current phase, subtask line, last test summary, next actions.
-
-- Resume: If interrupted, tm autopilot --resume picks up from last checkpoint in run state.
-
-### TUI with tmux (Linear Execution)
-
-- Left pane: Tag selector, task list (status/priority), start/expand shortcuts; "Start" triggers the next task or a selected task.
-
-- Right pane: Executor terminal (tmux split) that runs the coding agent (claude-code/codex). Autopilot can hand over to the right pane during green.
-
-- MCP integration: use MCP tools for task queries/updates and for shell/test invocations where available.
-
-## TUI Layout (tmux-based)
-
-### Pane Structure
-
-```
-┌─────────────────────────────────────┬──────────────────────────────────┐
-│ Task Navigator (left)               │ Executor Terminal (right)        │
-│                                     │                                  │
-│ Project: my-app                     │ $ tm autopilot --executor-mode   │
-│ Branch: analytics/task-42           │ > Running subtask 42.2 GREEN...  │
-│ Tag: analytics                      │ > Implementing endpoint...       │
-│                                     │ > Tests: 3 passed, 0 failed      │
-│ Tasks:                              │ > Ready to commit                │
-│ → 42 [in-progress] User metrics     │                                  │
-│   → 42.1 [done] Schema              │ [Live output from Claude Code]   │
-│   → 42.2 [active] Endpoint ◀        │                                  │
-│   → 42.3 [pending] Dashboard        │                                  │
-│                                     │                                  │
-│ [s] start  [p] pause  [q] quit      │                                  │
-└─────────────────────────────────────┴──────────────────────────────────┘
-```
-
-### Implementation Notes
-
-- **Left pane**: `apps/cli/src/ui/tui/navigator.ts` (new, uses `blessed` or `ink`)
-- **Right pane**: spawned via `tmux split-window -h` running `tm autopilot --executor-mode`
-- **Communication**: shared state file `.taskmaster/state/current-run.json` + file watching or event stream
-- **Keybindings**:
-  - `s` - Start selected task
-  - `p` - Pause/resume current run
-  - `q` - Quit (with confirmation if run active)
-  - `↑/↓` - Navigate task list
-  - `Enter` - Expand/collapse subtasks
-
-## Prompt Composition (Detailed)
-
-### System Prompt Assembly
-
-Prompts are composed in three layers:
-
-1. **Base rules** (loaded in order from `.cursor/rules/` and `.claude/agents/`):
-   - `git_workflow.mdc` → git commit conventions, branch policy, PR guidelines
-   - `test_workflow.mdc` → TDD loop requirements, coverage thresholds, test structure
-   - `surgical-test-generator.md` → test generation methodology, project-specific test patterns
-
-2. **Task context injection**:
-   ```
-   You are implementing:
-   Task #42 [analytics]: User metrics tracking
-   Subtask 42.2: Add collection endpoint
-
-   Description:
-   Implement POST /api/metrics endpoint to collect user metrics events
-
-   Acceptance criteria:
-   - POST /api/metrics accepts { userId, eventType, timestamp }
-   - Validates input schema (reject missing/invalid fields)
-   - Persists to database
-   - Returns 201 on success with created record
-   - Returns 400 on validation errors
-
-   Dependencies:
-   - Subtask 42.1 (metrics schema) is complete
-
-   Current phase: RED (generate failing tests)
-   Test command: npm test
-   Test file convention: src/**/*.test.js (vitest framework detected)
-   Branch: analytics/task-42-user-metrics
-   Project language: JavaScript (Node.js)
-   ```
-
-3. **Phase-specific instructions**:
-   - **RED phase**: "Generate minimal failing tests for this subtask. Do NOT implement any production code. Only create test files. Confirm tests fail with clear error messages indicating missing implementation."
-   - **GREEN phase**: "Implement minimal code to pass the failing tests. Follow existing project patterns in `src/`. Only modify files necessary for this subtask. Keep changes focused and reviewable."
-
-### Example Full Prompt (RED Phase)
-
-```markdown
-<SYSTEM PROMPT>
-[Contents of .cursor/rules/git_workflow.mdc]
-[Contents of .cursor/rules/test_workflow.mdc]
-[Contents of .claude/agents/surgical-test-generator.md]
-
-<TASK CONTEXT>
-You are implementing:
-Task #42.2: Add collection endpoint
-
-Description:
-Implement POST /api/metrics endpoint to collect user metrics events
-
-Acceptance criteria:
-- POST /api/metrics accepts { userId, eventType, timestamp }
-- Validates input schema (reject missing/invalid fields)
-- Persists to database using MetricsSchema from subtask 42.1
-- Returns 201 on success with created record
-- Returns 400 on validation errors with details
-
-Dependencies: Subtask 42.1 (metrics schema) is complete
-
-<INSTRUCTION>
-Generate failing tests for this subtask. Follow project conventions:
-- Test file: src/api/__tests__/metrics.test.js
-- Framework: vitest (detected from package.json)
-- Test cases to cover:
-  * POST /api/metrics with valid payload → should return 201 (will fail: endpoint not implemented)
-  * POST /api/metrics with missing userId → should return 400 (will fail: validation not implemented)
-  * POST /api/metrics with invalid timestamp → should return 400 (will fail: validation not implemented)
-  * POST /api/metrics should persist to database → should save record (will fail: persistence not implemented)
-
-Do NOT implement the endpoint code yet. Only create test file(s).
-Confirm tests fail with messages like "Cannot POST /api/metrics" or "endpoint not defined".
-
-Output format:
-1. File path to create: src/api/__tests__/metrics.test.js
-2. Complete test code
-3. Command to run: npm test src/api/__tests__/metrics.test.js
-```
-
-### Example Full Prompt (GREEN Phase)
-
-```markdown
-<SYSTEM PROMPT>
-[Contents of .cursor/rules/git_workflow.mdc]
-[Contents of .cursor/rules/test_workflow.mdc]
-
-<TASK CONTEXT>
-Task #42.2: Add collection endpoint
-[same context as RED phase]
-
-<CURRENT STATE>
-Tests created in RED phase:
-- src/api/__tests__/metrics.test.js
-- 5 tests written, all failing as expected
-
-Test output:
-```
-FAIL src/api/__tests__/metrics.test.js
-  POST /api/metrics
-    ✗ should return 201 with valid payload (endpoint not found)
-    ✗ should return 400 with missing userId (endpoint not found)
-    ✗ should return 400 with invalid timestamp (endpoint not found)
-    ✗ should persist to database (endpoint not found)
-```
-
-<INSTRUCTION>
-Implement minimal code to make all tests pass.
-
-Guidelines:
-- Create/modify file: src/api/metrics.js
-- Use existing patterns from src/api/ (e.g., src/api/users.js for reference)
-- Import MetricsSchema from subtask 42.1 (src/models/schema.js)
-- Implement validation, persistence, and response handling
-- Follow project error handling conventions
-- Keep implementation focused on this subtask only
-
-After implementation:
-1. Run tests: npm test src/api/__tests__/metrics.test.js
-2. Confirm all 5 tests pass
-3. Report results
-
-Output format:
-1. File(s) created/modified
-2. Implementation code
-3. Test command and results
-```
-
-### Prompt Loading Configuration
-
-See `.taskmaster/config.json` → `prompts` section for paths and load order.
-
-## Configuration Schema
-
-### .taskmaster/config.json
-
-```json
-{
-  "autopilot": {
-    "enabled": true,
-    "requireCleanWorkingTree": true,
-    "commitTemplate": "{type}({scope}): {msg}",
-    "defaultCommitType": "feat",
-    "maxGreenAttempts": 3,
-    "testTimeout": 300000
-  },
-  "test": {
-    "runner": "auto",
-    "coverageThresholds": {
-      "lines": 80,
-      "branches": 80,
-      "functions": 80,
-      "statements": 80
-    },
-    "targetedRunPattern": "**/*.test.js"
-  },
-  "git": {
-    "branchPattern": "{tag}/task-{id}-{slug}",
-    "pr": {
-      "enabled": true,
-      "base": "default",
-      "bodyTemplate": ".taskmaster/templates/pr-body.md"
-    }
-  },
-  "prompts": {
-    "rulesPath": ".cursor/rules",
-    "testGeneratorPath": ".claude/agents/surgical-test-generator.md",
-    "loadOrder": ["git_workflow.mdc", "test_workflow.mdc"]
-  }
-}
-```
-
-### Configuration Fields
-
-#### autopilot
-- `enabled` (boolean): Enable/disable autopilot functionality
-- `requireCleanWorkingTree` (boolean): Require clean git state before starting
-- `commitTemplate` (string): Template for commit messages (tokens: `{type}`, `{scope}`, `{msg}`)
-- `defaultCommitType` (string): Default commit type (feat, fix, chore, etc.)
-- `maxGreenAttempts` (number): Maximum retry attempts to achieve green tests (default: 3)
-- `testTimeout` (number): Timeout in milliseconds per test run (default: 300000 = 5min)
-
-#### test
-- `runner` (string): Test runner detection mode (`"auto"` or explicit command like `"npm test"`)
-- `coverageThresholds` (object): Minimum coverage percentages required
-  - `lines`, `branches`, `functions`, `statements` (number): Threshold percentages (0-100)
-- `targetedRunPattern` (string): Glob pattern for targeted subtask test runs
-
-#### git
-- `branchPattern` (string): Branch naming pattern (tokens: `{tag}`, `{id}`, `{slug}`)
-- `pr.enabled` (boolean): Enable automatic PR creation
-- `pr.base` (string): Target branch for PRs (`"default"` uses repo default, or specify like `"main"`)
-- `pr.bodyTemplate` (string): Path to PR body template file (optional)
-
-#### prompts
-- `rulesPath` (string): Directory containing rule files (e.g., `.cursor/rules`)
-- `testGeneratorPath` (string): Path to test generator prompt file
-- `loadOrder` (array): Order to load rule files from `rulesPath`
-
-### Environment Variables
-
-```bash
-# Required for executor
-ANTHROPIC_API_KEY=sk-ant-...          # Claude API key
-
-# Optional: for PR creation
-GITHUB_TOKEN=ghp_...                  # GitHub personal access token
-
-# Optional: for other executors (future)
-OPENAI_API_KEY=sk-...
-GOOGLE_API_KEY=...
-```
-
-## Run Artifacts & Observability
-
-### Per-Run Artifact Structure
-
-Each autopilot run creates a timestamped directory with complete traceability:
-
-```
-.taskmaster/reports/runs/2025-01-15-142033/
-├── manifest.json          # run metadata (task id, start/end time, status)
-├── log.jsonl              # timestamped event stream
-├── commits.txt            # list of commit SHAs made during run
-├── test-results/
-│   ├── subtask-42.1-red.json
-│   ├── subtask-42.1-green.json
-│   ├── subtask-42.2-red.json
-│   ├── subtask-42.2-green-attempt1.json
-│   ├── subtask-42.2-green-attempt2.json
-│   ├── subtask-42.2-green-attempt3.json
-│   └── final-suite.json
-└── pr.md                  # generated PR body
-```
-
-### manifest.json Format
-
-```json
-{
-  "runId": "2025-01-15-142033",
-  "taskId": "42",
-  "tag": "analytics",
-  "branch": "analytics/task-42-user-metrics",
-  "startTime": "2025-01-15T14:20:33Z",
-  "endTime": "2025-01-15T14:45:12Z",
-  "status": "completed",
-  "subtasksCompleted": ["42.1", "42.2", "42.3"],
-  "subtasksFailed": [],
-  "totalCommits": 3,
-  "prUrl": "https://github.com/org/repo/pull/123",
-  "finalCoverage": {
-    "lines": 85.3,
-    "branches": 82.1,
-    "functions": 88.9,
-    "statements": 85.0
-  }
-}
-```
-
-### log.jsonl Format
-
-Event stream in JSON Lines format for easy parsing and debugging:
-
-```jsonl
-{"ts":"2025-01-15T14:20:33Z","phase":"preflight","status":"ok","details":{"testCmd":"npm test","gitClean":true}}
-{"ts":"2025-01-15T14:20:45Z","phase":"branch","status":"ok","branch":"analytics/task-42-user-metrics"}
-{"ts":"2025-01-15T14:21:00Z","phase":"red","subtask":"42.1","status":"ok","tests":{"failed":3,"passed":0}}
-{"ts":"2025-01-15T14:22:15Z","phase":"green","subtask":"42.1","status":"ok","tests":{"passed":3,"failed":0},"attempts":2}
-{"ts":"2025-01-15T14:22:20Z","phase":"commit","subtask":"42.1","status":"ok","sha":"a1b2c3d","message":"feat(metrics): add metrics schema (task 42.1)"}
-{"ts":"2025-01-15T14:23:00Z","phase":"red","subtask":"42.2","status":"ok","tests":{"failed":5,"passed":0}}
-{"ts":"2025-01-15T14:25:30Z","phase":"green","subtask":"42.2","status":"error","tests":{"passed":3,"failed":2},"attempts":3,"error":"Max attempts reached"}
-{"ts":"2025-01-15T14:25:35Z","phase":"pause","reason":"max_attempts","nextAction":"manual_review"}
-```
-
-### Test Results Format
-
-Each test run stores detailed results:
-
-```json
-{
-  "subtask": "42.2",
-  "phase": "green",
-  "attempt": 3,
-  "timestamp": "2025-01-15T14:25:30Z",
-  "command": "npm test src/api/__tests__/metrics.test.js",
-  "exitCode": 1,
-  "duration": 2340,
-  "summary": {
-    "total": 5,
-    "passed": 3,
-    "failed": 2,
-    "skipped": 0
-  },
-  "failures": [
-    {
-      "test": "POST /api/metrics should return 201 with valid payload",
-      "error": "Expected status 201, got 500",
-      "stack": "..."
-    }
-  ],
-  "coverage": {
-    "lines": 78.5,
-    "branches": 75.0,
-    "functions": 80.0,
-    "statements": 78.5
-  }
-}
-```
-
-## Execution Model
-
-### Orchestration vs Direct Execution
-
-The autopilot system uses an **orchestration model** rather than direct code execution:
-
-**Orchestrator Role** (tm-core WorkflowOrchestrator):
-- Maintains state machine tracking current phase (RED/GREEN/COMMIT) per subtask
-- Validates preconditions (tests pass, git state clean, etc.)
-- Returns "work units" describing what needs to be done next
-- Records completion and advances to next phase
-- Persists state for resumability
-
-**Executor Role** (Claude Code/AI session via MCP):
-- Queries orchestrator for next work unit
-- Executes the work (generates tests, writes code, runs tests, makes commits)
-- Reports results back to orchestrator
-- Handles file operations and tool invocations
-
-**Why This Approach?**
-- Leverages existing AI capabilities (Claude Code) rather than duplicating them
-- MCP protocol provides clean separation between state management and execution
-- Allows human oversight and intervention at each phase
-- Simpler to implement: orchestrator is pure state logic, no code generation needed
-- Enables multiple executor types (Claude Code, other AI tools, human developers)
-
-**Example Flow**:
-```typescript
-// Claude Code (via MCP) queries orchestrator
-const workUnit = await orchestrator.getNextWorkUnit('42');
-// => {
-//      phase: 'RED',
-//      subtask: '42.1',
-//      action: 'Generate failing tests for metrics schema',
-//      context: { title, description, dependencies, testFile: 'src/__tests__/schema.test.js' }
-//    }
-
-// Claude Code executes the work (writes test file, runs tests)
-// Then reports back
-await orchestrator.completeWorkUnit('42', '42.1', 'RED', {
-  success: true,
-  testsCreated: ['src/__tests__/schema.test.js'],
-  testsFailed: 3
-});
-
-// Query again for next phase
-const nextWorkUnit = await orchestrator.getNextWorkUnit('42');
-// => { phase: 'GREEN', subtask: '42.1', action: 'Implement code to pass tests', ... }
-```
-
-## Design Decisions
-
-### Why commit per subtask instead of per task?
-
-**Decision**: Commit after each subtask's green state, not after the entire task.
-
-**Rationale**:
-- Atomic commits make code review easier (reviewers can see logical progression)
-- Easier to revert a single subtask if it causes issues downstream
-- Matches the TDD loop's natural checkpoint and cognitive boundary
-- Provides resumability points if the run is interrupted
-
-**Trade-off**: More commits per task (can use squash-merge in PRs if desired)
-
-### Why not support parallel subtask execution?
-
-**Decision**: Sequential subtask execution in Phase 1; parallel execution deferred to Phase 3.
-
-**Rationale**:
-- Subtasks often have implicit dependencies (e.g., schema before endpoint, endpoint before UI)
-- Simpler orchestrator state machine (less complexity = faster to ship)
-- Parallel execution requires explicit dependency DAG and conflict resolution
-- Can be added in Phase 3 once core workflow is proven stable
-
-**Trade-off**: Slower for truly independent subtasks (mitigated by keeping subtasks small and focused)
-
-### Why require 80% coverage by default?
-
-**Decision**: Enforce 80% coverage threshold (lines/branches/functions/statements) before allowing commits.
-
-**Rationale**:
-- Industry standard baseline for production code quality
-- Forces test generation to be comprehensive, not superficial
-- Configurable per project via `.taskmaster/config.json` if too strict
-- Prevents "green tests" that only test happy paths
-
-**Trade-off**: May require more test generation iterations; can be lowered per project
-
-### Why use tmux instead of a rich GUI?
-
-**Decision**: MVP uses tmux split panes for TUI, not Electron/web-based GUI.
-
-**Rationale**:
-- Tmux is universally available on dev machines; no installation burden
-- Terminal-first workflows match developer mental model (no context switching)
-- Simpler to implement and maintain; can add GUI later via extensions
-- State stored in files allows IDE/extension integration without coupling
-
-**Trade-off**: Less visual polish than GUI; requires tmux familiarity
-
-### Why not support multiple executors (codex/gemini/claude) in Phase 1?
-
-**Decision**: Start with Claude executor only; add others in Phase 2+.
-
-**Rationale**:
-- Reduces scope and complexity for initial delivery
-- Claude Code already integrated with existing executor service
-- Executor abstraction already exists; adding more is straightforward later
-- Different executors may need different prompt strategies (requires experimentation)
-
-**Trade-off**: Users locked to Claude initially; can work around with manual executor selection
-
-## Risks and Mitigations
-
-- Model hallucination/large diffs: restrict prompt scope; enforce minimal changes; show diff previews (optional) before commit.
-
-- Flaky tests: allow retries, isolate targeted runs for speed, then full suite before commit.
-
-- Environment variability: detect runners/tools; provide fallbacks and actionable errors.
-
-- PR creation fails: still push and print manual commands; persist PR body to reuse.
-
-## Open Questions
-
-1) Slugging rules for branch names; any length limits or normalization beyond {slug} token sanitize?
-
-2) PR body standard sections beyond run report (e.g., checklist, coverage table)?
-
-3) Default executor prompt fine-tuning once codex/gemini integration is available.
-
-4) Where to store persistent TUI state (pane layout, last selection) in .taskmaster/state.json?
-
-## Branch Naming
-
-- Include both the tag and the task id in the branch name to make lineage explicit.
-
-- Default pattern: <tag>/task-<id>[-slug] (e.g., master/task-12, tag-analytics/task-4-user-auth).
-
-- Configurable via .taskmaster/config.json: git.branchPattern supports tokens {tag}, {id}, {slug}.
-
-## PR Base Branch
-
-- Use the repository’s default branch (detected via git) unless overridden.
-
-- Title format: Task #<id> [<tag>]: <title>.
-
-## RPG Mapping (Repository Planning Graph)
-
-Functional nodes (capabilities):
-
-- Autopilot Orchestration → drives TDD loop and lifecycle
-
-- Test Generation (Surgical) → produces failing tests from subtask context
-
-- Test Execution + Coverage → runs suite, enforces thresholds
-
-- Git/Branch/PR Management → safe operations and PR creation
-
-- TUI/Terminal Integration → interactive control and visibility via tmux
-
-- MCP Integration → structured task/status/context operations
-
-Structural nodes (code organization):
-
-- packages/tm-core:
-
-  - services/workflow-orchestrator.ts (new)
-
-  - services/test-runner-adapter.ts (new)
-
-  - services/git-adapter.ts (new)
-
-  - existing: task-service.ts, task-execution-service.ts, executors/*
-
-- apps/cli:
-
-  - src/commands/autopilot.command.ts (new)
-
-  - src/ui/tui/ (new tmux/TUI helpers)
-
-- scripts/modules:
-
-  - reuse utils/git-utils.js, task-manager/tag-management.js
-
-- .claude/agents/:
-
-  - surgical-test-generator.md
-
-Edges (data/control flow):
-
-- Autopilot → Test Generation → Test Execution → Git Commit → loop
-
-- Autopilot → Git Adapter (branch, tag, PR)
-
-- Autopilot → TUI (event stream) → tmux pane control
-
-- Autopilot → MCP tools for task/status updates
-
-- Test Execution → Coverage gate → Autopilot decision
-
-Topological traversal (implementation order):
-
-1) Git/Test adapters (foundations)
-
-2) Orchestrator skeleton + events
-
-3) CLI autopilot command and dry-run
-
-4) Surgical test-gen integration and execution gate
-
-5) PR creation, run reports, resumability
-
-## Phased Roadmap
-
-- Phase 0: Spike
-
-  - Implement CLI skeleton tm autopilot with dry-run showing planned steps from a real task + subtasks.
-
-  - Detect test runner (package.json) and git state; render a preflight report.
-
-- Phase 1: Core Rails (State Machine & Orchestration)
-
-  - Implement WorkflowOrchestrator in tm-core as a **state machine** that tracks TDD phases per subtask.
-
-  - Orchestrator **guides** the current AI session (Claude Code/MCP client) rather than executing code itself.
-
-  - Add Git/Test adapters for status checks and validation (not direct execution).
-
-  - WorkflowOrchestrator API:
-    - `getNextWorkUnit(taskId)` → returns next phase to execute (RED/GREEN/COMMIT) with context
-    - `completeWorkUnit(taskId, subtaskId, phase, result)` → records completion and advances state
-    - `getRunState(taskId)` → returns current progress and resumability data
-
-  - MCP integration: expose work unit endpoints so Claude Code can query "what to do next" and report back.
-
-  - Branch/tag mapping via existing tag-management APIs.
-
-  - Run report persisted under .taskmaster/reports/runs/ with state checkpoints for resumability.
-
-- Phase 2: PR + Resumability
-
-  - Add gh PR creation with well-formed body using the run report.
-
-  - Introduce resumable checkpoints and --resume flag.
-
-  - Add coverage enforcement and optional lint/format step.
-
-- Phase 3: Extensibility + Guardrails
-
-  - Add support for basic pytest/go test adapters.
-
-  - Add safeguards: diff preview mode, manual confirm gates, aggressive minimal-change prompts.
-
-  - Optional: small TUI panel and extension panel leveraging the same run state file.
-
-## References (Repo)
-
-- Test Workflow: .cursor/rules/test_workflow.mdc
-
-- Git Workflow: .cursor/rules/git_workflow.mdc
-
-- CLI: apps/cli/src/commands/start.command.ts, apps/cli/src/ui/components/*.ts
-
-- Core Services: packages/tm-core/src/services/task-service.ts, task-execution-service.ts
-
-- Executors: packages/tm-core/src/executors/*
-
-- Git Utilities: scripts/modules/utils/git-utils.js
-
-- Tag Management: scripts/modules/task-manager/tag-management.js
-
- - Surgical Test Generator: .claude/agents/surgical-test-generator.md
-

.taskmaster/docs/prd-tm-start.txt

@@ -1,91 +0,0 @@
-<context>
-# Overview
-Add a new CLI command: `task-master start <task_id>` (alias: `tm start <task_id>`). This command hard-codes `claude-code` as the executor, fetches task details, builds a standardized prompt, runs claude-code, shows the result, checks for git changes, and auto-marks the task as done if successful.
-
-We follow the Commander class pattern, reuse task retrieval from `show` command flow. Extremely minimal for 1-hour hackathon timeline.
-
-# Core Features
-- `start` command (Commander class style) 
-- Hard-coded executor: `claude-code`
-- Standardized prompt designed for minimal changes following existing patterns
-- Shows claude-code output (no streaming)
-- Git status check for success detection
-- Auto-mark task done if successful
-
-# User Experience
-```
-task-master start 12
-```
-1) Fetches Task #12 details
-2) Builds standardized prompt with task context
-3) Runs claude-code with the prompt
-4) Shows output
-5) Checks git status for changes
-6) Auto-marks task done if changes detected
-</context>
-
-<PRD>
-# Technical Architecture
-
-- Command pattern:
-  - Create `apps/cli/src/commands/start.command.ts` modeled on [list.command.ts](mdc:apps/cli/src/commands/list.command.ts) and task lookup from [show.command.ts](mdc:apps/cli/src/commands/show.command.ts)
-
-- Task retrieval:
-  - Use `@tm/core` via `createTaskMasterCore` to get task by ID
-  - Extract: id, title, description, details
-
-- Executor (ultra-simple approach):
-  - Execute `claude "full prompt here"` command directly
-  - The prompt tells Claude to first run `tm show <task_id>` to get task details
-  - Then tells Claude to implement the code changes
-  - This opens Claude CLI interface naturally in the current terminal
-  - No subprocess management needed - just execute the command
-
-- Execution flow:
-  1) Validate `<task_id>` exists; exit with error if not
-  2) Build standardized prompt that includes instructions to run `tm show <task_id>`
-  3) Execute `claude "prompt"` command directly in terminal
-  4) Claude CLI opens, runs `tm show`, then implements changes
-  5) After Claude session ends, run `git status --porcelain` to detect changes
-  6) If changes detected, auto-run `task-master set-status --id=<task_id> --status=done`
-
-- Success criteria:
-  - Success = exit code 0 AND git shows modified/created files
-  - Print changed file paths; warn if no changes detected
-
-# Development Roadmap
-
-MVP (ship in ~1 hour):
-1) Implement `start.command.ts` (Commander class), parse `<task_id>`
-2) Validate task exists via tm-core 
-3) Build prompt that tells Claude to run `tm show <task_id>` then implement
-4) Execute `claude "prompt"` command, then check git status and auto-mark done
-
-# Risks and Mitigations
-- Executor availability: Error clearly if `claude-code` provider fails
-- False success: Git-change heuristic acceptable for hackathon MVP
-
-# Appendix
-
-**Standardized Prompt Template:**
-```
-You are an AI coding assistant with access to this repository's codebase.
-
-First, run this command to get the task details:
-tm show <task_id>
-
-Then implement the task with these requirements:
-- Make the SMALLEST number of code changes possible
-- Follow ALL existing patterns in the codebase (you have access to analyze the code)
-- Do NOT over-engineer the solution
-- Use existing files/functions/patterns wherever possible
-- When complete, print: COMPLETED: <brief summary of changes>
-
-Begin by running tm show <task_id> to understand what needs to be implemented.
-```
-
-**Key References:**
-- [list.command.ts](mdc:apps/cli/src/commands/list.command.ts) - Command structure
-- [show.command.ts](mdc:apps/cli/src/commands/show.command.ts) - Task validation
-- Node.js `child_process.exec()` - For executing `claude "prompt"` command
-</PRD>

.taskmaster/docs/tdd-workflow-phase-0-spike.md

@@ -1,130 +0,0 @@
-# Phase 0: Spike - Autonomous TDD Workflow ✅ COMPLETE
-
-## Objective
-Validate feasibility and build foundational understanding before full implementation.
-
-## Status
-**COMPLETED** - All deliverables implemented and validated.
-
-See `apps/cli/src/commands/autopilot.command.ts` for implementation.
-
-## Scope
-- Implement CLI skeleton `tm autopilot` with dry-run mode
-- Show planned steps from a real task with subtasks
-- Detect test runner from package.json
-- Detect git state and render preflight report
-
-## Deliverables
-
-### 1. CLI Command Skeleton
-- Create `apps/cli/src/commands/autopilot.command.ts`
-- Support `tm autopilot <taskId>` command
-- Implement `--dry-run` flag
-- Basic help text and usage information
-
-### 2. Preflight Detection System
-- Detect test runner from package.json (npm test, pnpm test, etc.)
-- Check git working tree state (clean/dirty)
-- Validate required tools are available (git, gh, node/npm)
-- Detect default branch
-
-### 3. Dry-Run Execution Plan Display
-Display planned execution for a task including:
-- Preflight checks status
-- Branch name that would be created
-- Tag that would be set
-- List of subtasks in execution order
-- For each subtask:
-  - RED phase: test file that would be created
-  - GREEN phase: implementation files that would be modified
-  - COMMIT: commit message that would be used
-- Finalization steps: test suite run, coverage check, push, PR creation
-
-### 4. Task Loading & Validation
-- Load task from TaskMaster state
-- Validate task exists and has subtasks
-- If no subtasks, show message about needing to expand first
-- Show dependency order for subtasks
-
-## Example Output
-
-```bash
-$ tm autopilot 42 --dry-run
-
-Autopilot Plan for Task #42 [analytics]: User metrics tracking
-─────────────────────────────────────────────────────────────
-
-Preflight Checks:
-  ✓ Working tree is clean
-  ✓ Test command detected: npm test
-  ✓ Tools available: git, gh, node, npm
-  ✓ Current branch: main (will create new branch)
-  ✓ Task has 3 subtasks ready to execute
-
-Branch & Tag:
-  → Will create branch: analytics/task-42-user-metrics
-  → Will set active tag: analytics
-
-Execution Plan (3 subtasks):
-
-  1. Subtask 42.1: Add metrics schema
-     RED:    Generate tests → src/__tests__/schema.test.js
-     GREEN:  Implement code → src/schema.js
-     COMMIT: "feat(metrics): add metrics schema (task 42.1)"
-
-  2. Subtask 42.2: Add collection endpoint [depends on 42.1]
-     RED:    Generate tests → src/api/__tests__/metrics.test.js
-     GREEN:  Implement code → src/api/metrics.js
-     COMMIT: "feat(metrics): add collection endpoint (task 42.2)"
-
-  3. Subtask 42.3: Add dashboard widget [depends on 42.2]
-     RED:    Generate tests → src/components/__tests__/MetricsWidget.test.jsx
-     GREEN:  Implement code → src/components/MetricsWidget.jsx
-     COMMIT: "feat(metrics): add dashboard widget (task 42.3)"
-
-Finalization:
-  → Run full test suite with coverage (threshold: 80%)
-  → Push branch to origin (will confirm)
-  → Create PR targeting main
-
-Estimated commits: 3
-Estimated duration: ~20-30 minutes (depends on implementation complexity)
-
-Run without --dry-run to execute.
-```
-
-## Success Criteria
-- Dry-run output is clear and matches expected workflow
-- Preflight detection works correctly on the project repo
-- Task loading integrates with existing TaskMaster state
-- No actual git operations or file modifications occur in dry-run mode
-
-## Out of Scope
-- Actual test generation
-- Actual code implementation
-- Git operations (branch creation, commits, push)
-- PR creation
-- Test execution
-
-## Implementation Notes
-- Reuse existing `TaskService` from `packages/tm-core`
-- Use existing git utilities from `scripts/modules/utils/git-utils.js`
-- Load task/subtask data from `.taskmaster/tasks/tasks.json`
-- Detect test command via package.json → scripts.test field
-
-## Dependencies
-- Existing TaskMaster CLI structure
-- Existing task storage format
-- Git utilities
-
-## Estimated Effort
-2-3 days
-
-## Validation
-Test dry-run mode with:
-- Task with 1 subtask
-- Task with multiple subtasks
-- Task with dependencies between subtasks
-- Task without subtasks (should show warning)
-- Dirty git working tree (should warn)
-- Missing tools (should error with helpful message)

.taskmaster/docs/tdd-workflow-phase-1-orchestrator.md

@@ -1,369 +0,0 @@
-# Phase 1: Core Rails - State Machine & Orchestration
-
-## Objective
-Build the WorkflowOrchestrator as a state machine that guides AI sessions through TDD workflow, rather than directly executing code.
-
-## Architecture Overview
-
-### Execution Model
-The orchestrator acts as a **state manager and guide**, not a code executor:
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│                    Claude Code (MCP Client)                  │
-│  - Queries "what to do next"                                │
-│  - Executes work (writes tests, code, runs commands)        │
-│  - Reports completion                                        │
-└────────────────┬────────────────────────────────────────────┘
-                 │ MCP Protocol
-                 ▼
-┌─────────────────────────────────────────────────────────────┐
-│              WorkflowOrchestrator (tm-core)                  │
-│  - Maintains state machine (RED → GREEN → COMMIT)           │
-│  - Returns work units with context                          │
-│  - Validates preconditions                                  │
-│  - Records progress                                         │
-│  - Persists state for resumability                          │
-└─────────────────────────────────────────────────────────────┘
-```
-
-### Why This Approach?
-1. **Separation of Concerns**: State management separate from code execution
-2. **Leverage Existing Tools**: Uses Claude Code's capabilities instead of reimplementing
-3. **Human-in-the-Loop**: Easy to inspect state and intervene at any phase
-4. **Simpler Implementation**: Orchestrator is pure logic, no AI model integration needed
-5. **Flexible Executors**: Any tool (Claude Code, human, other AI) can execute work units
-
-## Core Components
-
-### 1. WorkflowOrchestrator Service
-**Location**: `packages/tm-core/src/services/workflow-orchestrator.service.ts`
-
-**Responsibilities**:
-- Track current phase (RED/GREEN/COMMIT) per subtask
-- Generate work units with context for each phase
-- Validate phase completion criteria
-- Advance state machine on successful completion
-- Handle errors and retry logic
-- Persist run state for resumability
-
-**API**:
-```typescript
-interface WorkflowOrchestrator {
-  // Start a new autopilot run
-  startRun(taskId: string, options?: RunOptions): Promise<RunContext>;
-
-  // Get next work unit to execute
-  getNextWorkUnit(runId: string): Promise<WorkUnit | null>;
-
-  // Report work unit completion
-  completeWorkUnit(
-    runId: string,
-    workUnitId: string,
-    result: WorkUnitResult
-  ): Promise<void>;
-
-  // Get current run state
-  getRunState(runId: string): Promise<RunState>;
-
-  // Pause/resume
-  pauseRun(runId: string): Promise<void>;
-  resumeRun(runId: string): Promise<void>;
-}
-
-interface WorkUnit {
-  id: string;                    // Unique work unit ID
-  phase: 'RED' | 'GREEN' | 'COMMIT';
-  subtaskId: string;             // e.g., "42.1"
-  action: string;                // Human-readable description
-  context: WorkUnitContext;      // All info needed to execute
-  preconditions: Precondition[]; // Checks before execution
-}
-
-interface WorkUnitContext {
-  taskId: string;
-  taskTitle: string;
-  subtaskTitle: string;
-  subtaskDescription: string;
-  dependencies: string[];        // Completed subtask IDs
-  testCommand: string;           // e.g., "npm test"
-
-  // Phase-specific context
-  redPhase?: {
-    testFile: string;            // Where to create test
-    testFramework: string;       // e.g., "vitest"
-    acceptanceCriteria: string[];
-  };
-
-  greenPhase?: {
-    testFile: string;            // Test to make pass
-    implementationHints: string[];
-    expectedFiles: string[];     // Files likely to modify
-  };
-
-  commitPhase?: {
-    commitMessage: string;       // Pre-generated message
-    filesToCommit: string[];     // Files modified in RED+GREEN
-  };
-}
-
-interface WorkUnitResult {
-  success: boolean;
-  phase: 'RED' | 'GREEN' | 'COMMIT';
-
-  // RED phase results
-  testsCreated?: string[];
-  testsFailed?: number;
-
-  // GREEN phase results
-  testsPassed?: number;
-  filesModified?: string[];
-  attempts?: number;
-
-  // COMMIT phase results
-  commitSha?: string;
-
-  // Common
-  error?: string;
-  logs?: string;
-}
-
-interface RunState {
-  runId: string;
-  taskId: string;
-  status: 'running' | 'paused' | 'completed' | 'failed';
-  currentPhase: 'RED' | 'GREEN' | 'COMMIT';
-  currentSubtask: string;
-  completedSubtasks: string[];
-  failedSubtasks: string[];
-  startTime: Date;
-  lastUpdateTime: Date;
-
-  // Resumability
-  checkpoint: {
-    subtaskId: string;
-    phase: 'RED' | 'GREEN' | 'COMMIT';
-    attemptNumber: number;
-  };
-}
-```
-
-### 2. State Machine Logic
-
-**Phase Transitions**:
-```
-START → RED(subtask 1) → GREEN(subtask 1) → COMMIT(subtask 1)
-                                               ↓
-                        RED(subtask 2) ← ─ ─ ─ ┘
-                             ↓
-                        GREEN(subtask 2)
-                             ↓
-                        COMMIT(subtask 2)
-                             ↓
-                           (repeat for remaining subtasks)
-                             ↓
-                        FINALIZE → END
-```
-
-**Phase Rules**:
-- **RED**: Can only transition to GREEN if tests created and failing
-- **GREEN**: Can only transition to COMMIT if tests passing (attempt < maxAttempts)
-- **COMMIT**: Can only transition to next RED if commit successful
-- **FINALIZE**: Can only start if all subtasks completed
-
-**Preconditions**:
-- RED: No uncommitted changes (or staged from previous GREEN that failed)
-- GREEN: RED phase complete, tests exist and are failing
-- COMMIT: GREEN phase complete, all tests passing, coverage meets threshold
-
-### 3. MCP Integration
-
-**New MCP Tools** (expose WorkflowOrchestrator via MCP):
-```typescript
-// Start an autopilot run
-mcp__task_master_ai__autopilot_start(taskId: string, dryRun?: boolean)
-
-// Get next work unit
-mcp__task_master_ai__autopilot_next_work_unit(runId: string)
-
-// Complete current work unit
-mcp__task_master_ai__autopilot_complete_work_unit(
-  runId: string,
-  workUnitId: string,
-  result: WorkUnitResult
-)
-
-// Get run state
-mcp__task_master_ai__autopilot_get_state(runId: string)
-
-// Pause/resume
-mcp__task_master_ai__autopilot_pause(runId: string)
-mcp__task_master_ai__autopilot_resume(runId: string)
-```
-
-### 4. Git/Test Adapters
-
-**GitAdapter** (`packages/tm-core/src/services/git-adapter.service.ts`):
-- Check working tree status
-- Validate branch state
-- Read git config (user, remote, default branch)
-- **Does NOT execute** git commands (that's executor's job)
-
-**TestAdapter** (`packages/tm-core/src/services/test-adapter.service.ts`):
-- Detect test framework from package.json
-- Parse test output (failures, passes, coverage)
-- Validate coverage thresholds
-- **Does NOT run** tests (that's executor's job)
-
-### 5. Run State Persistence
-
-**Storage Location**: `.taskmaster/reports/runs/<runId>/`
-
-**Files**:
-- `state.json` - Current run state (for resumability)
-- `log.jsonl` - Event stream (timestamped work unit completions)
-- `manifest.json` - Run metadata
-- `work-units.json` - All work units generated for this run
-
-**Example `state.json`**:
-```json
-{
-  "runId": "2025-01-15-142033",
-  "taskId": "42",
-  "status": "paused",
-  "currentPhase": "GREEN",
-  "currentSubtask": "42.2",
-  "completedSubtasks": ["42.1"],
-  "failedSubtasks": [],
-  "checkpoint": {
-    "subtaskId": "42.2",
-    "phase": "GREEN",
-    "attemptNumber": 2
-  },
-  "startTime": "2025-01-15T14:20:33Z",
-  "lastUpdateTime": "2025-01-15T14:35:12Z"
-}
-```
-
-## Implementation Plan
-
-### Step 1: WorkflowOrchestrator Skeleton
-- [ ] Create `workflow-orchestrator.service.ts` with interfaces
-- [ ] Implement state machine logic (phase transitions)
-- [ ] Add run state persistence (state.json, log.jsonl)
-- [ ] Write unit tests for state machine
-
-### Step 2: Work Unit Generation
-- [ ] Implement `getNextWorkUnit()` with context assembly
-- [ ] Generate RED phase work units (test file paths, criteria)
-- [ ] Generate GREEN phase work units (implementation hints)
-- [ ] Generate COMMIT phase work units (commit messages)
-
-### Step 3: Git/Test Adapters
-- [ ] Create GitAdapter for status checks only
-- [ ] Create TestAdapter for output parsing only
-- [ ] Add precondition validation using adapters
-- [ ] Write adapter unit tests
-
-### Step 4: MCP Integration
-- [ ] Add MCP tool definitions in `packages/mcp-server/src/tools/`
-- [ ] Wire up WorkflowOrchestrator to MCP tools
-- [ ] Test MCP tools via Claude Code
-- [ ] Document MCP workflow in CLAUDE.md
-
-### Step 5: CLI Integration
-- [ ] Update `autopilot.command.ts` to call WorkflowOrchestrator
-- [ ] Add `--interactive` mode that shows work units and waits for completion
-- [ ] Add `--resume` flag to continue paused runs
-- [ ] Test end-to-end flow
-
-### Step 6: Integration Testing
-- [ ] Create test task with 2-3 subtasks
-- [ ] Run autopilot start → get work unit → complete → repeat
-- [ ] Verify state persistence and resumability
-- [ ] Test failure scenarios (test failures, git issues)
-
-## Success Criteria
-- [ ] WorkflowOrchestrator can generate work units for all phases
-- [ ] MCP tools allow Claude Code to query and complete work units
-- [ ] State persists correctly between work unit completions
-- [ ] Run can be paused and resumed from checkpoint
-- [ ] Adapters validate preconditions without executing commands
-- [ ] End-to-end: Claude Code can complete a simple task via work units
-
-## Out of Scope (Phase 1)
-- Actual git operations (branch creation, commits) - executor handles this
-- Actual test execution - executor handles this
-- PR creation - deferred to Phase 2
-- TUI interface - deferred to Phase 3
-- Coverage enforcement - deferred to Phase 2
-
-## Example Usage Flow
-
-```bash
-# Terminal 1: Claude Code session
-$ claude
-
-# In Claude Code (via MCP):
-> Start autopilot for task 42
-[Calls mcp__task_master_ai__autopilot_start(42)]
-→ Run started: run-2025-01-15-142033
-
-> Get next work unit
-[Calls mcp__task_master_ai__autopilot_next_work_unit(run-2025-01-15-142033)]
-→ Work unit: RED phase for subtask 42.1
-→ Action: Generate failing tests for metrics schema
-→ Test file: src/__tests__/schema.test.js
-→ Framework: vitest
-
-> [Claude Code creates test file, runs tests]
-
-> Complete work unit
-[Calls mcp__task_master_ai__autopilot_complete_work_unit(
-  run-2025-01-15-142033,
-  workUnit-42.1-RED,
-  { success: true, testsCreated: ['src/__tests__/schema.test.js'], testsFailed: 3 }
-)]
-→ Work unit completed. State saved.
-
-> Get next work unit
-[Calls mcp__task_master_ai__autopilot_next_work_unit(run-2025-01-15-142033)]
-→ Work unit: GREEN phase for subtask 42.1
-→ Action: Implement code to pass failing tests
-→ Test file: src/__tests__/schema.test.js
-→ Expected implementation: src/schema.js
-
-> [Claude Code implements schema.js, runs tests, confirms all pass]
-
-> Complete work unit
-[...]
-→ Work unit completed. Ready for COMMIT.
-
-> Get next work unit
-[...]
-→ Work unit: COMMIT phase for subtask 42.1
-→ Commit message: "feat(metrics): add metrics schema (task 42.1)"
-→ Files to commit: src/__tests__/schema.test.js, src/schema.js
-
-> [Claude Code stages files and commits]
-
-> Complete work unit
-[...]
-→ Subtask 42.1 complete! Moving to 42.2...
-```
-
-## Dependencies
-- Existing TaskService (task loading, status updates)
-- Existing PreflightChecker (environment validation)
-- Existing TaskLoaderService (dependency ordering)
-- MCP server infrastructure
-
-## Estimated Effort
-7-10 days
-
-## Next Phase
-Phase 2 will add:
-- PR creation via gh CLI
-- Coverage enforcement
-- Enhanced error recovery
-- Full resumability testing

.taskmaster/docs/tdd-workflow-phase-2-pr-resumability.md

@@ -1,433 +0,0 @@
-# Phase 2: PR + Resumability - Autonomous TDD Workflow
-
-## Objective
-Add PR creation with GitHub CLI integration, resumable checkpoints for interrupted runs, and enhanced guardrails with coverage enforcement.
-
-## Scope
-- GitHub PR creation via `gh` CLI
-- Well-formed PR body using run report
-- Resumable checkpoints and `--resume` flag
-- Coverage enforcement before finalization
-- Optional lint/format step
-- Enhanced error recovery
-
-## Deliverables
-
-### 1. PR Creation Integration
-
-**PRAdapter** (`packages/tm-core/src/services/pr-adapter.ts`):
-```typescript
-class PRAdapter {
-  async isGHAvailable(): Promise<boolean>
-  async createPR(options: PROptions): Promise<PRResult>
-  async getPRTemplate(runReport: RunReport): Promise<string>
-
-  // Fallback for missing gh CLI
-  async getManualPRInstructions(options: PROptions): Promise<string>
-}
-
-interface PROptions {
-  branch: string
-  base: string
-  title: string
-  body: string
-  draft?: boolean
-}
-
-interface PRResult {
-  url: string
-  number: number
-}
-```
-
-**PR Title Format:**
-```
-Task #<id> [<tag>]: <title>
-```
-
-Example: `Task #42 [analytics]: User metrics tracking`
-
-**PR Body Template:**
-
-Located at `.taskmaster/templates/pr-body.md`:
-
-```markdown
-## Summary
-
-Implements Task #42 from TaskMaster autonomous workflow.
-
-**Branch:** {branch}
-**Tag:** {tag}
-**Subtasks completed:** {subtaskCount}
-
-{taskDescription}
-
-## Subtasks
-
-{subtasksList}
-
-## Test Coverage
-
-| Metric | Coverage |
-|--------|----------|
-| Lines | {lines}% |
-| Branches | {branches}% |
-| Functions | {functions}% |
-| Statements | {statements}% |
-
-**All subtasks passed with {totalTests} tests.**
-
-## Commits
-
-{commitsList}
-
-## Run Report
-
-Full execution report: `.taskmaster/reports/runs/{runId}/`
-
----
-
-🤖 Generated with [Task Master](https://github.com/cline/task-master) autonomous TDD workflow
-```
-
-**Token replacement:**
-- `{branch}` → branch name
-- `{tag}` → active tag
-- `{subtaskCount}` → number of completed subtasks
-- `{taskDescription}` → task description from TaskMaster
-- `{subtasksList}` → markdown list of subtask titles
-- `{lines}`, `{branches}`, `{functions}`, `{statements}` → coverage percentages
-- `{totalTests}` → total test count
-- `{commitsList}` → markdown list of commit SHAs and messages
-- `{runId}` → run ID timestamp
-
-### 2. GitHub CLI Integration
-
-**Detection:**
-```bash
-which gh
-```
-
-If not found, show fallback instructions:
-```bash
-✓ Branch pushed: analytics/task-42-user-metrics
-✗ gh CLI not found - cannot create PR automatically
-
-To create PR manually:
-  gh pr create \
-    --base main \
-    --head analytics/task-42-user-metrics \
-    --title "Task #42 [analytics]: User metrics tracking" \
-    --body-file .taskmaster/reports/runs/2025-01-15-142033/pr.md
-
-Or visit:
-  https://github.com/org/repo/compare/main...analytics/task-42-user-metrics
-```
-
-**Confirmation gate:**
-```bash
-Ready to create PR:
-  Title: Task #42 [analytics]: User metrics tracking
-  Base: main
-  Head: analytics/task-42-user-metrics
-
-Create PR? [Y/n]
-```
-
-Unless `--no-confirm` flag is set.
-
-### 3. Resumable Workflow
-
-**State Checkpoint** (`state.json`):
-```json
-{
-  "runId": "2025-01-15-142033",
-  "taskId": "42",
-  "phase": "subtask-loop",
-  "currentSubtask": "42.2",
-  "currentPhase": "green",
-  "attempts": 2,
-  "completedSubtasks": ["42.1"],
-  "commits": ["a1b2c3d"],
-  "branch": "analytics/task-42-user-metrics",
-  "tag": "analytics",
-  "canResume": true,
-  "pausedAt": "2025-01-15T14:25:35Z",
-  "pausedReason": "max_attempts_reached",
-  "nextAction": "manual_review_required"
-}
-```
-
-**Resume Command:**
-```bash
-$ tm autopilot --resume
-
-Resuming run: 2025-01-15-142033
-  Task: #42 [analytics] User metrics tracking
-  Branch: analytics/task-42-user-metrics
-  Last subtask: 42.2 (GREEN phase, attempt 2/3 failed)
-  Paused: 5 minutes ago
-
-Reason: Could not achieve green state after 3 attempts
-Last error: POST /api/metrics returns 500 instead of 201
-
-Resume from subtask 42.2 GREEN phase? [Y/n]
-```
-
-**Resume logic:**
-1. Load state from `.taskmaster/reports/runs/<runId>/state.json`
-2. Verify branch still exists and is checked out
-3. Verify no uncommitted changes (unless `--force`)
-4. Continue from last checkpoint phase
-5. Update state file as execution progresses
-
-**Multiple interrupted runs:**
-```bash
-$ tm autopilot --resume
-
-Found 2 resumable runs:
-  1. 2025-01-15-142033 - Task #42 (paused 5 min ago at subtask 42.2 GREEN)
-  2. 2025-01-14-103022 - Task #38 (paused 2 hours ago at subtask 38.3 RED)
-
-Select run to resume [1-2]:
-```
-
-### 4. Coverage Enforcement
-
-**Coverage Check Phase** (before finalization):
-```typescript
-async function enforceCoverage(runId: string): Promise<void> {
-  const testResults = await testRunner.runAll()
-  const coverage = await testRunner.getCoverage()
-
-  const thresholds = config.test.coverageThresholds
-  const failures = []
-
-  if (coverage.lines < thresholds.lines) {
-    failures.push(`Lines: ${coverage.lines}% < ${thresholds.lines}%`)
-  }
-  // ... check branches, functions, statements
-
-  if (failures.length > 0) {
-    throw new CoverageError(
-      `Coverage thresholds not met:\n${failures.join('\n')}`
-    )
-  }
-
-  // Store coverage in run report
-  await storeRunArtifact(runId, 'coverage.json', coverage)
-}
-```
-
-**Handling coverage failures:**
-```bash
-⚠️  Coverage check failed:
-  Lines: 78.5% < 80%
-  Branches: 75.0% < 80%
-
-Options:
-  1. Add more tests and resume
-  2. Lower thresholds in .taskmaster/config.json
-  3. Skip coverage check: tm autopilot --resume --skip-coverage
-
-Run paused. Fix coverage and resume with:
-  tm autopilot --resume
-```
-
-### 5. Optional Lint/Format Step
-
-**Configuration:**
-```json
-{
-  "autopilot": {
-    "finalization": {
-      "lint": {
-        "enabled": true,
-        "command": "npm run lint",
-        "fix": true,
-        "failOnError": false
-      },
-      "format": {
-        "enabled": true,
-        "command": "npm run format",
-        "commitChanges": true
-      }
-    }
-  }
-}
-```
-
-**Execution:**
-```bash
-Finalization Steps:
-
-  ✓ All tests passing (12 tests, 0 failures)
-  ✓ Coverage thresholds met (85% lines, 82% branches)
-
-  LINT Running linter... ⏳
-  LINT ✓ No lint errors
-
-  FORMAT Running formatter... ⏳
-  FORMAT ✓ Formatted 3 files
-  FORMAT ✓ Committed formatting changes: "chore: auto-format code"
-
-  PUSH Pushing to origin... ⏳
-  PUSH ✓ Pushed analytics/task-42-user-metrics
-
-  PR Creating pull request... ⏳
-  PR ✓ Created PR #123
-      https://github.com/org/repo/pull/123
-```
-
-### 6. Enhanced Error Recovery
-
-**Pause Points:**
-- Max GREEN attempts reached (current)
-- Coverage check failed (new)
-- Lint errors (if `failOnError: true`)
-- Git push failed (new)
-- PR creation failed (new)
-
-**Each pause saves:**
-- Full state checkpoint
-- Last command output
-- Suggested next actions
-- Resume instructions
-
-**Automatic recovery attempts:**
-- Git push: retry up to 3 times with backoff
-- PR creation: fall back to manual instructions
-- Lint: auto-fix if enabled, otherwise pause
-
-### 7. Finalization Phase Enhancement
-
-**Updated workflow:**
-1. Run full test suite
-2. Check coverage thresholds → pause if failed
-3. Run lint (if enabled) → pause if failed and `failOnError: true`
-4. Run format (if enabled) → auto-commit changes
-5. Confirm push (unless `--no-confirm`)
-6. Push branch → retry on failure
-7. Generate PR body from template
-8. Create PR via gh → fall back to manual instructions
-9. Update task status to 'review' (configurable)
-10. Save final run report
-
-**Final output:**
-```bash
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-✅ Task #42 [analytics]: User metrics tracking - COMPLETE
-
-  Branch: analytics/task-42-user-metrics
-  Subtasks completed: 3/3
-  Commits: 3
-  Total tests: 12 (12 passed, 0 failed)
-  Coverage: 85% lines, 82% branches, 88% functions, 85% statements
-
-  PR #123: https://github.com/org/repo/pull/123
-
-  Run report: .taskmaster/reports/runs/2025-01-15-142033/
-
-Next steps:
-  - Review PR and request changes if needed
-  - Merge when ready
-  - Task status updated to 'review'
-
-Completed in 24 minutes
-```
-
-## CLI Updates
-
-**New flags:**
-- `--resume` → Resume from last checkpoint
-- `--skip-coverage` → Skip coverage checks
-- `--skip-lint` → Skip lint step
-- `--skip-format` → Skip format step
-- `--skip-pr` → Push branch but don't create PR
-- `--draft-pr` → Create draft PR instead of ready-for-review
-
-## Configuration Updates
-
-**Add to `.taskmaster/config.json`:**
-```json
-{
-  "autopilot": {
-    "finalization": {
-      "lint": {
-        "enabled": false,
-        "command": "npm run lint",
-        "fix": true,
-        "failOnError": false
-      },
-      "format": {
-        "enabled": false,
-        "command": "npm run format",
-        "commitChanges": true
-      },
-      "updateTaskStatus": "review"
-    }
-  },
-  "git": {
-    "pr": {
-      "enabled": true,
-      "base": "default",
-      "bodyTemplate": ".taskmaster/templates/pr-body.md",
-      "draft": false
-    },
-    "pushRetries": 3,
-    "pushRetryDelay": 5000
-  }
-}
-```
-
-## Success Criteria
-- Can create PR automatically with well-formed body
-- Can resume interrupted runs from any checkpoint
-- Coverage checks prevent low-quality code from being merged
-- Clear error messages and recovery paths for all failure modes
-- Run reports include full PR context for review
-
-## Out of Scope (defer to Phase 3)
-- Multiple test framework support (pytest, go test)
-- Diff preview before commits
-- TUI panel implementation
-- Extension/IDE integration
-
-## Testing Strategy
-- Mock `gh` CLI for PR creation tests
-- Test resume from each possible pause point
-- Test coverage failure scenarios
-- Test lint/format integration with mock commands
-- End-to-end test with PR creation on test repo
-
-## Dependencies
-- Phase 1 completed (core workflow)
-- GitHub CLI (`gh`) installed (optional, fallback provided)
-- Test framework supports coverage output
-
-## Estimated Effort
-1-2 weeks
-
-## Risks & Mitigations
-- **Risk:** GitHub CLI auth issues
-  - **Mitigation:** Clear auth setup docs, fallback to manual instructions
-
-- **Risk:** PR body template doesn't match all project needs
-  - **Mitigation:** Make template customizable via config path
-
-- **Risk:** Resume state gets corrupted
-  - **Mitigation:** Validate state on load, provide --force-reset option
-
-- **Risk:** Coverage calculation differs between runs
-  - **Mitigation:** Store coverage with each test run for comparison
-
-## Validation
-Test with:
-- Successful PR creation end-to-end
-- Resume from GREEN attempt failure
-- Resume from coverage failure
-- Resume from lint failure
-- Missing `gh` CLI (fallback to manual)
-- Lint/format integration enabled
-- Multiple interrupted runs (selection UI)

.taskmaster/docs/tdd-workflow-phase-3-extensibility-guardrails.md

@@ -1,534 +0,0 @@
-# Phase 3: Extensibility + Guardrails - Autonomous TDD Workflow
-
-## Objective
-Add multi-language/framework support, enhanced safety guardrails, TUI interface, and extensibility for IDE/editor integration.
-
-## Scope
-- Multi-language test runner support (pytest, go test, etc.)
-- Enhanced safety: diff preview, confirmation gates, minimal-change prompts
-- Optional TUI panel with tmux integration
-- State-based extension API for IDE integration
-- Parallel subtask execution (experimental)
-
-## Deliverables
-
-### 1. Multi-Language Test Runner Support
-
-**Extend TestRunnerAdapter:**
-```typescript
-class TestRunnerAdapter {
-  // Existing methods...
-
-  async detectLanguage(): Promise<Language>
-  async detectFramework(language: Language): Promise<Framework>
-  async getFrameworkAdapter(framework: Framework): Promise<FrameworkAdapter>
-}
-
-enum Language {
-  JavaScript = 'javascript',
-  TypeScript = 'typescript',
-  Python = 'python',
-  Go = 'go',
-  Rust = 'rust'
-}
-
-enum Framework {
-  Vitest = 'vitest',
-  Jest = 'jest',
-  Pytest = 'pytest',
-  GoTest = 'gotest',
-  CargoTest = 'cargotest'
-}
-
-interface FrameworkAdapter {
-  runTargeted(pattern: string): Promise<TestResults>
-  runAll(): Promise<TestResults>
-  parseCoverage(output: string): Promise<CoverageReport>
-  getTestFilePattern(): string
-  getTestFileExtension(): string
-}
-```
-
-**Framework-specific adapters:**
-
-**PytestAdapter** (`packages/tm-core/src/services/test-adapters/pytest-adapter.ts`):
-```typescript
-class PytestAdapter implements FrameworkAdapter {
-  async runTargeted(pattern: string): Promise<TestResults> {
-    const output = await exec(`pytest ${pattern} --json-report`)
-    return this.parseResults(output)
-  }
-
-  async runAll(): Promise<TestResults> {
-    const output = await exec('pytest --cov --json-report')
-    return this.parseResults(output)
-  }
-
-  parseCoverage(output: string): Promise<CoverageReport> {
-    // Parse pytest-cov XML output
-  }
-
-  getTestFilePattern(): string {
-    return '**/test_*.py'
-  }
-
-  getTestFileExtension(): string {
-    return '.py'
-  }
-}
-```
-
-**GoTestAdapter** (`packages/tm-core/src/services/test-adapters/gotest-adapter.ts`):
-```typescript
-class GoTestAdapter implements FrameworkAdapter {
-  async runTargeted(pattern: string): Promise<TestResults> {
-    const output = await exec(`go test ${pattern} -json`)
-    return this.parseResults(output)
-  }
-
-  async runAll(): Promise<TestResults> {
-    const output = await exec('go test ./... -coverprofile=coverage.out -json')
-    return this.parseResults(output)
-  }
-
-  parseCoverage(output: string): Promise<CoverageReport> {
-    // Parse go test coverage output
-  }
-
-  getTestFilePattern(): string {
-    return '**/*_test.go'
-  }
-
-  getTestFileExtension(): string {
-    return '_test.go'
-  }
-}
-```
-
-**Detection Logic:**
-```typescript
-async function detectFramework(): Promise<Framework> {
-  // Check for package.json
-  if (await exists('package.json')) {
-    const pkg = await readJSON('package.json')
-    if (pkg.devDependencies?.vitest) return Framework.Vitest
-    if (pkg.devDependencies?.jest) return Framework.Jest
-  }
-
-  // Check for Python files
-  if (await exists('pytest.ini') || await exists('setup.py')) {
-    return Framework.Pytest
-  }
-
-  // Check for Go files
-  if (await exists('go.mod')) {
-    return Framework.GoTest
-  }
-
-  // Check for Rust files
-  if (await exists('Cargo.toml')) {
-    return Framework.CargoTest
-  }
-
-  throw new Error('Could not detect test framework')
-}
-```
-
-### 2. Enhanced Safety Guardrails
-
-**Diff Preview Mode:**
-```bash
-$ tm autopilot 42 --preview-diffs
-
-[2/3] Subtask 42.2: Add collection endpoint
-
-  RED   ✓ Tests created: src/api/__tests__/metrics.test.js
-
-  GREEN Implementing code...
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Proposed changes (src/api/metrics.js):
-
-  + import { MetricsSchema } from '../models/schema.js'
-  +
-  + export async function createMetric(data) {
-  +   const validated = MetricsSchema.parse(data)
-  +   const result = await db.metrics.create(validated)
-  +   return result
-  + }
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Apply these changes? [Y/n/e(dit)/s(kip)]
-  Y - Apply and continue
-  n - Reject and retry GREEN phase
-  e - Open in editor for manual changes
-  s - Skip this subtask
-```
-
-**Minimal Change Enforcement:**
-
-Add to system prompt:
-```markdown
-CRITICAL: Make MINIMAL changes to pass the failing tests.
-- Only modify files directly related to the subtask
-- Do not refactor existing code unless absolutely necessary
-- Do not add features beyond the acceptance criteria
-- Keep changes under 50 lines per file when possible
-- Prefer composition over modification
-```
-
-**Change Size Warnings:**
-```bash
-⚠️  Large change detected:
-  Files modified: 5
-  Lines changed: +234, -12
-
-This subtask was expected to be small (~50 lines).
-Consider:
-  - Breaking into smaller subtasks
-  - Reviewing acceptance criteria
-  - Checking for unintended changes
-
-Continue anyway? [y/N]
-```
-
-### 3. TUI Interface with tmux
-
-**Layout:**
-```
-┌──────────────────────────────────┬─────────────────────────────────┐
-│ Task Navigator (left)            │ Executor Terminal (right)       │
-│                                  │                                 │
-│ Project: my-app                  │ $ tm autopilot --executor-mode  │
-│ Branch: analytics/task-42        │ > Running subtask 42.2 GREEN... │
-│ Tag: analytics                   │ > Implementing endpoint...      │
-│                                  │ > Tests: 3 passed, 0 failed     │
-│ Tasks:                           │ > Ready to commit               │
-│ → 42 [in-progress] User metrics  │                                 │
-│   → 42.1 [done] Schema           │ [Live output from executor]     │
-│   → 42.2 [active] Endpoint ◀     │                                 │
-│   → 42.3 [pending] Dashboard     │                                 │
-│                                  │                                 │
-│ [s] start  [p] pause  [q] quit   │                                 │
-└──────────────────────────────────┴─────────────────────────────────┘
-```
-
-**Implementation:**
-
-**TUI Navigator** (`apps/cli/src/ui/tui/navigator.ts`):
-```typescript
-import blessed from 'blessed'
-
-class AutopilotTUI {
-  private screen: blessed.Widgets.Screen
-  private taskList: blessed.Widgets.ListElement
-  private statusBox: blessed.Widgets.BoxElement
-  private executorPane: string  // tmux pane ID
-
-  async start(taskId?: string) {
-    // Create blessed screen
-    this.screen = blessed.screen()
-
-    // Create task list widget
-    this.taskList = blessed.list({
-      label: 'Tasks',
-      keys: true,
-      vi: true,
-      style: { selected: { bg: 'blue' } }
-    })
-
-    // Spawn tmux pane for executor
-    this.executorPane = await this.spawnExecutorPane()
-
-    // Watch state file for updates
-    this.watchStateFile()
-
-    // Handle keybindings
-    this.setupKeybindings()
-  }
-
-  private async spawnExecutorPane(): Promise<string> {
-    const paneId = await exec('tmux split-window -h -P -F "#{pane_id}"')
-    await exec(`tmux send-keys -t ${paneId} "tm autopilot --executor-mode" Enter`)
-    return paneId.trim()
-  }
-
-  private watchStateFile() {
-    watch('.taskmaster/state/current-run.json', (event, filename) => {
-      this.updateDisplay()
-    })
-  }
-
-  private setupKeybindings() {
-    this.screen.key(['s'], () => this.startTask())
-    this.screen.key(['p'], () => this.pauseTask())
-    this.screen.key(['q'], () => this.quit())
-    this.screen.key(['up', 'down'], () => this.navigateTasks())
-  }
-}
-```
-
-**Executor Mode:**
-```bash
-$ tm autopilot 42 --executor-mode
-
-# Runs in executor pane, writes state to shared file
-# Left pane reads state file and updates display
-```
-
-**State File** (`.taskmaster/state/current-run.json`):
-```json
-{
-  "runId": "2025-01-15-142033",
-  "taskId": "42",
-  "status": "running",
-  "currentPhase": "green",
-  "currentSubtask": "42.2",
-  "lastOutput": "Implementing endpoint...",
-  "testsStatus": {
-    "passed": 3,
-    "failed": 0
-  }
-}
-```
-
-### 4. Extension API for IDE Integration
-
-**State-based API:**
-
-Expose run state via JSON files that IDEs can read:
-- `.taskmaster/state/current-run.json` - live run state
-- `.taskmaster/reports/runs/<runId>/manifest.json` - run metadata
-- `.taskmaster/reports/runs/<runId>/log.jsonl` - event stream
-
-**WebSocket API (optional):**
-```typescript
-// packages/tm-core/src/services/autopilot-server.ts
-class AutopilotServer {
-  private wss: WebSocketServer
-
-  start(port: number = 7890) {
-    this.wss = new WebSocketServer({ port })
-
-    this.wss.on('connection', (ws) => {
-      // Send current state
-      ws.send(JSON.stringify(this.getCurrentState()))
-
-      // Stream events
-      this.orchestrator.on('*', (event) => {
-        ws.send(JSON.stringify(event))
-      })
-    })
-  }
-}
-```
-
-**Usage from IDE extension:**
-```typescript
-// VS Code extension example
-const ws = new WebSocket('ws://localhost:7890')
-
-ws.on('message', (data) => {
-  const event = JSON.parse(data)
-
-  if (event.type === 'subtask:complete') {
-    vscode.window.showInformationMessage(
-      `Subtask ${event.subtaskId} completed`
-    )
-  }
-})
-```
-
-### 5. Parallel Subtask Execution (Experimental)
-
-**Dependency Analysis:**
-```typescript
-class SubtaskScheduler {
-  async buildDependencyGraph(subtasks: Subtask[]): Promise<DAG> {
-    const graph = new DAG()
-
-    for (const subtask of subtasks) {
-      graph.addNode(subtask.id)
-
-      for (const depId of subtask.dependencies) {
-        graph.addEdge(depId, subtask.id)
-      }
-    }
-
-    return graph
-  }
-
-  async getParallelBatches(graph: DAG): Promise<Subtask[][]> {
-    const batches: Subtask[][] = []
-    const completed = new Set<string>()
-
-    while (completed.size < graph.size()) {
-      const ready = graph.nodes.filter(node =>
-        !completed.has(node.id) &&
-        node.dependencies.every(dep => completed.has(dep))
-      )
-
-      batches.push(ready)
-      ready.forEach(node => completed.add(node.id))
-    }
-
-    return batches
-  }
-}
-```
-
-**Parallel Execution:**
-```bash
-$ tm autopilot 42 --parallel
-
-[Batch 1] Running 2 subtasks in parallel:
-  → 42.1: Add metrics schema
-  → 42.4: Add API documentation
-
-  42.1 RED   ✓ Tests created
-  42.4 RED   ✓ Tests created
-
-  42.1 GREEN ✓ Implementation complete
-  42.4 GREEN ✓ Implementation complete
-
-  42.1 COMMIT ✓ Committed: a1b2c3d
-  42.4 COMMIT ✓ Committed: e5f6g7h
-
-[Batch 2] Running 2 subtasks in parallel (depend on 42.1):
-  → 42.2: Add collection endpoint
-  → 42.3: Add dashboard widget
-  ...
-```
-
-**Conflict Detection:**
-```typescript
-async function detectConflicts(subtasks: Subtask[]): Promise<Conflict[]> {
-  const conflicts: Conflict[] = []
-
-  for (let i = 0; i < subtasks.length; i++) {
-    for (let j = i + 1; j < subtasks.length; j++) {
-      const filesA = await predictAffectedFiles(subtasks[i])
-      const filesB = await predictAffectedFiles(subtasks[j])
-
-      const overlap = filesA.filter(f => filesB.includes(f))
-
-      if (overlap.length > 0) {
-        conflicts.push({
-          subtasks: [subtasks[i].id, subtasks[j].id],
-          files: overlap
-        })
-      }
-    }
-  }
-
-  return conflicts
-}
-```
-
-### 6. Advanced Configuration
-
-**Add to `.taskmaster/config.json`:**
-```json
-{
-  "autopilot": {
-    "safety": {
-      "previewDiffs": false,
-      "maxChangeLinesPerFile": 100,
-      "warnOnLargeChanges": true,
-      "requireConfirmOnLargeChanges": true
-    },
-    "parallel": {
-      "enabled": false,
-      "maxConcurrent": 3,
-      "detectConflicts": true
-    },
-    "tui": {
-      "enabled": false,
-      "tmuxSession": "taskmaster-autopilot"
-    },
-    "api": {
-      "enabled": false,
-      "port": 7890,
-      "allowRemote": false
-    }
-  },
-  "test": {
-    "frameworks": {
-      "python": {
-        "runner": "pytest",
-        "coverageCommand": "pytest --cov",
-        "testPattern": "**/test_*.py"
-      },
-      "go": {
-        "runner": "go test",
-        "coverageCommand": "go test ./... -coverprofile=coverage.out",
-        "testPattern": "**/*_test.go"
-      }
-    }
-  }
-}
-```
-
-## CLI Updates
-
-**New commands:**
-```bash
-tm autopilot <taskId> --tui              # Launch TUI interface
-tm autopilot <taskId> --parallel         # Enable parallel execution
-tm autopilot <taskId> --preview-diffs    # Show diffs before applying
-tm autopilot <taskId> --executor-mode    # Run as executor pane
-tm autopilot-server start                # Start WebSocket API
-```
-
-## Success Criteria
-- Supports Python projects with pytest
-- Supports Go projects with go test
-- Diff preview prevents unwanted changes
-- TUI provides better visibility for long-running tasks
-- IDE extensions can integrate via state files or WebSocket
-- Parallel execution reduces total time for independent subtasks
-
-## Out of Scope
-- Full Electron/web GUI
-- AI executor selection UI (defer to Phase 4)
-- Multi-repository support
-- Remote execution on cloud runners
-
-## Testing Strategy
-- Test with Python project (pytest)
-- Test with Go project (go test)
-- Test diff preview UI with mock changes
-- Test parallel execution with independent subtasks
-- Test conflict detection with overlapping file changes
-- Test TUI with mock tmux environment
-
-## Dependencies
-- Phase 2 completed (PR + resumability)
-- tmux installed (for TUI)
-- blessed or ink library (for TUI rendering)
-
-## Estimated Effort
-3-4 weeks
-
-## Risks & Mitigations
-- **Risk:** Parallel execution causes git conflicts
-  - **Mitigation:** Conservative conflict detection, sequential fallback
-
-- **Risk:** TUI adds complexity and maintenance burden
-  - **Mitigation:** Keep TUI optional, state-based design allows alternatives
-
-- **Risk:** Framework adapters hard to maintain across versions
-  - **Mitigation:** Abstract common parsing logic, document adapter interface
-
-- **Risk:** Diff preview slows down workflow
-  - **Mitigation:** Make optional, use --preview-diffs flag only when needed
-
-## Validation
-Test with:
-- Python project with pytest and pytest-cov
-- Go project with go test
-- Large changes requiring confirmation
-- Parallel execution with 3+ independent subtasks
-- TUI with task selection and live status updates
-- VS Code extension reading state files

.taskmaster/reports/task-complexity-report_autonomous-tdd-git-workflow.json

@@ -1,197 +0,0 @@
-{
-	"meta": {
-		"generatedAt": "2025-10-07T09:46:06.248Z",
-		"tasksAnalyzed": 23,
-		"totalTasks": 23,
-		"analysisCount": 23,
-		"thresholdScore": 5,
-		"projectName": "Taskmaster",
-		"usedResearch": false
-	},
-	"complexityAnalysis": [
-		{
-			"taskId": 31,
-			"taskTitle": "Create WorkflowOrchestrator service foundation",
-			"complexityScore": 7,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Break down the WorkflowOrchestrator foundation into its core architectural components: phase management system, event emitter infrastructure, state management interfaces, service integration, and lifecycle control methods. Each subtask should focus on a specific architectural concern with clear interfaces and testable units.",
-			"reasoning": "This is a foundational service requiring state machine implementation, event-driven architecture, and integration with existing services. The complexity is high due to the need for robust phase management, error handling, and service orchestration patterns."
-		},
-		{
-			"taskId": 32,
-			"taskTitle": "Implement GitAdapter for repository operations",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Decompose the GitAdapter implementation into: TypeScript wrapper creation around existing git-utils.js, core git operation methods with comprehensive error handling, branch naming pattern system with token replacement, and confirmation gates for destructive operations. Focus on type safety and existing code integration.",
-			"reasoning": "Moderate-high complexity due to TypeScript integration over existing JavaScript utilities, branch pattern implementation, and safety mechanisms. The existing git-utils.js provides a solid foundation, reducing complexity."
-		},
-		{
-			"taskId": 33,
-			"taskTitle": "Create TestRunnerAdapter for framework detection and execution",
-			"complexityScore": 8,
-			"recommendedSubtasks": 6,
-			"expansionPrompt": "Break down TestRunnerAdapter into framework detection logic, test execution engine with process management, Jest-specific result parsing, Vitest-specific result parsing, unified result interfaces, and final integration. Each framework parser should be separate to handle their unique output formats.",
-			"reasoning": "High complexity due to multiple framework support (Jest, Vitest), child process management, result parsing from different formats, coverage reporting, and timeout handling. Each framework has unique output formats requiring specialized parsers."
-		},
-		{
-			"taskId": 34,
-			"taskTitle": "Implement autopilot CLI command structure",
-			"complexityScore": 5,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Structure the autopilot command into: basic command setup with Commander.js integration, comprehensive flag handling and validation system, preflight check validation with environment validation, and WorkflowOrchestrator integration with dry-run execution planning. Follow existing CLI patterns from the codebase.",
-			"reasoning": "Moderate complexity involving CLI structure, flag handling, and integration with WorkflowOrchestrator. The existing CLI patterns and Commander.js usage in the codebase provide good guidance, reducing implementation complexity."
-		},
-		{
-			"taskId": 35,
-			"taskTitle": "Integrate surgical test generator with WorkflowOrchestrator",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Decompose the test generation integration into: TaskExecutionService enhancement for test generation mode, TestGenerationService creation using executor framework, prompt composition system for rule integration, and framework-specific test pattern support. Leverage existing executor patterns from the codebase.",
-			"reasoning": "Moderate-high complexity due to integration with existing services, prompt composition system, and framework-specific test generation. The existing executor framework and TaskExecutionService provide good integration points."
-		},
-		{
-			"taskId": 36,
-			"taskTitle": "Implement subtask TDD loop execution",
-			"complexityScore": 9,
-			"recommendedSubtasks": 7,
-			"expansionPrompt": "Break down the TDD loop into: SubtaskExecutor class architecture, RED phase test generation, GREEN phase code generation, COMMIT phase with conventional commits, retry mechanism for GREEN phase, timeout and backoff policies, and TaskService integration. Each phase should be independently testable.",
-			"reasoning": "Very high complexity due to implementing the complete TDD red-green-commit cycle with AI integration, retry logic, timeout handling, and git operations. This is the core autonomous workflow requiring robust error handling and state management."
-		},
-		{
-			"taskId": 37,
-			"taskTitle": "Add configuration schema for autopilot settings",
-			"complexityScore": 4,
-			"recommendedSubtasks": 3,
-			"expansionPrompt": "Expand configuration support into: extending configuration interfaces with autopilot settings, updating ConfigManager validation logic, and implementing default configuration values. Build on existing configuration patterns and maintain backward compatibility.",
-			"reasoning": "Low-moderate complexity involving schema extension and validation logic. The existing configuration system provides clear patterns to follow, making this primarily an extension task rather than new architecture."
-		},
-		{
-			"taskId": 38,
-			"taskTitle": "Implement run state persistence and logging",
-			"complexityScore": 6,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Structure run state management into: RunStateManager service class creation, run directory structure and manifest creation, JSONL event logging system, test result and commit tracking storage, and state checkpointing with resume functionality. Focus on data integrity and structured logging.",
-			"reasoning": "Moderate-high complexity due to file system operations, structured logging, state serialization, and resume functionality. Requires careful design of data formats and error handling for persistence operations."
-		},
-		{
-			"taskId": 39,
-			"taskTitle": "Add GitHub PR creation with run reports",
-			"complexityScore": 5,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Decompose PR creation into: PRAdapter service foundation with interfaces, GitHub CLI integration and command execution, PR body generation from run data and test results, and custom PR template system with configuration support. Leverage existing git-utils.js patterns for CLI integration.",
-			"reasoning": "Moderate complexity involving GitHub CLI integration, report generation, and template systems. The existing git-utils.js provides patterns for CLI tool integration, reducing implementation complexity."
-		},
-		{
-			"taskId": 40,
-			"taskTitle": "Implement task dependency resolution for subtask ordering",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Break down dependency resolution into: dependency resolution algorithm with cycle detection, topological sorting for subtask ordering, task eligibility checking system, and TaskService integration. Implement graph algorithms for dependency management with proper error handling.",
-			"reasoning": "Moderate-high complexity due to graph algorithm implementation, cycle detection, and integration with existing task management. Requires careful design of dependency resolution logic and edge case handling."
-		},
-		{
-			"taskId": 41,
-			"taskTitle": "Create resume functionality for interrupted runs",
-			"complexityScore": 7,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Structure resume functionality into: checkpoint creation in RunStateManager, state restoration logic with validation, state validation for safe resume operations, CLI flag implementation for resume command, and partial phase resume functionality. Focus on data integrity and workflow consistency.",
-			"reasoning": "High complexity due to state serialization/deserialization, workflow restoration, validation logic, and CLI integration. Requires robust error handling and state consistency checks for reliable resume operations."
-		},
-		{
-			"taskId": 42,
-			"taskTitle": "Add coverage threshold enforcement",
-			"complexityScore": 5,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Decompose coverage enforcement into: coverage report parsing from Jest/Vitest, configurable threshold validation logic, coverage gates integration in workflow phases, and detailed coverage failure reporting system. Build on existing TestRunnerAdapter patterns.",
-			"reasoning": "Moderate complexity involving coverage report parsing, validation logic, and workflow integration. The existing TestRunnerAdapter provides good foundation for extending coverage capabilities."
-		},
-		{
-			"taskId": 43,
-			"taskTitle": "Implement tmux-based TUI navigator",
-			"complexityScore": 8,
-			"recommendedSubtasks": 6,
-			"expansionPrompt": "Break down TUI implementation into: framework selection and basic structure setup, left pane interface layout with status indicators, tmux integration and terminal coordination, navigation system with keybindings, real-time status updates system, and comprehensive event handling with UX polish. Each component should be independently testable.",
-			"reasoning": "High complexity due to terminal UI framework integration, tmux session management, real-time updates, keyboard event handling, and terminal interface design. Requires expertise in terminal UI libraries and tmux integration."
-		},
-		{
-			"taskId": 44,
-			"taskTitle": "Add prompt composition system for context-aware test generation",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Structure prompt composition into: PromptComposer service foundation, template processing engine with token replacement, rule loading system with precedence handling, and context injection with phase-specific prompt generation. Focus on flexible template system and rule management.",
-			"reasoning": "Moderate-high complexity due to template processing, rule precedence systems, and context injection logic. Requires careful design of template syntax and rule loading mechanisms."
-		},
-		{
-			"taskId": 45,
-			"taskTitle": "Implement tag-branch mapping and automatic tag switching",
-			"complexityScore": 5,
-			"recommendedSubtasks": 3,
-			"expansionPrompt": "Decompose tag-branch mapping into: GitAdapter enhancement with branch-to-tag extraction logic, automatic tag switching workflow integration, and branch-to-tag mapping persistence with validation. Build on existing git-utils.js and tag management functionality.",
-			"reasoning": "Moderate complexity involving pattern matching, tag management integration, and workflow automation. The existing git-utils.js and tag management systems provide good foundation for implementation."
-		},
-		{
-			"taskId": 46,
-			"taskTitle": "Add comprehensive error handling and recovery",
-			"complexityScore": 7,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Structure error handling into: error classification system with specific error types, recovery suggestion engine with actionable recommendations, error context management and preservation, force flag implementation with selective bypass, and logging/reporting system integration. Focus on actionable error messages and automated recovery where possible.",
-			"reasoning": "High complexity due to comprehensive error taxonomy, recovery automation, context preservation, and integration across all workflow components. Requires deep understanding of failure modes and recovery strategies."
-		},
-		{
-			"taskId": 47,
-			"taskTitle": "Implement conventional commit message generation",
-			"complexityScore": 4,
-			"recommendedSubtasks": 3,
-			"expansionPrompt": "Break down commit message generation into: template system creation with variable substitution, commit type auto-detection based on task content and file changes, and validation with GitAdapter integration. Follow conventional commit standards and integrate with existing git operations.",
-			"reasoning": "Low-moderate complexity involving template processing, pattern matching for commit type detection, and validation logic. Well-defined conventional commit standards provide clear implementation guidance."
-		},
-		{
-			"taskId": 48,
-			"taskTitle": "Add multi-framework test execution support",
-			"complexityScore": 7,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Expand test framework support into: framework detection system for multiple languages, common adapter interface design, Python pytest adapter implementation, Go and Rust adapter implementations, and integration with existing TestRunnerAdapter. Each language adapter should follow the unified interface pattern.",
-			"reasoning": "High complexity due to multi-language support, framework detection across different ecosystems, and adapter pattern implementation. Each language has unique testing conventions and output formats."
-		},
-		{
-			"taskId": 49,
-			"taskTitle": "Implement workflow event streaming for real-time monitoring",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Structure event streaming into: WorkflowOrchestrator EventEmitter enhancement, structured event format with metadata, event persistence to run logs, and optional WebSocket streaming for external monitoring. Focus on event consistency and real-time delivery.",
-			"reasoning": "Moderate-high complexity due to event-driven architecture, structured event formats, persistence integration, and WebSocket implementation. Requires careful design of event schemas and delivery mechanisms."
-		},
-		{
-			"taskId": 50,
-			"taskTitle": "Add intelligent test targeting for faster feedback",
-			"complexityScore": 7,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Decompose test targeting into: file change detection system, test dependency analysis engine, framework-specific targeting adapters, test impact calculation algorithm, and fallback integration with TestRunnerAdapter. Focus on accuracy and performance optimization.",
-			"reasoning": "High complexity due to dependency analysis, impact calculation algorithms, framework-specific targeting, and integration with existing test execution. Requires sophisticated analysis of code relationships and test dependencies."
-		},
-		{
-			"taskId": 51,
-			"taskTitle": "Implement dry-run visualization with execution timeline",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Structure dry-run visualization into: timeline calculation engine with duration estimates, estimation algorithms based on task complexity, ASCII art progress visualization with formatting, and resource validation with preflight checks. Focus on accurate planning and clear visual presentation.",
-			"reasoning": "Moderate-high complexity due to timeline calculation, estimation algorithms, ASCII visualization, and resource validation. Requires understanding of workflow timing and visual formatting for terminal output."
-		},
-		{
-			"taskId": 52,
-			"taskTitle": "Add autopilot workflow integration tests",
-			"complexityScore": 8,
-			"recommendedSubtasks": 6,
-			"expansionPrompt": "Structure integration testing into: isolated test environment infrastructure, mock integrations and service stubs, end-to-end workflow test scenarios, performance benchmarking and resource monitoring, test isolation and parallelization strategies, and comprehensive result validation and reporting. Focus on realistic test scenarios and reliable automation.",
-			"reasoning": "High complexity due to end-to-end testing requirements, mock service integration, performance testing, isolation mechanisms, and comprehensive validation. Requires sophisticated test infrastructure and scenario design."
-		},
-		{
-			"taskId": 53,
-			"taskTitle": "Finalize autopilot documentation and examples",
-			"complexityScore": 3,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Structure documentation into: comprehensive autopilot documentation covering setup and usage, example PRD files and templates for different project types, troubleshooting guide for common issues and solutions, and demo materials with workflow visualization. Focus on clarity and practical examples.",
-			"reasoning": "Low complexity involving documentation writing, example creation, and demo material production. The main challenge is ensuring accuracy and completeness rather than technical implementation."
-		}
-	]
-}

.taskmaster/reports/task-complexity-report_tdd-phase-1-core-rails.json

@@ -1,93 +0,0 @@
-{
-	"meta": {
-		"generatedAt": "2025-10-09T12:47:27.960Z",
-		"tasksAnalyzed": 10,
-		"totalTasks": 10,
-		"analysisCount": 10,
-		"thresholdScore": 5,
-		"projectName": "Taskmaster",
-		"usedResearch": false
-	},
-	"complexityAnalysis": [
-		{
-			"taskId": 1,
-			"taskTitle": "Design and Implement Global Storage System",
-			"complexityScore": 7,
-			"recommendedSubtasks": 6,
-			"expansionPrompt": "Break down the global storage system implementation into: 1) Path normalization utilities with cross-platform support, 2) Run ID generation and validation, 3) Manifest.json structure and management, 4) Activity.jsonl append-only logging, 5) State.json mutable checkpoint handling, and 6) Directory structure creation and cleanup. Focus on robust error handling, atomic operations, and isolation between different runs.",
-			"reasoning": "Complex system requiring cross-platform path handling, multiple file formats (JSON/JSONL), atomic operations, and state management. The existing codebase shows sophisticated file operations infrastructure but this extends beyond current patterns. Implementation involves filesystem operations, concurrency concerns, and data integrity."
-		},
-		{
-			"taskId": 2,
-			"taskTitle": "Build GitAdapter with Safety Checks",
-			"complexityScore": 8,
-			"recommendedSubtasks": 7,
-			"expansionPrompt": "Decompose GitAdapter into: 1) Git repository detection and validation, 2) Working tree status checking with detailed reporting, 3) Branch operations (create, checkout, list) with safety guards, 4) Commit operations with metadata embedding, 5) Default branch detection and protection logic, 6) Push operations with conflict handling, and 7) Branch name generation from patterns. Emphasize safety checks, confirmation gates, and comprehensive error messages.",
-			"reasoning": "High complexity due to git operations safety requirements, multiple git commands integration, error handling for various git states, and safety mechanisms. The PRD emphasizes never allowing commits on default branch and requiring clean working tree - critical safety features that need robust implementation."
-		},
-		{
-			"taskId": 3,
-			"taskTitle": "Implement Test Result Validator",
-			"complexityScore": 5,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Split test validation into: 1) Input validation and schema definition for test results, 2) RED phase validation logic (ensuring failures exist), 3) GREEN phase validation logic (ensuring all tests pass), and 4) Coverage threshold validation with configurable limits. Include comprehensive validation messages and suggestions for common failure scenarios.",
-			"reasoning": "Moderate complexity focused on business logic validation. The validator is framework-agnostic (only validates reported numbers), has clear validation rules, and well-defined input/output. The existing codebase shows validation patterns that can be leveraged."
-		},
-		{
-			"taskId": 4,
-			"taskTitle": "Develop WorkflowOrchestrator State Machine",
-			"complexityScore": 9,
-			"recommendedSubtasks": 8,
-			"expansionPrompt": "Structure the orchestrator into: 1) State machine definition and transitions (Preflight → BranchSetup → SubtaskLoop → Finalize), 2) Event emission system with comprehensive event types, 3) State persistence and recovery mechanisms, 4) Phase coordination and validation, 5) Subtask iteration and progress tracking, 6) Error handling and recovery strategies, 7) Resume functionality from checkpoints, and 8) Integration points for Git, Test, and other adapters.",
-			"reasoning": "Very high complexity as the central coordination component. Must orchestrate multiple adapters, handle state transitions, event emission, persistence, and recovery. The state machine needs to be robust, resumable, and coordinate all other components. Critical for the entire workflow's reliability."
-		},
-		{
-			"taskId": 5,
-			"taskTitle": "Create Enhanced Commit Message Generator",
-			"complexityScore": 4,
-			"recommendedSubtasks": 3,
-			"expansionPrompt": "Organize commit message generation into: 1) Template parsing and variable substitution with configurable templates, 2) Scope detection from changed files with intelligent categorization, and 3) Metadata embedding (task context, test results, coverage) with conventional commits compliance. Ensure messages are parseable and contain all required task metadata.",
-			"reasoning": "Relatively straightforward text processing and template system. The conventional commits format is well-defined, and the metadata requirements are clear. The existing package.json shows commander dependency for CLI patterns that can be leveraged."
-		},
-		{
-			"taskId": 6,
-			"taskTitle": "Implement Subtask TDD Loop",
-			"complexityScore": 8,
-			"recommendedSubtasks": 6,
-			"expansionPrompt": "Break down the TDD loop into: 1) RED phase orchestration with test generation coordination, 2) GREEN phase orchestration with implementation guidance, 3) COMMIT phase with file staging and commit creation, 4) Attempt tracking and maximum retry logic, 5) Phase transition validation and state updates, and 6) Activity logging for all phase transitions. Focus on robust state management and clear error recovery paths.",
-			"reasoning": "High complexity due to coordinating multiple phases, state transitions, retry logic, and integration with multiple adapters (Git, Test, State). This is the core workflow execution engine requiring careful orchestration and error handling."
-		},
-		{
-			"taskId": 7,
-			"taskTitle": "Build CLI Commands for AI Agent Orchestration",
-			"complexityScore": 6,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Structure CLI commands into: 1) Command registration and argument parsing setup, 2) `start` and `resume` commands with initialization logic, 3) `next` and `status` commands with JSON output formatting, 4) `complete` command with result validation integration, and 5) `commit` and `abort` commands with git operation coordination. Ensure consistent JSON output for machine parsing and comprehensive error handling.",
-			"reasoning": "Moderate complexity leveraging existing CLI infrastructure. The codebase shows commander usage patterns and CLI structure. Main complexity is in JSON output formatting, argument validation, and integration with the orchestrator component."
-		},
-		{
-			"taskId": 8,
-			"taskTitle": "Develop MCP Tools for AI Agent Integration",
-			"complexityScore": 6,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Organize MCP tools into: 1) Tool schema definition and parameter validation, 2) `autopilot_start` and `autopilot_resume` tool implementation, 3) `autopilot_next` and `autopilot_status` tools with context provision, 4) `autopilot_complete_phase` tool with validation integration, and 5) `autopilot_commit` tool with git operations. Ensure parity with CLI functionality and proper error handling.",
-			"reasoning": "Moderate complexity building on existing MCP infrastructure. The codebase shows extensive MCP tooling patterns. Main work is adapting CLI functionality to MCP interface patterns and ensuring consistent behavior between CLI and MCP interfaces."
-		},
-		{
-			"taskId": 9,
-			"taskTitle": "Write AI Agent Integration Documentation and Templates",
-			"complexityScore": 2,
-			"recommendedSubtasks": 2,
-			"expansionPrompt": "Structure documentation into: 1) Comprehensive workflow documentation with step-by-step examples, command usage, and integration patterns, and 2) Template creation for CLAUDE.md integration, example prompts, and troubleshooting guides. Focus on clear examples and practical integration guidance.",
-			"reasoning": "Low complexity documentation task. Requires understanding of the implemented system but primarily involves writing clear instructions and examples. The existing codebase shows good documentation patterns that can be followed."
-		},
-		{
-			"taskId": 10,
-			"taskTitle": "Implement Configuration System and Project Hygiene",
-			"complexityScore": 5,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Structure configuration into: 1) Configuration schema definition with comprehensive validation using ajv, 2) Default configuration setup and loading mechanisms, 3) Gitignore management and project directory hygiene rules, and 4) Configuration validation and error reporting. Ensure configurations are validated on startup and provide clear error messages for invalid settings.",
-			"reasoning": "Moderate complexity involving schema validation, file operations, and configuration management. The package.json shows ajv dependency is available. Configuration systems require careful validation and user-friendly error reporting, but follow established patterns."
-		}
-	]
-}

.taskmaster/reports/task-complexity-report_tdd-workflow-phase-0.json

@@ -1,93 +0,0 @@
-{
-	"meta": {
-		"generatedAt": "2025-10-07T14:16:40.283Z",
-		"tasksAnalyzed": 10,
-		"totalTasks": 10,
-		"analysisCount": 10,
-		"thresholdScore": 5,
-		"projectName": "Taskmaster",
-		"usedResearch": false
-	},
-	"complexityAnalysis": [
-		{
-			"taskId": 1,
-			"taskTitle": "Create autopilot command CLI skeleton",
-			"complexityScore": 4,
-			"recommendedSubtasks": 3,
-			"expansionPrompt": "Break down the autopilot command creation into: 1) Create AutopilotCommand class extending Commander.Command with proper argument parsing and options, 2) Implement command structure with help text and validation following existing patterns, 3) Add basic registration method and placeholder action handler",
-			"reasoning": "Medium complexity due to following established patterns in the codebase. The command-registry.ts and start.command.ts provide clear templates for implementation. Main complexity is argument parsing and option validation."
-		},
-		{
-			"taskId": 2,
-			"taskTitle": "Implement preflight detection system",
-			"complexityScore": 7,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Create PreflightChecker with these subtasks: 1) Package.json test script detection and validation, 2) Git working tree status checking using system commands, 3) Tool availability validation (git, gh, node/npm), 4) Default branch detection via git commands, 5) Structured result reporting with success/failure indicators and error messages",
-			"reasoning": "High complexity due to system integration requirements. Needs to interact with multiple external tools (git, npm, gh), parse various file formats, and handle different system configurations. Error handling for missing tools adds complexity."
-		},
-		{
-			"taskId": 3,
-			"taskTitle": "Implement task loading and validation",
-			"complexityScore": 5,
-			"recommendedSubtasks": 3,
-			"expansionPrompt": "Implement task loading: 1) Use existing TaskService from @tm/core to load tasks by ID with proper error handling, 2) Validate task structure including subtask existence and dependency validation, 3) Provide user-friendly error messages for missing tasks or need to expand subtasks first",
-			"reasoning": "Medium-high complexity. While leveraging existing TaskService reduces implementation effort, the validation logic for subtasks and dependencies requires careful handling of edge cases. Task structure validation adds complexity."
-		},
-		{
-			"taskId": 4,
-			"taskTitle": "Create execution plan display logic",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Build ExecutionPlanDisplay: 1) Create display formatter using boxen and chalk for consistent CLI styling, 2) Format preflight check results with color-coded status indicators, 3) Display subtask execution order with RED/GREEN/COMMIT phase visualization, 4) Show branch/tag info and finalization steps with duration estimates",
-			"reasoning": "Moderate-high complexity due to complex formatting requirements and dependency on multiple other components. The display needs to coordinate information from preflight, task validation, and execution planning. CLI styling consistency adds complexity."
-		},
-		{
-			"taskId": 5,
-			"taskTitle": "Implement branch and tag planning",
-			"complexityScore": 3,
-			"recommendedSubtasks": 2,
-			"expansionPrompt": "Create BranchPlanner: 1) Implement branch name generation using pattern <tag>/task-<id>-<slug> with kebab-case conversion and special character handling, 2) Add TaskMaster config integration to determine active tag and handle existing branch conflicts",
-			"reasoning": "Low-medium complexity. String manipulation and naming convention implementation is straightforward. The main complexity is handling edge cases with special characters and existing branch conflicts."
-		},
-		{
-			"taskId": 6,
-			"taskTitle": "Create subtask execution order calculation",
-			"complexityScore": 8,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Implement dependency resolution: 1) Build dependency graph from subtask data with proper parsing, 2) Implement topological sort algorithm for execution order, 3) Add circular dependency detection with clear error reporting, 4) Create parallel execution grouping for independent subtasks",
-			"reasoning": "High complexity due to graph algorithms and dependency resolution. Topological sorting, circular dependency detection, and parallel grouping require algorithmic sophistication. Edge cases in dependency chains add significant complexity."
-		},
-		{
-			"taskId": 7,
-			"taskTitle": "Implement TDD phase planning for subtasks",
-			"complexityScore": 6,
-			"recommendedSubtasks": 4,
-			"expansionPrompt": "Create TDDPhasePlanner: 1) Implement test file path detection for common project structures (src/, tests/, __tests__), 2) Parse implementation files from subtask details and descriptions, 3) Generate conventional commit messages for RED/GREEN/COMMIT phases, 4) Add implementation complexity estimation based on subtask content",
-			"reasoning": "Moderate-high complexity due to project structure detection and file path inference. Conventional commit message generation and complexity estimation require understanding of different project layouts and parsing subtask content effectively."
-		},
-		{
-			"taskId": 8,
-			"taskTitle": "Add finalization steps planning",
-			"complexityScore": 4,
-			"recommendedSubtasks": 3,
-			"expansionPrompt": "Create FinalizationPlanner: 1) Implement test suite execution planning with coverage threshold detection from package.json, 2) Add git operations planning (branch push, PR creation) using existing git patterns, 3) Create duration estimation algorithm based on subtask count and complexity metrics",
-			"reasoning": "Medium complexity. Building on existing git utilities and test command detection reduces complexity. Main challenges are coverage threshold parsing and duration estimation algorithms."
-		},
-		{
-			"taskId": 9,
-			"taskTitle": "Integrate command with existing CLI infrastructure",
-			"complexityScore": 3,
-			"recommendedSubtasks": 2,
-			"expansionPrompt": "Complete CLI integration: 1) Add AutopilotCommand to command-registry.ts following existing patterns and update command metadata, 2) Test command registration and help system integration with proper cleanup and error handling",
-			"reasoning": "Low-medium complexity. The command-registry.ts provides a clear pattern to follow. Main work is registration and ensuring proper integration with existing CLI infrastructure. Well-established patterns reduce complexity."
-		},
-		{
-			"taskId": 10,
-			"taskTitle": "Add comprehensive error handling and edge cases",
-			"complexityScore": 7,
-			"recommendedSubtasks": 5,
-			"expansionPrompt": "Implement error handling: 1) Add missing task and invalid task structure error handling with helpful messages, 2) Handle git state errors (dirty working tree, missing tools), 3) Add dependency validation errors (circular, invalid references), 4) Implement missing tool detection with installation guidance, 5) Create user-friendly error messages following existing CLI patterns",
-			"reasoning": "High complexity due to comprehensive error scenarios. Each component (preflight, task loading, dependency resolution) has multiple failure modes that need proper handling. Providing helpful error messages and recovery suggestions adds complexity."
-		}
-	]
-}

.taskmaster/state.json

@@ -1,6 +1,6 @@
 {
-	"currentTag": "tdd-phase-1-core-rails",
+	"currentTag": "master",
-	"lastSwitched": "2025-10-09T12:41:40.367Z",
+	"lastSwitched": "2025-08-27T21:03:20.550Z",
 	"branchTagMapping": {
 		"v017-adds": "v017-adds",
 		"next": "next"

.taskmaster/tasks/task_001_tm-start.txt

@@ -1,34 +0,0 @@
-# Task ID: 1
-# Title: Create start command class structure
-# Status: pending
-# Dependencies: None
-# Priority: high
-# Description: Create the basic structure for the start command following the Commander class pattern
-# Details:
-Create a new file `apps/cli/src/commands/start.command.ts` based on the existing list.command.ts pattern. Implement the command class with proper command registration, description, and argument handling for the task_id parameter. The class should extend the base Command class and implement the required methods.
-
-Example structure:
-```typescript
-import { Command } from 'commander';
-import { BaseCommand } from './base.command';
-
-export class StartCommand extends BaseCommand {
-  public register(program: Command): void {
-    program
-      .command('start')
-      .alias('tm start')
-      .description('Start implementing a task using claude-code')
-      .argument('<task_id>', 'ID of the task to start')
-      .action(async (taskId: string) => {
-        await this.execute(taskId);
-      });
-  }
-
-  public async execute(taskId: string): Promise<void> {
-    // Implementation will be added in subsequent tasks
-  }
-}
-```
-
-# Test Strategy:
-Verify the command registers correctly by running the CLI with --help and checking that the start command appears with proper description and arguments. Test the basic structure by ensuring the command can be invoked without errors.

.taskmaster/tasks/task_002_tm-start.txt

@@ -1,26 +0,0 @@
-# Task ID: 2
-# Title: Register start command in CLI
-# Status: pending
-# Dependencies: 7
-# Priority: high
-# Description: Register the start command in the CLI application
-# Details:
-Update the CLI application to register the new start command. This involves importing the StartCommand class and adding it to the commands array in the CLI initialization.
-
-In `apps/cli/src/index.ts` or the appropriate file where commands are registered:
-
-```typescript
-import { StartCommand } from './commands/start.command';
-
-// Add StartCommand to the commands array
-const commands = [
-  // ... existing commands
-  new StartCommand(),
-];
-
-// Register all commands
-commands.forEach(command => command.register(program));
-```
-
-# Test Strategy:
-Verify the command is correctly registered by running the CLI with --help and checking that the start command appears in the list of available commands.

.taskmaster/tasks/task_003_tm-start.txt

@@ -1,32 +0,0 @@
-# Task ID: 3
-# Title: Create standardized prompt builder
-# Status: pending
-# Dependencies: 1
-# Priority: medium
-# Description: Implement a function to build the standardized prompt for claude-code based on the task details
-# Details:
-Create a function in the StartCommand class that builds the standardized prompt according to the template provided in the PRD. The prompt should include instructions for Claude to first run `tm show <task_id>` to get task details, and then implement the required changes.
-
-```typescript
-private buildPrompt(taskId: string): string {
-  return `You are an AI coding assistant with access to this repository's codebase.
-
-First, run this command to get the task details:
-tm show ${taskId}
-
-Then implement the task with these requirements:
-- Make the SMALLEST number of code changes possible
-- Follow ALL existing patterns in the codebase (you have access to analyze the code)
-- Do NOT over-engineer the solution
-- Use existing files/functions/patterns wherever possible
-- When complete, print: COMPLETED: <brief summary of changes>
-
-Begin by running tm show ${taskId} to understand what needs to be implemented.`;
-}
-```
-<info added on 2025-09-12T02:40:01.812Z>
-The prompt builder function will handle task context retrieval by instructing Claude to use the task-master show command. This approach ensures Claude has access to all necessary task details before implementation begins. The command syntax "tm show ${taskId}" embedded in the prompt will direct Claude to first gather the complete task context, including description, requirements, and any existing implementation details, before proceeding with code changes.
-</info added on 2025-09-12T02:40:01.812Z>
-
-# Test Strategy:
-Verify the prompt is correctly formatted by calling the function with a sample task ID and checking that the output matches the expected template with the task ID properly inserted.

.taskmaster/tasks/task_004_tm-start.txt

@@ -1,36 +0,0 @@
-# Task ID: 4
-# Title: Implement claude-code executor
-# Status: pending
-# Dependencies: 3
-# Priority: high
-# Description: Add functionality to execute the claude-code command with the built prompt
-# Details:
-Implement the functionality to execute the claude command with the built prompt. This should use Node.js child_process.exec() to run the command directly in the terminal.
-
-```typescript
-import { exec } from 'child_process';
-
-// Inside execute method, after task validation
-private async executeClaude(prompt: string): Promise<void> {
-  console.log('Starting claude-code to implement the task...');
-  
-  try {
-    // Execute claude with the prompt
-    const claudeCommand = `claude "${prompt.replace(/"/g, '\\"')}"`;
-    
-    // Use execSync to wait for the command to complete
-    const { execSync } = require('child_process');
-    execSync(claudeCommand, { stdio: 'inherit' });
-    
-    console.log('Claude session completed.');
-  } catch (error) {
-    console.error('Error executing claude-code:', error.message);
-    process.exit(1);
-  }
-}
-```
-
-Then call this method from the execute method after building the prompt.
-
-# Test Strategy:
-Test by running the command with a valid task ID and verifying that the claude command is executed with the correct prompt. Check that the command handles errors appropriately if claude-code is not available.