docs(vault): destroy the dead weight — 53 pages and the change diary

The vault was 155 pages / 31,210 lines, most of it measurement ledgers for
payloads that no longer run. A throughput figure for a runtime nobody operates is
not a record: AI moves faster than the vault, so the number is wrong before
anyone reads it, and a wrong number in a runbook gets believed. Per the new
purpose test in `AGENTS.md` → *Documentation Policy*, it is destroyed.

Gone (`.AGENTTRASH/20261019-destruction/`, KILL-LIST.txt is the manifest):
- the `frank-medium` endpoint and its five era pages, `frank-npu`, FastFlowLM,
  the ikllama/kingjones/dealign/frank-redo eras, the ling/swift15/freetoken/ubatch
  campaign pages, qwen3.8 spec-matrix and strix-optimizations, the two
  "Running Qwen3.6 …" pages;
- the whole `Pipeline Parallelism/` folder (no live script passes a pipeline flag)
  and the multi-device/x4-pair/hybrid/offload experiment pages;
- every vLLM page — no vLLM endpoint exists on this fleet;
- `LLM/deployment.md` (`Architecture/Deployment Flow.md` is the test-referenced
  owner) and the external surveys (SGLang, Lemonade, llama.cpp forks/diff,
  self-hosted app census, the TTS survey) that were obsolete by construction;
- `log.md`, 2,380 lines. Git holds the chronology; a causal law belongs to the
  page that owns the thing it governs, never to a diary.

Survivors: 101 pages, 17,542 lines, 0 OKF violations, 0 unresolved links. Eras
tables keep the window, payload, runtime, reason and rollback pointer; the rate
columns are blanked. The live shapes stay verbatim — those numbers are what the
deployer and `models.yml` consume.

serverAppConfigs-docs/LLM/Llama Cpp Serving Sizing.md

@@ -19,7 +19,7 @@ guesswork.
    `n_ctx_slot = CTX_SIZE / PARALLEL`. A hybrid model with
    `kv_unified = 'false'` gives each slot its own cache AND a fixed per-slot
    state buffer — slot count is a memory term, not free.
-2. **Two boots on the real card** (production stopped, per the bench law),
+2. **Two boots on the real card** (production stopped, per the bench law)
    each near the target; record `nvidia-smi` used/total plus the boot log's
    `n_slots`/`n_ctx_slot`: shape A = current/cheap, shape B = new demand.
    `non-KV = used − (tokens × KiB/token)`; the two rows separate
@@ -31,7 +31,7 @@ guesswork.
    slot gets an equal integer window. Boot and measure; if outside the band,
    walk one step — never re-derive from a formula.
 4. **Propagate the per-slot number — it is the client contract:**
-   `models.yml` `contextWindow` = `n_ctx_slot` (NOT the model's native window),
+   `models.yml` `contextWindow` = `n_ctx_slot` (NOT the model's native window)
    or long conversations die with `400 exceed_context_size_error` instead of
    compacting; compaction/summary budgets sized to the old window get
    re-checked; endpoint docs and the rollback table move too.
@@ -66,13 +66,13 @@ co-tenants.
 - **Engine ledger first.** Halogen prints weights pinned (+ remaining 2 MiB
   contiguous blocks — the honest fragmentation signal: a block census that drops
   across a restart means the model did not come back into the same hole; the
-  before/after census this was learned on is that era's, on [[frank-dragoon]]),
+  before/after census this was learned on is that era's, on [[frank-dragoon]])
   device budget, KV pool/working split, "left for everything
   else". llama.cpp prints them at `llama-model.cpp:1827` (per-backend model buffer)
   and `llama-context.cpp:692` (compute buffer) on the era's build; on today's
   `master` the same `LLAMA_LOG_INFO` lines sit at `llama-model.cpp:2009`
   ("model buffer size =") and `llama-context.cpp:842` ("compute buffer size =")
-  ([source](https://raw.githubusercontent.com/ggml-org/llama.cpp/master/src/llama-context.cpp),
+  ([source](https://raw.githubusercontent.com/ggml-org/llama.cpp/master/src/llama-context.cpp)
   re-read 2026-10-18) — but **`llama-bench`
   suppresses loader INFO and a systemd unit did not put them in the journal**
   (verified `grep -c` = 0). Recipe: one launch through `llama-cli`/`llama-server`
@@ -92,7 +92,6 @@ co-tenants.
   projector, never weights alone. Do
   the capacity subtraction before designing, on the card number the owner page
   quotes, not the advertised one.
-- **Context lengths: derive, never remember.** `llama-bench` computes
   `n_ctx = n_prompt + n_gen + n_depth` (defaults 512/128/0, type_k/v F16,
   flash_attn AUTO, split_mode LAYER). `-p 512,16384 -n 64` = contexts
   576/16,448; a plain `tg` row has ~zero depth — `-d` is the only thing that
@@ -116,7 +115,7 @@ of the whole sequence + constant recurrent state + the draft context's KV:
 `per_token = 2 × n_full_attn_layers × n_kv_heads × head_dim × bytes (K and V) +
 draft_per_token`. The worked qwen35-hybrid instance of that formula (full layer
 count, f16 KV, MTP draft) and the slot-size table it prices are on
-[[frank-medium-llamacpp-dflash2]]; cross-check any such arithmetic against the
+; cross-check any such arithmetic against the
 journal's `prompt state size` lines — the two must agree.
 
 **The journal is the instrument:** `exceeds cache size limit … skipping` =
@@ -171,6 +170,6 @@ part of that era's record on [[frank-dragoon]].
 
 - [[GGUF Compatibility]] — what a payload is before it is priced
 - [[frank-zealot]] — the endpoint whose Eras rows are the two-boot priced shapes this method produced
-- [[frank-medium-llamacpp-dflash2]] — the state-law worked example behind section 3
+-  the state-law worked example behind section 3
 - [[DFlash DSpark Speculative Decoding]] — the spec A/B protocol on llama.cpp
-- [[Dual-R9700-Cooperation]] / [[x4-pair-experiment]] — the multi-device side
+- /  — the multi-device side