- Connector: moved from per-entry pseudo-elements to a single linear-gradient line on the body. Fades in/out 28px at each end and no longer has gaps at entry boundaries. Dots and the date rect's solid background sit naturally on top; everything else stays transparent so the line threads through cleanly. - Layout: entry is now a 2-row grid. The optional date rect lives in row 1 (justify-self:start, left-aligned), while the dot-row and the events column both pin to row 2 so the time label always lines up with the first event of the cluster — even when a date rect sits above. Time+dot `align-self: start` keeps them at the top of the event section instead of vertically centred through the whole cluster. - Filters: state.timelineFilter is a Set now, so clicking multiple workload pills (or the overflow entries) stacks them as an any-of filter. "all" clears the set. The overflow dropdown stays open on pick so several can be toggled without reopening it each time. Scope label shows "filtered · N" with the active count. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
oumta-dashboard plugin
Fullscreen view for the Oumta cluster dashboard (Go backend in oumta-dashboard/).
Open
- Oumta button in the hyprcrd top bar (next to Tasks)
window._oumtaToggle()from the console / other plugins
Close with ESC or the × button.
Views
- Overview — cluster state, workload counts, attention list
- Workloads — filterable table (name, state, replicas, cpu/mem, image, reason)
- Timeline — event stream; clicking a workload filters down to its own events
Namespaces
Tab row at the top. Currently two mocks (oumta-dev, oumta-beta). Real list comes from the backend once /api/namespaces exists.
Configuration
Hardwired at the top of oumta-dashboard.js in the CONFIG block:
- baseUrl — where the Oumta Go backend is reachable (default
http://localhost:8085). - authToken — optional, sent as
Authorization: Bearer …when non-empty. - pollIntervalSec — polling fallback cadence when SSE is unavailable. Default 15 s.
No UI settings panel: the dashboard only runs against one specific deployment, so exposing these as editable fields would be noise.
State today
Everything is mocked. The live indicator in the top right shows polling once the overlay is open, but no real HTTP call fires yet. See TODO.md for the integration plan.
Disabling
Add "oumta-dashboard" to the disabled array in data/plugins.json.