Fix container resource sampling and surface collection failures

docs/native-hosts.md

@@ -140,12 +140,19 @@ memory measurements. Hosts with stale or missing measurements cannot accept new
 servers. Existing API clients may still explicitly constrain a launch to a host.
 
 Admission reserves a provisional host and port atomically, including collection
-launches. Agent **1.4.3** samples each managed running container with a bounded
+launches. Agent **1.4.6** fixes container discovery for resource sampling (the
+earlier collector omitted `label=` from its Docker filter). It samples each
+managed running container with a bounded
 [`docker stats`](https://docs.docker.com/reference/cli/docker/container/stats/)
 batch during inventory collection. CPU is normalized to cores (100% Docker CPU
 is one core); memory is the Linux working usage reported by Docker, excluding
 reclaimable cache. Missing or failed samples stay unknown instead of becoming
 zero usage. Samples must match the host's live instance and generation.
+Measurements arrive through `/api/agent/heartbeat`, normally every 15 seconds
+plus collection and delivery time, independently of RCON or inspection operations.
+Sampling failures appear on the host's Learned server capacity panel. Existing
+containers can begin contributing running samples as soon as the agent updates;
+startup samples require observing the first five minutes of a container's run.
 
 The controller retains per-instance minute peaks for 24 hours and caches learned
 CPU/memory allowances. The first five minutes after a container starts count as