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

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

  Original commit: fix: improve docs and command help for analzye-complexity (#1235)\n\n\n

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

.taskmaster/docs/README.md

@@ -12,7 +12,7 @@ In an AI-driven development process—particularly with tools like [Cursor](http
 4. **Generate** individual task files (e.g., `task_001.txt`) for easy reference or to feed into an AI coding workflow.
 5. **Set task status**—mark tasks as `done`, `pending`, or `deferred` based on progress.
 6. **Expand** tasks with subtasks—break down complex tasks into smaller, more manageable subtasks.
-7. **Research-backed subtask generation**—use Perplexity AI to generate more informed and contextually relevant subtasks.
+7. **Research-backed subtask generation**—use your configured research model to generate more informed and contextually relevant subtasks.
 8. **Clear subtasks**—remove subtasks from specified tasks to allow regeneration or restructuring.
 9. **Show task details**—display detailed information about a specific task and its subtasks.
 
@@ -29,7 +29,7 @@ The script can be configured through environment variables in a `.env` file at t
 - `MODEL`: Specify which Claude model to use (default: "claude-3-7-sonnet-20250219")
 - `MAX_TOKENS`: Maximum tokens for model responses (default: 4000)
 - `TEMPERATURE`: Temperature for model responses (default: 0.7)
-- `PERPLEXITY_API_KEY`: Your Perplexity API key for research-backed subtask generation
+- `PERPLEXITY_API_KEY`: Your Perplexity API key for research-backed subtask generation (if using Perplexity as your research model)
 - `PERPLEXITY_MODEL`: Specify which Perplexity model to use (default: "sonar-medium-online")
 - `DEBUG`: Enable debug logging (default: false)
 - `TASKMASTER_LOG_LEVEL`: Log level - debug, info, warn, error (default: info)
@@ -97,7 +97,7 @@ node scripts/dev.js update --from=4 --prompt="Refactor tasks from ID 4 onward to
 # Update all tasks (default from=1)
 node scripts/dev.js update --prompt="Add authentication to all relevant tasks"
 
-# With research-backed updates using Perplexity AI
+# With research-backed updates using your configured research model
 node scripts/dev.js update --from=4 --prompt="Integrate OAuth 2.0" --research
 
 # Specify a different tasks file
@@ -109,7 +109,7 @@ Notes:
 - The `--prompt` parameter is required and should explain the changes or new context
 - Only tasks that aren't marked as 'done' will be updated
 - Tasks with ID >= the specified --from value will be updated
-- The `--research` flag uses Perplexity AI for more informed updates when available
+- The `--research` flag uses your configured research model for more informed updates when available
 
 ## Updating a Single Task
 
@@ -119,7 +119,7 @@ The `update-task` command allows you to update a specific task instead of multip
 # Update a specific task with new information
 node scripts/dev.js update-task --id=4 --prompt="Use JWT for authentication"
 
-# With research-backed updates using Perplexity AI
+# With research-backed updates using your configured research model
 node scripts/dev.js update-task --id=4 --prompt="Use JWT for authentication" --research
 ```
 
@@ -178,10 +178,10 @@ node scripts/dev.js expand --all
 # Force regeneration of subtasks for all pending tasks
 node scripts/dev.js expand --all --force
 
-# Use Perplexity AI for research-backed subtask generation
+# Use your configured research model for research-backed subtask generation
 node scripts/dev.js expand --id=3 --research
 
-# Use Perplexity AI for research-backed generation on all pending tasks
+# Use your configured research model for research-backed generation on all pending tasks
 node scripts/dev.js expand --all --research
 ```
 
@@ -211,17 +211,16 @@ Notes:
 
 The script integrates with two AI services:
 
-1. **Anthropic Claude**: Used for parsing PRDs, generating tasks, and creating subtasks.
-2. **Perplexity AI**: Used for research-backed subtask generation when the `--research` flag is specified.
+1. **Main AI Model**: Used for parsing PRDs, generating tasks, and creating subtasks (typically Anthropic Claude).
+2. **Research Model**: Used for research-backed subtask generation when the `--research` flag is specified.
 
-The Perplexity integration uses the OpenAI client to connect to Perplexity's API, which provides enhanced research capabilities for generating more informed subtasks. If the Perplexity API is unavailable or encounters an error, the script will automatically fall back to using Anthropic's Claude.
+The research integration provides enhanced research capabilities for generating more informed subtasks. You can configure different models for research (like Perplexity, which has access to current information) vs. main tasks. If the research model is unavailable or encounters an error, the script will automatically fall back to using your main model.
 
-To use the Perplexity integration:
+To use research-backed features:
 
-1. Obtain a Perplexity API key
-2. Add `PERPLEXITY_API_KEY` to your `.env` file
-3. Optionally specify `PERPLEXITY_MODEL` in your `.env` file (default: "sonar-medium-online")
-4. Use the `--research` flag with the `expand` command
+1. Configure your research model using `task-master models --setup`
+2. Ensure you have the appropriate API key in your `.env` file (e.g., `PERPLEXITY_API_KEY` if using Perplexity)
+3. Use the `--research` flag with supported commands
 
 ## Logging
 
@@ -342,13 +341,13 @@ node scripts/dev.js analyze-complexity --model=claude-3-opus-20240229
 # Set a custom complexity threshold (1-10)
 node scripts/dev.js analyze-complexity --threshold=6
 
-# Use Perplexity AI for research-backed complexity analysis
+# Use your configured research model for research-backed complexity analysis
 node scripts/dev.js analyze-complexity --research
 ```
 
 Notes:
 
-- The command uses Claude to analyze each task's complexity (or Perplexity with --research flag)
+- The command uses your main model to analyze each task's complexity (or your configured research model with --research flag)
 - Tasks are scored on a scale of 1-10
 - Each task receives a recommended number of subtasks based on DEFAULT_SUBTASKS configuration
 - The default output path is `scripts/task-complexity-report.json`