docs(vault): fleet-wide fact re-verification pass (67 pages)

The docs-fact census wave re-read the live hosts and re-keyed every page
it could: runtime/payload identities, ports, sizes, ledger figures, unit
state, and the retirement banners that drifted as the fleet moved. The
wave was interrupted mid-run, so this commit carries only what passed the
integrity gates: every touched page parses (front matter or H1+status
convention intact, balanced fences, no truncated tables, trailing
newline), the docs_completeness and link-integrity seams are green, and
bats is 384/384.

Numbers that this session proved on live hosts are keyed to the measured
value, not the page's earlier claim.

serverAppConfigs-docs/LLM/frank-zealot-llama-qwen35-9b-q6k-2x200704.md

@@ -1,7 +1,7 @@
 ---
 type: reference
-title: "frank-zealot on Dankclaw — llama.cpp, Qwen3.5-9B Q6_K, 2 x 200704, f16 KV (ACTIVE)"
-description: "The ACTIVE frank-zealot runbook (since 2026-10-07) — llama.cpp master (CUDA sm_86) serving HauhauCS/Qwen3.5-9B-Uncensored-HauhauCS-Aggressive at Q6_K on the RTX 3090: two conversations of 200,704 tokens with exact f16 KV, vision through the publisher's BF16 projector, MTP impossible (no tensors in the file), and the measured geometry that priced the shape."
+title: "frank-zealot on Dankclaw — llama.cpp, Qwen3.5-9B Q6_K, 2 x 200704, f16 KV (RETIRED, rollback target)"
+description: "The frank-zealot runbook of 2026-10-07 → 2026-10-17 (RETIRED — rollback target) — llama.cpp master (CUDA sm_86) serving HauhauCS/Qwen3.5-9B-Uncensored-HauhauCS-Aggressive at Q6_K on the RTX 3090: two conversations of 200,704 tokens with exact f16 KV, vision through the publisher's BF16 projector, MTP impossible (no tensors in the file), and the measured geometry that priced the shape."
 tags:
   - llm
   - frank-zealot
@@ -14,7 +14,22 @@ timestamp: 2026-10-07
 
 # frank-zealot — llama.cpp Qwen3.5-9B Q6_K, 2 × 200,704, f16 KV
 
-Live since 2026-10-07, replacing the
+**RETIRED 2026-10-07 → 2026-10-17** (AGENTS.md Runbook Index), superseded by
+[[frank-zealot-llama-prism-bonsai2-pq20]] (27B PQ2_0, 2 × 200,704 q8_0 KV, build
+10754), itself retired 2026-10-17 → 10-18 and now the rollback target: :7771
+today is llama.cpp PrismML build **10777** on
+`Ternary-Bonsai-2-9B-PQ2_0-MTP-Q8_0.gguf`, 3 × 262,144 q8_0 KV, MTP off by
+measurement (AGENTS.md Runbook Index active row; `scripts/frank-zealot.env`).
+Transient 2026-10-18: :7771 is inside a bench window — the unit is `failed`
+since 03:14 and a hand-booted process answers the port; restore with
+`./scripts/deploy.sh dankclaw --service frank-zealot`.
+This era is the rollback target: the payload is still on disk
+(`stat -c %s /home/dank/models/Qwen35-9B-HauhauCS-Q6K/Qwen3.5-9B-Uncensored-HauhauCS-Aggressive-Q6_K.gguf`
+→ 7359259008, read 2026-10-18) with its master CUDA build. Same census: the
+10754 rollback payload `Bonsai2-PQ2_0/Ternary-Bonsai-2-27B-PQ2_0.gguf` is
+present at 7206168928 with its Q8_0 mmproj at 629246976, and
+`Bonsai2-9B-MTP/Ternary-Bonsai-2-9B-PQ2_0-MTP-Q8_0.gguf` at 2675410720 —
+nothing this era or its successors need has been purged. It replaced the
 [[frank-zealot-llama-gemma4-q4km-200704]] era (Q4_K_M on ONE 200,704
 slot). The swap is a capacity trade: the 9B dense-hybrid rung costs ~7 GiB of
 weights where the 26B MoE cost ~16.6 GiB, and the freed room buys the second
