980df5517d
- Pinned traefik-manager to 172.18.0.4 (was floating in the dynamic pool) - Added Uptime Kuma monitor id=38 "Traefik Container (direct)" — TCP probe at 172.18.0.3:80, decoupled from the routing-layer HTTP probe so a Traefik container failure is distinguishable from a routing breakage - Documented that AutoKuma v2 is silently broken; monitor was created via direct SQL insert as a workaround