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-npu.md

@@ -15,11 +15,17 @@ timestamp: 2026-09-11
 
 # frank-npu — the retired FLM NPU endpoint
 
-> **RETIRED 2026-09-11.** The endpoint is gone by operator decision, together
-> with the IOMMU configuration it required — see
-> [[dankclaw-iommu-translation-off]]. The service unit, env file and serve
-> script are staged in `serverAppConfigs/.AGENTTRASH/` (suffixed `.flm-npu`),
-> and the host unit is stopped and masked.
+> **RETIRED 2026-09-11 by operator decision** — and still retired: there is no
+> NPU endpoint service on Dankclaw today. The IOMMU configuration it required
+> has since been reversed twice — see
+> [[dankclaw-iommu-translation-off]]: the live 2026-10-18 posture is
+> `cat /proc/cmdline` → `… ro quiet splash iommu=pt …` (no `amd_iommu` token),
+> `amdxdna` is bound and `/dev/accel/accel0` exists, so the hardware is
+> reachable again — revival is tracked as Gitea issue #3. The service unit, env
+> file and serve script are staged in `serverAppConfigs/.AGENTTRASH/`
+> (suffixed `.flm-npu`), and the host unit is still masked
+> (`systemctl is-enabled frank-npu` → `masked`, read 2026-10-18). Port 7771
+> belongs to [[frank-zealot-llama-prism-bonsai2-pq20]] today.
 
 The third inference endpoint on Dankclaw: a FastFlowLM (FLM) v1.0.1 server
 (`/usr/bin/flm`, dpkg `fastflowlm`) on the **XDNA2 NPU** (50 TOPS), serving the
@@ -56,9 +62,16 @@ upstream project on this exact silicon. That single flag is the whole decision:
   NPU sits in IOMMU group 26 `identity` with PASID width 10, `/dev/accel/accel0`
   is `crw-rw---- root:render 261,0` and `dank` is in `render` — so a revival
   quadlet needs `AddDevice=/dev/accel/accel0` + `GroupAdd=keep-groups`, the
-  ComfyUI `/dev/kfd` pattern. Kernel versions to avoid: **6.18–6.18.7** disables
-  SVA outright. Full census in [[dankclaw-iommu-translation-off]]
-  § *2026-10-18 execution*.
+  ComfyUI `/dev/kfd` pattern. Re-read live 2026-10-18: `lspci -k -s c6:00.1` →
+  `Kernel driver in use: amdxdna`; `journalctl -k -b` → `Initialized
+  amdxdna_accel_driver 0.7.0 for 0000:c6:00.1` and `Load firmware
+  amdnpu/17f0_11/npu_7.sbin`; `/sys/kernel/iommu_groups/26/type` → `identity`;
+  `ls -l /dev/accel/accel0` → `crw-rw---- 1 root render 261, 0` (created
+  2026-10-18 01:25); `id -nG dank` contains `render`. Kernel versions to avoid:
+  **6.18–6.18.7** disables SVA outright *(unverified 2026-10-18 — upstream
+  reports place the amdxdna/Strix-Halo breakage at 6.18.4+ and fixed by 6.19.2,
+  not at a clean 6.18–6.18.7 window)*. Full census in
+  [[dankclaw-iommu-translation-off]] § *2026-10-18 execution*.
 - The operator took the vendor's prefill figure on the September evidence, so the
   NPU endpoint went — and it stays retired because nobody has asked for a model
   on it, not because the hardware is unreachable.
@@ -71,11 +84,11 @@ image path is halogen's vision tower on `frank-dragoon`.
 
 | consumer | setting | now |
 |---|---|---|
-| Hermes | `auxiliary.vision` | `dankclaw-large` / `frank-dragoon` (halogen vision tower) |
-| Hermes | `auxiliary.title_generation` | `dankserver-small` / `frank-zealot` |
-| harness (`~/.omp/agent/models.yml`) | `modelRoles.vision` | `llamacpp (dankclaw)` / `frank-dragoon` |
-| harness | `modelRoles.tiny` | `llamacpp (dankserver)` / `frank-zealot` |
-| harness | `modelRoles.task` | `llamacpp (dankclaw)` / `frank-dragoon:medium` |
+| Hermes | `auxiliary.vision` | `dankclaw-large` / `frank-dragoon` (halogen vision tower) *(unverified 2026-10-18: `/opt/hermes` is gone from Dankclaw, so the live `config.yaml` could not be read)* |
+| Hermes | `auxiliary.title_generation` | `dankserver-small` / `frank-zealot` *(unverified 2026-10-18: same)* |
+| harness (`~/.omp/agent/config.yml`) | `modelRoles.vision` | moved again: `llamacpp (dankclaw-3090)/frank-zealot:xhigh` (`config.yml:6`) |
+| harness | `modelRoles.tiny` | `llamacpp (dankclaw-3090)/frank-zealot:off` (`config.yml:10`) |
+| harness | `modelRoles.task` | `llamacpp (dankclaw-3090)/frank-zealot:off` (`config.yml:11`) |
 
 The `flm (dankclaw-npu)` provider block was removed from the harness model
 config, and the `dankclaw-npu` provider from Hermes's live `config.yaml`.
@@ -84,10 +97,10 @@ config, and the `dankclaw-npu` provider from Hermes's live `config.yaml`.
 
 | Field | Value |
 |---|---|
-| Runtime | FLM v1.0.1 (`/usr/bin/flm`, dpkg `fastflowlm`) on the XDNA2 NPU |
+| Runtime | FLM v1.0.1 (`/usr/bin/flm`, dpkg `fastflowlm`; `dpkg -l fastflowlm` on 2026-10-18 still reports `fastflowlm 1.0.1`) on the XDNA2 NPU |
 | Service | `frank-npu.service` (systemd **system** unit, `User=dank`, `Restart=on-failure`, `RestartSec=10`, `LimitMEMLOCK=infinity`) |
 | Files (archived) | `scripts/frank-npu.env`, `scripts/serve-frank-npu.sh`, `scripts/frank-npu.service` |
-| Port | `7771` on `0.0.0.0` |
+| Port | `7771` on `0.0.0.0` (that port is frank-zealot's today) |
 | Power mode | `FLM_PMODE=turbo` — nothing else used the NPU, so the top power mode cost no neighbour anything |
 | Context | `FLM_CTX_LEN=131072` (128K, the verified maximum on this box) |
 | Vision/audio | `FLM_ASR=0`; the E4B pack answers images through its own vision tower, and `FLM_ASR=1` would have added Whisper-V3-Turbo-NPU2 (+0.62 GB) and `/v1/audio/transcriptions` |
@@ -132,8 +145,9 @@ The same root cause explained the older
 consequence of IOMMU-off, not a GPU fault.
 
 **The standing rule this produced — "never set `iommu=off` on this host again" —
-has been superseded**: the NPU it protected is retired by decision, and
-`amd_iommu=off` is now intentional. See
+was superseded twice**: `amd_iommu=off` was the intentional posture from
+2026-10-16 to 2026-10-18, and the host has since flipped back to `iommu=pt`
+(live `cat /proc/cmdline`, 2026-10-18: `… ro quiet splash iommu=pt …`). See
 [[dankclaw-iommu-translation-off]] for the current posture and how to revert it.
 
 ## Client wiring (historical)