docs: auto-update documentation based on changes in next branch

This PR was automatically generated to update documentation based on recent changes.

  Original commit: feat: implement tdd workflow (#1309)\n\nCo-authored-by: Claude <noreply@anthropic.com>\nCo-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>\n\n

  Co-authored-by: Claude <claude-assistant@anthropic.com>

.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.

.coderabbit.yaml

@@ -1,7 +1,3 @@
 reviews:
   profile: chill
   poem: false
-  auto_review:
-    enabled: true
-    base_branches:
-      - ".*"

apps/docs/capabilities/mcp.mdx

@@ -20,7 +20,7 @@ To optimize LLM context usage, you can control which Task Master MCP tools are l
 ### Configuration Modes
 
 #### All Tools (Default)
-Loads all 36 available tools. Use when you need full Task Master functionality.
+Loads all 44 available tools. Use when you need full Task Master functionality.
 
 ```json
 {
@@ -40,7 +40,7 @@ Loads all 36 available tools. Use when you need full Task Master functionality.
 If `TASK_MASTER_TOOLS` is not set, all tools are loaded by default.
 
 #### Core Tools (Lean Mode)
-Loads only 7 essential tools for daily development. Ideal for minimal context usage.
+Loads only 12 essential tools for daily development. Ideal for minimal context usage.
 
 **Core tools included:**
 - `get_tasks` - List all tasks
@@ -50,6 +50,11 @@ Loads only 7 essential tools for daily development. Ideal for minimal context us
 - `update_subtask` - Add implementation notes
 - `parse_prd` - Generate tasks from PRD
 - `expand_task` - Break down tasks into subtasks
+- `autopilot_start` - Start TDD workflow
+- `autopilot_next` - Get next workflow action
+- `autopilot_status` - Check workflow status
+- `autopilot_complete_phase` - Complete workflow phase
+- `autopilot_commit` - Commit workflow changes
 
 ```json
 {
@@ -69,7 +74,7 @@ Loads only 7 essential tools for daily development. Ideal for minimal context us
 You can also use `"lean"` as an alias for `"core"`.
 
 #### Standard Tools
-Loads 15 commonly used tools. Balances functionality with context efficiency.
+Loads 20 commonly used tools. Balances functionality with context efficiency.
 
 **Standard tools include all core tools plus:**
 - `initialize_project` - Set up new projects
@@ -80,6 +85,9 @@ Loads 15 commonly used tools. Balances functionality with context efficiency.
 - `generate` - Generate task markdown files
 - `add_task` - Create new tasks
 - `complexity_report` - View complexity analysis
+- `autopilot_resume` - Resume interrupted workflow
+- `autopilot_finalize` - Complete and merge workflow
+- `autopilot_abort` - Abort current workflow
 
 ```json
 {
@@ -129,8 +137,8 @@ When the MCP server starts, it logs which tools were loaded:
 Task Master MCP Server starting...
 Tool mode configuration: standard
 Loading standard tools
-Registering 15 MCP tools (mode: standard)
-Successfully registered 15/15 tools
+Registering 20 MCP tools (mode: standard)
+Successfully registered 20/20 tools
 ```
 
 ## Tool Categories
@@ -187,53 +195,13 @@ The MCP tools can be categorized in the same way as the core functionalities:
 -   **`rename_tag`**: Renames a tag.
 -   **`copy_tag`**: Copies a tag.
 
-### 7. Scope Management
+### 7. Autonomous TDD Workflow (Autopilot)
 
--   **`scope_up`**: Moves a task up in the hierarchy.
--   **`scope_down`**: Moves a task down in the hierarchy.
-
-## Troubleshooting
-
-### MCP Client Compatibility Issues
-
-If you're experiencing issues with MCP clients not discovering Task Master tools, or seeing "vendor undefined" errors, this is likely due to JSON Schema compatibility differences.
-
-**Common symptoms:**
-- Tools show as "0 tools enabled" in MCP client settings
-- "vendor undefined" errors in MCP client logs  
-- Task Master tools not appearing in tool lists
-
-**Root cause:**
-Some MCP clients (Augment IDE, gemini-cli, etc.) only support JSON Schema Draft-07, while newer schema generators output Draft 2020-12.
-
-**Solution:**
-Task Master includes a compatibility fix (as of v2.1.2) that ensures all MCP tools use JSON Schema Draft-07. This fix:
-
-- Uses Zod v3 compatibility mode for schema generation
-- Ensures proper tool discovery across all MCP clients
-- Maintains full functionality while improving compatibility
-
-If you're still experiencing issues after updating to the latest version:
-
-1. **Restart your MCP client** - Schema changes require a restart
-2. **Verify API keys** - Tools may not load without proper authentication
-3. **Check client logs** - Look for any remaining compatibility errors
-4. **Try a different client** - Test with Claude Code or Cursor to isolate client-specific issues
-
-### Custom MCP Tool Development
-
-If you're extending Task Master with custom MCP tools, ensure you import from the Draft-07 compatible version:
-
-```typescript
-// ✅ CORRECT - Draft-07 compatible
-import { z } from 'zod/v3';
-
-// ❌ WRONG - May cause compatibility issues
-import { z } from 'zod';
-```
-
-This compatibility requirement applies only to MCP tool definitions in:
-- `apps/mcp/src/tools/`
-- `mcp-server/src/tools/`
-
-The rest of the codebase can continue using standard Zod v4.
+-   **`autopilot_start`**: Initialize autonomous TDD workflow for a task.
+-   **`autopilot_next`**: Get next action with context in the workflow.
+-   **`autopilot_status`**: Check current workflow status and progress.
+-   **`autopilot_complete_phase`**: Complete current phase with test results.
+-   **`autopilot_commit`**: Commit changes with generated metadata.
+-   **`autopilot_resume`**: Resume interrupted workflow from saved state.
+-   **`autopilot_finalize`**: Complete workflow and merge changes.
+-   **`autopilot_abort`**: Abort current workflow and clean up state.

apps/docs/configuration.mdx

@@ -33,7 +33,47 @@ description: "Configure Task Master through environment variables in a .env file
 
 ## TDD Workflow Configuration
 
-Additional options for autonomous TDD workflow:
+Comprehensive options for autonomous TDD workflow via `.taskmaster/config.json`:
+
+### Core Workflow Settings
+
+| Setting | Default | Description |
+| --- | --- | --- |
+| `workflow.enableAutopilot` | `true` | Enable autopilot/TDD workflow features |
+| `workflow.maxPhaseAttempts` | `3` | Maximum retry attempts for phase validation |
+| `workflow.branchPattern` | `"task-{taskId}"` | Branch naming pattern for workflow branches |
+| `workflow.requireCleanWorkingTree` | `true` | Require clean working tree before starting workflow |
+| `workflow.autoStageChanges` | `true` | Automatically stage all changes during commit phase |
+
+### Commit Configuration
+
+| Setting | Default | Description |
+| --- | --- | --- |
+| `workflow.includeCoAuthor` | `true` | Include co-author attribution in commits |
+| `workflow.coAuthorName` | `"Claude"` | Co-author name for commit messages |
+| `workflow.coAuthorEmail` | `"noreply@anthropic.com"` | Co-author email for commit messages |
+| `workflow.commitMessageTemplate` | `"{type}: {description}\n\n{body}"` | Commit message template pattern |
+| `workflow.defaultCommitType` | `"feat"` | Default commit type for autopilot |
+| `workflow.allowedCommitTypes` | `["feat", "fix", "refactor", "test", "docs", "chore"]` | Allowed conventional commit types |
+
+### Test Validation Thresholds
+
+| Setting | Default | Description |
+| --- | --- | --- |
+| `workflow.testThresholds.minTests` | `1` | Minimum test count for valid RED phase |
+| `workflow.testThresholds.maxFailuresInGreen` | `0` | Maximum allowed failing tests in GREEN phase |
+
+### Activity Logging
+
+| Setting | Default | Description |
+| --- | --- | --- |
+| `workflow.enableActivityLogging` | `true` | Enable activity logging for workflow events |
+| `workflow.activityLogPath` | `".taskmaster/logs"` | Path to store workflow activity logs |
+| `workflow.enableStateBackup` | `true` | Enable automatic backup of workflow state |
+| `workflow.maxStateBackups` | `10` | Maximum workflow state backups to retain |
+| `workflow.operationTimeout` | `300000` | Timeout for workflow operations in milliseconds |
+
+### Environment Variables (Legacy Support)
 
 | Variable | Default | Description |
 | --- | --- | --- |
@@ -41,9 +81,11 @@ Additional options for autonomous TDD workflow:
 | `TM_AUTO_COMMIT` | `true` | Auto-commit after GREEN phase |
 | `TM_PROJECT_ROOT` | Current dir | Default project root |
 
-## Example .env File
+## Example Configuration
 
-```
+### Environment Variables (.env file)
+
+```bash
 # Required
 ANTHROPIC_API_KEY=sk-ant-api03-your-api-key
 
@@ -66,11 +108,56 @@ DEFAULT_PRIORITY=medium
 DEBUG=false
 LOG_LEVEL=info
 
-# TDD Workflow
+# TDD Workflow (Legacy)
 TM_MAX_ATTEMPTS=3
 TM_AUTO_COMMIT=true
 ```
 
+### Config JSON (.taskmaster/config.json)
+
+```json
+{
+  "models": {
+    "main": "claude-3-5-sonnet-20241022",
+    "research": "perplexity-llama-3.1-sonar-large-128k-online",
+    "fallback": "claude-3-haiku-20240307"
+  },
+  "workflow": {
+    "enableAutopilot": true,
+    "maxPhaseAttempts": 3,
+    "branchPattern": "task-{taskId}",
+    "requireCleanWorkingTree": true,
+    "autoStageChanges": true,
+    "includeCoAuthor": true,
+    "coAuthorName": "Claude",
+    "coAuthorEmail": "noreply@anthropic.com",
+    "commitMessageTemplate": "{type}: {description}\n\n{body}",
+    "defaultCommitType": "feat",
+    "allowedCommitTypes": ["feat", "fix", "refactor", "test", "docs", "chore"],
+    "testThresholds": {
+      "minTests": 1,
+      "maxFailuresInGreen": 0
+    },
+    "enableActivityLogging": true,
+    "activityLogPath": ".taskmaster/logs",
+    "enableStateBackup": true,
+    "maxStateBackups": 10,
+    "operationTimeout": 300000
+  },
+  "tasks": {
+    "defaultPriority": "medium",
+    "maxSubtasks": 10,
+    "validateDependencies": true
+  },
+  "logging": {
+    "enabled": true,
+    "level": "info",
+    "logRequests": false,
+    "logPerformance": false
+  }
+}
+```
+
 ## Troubleshooting
 
 ### If `task-master init` doesn't respond:

apps/docs/getting-started/quick-start/installation.mdx

@@ -88,7 +88,7 @@ MCP (Model Control Protocol) lets you run Task Master directly from your editor.
 
 > 🔑 Replace `YOUR_…_KEY_HERE` with your real API keys. You can remove keys you don't use.
 
-> **Note**: If you see `0 tools enabled` in the MCP settings, restart your editor and check that your API keys are correctly configured. Task Master v2.1.2+ includes compatibility fixes for MCP clients that only support JSON Schema Draft-07.
+> **Note**: If you see `0 tools enabled` in the MCP settings, restart your editor and check that your API keys are correctly configured.
 
 ### VS Code (`servers` + `type`)
 

apps/mcp/src/tools/README-ZOD-V3.md

@@ -1,70 +0,0 @@
-# Why MCP Tools Use Zod v3
-
-## Problem
-
-- **FastMCP** uses `xsschema` to convert schemas → outputs JSON Schema **Draft 2020-12**
-- **MCP clients** (Augment IDE, gemini-cli, etc.) only support **Draft-07**
-- Using Zod v4 in tools causes "vendor undefined" errors and tool discovery failures
-
-## Temporary Solution
-
-All MCP tool files import from `zod/v3` instead of `zod`:
-
-```typescript
-import { z } from 'zod/v3';  // ✅ Draft-07 compatible
-// NOT: import { z } from 'zod';  // ❌ Would use Draft 2020-12
-```
-
-### Why This Works
-
-- Zod v4 ships with v3 compatibility at `zod/v3`
-- FastMCP + zod-to-json-schema converts Zod v3 schemas → **Draft-07**
-- This ensures MCP clients can discover and use our tools
-
-### What This Means
-
-- ✅ **MCP tools** → use `zod/v3` (apps/mcp & mcp-server/src/tools)
-- ✅ **Rest of codebase** → uses `zod` (Zod v4)
-- ✅ **No conflicts** → they're from the same package, just different versions
-
-## When Can We Remove This?
-
-This workaround can be removed when **either**:
-
-1. **FastMCP adds JSON Schema version configuration**
-   - e.g., `new FastMCP({ jsonSchema: { target: 'draft-07' } })`
-   - Tracking: https://github.com/punkpeye/fastmcp/issues/189
-
-2. **MCP spec adds Draft 2020-12 support**
-   - Unlikely in the short term
-
-3. **xsschema adds version targeting**
-   - Would allow FastMCP to use Draft-07
-
-## How to Maintain
-
-When adding new MCP tools:
-
-```typescript
-// ✅ CORRECT
-import { z } from 'zod/v3';
-
-export function registerMyTool(server: FastMCP) {
-  server.addTool({
-    name: 'my_tool',
-    parameters: z.object({ ... }),  // Will use Draft-07
-    execute: async (args, context) => { ... }
-  });
-}
-```
-
-```typescript
-// ❌ WRONG - Will break MCP client compatibility
-import { z } from 'zod';  // Don't do this in apps/mcp/src/tools/
-```
-
----
-
-**Last Updated:** 2025-10-18
-**Affects:** All files in `apps/mcp/src/tools/`
-**See Also:** `mcp-server/src/tools/README-ZOD-V3.md` (same workaround)

apps/mcp/src/tools/autopilot/abort.tool.ts

@@ -3,9 +3,7 @@
  * Abort a running TDD workflow and clean up state
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

apps/mcp/src/tools/autopilot/commit.tool.ts

@@ -3,9 +3,7 @@
  * Create a git commit with automatic staging and message generation
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

apps/mcp/src/tools/autopilot/complete.tool.ts

@@ -3,9 +3,7 @@
  * Complete the current TDD phase with test result validation
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

apps/mcp/src/tools/autopilot/finalize.tool.ts

@@ -3,9 +3,7 @@
  * Finalize and complete the workflow with working tree validation
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

apps/mcp/src/tools/autopilot/next.tool.ts

@@ -3,9 +3,7 @@
  * Get the next action to perform in the TDD workflow
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

apps/mcp/src/tools/autopilot/resume.tool.ts

@@ -3,9 +3,7 @@
  * Resume a previously started TDD workflow from saved state
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

apps/mcp/src/tools/autopilot/start.tool.ts

@@ -3,9 +3,7 @@
  * Initialize and start a new TDD workflow for a task
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

apps/mcp/src/tools/autopilot/status.tool.ts

@@ -3,9 +3,7 @@
  * Get comprehensive workflow status and progress information
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot

mcp-server/src/logger.js

@@ -78,7 +78,7 @@ function log(level, ...args) {
 		// is responsible for directing logs correctly (e.g., to stderr)
 		// during tool execution without upsetting the client connection.
 		// Logs outside of tool execution (like startup) will go to stdout.
-		console.error(prefix, ...coloredArgs);
+		console.log(prefix, ...coloredArgs);
 	}
 }
 

mcp-server/src/tools/README-ZOD-V3.md

@@ -1,67 +0,0 @@
-# Why MCP Tools Use Zod v3
-
-## Problem
-
-- **FastMCP** uses `xsschema` to convert schemas → outputs JSON Schema **Draft 2020-12**
-- **MCP clients** (Augment IDE, gemini-cli, etc.) only support **Draft-07**
-- Using Zod v4 in tools causes "vendor undefined" errors and tool discovery failures
-
-## Temporary Solution
-
-All MCP tool files import from `zod/v3` instead of `zod`:
-
-```javascript
-import { z } from 'zod/v3';  // ✅ Draft-07 compatible
-// NOT: import { z } from 'zod';  // ❌ Would use Draft 2020-12
-```
-
-### Why This Works
-
-- Zod v4 ships with v3 compatibility at `zod/v3`
-- FastMCP + zod-to-json-schema converts Zod v3 schemas → **Draft-07**
-- This ensures MCP clients can discover and use our tools
-
-### What This Means
-
-- ✅ **MCP tools** → use `zod/v3` (this directory)
-- ✅ **Rest of codebase** → uses `zod` (Zod v4)
-- ✅ **No conflicts** → they're from the same package, just different versions
-
-## When Can We Remove This?
-
-This workaround can be removed when **either**:
-
-1. **FastMCP adds JSON Schema version configuration**
-   - e.g., `new FastMCP({ jsonSchema: { target: 'draft-07' } })`
-   - Tracking: https://github.com/punkpeye/fastmcp/issues/189
-
-2. **MCP spec adds Draft 2020-12 support**
-   - Unlikely in the short term
-
-3. **xsschema adds version targeting**
-   - Would allow FastMCP to use Draft-07
-
-## How to Maintain
-
-When adding new MCP tools:
-
-```javascript
-// ✅ CORRECT
-import { z } from 'zod/v3';
-
-server.addTool({
-  name: 'my_tool',
-  parameters: z.object({ ... }),  // Will use Draft-07
-  execute: async (args) => { ... }
-});
-```
-
-```javascript
-// ❌ WRONG - Will break MCP client compatibility
-import { z } from 'zod';  // Don't do this in mcp-server/src/tools/
-```
-
----
-
-**Last Updated:** 2025-10-18
-**Affects:** All files in `mcp-server/src/tools/`

mcp-server/src/tools/add-dependency.js

@@ -3,9 +3,7 @@
  * Tool for adding a dependency to a task
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/add-subtask.js

@@ -3,9 +3,7 @@
  * Tool for adding subtasks to existing tasks
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/add-tag.js

@@ -3,9 +3,7 @@
  * Tool to create a new tag
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/add-task.js

@@ -3,9 +3,7 @@
  * Tool to add a new task using AI
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/analyze.js

@@ -3,9 +3,7 @@
  * Tool for analyzing task complexity and generating recommendations
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import path from 'path';
 import fs from 'fs'; // Import fs for directory check/creation
 import {

mcp-server/src/tools/clear-subtasks.js

@@ -3,9 +3,7 @@
  * Tool for clearing subtasks from parent tasks
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/complexity-report.js

@@ -3,9 +3,7 @@
  * Tool for displaying the complexity analysis report
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/copy-tag.js

@@ -3,9 +3,7 @@
  * Tool to copy an existing tag to a new tag
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/delete-tag.js

@@ -3,9 +3,7 @@
  * Tool to delete an existing tag
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/expand-all.js

@@ -3,9 +3,7 @@
  * Tool for expanding all pending tasks with subtasks
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/expand-task.js

@@ -3,9 +3,7 @@
  * Tool to expand a task into subtasks
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/fix-dependencies.js

@@ -3,9 +3,7 @@
  * Tool for automatically fixing invalid task dependencies
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/generate.js

@@ -3,9 +3,7 @@
  * Tool to generate individual task files from tasks.json
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/get-operation-status.js

@@ -1,7 +1,5 @@
 // mcp-server/src/tools/get-operation-status.js
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import { createErrorResponse, createContentResponse } from './utils.js'; // Assuming these utils exist
 
 /**

mcp-server/src/tools/get-task.js

@@ -3,9 +3,7 @@
  * Tool to get task details by ID
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/get-tasks.js

@@ -3,9 +3,7 @@
  * Tool to get all tasks from Task Master
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/initialize-project.js

@@ -1,6 +1,4 @@
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/list-tags.js

@@ -3,9 +3,7 @@
  * Tool to list all available tags
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/models.js

@@ -3,9 +3,7 @@
  * MCP tool for managing AI model configurations
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/move-task.js

@@ -3,9 +3,7 @@
  * Tool for moving tasks or subtasks to a new position
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/next-task.js

@@ -3,9 +3,7 @@
  * Tool to find the next task to work on based on dependencies and status
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/parse-prd.js

@@ -3,9 +3,7 @@
  * Tool to parse PRD document and generate tasks
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	withNormalizedProjectRoot,

mcp-server/src/tools/remove-dependency.js

@@ -3,9 +3,7 @@
  * Tool for removing a dependency from a task
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/remove-subtask.js

@@ -3,9 +3,7 @@
  * Tool for removing subtasks from parent tasks
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/remove-task.js

@@ -3,9 +3,7 @@
  * Tool to remove a task by ID
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/rename-tag.js

@@ -3,9 +3,7 @@
  * Tool to rename an existing tag
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/research.js

@@ -3,9 +3,7 @@
  * Tool to perform AI-powered research queries with project context
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/response-language.js

@@ -1,6 +1,4 @@
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/rules.js

@@ -3,9 +3,7 @@
  * Tool to add or remove rules from a project (MCP server)
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/scope-down.js

@@ -3,9 +3,7 @@
  * Tool to scope down task complexity
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/scope-up.js

@@ -3,9 +3,7 @@
  * Tool to scope up task complexity
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/set-task-status.js

@@ -3,9 +3,7 @@
  * Tool to set the status of a task
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/update-subtask.js

@@ -3,9 +3,7 @@
  * Tool to append additional information to a specific subtask
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/update-task.js

@@ -3,9 +3,7 @@
  * Tool to update a single task by ID with new information
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/update.js

@@ -3,9 +3,7 @@
  * Tool to update tasks based on new context/prompt
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,

mcp-server/src/tools/use-tag.js

@@ -3,9 +3,7 @@
  * Tool to switch to a different tag context
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	createErrorResponse,
 	handleApiResult,

mcp-server/src/tools/validate-dependencies.js

@@ -3,9 +3,7 @@
  * Tool for validating task dependencies
  */
 
-// TEMPORARY: Using zod/v3 for Draft-07 JSON Schema compatibility with FastMCP's zod-to-json-schema
-// TODO: Revert to 'zod' when MCP spec issue is resolved (see PR #1323)
-import { z } from 'zod/v3';
+import { z } from 'zod';
 import {
 	handleApiResult,
 	createErrorResponse,