3 Commits

Include renames

Author	SHA1	Message	Date
Omar SobhandClaude Opus 4.8	3554a3aaf2	CI: remove k8s stages, fix the Docker-level pipeline green ... Survey + fixes so the pipeline passes at the Docker level (no k8s). - Remove k8s: drop the `sandbox-k8s` job (kind/Calico/--features k8s-tests) and the "Helm chart lints" gate step. release.yml was already k8s-clean. - Rust job: - `cargo fmt --all` — fix pre-existing formatting drift (fmt --check was failing). - clippy -D warnings: fix 3 lib warnings (cm-brain sort_by_key→Reverse, cm-api fleet.rs doc list indentation, node_rules map_or→is_none_or). - Regenerate the .sqlx offline cache (was missing the cm-runtime run_loop test query → offline compile failed). DB-backed tests use testcontainers at runtime. - Set SQLX_OFFLINE=true on the rust + e2e jobs so query! macros compile against the committed cache deterministically (no DB needed at compile time). - Frontend job: - Fix the 1 ESLint error (useAgentTelemetry: no setState-synchronously-in-effect; tag the slice with agentId + derive null on mismatch). - Fix 2 stale panel-params tests (`terminal` is a valid app id now; assert the current APP_IDS + use a genuinely-unknown id for the reject case). Verified locally: fmt clean, clippy --all-targets -D warnings clean (offline), frontend lint 0 errors, tsc clean, 86/86 frontend tests pass, build OK. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>	2026-06-26 18:15:31 -07:00
Omar SobhandClaude Opus 4.8	c94784bab2	Fleet: actionable executions — rules engine + metrics-aware placement (Phase 2) ... Turn the Beszel-tapped metrics into a self-managing loop. - migration node_rules (workspace/node-scoped: metric op threshold, for_seconds, action JSONB, last_fired). - cm-db: repo/node_rules.rs (CRUD + list_enabled); node_metrics::eval_all merges Beszel + heartbeat scalars per node + a headroom() heuristic; nodes::status_of; heartbeat now PRESERVES a `draining` status across heartbeats (so a cordon sticks). - cm-api: node_rules.rs evaluator (spawn_evaluator, 20s) — when a metric condition holds for the rule's window it fires drain / undrain / alert (in-memory sustained + cooldown tracking, modeled on the node sweeper); routes/beszel.rs rules CRUD (GET/POST/PATCH/DELETE /api/fleet/rules); spawned in clawmates-server. - cm-runtime: placement_node() is metrics-aware — a `draining` node stops receiving new agent sandboxes (falls back to local), so the drain rule is actionable. - frontend: FleetRules section in the Local view — build rules (node · metric · op · threshold · duration → action), toggle/delete, with fired-history. The loop: hot/overloaded node → rule drains it → placement avoids it → recovers → undrain rule brings it back. Deployed; node_rules migration applied. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>	2026-06-25 23:43:49 -07:00
Omar SobhandClaude Opus 4.8	36a227566b	Fleet: Beszel hub integration — rich per-node metrics + per-node monitor (Phase 1) ... Tap each node's Beszel metrics (GPU/temps/disk-IO/network/per-container — beyond our basic heartbeat) by reading the workspace's Beszel hub. The agents run in WS-only mode with no locally-readable socket, so (per the de-risk) the server taps the hub's PocketBase API instead of the daemon reading agents — no daemon changes. - migrations: workspace_beszel (BYO hub URL + login, server-side only, mirrors the Tailscale BYO pattern) + node_metrics (latest scalar columns + JSONB blob). - cm-db: repo/fleet_beszel.rs, repo/node_metrics.rs; nodes SELECT joins node_metrics (gpu_pct/temp_max surfaced on node_json for the live cards). - cm-api: beszel.rs client (auth-with-password, poll `systems`, map to nodes by hostname, upsert metrics) + a 15s spawn_poller; routes/beszel.rs (connect/status/ disconnect + GET /api/nodes/{id}/metrics with history proxied live from the hub). - frontend: HostCard gains a GPU/temp readout + a Monitor button; NodeMonitor is a full-width per-node page (current panel + CPU/mem/GPU/temp/net/disk charts from the hub's 1m history); a "Beszel monitoring" connect form in the Local view. Reachability confirmed: gw-04 → the hub over the tailnet (100.123.224.84:8090). Needs the user to connect their hub login to activate the poller. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>	2026-06-25 23:28:29 -07:00