docs: distill the managed skill library into the vault (waves 1-7)

All ~173 managed skills read in full and merged, one polished reference
page per skill-cluster:

- LLM cross-cutting (17 pages): GGUF Compatibility, Llama Cpp Serving
  Sizing, Llama Cpp Multi-Device Splits, PCIe Link and Atomics, RDNA4
  Container Serving, RDNA4 MoE Expert Offload VRAM Budget, vLLM Boot
  Forensics, vLLM Porting and Compile Triage, LLM Bench Windows, LLM
  Performance Diagnosis, Model Swap and Rollback, Tcclaviger Fork Ops,
  Heterogeneous Split Triage, FreeToken Builds + deltas folded into the
  retired runbooks (GLM DFlash2 port laws, Lucebox dual-R9700, R9V
  qualification pipeline, FLM pack registration, ik hybrid envelope,
  frank-medium split rebalance, llama.cpp GGUF preflight, batch-ubatch
  split section, bench-window D-state/stale-read notes, second-endpoint
  bring-up).
- Architecture (3): Stale Signal Audit, Quadlet Lifecycle, Deploy State
  Triage.
- Operations (6 + index): Remote Job Runner, Payload and Disk Reclaim,
  Container Host Reachability, Fleet Ops Playbook, Fleet Audit and
  Posture, SSH and Remote Access.
- Infrastructure: Observability Provisioning + Homepage Status Probes;
  updates to Authentik, Anubis, LAN-DNS (per-client DoH bypass, Porkbun
  zone ops), Swap Configuration, OpenWebUI, Hermes (pre-existing page
  preserved and extended).
- FrankBook-Pro: ARR-Stack filled (API split, schema-first probing,
  auth-posture, auth-config trap); qBittorrent E2E verification.
- Desktop/Agent/Research: Noctalia and Niri, OMP Harness, Agent Docs and
  Edits, Command Center Dotfiles, PICO-8 Asset Standards.
- Indexes: LLM Cross-Cutting References section, Operations/ and Agent/
  index pages, root-index Skill Distillation section, AGENTS.md pointer.
- log.md carries the wave plan.

check-vault-links.py 0 unresolved (185 pages); ./tests/run.sh 366/366.

serverAppConfigs-docs/Dankclaw/Swap Configuration.md

@@ -117,6 +117,18 @@ frank-large `health=200` throughout.
   the model is loaded. Trust the engine's `host memory left for everything
   else` line, not `free`.
 
+- **Filesystem prerequisite (other hosts).** ext4 and xfs take swapfiles
+  directly. btrfs needs `chattr +C` (NOCOW), no compression, and no
+  snapshots in the swapfile path — check `df -T` before planning, or
+  `mkswap` will reject the file.
+- **Renaming an *active* swapfile works (inode-based) but leaves a stale
+  path in `/proc/swaps`** — swap it off first, then rename, then `swapon`
+  (which is exactly what the step-3 consolidation does). Migration is
+  observable while it runs: in the 2026-09-12 run `swapoff` of 4 GiB took
+  65 s and used-RAM rose only ~3 GiB (pages touched during migration), the
+  rest relocating on disk. If used-RAM climbs toward the whole swapped
+  amount, let it finish rather than aborting.
+
 ## Trash
 
 The previous 8 GiB `/swap.img` (dated 2026-07-21) is staged, not deleted, at