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 Audit and Posture.md

@@ -155,15 +155,15 @@ http://127.0.0.1:3002/api/org` → 200 means `admin:admin` still live
 (loopback-only; the vhost path needs Anubis + OAuth2 first). LLM binds:
 `sudo ss -tln | grep -E ':(7770|7771)'` — `0.0.0.0` = LAN-reachable with no
 auth (OpenAI API, no token). Stale-record check: current WAN IP =
-`ssh frankbook-pro 'curl -s https://api.ipify.org'` (residential egress);
+`ssh frankbook-pro 'curl -s https://api.ipify.org'` (residential egress)
 compare against every public A record — a record at a different Comcast IP
 is stale.
 
-**Baseline (2026-09-21):** WAN: only 80 + 443 open. Public names: `www`,
+**Baseline (2026-09-21):** WAN: only 80 + 443 open. Public names: `www`
 `search` (guarded) + `ai`, `gitea`, `plex`, `books`, `jelly` (own auth, all
 verified) + `auth` (IdP, by design); everything else LAN-only. Open findings:
 LLM endpoints 0.0.0.0 auth-less on the LAN; Grafana `admin:admin` loopback
-residual; `plex.franksdank.casa` stale (73.59.75.210 = previous Comcast IP);
+residual; `plex.franksdank.casa` stale (73.59.75.210 = previous Comcast IP)
 `plex.franksdank.cloud` WAN-broken (Plex Web 302s to LAN origin
 192.168.0.235:32400); vestigial *arr handlers on the :8017 post-auth listener
 (dead config, no exposure).
@@ -242,7 +242,7 @@ git stash list; git worktree list` (prune stale worktrees), and
 `du -sh .AGENTTRASH` for staged deletions awaiting purge approval. This is a
 **shared checkout with parallel instances**: uncommitted peer WIP and
 stash-list churn are expected. Never commit or drop a peer's files. To
-deploy with a dirty tree: `git stash push -u -m "..." -- <peer paths>`,
+deploy with a dirty tree: `git stash push -u -m "..." -- <peer paths>`
 deploy, `git stash pop`. `deploy.sh` refuses a dirty tree.
 
 **5. Prometheus — expected-down targets (not outages).** Query
@@ -253,7 +253,7 @@ down, especially a `node-*` or LLM job, is a real gap. The recurring trap: a
 same-host `net=host` bind (node-exporter :9100, llama-server :7770/:7771) is
 a *host bind*, not a published port, so the bridge-networked Prometheus
 container cannot reach it at the host's LAN IP — netavark DNATs published
-ports only. Scrape same-host services via
+ports only. Scrape same-host services
 `host.containers.internal:<port>`; verify the fix from inside the container
 before editing: `podman exec prometheus wget -qO-
 http://host.containers.internal:<port>/metrics`.
@@ -270,7 +270,7 @@ Removing a retired host / machine / project name from a repo that holds both
 documentation and live config. Evidence-first, surgical, reversible.
 
 **1. Inventory before touching anything.** Count hits **per file** (the
-count decides whether this is a 5-minute job or a user-input decision),
+count decides whether this is a 5-minute job or a user-input decision)
 excluding logs/`*.db`/runtime state, and capture `git status --short` first
 — you must know which files carry in-flight peer WIP so you never stage
 them.