@prismer/runtime 1.9.1 → 1.9.6

package/CHANGELOG.md

@@ -0,0 +1,178 @@
+# Changelog — @prismer/runtime
+
+## 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.
+
+### Added
+
+- **CLI: 8 new verbs** — `setup`, `banner`, `chat`, `cookbook`, `asset`, `sandbox`, `memory`, `events` (+ `events:stats`). Plus `workspace` (already shipped). Total surface is now **16 verbs**.
+  - `setup` — three onboarding paths (direct API key, `--token <jwt>` mints a daemon-scoped key via `POST /api/keys`, `--pair` delegates to QR/local-only). `--force` archives `local.db` → `local.db.<iso>.bak` when key/cloud/daemon_id changed.
+  - `chat` — `me` / `direct` / `messages` / `group (create|send|messages|remove-member)`. Sanitizes `sk-prismer-*` from error messages.
+  - `cookbook run` — 54release MVP regression suites (`status` / `im` / `task` / `group` / `asset` / `sandbox`); `--strict` treats skips as failure.
+  - `asset` — `list` / `upload` (multipart) / `download` / `get` / `by-hash`.
+  - `sandbox` — full `/api/sandboxes` CRUD + `runCmd` + log streaming.
+  - `memory` — daemon Memory Gateway first; falls back to read-only view of `~/.prismer/local.db` cache tables when gateway is absent (returns `error.code='memory_gateway_unavailable'` with a fix hint).
+  - `events` / `events:stats` — read `~/.prismer/para/events.jsonl` with `--limit / --agent-id / --session-id / --family / --type` filters; stats aggregates `byFamily / byType / byAgentId / bySessionId`.
+- **Hermes long-running adapter** — autostart from `~/.hermes/profiles/<name>/config.yaml`, `/v1/runs` SSE consumer, full `tool.started` / `tool.completed` / `reasoning.available` event handling, Kanban + Goal mirror writeback onto `IMTask.metadata.bridge.hermes`. New runtime dep: `yaml@^2.8.2`. Hermes runs in the user's own Python venv; the runtime stays TS-only.
+- **Hosted-agent pipeline** — `agent.host.declare` payload now stamps `daemonId` onto `IMAgentCard.metadata` so the workspace runtime view groups daemon-declared agents under the right device (instead of `__unbound__`). New `POST /v1/agents/install` LocalServer endpoint + `POST /:id/installAgent` sandbox-controller proxy enable cloud→daemon agent install RPC.
+- **Static binding** — `PRISMER_HOSTED_AGENT_FILE` / `PRISMER_HOSTED_AGENT_JSON` / `PRISMER_STATIC_BINDING_REQUIRED` env vars consumed by `Runner.installStaticHostedAgentFromEnv`. K8s deployments seed one `agents` + `agent_profiles` row before the first `host.declare`.
+- **Daemon-local shell route** — `runtimeRoute='shell'` (or `metadata.execution.kind === 'shell'`) routes through `shell-executor.ts`. Output capping (default 256 KiB, hard max 5 MiB), timeout enforcement (default 60s, hard max 30 min), `allowedWorkspaces` allow-list, `bash|zsh|sh` selector, structured error codes (`shell_disabled`, `shell_workspace_not_allowed`, `shell_command_required`, `shell_cwd_missing`, `shell_spawn_failed`, `shell_timeout`, `task_cancelled`, `shell_exit_nonzero`).
+- **Stuck-task reaper** (60s) + **per-`taskId` dedupe** in `Runner.runningTasks` — closes the failure mode where cloud's `redispatchPending` fires the same task five times during a long LLM call and an upstream gateway half-closes a connection. Reaper aborts past `max(timeoutMs, 5min)` and emits `task.dispatch.reply {ok:false, error.code:'daemon_task_timeout'}`.
+- **30s heartbeat re-declare** — re-sends `agent.host.declare` so cloud's 90s `sweepTimedOut()` doesn't flip status back offline.
+- **Bridge + observability writeback** — dispatch PATCH-merges `result.metadata.hermes` onto `IMTask.metadata.bridge.hermes` (with `lastSyncedAt`) and writes `metadata.observability` with `{identity, memory, goals, lastSyncedAt}`.
+- **8 new tests** under `test/` (Vitest):
+  - `asset.test.ts` (240 LOC) — CLI asset CRUD + envelope normalization.
+  - `chat-cli.test.ts` (135 LOC) — chat envelope + `sk-prismer` redaction.
+  - `cookbook.test.ts` (148 LOC) — suite parsing, summary, strict-skip.
+  - `dispatch.test.ts` (265 LOC) — `composePrompt` / `appendGoalContext` / `appendMemoryContext` + full `handleDispatch` path with mocked resolver/cache/ws/service-pool, plus error paths.
+  - `hermes-validate.test.ts` (88 LOC) — `hermesAdapter.validate` accepts/rejects port, apiKey, env-var key regex, provider URL.
+  - `sandbox.test.ts` (189 LOC) — sandbox CRUD + `runCmd` + logs streaming.
+  - `shell-executor.test.ts` (66 LOC) — `resolveShellConfig` defaults + clamping, `isShellDispatch` routing, `executeShellDispatch` enabled/disabled/timeout.
+  - `workspace-cli.test.ts` (89 LOC) — `prismer workspace (list|create|get|runtime|files)` envelope unwrapping.
+- **2 opt-in Playwright e2e specs** under `e2e-playwright/specs/`:
+  - `workspace-hermes-daemon-runtime.spec.ts` — `WAVE7_HERMES_E2E=1 HERMES_API_KEY=...`. Drives full `pair → register Hermes agent → AgentProfile → host.declare → POST /api/im/tasks → Hermes reply` chain via product APIs only.
+  - `workspace-hermes-ui-flow.spec.ts` — `WAVE7_HERMES_UI_E2E=1`. Workspace UI: New Agent dialog → Hermes long-running role → direct session → IM message → reply persisted. Requires a real local daemon on `127.0.0.1:3210`.
+
+### Evolved
+
+- **5 existing CLI verbs reworked**: `adapter` (richer install/uninstall + per-adapter register, new `doctor` + `hooks`), `agent` (host register/list/unregister + 6-check `doctor`), `daemon` (`--foreground` for LaunchAgent + log tail-N + follow), `status` (consolidated banner + composite `/healthz` + `/api/im/me` + `local.db` row counts), `task` (tolerant envelope parsing for both `{task:{...}}` and flat shapes; reads `output` from `task.output` or `task.result.output`).
+- **`Runner` + `dispatch` + `LocalServer`** gain hosted-agent paths (~940 lines added across the three files).
+
+### Breaking
+
+- **`package.json` `module` + `exports.import` now point at `dist/index.js`** (was `dist/index.mjs`, which `tsup` never actually emitted — bug fix that may affect bundlers respecting the old field).
+- **`yaml@^2.8.2` is a new runtime dependency.** Used by the Hermes adapter to read/write `~/.hermes/profiles/<name>/config.yaml`.
+- **`public/install.sh` strict-pins `@prismer/runtime@1.9.3`** (no caret). Stale 1.8.x installs will not auto-upgrade via curl re-run; users must explicitly re-run the installer.
+- **LaunchAgent plist `ProgramArguments` now include `--foreground`.** Existing 1.8.x installs that loaded the plist without it would respawn-loop unless the user re-runs the installer (which does `bootout` + `bootstrap`).
+- **`agent.host.declare` payload now requires `daemonId`** to be honored by cloud — without it the agent renders under `__unbound__` in the workspace runtime view.
+- **`runtimeRoute` extended** with `'shell'` as a valid value of `TaskDispatchRequestPayload.runtimeRoute`. Cloud-side dispatchers that previously hard-coded `'agent'|'sandbox'` need a passthrough for `'shell'`.
+- **`adapter list` JSON output now includes `installed: { package_manager, package_name, binary, version, installed_at } | null`** field. Strict-shape consumers need an update.
+- **New CLI verbs may shadow user aliases**: `setup`, `banner`, `chat`, `cookbook`, `asset`, `sandbox`, `memory`, `events`, `events:stats`, `workspace`. None overlap with the prior 7-verb shape, but wrapper scripts that did `prismer <unknown>` and got a friendly error will now get command-not-found.
+- **claude-code adapter closes child stdin** (`stdio: ['ignore', 'pipe', 'pipe']`). Operators relying on stdin-mode interactive use of `claude` via the daemon (which was never supported) see no behavior change; this only removes the 3s "no stdin" warning that made daemon dispatches appear hung on `claude` ≥ 2.1.128.
+
+### Fixed
+
+- **LaunchAgent KeepAlive respawn loop on macOS** — `install.sh` now passes `--foreground` to `prismer daemon start` in the plist `ProgramArguments`. Without it, `daemon start` spawned a child and exited, `launchd` saw exit-zero, KeepAlive=true respawned immediately. With `--foreground` the binary blocks in the polling loop until `config.toml` appears.
+
+### Internal
+
+- `module` / `exports.import` field correctness (`dist/index.js`).
+- `qrcode@^1.5.4` runtime dep added (used by the QR pair flow).
+- `eslint-plugin-react-hooks` added to dev tooling.
+
+---
+
+## v1.8.x — Pre-publish scaffolding
+
+The runtime tree was scaffolded across the `feat/refactoring` branch. There were no published cuts before v1.9.3; the package landed at v1.9.3 directly when its public API surface stabilized.