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/Heterogeneous Split Triage.md

@@ -74,6 +74,11 @@ cat /sys/class/drm/card*/device/mem_info_gtt_total    # aperture onto SYSTEM RAM
 rocm-smi --showmeminfo all | grep -i gtt              # used == what the CPU also sees
 ```
 
+Read on Dankclaw 2026-10-18: `mem_info_vram_total` = 2147483648 (2 GiB of
+dedicated carve), `mem_info_gtt_total` = 122402963456 (114 GiB) — the aperture is
+the whole budget, the carve is noise, and the OS sees 121 GiB of it
+([[Dankclaw System Specs]]).
+
 A large GTT window means the "GPU memory" is the *same* LPDDR under one
 memory controller: adding a stage there adds a compute engine, not capacity
 or bandwidth. Only the discrete card's VRAM is additive. Fencing more
@@ -101,6 +106,13 @@ of bytes), so it is tempting. Before proposing it:
   gap. In llama.cpp the portable mechanism is `--spec-draft-device/-devd`
   (draft gets its own device list) plus `-ngld`/`-otd`/`-ctkd -ctvd`.
 
+The llama.cpp half of that bullet is checkable upstream: `--spec-draft-device`
+(`-devd` / `--device-draft`, line 4259), `--spec-draft-ngl` (`-ngld`, 4268),
+`--spec-draft-override-tensor` (`-otd`, 4137) and `--spec-draft-type-k/v`
+(`-ctkd`/`-ctvd`, 4111/4124) all exist in
+`common/arg.cpp` ([source](https://raw.githubusercontent.com/ggml-org/llama.cpp/master/common/arg.cpp),
+read 2026-10-18).
+
 ## 6. Expressing a split (llama.cpp, the usual vehicle)
 
 ```bash
@@ -110,10 +122,12 @@ of bytes), so it is tempting. Before proposing it:
 
 - buffer types match by name at load (`ggml_backend_buft_name`), so device
   names work as `-ot` values;
-- `-cmoe`/`-ncmoe` are **CPU-only**; device-side MoE placement is `-ot`;
+- `-cmoe`/`-ncmoe` are **CPU-only** (`--cpu-moe` / `--n-cpu-moe`,
+  `common/arg.cpp:2764,2771`); device-side MoE placement is `-ot`;
 - several backends in one binary is fine (CUDA + Vulkan is the practical
-  pair; HIP + CUDA do not coexist) — `GPU_BACKEND_A=OFF` in the existing
-  build's CMakeCache tells you what needs adding;
+  pair; HIP + CUDA do not coexist *(unverified 2026-10-18 — upstream build docs
+  do not settle the combination either way)*) — `GPU_BACKEND_A=OFF` in the
+  existing build's CMakeCache tells you what needs adding;
 - contiguous ranges are the WRONG split when KV bandwidth dominates: they
   drag half the attention layers (and their KV) back to the slow pool.