Fix race condition destroying terminals when opening terminals view

The cleanup effect in /terminals that removes orphaned worktree terminals
was running before tasks finished loading. Since allTaskWorktrees derives
from tasks (defaulting to []), all worktree terminals appeared orphaned
and were destroyed.

This was triggered by opening the terminals view in a new browser tab -
terminals arrived via WebSocket faster than tasks via HTTP API.

Added isTasksLoading guard to prevent cleanup until tasks are loaded.

Author: knowsuchagency

src/routes/terminals/index.tsx

@@ -60,7 +60,7 @@ function TerminalsView() {
     }
   }, [tabs, activeTabId, isViewStateLoading, setActiveTab])
 
-  const { data: tasks = [] } = useTasks()
+  const { data: tasks = [], isLoading: isTasksLoading } = useTasks()
   const { data: repositories = [] } = useRepositories()
   const { data: worktreeBasePath } = useWorktreeBasePath()
   const [repoFilter, setRepoFilter] = useState<string | null>(null)
@@ -136,7 +136,9 @@ function TerminalsView() {
 
   // Destroy orphaned worktree terminals (terminals in worktrees dir but no matching task)
   useEffect(() => {
-    if (!worktreeBasePath) return
+    // Don't run cleanup until tasks are loaded - otherwise we'd destroy valid terminals
+    // because allTaskWorktrees would be empty while tasks are still loading
+    if (!worktreeBasePath || isTasksLoading) return
 
     for (const terminal of terminals) {
       const isInWorktreesDir = terminal.cwd?.startsWith(worktreeBasePath)
@@ -146,7 +148,7 @@ function TerminalsView() {
         destroyTerminal(terminal.id)
       }
     }
-  }, [terminals, allTaskWorktrees, worktreeBasePath, destroyTerminal])
+  }, [terminals, allTaskWorktrees, worktreeBasePath, destroyTerminal, isTasksLoading])
 
   // Filter terminals for the active tab
   const visibleTerminals = useMemo(() => {