docs(vault): verified corrections with sources, not assertions

- frank-archon KV dtype law: `bf16|fp8` is a **radiance** restriction. Stock
  vLLM advertises `auto|fp8|fp8_e5m2|fp8_e4m3` (docs.vllm.ai engine args), and
  even there the advertised set is not the usable set — several accepted
  values crash engine init at the attention layer's own dtype check
  (vllm-project/vllm#42587). The page stated the restriction as if upstream
  had it.
- Open Notebook: re-censused 2026-10-19 — no unit file, no installed quadlet,
  no container. The page already said NOT deployed; it now says what was
  checked, so the claim is re-checkable instead of remembered.

serverAppConfigs-docs/LLM/frank-archon.md

@@ -150,7 +150,11 @@ vllm-radiance era (this table opens on 09-26; the era page claims 10-10).
 ### The radiance engine
 
 - **KV dtype law.** `--kv-cache-dtype` takes only `bf16|fp8` — ONE dtype for the whole cache,
-  so llama.cpp's exact-K / quantized-V pair (what [[frank-zealot]] runs as `--cache-type-k`/
+  a **radiance** restriction, not stock vLLM's: upstream advertises `auto|fp8|fp8_e5m2|fp8_e4m3`
+  (`docs.vllm.ai` engine-args) and even there the advertised set is not the usable set — several
+  accepted values crash engine init at the attention layer's own dtype check
+  ([vllm-project/vllm#42587](https://github.com/vllm-project/vllm/issues/42587)).
+  So llama.cpp's exact-K / quantized-V pair (what [[frank-zealot]] runs as `--cache-type-k`/
   `--cache-type-v`) is unservable here: the rung below bf16 is fp8 on both halves. Measured
   per-rank cost out of the boot ledger's group table (fp8 boot 2026-10-08, bf16 boot
   2026-10-11): `kv_attn` 13 layers / 4-token blocks pages **26.00 → 52.00 KiB**, while