[wangcan26]

Summary

• preserve one MCP App runtime across repeated project and canvas tool results
• retain ready canvas runtimes when result rows are replaced
• keep the active-app menu attached to its anchor and inside the visual viewport

Real-model demo

The isolated run used the normal DSH Agent Loop and configured GLM-5.3-Flash High model. It shows the real model-backed Three.js App result, the anchored MCP App action menu, persistent App state, fullscreen Play, character movement with running audio, and skeleton diagnostics. No fixture model, mock transport, replay provider, or test-only runtime hook was used.

Provenance

• demonstrated Host PR head: d17cedcd65d40976097c2a903d7168e83e627512
• served Host tarball: @creative-dswork/dsh-uni-editor@0.3.2, SHA-256 7cc7e5008826f71b45c8508de5eb6bf2b0d11d65690577d19a5130980dc8e7e8, packed from a clean detached worktree at that head
• companion MCP head: 49e2e1bdcc6a3d3ee495e46535d7eab98deef0ba
• served MCP tarball: threejs-editor-mcp@0.2.0, SHA-256 712f37f181c0b60d90e766c021ddc40a226283d9c2c51fe54b2ca360f952d288
• DSH Host checkout: 0ced0a9184dd6694502ce63e9874e084ee90c53d, with local provider/workspace configuration changes
• browser: fresh isolated headless Chrome context through the repository Playwright dependency
• result: real open_editor and build_project calls; browserProblems: []

Verification

• pnpm run check
• 28 tests passed; one external-artifact test skipped as expected
• pnpm run pack:dry-run produced the expected 17-file package
• focused continuity, frame-placement, package, and view-binding tests passed
• GitHub CI passes on the demonstrated head
• cumulative code review: no remaining P0-P2 findings
• security review: no demonstrably exploitable issues

Related

• companion Three.js MCP release: feat: release threejs-editor-mcp 0.2.0 threejs-editor-mcp#1
• this package is not being published as part of the 0.2.0 release