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

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

  Original commit: Merge pull request #1250 from eyaltoledano/chore/merge.main.september\n\n\n

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

apps/docs/capabilities/cli-root-commands.mdx

@@ -101,7 +101,12 @@ sidebarTitle: "CLI Commands"
     task-master set-status --id=1.1,1.2 --status=<status>
     ```
 
-    When marking a task as "done", all of its subtasks will automatically be marked as "done" as well.
+    **Automatic Parent Status Management:**
+    When updating subtask statuses, parent task statuses are automatically adjusted:
+    - When **all subtasks** are marked `done`, the parent task becomes `done`
+    - When **at least one subtask** is `in-progress` or `done`, the parent task becomes `in-progress`
+    
+    When marking a parent task as "done", all of its subtasks will automatically be marked as "done" as well.
   </Accordion>
 
   <Accordion title="Expand Tasks">

apps/docs/capabilities/mcp.mdx

@@ -34,7 +34,7 @@ The MCP tools can be categorized in the same way as the core functionalities:
 -   **`get_tasks`**: Lists all tasks.
 -   **`get_task`**: Shows the details of a specific task.
 -   **`next_task`**: Shows the next task to work on.
--   **`set_task_status`**: Sets the status of a task or subtask.
+-   **`set_task_status`**: Sets the status of a task or subtask. When updating subtask statuses, parent task statuses are automatically adjusted based on subtask completion.
 
 ### 3. Task Analysis and Expansion
 

apps/docs/capabilities/task-structure.mdx

@@ -120,6 +120,23 @@ The `show` command:
 - Provides contextual action suggestions based on the task's state
 - Works with both regular tasks and subtasks (using the format taskId.subtaskId)
 </Accordion>
+
+<Accordion title="Automatic Parent Status Management">
+Task Master automatically manages parent task statuses based on subtask changes:
+
+**Status Rules:**
+- When **all subtasks** are marked as `done`, the parent task is automatically set to `done`
+- When **at least one subtask** is `in-progress` or `done`, the parent task is automatically set to `in-progress`
+- This ensures parent tasks accurately reflect the progress of their subtasks
+
+**Example Workflow:**
+1. Parent task starts as `pending`
+2. First subtask marked `in-progress` → Parent becomes `in-progress`
+3. Some subtasks completed (`done`) → Parent remains `in-progress`
+4. All subtasks completed (`done`) → Parent automatically becomes `done`
+
+This automation eliminates the need to manually update parent task statuses and ensures consistency across your task hierarchy.
+</Accordion>
 </AccordionGroup>
 
 ## Best Practices for AI-Driven Development