@volter/game-editor 0.5.69 → 0.5.70

package/template/.agents/skills/volter-threejs-authoring/SKILL.md

@@ -3,7 +3,7 @@ name: volter-threejs-authoring
 description: Build, rig, animate, diagnose, and visually refine polished native Three.js scenes and procedural assets with direct Object3D code, reusable construction helpers, geometry libraries, and an inspect-render-critique loop. Use for procedural models, rigid mechanical armatures, environments, static props, stylized materials, lighting, cameras, scene composition, or an agent-focused Blender-like workflow. Use volter-3d-models when the result should be a Blender source document with an exported GLB. Do not use for Blender bpy work or imported skeletal retargeting.
 ---
 
-# VOLTER Three.js Authoring
+# Volter Three.js Authoring
 
 Author ordinary project source against Three.js. Treat the source module and
 live `Object3D` graph as truth. Use helpers for leverage, not as a replacement
@@ -14,7 +14,7 @@ scene language.
 1. Read the project instructions and architecture.
 2. Locate the Three root or modeling build entry, existing helpers,
    renderer setup, and verification commands.
-3. Start or reuse the VOLTER editor immediately and keep it open.
+3. Start or reuse the Volter editor immediately and keep it open.
 4. Capture a fixed-camera visual baseline.
 5. Inspect the live hierarchy, selected-object facts, renderer state, and
    console before changing code.
@@ -67,7 +67,7 @@ Use raw Three.js whenever a helper becomes awkward.
 Keep shader source in ordinary `.vert`, `.frag`, or `.glsl` files and bind it
 with `THREE.ShaderMaterial` directly. A sibling `name.vert.glsl` +
 `name.frag.glsl` pair is the portable convention Asset Lab recognizes; it is
-not a VOLTER format. Keep authored uniform defaults, defines, textures, and
+not a Volter format. Keep authored uniform defaults, defines, textures, and
 material composition beside the owning material in TS/TSX, where the runtime
 actually reads them. Never add a `.shader.json`, uniform sidecar, or generated
 shader graph to duplicate those facts.
@@ -86,7 +86,7 @@ postprocessing, or the game's actual texture bindings.
 ## Compose postprocessing directly
 
 When a game needs postprocessing, add `@react-three/postprocessing` to that
-project and import its components directly. Do not create a VOLTER chain file,
+project and import its components directly. Do not create a Volter chain file,
 effect registry, wrapper component, or JSON descriptor. The owning scene's JSX
 is already the ordered chain; conditionally render one effect to bypass it and
 move its JSX child to reorder it. Keep the finishing order restrained: render,

package/template/.agents/skills/volter-threejs-authoring/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "VOLTER Three.js Authoring"
+  display_name: "Volter Three.js Authoring"
   short_description: "Build polished native Three.js scenes and assets"
   default_prompt: "Use $volter-threejs-authoring to build and visually refine native Three.js source without introducing a parallel scene model."

package/template/.claude/skills/editor/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: editor
-description: Launch, control, inspect, and verify a VOLTER game through its live visual editor. Use for editor sessions, Play mode, selection, hierarchy or inspector work, screenshots, status, logs, restart after setup changes, or the live playtest loop.
+description: Launch, control, inspect, and verify a Volter game through its live visual editor. Use for editor sessions, Play mode, selection, hierarchy or inspector work, screenshots, status, logs, restart after setup changes, or the live playtest loop.
 ---
 
-# Control the VOLTER editor
+# Control the Volter editor
 
 ## Open the observable session
 

package/template/.claude/skills/editor/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "Control the VOLTER Editor"
-  short_description: "Operate and inspect the live VOLTER editor"
-  default_prompt: "Use $editor to open, control, inspect, and verify this game in the VOLTER editor."
+  display_name: "Control the Volter Editor"
+  short_description: "Operate and inspect the live Volter editor"
+  default_prompt: "Use $editor to open, control, inspect, and verify this game in the Volter editor."

package/template/.claude/skills/editor/references/editor-control.md

