docs(frank-dragoon): the 401,408-position pool is live; every figure re-keyed to the boot ledger

Deployed 2026-10-18 (e2e 33/33). The boot ledger prints
`reserving the KV pool, 401408 positions (about 11.0 GiB)` and
`62.9 GiB of weights locked … 11.0 GiB of KV pool, 5.7 GiB of working memory,
79.6 GiB in all`, so the ~10.8 GiB that every page quoted from the
~28 KiB/position arithmetic is replaced by the reservation the engine actually
makes (11.0) and its preflight bill (11.3). Host MemAvailable fell 26 -> 22 GiB
across the raise: the FLAGS.md collision (pool RAM is n-gram page cache) paid in
full, so the warm prompt-cache ratio is flagged as the number to watch.

All "committed but not yet deployed" clauses retired: AGENTS.md topology row,
KV-pool law and memory ledger, frank-dragoon.env lore, both index pages, the
iommu page, and the runbook chronology (third production boot recorded).

The sweep also caught the LLM index still describing frank-zealot as
Bonsai-2-27B at 2 x 200,704 in its intro and topology diagram - re-keyed to the
live 9B: 8 full-attention + 24 Gated DeltaNet + blk.32 MTP, 3 x 262,144,
tensor type 141.

serverAppConfigs-docs/index.md

@@ -314,8 +314,9 @@ The LLM inference fleet on the two hosts. Full index:
   since 2026-10-17**: halogen-flash-server 0.16.2 serving the **NATIVE v2
   abliterated** conversion of orcarouter's pinned BF16
   (`qwen38-flash-next-v2-abliterated.hgn`, 62.1 GiB) at ctx **200,704** over a
-  **401,408**-position pool (`HALOGEN_KV_POOL_POSITIONS=401408`, ~10.8 GiB — one
-  pool behind both slots, raised to 2 × ctx on 2026-10-18 so TWO maximum-length
+  **401,408**-position pool (`HALOGEN_KV_POOL_POSITIONS=401408`, 11.0 GiB
+  reserved — one pool behind both slots, raised to 2 × ctx and deployed
+  2026-10-18 so TWO maximum-length
   requests coexist) and the stock peonist n-gram/vision companions **hardlinked**
   in — engine-tool certified (NIAH 18/18, PPL 3.968, mean KL 0.155); MTP
   always-on, vision ON, no server-side sampler change