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.

CHANGELOG.md

@@ -25,11 +25,28 @@ release PR may merge — and a section is closed at the commit that bumps it.
 
 ### Fixed
 
+- **Honcho long-term memory read nothing at all** against a self-hosted Honcho v3
+  server: the `honcho_context` and `honcho_search` tools answered "no context", the
+  automatic memory injection into chats silently never happened, and the *Long-term
+  memory* page showed an empty overview — while the server was healthy and full of
+  derived facts. The plugin parsed an outdated response shape; it now reads the
+  `representation` / `peer_card` fields Honcho 3.0.x actually returns, and search is a
+  real ranked semantic search whose fact ids can be deleted via `honcho_conclude`.
+- The `honcho_profile` tool could not **write** the peer card (the API rejects a bare
+  array — it wants a `{"peer_card": …}` wrapper) and read back a raw JSON envelope;
+  writes now succeed and reads show the facts, or a clean "no card set yet".
 - The **Providers** page said *API key missing* on every provider, including the ones
   with a perfectly good key. It now reports the real state. Editing a provider no longer
   shows the saved key in the form either — leave the field blank and the existing key is
   kept, type a new one to replace it.
 
+### Changed
+
+- The self-hosted Honcho compose setup (`honcho/docker-compose.yml`) pins the server
+  image **by digest (3.0.11)** instead of tracking `:latest` — ghcr publishes no v3
+  version tags, and an untracked pull is what silently changed the API schema under the
+  plugin. Upgrading Honcho is now a deliberate, verified step.
+
 ### Security
 
 - An LLM provider's API key is never sent to the browser any more: the provider list and