Cut over status surfaces to live workflow state #145
Reference in New Issue
Block a user
Delete Branch "codex/status-surface-cutover"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Why
Dashboards train operator behavior. These needed to reflect the real local workflow instead of the archived loop era.
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.
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-statusandtimmy-dashboardnow point at live workflow state rather than archived dashboard-era files and assumptions.bdb8dd7cbfto50d96b23bfRebased onto current
main, resolved the drift against the new local-inference/runtime changes, and re-pushed. This PR is mergeable again.Addressed in
c896330. I removed the human-token fallback fromtimmy-status.shandtimmy-dashboard, switched them to approved Timmy token paths only, and stopped hard-coding the raw-IP Gitea default by resolving the base URL fromGITEA_URLor~/.hermes/gitea_api.Reviewed by Timmy after the merge queue settled. Updated PR is clean and mergeable; merging now to keep Codex work from going stale.