nexxo 353df9f054 fix(kuma-bridge): detect Kuma outages and never trust the cached monitor list ... Verified against a real Kuma by stopping it mid-test: - get_monitors() reads the library's CACHED monitorList event, so it reported 'up' long after Kuma died. Reachability now does a real HTTP round-trip plus a live socket check. - the cached list could yield an id for a monitor that no longer exists; a match is now confirmed with a live get_monitor before it is returned, so CluPilot can never record a target that is never checked. - liveness (/health, always 200 while serving) split from readiness (/ready, 503 when Kuma is unreachable) — the container healthcheck must not restart a healthy bridge just because a dependency is down. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-25 20:13:34 +02:00
..
handoffs	docs: provisioning engine v1.0 build handoff (standalone fleet + cluster-per-DC target)	2026-07-25 09:31:51 +02:00
specs	docs: Phase D spec — service framing, redesign & CRUD completeness	2026-07-25 14:13:23 +02:00
superpowers	docs: customer pipeline (Subsystem B) implementation plan	2026-07-25 11:35:28 +02:00
monitoring-uptime-kuma.md	fix(kuma-bridge): detect Kuma outages and never trust the cached monitor list	2026-07-25 20:13:34 +02:00