@prismer/runtime 1.9.6 → 1.9.21

package/CHANGELOG.md

@@ -1,5 +1,61 @@
 # Changelog — @prismer/runtime
 
+## v1.9.7 — 2026-05-12 — Device capacity fix + setup daemon auto-start
+
+### Fixed
+
+- **`host.declare` now upserts `im_containers` row** so agent.register's
+  `assertDeviceCapacityAvailable` can find the daemon device. Previously only
+  Redis presence was written; the MySQL `im_containers` table was empty for
+  local daemons, causing `UNKNOWN_DAEMON` (409) on every agent create from
+  the workspace UI.
+- **`prismer setup` auto-starts daemon when config already exists** — the
+  "Already configured" branch was returning early before `startDaemonDetached`,
+  leaving users with a working config but no running daemon (no device
+  appeared in the workspace).
+
+### Internal
+
+- `src/im/ws/handler.ts` — upsert im_containers on host.declare, guarded
+  against empty daemonId; `startedAt` preserved across heartbeat redeclares.
+- `src/im/api/register.ts` — `assertDeviceCapacityAvailable` matches by
+  `OR(agentImUserId, daemonId)` so both runtime-installation and local daemon
+  paths find the device row.
+- `src/im/db/index.ts` — Prisma client re-export (unchanged, listed for audit
+  completeness).
+
+## v1.9.6 — 2026-05-12 — Refactoring wave: register hardening + CLI version sync
+
+Batch delivery of §30 / §31 refactoring items affecting IM register flow,
+CEO authorization data layer, and runtime version hygiene.
+
+### Fixed
+
+- **CLI `--version` + banner displayed stale `1.9.3`** after package.json was
+  bumped to 1.9.6. `src/cli/index.ts` hardcoded `VERSION` const and
+  `src/cli/util.ts` banner strings were missed in the 1.9.4→1.9.5→1.9.6 bump
+  chain. Now reads `1.9.6` in both places.
+- **Hermes adapter prompt still referenced old `im_send_to_agent` /
+  `im_list_agents` tool names** after the MCP 58-tool rename sweep. Replaced
+  with `prismer.agent.send` / `prismer.conversation.listAgents`. The old names
+  returned 404 at dispatch time if the adapter actually called them.
+- **`--json` output from `agent list` now surfaces `local.hosted: true`
+  correctly** for agents that were registered with an adapter (was returning
+  `local.hosted: false` when the local mirror hadn't synced yet).
+
+### Internal
+
+- Tool name sweep: `sdk/prismer-cloud/runtime/src/adapters/hermes/index.ts`
+  (`buildHermesPrompt`), `src/im/types/im-events.ts` (unused old types),
+  `src/im/services/message.service.ts` (WS event type const),
+  `src/im/daemon/dispatch.ts` (dispatch compose).
+- Version files bumped via `sdk/build/version.sh --scope prismer-cloud --patch`:
+  `VERSION`, all SDK package.json, `mcp/src/index.ts`,
+  `python/prismer/__init__.py`, `rust/Cargo.toml`, plugin manifests, root
+  `package.json`, `src/lib/version.ts`.
+
+---
+
 ## Unreleased — Origin Adapter framework + memory-curation skill
 
 Doc 26 §4 Phase 2 + doc 27 rev 5 §3. Daemon-side asset producers behind a