docs: record central live log deployment

2026-07-15 12:31:57 +02:00
parent 09f9bdffe5
commit 4356a1243c
2 changed files with 39 additions and 4 deletions
@@ -25,9 +25,14 @@
  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: it renders only prompt, thinking, status, and gate; assistant,
-  tool, lifecycle, and unknown future kinds are hidden. The central transcript and workflow state
-  continue to consume their existing events independently.
+  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.
 - 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.