docs(agent-page): document the running bash-tasks pill + flyout

docs/web-ui/agent.md

@@ -61,6 +61,11 @@ through. Three flex columns:
     the inbox flyout in the side panel.
   - **Loose-ends pill** (`🪢 loose ends · N`): hidden when empty;
     click opens the loose-ends flyout.
+  - **Tasks pill** (`⚙ tasks · N`): hidden when empty; click opens the
+    running-bash-tasks flyout (`GET /api/bash-tasks` — the in-flight
+    Pending/Running tasks from the in-container `bash-tasks/` dir). Polled
+    on the same `/api/state` cycle as loose-ends, since tasks complete
+    asynchronously between turns. Snapshot only (no SSE push yet).
   - **Overflow button** (`⋯`): always visible. Opens a frosted popover
     (`#overflow-menu`, positioned outside the header to escape any
     stacking context) with four management rows followed by a model
@@ -149,7 +154,11 @@ will reflect zero. Loose-ends flyout: questions,
 approvals, and reminders pending against this agent (`GET /api/loose-ends`);
 question rows carry an inline answer form that POSTs cross-origin to
 the core dashboard's `/answer-question/{id}` so the operator answers
-*as operator* (see `docs/boundary.md`).
+*as operator* (see `docs/boundary.md`). Tasks flyout: in-flight bash
+tasks (`GET /api/bash-tasks`); each row shows status (`▶ running` /
+`◷ queued`), the task id, elapsed time, and a truncated one-line
+command preview. Read-only — kill/inspect lives in the harness, not
+the page.
 
 **Ask → operator inline-answer binding.** When the agent emits
 `mcp__hyperhive__ask(to: "operator", ...)`, the tool_use renderer