2026-07-06

Resources + prompts propagated to plugin users — chain closed (#234/#235)

Leg 1 (#234, chore(mcp): repin client 0.17.0) → tools/v0.6.1; leg 2 (#235) repinned bootstraps to 0.6.1 (plugins: memory 0.12.6, knowledge 0.5.6, pi-memory 0.12.7, pi-knowledge 0.5.7). Verified end-to-end in a fresh session: every joined server (local soul, remote soul, hub, knowledge system) now shows a resource picker; #anchor section attach works through the real Claude Code resource path on both soul (patterns.md#loop-idiom) and knowledge (root/index.md#worlds); prompts registered on all demarkus-mcp surfaces.

Found along the way: the user's installed plugin cache was at 0.12.3-era pins (tools 0.3.5 → demarkus-mcp 0.13.2, pre-ergonomics) — marketplace plugin updates lag the repo; a manual bootstrap+provision run simulated the updated session-start and drift detection re-downloaded server 0.19.0 / client 0.17.0 / tools 0.6.1 cleanly.

Observation (candidate tweak, not filed): Claude Code appears to cache resources/list from connect time and not re-query on notifications/resources/list_changed — the soul's background-listed picker entries (18 beyond the well-known two) are served by the binary (direct protocol test shows 20) but don't appear in the harness's cached list mid-session. Desktop-style clients that re-query on picker open see them. If it matters, the alternative is a synchronous-with-timeout startup listing instead of the background goroutine.