docs(frank-zealot): Prism Bonsai-2 PQ2_0 runbook; indexes and log re-keyed

- new runbook: runtime lock (build 10754 / type 142 door), geometry census,
  four-arm VRAM table (f16 wall, q8_0 deployed, q4_0 rung, 2x262,144),
  measured rate ladder, behavior contract, ops notes
- LLM/index.md + vault root index: new ACTIVE entry, 9B era retired in place
- log.md: the trial+cutover wave record, incl. the env-var-name law

serverAppConfigs-docs/log.md

@@ -1799,3 +1799,56 @@ every restart since the cutover.
   mints their accounts as role `pending` on first login.
 - `/serverAppConfigs-docs/Infrastructure/Authentik.md` — human-user template
   census extended with pk 22–23.
+
+## 2026-10-17 — frank-zealot: Bonsai-2-27B PQ2_0 trial + cutover (2 × 200,704, q8_0 KV)
+
+- Ask: evaluate `prism-ml/Ternary-Bonsai-2-27B-gguf` (PQ2_0) as frank-zealot's
+  payload, and specifically measure **2 × 200,704 with q8_0 K + q8_0 V** on the
+  RTX 3090. Fetch script `scripts/download-frank-zealot-bonsai2.sh` (exact
+  bytes + sha256, `--verify-only`) landed first; payload verified at
+  `/home/dank/models/Bonsai2-PQ2_0/` (7,206,168,928 B + 629,246,976 B mmproj).
+- Runtime door: the file is `file_type 141` with 402 tensors of custom GGML
+  type **142** plus `prism.hadamard.*` metadata — stock llama.cpp refuses it,
+  so the PrismML vendor build 10754 (`2459f68b5`) is forced, not chosen. A
+  source build with `GGML_CUDA_FA_ALL_QUANTS=ON` was started and then
+  cancelled as unnecessary: the vendor build already serves q8_0 V under flash
+  attention at the exact 34,816 B/token (ledger-confirmed).
+- Trial-window law cost one boot: the scratch env invented `KV_CACHE_TYPE`
+  where the serve script reads `CACHE_TYPE_K`/`CACHE_TYPE_V`, so the script's
+  `:=f16` default silently won and every arm booted f16. That failed window is
+  now the measured f16 wall: `cudaMalloc` OOM on a 25,088.00 MiB KV request,
+  engine fit 33,198 vs 23,558 free.
+- Four-arm census (production stopped, trap-guarded restore, `bg_12`):
+  **2 × 200,704 q8_0 = 22,664 used / 1,461 free (DEPLOYED)**; 1 × 262,144
+  q8_0 = 18,130 / 5,995 (fits, but serializes compaction); 2 × 262,144 q8_0
+  ≈ 25,758 projected (no fit); 2 × 200,704 q4_0 = 16,392 / 7,733 (fallback
+  rung). Recurrent DeltaNet state bills ~150 MiB per SLOT (context 13,627 −
+  KV 13,328 for two slots), which pool arithmetic alone misses.
+- Behavior probes green: exact-instruction chat, `reasoning_content` present,
+  `tool_calls` with valid JSON arguments (no fork `KNOWN_ISSUES` loop/500),
+  512 px solid-red PNG answered **"Red"**, needle retrieval exact through a
+  25,960-token prompt, 166,027-token prefill clean in 240.0 s. Rates: 76.6 t/s
+  single-stream (9B ran 94.4), 1,258 t/s at 35k, 691.7 t/s at 166k,
+  **109.4 t/s aggregate** at two concurrent streams.
+- New fleet laws recorded (AGENTS.md + runbook): the mmproj's 873.10 MiB
+  worst-case is NOT inside the engine's fit projection; the first request after
+  a boot is a warmup artifact (2.6 / 37.7 t/s measured); a 64-token thinking
+  budget makes a thinking model look blind; the Bonsai-2 template reads
+  `reasoning_effort` (xhigh/medium/low, raises otherwise) so the harness fold
+  became load-bearing on this endpoint, and it reads `preserve_thinking`.
+- Cutover: `scripts/frank-zealot.env` (payload + `CACHE_TYPE_*`=q8_0 + ledger
+  lore), `scripts/deploy-remote.sh` (runtime/model/mmproj gates re-keyed, fork
+  hint), `tests/frank_zealot_unit.bats` (payload pair pinned; KV assertions now
+  env-derived instead of an f16 literal), harness `models.yml` (extraBody 1.0
+  /0.95/20 + `preserve_thinking`, effort-map comment corrected —
+  `contextWindow` 200704 and `maxTokens` 16384 unchanged), new runbook
+  [[frank-zealot-llama-prism-bonsai2-pq20]], indexes re-keyed, 9B era retired
+  in place. Full bats green (371).
+- Base alignment: **Frank chose the OFFICIAL censored payload** — publisher
+  provenance over refusal-freedom. The 9B it replaces was uncensored, so the
+  homepage card and its warning contract were re-keyed with it: zealot's card
+  now carries the base-alignment notice, the shared legal warning belongs to
+  dragoon alone, and the `homepage_config.bats` equality
+  (`zealot.warn == dragoon.warn`) retired with the payload it described.
+  The CRACK re-export (byte-identical geometry per header census) stays on
+  disk as the one-line `MODEL_FILE` fallback if refusals bite.