Skip to content

Show program health, owner liveness, and a compact Inbox on the command center - #185

Merged
sreejithraman merged 7 commits into
refactor/coordinator-keep-movingfrom
feat/coordinator-command-center
Nov 15, 2026
Merged

sreejithraman merged 7 commits into
refactor/coordinator-keep-movingfrom
feat/coordinator-command-center

Conversation

@sreejithraman

Copy link
Copy Markdown
Owner

The coordinator's command center now tells you, at a glance on a phone, whether the program needs anything, what each piece of work is doing right now, and how stale the page is. The Inbox takes about half the scroll it did.

Stacked on #183 (refactor/coordinator-keep-moving), which sits on #182. PR 4, the Inbox prototype, will stack on this one.

Summary

  • Health strip. The page opens with the status verdict and four counts: owners running, idle while owing work, ready but not started, and ready to land. It also shows the oldest Inbox item with its age, and the record's next. The renderer computes these with the same assess function status uses. To allow that without a circular import, the pure assessment helpers moved unchanged from record.py into render_dashboard.py.
  • Owner liveness. status now records each owner thread's state in a new optional owner.seen field: running, idle, or unreadable, with when it was read and any pending approvals. An owner status has not read yet shows as not observed and doesn't count as idle. status --turn-end now also fails while a live owner state differs from the record, so a turn can't end with the page showing a stale verdict. The renderer reads only the record and never calls gh or t3.
  • A "now" line per work card. One sentence says what is happening or what the work waits on, under the owner's last observed state. It follows status's own findings first: a running owner or a provisional start outranks a halting Need.
  • Record stamp. The masthead shows the record commit the page renders and its local time and age, so a page behind the record shows an older commit.
  • Compact Inbox. Options are one pick list with one Copy answer action. The recommended option is pre-picked. Each prompt keeps its Decision "<id>" (revision <rev>) line exactly. A pick survives a republish until its decision changes. Each open item shows how long it has waited. The batch prompt stays. Settled sections start closed. Option rows leave room for PR 4's per-option pictures.
  • Result cards. A result with a picture shows a thumbnail. Otherwise it shows a link card with its host.
    • report copies an owner's shown image into the program's files/, named by content hash, and commits it with the record.
    • render_dashboard.py --page writes each committed image beside the page and lists it.
    • references/hosting.md says to publish each listed image with publish_files; prepare_sites.py copies them for Codex Sites.
  • Finished section. Landed, done, and scrapped work collapses into one closed section with a count.
  • Local times everywhere. Bare dates stay their own calendar day, and tooltips are local too.

Evidence

Before and after, iPhone width (390 px), same example program:

Before After
Inbox, about 4,480 px tall Inbox with the health strip, about 3,070 px tall
  • python3 scripts/check.py passes locally. That includes 143 coordinator tests, some of them in headless Chrome. The tests catch:
    • a missing health strip count;
    • a UTC string outside a local <time>, or in a tooltip west of UTC after the script runs;
    • a lost Need revision in a copied answer;
    • landed work outside a closed Finished section;
    • page counts that differ from status --json;
    • a turn end that passes while the record holds a stale owner state;
    • a failed report commit that leaves an image behind;
    • an edited image that a report or a page render would overwrite.
  • I mutation-checked the four required catches. Breaking each behavior fails its test.
  • A real run against a scratch program:
    • report with an image, then status with the real gh and T3 CLI. This thread's real session was recorded as running.
    • The staged page's verdict and counts matched status.
    • The thumbnail loaded in Chrome from files/.
  • I did not publish to a live Claude artifact. The artifact server's rules state that "a page published from files may also load its own files by relative path."

Merge Danger

Two-way door. The new record fields (owner.seen, results[].image) are optional, so older records still validate and render. A revert restores the old page. A record written after this change would then fail the old validator on owner.seen until that field is removed. status already commits each run that reads something new; a thread that stays unreadable adds no commit. The page changes whenever a wait, next, or an owner's observed state changes, so the coordinator publishes a little more often. This layer touches only skills/coordinator and SOURCES.md.

🤖 Generated with Claude Code

sreejithraman and others added 6 commits November 15, 2026 13:59
…center

The page now opens with the status verdict and its counts, computed from
the recorded facts with the same function status uses. status records each
owner thread's state in owner.seen, and each work card says what is
happening now and how its owner was last seen. The masthead names the
record commit the page renders.

Inbox options become one pick list with a single answer action, and each
open item shows its age. Landed, done, and scrapped work collapses into one
closed Finished section. Results render as cards, with a thumbnail when the
owner showed a picture: report copies it into the program's files/, and
the renderer serves it beside the page by content name. Every time reads
in the viewer's time zone, including bare dates and tooltips.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner thread states now stand whichever forge facts status keeps, and
carry pending approvals so the page shows what status finds. The now line
follows status's own action before raw holds: a running owner or a
provisional start outranks a halting Need, and an idle owner outranks a
Need that lets work continue.

Result images keep one content name from report to page, and staging
refuses an image that differs from its commit. Saving a report with
images is all or nothing. A pick survives a republish until its decision
changes. Small cuts: one clock, one image type list, no dead hooks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A report no longer overwrites a hand-edited image under the same content
name; it refuses before writing, as page staging already did.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Turn end now fails while a live owner state differs from the record, so the
published health strip matches the state the turn ended on. An owner status
has not read yet is no longer counted idle, start drops an old thread's
sighting, and a thread that stays unreadable keeps when it became so.

Also clean up an interrupted image write, leave index entries alone on a
refused report, and keep the manual copy box on the current pick.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sreejithraman
sreejithraman added this pull request to stack #184 November 15, 2026 20:18
The settled Inbox section read "Chief decided" and its cards "Chief's call"
after the skill's rename. A test now keeps "Chief" out of the page's text.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sreejithraman
sreejithraman merged commit 62bbafd into main Nov 15, 2026
3 checks passed
@sreejithraman
sreejithraman deleted the feat/coordinator-command-center branch November 15, 2026 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant