kb: retire pi-installation association (OMP is the primary harness)

Purge live-state claims that ~/.pi is our harness; keep general
pi documentation in omp-docs/ and dated historical records.

- README.md: single config source; Legacy Notes reworded
- AGENTS.md: drop 'like ~/.pi did' framing
- APPEND_SYSTEM.md: okf-spec -> omp-docs/references/okf-spec.md
- dotfiles/zsh/.zshrc: systemprompt alias -> APPEND_SYSTEM.md
- managed skill llm-fleet-model-swap + model_config_sync skill:
  single-source models.yml; validation script YAML-only
- memories (MEMORY.md, memory_summary.md, learned.md): single source
- omp-docs: .okf root -> ~/.omp/omp-docs; de-live pi-era claims in
  pi/index.md, pi-web-access.md, engineering/agents-files.md

agent/memories/--home-blank-Projects-serverAppConfig--/rollout_summaries/01a0ac72-2620-750f-82dd-79c84e00e98d-dankclaw_m2_qwen_fla.md

@@ -0,0 +1,4 @@
+thread_id: 01a0ac72-2620-750f-82dd-79c84e00e98d
+updated_at: 1789631572
+
+User asked about M.2 slots on dankclaw, clarified they meant the Qwen Flash pipeline-parallel deployment. Dankclaw is an AMD Strix Halo APU (gfx1151) with an M.2 dock carrying an RTX 3090 at PCIe x4. The M.2 slot docs in the repo are split: dankserver (B650-E, M.2_2 free for R9700 riser) vs dankclaw (M.2 dock for 3090). The Qwen Flash pipeline-parallel M.2 question was aborted before being answered.