Reuse heartbeat container state and batch host RCON status

docs/native-hosts.md

@@ -584,6 +584,17 @@ and maintenance additionally share successful health results for up to 30 second
 from the request start, preserving the original observation time. Changed server
 identity or lifecycle intent invalidates reuse. Manual checks and disruption
 safety checks continue to request fresh evidence.
+Status scans allow two checks per host, so a slow host cannot stall the fleet.
+Accepted or running health operations are withheld from the other health lane
+for 30 seconds; an expired replay lease allows recovery with the original ID.
+Agent 1.4.10 includes generation-tagged container states in its 15-second
+heartbeat, using the same Docker inspection as resource sampling (including
+stopped containers). Routine monitoring uses samples younger than 30 seconds,
+preserving their sample time and falling back to inspection when evidence is
+missing, stale, or predates lifecycle changes. RCON status queries share one
+operation per host, with two concurrent local probes and a 20-second batch
+deadline. Individual failures remain visible per server. Both additions are
+capability-gated; older agents retain individual inspection and RCON operations.
 Agent 1.4.5 reserves two observation workers for instance health and read-only RCON,
 and one for files, logs, and host inventory. Background reads arrive in batches of
 up to four. File receipt uploads release the instance lock before contacting the