@forgeax/engine-sdk 0.5.0-dev.15093.89d287422343 → 0.5.0-dev.15095.c10283ee6c8f

package/README.md

@@ -92,8 +92,9 @@ Bundle the same Web fonts; do not rely on matching system fonts.
 For cross-machine color regression, use --deterministic and ?forgeaxCapture=1. Games pin random
 seed/logical frame/fonts and set readiness only after Canvas/UI stabilize:
 document.documentElement.dataset.forgeaxCaptureReady = 'true'. App also publishes
-forgeaxFrameSubmitted after actual Renderer submission and dispatches
-forgeax:frame-submitted. The CLI waits for Engine submission/non-flat output before the game marker.
+`canvas.forgeaxFrameProgress.submitted` after actual Renderer submission and dispatches
+`forgeax:frame-submitted` as a future-only notification. The CLI reads the canvas snapshot and
+waits for non-flat output before the game marker.
 wait-ms adds settling after these handshakes; it does not identify a deterministic frame.
 
 For continuous captures, keep one Vite/Xvfb/Chrome/Page/World session and use named ready markers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forgeax/engine-sdk",
-  "version": "0.5.0-dev.15093.89d287422343",
+  "version": "0.5.0-dev.15095.c10283ee6c8f",
   "license": "Apache-2.0",
   "description": "On-demand ForgeaX SDK carrier for the forgeax CLI.",
   "homepage": "https://forgeax.github.io/download/engine-ai.md",

package/sdk/AGENTS.md

@@ -134,10 +134,10 @@ pnpm exec forgeax project capture --headless true --backend software --require-u
 
 This uses source-development assets and browser compositor screenshots; retain adapter/error sidecar evidence.
 For cross-machine comparison, add --deterministic and pin game state in forgeaxCapture mode.
-App's actual frame-submitted event projects to
-document.documentElement.dataset.forgeaxFrameSubmitted and the Canvas
-forgeax:frame-submitted event. Capture waits for Engine submission and non-flat Canvas pixels,
-then the game's forgeaxCaptureReady checkpoint. Elapsed waiting is
+App retains submitted and completed facts on `canvas.forgeaxFrameProgress` and dispatches
+the Canvas `forgeax:frame-submitted` event as a future-only notification. Capture reads the
+snapshot and waits for non-flat Canvas pixels, then the game's forgeaxCaptureReady checkpoint.
+Elapsed waiting is
 only extra settling, not a deterministic frame or substitute for pixel evidence.
 Use a Node/Bun SDK command-client scenario for input, assertions, and multiple checkpoints in one session.
 Open browser once, drive native session.page, and call session.capture(name)

package/sdk/README.md

@@ -92,8 +92,9 @@ Bundle the same Web fonts; do not rely on matching system fonts.
 For cross-machine color regression, use --deterministic and ?forgeaxCapture=1. Games pin random
 seed/logical frame/fonts and set readiness only after Canvas/UI stabilize:
 document.documentElement.dataset.forgeaxCaptureReady = 'true'. App also publishes
-forgeaxFrameSubmitted after actual Renderer submission and dispatches
-forgeax:frame-submitted. The CLI waits for Engine submission/non-flat output before the game marker.
+`canvas.forgeaxFrameProgress.submitted` after actual Renderer submission and dispatches
+`forgeax:frame-submitted` as a future-only notification. The CLI reads the canvas snapshot and
+waits for non-flat output before the game marker.
 wait-ms adds settling after these handshakes; it does not identify a deterministic frame.
 
 For continuous captures, keep one Vite/Xvfb/Chrome/Page/World session and use named ready markers

package/sdk/docs/DEVKIT.md

@@ -1,5 +1,12 @@
 # @forgeax/engine-devkit
 
+Interactive Material resource presentations expose App's native material-preview
+Fiber through the existing workspace provider and browser command transport.
+`engine.preview.material.get/set/rotate/reset` preserve authenticated caller and
+exact preview ownership; reads do not enter the ordered mutation queue. Source
+generation only composes the owner, never implements geometry or rotation math.
+Transparent thumbnails retain their canonical sphere and existing cache policy.
+
 ## Pack authoring sessions
 
 `forgeax asset inspect <source.pack.ts> --parameters-only --json` is the quick
@@ -1095,10 +1102,10 @@ session uses the native window and display density. Projects must ship the same
 Web font files on every machine; a system-font fallback is not a colour or layout parity contract.
 
 For local/remote pixel or colour comparison, add `--deterministic`. The command navigates with
-`?forgeaxCapture=1`. The Engine App publishes
-`document.documentElement.dataset.forgeaxFrameSubmitted` (the monotonic frame id) after the Renderer
-crosses its real queue-submit boundary and dispatches `forgeax:frame-submitted` on the canvas. DevKit
-waits for that engine signal and a non-flat canvas crop before consuming the game's
+`?forgeaxCapture=1`. The Engine App retains the submitted and completed frame facts on
+`canvas.forgeaxFrameProgress` after the Renderer crosses its real queue-submit boundary and
+dispatches `forgeax:frame-submitted` on the canvas as a future-only notification. DevKit reads
+the canvas snapshot and waits for a non-flat canvas crop before consuming the game's
 `document.documentElement.dataset.forgeaxCaptureReady` checkpoint; it never guesses startup time. The
 game remains the time authority: in capture mode it must pin its random seed, viewport-independent
 state, local web fonts, and logical time/frame, render that state, then publish the ready marker. A

package/sdk/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forgeax/engine-sdk-root",
-  "version": "0.5.0-dev.15093.89d287422343",
+  "version": "0.5.0-dev.15095.c10283ee6c8f",
   "private": true,
   "packageManager": "pnpm@12.10.1",
   "engines": {