@@ -26,7 +41,7 @@ conversation slot and unquantized KV back.
 |---|---|
 | Host / device | Dankclaw (192.168.0.143), RTX 3090, 24,576 MiB |
 | Endpoint | `http://192.168.0.143:7771` — served model id **`frank-zealot`** (`ALIAS` in the env; the SERVICE keeps the `frank-zealot` name), `/v1` OpenAI surface |
-| Runtime | llama.cpp master (0.5.0-dev, commit `5fc4f3c`), CUDA sm_86 build `…/llama-master/build-cuda/bin/llama-server` (`GGML_CUDA_FA_ALL_QUANTS=ON`); `qwen35` is registered in the build's own `src/llama-arch.cpp` and `src/models/qwen35.cpp` exists at that commit |
+| Runtime | llama.cpp master (0.5.0-dev, commit `5fc4f3c`), CUDA sm_86 build `…/llama-master/build-cuda/bin/llama-server` — `--version` on the disk build reads `0.5.0-dev (build 1, commit 5fc4f3c)` (built 2026-10-01); its `CMakeCache.txt` says `GGML_CUDA_FA_ALL_QUANTS:BOOL=OFF` and that tree carries no CUDA-side guard for the option (`ggml/src/ggml-cuda/fattn.cu:438-449` dispatches Q4/Q5 KV unconditionally), so quantized KV never required it; `qwen35` is registered in the build's own `src/llama-arch.cpp` and `src/models/qwen35.cpp` exists at that commit |
 | Unit | root systemd `frank-zealot.service` ([`scripts/frank-zealot.service`](../../scripts/frank-zealot.service)), `User=dank`, `Restart=on-failure`, `LimitMEMLOCK=infinity` |
 | Serve script | [`scripts/serve-frank-zealot.sh`](../../scripts/serve-frank-zealot.sh), tunables [`scripts/frank-zealot.env`](../../scripts/frank-zealot.env) |
 | Weights | `/home/dank/models/Qwen35-9B-HauhauCS-Q6K/Qwen3.5-9B-Uncensored-HauhauCS-Aggressive-Q6_K.gguf` — HauhauCS **Q6_K**, 7,359,259,008 B, sha256 `c0ba7beb68fd3fe47891bd549486d38dcf62d00817296ea314ad37017f5a4986` |
@@ -98,7 +113,9 @@ safe; the Gemma4 era's warning was the opposite case, a drafter running 53 %
 **past** its window). Weights load in ~6 s from page cache; `/health` answers
 `{"status":"ok"}` and `/v1/models` serves the alias `frank-zealot`.
 
-**Wire rename (2026-10-09):** `ALIAS` moved `frank-zealot` → `frank-zealot`,
+**Wire rename (2026-10-09):** `ALIAS` moved `frank-secondary` → `frank-zealot`
+(commit `7c77326`; the service-file rename to the `frank-zealot.*` names
+followed 2026-10-10, commit `55f87fc`),
 so the served id matches the harness model id and the family-facing name.
 Consumers re-keyed in the same change: OpenWebUI (`model` row, `access_grant`
 row, `openai.api_configs` index-2 `model_ids`) and `models.yml` (already
@@ -120,7 +137,7 @@ The publisher's recipe ships in `models.yml` `extraBody`: thinking mode
 thinking" is satisfied by the 200,704 slot.
 
 **Compaction hub**: `models.yml` routes `compactionModel` for all three
-endpoints here. With `--parallel 2` a compaction request no longer serializes
+endpoints here — still true 2026-10-18 (`~/.omp/agent/models.yml:25,107,185` all name `llamacpp (dankclaw-3090)/frank-zealot`). With `--parallel 2` a compaction request no longer serializes
 behind a live generation (the Gemma4 era's `--parallel 1` law), and the
 200,704 slot still fits the worst-case compaction input (~133k tokens).