Skip to content

A fast 2D and 3D game engine — TypeScript SDK, C++/WebAssembly core, visual editor. Ship one project to web, desktop, WeChat MiniGames, playable ads, and native Android / iOS.

ci: run the editor's own end-to-end checks

yhha2102fbedbcb
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 783ca56d6..36531f21b 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -399,6 +399,29 @@ jobs:
ESTELLA_VERIFY_W=256 ESTELLA_VERIFY_H=256 ESTELLA_VERIFY_STEPS=10 \
'ESTELLA_VERIFY_EXPECT=[{"x":0.5,"y":0.5,"rgb":[0,255,0],"tol":25},{"x":0.64,"y":0.5,"rgb":[0,255,0],"tol":35},{"x":0.85,"y":0.5,"rgb":[0,0,0],"tol":12}]'
+ # The MCP surface itself, both hosts: the headless one (scene tools) and the
+ # real app (project → scene → entity → save → play → hot reload). Both have
+ # existed as scripts somebody ran by hand; nothing ran them.
+ - name: Run MCP end-to-end
+ working-directory: desktop
+ env:
+ ELECTRON_DISABLE_SANDBOX: '1'
+ run: |
+ xvfb-run -a node scripts/editor-mcp-e2e.mjs
+ xvfb-run -a node scripts/editor-mcp-editor-e2e.mjs
+
+ # The EDITOR's authoring surface, driven for real. The engine has had a pixel
+ # gate for years; the editor had none, which is how depth layers shipped
+ # reaching the play realm and neither the viewport nor a build. Each check
+ # opens the app over MCP and asks a question only the running editor can
+ # answer (does the project setting reach the viewport, does a click select
+ # what is drawn on top, does the grid cover a perspective frame).
+ - name: Run editor authoring checks
+ working-directory: desktop
+ env:
+ ELECTRON_DISABLE_SANDBOX: '1'
+ run: xvfb-run -a node scripts/editor-checks/run.mjs
+
# The SAME pixel assertions on the WebGPU backend — Dawn renders through the
# bundled SwiftShader Vulkan (--use-webgpu-adapter=swiftshader), so a GPU-less
# runner verifies the second backend for real: WGSL twins, the reflected
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5bd405cde..99018c2eb 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -42,6 +42,16 @@ published separately; it ships inside the editor.
previewed. Picking and dragging follow onto the plane each entity actually sits
on, so a sprite at z = -400 is grabbable where it is drawn.
+- **The editor's authoring surface is gated.** The engine has had a pixel gate
+ for a long time; every check that opens the real EDITOR was a script somebody
+ ran once, on the machine that wrote it — which is how depth layers shipped
+ reaching the play realm and neither the viewport nor a build. `verify:editor`
+ runs them all (each in its own editor), CI runs it alongside the MCP
+ end-to-end walks, and adding a check is adding one file to
+ `desktop/scripts/editor-checks/`: the JSON-RPC plumbing, the PNG reader for
+ pixel assertions and the temp-project builder are shared
+ (`scripts/lib/editorDriver.mjs`), so a check is only its claim.
+
### Fixed
- **Compressed and uncompressed sprites no longer disagree about where a sprite
@@ -121,6 +131,12 @@ published separately; it ships inside the editor.
`packagedRuntimeInit` what is APPLIED to it, which is also how the web host had
been quietly dropping the depth mask it was already being sent.
+- **Switching the viewport between 2D and 3D keeps the framing.** The two
+ projections zoom with different fields (a box half-height, a camera distance),
+ so flipping the toggle jumped to whatever the other field happened to hold —
+ the scene lurched about 2× on a button that is meant to change how depth looks,
+ not what you are looking at. Found by the new editor gate on its first run.
+
- **The mixer applies when a project opens, not when its panel does.** Bus
volumes, effects and duck rules were applied by the Audio Mixer panel, so a
project's audio previewed at the wrong levels until someone happened to open