Spec: the Console, a web page for each machine's Commands

[JacobStephens2]

Summary

Closes #776

Each machine now serves its own authenticated Console. The seven pages and CLI share Command observations, Inbox grouping, Silent/Slow health, stage Usual ranges and exact log ownership. CI watch and Self-merge emit waiting lines; Setup offers the Console and an owner-run installation script.

Command records + Activity / Command / Session logs
  shared blocking reader
    status / show / logs / stop
    Console on localhost
      Inbox · Lanes · Stages · Waterfall · History · Logs · Security
      email/password accounts · Stop/Requeue · machine-wide Themes
Setup → console install → owner-run service + reverse proxy

Includes live conversation readers for Claude/Codex, keyboard navigation and peeks, authenticated Stop/Requeue, durable accounts and email password codes, the Console log, six built-in Theme families, custom Theme import/export and confined local fonts. Assets are embedded; the release build needs no Node or CDN. Console updates re-exec the replaced binary. The page writes only Stop, its own look and Theme files.

Evidence

Seams under test:

• The CLI binary reading fixture Command records and logs, with observable status JSON and text.

• The running Console over HTTP, including authenticated actions and appended log batches.

• The Console in Playwright, including DOM preservation and recovery when streaming fails.

• Before: a ready Run dispatched by a Pass had no top-level Ready for review row. After: the retained CLI/HTTP reproduction passes; the complete Pass tree remains in History and show.

• Before: a Session reader stayed frozen for the reproduction's 12-second wait when SSE failed. After: finite offset-based polling appends lines while preserving existing DOM nodes. Both recovered-SSE and pending-poll overlap reproductions changed from two copies of a line to one.

• Before: the seven-page header reproduction failed on Logs. After: shared PageContext and header markup keep the machine and other-Console links on all seven pages, log readers and Stop.

• Removed source-regex parity and invented-markup CSS checks, retaining registered-router parity and served-page coverage.

• Validation: 35/35 Console Playwright tests, ready/header reproductions, three standalone streaming regressions, formatting and Clippy pass. The full Rust run passed units (1,081 passed, two ignored) and all binaries before status, then found one outdated row-count assertion. After correcting it and checking the promoted child tree, all 26 status tests and the four remaining binaries passed; Clippy passed again. The full command was not restarted after this test-only correction.

Unaddressed findings

Standards

• J2, browser fixture lifecycle duplication — declined judgment. console/tests/accounts.test.cjs:12, console/tests/logs.test.cjs:14 and the per-test custom-Theme setup own different authentication, process/log and configuration lifetimes. The implementation decision is to keep those fixture owners explicit rather than introduce a generic lifecycle interface. No behavioral defect was asserted; the independent followup accepted this rationale.
• J3, common Entry facts — declined judgment. src/logs/reading/inbox.rs:109 computes readiness/cause for grouping; src/logs/status/inbox.rs:92 computes repository/outcome filters; src/logs/status/time.rs preserves unknown historical stage evidence. These policies remain with their presenters. The ready-row fix reuses the existing Observation interface where behavior is shared. The independent followup accepted this rationale.

The page-context/data-clump judgment was addressed with PageContext and header.html. A universal HTML base remains optional: shared nav/chrome already own controls; Inbox's htmx/attention head and time/log heads load different resources and metadata.

Spec

• 3 / P2, Codex edits lack unified diffs — retained for the Day shift in #854, already open with only needs-triage. python3 console/reproductions/codex-edit-diff.py was run and failed because real retained Codex file-change events contain only path/kind, not old/new text. src/console/conversation.rs preserves the event and explicitly says the patch is unavailable. Issue Decide Codex patch evidence retention for Console edit diffs #854 records the finding, evidence and originating PR Add Console log inventory and live conversation readers #853; this whole-Spec review raises the same gap on Spec: the Console, a web page for each machine's Commands #842. Choosing genuine patch capture, retention format and historical behavior changes the recording contract and belongs to the Day shift. The reproduction remains; this requirement is incomplete.

Security review outcome

• Security review refused: Codex's cybersecurity safeguard refusal

Review coverage

Both independent reviewers inspected all 153 original changed paths across the whole Spec, including vendor text, licenses and lockfiles. The 15 WOFF2 assets received metadata inspection; font outlines were not source-reviewed. No generated-output exclusions were taken.

Standards also read all three added review-fix files. The independent Spec reviewer did not inspect src/console/header.html and console/reproductions/header-machines.py: these two paths remain unread on that axis. Both were read by Standards and the primary reviewer, and their served-page reproduction passes. No other changed path remains unread. Final files-read inventories and dispositions are written to .thirdshift-review-C0SjsM/standards.md and .thirdshift-review-C0SjsM/spec.md in the review workspace.

Merge Danger

Door: two-way

The binary can be rolled back. Accounts, Console log and custom Themes persist beside the User config. Stop interrupts real Commands and changes issue labels.

Blast Radius: machine

Adds a persistent Console behind the owner's proxy and changes machine-wide status grouping, health, Setup and waiting-line behavior.

Built with codex · gpt-6.1-sol · high

Tickets

• Waiting lines in CI watch and Self-merge #814 landed with Keep CI watch and Self-merge waiting lines active #841
• Silent, Slow and the Usual range in status and show #815 landed with Show Silent and Slow Runs with repository Usual ranges #844
• The Inbox's groups in thirdshift status #816 landed with Show the machine’s Inbox in thirdshift status #848
• thirdshift console --no-sign-in serves the Inbox #817 landed with Serve the localhost Console Inbox with Focus #850
• A live Inbox: server push, heartbeat and tab title #818 landed with Keep the Console Inbox live #855
• Session log and Command log views, and the Logs page #819 landed with Add Console log inventory and live conversation readers #853
• History, Security, the peek and the keyboard model #820 landed with Add History, Security, the peek and Console keyboard navigation #856
• Console accounts and sign-in #821 landed with Add Console accounts and sign-in #860
• Set your password by email code #822 landed with Set Console passwords by email code #868
• Stop from the Console #823 landed with Stop live Commands from the Console #869
• Built-in Themes, the picker and the page's own look #824 landed with Add Console Themes, saved look settings and activity motion #870
• Your own Themes and fonts #825 landed with Add custom Console Themes and local fonts #895
• The Lanes and Stages pages #826 landed with Add Console Lanes and Stages pages #861
• The Waterfall page #827 landed with Add the Console Waterfall page #863
• thirdshift console install #828 landed with Add Console service and proxy installation scripts #872
• Setup's Console questions #829 landed with Ask about the Console during Setup #874