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
This commit is contained in:
Frank committed 2026-09-17 19:24:02 -07:00
1 parent eebcfbf5ac
commit c3f30bdbd0
23 files changed
+81 -76

No files matched your search

@@ -1,4 +0,0 @@
Verifying the Marreta auth chain:
1. Probe `http://localhost:8017/` from host (expected 000, listener is in Caddy netns).
2. Check `authentik-proxy-provider-app-link` for null flows.
3. Ensure non-browser clients can bypass JS challenges or use backend datasource URLs.
@@ -1,4 +0,0 @@
Verify if the request fits the allocated KV pool:
1. Run `podman logs frank-large | grep 'kv pool:'`.
2. Compare 'reserved' count to 'requested' count.
3. Note: /health does not prove pool size; absence of WARNING is not evidence of headroom.
@@ -1,4 +1,7 @@
To retrieve logs for a rootless Quadlet service (e.g., frank-large):
1. Use `podman logs frank-large` for container-specific output.
2. Use `journalctl --user -u frank-large` for systemd-integrated output.
3. Use `podman logs frank-large 2>&1 | grep -E '^(dmalloc|kv pool):'` to filter for memory/allocations.
Retrieving logs for a rootless Quadlet container.
Specific considerations:
1. Use `podman logs <container>` for standard output.
2. Use `journalctl --user -u <unit_name>` for systemd-integrated logs.
3. Filter specifically for dmalloc/kv pool events to monitor memory state.
4. Note that rootless quadlet log retrieval has specific gotchas regarding standard output capturing in nested namespaces.