@@ -39,7 +39,7 @@ npm run --silent volter -- eval --list      # Everything you can drive — ask t
 ```
 
 **Port cross-talk:** the default editor port (5173) is shared across every
-VOLTER project on the machine. `npm run --silent volter -- edit .` never silently retargets a
+Volter project on the machine. `npm run --silent volter -- edit .` never silently retargets a
 DIFFERENT project's already-running editor — if one is already open
 elsewhere, this one starts a second instance on a fresh free port and prints
 that URL instead (use `--switch` to retarget the existing one on purpose).

package/template/.claude/skills/volter-ingest-existing-game/SKILL.md

@@ -30,7 +30,7 @@ orders. Mounting the game is STEP ONE of seven, not the deliverable.
   objects; the navigation slots show the host-computation form (host BFS
   over the game's own public graph, labeled as the host's in so many
   words).
-- The contract shapes: `packages/project/src/adapter/ingest/game-contract.ts`
+- The contract shapes: `packages/editor-project/src/adapter/ingest/game-contract.ts`
   (root · lifecycle · systems.commands/state/hierarchy · systemAdapters) and
   `contract-system-adapters.ts` (the projection that rejects malformed
   claims — a `present` missing required members, or an `empty` without

package/template/.claude/skills/volter-threejs-authoring/SKILL.md

@@ -3,7 +3,7 @@ name: volter-threejs-authoring
 description: Build, rig, animate, diagnose, and visually refine polished native Three.js scenes and procedural assets with direct Object3D code, reusable construction helpers, geometry libraries, and an inspect-render-critique loop. Use for procedural models, rigid mechanical armatures, environments, static props, stylized materials, lighting, cameras, scene composition, or an agent-focused Blender-like workflow. Use volter-3d-models when the result should be a Blender source document with an exported GLB. Do not use for Blender bpy work or imported skeletal retargeting.
 ---
 
-# VOLTER Three.js Authoring
+# Volter Three.js Authoring
 
 Author ordinary project source against Three.js. Treat the source module and
 live `Object3D` graph as truth. Use helpers for leverage, not as a replacement
@@ -14,7 +14,7 @@ scene language.
 1. Read the project instructions and architecture.
 2. Locate the Three root or modeling build entry, existing helpers,
    renderer setup, and verification commands.
-3. Start or reuse the VOLTER editor immediately and keep it open.
+3. Start or reuse the Volter editor immediately and keep it open.
 4. Capture a fixed-camera visual baseline.
 5. Inspect the live hierarchy, selected-object facts, renderer state, and
    console before changing code.
@@ -67,7 +67,7 @@ Use raw Three.js whenever a helper becomes awkward.
 Keep shader source in ordinary `.vert`, `.frag`, or `.glsl` files and bind it
 with `THREE.ShaderMaterial` directly. A sibling `name.vert.glsl` +
 `name.frag.glsl` pair is the portable convention Asset Lab recognizes; it is
-not a VOLTER format. Keep authored uniform defaults, defines, textures, and
+not a Volter format. Keep authored uniform defaults, defines, textures, and
 material composition beside the owning material in TS/TSX, where the runtime
 actually reads them. Never add a `.shader.json`, uniform sidecar, or generated
 shader graph to duplicate those facts.
@@ -86,7 +86,7 @@ postprocessing, or the game's actual texture bindings.
 ## Compose postprocessing directly
 
 When a game needs postprocessing, add `@react-three/postprocessing` to that
-project and import its components directly. Do not create a VOLTER chain file,
+project and import its components directly. Do not create a Volter chain file,
 effect registry, wrapper component, or JSON descriptor. The owning scene's JSX
 is already the ordered chain; conditionally render one effect to bypass it and
 move its JSX child to reorder it. Keep the finishing order restrained: render,

package/template/.claude/skills/volter-threejs-authoring/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "VOLTER Three.js Authoring"
+  display_name: "Volter Three.js Authoring"
   short_description: "Build polished native Three.js scenes and assets"
   default_prompt: "Use $volter-threejs-authoring to build and visually refine native Three.js source without introducing a parallel scene model."

package/template/.github/copilot-instructions.md

@@ -1,4 +1,4 @@
-# VOLTER project instructions
+# Volter project instructions
 
 Read and follow `AGENTS.md` before changing this project. Reusable workflows
 use the open Agent Skills format under `.github/skills/`; those files are

package/template/.github/skills/editor/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: editor
-description: Launch, control, inspect, and verify a VOLTER game through its live visual editor. Use for editor sessions, Play mode, selection, hierarchy or inspector work, screenshots, status, logs, restart after setup changes, or the live playtest loop.
+description: Launch, control, inspect, and verify a Volter game through its live visual editor. Use for editor sessions, Play mode, selection, hierarchy or inspector work, screenshots, status, logs, restart after setup changes, or the live playtest loop.
 ---
 
-# Control the VOLTER editor
+# Control the Volter editor
 
 ## Open the observable session
 

package/template/.github/skills/editor/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "Control the VOLTER Editor"
-  short_description: "Operate and inspect the live VOLTER editor"
-  default_prompt: "Use $editor to open, control, inspect, and verify this game in the VOLTER editor."
+  display_name: "Control the Volter Editor"
+  short_description: "Operate and inspect the live Volter editor"
+  default_prompt: "Use $editor to open, control, inspect, and verify this game in the Volter editor."

package/template/.github/skills/editor/references/editor-control.md

@@ -39,7 +39,7 @@ npm run --silent volter -- eval --list      # Everything you can drive — ask t
 ```
 
 **Port cross-talk:** the default editor port (5173) is shared across every
-VOLTER project on the machine. `npm run --silent volter -- edit .` never silently retargets a
+Volter project on the machine. `npm run --silent volter -- edit .` never silently retargets a
 DIFFERENT project's already-running editor — if one is already open
 elsewhere, this one starts a second instance on a fresh free port and prints
 that URL instead (use `--switch` to retarget the existing one on purpose).

package/template/.github/skills/volter-ingest-existing-game/SKILL.md

