pmx-canvas 0.1.34 → 0.1.36

package/CHANGELOG.md

@@ -5,6 +5,69 @@ All notable changes to `pmx-canvas` are documented here. This project follows
 
 ## [Unreleased]
 
+## [0.1.36] - 2026-06-09
+
+### Added
+
+- **Activity ingestion closes the AX loop (report primitive A).** New
+  `POST /api/canvas/ax/activity` + `canvas_ingest_activity` MCP tool let a harness
+  forward the agent's real tool/session events; the board auto-reacts with
+  kind-driven, overridable defaults — `failure`/`error` (or `outcome:"failure"`) →
+  a blocked work item + a review finding + a `logs` evidence item; `tool-result` +
+  `outcome:"success"` → a `tool-result` evidence item; everything else (tool-start,
+  `session-start`/`session-end`, command, note) records a timeline event only. A
+  reaction set to `false` suppresses it; an object overrides its fields. AX is now
+  bidirectional (agent → board *and* work → board), no longer one-directional.
+- **Blocking gates (report primitive D).** Single-item `GET /api/canvas/ax/{approval
+  |elicitation|mode}/<id>` returns the primitive (404 if unknown) and accepts an
+  optional `?waitMs=` long-poll that resolves the moment the human resolves the gate
+  in the browser (or times out, ≤120000ms). New `canvas_await_approval` /
+  `canvas_await_elicitation` / `canvas_await_mode` MCP tools block the same way, so an
+  agent can request a gate and *wait* for the decision instead of polling. Gates that
+  actually gate.
+- **Context delivery lead block (report #54 hardening, harness-neutral).**
+  `GET /api/canvas/ax/context` (and `canvas://ax-context`) now include a compact
+  `delivery: { pendingSteering, pendingActivity }` block, with an optional
+  `?consumer=` filter (loop-safe — a consumer never sees what it originated). A host
+  adapter can inject this small, un-truncated block per turn so steering survives the
+  full-context char clip on a busy board.
+- **AX host-adapter contract.** New `docs/ax-host-adapter-contract.md` documents the
+  harness-neutral interface (pull-context / deliver-steer / ingest-activity /
+  await-gate / mirror-log), what PMX owns vs. what each adapter implements, and the
+  steering lifecycle + gating conditions.
+
+### Fixed
+
+- **`window.PMX_AX.emit` now confirms (report #55).** Emit returns a Promise that
+  resolves with the interaction result once the parent acks it (and fires a
+  `pmx-ax-ack` event / `window.PMX_AX.on('ack', cb)`), so a surface button can
+  self-confirm (`queued ✓`) instead of looking like "nothing happened". Falls back to
+  an `ax-ack-timeout` result after 10s so `await emit()` never hangs.
+- **HTTP node creation requires a `type` (report #50).** `POST /api/canvas/node` with
+  an empty / type-less body now returns `400` (with the valid-type list) instead of
+  silently creating a phantom markdown node. The `?type=` query param still resolves it.
+- **HTTP accepts top-level `html` / `axCapabilities` on html nodes (report #53).** Both
+  `POST /api/canvas/node` and `PATCH /api/canvas/node/<id>` now accept these fields at
+  the top level (previously dropped on update, and `axCapabilities` dropped on add) —
+  transport parity with `canvas_add_html_node` / `canvas_update_node`. `data.*` nesting
+  still works.
+- **`POST`/`PATCH /api/canvas/ax/work` reject an unknown status (report #56).** Sending
+  `status: "in_progress"` (underscore) now returns `400` with the valid enum instead of
+  `ok:true` + a silent no-op. Accepted tokens: `todo`, `in-progress`, `blocked`, `done`,
+  `cancelled`.
+
+## [0.1.35] - 2026-06-08
+
+### Fixed
+
+- **HTTP batch accepts a bare-array body again (report #49).** `POST /api/canvas/batch`
+  with a top-level `[ ... ]` array created nothing and returned `{ ok: true, results: [] }`
+  — the 0.1.33 `readJson` hardening (empty/whitespace/non-object → `{}`) also coerced
+  top-level arrays to `{}`, so the handler's bare-array branch was dead. Batch now reads
+  the body with an array-preserving variant, so both documented shapes work: the canonical
+  `{ "operations": [...] }` and a bare `[...]`. `readJson` is unchanged for every other
+  endpoint (still object-only), so the malformed-body robustness is preserved.
+
 ## [0.1.34] - 2026-06-08
 
 ### Added
@@ -1763,6 +1826,8 @@ otherwise have to discover by trial and error.
 - Regression coverage for snapshot flat-`id` aliases on both MCP and
   HTTP surfaces, plus async / top-level-`await` WebView script bodies.
 
+[0.1.36]: https://github.com/pskoett/pmx-canvas/releases/tag/v0.1.36
+[0.1.35]: https://github.com/pskoett/pmx-canvas/releases/tag/v0.1.35
 [0.1.34]: https://github.com/pskoett/pmx-canvas/releases/tag/v0.1.34
 [0.1.33]: https://github.com/pskoett/pmx-canvas/releases/tag/v0.1.33
 [0.1.32]: https://github.com/pskoett/pmx-canvas/releases/tag/v0.1.32

package/Readme.md

@@ -61,6 +61,10 @@ immediately — an explicit, low-noise control over what the agent sees next.
 On top of pins, a host-agnostic **AX (agent-experience) layer** turns the
 canvas into a shared workspace between you and the agent:
 
+- **Agent-native nodes** — create markdown, status, HTML, json-render, graph,
+  web-artifact, or MCP app nodes that can act as interactive controls for the
+  agent. A node can focus context, create or update work, add evidence, request
+  input or approval, or send steering without leaving the board.
 - **Focus** — promote nodes into the agent's active context without moving the viewport.
 - **Work items & approval gates** — track visible tasks tied to nodes, and gate
   high-impact actions behind a human `pending → approved/rejected` decision.
@@ -76,6 +80,12 @@ canvas into a shared workspace between you and the agent:
   commands (`pmx.plan`, `pmx.review`, …), and read a tool/prompt policy.
 - **Host capability** — adapters report what the host can do, for diagnostics.
 
+Recent additions in this layer: agent-native nodes can now complete the full
+AX loop; agent tool/session activity can flow back into the board as work,
+evidence, and findings; approval, input, and mode gates can wait for a human
+decision instead of polling; and AX-enabled HTML/web-artifact or MCP app
+controls can show an in-surface confirmation after an action is accepted.
+
 Canvas-bound state (focus, work items, approvals, review annotations,
 elicitations, mode requests, policy) rides canvas snapshots and restore; the
 timeline persists for continuity but is retention-bounded and never restored by a
@@ -95,7 +105,7 @@ the DB so SQLite WAL data is checkpointed into the file.
 
 ### 06 / Any agent
 
-Harness-agnostic. Drive the canvas from [MCP](docs/mcp.md) (65 tools,
+Harness-agnostic. Drive the canvas from [MCP](docs/mcp.md) (69 tools,
 14 resources, change notifications), the [CLI](docs/cli.md), the
 [HTTP API](docs/http-api.md), or the [Bun SDK](docs/sdk.md). Works with
 Claude Code, GitHub Copilot CLI, Codex, Cursor, Windsurf, or any agent
@@ -245,9 +255,11 @@ the agent can read `canvas://skills` and pull in companion skills
   the three-tier visual matrix (json-render → html → web-artifact)
 - **[CLI reference](docs/cli.md)** — full command surface, daemon mode,
   watch streams, WebView automation
-- **[MCP reference](docs/mcp.md)** — 65 tools, 14 resources, change
+- **[MCP reference](docs/mcp.md)** — 69 tools, 14 resources, change
   notifications, node-type routing
 - **[HTTP API](docs/http-api.md)** — REST endpoints, SSE, batch operations
+- **[AX host-adapter contract](docs/ax-host-adapter-contract.md)** — how native
+  host adapters connect context, steering, activity, and human gates
 - **[Bun SDK](docs/sdk.md)** — `createCanvas()` for TypeScript on Bun
 - **[Release process](docs/RELEASE.md)** — maintainer-only