feat: streamline structured transcript

docs/STRUCTURED-VIEW.md

@@ -164,8 +164,14 @@ choices, not daemon ones.
 - How each row kind is drawn — markdown for `AgentText`/`AgentThought`, a
   diff view for `ToolDiff`, a tool card for `ToolCall`, and a floor
   presentation for `Notice`. `Plan` is the exception: both clients omit it
-  from the transcript entirely and render the current plan in a separate
-  plan rail (web) / status line (TUI) instead.
+  from the transcript; the TUI may show the current plan in its status line,
+  while the web client deliberately has no stats or plan rail.
+- The web client groups two or more tool rows after the same `User` row into
+  one collapsed turn activity block. Opening it reveals independently
+  expandable tool calls, including any raw command, input, output, and diff
+  content the adapter supplied.
+- The web client's user, agent, thought, tool-detail, and notice text blocks
+  copy their complete source text when clicked or keyboard-activated.
 - How `responding` vs. `thinking` are distinguished visually, if at all.
 - How the operator is asked to resolve an `Approval` row — the daemon only
   exposes the three-way decision (`AllowOnce` / `AllowForSession` / `Deny`),