@prismer/runtime 1.9.24 → 2.0.1

package/CHANGELOG.md

@@ -1,5 +1,208 @@
 # Changelog — @prismer/runtime
 
+## Unreleased
+
+## v2.0.1 — 2026-05-21 — Skill multi-file manifest protocol (§A.7 Phase 1) + URL asset fetch
+
+Coordinated v2.0.1 patch release. `/VERSION` → 2.0.1. Internal preview only;
+open-source npm publish deferred.
+
+### Added — Multi-file Skill Manifest protocol (agentskills.io 合规)
+
+`src/daemon/skill-sync.ts` extended for the §A.7 multi-file manifest
+protocol. Existing single-file callers stay functional via dual-write on
+cloud side.
+
+- **New wire shape**: cloud `/api/im/skills/installed` now returns
+  `skill.contentManifest` (JSON `files[]`) + `skill.contentManifestRevision`
+  (merkle). Daemon parses files[], per-file writes to
+  `<skillsRoot>/<slug>/<path>`, per-file sha256 verifies, computes merkle,
+  acks back to cloud.
+- **`computeMerkle(files)`** export — sha256 of sorted `"path:sha256\n"`
+  lines. Same formula the cloud uses, so
+  `IMAgentSkill.installedRevision == manifestRevision` after ack.
+- **Hybrid inline/url storage** — files ≤ 100 KB inline as base64;
+  > threshold goes to S3 presigned URL (env-overridable via
+  `PRISMER_SKILL_INLINE_THRESHOLD_BYTES`).
+- **Path traversal guard** — `isSafeRelativePath` rejects `..`, absolute
+  paths, symlink-escaping joins. Double-checked at the writeFile call site.
+- **Legacy single-file fallback** — when cloud row has `contentManifest=null`
+  (pre-migration 400), daemon synthesises a single-file manifest
+  `[{path:"SKILL.md", sha256: sha256(content)}]` and acks the same merkle
+  the cloud computes (cloud side aligned in this release too).
+
+### Added — `AssetCache.getOrFetchUrl()` — public URL fetch with SSRF + size + redirect guards
+
+`src/asset-cache.ts` new helper mirrors `getOrFetch` shape but takes a URL.
+Hash computed after download; cache-key = sha256 of body bytes.
+
+- **SSRF guard**: DNS-resolves host before each hop, rejects loopback /
+  RFC1918 / link-local / cloud-metadata IPv4 + IPv6 ULA/link-local.
+  Cross-host redirects re-validate before following.
+- **Manual redirect chain** — max 3 hops; refuses loops.
+- **Hard timeout** — default 15 s, override via env
+  `PRISMER_URL_FETCH_TIMEOUT_MS`.
+- **Streaming read with abort-at-limit** — default 5 MiB, override via env
+  `PRISMER_URL_FETCH_MAX_BYTES`. Truncated bodies are NOT cached.
+- Non-2xx throws; caller surfaces an `error` observation.
+
+### Tests
+
+- 11 new `test/skill-sync-multifile.test.ts` (mocked cloud, real file
+  writes to tmpdir, sha256 + merkle verification).
+- Runtime vitest 362/362 PASS.
+
+## v2.0.0 — 2026-05-19 — `prismer` daemon bin retained + Skill Gate GA
+
+Coordinated v2.0.0 GA. `/VERSION` (single source of truth) → 2.0.0 via
+`sdk/build/version.sh`. The headline bin-split was resolved by keeping
+`@prismer/runtime` on `bin: { prismer }` (daemon priority is higher than
+SDK, so the daemon claims the canonical name) and renaming `@prismer/sdk`
+to `bin: { cloud }` instead.
+
+### Changed — **Binary retained: `bin: prismer`** (daemon priority decision, 2026-05-19)
+
+- `package.json` `bin` keeps mapping `prismer` → `./dist/cli.js`. `@prismer/sdk`
+  renamed its binary to `cloud` (see `@prismer/sdk` CHANGELOG). The two bins
+  now coexist — sandbox image install order no longer creates conflicts.
+- Executable shim at `src/bin/prismer.ts`. Tsup emits to `dist/cli.js`;
+  package.json bin maps it to `prismer`.
+- `cli/index.ts`: `new Command('prismer')` (unchanged from v1.x); `--help`
+  and parse errors report `Usage: prismer [options]`.
+- Help text + error prefixes + cookbook references stay on `prismer` across
+  `src/cli/*`, `src/cli/commands/*`, `src/config.ts`, `src/daemon-id.ts`,
+  `src/pair.ts`, `src/index.ts`. (An intermediate Session-3 commit had
+  temporarily renamed these to a daemon-suffixed form; reverted before GA
+  per user direction.)
+- See `docs/release200/02-v20-daemon-runtime-plan.md` §CLI 边界更新 for the
+  rationale (fixes v1.x sandbox-image bin clobber bug that caused the v2.0
+  Built-in skill Kanban scheduling regression).
+
+### Changed — **VERSION sync**
+
+- `cli/index.ts` `VERSION` literal synced from 1.9.7 → 2.0.0. Now sourced
+  from `/VERSION` via `sdk/build/version.sh`.
+
+### Added — **Skill Gate foundation (v2.0 GA gate)**
+
+The Skill Gate (cloud `/skills/ack` round-trip + dispatch-time skill sync
++ `SkillLoader` per-adapter) was incrementally landed across 1.9.x cuts.
+v2.0 promotes it to GA. Recap of the components carried by this release:
+
+- **SkillSyncManager** (`daemon/skill-sync.ts`): reconciles
+  `agent.skills.list` ↔ local `~/.prismer/agents/<id>/skills/`,
+  writes `SKILL.md` to disk, replies `skills.ack` once content is durable.
+- **SkillLoader SPI**: adapters can opt into per-dispatch skill payload
+  composition. Hermes + OpenClaw implement; Codex + claude-code are no-ops
+  in 2.0 (skill sync still writes files to disk for those, but the
+  dispatch-time injection is gated by adapter capability).
+- **v2.0 Skill Gate scope**: dispatch-time skill payload coverage validated
+  for `hermes` + `openclaw` only. `codex` + `claude-code` skill sync remains
+  a file-write no-op pending adapter framework support (tracked v2.1+).
+- Live-gate evidence: `dev-loop.sh skill-live-gate` /
+  `scripts/sandbox/e2e/skill-agent-dispatch-live.ts` capture 21 Built-in +
+  1 magic-marker skill in `POST /v1/runs.instructions` (~31 KB payload).
+  See `docs/release200/evidence/05-live-dispatch-gate-2026-05-19.md`.
+
+### Added — **Origin Adapter framework** (promoted from "Unreleased")
+
+`daemon/asset/origin/` — daemon-side asset producers behind a uniform
+OriginAdapter SPI (doc 26 §4 Phase 2). Foundation for the v2.0 `assets` +
+`ingest` Built-in skills.
+
+- **SPI** (`spi.ts`): `OriginAdapter` interface with
+  `kind: 'upload' | 'drop-folder' | 'agent-gen'`,
+  `observe / identifySource / fetch` decomposition. Identification stays
+  separate from byte fetch so the outbox can dedupe before paying read cost.
+- **Outbox** (`outbox.ts`): SQLite-backed pending-upload queue mirroring
+  `daemon/memory/outbox.ts` shape — Zod validation → dead-letter,
+  `idempotencyKey = sha256(originKind|wid|sourceRef|observedAt)` UNIQUE,
+  `claimNext()` transactional, `recordFailure(maxAttempts)` auto-spills to
+  dead-letter. Restart-resume-friendly.
+- **Drop-folder adapter** (`drop-folder.ts`): polls
+  `~/.prismer/workspaces/<wid>/drop/` (1 s tick, recursive), enqueues
+  observations, moves files to `uploaded/` on success and `upload-failed/`
+  on persistent failure.
+- **Agent-gen adapter** (`agent-gen.ts`): synchronous
+  `handleAssetWrite(body, { cloud })` for the `POST /local/asset/write` RPC.
+- **Web-upload adapter** (`web-upload.ts`): cloud-side marker class for SPI
+  symmetry.
+- **Upload runner** (`upload-runner.ts`): generic worker draining the
+  outbox; `onUploadSuccess` / `onUploadFailure` hooks per adapter.
+- **`POST /local/asset/write` route** (`local-server.ts`): wires
+  `onAssetWrite` sink alongside `onDispatch` / `attachMemory`. Returns
+  `{ assetId, contentHash, prismerUri }`. 400 / 502 / 501 error contract.
+
+### Added — **memory-curation skill** (promoted from "Unreleased")
+
+- **Codex adapter** (`adapters/codex/index.ts`): `buildCodexPrompt()`
+  extracted as pure function; injects `MEMORY_CURATION_SKILL_TEXT` as
+  system-prompt preamble (Codex has no native skill framework).
+- **Embedded skill module** (`src/skills/memory-curation.ts`): regenerated
+  from canonical `sdk/prismer-cloud/skill/memory-curation.md` via
+  `scripts/regenerate-memory-curation-skill.cjs`.
+
+### Added — **CLI hardening pass** (promoted from "Unreleased")
+
+Audit of the 16-verb CLI surface. No new daemon behavior; existing commands
+now fail closed and emit consistent JSON.
+
+- **`prismer config (path|show|set)`** — inspect or edit `~/.prismer/config.toml`.
+  `show` redacts the api_key by default; `--reveal` prints clear text.
+  `set cloud_api_base <url>` runs through `normalizeCloudUrl`,
+  `set api_key sk-…` validates the key format.
+- **`prismer setup --check`** — dry-run mode. Validates `--cloud`, prints
+  the would-be config target and api-key source, returns without touching
+  disk. JSON: `{ok:true, check:true, mode, cloud, …}`.
+- **Default `--cloud` URL is `https://prismer.cloud`** (was
+  `https://cloud.prismer.dev`). Visible in `setup --help` / `pair --help`.
+- **Stable error codes** on every CLI exit path so JSON consumers can
+  branch on `error.code` (e.g. `invalid_cloud_url`, `config_missing`,
+  `task_create_failed`).
+
+### Fixed — **CLI hardening pass** (promoted from "Unreleased")
+
+- **`--json` was dead code on every subcommand.** `applyCommonFlags`
+  stripped `--json` from argv before commander parsed per-command options,
+  so JSON branches silently no-op'd (e.g. `prismer status --json` exit 0
+  with no body). Now `--json` is kept in argv and declared on every
+  printing subcommand.
+- **`prismer setup --cloud 0.0.0.0:3000` accepted bare host:port and
+  exploded with raw Zod JSON.** `normalizeCloudUrl()` now auto-prefixes
+  `http://` for bare host shapes and rejects everything else with a
+  single-line error.
+- **`exitWithError` is JSON-aware.** Emits
+  `{ok:false, error:{code, message}}` to stdout when UI is in JSON mode.
+  Every action handler goes through a `runAction(fn, { code })` wrapper.
+- **Daemon ignored application-level `AUTH_FAILED`.** The runner now
+  detects `AUTH_FAILED` / `AUTH_REQUIRED` / `auth_invalid` payload codes,
+  emits `auth-failed`, and `daemon run` clears the pid file + exits 2.
+- **`memory stats` returned exit 0 when the gateway was unavailable** even
+  though `delete` and `sync` exited 1 in the same condition. Now consistent.
+- **`task create` printed `(0): fetch failed`.** Network errors now render
+  as `(network error): …` so the `0` HTTP status doesn't leak.
+- **`daemon restart` dropped `--port` / `--foreground` / `--no-local-server`
+  on the floor.** Restart now forwards the flags through to `start`.
+- **`daemon logs --tail` read the entire log file into memory.** Now seeks
+  from the end in 64 KiB chunks.
+
+### Tests
+
+- Origin Adapter framework: 44 new vitest assertions across 8 new test files
+  (`origin-spi`, `origin-outbox`, `origin-drop-folder`, `origin-agent-gen`,
+  `local-server-asset-write`, `origin-web-upload`,
+  `skill-memory-curation-sync`, `codex-adapter-skill-injection`).
+- Acceptance criteria covered: doc 26 §5 L2-T1 (100-burst, dead-letter=0),
+  L2-T2 (restart resume), L2-T3 (RPC sync return).
+- Total runtime suite: 192 → 234 passing, 0 failures.
+
+### Cookbook
+
+- `docs/cookbook/m-asset-origin-drop-folder.md`
+- `docs/cookbook/m-asset-origin-agent-gen.md`
+
+---
+
 ## v1.9.7 — 2026-05-12 — Device capacity fix + setup daemon auto-start
 
 ### Fixed
