proxy/.scratch/tui-redesign/issues/02-operations-console-dashboard.md

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

• The header shows a compact proxyctl identity, the Active Profile, and counts for the current Target states.
• Available Targets appear in stable product order by default.
• A contextual action reveals unavailable Targets and their detection evidence without changing product order.
• Each Target row combines a standard Unicode/ASCII-safe symbol, explicit state text, and semantic styling.
• The selected Target details prioritize state, evidence, affected scope, permissions, ownership/restoration implications, and restart risk.
• Wide terminals show Target list and details panes side by side; narrow terminals stack the same regions.
• Tab changes pane focus, the focused pane is visible without relying only on color, and arrows navigate within the focused pane.
• Long Target lists and details remain reachable through list/viewport scrolling.
• The footer shows only actions valid for the current focus and state.
• Resizing preserves selection by Target identity rather than fragile row position.
• Complete-Model tests cover every Target state, unavailable visibility, long content, focus, scrolling, and wide/narrow rendering.
• 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.