Live flow diagram on web dashboard

[alekb]

When I’m watching a long run on the --serve dashboard, I keep wanting a small visual of where in the pipeline the current session actually is. The flow diagram in the README (assets/ralphex-flow.png) is the mental model I already have — right now I have to read the stream to figure out which phase we’re in.
Idea: render that diagram as inline SVG, pinned under the session list in the left sidebar. Completed phases get a checkmark, current phase highlights, upcoming stay muted. Switching sessions updates it to reflect that session’s state.

From the docs it looks like phase transitions are already first-class (SetPhase on BroadcastLogger, the pkg/status package), so the SSE stream might already carry what’s needed — haven’t read the code yet though, could be wrong.

Would you accept a PR for this? Any scope opinions up front — config flag, on by default, etc.? Happy to keep the first cut minimal (just current-phase highlight) and iterate.

[umputun]

the inline-svg flow diagram is heavier than I'd want to land for this. The dashboard already has a .phase-nav at the top of the main wrapper (pkg/web/templates/base.html:48-56) with tabs labeled All / Implementation / Claude Review / Codex Review. Those map 1:1 to the phases in pkg/status/status.go. The simplest thing that gets you the orientation you're after: a small indicator (colored dot, or a subtle background tint) on whichever tab matches the current live phase, separate from the active class that controls filtering. The tab keeps its filter behavior; the indicator is purely a status hint.

you're right that the SSE stream already carries phase data. Every event has a phase field, so no Go changes needed. Frontend listener flips a CSS class on the matching .phase-tab when phase events arrive. ~10 lines CSS + ~5 lines JS, no new HTML element.

scope:

• on by default, no config flag (small visual cue, not worth a knob)
• start there. If after shipping that you still want a fuller diagram or completed-phase checkmarks, separate iteration
• pure frontend, no Go changes

happy to take a PR for this shape.