ops-fleet

# OPS ► FLEET Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). Unified, read-only operational dashboard for: - local Claude Code sessions and daemon state; - the configured CLIProxyAPI gateway; - the effective model catalog grouped by provider; - the canonical server-side auth-record pool and configured load-balancing policy; - recent inference-only request, error, and latency signals; - optional legacy local account-rotator utilization. It renders state and never changes it. It does not consume the CLIProxyAPI usage queue, modify configuration, refresh credentials, switch accounts, or restart services. ## Runtime sources | Layer | Source | Truth represented | |---|---|---| | Claude sessions | `claude agents --json` | live interactive/background session census | | Claude daemon | `claude daemon status` | local supervisor/socket state | | Gateway | `GET /` | CLIProxyAPI server identity, reachability, latency | | Models | authenticated `GET /v1/models` | effective client-visible model catalog | | Pool | sanitized helper/command JSON | enabled/disabled/backup auth records, configured routing/retries, recent inference RED signals | | Legacy rotator | local state file, opt-in | compatibility utilization only; not canonical gateway pool truth | A protected model endpoin...