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.

scripts/frank-dragoon.env

@@ -68,10 +68,11 @@
 #   ceiling does NOT move with it: HALOGEN_CTX stays 200,704, because the
 #   checkpoint's native window is 262,144 and the engine refuses to go past it
 #   without HALOGEN_ROPE_YARN (its own 400 text says so). ~28 KiB/position
-#   (FLAGS.md) ⇒ ~10.8 GiB, where pool == ctx (200,704) cost 5.5, 262,144 cost
-#   7.2 and the 2026-10-06 shape's 524,288 measured 14.6. The engine's preflight
-#   formula bills a little more than the reservation (block scratch + ~115
-#   MiB/slot of O(1) state) — quote the RESERVATION. FLAGS.md law: "RAM the pool
+#   (FLAGS.md) ⇒ the DEPLOYED 2026-10-18 boot RESERVES 11.0 GiB (`reserving the
+#   KV pool, 401408 positions (about 11.0 GiB)`), where pool == ctx (200,704)
+#   cost 5.5, 262,144 cost 7.2 and the 2026-10-06 shape's 524,288 measured 14.6.
+#   The preflight formula bills 11.3 (block scratch + ~115 MiB/slot of O(1)
+#   state) — quote the RESERVATION. FLAGS.md law: "RAM the pool
 #   takes is RAM that table loses" — the 47.68 GiB n-gram table surrenders this
 #   much page cache, so the warm prompt-cache ratio is what to re-measure.
 #   HALOGEN_KV_SLOTS=2 restores the w4b-era shape on this box: the MTP
@@ -82,14 +83,16 @@
 #   Memory ledger against the box's 121.2 GiB unified (the n-gram table is
 #   mmap'd page cache beside the checkpoint, not a pinned charge — the boot
 #   ledger agrees: "mapped 51.2 GB, NOT pinned (Pin::None)"):
-#     weights ~62.9 GiB locked (0.8 of them the vision tower) + KV ~10.8 +
-#     working ~5.7 (HALOGEN_MAX_TOK=8192) ≈ 79.4 GiB engine-side, with the
-#     prompt cache (~1.0 at this ctx; 1.3 was measured at 262144) booked
-#     separately by the ledger; HALOGEN_HOST_RESERVE_GIB=20 keeps the host
-#     honest. Against the 121.2 GiB box that leaves ~22 GiB over the reserve for
-#     baseline co-tenancy (frank-zealot, ComfyUI, Caddy/observ ~10-15). The boot
-#     ledger is the referee — read it after deploy and re-size if the engine
-#     prints a clamp.
+#     weights 62.9 GiB locked (0.8 of them the vision tower) + KV 11.0 +
+#     working 5.7 (HALOGEN_MAX_TOK=8192) = 79.6 GiB engine-side (the boot
+#     ledger of the 401408-position deploy, 2026-10-18), with the 1.3 GiB
+#     prompt cache (12 entries x 111 MiB at ctx 200704) booked separately by
+#     the ledger; HALOGEN_HOST_RESERVE_GIB=20 keeps the host honest. Against
+#     the 121.2 GiB box that leaves ~20 GiB over the reserve (MemAvailable
+#     read 22 GiB right after the raise) for baseline co-tenancy
+#     (frank-zealot, ComfyUI, Caddy/observ ~10-15). The boot ledger is the
+#     referee — read it after deploy and re-size if the engine prints a
+#     clamp.
 #   HALOGEN_SPEC_ADAPT=0 is MANDATORY (card): the default adaptive policy
 #   turns the MTP head off for whole requests after low acceptance and
 #   HALVES decode as a result. Frank accepted the head always-on trade