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/GGUF Compatibility.md

@@ -14,7 +14,7 @@ Studio refuse custom types at load (`unknown tensor type`); a fork-private type
 means exactly one engine can serve the file. Measured on this fleet repeatedly:
 `Qwen3.8-27B-Q8_0_ROCMFPX_AGENT.gguf` is ftype 115 with 311 tensors of type 103
 (`GGML_TYPE_Q8_0_ROCMFPX`) — only charlie12345/ROCmFPX reads it. The full type
-tables live in [[Llama Cpp Runtimes]] and [[Llama Cpp Code Diff]]
+tables live in  and
 (ggml_type 100–108, ftype families 100–106 / 110–113 / 118).
 
 ## 1. Read the header, do not guess
@@ -69,14 +69,14 @@ filenames lie about quantization and about MTP/vision heads.
    ```
 
    Validate before trusting: the parse is right iff the tensor-info block ends
-   somewhere sane and names look real (`blk.0.attn_q.weight`,
+   somewhere sane and names look real (`blk.0.attn_q.weight`
    `token_embd.weight`, `output_norm.weight`). EOF throw = wrong enum or
    offset — do not work around it.
 
 3. **Diff what engines actually bind on**: `general.architecture`; tensor
    count; tensor name list in order; per-tensor `ggml_type` and dims; geometry
-   KVs (`<arch>.block_count`, `.embedding_length`, `.feed_forward_length`,
-   `.attention.head_count[_kv]`, `.rope.*`, `.ssm.*`, `.context_length`,
+   KVs (`<arch>.block_count`, `.embedding_length`, `.feed_forward_length`
+   `.attention.head_count[_kv]`, `.rope.*`, `.ssm.*`, `.context_length`
    `.nextn_predict_layers`); MTP tensors (`nextn` in the name); vision tensors
    (`visual`, `v_` prefixes). A same-family fine-tune quantized by the same
    tool usually comes out byte-identical in every one of these — that is the
@@ -117,8 +117,8 @@ re-download.
 
 ## Related
 
-- [[Llama Cpp Runtimes]] — which fork ships which custom types
-- [[Llama Cpp Code Diff]] — the enum tables and code-level differences
-* [[kingjones-q8agent-rocmfpx]] — the era that served the ftype-115 file, and
+-  which fork ships which custom types
+-  the enum tables and code-level differences
+*  the era that served the ftype-115 file, and
   [[frank-dragoon]] for what runs there now
 - [[Llama Cpp Serving Sizing]] — pricing what a payload costs once it loads