ops-dashlisted

# OPS > DASH — Interactive Command Center ## Runtime Context Before rendering, load available context: 1. **Preferences**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` - `owner` — personalize the dashboard header greeting - `timezone` — display timestamps correctly in status indicators 2. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json` - If `action_needed` is not null → show a warning banner at the top of the dashboard before the menu ## CLI/API Reference ### bin/ops-dash | Command | Usage | Output | |---------|-------|--------| | `${CLAUDE_PLUGIN_ROOT}/bin/ops-dash` | Render hybrid live command center | 12-section live dashboard | | `${CLAUDE_PLUGIN_ROOT}/bin/ops-dash 2>/dev/null \|\| echo "DASH_RENDER_FAILED"` | Render with failure detection | Dashboard or `DASH_RENDER_FAILED` sentinel | | `OPS_MOBILE=1 ${CLAUDE_PLUGIN_ROOT}/bin/ops-dash` | Plain-text compact mode (SSH/mobile) | No ANSI boxes, single-line sections | The bin script fires all 12 data probes in parallel (background subshells writing to a tmpdir), renders an animated loading bar while they run, then renders sections sequentially top-to-bottom. Each section degrades to `(no data)` if its probe fails — the script never crashes. **Live data rendered per section:** 1. **HERO** — pixel-art logo (gradient cyan→violet), vitals strip: fires · unread · PRs · MRR · GSD active 2. **FIRES** — CI failures across registry repos (via