fix(honcho): read Honcho 3.0.x response schema — memory reads were silently empty

Against a self-hosted Honcho 3.0.11 every read path came back empty while
the server was healthy and full of derived facts: the plugin parsed a
`conclusions`/`summary` shape the API no longer emits.

- honcho-client: typed models for the real schema — `PeerContext`
  (`representation` markdown + `peer_card`), `SessionContext` (`summary` as
  an object, `peer_representation`), wrapped `PeerCard` (a bare array on PUT
  is a 422, which also broke `honcho_profile` writes).
- plugin: the turn-time injection and `honcho_context` read the
  representation; `honcho_search` and the page's /search now use
  `conclusions/query` (observer/observed scoping inside `filters`) — a real
  ranked semantic search with fact ids, which `peer_context?search_query`
  never provided; /overview returns card + representation + conclusions.
- compose: pin the Honcho image by digest (3.0.11) — ghcr publishes no v3
  semver tags, and an untracked `:latest` pull is what drifted the schema.
- tests: fixture tests from payloads captured on the live server, plus an
  env-gated live smoke test (HONCHO_E2E_URL/_WS/_PEER, `cargo test
  -p honcho-client -- --ignored`) — run it before any future Honcho bump.

honcho/README.md

@@ -1,8 +1,8 @@
 # Honcho — self-hosted Docker package
 
 This folder contains a ready-to-run Docker Compose setup for [Honcho](https://honcho.dev),
-the memory server used by the personal-agent's Honcho plugin
-([`src/plugin/honcho/`](../src/plugin/honcho/)).
+the memory server used by the Honcho plugin
+([`crates/plugin-honcho/`](../crates/plugin-honcho/)).
 
 ---
 
@@ -10,11 +10,16 @@ the memory server used by the personal-agent's Honcho plugin
 
 | Service | Image | Port | Role |
 | --- | --- | --- | --- |
-| `api` | `ghcr.io/plastic-labs/honcho:latest` | **8000** | REST API (the endpoint personal-agent talks to) |
+| `api` | `ghcr.io/plastic-labs/honcho@sha256:59f0…8c6b` (**3.0.11**, digest-pinned) | **8000** | REST API (the endpoint the app talks to) |
 | `deriver` | same image | — | Background worker: extracts conclusions, summaries, peer representations |
 | `db` | `pgvector/pgvector:pg17` | 5432 (internal) | PostgreSQL + pgvector (vector search) |
 | `redis` | `redis:7-alpine` | 6379 (internal) | Cache for session context |
 
+> The Honcho image is **pinned by digest** because ghcr publishes no v3 semver
+> tags (only `latest`), and the plugin parses a version-specific API schema —
+> a silent `:latest` bump already changed response shapes once. Upgrade
+> deliberately: pick the new digest, verify the plugin against it, then edit.
+
 Data is stored in named Docker volumes (`honcho_db`, `honcho_redis`) and survives container restarts.
 
 ---
@@ -140,7 +145,8 @@ docker compose restart api
 # Stop and wipe all data (destructive!)
 docker compose down -v
 
-# Upgrade to a newer Honcho image
+# Upgrade Honcho: bump the pinned digest in docker-compose.yml (deliberately —
+# the plugin's API parsing is verified against the pinned version), then
 docker compose pull
 docker compose up -d
 ```
@@ -181,5 +187,5 @@ docker compose up -d --build
 - [Honcho GitHub](https://github.com/plastic-labs/honcho)
 - [Honcho docs](https://docs.honcho.dev)
 - [Self-hosting guide (official)](https://docs.honcho.dev/v3/contributing/self-hosting)
-- [personal-agent Honcho plugin docs](../docs/honcho.md)
-- [personal-agent Memory architecture](../docs/memory.md)
+- [Honcho plugin docs](../docs/plugins/honcho.md)
+- [Memory architecture](../docs/memory.md)