Description
## Observations
### Sessions tab
The sessions history tab does not display the **head** (kiosk) nor the **experience** associated with each session. These are the two most important pieces of context when reviewing session history — operators need to know which head ran which experience.
Additionally, the sessions tab does not auto-refresh. When there is an active stream, the tab should poll and refresh every 5 seconds so operators see new session data without a manual page reload.
### Stream menu / active stream visualisation
The stream menu (the panel with the green arrow indicating an active stream) has no indication of which session is currently running. A natural place would be a label centred on or near the green arrow showing the session identifier (or head + experience inline).
## Investigation questions
1. What fields does the streaming monitor receive per session — does the session payload already carry head ID / name and experience ID / name, or does it need to be fetched from HydraCluster?
2. If the data is available, is it just a rendering gap in the sessions tab template?
3. For the stream menu label: what is the current data model for an active stream — is the session linked there already?
4. How is active stream state currently detected client-side — can the same signal drive the 5-second refresh toggle?
## Suggested approach
1. Audit the session data model in `hydrastreamingmonitor` — check what fields are stored/displayed for a session.
2. If head and experience are already in the model, add them to the sessions tab table columns (head name, experience name).
3. If not, determine the join point (likely HydraCluster API or the stream start event payload) and enrich the session record on ingest.
4. For the stream menu: add a small centred label on the green arrow showing `<head> — <experience>` (or just the session ID as a fallback) so operators can see at a glance what is streaming and to which head.
5. Keep the label concise — truncate long experience names with an ellipsis.
6. Add a 5-second client-side refresh of the sessions tab that activates only while an active stream is detected (stop polling when idle to avoid unnecessary load).
## Acceptance criteria
- Sessions tab shows head name and experience name for every session row.
- Active stream in the stream menu displays a label (head + experience or session reference) centred on/near the green arrow.
- Sessions tab auto-refreshes every 5 seconds when there is an active stream; stops refreshing when no stream is active.
- No new external HTTP calls between services — data must flow through existing NATS/Wind channels if enrichment is needed.