2 Commits

Author	SHA1	Message	Date
Kyle Isom	3b08caaa0a	Add [master] config section to agent for registration ... Heartbeat client now reads master connection settings from the agent config ([master] section) with env var fallback. Includes address, ca_cert, token_path, and role fields. Agent's Run() creates and starts the heartbeat client automatically when [master] is configured. Tested on all three nodes: rift (master), svc (edge), orion (worker) all registered with the master and sending heartbeats every 30s. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-04 13:53:15 -07:00
Kyle Isom	6351b68ef6	Add agent registration, heartbeats, and monitoring (Phase 4) ... Master side: - Register RPC: identity-bound (agent-rift → rift), allowlist check, max nodes limit, upserts node in registry, updates agent pool - Heartbeat RPC: derives node name from MCIAS identity (not request), updates container count and last-heartbeat timestamp - HeartbeatMonitor: background goroutine checks for missed heartbeats (90s threshold), probes agents via HealthCheck, marks unhealthy Agent side: - HeartbeatClient: connects to master via env vars (MCP_MASTER_ADDRESS, MCP_MASTER_CA_CERT, MCP_MASTER_TOKEN_PATH), registers on startup with exponential backoff, sends heartbeats every 30s Proto: added Register and Heartbeat RPCs + messages to master.proto. Architecture v2 Phase 4. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-04 12:00:31 -07:00