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/log.md

@@ -2190,3 +2190,39 @@ every restart since the cutover.
   200,704). Note the columns are `params`/`meta` JSON — the table has no
   `context_length`/`description` columns.
 
+
+## 2026-10-18 — frank-dragoon: the 401,408-position pool goes live; docs re-keyed to the measured boot
+
+- `./scripts/deploy.sh dankclaw --service frank-dragoon` — e2e 33/33. The
+  drop-in check the zealot incident bought ran FIRST: `DropInPaths` empty, so
+  the repo env governed. Boot ledger: `reserving the KV pool, 401408 positions
+  (about 11.0 GiB)`, `2 slots over ONE 401408-position KV pool, each request up
+  to 200704`, and `62.9 GiB of weights locked … 11.0 GiB of KV pool, 5.7 GiB of
+  working memory, 79.6 GiB in all`; prompt cache ON (12 entries × 111 MiB at
+  ctx 200704 = 1.3 GiB), n-gram 47.68 GiB still `Pin::None`, no clamp line.
+- The price is exactly the FLAGS.md collision: host `MemAvailable` fell
+  **26 → 22 GiB**, because every pool position is RAM the n-gram table's page
+  cache loses. The warm prompt-cache ratio (136.7× measured pre-raise) was NOT
+  re-measured — recorded in the runbook as the number to watch.
+- Every document quoted **~10.8 GiB**, the ~28 KiB/position arithmetic; the
+  engine reserves **11.0 GiB** and its preflight bills **11.3**. Re-keyed in
+  AGENTS.md (topology row, KV-pool law, memory ledger), the `frank-dragoon.env`
+  lore block, both index pages, the iommu page and the runbook, and every
+  "committed but not yet deployed" clause was retired with the measurement.
+- The same sweep caught the LLM index still describing frank-zealot as
+  **Bonsai-2-27B at 2 × 200,704** in its intro paragraph and topology diagram —
+  the 9B swap of the same day had not reached those two spots. Re-keyed: 8
+  full-attention + 24 Gated DeltaNet + the `blk.32` MTP block, 3 × 262,144,
+  tensor type **141**.
+- PTQ1_0 provenance corrected: `scripts/download-frank-zealot-bonsai2-ptq1.sh`
+  IS committed, so the armed-but-never-measured arm that hijacked the zealot
+  deploy was a **repo-tracked candidate**, not an orphan. The runbook now states
+  the decision it still owes: measure it in a real window, or record it
+  declined.
+- OpenWebUI: both decoration rows re-keyed in the live DB. The values live
+  inside JSON columns — `params.context.length` and `meta.description` — not in
+  fields named for them, and there is no `sqlite3` binary on the host, so
+  `python3` stdlib + `Connection.backup()` (`webui.db.bak-20261018`). Zealot
+  200,704 → **262,144** with the 9B description; dragoon 262,144 → **200,704**,
+  which had kept the pre-lowering window while its own description said
+  200,704.