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: prioritize .taskmaster in parent directories over other project markers (#1351)\n\nCo-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>\nCo-authored-by: Ben Coombs <bjcoombs@users.noreply.github.com>\n\n

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

apps/docs/best-practices/advanced-tasks.mdx

@@ -207,4 +207,57 @@ The agent will execute:
 
 ```bash
 task-master expand --id=5 --research
-```
+```
+
+## Working with Monorepos and Multi-Project Setups
+
+Task Master now intelligently handles monorepos and multi-project setups by prioritizing `.taskmaster` directories in parent directories over other project markers.
+
+### How Project Root Detection Works
+
+When you run Task Master commands from subdirectories, it uses a two-pass search strategy:
+
+1. **First Pass**: Searches ALL parent directories for `.taskmaster` markers (highest priority)
+2. **Second Pass**: If no `.taskmaster` found, searches for other project markers (`.git`, `package.json`, etc.)
+
+This ensures that a `.taskmaster` directory in a parent directory takes precedence over project markers in subdirectories.
+
+### Monorepo Example
+
+```
+/project/.taskmaster          # Task Master project root
+/project/packages/frontend/.git
+/project/packages/backend/package.json
+/project/packages/api/go.mod
+```
+
+When running `task-master list` from any subdirectory:
+- From `/project/packages/frontend/`: Uses `/project` (not `/project/packages/frontend`)
+- From `/project/packages/backend/src/`: Uses `/project` (not `/project/packages/backend`)  
+- From `/project/packages/api/`: Uses `/project` (not `/project/packages/api`)
+
+### Setting Up Monorepo Task Management
+
+1. **Initialize Task Master at the monorepo root**:
+   ```bash
+   cd /project
+   task-master init
+   ```
+
+2. **Work from any subdirectory**:
+   ```bash
+   cd packages/frontend
+   task-master next  # Uses /project/.taskmaster
+   ```
+
+3. **All subprojects share the same task system**:
+   - Tasks can span multiple packages
+   - Dependencies work across package boundaries  
+   - Single source of truth for project-wide task management
+
+### Benefits for Team Workflows
+
+- **Consistent Task Management**: All team members see the same tasks regardless of which package they're working in
+- **Cross-Package Tasks**: Tasks can involve changes across multiple packages
+- **Simplified Setup**: Only need to configure Task Master once at the root
+- **Unified Progress tracking**: Track progress across the entire project from anywhere

apps/docs/whats-new.mdx

@@ -3,4 +3,20 @@ title: "What's New"
 sidebarTitle: "What's New"
 ---
 
+## Latest Improvements
+
+### Enhanced Monorepo Support
+
+Task Master now provides improved support for monorepos and multi-project setups:
+
+- **Smart Project Root Detection**: When running commands from subdirectories, Task Master now prioritizes `.taskmaster` directories in parent folders over other project markers (like `.git`, `package.json`, etc.)
+- **Unified Task Management**: A single `.taskmaster` at the monorepo root can now manage tasks across multiple sub-repositories
+- **Consistent Behavior**: All team members see the same tasks regardless of which package directory they're working in
+
+This enables seamless task management in complex project structures where you might have multiple packages, services, or applications under a single task management system.
+
+**Example**: In a monorepo with `/project/.taskmaster` and `/project/packages/frontend/.git`, running `task-master list` from the frontend package will correctly use the root `.taskmaster` instead of treating the frontend as a separate project.
+
+---
+
 An easy way to see the latest releases