Session log and Command log views, and the Logs page #819

Parent

#776

What to build

The Console reads logs, through the Logs page (page 6) and from any Command.

• Command logs are shown as plain text.
• Session logs are rendered as a conversation. The page reads Claude's stream-json and the codex exec --json output thirdshift keeps, and turns Codex items into the same shape.
  • Consecutive tool calls fold into one group.
  • Thinking is collapsed.
  • Each tool has its own renderer, over a plain fallback: Bash, Edit as a unified diff, Read and Grep come first.
  • Unknown events are shown plainly, never hidden.
• A live Session log has its own stream, which sends rendered HTML for lines appended since a byte offset. Only those lines are added; the log is never redrawn. You choose whether the view follows the newest line.
• A Ticket's Run and its Session logs are reachable from its Spec run.
• The Logs page lists every Session log and Command log on the machine, live ones marked, with a reader. It's paired with thirdshift logs in the parity test.

Only the current log layout is read. Session logs in the old sessions/ folder aren't linked.

Acceptance criteria

• Claude and Codex Session logs both render, with folding, collapsed thinking, a renderer per tool, and the fallback for unknown events.
• Appending lines to a live fixture log streams only the new lines from the byte offset.
• Following the newest line can be turned on and off.
• The Logs page lists every log, live ones marked, and is paired with logs.
• The renderers are tested against real-shaped logs with made-up content.
• Playwright checks a live log gaining lines without a redraw.