Artifact f791bcfabe1a044aaa2070e1878cce1f8b96d96410830518dbf5c88e9e41d3e8:
- File
internal/api/register.go
-
2026-08-25 17:37:13
— part of check-in
[78fbef9d30]
on branch ops-phase
— ops: say what the forge is doing, not just how fast
The panels were steady-state numbers and said nothing while a fleet came up — which is the window an operator most wants to watch and the one where a forge most looks hung. A multi-repo re-ingest on this fleet was mistaken for a hang precisely because nothing said '23 of 25 stores ready' while it worked.
A phase banner leads the page: starting, indexing, syncing or rest, with stores ready over stores served, artifacts this session, the slowest recent round, and the names of what is rebuilding — which, not merely that something is.
Derived rather than tracked. Every store already reports Indexing, LastOK, LastCount, Total and Stalled; a phase field somewhere would be one more thing to keep true. The test ordering is the reader's priority: rebuilding outranks syncing, and a store that has never finished a round outranks both.
A stalled store is DONE waiting — it needs a person, not time — so it does not hold the fleet in 'starting' forever and does not sit in the bar as pending. Ready and stalled are drawn as two segments of one track, or the bar could never fill. (user: dmestas, size: 262060) [annotate] [blame] [check-ins using]
- 2026-08-25 19:03:21 — part of check-in [96b30ad4f5] on branch trunk — land ops-phase (user: dmestas, size: 262060) [annotate] [blame] [check-ins using]
-
2026-08-25 17:37:13
— part of check-in
[78fbef9d30]
on branch ops-phase
— ops: say what the forge is doing, not just how fast