frank-large: correct docs to measured 401408 ledger figures

Predicted ~10.8 GiB KV / ~33.4 need / ~10.5 host-left; the boot ledger
printed ~11.0 / ~31.5 / 100.0 GiB held with 9.1 GiB + 1396 contiguous
2 MiB blocks left. Stall NOTE no longer prints at this footprint. Also
documents the ~45-60 s first-request PING silence after a restart (the
healthcheck's HealthStartPeriod covers it; do not restart the unit).

AGENTS.md

@@ -413,9 +413,12 @@ free memory for co-tenants, it can only remove the pool. Against the old
 524,288 pool the reserve ceiling was 16 (engine needs budget ≥ 36.5; reserve
 18 yields 35.5 and silently clamps); at 401,408 the need is ~33.4 so the
 ceiling loosens, but a bigger reserve still buys nothing. To free host RAM,
-cut `HALOGEN_KV_POOL_POSITIONS` (262144 hands back another 3.6 GiB) or
-`HALOGEN_MAX_TOK` (16384 hands back 8.4). At the trimmed pool expect roughly
-10.5 GiB left on the host — confirm on the boot ledger, not here. If a
+cut `HALOGEN_KV_POOL_POSITIONS` (262144 hands back another ~3.6 GiB) or
+`HALOGEN_MAX_TOK` (16384 hands back 8.4). Measured at 401,408 (2026-09-13
+deploy ledger): 100.0 GiB held (68.0 weights + 11.0 KV + 21.0 working), ~9.1
+GiB / 1396 contiguous 2 MiB blocks left on the host, engine need printed
+~31.5 GiB against the 38.5 budget, and the co-tenant stall NOTE no longer
+prints — confirm on the boot ledger, not here. If a
 co-tenant still runs it dry, frank-large and its neighbours stall for
 minutes at full CPU with no disk activity — not a crash, and invisible to
 `free`, which still reads ~74 GiB available. The weights stay pinned (~68 GiB)