@@ -30,7 +30,7 @@ orders. Mounting the game is STEP ONE of seven, not the deliverable.
   objects; the navigation slots show the host-computation form (host BFS
   over the game's own public graph, labeled as the host's in so many
   words).
-- The contract shapes: `packages/project/src/adapter/ingest/game-contract.ts`
+- The contract shapes: `packages/editor-project/src/adapter/ingest/game-contract.ts`
   (root · lifecycle · systems.commands/state/hierarchy · systemAdapters) and
   `contract-system-adapters.ts` (the projection that rejects malformed
   claims — a `present` missing required members, or an `empty` without

package/template/.github/skills/volter-threejs-authoring/SKILL.md

@@ -3,7 +3,7 @@ name: volter-threejs-authoring
 description: Build, rig, animate, diagnose, and visually refine polished native Three.js scenes and procedural assets with direct Object3D code, reusable construction helpers, geometry libraries, and an inspect-render-critique loop. Use for procedural models, rigid mechanical armatures, environments, static props, stylized materials, lighting, cameras, scene composition, or an agent-focused Blender-like workflow. Use volter-3d-models when the result should be a Blender source document with an exported GLB. Do not use for Blender bpy work or imported skeletal retargeting.
 ---
 
-# VOLTER Three.js Authoring
+# Volter Three.js Authoring
 
 Author ordinary project source against Three.js. Treat the source module and
 live `Object3D` graph as truth. Use helpers for leverage, not as a replacement
@@ -14,7 +14,7 @@ scene language.
 1. Read the project instructions and architecture.
 2. Locate the Three root or modeling build entry, existing helpers,
    renderer setup, and verification commands.
-3. Start or reuse the VOLTER editor immediately and keep it open.
+3. Start or reuse the Volter editor immediately and keep it open.
 4. Capture a fixed-camera visual baseline.
 5. Inspect the live hierarchy, selected-object facts, renderer state, and
    console before changing code.
@@ -67,7 +67,7 @@ Use raw Three.js whenever a helper becomes awkward.
 Keep shader source in ordinary `.vert`, `.frag`, or `.glsl` files and bind it
 with `THREE.ShaderMaterial` directly. A sibling `name.vert.glsl` +
 `name.frag.glsl` pair is the portable convention Asset Lab recognizes; it is
-not a VOLTER format. Keep authored uniform defaults, defines, textures, and
+not a Volter format. Keep authored uniform defaults, defines, textures, and
 material composition beside the owning material in TS/TSX, where the runtime
 actually reads them. Never add a `.shader.json`, uniform sidecar, or generated
 shader graph to duplicate those facts.
@@ -86,7 +86,7 @@ postprocessing, or the game's actual texture bindings.
 ## Compose postprocessing directly
 
 When a game needs postprocessing, add `@react-three/postprocessing` to that
-project and import its components directly. Do not create a VOLTER chain file,
+project and import its components directly. Do not create a Volter chain file,
 effect registry, wrapper component, or JSON descriptor. The owning scene's JSX
 is already the ordered chain; conditionally render one effect to bypass it and
 move its JSX child to reorder it. Keep the finishing order restrained: render,

package/template/.github/skills/volter-threejs-authoring/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "VOLTER Three.js Authoring"
+  display_name: "Volter Three.js Authoring"
   short_description: "Build polished native Three.js scenes and assets"
   default_prompt: "Use $volter-threejs-authoring to build and visually refine native Three.js source without introducing a parallel scene model."

package/template/AGENTS.md

@@ -1,6 +1,6 @@
-# AGENTS.md — VOLTER Game Project
+# AGENTS.md — Volter Game Project
 
-A standalone game built with VOLTER — work here, not in the engine repo.
+A standalone game built with Volter — work here, not in the engine repo.
 The editor is the authoring and verification surface.
 
 ## Route the request first
@@ -134,7 +134,7 @@ request needs.
 Games are fundamentally unpredictable; pre-written assertions enter an
 endless rewrite cycle. Playtest live; the play log is the receipt.
 
-1. Run `check-idioms`, `typecheck`, `validate`, and `validate-manifest`.
+1. Run `check-idioms`, `typecheck`, and `validate-manifest`.
    **`npm run typecheck` is the gate, never bare `tsc`** (bare `tsc`
    skips `src/tools`).
 2. The ONLY approved slice test is LIVE: a REPL-style manual session in
@@ -170,7 +170,6 @@ npm run --silent volter -- restart       # remount after init-time edits
 npm run --silent volter -- screenshot    # visible evidence
 npm run --silent volter -- eval '<js>'   # THE door onto the running game
 npm run check-idioms          # every slice
-npm run validate              # manifest/files + React design states
 npm run typecheck             # THE gate: src + src/tools + server
 npm run dev:standalone        # EXPORTED builds only
 ```

package/template/README.md

@@ -1,6 +1,6 @@
-# VOLTER game project
+# Volter game project
 
-This is a standalone game project created by VOLTER. Describe the game you want
+This is a standalone game project created by Volter. Describe the game you want
 to a coding agent, or open the shared visual editor directly:
 
 ```bash
@@ -17,7 +17,6 @@ exported builds only.
 npm run dev               # open/reuse this project's editor
 npm run check-idioms      # project architecture and completion diagnostics
 npm run typecheck         # game, editor contributions, Node config, and server
-npm run validate          # project files and React design states
 npm run validate-manifest # volter.project.json
 npm run build             # production game bundle
 ```

package/template/check-idioms.ts

@@ -104,12 +104,11 @@ import { fileURLToPath } from 'node:url';
 //
 // E9 is the one rule that does NOT answer its question from the file tree
 // alone: the R3F00x codes come from the editor's own source analyzer
-// (`ui-source/r3f-project-contracts.ts`), the same pass validate-on-save and
+// (`@volter/editor-react`'s `src/source/r3f-project-contracts.ts`), the same pass validate-on-save and
 // `volter-game-editor status` report from. It is loaded OFFLINE — the analyzer is a pure
 // `(code, file) => diagnostics` function over `typescript`, with no dev
-// server, browser or editor session anywhere in it — through this project's
-// own `@editor/*` tsconfig mapping, so check-idioms never requires a running
-// editor. See `loadR3fAnalyzer`.
+// server, browser or editor session anywhere in it — from the installed
+// package, so check-idioms never requires a running editor. See `loadR3fAnalyzer`.
 //
 // Suppression: put `// idioms-ignore <rule-id> <reason>` on the flagged
 // line. The reason is REQUIRED — an empty/missing reason does not suppress
@@ -710,11 +709,6 @@ function checkTriggerNameIdentity(): void {
 // ---------------------------------------------------------------------------
 // git-history plumbing shared by slice-proxy rules (W9)
 // ---------------------------------------------------------------------------
-// The volter CLI mirrors this exact measurement (source path, gameplay
-// pathspecs, threshold, silent-on-unaskable) as `volter-game-editor status`'s ambient
-// bot-drift line — engine repo, packages/volter-cli/src/instrumentation-signal.ts.
-// If you change any of the three constants below, change them there too, or
-// the ambient signal and this rule will disagree about whether a bot drifted.
 
 /** The files that ARE the game, for slice-proxy measurements (W9). Deliberately
  *  NOT all of src/ — churn in src/ui/, src/tools/ or src/data/ is not by
@@ -833,7 +827,7 @@ function checkUseFramePriority(): void {
 
 /** The one way a project shows that Play has actually run: `logs/play-*.jsonl`
  *  — the editor server opens one per Play session
- *  (packages/editor/server/editor-server.ts, POST /__editor/log-session).
+ *  (packages/editor-core/server/editor-server.ts, POST /__editor/log-session).
  *  A working-tree fact, not a git fact (`logs/` is gitignored), written by
  *  the tool itself, so it cannot be produced by intending to play. This
  *  receipt is also the playtest's proof (owner ruling 2026-08-21). */
@@ -848,7 +842,7 @@ function hasPlayEvidence(): boolean {
 }
 
 /** The scaffolder's own record of where this project came from
- *  (packages/create-volter-project/src/baseline.ts). W9's history ANCHOR.
+ *  (packages/game-editor/node/scaffold/baseline.ts). W9's history ANCHOR.
  *
  *  W7 anchors its window on a file's last commit; W9 does the same, and this
  *  is the file that means "this project began here". Anchoring matters: an
@@ -1007,8 +1001,8 @@ type R3fAnalyzer = (
 ) => R3fDiagnostic[];
 
 /**
- * The editor's OWN R3F source analyzer, resolved from this project's
- * `@editor/*` tsconfig mapping and loaded synchronously.
+ * The editor's OWN R3F source analyzer, resolved from the installed
+ * `@volter/editor-react` package and loaded synchronously.
  *
  * Why not re-implement the codes here: they are a real TypeScript AST pass
  * over the project's import graph (relative imports, re-exports, shared prop
@@ -1018,49 +1012,28 @@ type R3fAnalyzer = (
  * pure (`(code, file) => diagnostics`, `typescript` + `node:fs` and nothing
  * else), so nothing about reusing it needs a server or a session.
  *
- * The mapping is read from the project's own `tsconfig.json` instead of
- * hardcoding a path because it is exactly what the scaffolder rewrites per
- * dependency mode: an in-checkout project points at the engine checkout's
- * `packages/editor/src`, an installed one at
- * `node_modules/@volter/editor-core/src` (the published package ships `src/`).
- * Reading the alias means one code path serves both without knowing which.
- * A node_modules target uses Node's package resolution as a fallback so the
- * same mapping also works when a workspace manager hoists the package.
+ * The published packages ship `src/`, so a module is found as
+ * `node_modules/<package>/<file>` in the project or any directory above it
+ * (a workspace manager may hoist the package).
  *
  * Returns null when the analyzer genuinely cannot be reached. E9 reports that
  * as a finding of its own rather than passing silently — a floor rule that
  * disappears when its instrument is missing reads as a clean bill of health,
  * which is the one thing an analyzer must never produce.
  */
-function resolveEditorModule(relative: string): string | null {
-  const tsconfig = join(rootDir, 'tsconfig.json');
-  if (!existsSync(tsconfig)) return null;
-  let mapped: string;
-  try {
-    const raw = readFileSync(tsconfig, 'utf-8');
-    // Deliberately a text match, not JSON.parse: tsconfigs legitimately carry
-    // comments, and this needs one string out of a known key.
-    const alias = raw.match(/"@editor\/\*"\s*:\s*\[\s*"([^"]+)"/);
-    if (!alias) return null;
-    const baseUrl = raw.match(/"baseUrl"\s*:\s*"([^"]+)"/)?.[1] ?? '.';
-    const aliasTarget = alias[1]!.replace('*', relative);
-    mapped = resolve(rootDir, baseUrl, aliasTarget);
-    if (!existsSync(mapped)) {
-      const nodeModulesMarker = 'node_modules/';
-      const normalizedTarget = aliasTarget.replaceAll('\\', '/');
-      const markerIndex = normalizedTarget.lastIndexOf(nodeModulesMarker);
-      if (markerIndex < 0) return null;
-      const packageTarget = normalizedTarget.slice(markerIndex + nodeModulesMarker.length);
-      mapped = createRequire(join(rootDir, 'package.json')).resolve(packageTarget);
-    }
-  } catch {
-    return null;
+function resolvePackageModule(packageName: string, relative: string): string | null {
+  let dir = rootDir;
+  for (;;) {
+    const candidate = join(dir, 'node_modules', packageName, relative);
+    if (existsSync(candidate)) return candidate;
+    const parent = dirname(dir);
+    if (parent === dir) return null;
+    dir = parent;
   }
-  return existsSync(mapped) ? mapped : null;
 }
 
 function loadR3fAnalyzer(): R3fAnalyzer | null {
-  const mapped = resolveEditorModule('ui-source/r3f-project-contracts.ts');
+  const mapped = resolvePackageModule('@volter/editor-react', 'src/source/r3f-project-contracts.ts');
   if (!mapped) return null;
   try {
     const loaded = createRequire(import.meta.url)(mapped) as {
@@ -1096,7 +1069,10 @@ interface RegionSurfaces {
 }
 
 function loadRegionSurfaces(): RegionSurfaces | null {
-  const mapped = resolveEditorModule('asset-workflow/project-content.ts');
+  const mapped = resolvePackageModule(
+    '@volter/editor-sdk',
+    'src/kit/asset-workflow/project-source-index.ts',
+  );
   if (!mapped) return null;
   try {
     const loaded = createRequire(import.meta.url)(mapped) as {
@@ -1151,8 +1127,8 @@ function checkAuthoringWarnings(): void {
       'E9',
       'warn',
       'authoring-warnings-zero',
-      'the R3F authoring analyzer could not be loaded, so authoring warnings were NOT checked — this run says nothing about them. It resolves through this project\'s tsconfig.json "@editor/*" path mapping.',
-      'Restore the "@editor/*" mapping in tsconfig.json (it points at the engine checkout, or at node_modules/@volter/editor-core/src) and re-run. `npm run volter -- status` reports the same counts from the live editor meanwhile.',
+      'the R3F authoring analyzer could not be loaded, so authoring warnings were NOT checked — this run says nothing about them. It resolves from the installed `@volter/editor-react` package.',
+      'Install the project\'s dependencies (`npm install`): the analyzer is `@volter/editor-react`\'s source and the region resolver `@volter/editor-sdk`\'s. `npm run volter -- status` reports the same counts from the live editor meanwhile.',
     );
     return;
   }
@@ -1165,7 +1141,7 @@ function checkAuthoringWarnings(): void {
       'warn',
       'authoring-warnings-zero',
       "the region resolver could not be loaded, so no file could be attributed to this project's `three` region and authoring warnings were NOT checked — this run says nothing about them.",
-      'Restore the "@editor/*" mapping in tsconfig.json (it points at the engine checkout, or at node_modules/@volter/editor-core/src) and re-run. `npm run volter -- status` reports the same counts from the live editor meanwhile.',
+      'Install the project\'s dependencies (`npm install`): the analyzer is `@volter/editor-react`\'s source and the region resolver `@volter/editor-sdk`\'s. `npm run volter -- status` reports the same counts from the live editor meanwhile.',
     );
     return;
   }

package/template/package.json

@@ -24,9 +24,9 @@
     "@colyseus/sdk": "^0.17.34",
     "@react-three/drei": "^10.7.7",
     "@react-three/fiber": "^9.6.1",
-    "@volter/editor-project": "^0.5.69",
-    "@volter/game-runtime": "^0.5.69",
-    "@volter/threejs-runtime": "^0.5.69",
+    "@volter/editor-project": "^0.5.70",
+    "@volter/game-runtime": "^0.5.70",
+    "@volter/threejs-runtime": "^0.5.70",
     "react": "~19.2.4",
     "react-dom": "~19.2.4",
     "three": "^0.180.0",
@@ -40,13 +40,13 @@
     "@types/react-dom": "^19.2.3",
     "@types/three": "^0.180.0",
     "@vitejs/plugin-react": "^5.1.4",
-    "@volter/editor-core": "^0.5.69",
-    "@volter/editor-game": "^0.5.69",
-    "@volter/editor-live": "^0.5.69",
-    "@volter/editor-sdk": "^0.5.69",
-    "@volter/editor-threejs": "^0.5.69",
-    "@volter/game-editor": "^0.5.69",
-    "@volter/game-live": "^0.5.69",
+    "@volter/editor-core": "^0.5.70",
+    "@volter/editor-game": "^0.5.70",
+    "@volter/editor-live": "^0.5.70",
+    "@volter/editor-sdk": "^0.5.70",
+    "@volter/editor-threejs": "^0.5.70",
+    "@volter/game-editor": "^0.5.70",
+    "@volter/game-live": "^0.5.70",
     "colyseus": "^0.17.8",
     "storybook": "10.6.0",
     "tsx": "^4.23.0",

package/template/server/colyseus-setup.ts

@@ -5,18 +5,10 @@
  * via SSE.
  *
  * There is no auto-started Colyseus process — this is imported by the
- * standalone `npm run server` entry (server/main.ts) and by two
- * harnesses: the e2e showcase's `startColyseusServer`
- * (packages/editor/e2e/helpers/colyseus.ts, which esbuild-bundles this +
- * rooms.ts to run against a real scaffolded project) and the unit-test
- * in-process loopback server (packages/editor/test/helpers/colyseus-loopback.ts,
- * which imports this directly for headless multiplayer tests).
+ * standalone `npm run server` entry (server/main.ts).
  */
 
 import type { Server as HttpServer } from 'node:http';
-// A LEAF module by design — the browser P2P host must reach the same check
-// without dragging this file's server transport into its bundle. See
-// `declared-room.ts`'s header for the build failure that proved it.
 
 export interface ColyseusOptions {
   /** Room definitions: array of { name, handler }. */

package/template/server/main.ts

@@ -6,11 +6,6 @@
  * through `play + server`, before the game's client half (`src/net/`) joins `game_room`. Both
  * arrive with the `server` addition; a project without it keeps these rooms and has neither.
  *
- * This is the standalone counterpart to the two existing harnesses that already start
- * `startColyseus` (colyseus-setup.ts): the e2e showcase's
- * `startColyseusServer` (packages/editor/e2e/helpers/colyseus.ts) and the
- * unit-test in-process loopback (packages/editor/test/helpers/colyseus-loopback.ts).
- *
  * Run via `npm run server`, which invokes tsx against `server/tsconfig.json`
  * (not the app `tsconfig.json` at the project root) — `@colyseus/schema`'s
  * `@type(...)` decorators are legacy (TC39 stage-2) decorators, which need

package/template/server/rooms/arena-room.ts

@@ -149,8 +149,8 @@ export class ArenaRoom extends Room {
     const npcCount = Math.max(0, Math.min(MAX_NPCS, options?.botCount ?? 2));
     this.spawnNPCs(npcCount);
 
-    // Off by default (FROZEN DECISION: env-var OR room-option) — the loopback harness/
-    // the loopback harness (`../loopback.ts`) opt in via the room option; a
+    // Off by default (FROZEN DECISION: env-var OR room-option) — a caller that
+    // creates the room with `allowDebugCommands: true` opts in; a
     // plain `npm run server` boot never accepts debug commands unless
     // VOLTER_ALLOW_DEBUG_COMMANDS is set in its environment.
     const debugCommandsAllowed =

package/template/server/rooms/game-room.ts

@@ -152,8 +152,8 @@ export class GameRoom extends Room {
   private orbRespawnTicks: number[] = [];
 
   onCreate(options?: { allowDebugCommands?: boolean }) {
-    // Off by default (FROZEN DECISION: env-var OR room-option) — the loopback harness/
-    // the loopback harness (`../loopback.ts`) opt in via the room option; a
+    // Off by default (FROZEN DECISION: env-var OR room-option) — a caller that
+    // creates the room with `allowDebugCommands: true` opts in; a
     // plain `npm run server` boot never accepts debug commands unless
     // VOLTER_ALLOW_DEBUG_COMMANDS is set in its environment.
     const debugCommandsAllowed =

package/template/server/rooms.ts

@@ -1,9 +1,7 @@
 /**
  * Room registry — defines all available Colyseus rooms, passed to
  * `startColyseus({ rooms, ... })` (colyseus-setup.ts) to call server.define()
- * for each. Imported by the e2e showcase harness
- * (packages/editor/e2e/helpers/colyseus.ts) and the unit-test in-process
- * loopback server (packages/editor/test/helpers/colyseus-loopback.ts).
+ * for each.
  */
 
 import { ArenaRoom } from './rooms/arena-room.js';

package/template/src/net/NetworkedPlayers.tsx

@@ -10,7 +10,7 @@
  */
 
 import type { Room } from '@colyseus/sdk';
-import { useFrame } from '@react-three/fiber';
+import { type ThreeElements, useFrame } from '@react-three/fiber';
 import { useEffect, useRef, useState } from 'react';
 import { actionPressed } from '../input';
 import { joinGameRoom } from './game-room';
@@ -42,7 +42,7 @@ interface StateShape {
   orbs: { forEach(fn: (orb: OrbView, id: string) => void): void };
 }
 
-export function NetworkedPlayers({ name = 'Networked Players' }: { readonly name?: string }) {
+export function NetworkedPlayers({ name = 'Networked Players', ...props }: ThreeElements['group']) {
   const [room, setRoom] = useState<Room | null>(null);
   const [running, setRunning] = useState(false);
   const [players, setPlayers] = useState<readonly PlayerView[]>([]);
@@ -115,7 +115,7 @@ export function NetworkedPlayers({ name = 'Networked Players' }: { readonly name
   });
 
   return (
-    <group name={name}>
+    <group {...props} name={name}>
       {players.map((player) => (
         <mesh key={player.id} name={player.name || player.id} position={[player.x, 0.45, player.z]} castShadow>
           <sphereGeometry args={[0.45, 24, 16]} />

package/template/vite.config.ts

@@ -12,7 +12,7 @@ const packageSource = (name: string) =>
 
 /**
  * Run-4 dry-run friction #2 — auto-detect drvfs the SAME way the editor dev
- * server does (`packages/editor/server/server-utils.ts`'s
+ * server does (`packages/editor-core/server/server-utils.ts`'s
  * `resolveWatcherPollOptions`, and `dev.ts`'s own `projectOnDrvfs` check):
  * on WSL, a project living on a Windows drive (`/mnt/<drive>/…`) never fires
  * inotify, so without polling this standalone server (`npm run dev:standalone`)

package/template-dotfiles/gitignore

@@ -61,7 +61,7 @@ dist-server/
 # the very dirty-file count the commit-cadence tripwire reports.
 .volter/tripwire-gate.json
 
-# `volter-game-editor play`'s run logs (logs/play-*.jsonl — see packages/volter-cli/src/index.ts)
+# `volter-game-editor play`'s run logs (logs/play-*.jsonl)
 logs/
 *.jsonl
 

package/dist/assets/InspectorObjectPreview-CY5xVsPR.js

@@ -1 +0,0 @@
-import{a as t}from"./jsx-runtime-DPjLkJKQ.js";import{Object3DSnapshotDocument as m}from"./EntityModelDocument-B_4ENTCq.js";import"./_commonjsHelpers-D6-XlEtG.js";import"./editor-shell-store-DHVWS8cE.js";import"./output-pass-HurwNl0G.js";import"./three.module-BLhyNg0e.js";import"./three.core-3arARmh6.js";import"./Pass-D1MRT672.js";import"./editor-layers-D-CTUqco.js";import"./workspace-arrangement-DqG5sUns.js";import"./index-C5ZAyrKq.js";import"./index-nmcBqr7Y.js";import"./index-D_NuPfjr.js";import"./index-CtzuWnCS.js";import"./index-CinJrH5C.js";import"./index-FUuS4qwW.js";import"./client-DNXj_opT.js";import"./user-data-C84W0V47.js";import"./entity-object-MKYemTFM.js";import"./three-contract-Dkt6PmWY.js";import"./live-mixers-B-bwLZ7c.js";import"./asset-preview-DxlSdRZn.js";import"./renderer-ownership-BovSEcLv.js";import"./hierarchy-marks-BuCO8Ke-.js";import"./studio-environment-R9qXUUcC.js";import"./KTX2Loader-CaqVE6nY.js";import"./GLTFLoader-KeoruJgS.js";import"./BufferGeometryUtils-B22h7jo4.js";import"./environment-Dg-YaLsA.js";import"./RoomEnvironment-BkknvS_I.js";import"./EXRLoader-CITMBvGd.js";import"./HDRLoader-BTGuGhVo.js";import"./bitmap-label-Ct4k6ehY.js";import"./StageHost-DYfGYwvq.js";import"./three-state-BCACvUtm.js";import"./standard-viewport-dressing-BW-dM_1h.js";import"./content-bounds-DROIchTa.js";import"./preview-renderer-BrYNFV1p.js";import"./live-gesture-lock-DJbrjOqf.js";import"./model-inspection-DvspbmJl.js";import"./three-viewport-presentation-CBzvc2v2.js";import"./clip-planes-CnAI6DZn.js";import"./three-DiL6vMXq.js";import"./component-instance-root-DLI40MiB.js";import"./viewport-editor-controls-BYaAZ_Ku.js";import"./model-thumbnail-BmQs-h6t.js";import"./OrbitControls-B13MKuwC.js";import"./LineSegments2-DN9pUfWA.js";import"./three.quarks.esm-C_HmSKXo.js";import"./three-integration-DXOFI88n.js";import"./host-hierarchy-objects-BV3WqU2w.js";import"./layered-pick-CAVQMPI7.js";import"./root-stacking-BEd9ZvxC.js";import"./object3d-document-session-registry-CMRJdFp6.js";import"./viewport-door-BARIpMu-.js";import"./scene-framing-DkZKDwH3.js";import"./source-object3d-authoring-adapter-CvmFpSUj.js";import"./three-projection-core-B7Lf8tOp.js";import"./editor-presentation-activity-CqJH4G9t.js";import"./transport-strip-xCg94CuI.js";import"./viewport-surface-status-TUfhXKR9.js";function ut({previewKey:o,object:r,displayName:i,fill:p=!1}){return t.jsx("div",{"data-testid":"inspector-object-preview",style:p?{position:"absolute",inset:0,overflow:"hidden"}:{width:"100%",height:220,minHeight:220,borderBottom:"1px solid var(--volter-structural-divider)",overflow:"hidden",position:"relative"},children:t.jsx(m,{documentId:`inspector-preview:${o}`,source:r,displayName:i,active:!0,chromeless:!0})})}export{ut as InspectorObjectPreview};

package/dist/assets/Object3DDocumentViewport-D6QoHfa_.js

@@ -1,2 +0,0 @@
-const __vite__mapDeps=(i,m=__vite__mapDeps,d=(m.f||(m.f=["assets/StageHost-DYfGYwvq.js","assets/index-C5ZAyrKq.js","assets/index-nmcBqr7Y.js","assets/_commonjsHelpers-D6-XlEtG.js","assets/index-D_NuPfjr.js","assets/jsx-runtime-DPjLkJKQ.js","assets/index-CtzuWnCS.js","assets/index-CinJrH5C.js","assets/index-FUuS4qwW.js","assets/client-DNXj_opT.js","assets/index-CPiRKiDC.css","assets/three-state-BCACvUtm.js","assets/editor-shell-store-DHVWS8cE.js","assets/output-pass-HurwNl0G.js","assets/three.module-BLhyNg0e.js","assets/three.core-3arARmh6.js","assets/Pass-D1MRT672.js","assets/editor-layers-D-CTUqco.js","assets/workspace-arrangement-DqG5sUns.js","assets/user-data-C84W0V47.js","assets/entity-object-MKYemTFM.js","assets/three-contract-Dkt6PmWY.js","assets/standard-viewport-dressing-BW-dM_1h.js","assets/content-bounds-DROIchTa.js","assets/hierarchy-marks-BuCO8Ke-.js","assets/environment-Dg-YaLsA.js","assets/RoomEnvironment-BkknvS_I.js","assets/EXRLoader-CITMBvGd.js","assets/HDRLoader-BTGuGhVo.js","assets/preview-renderer-BrYNFV1p.js","assets/renderer-ownership-BovSEcLv.js","assets/live-mixers-B-bwLZ7c.js","assets/live-gesture-lock-DJbrjOqf.js","assets/model-inspection-DvspbmJl.js","assets/three-viewport-presentation-CBzvc2v2.js","assets/clip-planes-CnAI6DZn.js","assets/three-DiL6vMXq.js","assets/component-instance-root-DLI40MiB.js","assets/viewport-editor-controls-BYaAZ_Ku.js","assets/model-thumbnail-BmQs-h6t.js","assets/studio-environment-R9qXUUcC.js","assets/KTX2Loader-CaqVE6nY.js","assets/GLTFLoader-KeoruJgS.js","assets/BufferGeometryUtils-B22h7jo4.js","assets/OrbitControls-B13MKuwC.js","assets/LineSegments2-DN9pUfWA.js","assets/three.quarks.esm-C_HmSKXo.js","assets/three-integration-DXOFI88n.js","assets/host-hierarchy-objects-BV3WqU2w.js","assets/layered-pick-CAVQMPI7.js","assets/root-stacking-BEd9ZvxC.js","assets/object3d-document-session-registry-CMRJdFp6.js","assets/viewport-door-BARIpMu-.js","assets/asset-preview-DxlSdRZn.js","assets/bitmap-label-Ct4k6ehY.js","assets/scene-framing-DkZKDwH3.js","assets/source-object3d-authoring-adapter-CvmFpSUj.js","assets/three-projection-core-B7Lf8tOp.js","assets/editor-presentation-activity-CqJH4G9t.js","assets/transport-strip-xCg94CuI.js","assets/viewport-surface-status-TUfhXKR9.js"])))=>i.map(i=>d[i]);
-import{ae as r,_ as a}from"./index-C5ZAyrKq.js";import{a as o}from"./jsx-runtime-DPjLkJKQ.js";import{r as n}from"./index-nmcBqr7Y.js";import{V as c,O as u}from"./viewport-surface-status-TUfhXKR9.js";const s=n.lazy(async()=>({default:(await a(()=>import("./StageHost-DYfGYwvq.js").then(e=>e.S),__vite__mapDeps([0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60]))).Object3DDocumentViewport}));function l(t){return i(t.documentId,t.chromeless),o.jsx(n.Suspense,{fallback:o.jsx(c,{testId:"object3d-document-loading",children:u}),children:o.jsx(s,{...t})})}function i(t,e=!1){n.useEffect(()=>{if(!e)return r(t)},[t,e])}export{l as O};