Merge active-status task forest

Author: Pyiner

desktop/garyx-desktop/src/renderer/src/app-shell/components/TaskForestConsole.tsx

@@ -67,6 +67,11 @@ const STATUS_ORDER: DesktopTaskStatus[] = [
   "done",
 ];
 
+const FOREST_CHIP_STATUS_ORDER: DesktopTaskStatus[] = [
+  "in_progress",
+  "in_review",
+];
+
 const REFRESH_INTERVAL_MS = 5000;
 const CULLING_NODE_THRESHOLD = 120;
 const CULLING_OVERSCAN_PX = 360;
@@ -726,7 +731,7 @@ export function TaskForestConsole({
           <span>{t("Task Forest")}</span>
         </div>
         <div className="task-forest-status-chips">
-          {STATUS_ORDER.map((status) => {
+          {FOREST_CHIP_STATUS_ORDER.map((status) => {
             const meta = STATUS_META[status];
             return (
               <button
@@ -824,7 +829,7 @@ export function TaskForestConsole({
         ) : !tasks.length ? (
           <div className="task-forest-state">
             {pinnedThreadIds.length
-              ? t("Pinned conversations with tasks will appear here.")
+              ? t("No active tasks right now.")
               : t("Pin conversations to add them to the operation room.")}
           </div>
         ) : null}

desktop/garyx-desktop/src/shared/contracts.ts

@@ -294,7 +294,7 @@ export interface DesktopTaskForestPage {
   skippedPinnedThreadIds: string[];
 }
 
-export type DesktopTaskForestScope = 'all';
+export type DesktopTaskForestScope = 'pinned' | 'all';
 
 export interface DesktopDreamSpan {
   spanId: string;

docs/design/task-1167-rooted-task-forest.md

@@ -9,6 +9,11 @@ is rendered as a root node using thread metadata, then the gateway attaches
 tasks whose `TaskSource.thread_id` points at that conversation and recursively
 attaches task children below them. Unrelated tasks are not returned.
 
+Follow-up: Task 1216 keeps the pinned-root contract but changes the default task
+node set to active statuses only. See
+`docs/design/task-1216-active-status-task-forest.md` for the status filter and
+reparenting rules.
+
 Keep the existing canvas, tidy-tree layout, cycle defense, node cards, node
 selection, thread detail panel, panning, zooming, minimap, and visual styling.
 This change only replaces the task set selection contract and wires the forest

docs/design/task-1216-active-status-task-forest.md

@@ -0,0 +1,37 @@
+# Task 1216 Active-Status Task Forest
+
+## Goal
+
+Keep the pinned-conversation task forest as the operation-room view, but only
+render task nodes whose status is `in_progress` or `in_review`. Historical
+`done` tasks and not-yet-started `todo` tasks stay out of the default forest.
+
+`scope=all` remains the diagnostic escape hatch for the complete task map.
+
+## Filtering Contract
+
+The default forest endpoint still starts from pinned conversation roots and
+uses the existing recursive task subtree walk. The status filter is applied
+after the recursive walk has reached the subtree, not before it. This preserves
+active descendants below inactive intermediate tasks.
+
+Thread root nodes are not task status filtered. If a pinned conversation has a
+task subtree but no retained active task, the response may contain only the
+thread root for that pinned conversation.
+
+## Reparenting Contract
+
+Filtering inactive task nodes can remove an intermediate parent. Every retained
+task is reparented as follows:
+
+1. Follow the original parent chain using `parent_task_number`, with legacy
+   `source_task_id` and `source_task_thread_id` as fallbacks.
+2. The first ancestor in the same pinned subtree whose status is
+   `in_progress` or `in_review` becomes the retained task's parent.
+3. If no retained ancestor exists before the pinned conversation root, the task
+   attaches directly to that thread root.
+4. The returned `parent_node_id`, `parent_thread_id`, and `parent_task_number`
+   describe this rendered parent, not the filtered-out original parent.
+
+The resulting graph stays connected from each pinned conversation root to the
+active task nodes while skipping inactive history.