Use status monitor evidence for routine watchdog health checks

docs/maintenance.md

@@ -102,9 +102,18 @@ reachable. Finished scheduled and legacy maintenance activity is retained for
 
 ## Health recovery and configuration drift
 
-The health observer (the watchdog) scans once per minute. Three observations over
-at least two minutes are required before an automatic health restart; starting or
-restarting containers get five minutes. Unknown Komodo responses are observations,
+The status monitor collects container and game health every 30 seconds. Once per
+minute, the watchdog evaluates that completed evidence without issuing its own
+routine health probes. Samples expire after 45 seconds; missing or stale evidence
+leaves health unknown and cannot justify recovery. Samples retain their original
+timestamps and instance identity, and each failure sample counts at most once.
+A monitoring gap or changed instance resets the sustained failure window. After
+an application restart, routine watchdog checks wait for a new status-monitor pass.
+**Check now** and recovery verification still request fresh evidence, and
+Provisioning retains its checks before executing recovery actions.
+
+Three observations over at least two minutes are required before an automatic
+health restart; starting or restarting containers get five minutes. Unknown Komodo responses are observations,
 not proof of a stopped container. Repeated manual checks do not accelerate this
 window. A successful routine or manual game-status probe between scans resets
 the failure streak. Missing RCON configuration, unresolved ports, and invalid