docs: record activity split deployment

2026-07-15 15:32:29 +02:00
parent f1af1f909b
commit f0ef2654df
2 changed files with 41 additions and 10 deletions
@@ -23,16 +23,14 @@
  closes the old EventSource and opens the same session URL again. Failed Resume must not reconnect.
 - SSE endpoints are intentionally keep-alive. Browser cleanup and one-off probes must explicitly
  close the EventSource or cancel/abort the response reader after their terminal event.
- `activityLog` remains the complete in-memory chronological fold of prompt, thinking, assistant,
-  sanitized tool lifecycle, reviewer gates, status, and turn lifecycle. The left Model activity
-  panel is a strict projection of only thinking and status; prompt, gate, assistant, tool,
-  lifecycle, and unknown future kinds are hidden. While the model is working, the central body
-  projects every non-blank assistant transcript line into one bounded, accessible scrolling log;
-  user-entry echoes, timer/spinner labels, and step messages are not rendered there. Reviewer
-  widgets, artifacts, store folds, and workflow state continue to consume their existing events.
- F6 CTE cards keep their existing semantic structure and responsive grids while using 8 px
-  vertical padding, 12 px lateral padding below `sm`, and 16 px lateral padding from `sm` upward
-  for headers, content, table rows, and filter rows. Divider top padding is 8 px.
+- `activityLog` remains the complete in-memory chronological fold. The left Model activity panel
+  default-denies every kind except prompt, thinking, and assistant, presenting them as Question,
+  Reasoning, and Response in source order; status, tool, gate, lifecycle, and unknown kinds stay
+  hidden. Its desktop width is pointer/keyboard resizable from 288–576 px while preserving 512 px
+  centrally, persists globally in localStorage, and becomes an overlay drawer below `lg`.
+- F6 CTE cards keep their semantic structure, responsive grids, 12/16 px lateral padding, and 8 px
+  header/content edge padding. Internal section gaps are 12 px, headings/dividers use 4 px spacing,
+  and table/filter rows use 4 px vertical padding with compact line heights.
 - Pi tool events may cross the backend/client boundary only as call id, tool name, and
  `running`/`completed`/`failed` status. Tool updates, arguments, partial/final results, commands,
  raw output, and raw errors remain server-side.