@@ -56,116 +259,6 @@ CEO authorization data layer, and runtime version hygiene.
 
 ---
 
-## Unreleased — Origin Adapter framework + memory-curation skill
-
-Doc 26 §4 Phase 2 + doc 27 rev 5 §3. Daemon-side asset producers behind a
-uniform OriginAdapter SPI; agent-driven memory curation guidance loaded into
-the four host adapters.
-
-### Added — **Origin Adapter framework** (`daemon/asset/origin/`)
-- **SPI** (`spi.ts`): `OriginAdapter` interface with `kind: 'upload' | 'drop-folder' | 'agent-gen'`, `observe / identifySource / fetch` decomposition. Identification stays separate from byte fetch so the outbox can dedupe before paying read cost.
-- **Outbox** (`outbox.ts`): SQLite-backed pending-upload queue mirroring `daemon/memory/outbox.ts` shape — Zod validation → dead-letter, `idempotencyKey = sha256(originKind|wid|sourceRef|observedAt)` UNIQUE, `claimNext()` transactional, `recordFailure(maxAttempts)` auto-spills to dead-letter. Restart-resume-friendly (rows persist across daemon process death).
-- **Drop-folder adapter** (`drop-folder.ts`): polls `~/.prismer/workspaces/<wid>/drop/` (1s tick, recursive), enqueues observations, on success moves files to `uploaded/`, on persistent failure to `upload-failed/`. Mime detected by extension.
-- **Agent-gen adapter** (`agent-gen.ts`): synchronous handler `handleAssetWrite(body, { cloud })` for the new `POST /local/asset/write` RPC. Daemon writes under owner identity; `sourceAgentImUserId` is a passenger metadata field (decoupled from auth — no dependency on Line B B1 POST permission alignment).
-- **Web-upload adapter** (`web-upload.ts`): cloud-side marker class for SPI symmetry. Throws if invoked daemon-side; the actual upload is the cloud `POST /api/im/assets` handler.
-- **Upload runner** (`upload-runner.ts`): generic worker draining the outbox, dispatching to adapters by `originKind`. Hooks `onUploadSuccess` / `onUploadFailure` on the adapter (drop-folder uses these for the uploaded/upload-failed file moves).
-- **`POST /local/asset/write` route** (`local-server.ts`): wires `onAssetWrite` sink alongside `onDispatch` / `attachMemory`. Returns `{ assetId, contentHash, prismerUri: 'prismer://workspace/<wid>/asset/<contentHash>' }`. 400/502/501 error contract.
-
-### Added — **memory-curation skill** (doc 27 rev 5 §3)
-- **Codex adapter** (`adapters/codex/index.ts`): `buildCodexPrompt()` extracted as pure function; injects `MEMORY_CURATION_SKILL_TEXT` as system-prompt preamble (Codex has no native skill framework).
-- **Embedded skill module** (`src/skills/memory-curation.ts`): regenerated from canonical `sdk/prismer-cloud/skill/memory-curation.md` via `scripts/regenerate-memory-curation-skill.cjs` (also handles the openclaw / Python / CC plugin copies).
-
-### Tests
-- 44 new vitest assertions across 8 new test files: `origin-spi`, `origin-outbox`, `origin-drop-folder`, `origin-agent-gen`, `local-server-asset-write`, `origin-web-upload`, `skill-memory-curation-sync`, `codex-adapter-skill-injection`.
-- Acceptance criteria covered: doc 26 §5 L2-T1 (100-burst, dead-letter=0), L2-T2 (restart resume), L2-T3 (RPC sync return).
-- Total runtime suite: 192 → 234 passing, 0 failures.
-
-### Cookbook
-- `docs/cookbook/m-asset-origin-drop-folder.md`
-- `docs/cookbook/m-asset-origin-agent-gen.md`
-
-### Phase staging — what this PR does NOT yet wire
-- **Daemon `runner.ts` does not yet construct `OriginOutbox` / `DropFolderAdapter` / `UploadRunner`.** The SPI + handlers ship here; the runner-level wiring + a concrete `CloudUploadClient` (FormData wrapper around the existing `CloudClient`) land in a follow-up PR alongside the rest of doc 26 §4 Phase 2 production-enable work.
-- `POST /local/asset/write` returns **501 `asset_write_unavailable`** in production until that PR wires the `onAssetWrite` sink on `LocalServer`.
-- Acceptance criteria (L2-T1, L2-T2, L2-T3) are validated against `fakeCloud` in unit tests; an end-to-end cookbook run against the live `POST /api/im/assets` handler is part of the follow-up.
-
----
-
-## Unreleased — CLI hardening pass
-
-User-reported "大量空洞" — full audit of the 16-verb CLI surface. No new daemon
-behavior; existing commands now fail closed and emit consistent JSON when
-`--json` is set.
-
-### Fixed
-
-- **`--json` was dead code on every subcommand.** `applyCommonFlags` stripped
-  `--json` from argv before commander parsed per-command options, so
-  `if (opts.json) printJson(...)` branches in setup/status/workspace/sandbox/
-  asset/cookbook/chat never fired. UI mode was set, but the pretty branches
-  silently no-op'd in JSON mode and stdout came out empty (e.g.
-  `prismer status --json` exit 0 with no body). Now we keep `--json` in argv
-  and declare it on every subcommand that prints — empty-output paths are gone.
-- **`prismer setup --cloud 0.0.0.0:3000` accepted bare host:port and exploded
-  with raw Zod JSON six stack frames later.** `normalizeCloudUrl()` now
-  auto-prefixes `http://` for bare host shapes and rejects everything else
-  with a single-line error. The same helper is wired into `pair`, `setup`,
-  and `config set cloud_api_base`.
-- **`exitWithError` is JSON-aware.** When the UI is in JSON mode it emits
-  `{ok:false, error:{code, message}}` to stdout (with stable codes like
-  `invalid_cloud_url`, `config_missing`, `task_create_failed`) instead of
-  the pretty `Error: …` line. Every action handler now goes through a
-  `runAction(fn, { code })` wrapper that catches throws — including the
-  `loadConfig()` "Config not found" throw that previously bubbled to
-  commander's default handler with a `prismer:` prefix.
-- **Daemon ignored application-level `AUTH_FAILED`.** Cloud sends an
-  application error frame (not WS close 4001) when the post-handshake API
-  key lookup fails; the runner only logged it and stayed alive forever with
-  a stale pid file. Now the runner detects `AUTH_FAILED` / `AUTH_REQUIRED`
-  / `auth_invalid` payload codes, emits `auth-failed`, and `daemon run`'s
-  handler stops the runner, clears the pid file, and exits 2.
-- **`memory stats` returned exit 0 when the gateway was unavailable** even
-  though `delete` and `sync` both exit 1 in the same condition. All five
-  memory subcommands now consistently set `process.exitCode = 1` when the
-  gateway is missing.
-- **`task create` printed `(0): fetch failed`.** Network errors now render
-  as `(network error): …` so the `0` HTTP status doesn't leak.
-- **`daemon restart` dropped `--port` / `--foreground` / `--no-local-server`
-  on the floor.** Restart now forwards the flags through to `start`.
-- **`daemon logs --tail` read the entire log file into memory.** Now seeks
-  from the end in 64 KiB chunks until enough newlines are collected — works
-  on the multi-MB logs that long-lived hosts accumulate.
-- **`--no-start` was a redundant declaration** of commander's automatic
-  `--no-X` negation; removed.
-
-### Added
-
-- **`prismer config (path|show|set)`** — inspect or edit
-  `~/.prismer/config.toml` without hand-editing TOML. `show` redacts the
-  api_key by default; `--reveal` prints clear text. `set cloud_api_base
-  <url>` runs through `normalizeCloudUrl`, `set api_key sk-…` validates
-  the key format.
-- **`prismer setup --check`** — dry-run mode. Validates `--cloud`, prints
-  the would-be config target and api-key source, and returns without
-  touching disk. JSON-friendly: `{ok:true, check:true, mode, cloud, …}`.
-- **Default `--cloud` URL is `https://prismer.cloud`** (was
-  `https://cloud.prismer.dev`). The default is now visible in
-  `setup --help` / `pair --help`.
-- **Stable error codes** on every CLI exit path so JSON consumers can
-  branch on `error.code` rather than parsing `error.message`.
-
-### Internal
-
-- New `src/cli/util.ts` helpers: `DEFAULT_CLOUD_BASE_URL`,
-  `normalizeCloudUrl(input)`, `runAction(fn, { code, sanitize })`, and the
-  JSON-aware `exitWithError(message, { code, exitCode, details })`.
-- `applyCommonFlags` now keeps `--json` in argv (only `--quiet`,
-  `--no-color`, `--color` are still stripped). Every subcommand that
-  prints JSON now declares `.option('--json', …)` so commander parses it
-  consistently; pure-text commands (`daemon stop`, `pair`, `banner`,
-  `adapter install / remove`) declare `--json` as a passthrough so
-  `prismer --json daemon stop` doesn't error.
-
 ## v1.9.3 — 2026-05-07 — Hosted agents + Hermes long-running + 16-verb CLI
 
 First published cut of `@prismer/runtime`. The runtime is the TS-only daemon that hosts Prismer agents on a user's Mac (under `launchd`) or inside a sandbox pod (as PID 1). One binary, one WebSocket to cloud, four in-process adapters, local SQLite mirror.

