docs(vault): one fact, one owner — repair the doubled pages, single-source the facts

Structural repair:
- 13 pages were the same document twice (each exactly 2x its HEAD size),
  a second frontmatter block whose closing fence had been glued onto a body
  line by a frontmatter rewrite that re-read its own output. Un-doubled by
  cutting at the second frontmatter and keeping the copy whose body is a
  superset; the orphan census reports 0 lost tokens against HEAD.
- log.md: one entry per date, bare `## YYYY-MM-DD` headings, newest first —
  66 dated headings merged into 34, titles demoted to bold leads, every
  content line verified present. The file had been descending at the head
  and ascending at the tail.

Ownership moves:
- New `LLM/frank-medium.md` is the locator for the retired Dankserver
  endpoint: era windows quoted from each era page's own banner, no numbers
  restated, and the two unresolved date conflicts recorded instead of
  silently resolved. `frank-archon.md` links to it instead of restating the
  pre-rename window.
- The four Pipeline-Parallelism stubs (frontmatter only, no body) are gone;
  `Multi-Node Runtimes.md` owns runtime construction, launch, mixed-vendor
  verdicts and cross-split spec decode, and the four links that pointed at
  the stubs were repointed at it or at the drafter page.
- Authentik's three stub pages fold into `Authentik.md`, with the process
  detail and the outpost reference split out so the parent stays under the
  length hint.

Verified corrections (host census + live probe, 2026-10-19):
- The MXFP4 checkpoint two pages called the "on-disk rollback" is gone:
  /home/dank/models/ holds StillDeadcode, rad and tpl.jinja. Stated once, on
  the era page that owns that payload; the swap page now links to it.
- frank-medium-radiance-mxfp4: the 4.24/7 accept rate belongs to the DFlash2
  arm measured on the FP8 target, not to the MXFP4 era; the 3-family soak run
  census is kept once (155 requests) instead of twice (~120 and 155).
- Fleet shapes re-confirmed against the live endpoints before touching any
  page: 3x200000 fp8 KV, 2x200704, 2x262144.

Index rows are regenerated, not hand-carved. Net -1,849 vault lines.

serverAppConfigs-docs/LLM/vllm_research_findings.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "vLLM v0.26.0 (latest stable, released July 25, 2026) supports DFlash speculative decoding with the `--spec-method dflash` and `--spec-model` flags."
+description: "Upstream support survey for speculative decoding: which flags, releases and pull requests carry each method."
 tags:
   - llm
   - vllm
@@ -10,7 +10,17 @@ timestamp: 2026-08-28
 # Research: vLLM Parameters for Specified Configuration
 
 ## Summary
-vLLM v0.26.0 (latest stable, released July 25, 2026) supports DFlash speculative decoding with the `--spec-method dflash` and `--spec-model` flags. KV cache dtype `q8_0` is **not supported** — only fp8 variants and turboquant options are available. vLLM does not have a dedicated MoE expert CPU offload flag; general CPU offloading via `--cpu-offload-gb` is the closest option. The `--max-num-seqs` flag is confirmed. Podman GPU access requires `--gpus all` with the NVIDIA container toolkit.
+vLLM v0.26.0 (released 2026-07-25, the current stable when this survey was
+gathered on 2026-08-28; PyPI shows v0.32.0 as the latest on 2026-10-19, so
+re-check this page before acting on it) supports DFlash speculative decoding.
+The preferred CLI is the `--speculative-config` JSON object; `--spec-method`
+and `--spec-model` are the per-field aliases defined in
+`vllm/engine/arg_utils.py`. KV cache dtype `q8_0` is **not supported** — only
+fp8 variants and turboquant options are available. vLLM does not have a
+dedicated MoE expert CPU offload flag; general CPU offloading via
+`--cpu-offload-gb` is the closest option. The `--max-num-seqs` flag is
+confirmed. Podman GPU access requires `--gpus all` with the NVIDIA container
+toolkit.
 
 ## Findings