pmx-canvas 0.7.2 → 0.7.3

package/dist/types/client/canvas/ChoiceMenu.d.ts

@@ -0,0 +1,13 @@
+/** Themed single-choice menu shared by the feedback form and steering composer. */
+export declare function ChoiceMenu({ label, value, options, onChange, className, above, }: {
+    label: string;
+    value: string;
+    options: Array<{
+        value: string;
+        label: string;
+        disabled?: boolean;
+    }>;
+    onChange: (value: string) => void;
+    className?: string;
+    above?: boolean;
+}): import("preact/src").JSX.Element;

package/dist/types/client/nodes/McpAppNode.d.ts

@@ -12,10 +12,11 @@ type ViewerFrameSource = {
  * white navigation paint. Two animation frames after load gives the new document
  * a composited paint before the old one is removed.
  */
-export declare function RefreshingViewerFrame({ source, iframeRef, onLoad, title, className, sandbox, allow, tabIndex, }: {
+export declare function RefreshingViewerFrame({ source, iframeRef, onLoad, onDocumentLoad, title, className, sandbox, allow, tabIndex, }: {
     source: ViewerFrameSource;
     iframeRef: RefObject<HTMLIFrameElement>;
     onLoad: () => void;
+    onDocumentLoad?: (frame: HTMLIFrameElement) => void;
     title: string;
     className?: string;
     sandbox?: string;

package/dist/types/client/nodes/viewer-runtime-state.d.ts

@@ -0,0 +1 @@
+export declare function restoreViewerRuntimeState(nodeId: string, token: string, source: Window): void;

package/dist/types/client/state/canvas-store.d.ts

@@ -25,6 +25,8 @@ export declare const pendingExpandedNodeCloseId: import("@preact/signals-core").
 export declare const pendingConnection: import("@preact/signals-core").Signal<{
     from: string;
 } | null>;
+/** Invalidates in-flight interaction replies when board navigation resets the canvas. */
+export declare const canvasInteractionEpoch: import("@preact/signals-core").Signal<number>;
 export declare const draggingEdge: import("@preact/signals-core").Signal<{
     fromId: string;
     fromX: number;

package/dist/types/client/state/intent-bridge.d.ts

@@ -84,7 +84,7 @@ export declare function pushCanvasUpdate(updates: Array<{
 }>, options?: {
     recordHistory?: boolean;
 }): Promise<void>;
-/** Create a canvas edge via the server. */
+/** Render the server-confirmed edge immediately, without waiting for SSE/polling. */
 export declare function createEdgeFromClient(from: string, to: string, type: string, label?: string): Promise<{
     ok: boolean;
     id?: string;

package/dist/types/json-render/renderer/index.d.ts

@@ -5,7 +5,7 @@
  * Runs inside a pmx-canvas iframe and reads the normalized json-render spec
  * from an inline global injected by the server-side viewer route.
  */
-import type { Spec } from '@json-render/core';
+import { type Spec } from '@json-render/core';
 declare global {
     interface Window {
         __PMX_CANVAS_JSON_RENDER_SPEC__?: Spec & {
@@ -17,5 +17,6 @@ declare global {
         __PMX_CANVAS_JSON_RENDER_NODE_ID__?: string;
         __PMX_CANVAS_AX_TOKEN__?: string;
         __PMX_CANVAS_AX_STATE__?: unknown;
+        __PMX_CANVAS_UI_STATE_TOKEN__?: string;
     }
 }

package/dist/types/json-render/server.d.ts

@@ -101,6 +101,8 @@ export declare function buildJsonRenderViewerHtml(options: {
     nodeId?: string;
     axToken?: string;
     axState?: unknown;
+    /** Independent nonce for tab-local runtime state across focus transitions. */
+    stateToken?: string;
     /** Nonce for the content-height reporter so the node can grow to fit the chart. */
     frameToken?: string;
     /** When true, charts render at their natural (intrinsic) height instead of

package/dist/types/shared/ax-surface-protocol.d.ts

@@ -14,6 +14,8 @@ export declare const AX_SURFACE_EMIT_SOURCE = "pmx-canvas-ax";
 export declare const AX_SURFACE_ACK_SOURCE = "pmx-canvas-ax-ack";
 /** Parent→surface pushes (theme updates, live AX state) into html/viewer iframes. */
 export declare const HTML_SURFACE_PUSH_SOURCE = "pmx-canvas-html-node";
+/** Tab-local JSON viewer state handoff, independent of AX capabilities. */
+export declare const JSON_VIEWER_STATE_SOURCE = "pmx-canvas-json-state";
 /** Ext-app boot beacon: the iframe's scripts executed (WebKit watchdog liveness). */
 export declare const EXT_APP_BOOT_BEACON_SOURCE = "pmx-canvas-ext-app-alive";
 /**

package/docs/ax-host-adapter-contract.md

@@ -6,12 +6,23 @@ capabilities, and the tool/prompt policy — over HTTP and MCP. What makes AX
 *interactive* on a given coding harness (GitHub Copilot, Codex, Claude Code, …) is
 a thin **adapter** that wires PMX's neutral surfaces to that harness's lifecycle.
 
-"Agnostic" means a documented interface plus PMX-side behavior plus one small
-reference adapter per harness — not zero-adapter magic. The genuinely harness-owned
+"Agnostic" means a documented interface plus PMX-side behavior that a host-specific
+adapter can use — not a shipped adapter for every harness or zero-adapter magic. The genuinely harness-owned
 acts (waking a turn, per-turn context injection, forwarding native tool hooks,
 native modals) still need a per-harness adapter; PMX owns everything on its side of
 the line (queues, endpoints, schemas, the canvas-surface fallback).
 
+### Amp uses native MCP, not a bundled lifecycle adapter
+
+Amp's portal and agent connection are separate. Configure `amp.mcpServers` in the
+executing workspace's `.amp/settings.json`, align its root/port with the portal service,
+and have the human approve a new workspace command before reloading MCP. See the
+[Amp setup guide](../skills/pmx-canvas/references/installing-pmx-canvas.md#amp-connect-the-agent-separately-from-the-portal).
+An active Amp agent can read pinned context, claim addressed steering, edit, verify the
+visible result and acknowledge. PMX ships no Amp lifecycle adapter that automatically
+injects context, forwards tool hooks, or wakes idle threads. The injection/push behavior
+below requires an adapter implementing it; merely configuring MCP does not provide it.
+
 ## The interface
 
 Every adapter implements as much of this as its host allows; PMX provides the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pmx-canvas",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Spatial canvas workbench for coding agents — infinite 2D canvas with agent-native CLI, MCP integration, nodes, edges, file watching, and snapshots",
   "type": "module",
   "main": "./src/server/index.ts",

package/skills/pmx-canvas/SKILL.md

@@ -43,11 +43,14 @@ for the authoritative stop, viewport, persistence, reset, group-order, and captu
 
 ## Runtime prerequisites
 
-PMX Canvas 0.7.2 requires **Bun >=1.4.2**, including when installed through npm.
+PMX Canvas 0.7.3 requires **Bun >=1.4.2**, including when installed through npm.
 Check `bun --version` and ensure Bun is on the MCP host's PATH, not just your shell's;
 use an absolute executable path if needed. Install/configure only when requested.
 For pinned installation, MCP configuration, managed services, and disposable verification,
 read [Installing PMX Canvas](references/installing-pmx-canvas.md).
+In Amp, follow that reference's [Amp setup](references/installing-pmx-canvas.md#amp-connect-the-agent-separately-from-the-portal):
+portal access is separate from native MCP, workspace commands need human trust approval,
+and a connected MCP server does not install an idle-thread wake-up adapter.
 
 ## Reading bundled skills over MCP
 
@@ -58,7 +61,8 @@ files (for example `skill://pmx-canvas/references/installing-pmx-canvas.md`) thr
 `resources/read`, fetching only what is needed. Hosts without extension support can still read
 ordinary resources or use installed filesystem skills; `canvas://skills` remains available.
 Resource reads do not activate skills or authorize executing their scripts. The host must
-preserve MCP origin and apply integrity/approval checks. Restart MCP after upgrading the package;
+preserve MCP origin and apply integrity/approval checks. Native Canvas tool discovery alone
+does not establish native MCP Skills-extension support. Restart MCP after upgrading the package;
 the served catalog is a startup snapshot. Local mirrors still use `skills sync` below.
 
 ## Required Operating Sequence
@@ -104,7 +108,7 @@ the served catalog is a startup snapshot. Local mirrors still use `skills sync`
    Do not detach a host-owned session; its adapter manages its lifetime. Everything the session
    gives you and asks of you (cursor + phase chip, the session panel, steering, the scope fence's
    403s, the human edit lock's 409s, unattended approvals) is in **Sessions & the human** below.
-7. **Mutate through current composites.** Prefer the 16 composite MCP tools below.
+7. **Mutate through current composites.** Prefer the 18 composite MCP tools below.
 7. **Arrange and validate.** After batch changes, use `canvas_view { action: "arrange" }` when
    appropriate and always finish with `canvas_query { action: "validate" }`.
 7b. **Show the human.** After creating user-facing output, bring the camera to it: a single node
@@ -204,7 +208,7 @@ always authoritative, independent of the installed release version.
 |-----------|---------|
 | `canvas_import` | `list`, `read`, `submit`, `unavailable` |
 | `canvas_node` | `add`, `get`, `update`, `remove` |
-| `canvas_render` | `describe-schema`, `validate`, `add-json-render`, `stream-json-render`, `add-graph` |
+| `canvas_render` | `describe-schema`, `validate`, `add-json-render`, `stream-json-render`, `add-graph`, `workboard` |
 | `canvas_edge` | `add`, `update`, `remove` |
 | `canvas_group` | `create`, `add`, `ungroup` |
 | `canvas_history` | `undo`, `redo` |
@@ -217,7 +221,7 @@ always authoritative, independent of the installed release version.
 | `canvas_ax_gate` | `request`, `resolve`, `await` with `approval`, `elicitation`, or `mode` |
 | `canvas_ax_timeline` | `read`, `record-event`, `add-evidence`, `send-steering`, `reads` |
 | `canvas_ax_delivery` | `claim`, `mark` |
-| `canvas_board` | `list`, `get`, `create`, `create-from`, `update` |
+| `canvas_board` | `list`, `get`, `create`, `create-from`, `open`, `update` |
 | `canvas_snapshot` | `save`, `list`, `restore`, `delete`, `gc`, `diff` |
 | `canvas_intent` | `signal`, `update`, `clear` |
 
@@ -300,7 +304,12 @@ as layout work left to do.
 Creation responses may include `sizeAdjustment` (`defaulted`, `clamped-to-minimum`, or
 `fit-to-children`); use its `applied` geometry rather than assuming the request won. Json-render
 validation/creation may also return warnings for form controls whose value is not bound with
-`$bindState`; the panel can render, but edits are not durable state until the binding is fixed.
+`$bindState`; the panel can render, but edits do not update its runtime state until the binding is fixed.
+Bound JSON input and dynamic lists are local UI state, not saved canvas data. Focus-mode
+expand/close preserves that state for the same spec in the current tab; an authored spec update,
+board switch or page reload resets it. Persist important edits explicitly through the app's
+save/AX actions. Published 0.7.2 loses this state on expand/close too (AK): avoid changing views
+with an unsaved JSON form on that release. This contract does not extend to HTML or external apps.
 If the documented receipts or warnings are unexpectedly absent, do not guess around them with raw
 payload reads: verify that the CLI/MCP host and daemon use the same 0.7 installation and workspace,
 restart the matching daemon after upgrade, and re-check `/health`.
@@ -428,15 +437,18 @@ Use the visible workbench when the human is actively curating layout:
 - Other open tabs appear as green cursors with a name tag (`/workbench?name=mia` sets yours);
   a node you drag is locked for agents until you release it.
 - The chrome is a persistent 52px left tool rail plus a slim 44px top bar (0.4.8+). The rail
-  carries the tools (Select V, Pan Space, Connect C), node creation (markdown M, image I, file
-  Shift+F, webpage W, HTML surface H, group G, annotate A — a popover with draw / text / eraser),
+  carries the tools (Select V, Pan Space, Connect C), Markdown note M, Attach files, webpage W,
+  group G, and separate Draw A, Text note and Eraser buttons for board feedback,
   and utilities: search & commands (Cmd+K — actions with shortcuts, then jump-to-node), arrange,
   trace, minimap, history, the theme picker (nine themes: dark, light, high-contrast, midnight,
   sepia, arctic, ember, forest, volt), and shortcuts (?). The top bar holds the connection dot,
   workspace title, the session chip / gate badge / context meter while a session is attached
   (or the external-writers indicator and *Start agent session* otherwise), and the zoom cluster
   (zoom out, % label = reset, zoom in, fit F). Hovering a rail button shows a tooltip with its
-  shortcut.
+  shortcut or supported file types. Attach files shares the drop workflow: images, Markdown,
+  text/code and PDF/Office originals; PDF/Office extraction still requires the import request
+  and human review. Workspace file paths (Shift+F) and image URLs (I) remain in the canvas
+  menu and shortcuts; HTML surfaces remain available through H and agent tools.
   On viewports ≤1180px the top bar drops its meta text and the session panel becomes a drawer;
   every control stays in the rail at any width — there is no separate mobile menu.
 - Keyboard: nodes are focusable — arrow keys move to the nearest node, Enter opens it in focus
@@ -653,5 +665,5 @@ Load only the reference relevant to the task:
 - [GitHub Copilot adapter](references/github-copilot-app-adapter.md)
 - [Codex app adapter](references/codex-app-adapter.md)
 
-The authoritative current MCP inventory and legacy replacement table is
-[`docs/mcp.md`](../../docs/mcp.md).
+Use fresh MCP `tools/list` for the installed runtime's authoritative inventory and action schemas;
+the [bundled full reference](references/full-reference.md) remains available in mirrored skills.

package/skills/pmx-canvas/evals/evals.json

@@ -703,6 +703,75 @@
           "type": "output_check"
         }
       ]
+    },
+    {
+      "id": 29,
+      "name": "amp-workspace-trust-and-target",
+      "prompt": "The Canvas portal is working in this Amp orb, but tool_search finds no Canvas tools. The workspace MCP server is named review-canvas and amp mcp doctor says awaiting approval. The portal service health says workspace /work/review on port 4361; MCP is configured for /work/other on 4313. Fix the setup; can you just approve it or use global config?",
+      "expected_output": "Aligns the workspace amp.mcpServers entry with /work/review and port 4361, clearing stale PMX_CANVAS_URL, without altering unrelated settings or stopping the other workspace. Explains that workspace execution trust belongs to the human and gives amp mcp approve review-canvas for the orb workspace terminal after review. Does not execute approval or bypass it through global config/--mcp-config. After human approval, reloads MCP, requires connected and native tool discovery, verifies health identity and active board, and only then permits writes. Does not equate portal access or standalone MCP smoke with native integration.",
+      "assertions": [
+        {
+          "name": "preserves-human-trust-boundary",
+          "description": "Requests human review and amp mcp approve review-canvas in the executing workspace; neither self-approves nor changes configuration scope to bypass trust",
+          "type": "output_check"
+        },
+        {
+          "name": "aligns-actual-target",
+          "description": "Uses the observed /work/review workspace and 4361 local port, clears stale URL targeting and preserves unrelated settings/listeners",
+          "type": "output_check"
+        },
+        {
+          "name": "verifies-native-connection-after-approval",
+          "description": "Requires reload, connected status, actual Amp Canvas tools and matching health/board before writes; does not treat portal or standalone smoke as native proof",
+          "type": "output_check"
+        }
+      ]
+    },
+    {
+      "id": 30,
+      "name": "amp-native-steering-evidence-boundary",
+      "prompt": "On this disposable board, native Amp MCP is connected and your source/consumer is amp-review. The browser pinned the Review card and sent amp-review a fresh instruction to append receipt CHECK-30. Prove the round trip, then confirm that an idle Amp thread will now wake automatically and that native Skills discovery works.",
+      "expected_output": "Uses actual Amp Canvas tools to read the pinned card, claims only as amp-review, signals intent and appends the requested receipt without losing existing content. Verifies the rendered receipt before marking that delivery for amp-review and confirms it is no longer pending. Uses a different recipient as a negative control and detaches only self-owned test sessions. Reports active-agent polling as verified but declines to infer idle-thread wake-up, persistent pumping or native MCP Skills discovery from this evidence.",
+      "assertions": [
+        {
+          "name": "checks-pin-and-addressed-delivery",
+          "description": "Reads the browser-pinned card via native Amp tools, claims using amp-review, and verifies a different recipient does not receive the addressed test message",
+          "type": "output_check"
+        },
+        {
+          "name": "verifies-edit-before-ack",
+          "description": "Signals intent, preserves card content, verifies CHECK-30 in the browser before marking delivery, then confirms no pending test message remains",
+          "type": "output_check"
+        },
+        {
+          "name": "does-not-overclaim-host-support",
+          "description": "Distinguishes active-agent polling from idle wake-up/background pumps and tools/resources from native Skills discovery; cleans up only test-owned sessions",
+          "type": "output_check"
+        }
+      ]
+    },
+    {
+      "id": 31,
+      "name": "json-focus-runtime-state-continuity",
+      "prompt": "On a disposable board, verify that an unsaved JSON form and dynamic list survive inline-to-focus and focus-to-inline transitions. Seed draft Initial and one item; use the browser to enter DRAFT-MUST-SURVIVE and load 16 items, expand, then enter EXPANDED-MUST-SURVIVE and replace the list with three distinct items, and close. Does this also prove the draft survives a reload or spec replacement?",
+      "expected_output": "Runs the browser regression with bound input and echo plus runtime list values in both directions, without saving or updating the spec between transitions. Verifies exact values and counts, not only node size or server spec. Exercises src and srcdoc including AX-disabled JSON. Proves the regression fails with the old behavior before trusting green. Separately confirms an authored spec revision resets to the new seed and the server spec was not silently changed by runtime edits. Reports local focus continuity separately from durable AX state, page reload, other hosts, HTML and external apps; a defined eval is not a completed benchmark.",
+      "assertions": [
+        {
+          "name": "verifies-both-directions-in-browser",
+          "description": "Checks exact bound input, echo and asymmetric list contents/counts inline to focus and back without an intervening save or spec edit",
+          "type": "output_check"
+        },
+        {
+          "name": "checks-transport-and-revision-boundaries",
+          "description": "Runs src and srcdoc including AX-disabled JSON, verifies authored spec replacement resets runtime state and ordinary input edits leave server spec unchanged",
+          "type": "output_check"
+        },
+        {
+          "name": "discriminates-and-limits-claims",
+          "description": "Records a failure against old behavior and a passing fixed run; does not infer persistence across reloads, native-host support or scored model quality",
+          "type": "output_check"
+        }
+      ]
     }
   ]
 }

package/skills/pmx-canvas/references/full-reference.md

@@ -430,8 +430,8 @@ single-purpose tools behind an `action` (and, for `canvas_ax_gate`, a `kind`) di
 
 > **Legacy single-purpose tools were removed in v0.3.0.** The old names (`canvas_add_node`,
 > `canvas_update_node`, `canvas_request_approval`, `canvas_add_work_item`, …) are no longer
-> registered — use the composites instead. The authoritative legacy→composite mapping table lives
-> in [`docs/mcp.md`](../../../docs/mcp.md) — this skill does not re-enumerate the removed names.
+> registered — use the composites below and fresh MCP `tools/list` for the installed runtime's
+> authoritative action schemas. This skill does not re-enumerate the removed names.
 
 ### The 18 composites
 
@@ -439,7 +439,7 @@ single-purpose tools behind an `action` (and, for `canvas_ax_gate`, a `kind`) di
 |-----------|-----------------|--------------|
 | `canvas_import` | `list` · `read` · `submit` · `unavailable` | Process human-requested imports: inspect metadata/controlled bytes, submit reviewable Markdown with references/warnings/agent description, or report unavailable. Request/cancel/commit are human-only |
 | `canvas_node` | `add` · `get` · `update` · `remove` | Create / read / mutate / delete a node. **`add` covers html + primitives too**: `{ action:"add", type:"html", html:"…" }` and `{ action:"add", type:"html", primitive:"choice-grid", data:{} }` — no separate add-html tool needed |
-| `canvas_render` | `describe-schema` · `validate` · `add-json-render` · `stream-json-render` · `add-graph` | Schema introspection, spec dry-run validation, and native json-render / graph node creation |
+| `canvas_render` | `describe-schema` · `validate` · `add-json-render` · `stream-json-render` · `add-graph` · `workboard` | Schema introspection, spec dry-run validation, native json-render / graph node creation, and a live AX work-item board |
 | `canvas_edge` | `add` · `update` · `remove` | Connect / edit / disconnect nodes |
 | `canvas_group` | `create` · `add` · `ungroup` | Manage spatial group containers |
 | `canvas_history` | `undo` · `redo` | Time travel through the mutation ring buffer |

package/skills/pmx-canvas/references/installing-pmx-canvas.md

@@ -4,7 +4,7 @@ Use this reference when the `pmx-canvas` skill is installed but the `pmx-canvas`
 
 ## Prerequisites and version
 
-The examples pin **PMX Canvas 0.7.2**, which requires **Bun >=1.4.2** even when
+The examples pin **PMX Canvas 0.7.3**, which requires **Bun >=1.4.2** even when
 installed through npm: the CLI runs through Bun, not Node. Check `bun --version`
 first. If missing or older, follow the [Bun installation instructions](https://bun.sh/docs/installation)
 with the user's authorization. Ensure Bun is on the MCP host's PATH as well as the
@@ -17,11 +17,11 @@ in `SKILL.md`. Do not pair newer checkout guidance with an older runtime unknowi
 ## Install from npm
 
 ```bash
-npm install -g pmx-canvas@0.7.2
+npm install -g pmx-canvas@0.7.3
 pmx-canvas --version
 ```
 
-Without a global install, use `bunx pmx-canvas@0.7.2` in place of `pmx-canvas` in
+Without a global install, use `bunx pmx-canvas@0.7.3` in place of `pmx-canvas` in
 the commands below. Do not use unpinned `bunx pmx-canvas` for a version-specific check.
 
 ## Choose the workspace and target
@@ -91,7 +91,7 @@ discards empty env values, remove `PMX_CANVAS_URL` from its launch environment i
   "mcpServers": {
     "canvas": {
       "command": "bunx",
-      "args": ["pmx-canvas@0.7.2", "--mcp"],
+      "args": ["pmx-canvas@0.7.3", "--mcp"],
       "env": {
         "PMX_CANVAS_WORKSPACE_ROOT": "/absolute/path/to/project",
         "PMX_CANVAS_PORT": "14313",
@@ -123,6 +123,78 @@ If you are using a local checkout instead of the published package, point the co
 Restart the host's MCP process after changing configuration. Inspect startup output for
 fallback ports; do not assume the configured port is the one the MCP server bound.
 
+## Amp: connect the agent separately from the portal
+
+PMX does not ship a dedicated Amp lifecycle adapter. Amp can use the native MCP tools;
+the portal is only the human's browser UI. Configure MCP inside the orb or runner where
+Amp executes, not only on the user's laptop. Merge this into that workspace's
+`.amp/settings.json`, preserving other settings (Amp does not use the generic `.mcp.json`):
+
+```json
+{
+  "amp.mcpServers": {
+    "canvas": {
+      "command": "bunx",
+      "args": ["pmx-canvas@0.7.3", "--mcp"],
+      "includeTools": ["canvas_*"],
+      "env": {
+        "PMX_CANVAS_WORKSPACE_ROOT": "/absolute/path/to/project",
+        "PMX_CANVAS_PORT": "14313",
+        "PMX_CANVAS_URL": "",
+        "PMX_CANVAS_AGENT_SOURCE": "amp"
+      }
+    }
+  }
+}
+```
+
+Replace root and port with the **existing portal service's actual workspace and local
+listening port**. A supervised service may use an assigned `PORT`, not 4313 or 14313;
+inspect its status/logs and `/health`. Do not put the public portal URL in the stdio
+command or copy another test run's absolute paths. Use an absolute executable path if
+the MCP process cannot find Bun. The `canvas_*` filter exposes the Canvas tool family.
+
+### Workspace trust is a human approval
+
+Run `amp mcp doctor` from this workspace to distinguish `awaiting approval` from a
+missing executable or connection failure. A new workspace MCP command requires the
+user to review and approve it. Give the user this command to run in that workspace's
+orb Terminal or runner terminal (replace `canvas` if the configured server name differs):
+
+```bash
+amp mcp approve canvas
+```
+
+The agent must not run this approval itself or move the command to global settings or
+`--mcp-config` to bypass workspace trust. Approval authorizes execution of this MCP
+command; it is not a new Canvas import consent or permission to mutate arbitrary boards.
+After approval, reload MCP connections (`reload_mcp` in Amp) and require `connected`.
+Discover `canvas` tools with `tool_search`; for the full unfiltered 0.7.3 server there
+are 24 tools. If still absent, inspect the server status, command/PATH and target instead
+of reinstalling blindly. See [Amp MCP documentation](https://ampcode.com/docs/customize/mcp).
+
+### Verify native tools, then steering
+
+1. Check `/health` for the expected package version and canonical workspace. Through
+   Amp's discovered tools, read `canvas_board { action: "get" }` and
+   `canvas_query { action: "context" }`; verify the board matches the visible portal.
+   A CLI smoke check or SDK-spawned MCP client does not establish native Amp discovery.
+2. For a requested end-to-end check, use a disposable board. Pin a known card in the
+   portal and require a native context read to return that card as pinned. Use one
+   stable presence/steering identity (`amp` above, or a unique source per independent
+   agent); reuse any adapter-owned session instead of attaching a duplicate.
+3. Send a fresh browser message addressed to that identity. The running agent claims
+   it with `canvas_ax_delivery` using the same `consumer`, reads the relevant card,
+   signals intent, and performs the requested edit through native Canvas tools.
+4. Verify the visible result in the browser before marking the message delivered for
+   that consumer. A subsequent claim should omit it. Detach only test-owned sessions.
+
+This proves an **active agent can poll and act**, not automatic wake-up of an idle Amp
+thread, background polling, or automatic agent launch for imports. An MCP connection
+does not install a steering pump. Only configure a pump/host integration when requested;
+its startup backlog rules are in the main skill. Tool discovery and resource reads also
+do not establish Amp support for native MCP Skills-extension discovery or activation.
+
 ## Verify the actual target before writes
 
 For the local target selected above:

package/skills/pmx-canvas-testing/SKILL.md

@@ -139,6 +139,12 @@ Four ways a test silently stops discriminating in this repo:
 - For `graph`, `json-render`, `mcp-app`, webpage, and image nodes, API geometry is not enough.
   Verify the rendered browser frame when changing sizing: iframe/body `scrollHeight` and
   `scrollWidth` should fit the available frame unless scrolling is the intended behavior.
+- For JSON focus transitions, edit a bound input and load a multi-item runtime list inline,
+  expand and verify both, edit/replace them in focus mode, then close and verify both again.
+  Exercise `src` and `srcdoc`, including AX-disabled JSON. No save, spec edit or reload belongs
+  between those assertions. Separately verify a real spec revision resets to authored state,
+  and that local drafts never entered the server spec. See `tests/e2e/json-render-forms.pw.ts`.
+  Eval definitions are not evidence of executing this browser regression or a model benchmark.
 - When checking embedded frame fit manually, start from a clean seeded state, rebuild stale bundles,
   and inspect the actual iframe document in a browser. Server dimensions can look correct while the
   embedded content is still clipped.
@@ -160,6 +166,49 @@ Four ways a test silently stops discriminating in this repo:
 - If browser tests fail after a client change, confirm the bundle was rebuilt and the server
   started from the updated code
 
+### Keep first-failure evidence before rerunning
+
+Use a separate directory for each attempt, including non-browser probes. Save the exact
+command, target/version, exit status, stdout and stderr; keep credentials out of logs.
+Before rerunning Playwright, copy its failure traces/screenshots and results out of the
+runner's overwritten output directory. Never overwrite an initial failure log with a rerun.
+For a shell gate, capture its status even with `set -e`, for example:
+
+```bash
+attempt_dir=$(mktemp -d /tmp/pmx-check.XXXXXX)
+printf '%s\n' 'bun run test' > "$attempt_dir/command.txt"
+status=0
+bun run test > "$attempt_dir/stdout.log" 2> "$attempt_dir/stderr.log" || status=$?
+printf '%s\n' "$status" > "$attempt_dir/exit-status.txt"
+# Inspect this attempt before rerunning; return the gate's original exit status.
+(exit "$status")
+```
+
+Record what changed between attempts. Distinguish harness corrections, product fixes,
+unchanged retries and host approval. A corrected pass does not make the original attempt
+green. If logs were lost, say so; never reconstruct them or claim first-run success.
+
+## Native-host verification is separate from transport checks
+
+Record source, packed-package, registry-package, portal and native-host results separately.
+An SDK subprocess's MCP handshake/catalog is not evidence that Amp discovered tools.
+For Amp setup/trust and the pin → read → addressed steer → edit → visible result → ack
+procedure, follow the bundled [installation reference](../pmx-canvas/references/installing-pmx-canvas.md#amp-connect-the-agent-separately-from-the-portal).
+MCP-only consumers should read `skill://pmx-canvas/references/installing-pmx-canvas.md`
+directly with `resources/read`, not traverse outside the testing skill's resource tree.
+Workspace trust approval belongs to the human; report a blocked native check until approved.
+Include a different-recipient negative control for addressed delivery on a disposable board.
+Verify the rendered edit before acknowledging; detach only test-owned sessions afterward.
+Do not label active-agent polling as idle-thread wake-up, a persistent pump, or automatic
+import-agent launch. Native MCP tools do not prove native Skills-extension discovery.
+
+List unexercised surfaces explicitly: native Copilot/WebKit, Windows-native behavior,
+physical mobile, OCR and Office extraction need their own evidence. Source adapter tests
+or a source helper pointed at a published server do not establish installed-adapter execution.
+Sampled resource digests are not a full-catalog audit; eval definitions are not scored model
+results; a skipped mirror check is not validation. Do not change the product merely to
+turn an untested surface into a claimed pass.
+
 ## Handoff Standard
 
 Before marking work done, report: