@prismer/runtime 1.9.7 → 1.9.21

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # 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,