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/Operations/Fleet Ops Playbook.md

@@ -40,7 +40,7 @@ prod unit → get the holder, and compare its bytes against the service's
 requirement before concluding a start would even fit. The per-boot requirement
 is the endpoint's own arithmetic ([[frank-archon]], [[frank-dragoon]],
 [[frank-zealot]]; the retired `frank-medium` split is measured in
-[[frank-medium-llamacpp-dflash2]]) — a stray holder blocks the restart on
+) — a stray holder blocks the restart on
 allocation, not config.
 
 **3. Identify the holder and prove it is abandoned**
@@ -98,7 +98,7 @@ the local Gitea on Dankclaw — push allowed).
 unquoted word with `=` in an ssh one-liner (`echo ===` aborts the chain). A
 freshly restarted endpoint under live agent-queue backlog may return empty
 bodies/timeouts for minutes while `/health` is 200 — re-probe with a long
-timeout. The first request after a `frank-dragoon` restart is a warmup artifact — see
+timeout. The first request after a `frank-dragoon` restart is a warmup artifact —
 [[frank-dragoon]] → Contract; do not restart over it. Where an endpoint's own
 log lives (and whether sudo is needed to read it) is on its page. If the
 restore never happened,
@@ -146,7 +146,6 @@ there; `mask --runtime` is for scratch boots that must survive a stray
 restart. Always end a window by re-checking the conjunction before
 reporting — if a restore after failure doesn't happen automatically, prod
 stays DOWN. See the repo's benchmarking policy (AGENTS.md) and
-[[LLM Bench Windows and Measurement]].
 
 ## Iterating on a fleet service before commit
 
@@ -249,7 +248,7 @@ import socket, time
 MAC = "de:6b:6d:c1:52:23"
 mac = bytes(int(x,16) for x in MAC.split(":"))
 pkt = b"\xff"*6 + mac*16          # 102 bytes
-for local, dest in [("192.168.0.83","192.168.0.255"),("192.168.0.104","192.168.0.255"),
+for local, dest in [("192.168.0.83","192.168.0.255"),("192.168.0.104","192.168.0.255")
                     ("192.168.0.83","255.255.255.255"),("192.168.0.104","255.255.255.255")]:
     s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
     s.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
@@ -271,7 +270,7 @@ for local, dest in [("192.168.0.83","192.168.0.255"),("192.168.0.104","192.168.0
 
 ## Related
 
-- [[LLM Bench Windows and Measurement]] — the bench windows this playbook arms
+-  the bench windows this playbook arms
 - [[Remote Job Runner]] — supervising the long jobs that create these windows
 - [[Container Host Reachability]] — the pasta port gate at container create
 - [[Quadlet Lifecycle]] — the unit layer behind stop/mask/start