package/README.md

@@ -20,7 +20,7 @@ What the daemon-mode installer does:
 
 1. Detects OS / arch (Darwin or Linux x64/arm64; Windows requires WSL2).
 2. Installs Node.js via `fnm` under `$HOME/.local/share/fnm` if absent (no Homebrew, no sudo).
-3. Strict-pins `@prismer/runtime@1.9.3` (no caret) and installs globally via npm.
+3. Strict-pins `@prismer/runtime@2.0.0` (no caret) and installs globally via npm.
 4. Scaffolds `~/.prismer/{adapters,workspace,logs,bin}`.
 5. Writes `~/Library/LaunchAgents/com.prismer.daemon.plist` (label `com.prismer.daemon`, `KeepAlive=true`, `RunAtLoad=true`, `ProgramArguments` includes `--foreground`), then `bootout` + `bootstrap` to load it.
 6. Auto-runs `prismer adapter install <name>` for each adapter passed via `--adapters`.
@@ -32,7 +32,7 @@ Installer flags: `-y/--yes`, `--no-setup`, `-v/--verbose`, `--local <dir>` (inst
 ### npm (manual)
 
 ```sh
-npm install -g @prismer/runtime@1.9.3
+npm install -g @prismer/runtime@2.0.0
 prismer pair --device-name "$(hostname)"
 prismer daemon start
 ```
@@ -54,7 +54,7 @@ The container daemon binds `:7878` (controller proxy target) instead of the desk
 
 ## CLI reference (16 verbs)
 
-`VERSION = '1.9.3'`. Each verb is a `commander` subcommand under `src/cli/commands/`. Output is JSON (`--json`) or human-friendly ANSI by default.
+`VERSION = '2.0.0'`. Each verb is a `commander` subcommand under `src/cli/commands/`. Output is JSON (`--json`) or human-friendly ANSI by default.
 
 ### Lifecycle
 
@@ -405,17 +405,17 @@ shell = "bash"
 
 ## Troubleshooting
 
-- **LaunchAgent respawn loop after install** — the plist must include `--foreground` in `ProgramArguments`. v1.9.3 installs do this automatically; if you're upgrading from 1.8.x re-run `curl -fsSL https://prismer.cloud/install.sh | sh -s -- --component=daemon` (the installer does `bootout` + `bootstrap` to reload).
+- **LaunchAgent respawn loop after install** — the plist must include `--foreground` in `ProgramArguments`. v2.0.0 installs do this automatically; if you're upgrading from 1.8.x re-run `curl -fsSL https://prismer.cloud/install.sh | sh -s -- --component=daemon` (the installer does `bootout` + `bootstrap` to reload).
 - **Daemon shows "waiting for ~/.prismer/config.toml"** — that's expected behavior pre-pair. Run `prismer pair` (or `prismer setup sk-prismer-...`) and the daemon snaps to attention within 5s.
 - **Cloud unreachable** — `prismer status` will print the failing base URL. Common causes: stale `cloud_api_base` after a tenant move (run `prismer setup --force <new-key> --cloud <url>`), or the API key was rotated (mint a new one with `prismer setup --token <jwt>`).
-- **Agent shows under `__unbound__` device in workspace runtime view** — the daemon's `agent.host.declare` is not stamping `daemonId`. Confirm you're on `@prismer/runtime@1.9.3` (the `daemonId` payload field landed in 1.9.3).
-- **`claude --print` runs report "no stdin data received in 3s"** — fixed in 1.9.3 (`stdio: ['ignore', 'pipe', 'pipe']`). Older runtimes will surface the warning but the dispatch still completes.
+- **Agent shows under `__unbound__` device in workspace runtime view** — the daemon's `agent.host.declare` is not stamping `daemonId`. Confirm you're on `@prismer/runtime@2.0.0` (the `daemonId` payload field is required as of v2.0.0).
+- **`claude --print` runs report "no stdin data received in 3s"** — fixed in v2.0.0 (`stdio: ['ignore', 'pipe', 'pipe']`). Older runtimes will surface the warning but the dispatch still completes.
 - **Tasks dispatch but `@`-mention messages never reach the agent** — cloud-side `SHADOW_JOIN_FAILED` rollback. The runtime's `agent.host.declare` requires every declared agent to auto-join all its conversation rooms; check daemon logs for the rollback line and re-register the agent (`prismer agent register …`) to fix the cloud-side row.
 - **Stuck task that never replies** — the 60s reaper aborts and replies `{ok:false, error.code:'daemon_task_timeout'}` after `max(timeoutMs, 5min)`. Cloud will mark the task `failed` accordingly. Inspect via `prismer task get <id>`.
 
 ## Versioning
 
-> See [CHANGELOG.md](./CHANGELOG.md). Current: **v1.9.3** (2026-05-07).
+> See [CHANGELOG.md](./CHANGELOG.md). Current: **v2.0.0** (2026-05-19).
 
 ## License