control-flow

# /control-flow — Analyze and design control flows and data structures Read the relevant source code and produce ASCII tree diagrams inside ```txt blocks. ## Format - Each user action or IO event is a separate tree root - Real function names and types — never invent - Payload shapes as TypeScript types, not prose - State mutations: which fields change, what triggers - Re-render chain: which components and why - Cross-package when the flow spans app → CLI → server - Compact — skip trivial pass-throughs, show decisions Example: ```txt User taps "Archive" │ ├─ handleActionPress(action: SessionActionItem) │ └─ onClose() → setActionsAnchor(null) │ ├─ sessionKill(sessionId: string) │ ├─ POST /api/sessions/:id/kill │ └─ → { success: boolean, message?: string } │ └─ deleteSession(sessionId) ├─ mutates: sessions, sessionMessages, gitStatus, fileCache ├─ rebuilds: sessionListViewData └─ re-renders: SessionsListWrapper (data ref changed) ``` For data structures, show the shape and what depends on it: ```txt SessionRowData (flat primitives, cheap deep-equal) ├─ id, name, subtitle, avatarId ← identity + display ├─ state: SessionState ← collapsed from presence + agentState + thinking ├─ hasDraft: boolean ← collapsed from draft string ├─ activeAt?: number ← only inactive sessions (avoids heartbeat diffs) ├─ machineId, path, homeDir ← grouping in ActiveSessionsGroup └─ completedTodosCount, totalTodosCount │ consu...