feat: add cc-connect dashboard health integration

Add a protected backend health endpoint and a new dashboard page/sidebar entry so cc-connect operational status is visible in the UI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-02 23:24:03 +08:00
parent e76f15c432
commit 14965c7e03
8 changed files with 242 additions and 2 deletions
@@ -176,11 +176,12 @@ nas-tools/
 ### Phase 14 — Hybrid AI Gateway (LiteLLM + cc-connect) 🚧
 49. ~~Add `litellm/` service scaffold (`docker-compose.yml`, `config/litellm.yaml`, `.env.example`) with localhost-only host binding and env-driven provider keys~~ — Done
 50. ~~Add dashboard backend LiteLLM operational probe (`/api/litellm/health`) and wire into protected routes~~ — Done
-51. Add `cc-connect/` templates (`README.md`, `config.example.toml`, optional compose) for mobile bridge rollout
+51. ~~Add `cc-connect/` templates (`README.md`, `config.example.toml`, optional compose) for mobile bridge rollout~~ — Done
 52. ~~Deploy LiteLLM image to NAS using server2 pull + stream load workflow to avoid slow GHCR pulls on NAS~~ — Done
 53. ~~Network fix: attach LiteLLM to `nas-dashboard_internal` and set dashboard-dev `LITELLM_URL=http://litellm:4005`~~ — Done
 54. ~~Update backend health probe to support auth-required mode and configured health auth key~~ — Done
 55. ~~Add LiteLLM dashboard UI page with sidebar link and health status card~~ — Done
+56. ~~Add cc-connect dashboard UI page, sidebar link, and backend health/status endpoint~~ — Done

 ### Phase 13 — Off-site Backup
 46. Add cloud backup (OneDrive or Google Drive) for critical data