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

omp-docs/.okf/config.yaml

@@ -7,7 +7,7 @@ bundle:
   version: "0.1"
   author: "pi agent system"
   description: "Cached documentation for tools, configurations, and systems used during pi agent sessions."
-  root: "/home/dank/.pi/agent/docs"
+  root: "~/.omp/omp-docs"
 
 generator:
   # Index generation settings

omp-docs/engineering/agents-files.md

@@ -50,7 +50,7 @@ To make a repository work in both AGENTS.md and CLAUDE.md workflows, create a `C
 
 ## SYSTEM.md
 
-`SYSTEM.md` sets the system-level role and behavior for an agent. It establishes the persona, the prime directive, and the binding rules. In this setup, `/home/dank/.pi/agent/SYSTEM.md` defines the Comrade Chief Designer persona and the ASD-STE100 voice rules.
+`SYSTEM.md` sets the system-level role and behavior for an agent. It establishes the persona, the prime directive, and the binding rules. In the pi-era setup, `/home/dank/.pi/agent/SYSTEM.md` defined the Comrade Chief Designer persona and the ASD-STE100 voice rules; the live equivalent is `~/.omp/agent/APPEND_SYSTEM.md`.
 
 Use `SYSTEM.md` for stable, cross-project rules. Use `AGENTS.md` for project-specific context. Do not duplicate content between them. Keep the division of labor clear.
 

omp-docs/pi/index.md

@@ -47,13 +47,15 @@ graph TD
 
 ## Note on the Live Default
 
-`models.json` defines the live provider set. The main session provider is
-`llamacpp`; the default model is `frank-default-large` (Dankclaw). Subagents
-default to the local provider with `subagents.defaultModel = frank-default-small`
-(Dankserver); larger roles map to `frank-default-large`. Two scopes own settings:
-the user `~/.pi/settings.json` (main → Dankclaw/large) and the project
-`/home/dank/.pi/agent/settings.json` (main → Dankserver/small). When the two
-disagree, the project-scope `settings.json` in the agent home wins for the agent's
-own main session; the user-scope file governs the interactive `pi` session.
+In the pi era, `models.json` defined the live provider set: the main session
+provider was `llamacpp` with default model `frank-default-large` (Dankclaw);
+subagents defaulted to `frank-default-small` (Dankserver); larger roles mapped
+to `frank-default-large`. Two scopes owned settings: the user
+`~/.pi/settings.json` (main → Dankclaw/large) and the project
+`/home/dank/.pi/agent/settings.json` (main → Dankserver/small); when they
+disagreed, the project-scope file won for the agent's own main session.
 
-> **Note:** This documentation describes the pi-coding-agent era. The system has since migrated to the OMP harness era. Configuration is now at `~/.omp/agent/config.yml` and `~/.omp/agent/models.yml` (imported from `~/.pi/agent/models.json`). Legacy `~/.pi/settings.json` and `~/.pi/agent/settings.json` remain as pi-era artifacts. New OMP-managed skills live in `~/.omp/agent/managed-skills/` alongside the legacy symlinked skills at `~/.pi/agent/skills/` → `~/.agents/skills/`.
+> **Note:** This documentation describes the pi-coding-agent harness (config
+> format, packages, skill system) as general reference material. The live
+> harness is OMP at `~/.omp/`; OMP-managed skills live in
+> `~/.omp/agent/managed-skills/`.

omp-docs/pi/packages/pi-web-access.md

@@ -20,7 +20,7 @@ timestamp: 2026-08-28
 
 Web search, content extraction, and video understanding for Pi. It calls your self-hosted SearXNG first when one is configured, and falls through to other providers.
 
-> **Active setup:** `~/.pi/web-search.json` locks search to SearXNG at `http://192.168.0.143:8081` (dankclaw), permits LAN fetches via `ssrf.allowRanges`, and sets `maxInlineContentChars` to 50000. The config file is cached in memory per process — a changed file takes effect on the next Pi session.
+> **Pi-era setup:** `~/.pi/web-search.json` locked search to SearXNG at `http://192.168.0.143:8081` (dankclaw), permitted LAN fetches via `ssrf.allowRanges`, and set `maxInlineContentChars` to 50000. The config file is cached in memory per process — a changed file takes effect on the next Pi session.
 
 ---