Live control surface for infrastructure health, user account posture, scan throughput, and the config shared by Telegram and the web UI.
Dependency checks for the data plane, model runtime, Telegram polling loop, and configured fallbacks.
Aggregated from the `scan_metrics` table across UI and Telegram traffic.
Live ping against `/api/tags` on the configured server.
The active configuration row shared by the admin portal and Telegram bot.