# 02 — Deliver the Operations Console dashboard

**What to build:** Give users the accepted Operations Console experience: a stable, scannable Target list and concise selected-Target details, side by side on wide terminals and stacked on narrow terminals.

**Blocked by:** 01 — Build the responsive TUI foundation.

**Status:** done

- [x] The header shows a compact proxyctl identity, the Active Profile, and counts for the current Target states.
- [x] Available Targets appear in stable product order by default.
- [x] A contextual action reveals unavailable Targets and their detection evidence without changing product order.
- [x] Each Target row combines a standard Unicode/ASCII-safe symbol, explicit state text, and semantic styling.
- [x] The selected Target details prioritize state, evidence, affected scope, permissions, ownership/restoration implications, and restart risk.
- [x] Wide terminals show Target list and details panes side by side; narrow terminals stack the same regions.
- [x] Tab changes pane focus, the focused pane is visible without relying only on color, and arrows navigate within the focused pane.
- [x] Long Target lists and details remain reachable through list/viewport scrolling.
- [x] The footer shows only actions valid for the current focus and state.
- [x] Resizing preserves selection by Target identity rather than fragile row position.
- [x] Complete-Model tests cover every Target state, unavailable visibility, long content, focus, scrolling, and wide/narrow rendering.
- [x] Production rendering is rewritten from the spec; prototype branch `prototype/tui-operations-console` commit `364f28d` is reference material only and is not copied into production.