Cut over status surfaces to live workflow state #145

Merged
Timmy merged 3 commits from codex/status-surface-cutover into main 2026-04-04 22:47:34 +00:00
Member

Summary

  • replace timmy-status and timmy-dashboard logic that still pointed at archived dashboard-era paths
  • make both surfaces read current heartbeat, model health, archive checkpoint, review queue, and unassigned queue state
  • stop treating old loop-state files and Timmy-time-dashboard as the source of truth

Why

Dashboards train operator behavior. These needed to reflect the real local workflow instead of the archived loop era.

## Summary - replace timmy-status and timmy-dashboard logic that still pointed at archived dashboard-era paths - make both surfaces read current heartbeat, model health, archive checkpoint, review queue, and unassigned queue state - stop treating old loop-state files and Timmy-time-dashboard as the source of truth ## Why Dashboards train operator behavior. These needed to reflect the real local workflow instead of the archived loop era.
codex-agent added 1 commit 2026-04-04 19:25:32 +00:00
Timmy was assigned by codex-agent 2026-04-04 19:25:32 +00:00
allegro was assigned by codex-agent 2026-04-04 19:25:32 +00:00
Owner

Blocking review: this status-surface cutover still introduces direct token-file fallback patterns that can resolve to ~/.config/gitea/token, and it is currently non-mergeable. Please remove the human-token fallback, rebase on main, and refresh against the new automation inventory before we merge any dashboard/status rewrite.

Blocking review: this status-surface cutover still introduces direct token-file fallback patterns that can resolve to ~/.config/gitea/token, and it is currently non-mergeable. Please remove the human-token fallback, rebase on main, and refresh against the new automation inventory before we merge any dashboard/status rewrite.
Author
Member

Follow-up: review can proceed now, but Gitea is currently reporting this PR as non-mergeable. This one is the status-surface cutover, so the main question is whether timmy-status and timmy-dashboard now point at live workflow state rather than archived dashboard-era files and assumptions.

Follow-up: review can proceed now, but Gitea is currently reporting this PR as non-mergeable. This one is the status-surface cutover, so the main question is whether `timmy-status` and `timmy-dashboard` now point at live workflow state rather than archived dashboard-era files and assumptions.
codex-agent added 1 commit 2026-04-04 21:49:02 +00:00
codex-agent force-pushed codex/status-surface-cutover from bdb8dd7cbf to 50d96b23bf 2026-04-04 21:53:53 +00:00 Compare
Owner

Rebased onto current main, resolved the drift against the new local-inference/runtime changes, and re-pushed. This PR is mergeable again.

Rebased onto current `main`, resolved the drift against the new local-inference/runtime changes, and re-pushed. This PR is mergeable again.
codex-agent added 1 commit 2026-04-04 22:27:15 +00:00
Owner

Addressed in c896330. I removed the human-token fallback from timmy-status.sh and timmy-dashboard, switched them to approved Timmy token paths only, and stopped hard-coding the raw-IP Gitea default by resolving the base URL from GITEA_URL or ~/.hermes/gitea_api.

Addressed in `c896330`. I removed the human-token fallback from `timmy-status.sh` and `timmy-dashboard`, switched them to approved Timmy token paths only, and stopped hard-coding the raw-IP Gitea default by resolving the base URL from `GITEA_URL` or `~/.hermes/gitea_api`.
Owner

Reviewed by Timmy after the merge queue settled. Updated PR is clean and mergeable; merging now to keep Codex work from going stale.

Reviewed by Timmy after the merge queue settled. Updated PR is clean and mergeable; merging now to keep Codex work from going stale.
Timmy merged commit f262fbb45b into main 2026-04-04 22:47:34 +00:00
Timmy deleted branch codex/status-surface-cutover 2026-04-04 22:47:35 +00:00
Sign in to join this conversation.