@volter/editor-live 0.5.68 → 0.5.69

package/BUNDLED_NOTICES

@@ -3,9 +3,9 @@ Bundled license notices
 These notices accompany code incorporated into this package. Separate npm dependencies retain their own licenses.
 
 
-@volter/editor-project@0.5.68
+@volter/editor-project@0.5.69
 Declared license: Apache-2.0
-Source: the unmodified npm package @volter/editor-project@0.5.68, from https://github.com/volter-ai/editor.git
+Source: the unmodified npm package @volter/editor-project@0.5.69, from https://github.com/volter-ai/editor.git
 
 --- packages/editor-project/LICENSE ---
 
@@ -213,9 +213,9 @@ Source: the unmodified npm package @volter/editor-project@0.5.68, from https://g
    limitations under the License.
 
 
-@volter/editor-sdk@0.5.68
+@volter/editor-sdk@0.5.69
 Declared license: Apache-2.0
-Source: the unmodified npm package @volter/editor-sdk@0.5.68, from https://github.com/volter-ai/editor.git
+Source: the unmodified npm package @volter/editor-sdk@0.5.69, from https://github.com/volter-ai/editor.git
 
 --- packages/editor-sdk/LICENSE ---
 
@@ -428,7 +428,8 @@ Source: the unmodified npm package @volter/editor-sdk@0.5.68, from https://githu
 Copyright 2026 Volter AI, Inc.
 
 Project tool registry, provider execution and related types were transferred
-from the Apache-2.0 @vgai/sdk package. Original source hashes and revision are
+from the Apache-2.0 SDK package of volter-ai/volter-engine. Original source
+hashes and revision are
 recorded in provenance/editor-server.json.
 
 The project output-root policy is Apache-2.0, transferred from the original

package/dist/editor-document.d.ts

@@ -28,7 +28,7 @@
  * active; `editor.hierarchy()` / `editor.inspect()` keep answering what those
  * panels RESOLVED, where this door answers what they DREW.
  *
- * A field on `LiveEditor` rather than methods on it, so `vgai eval --list`
+ * A field on `LiveEditor` rather than methods on it, so the editor's `eval --list` command
  * shows the verbs as one named surface — the same reason `game.input`
  * and `game.events` are instance fields.
  */
@@ -74,13 +74,13 @@ export declare class LiveEditorDocument {
      * `styles` additionally resolves named properties per match — and resolving
      * is the point, because a theme token is an expression until an element
      * paints it. Ask for the standard property to learn the colour a person
-     * sees; ask for a `--vgai-…` custom property to learn what a rule WOULD
+     * sees; ask for a `--volter-…` custom property to learn what a rule WOULD
      * paint, which is the only way to measure a `:hover` colour (`:hover` is a
      * browser state no synthetic event can enter, so there is deliberately no
      * hover verb on this door).
      *
-     *   await editor.document.query('.vgai-tree-row', {
-     *     styles: ['backgroundColor', '--vgai-widget-regular-hover'],
+     *   await editor.document.query('.volter-tree-row', {
+     *     styles: ['backgroundColor', '--volter-widget-regular-hover'],
      *   });
      */
     query(selector: string, options?: DocumentScopeOption & {

package/dist/editor.d.ts

@@ -35,7 +35,7 @@ export declare class LiveEditor {
      * `blender-execute`, `blender-scene-info`, `blender-object-info`,
      * `blender-screenshot-view`, `blender-read-file`, `blender-write-file`,
      * `blender-list-files`, `blender-stop` and `blender-status`. They were
-     * reachable from `@volter/editor-sdk` and through `vgai blender-mcp` but from
+     * reachable from `@volter/editor-sdk` and through `volter blender-mcp` but from
      * no GENERAL door, so driving a session meant writing an MCP client script
      * per question — the same discovery failure `eval-surface.ts`'s header
      * records, in a lane that had not noticed it yet.
@@ -76,7 +76,7 @@ export declare class LiveEditor {
     captureActiveDocument(size?: CaptureDimensions, view?: EditorView): Promise<ActiveDocumentCapture>;
     /**
      * Photograph the editor PAGE — every panel, tab strip and viewport as the
-     * person sees it. `vgai screenshot editor` is this verb from the shell. The
+     * person sees it. the editor's `screenshot editor` command is this verb from the shell. The
      * one door for judging chrome sighted: a skin, a workspace arrangement or a
      * contributed panel is looked at through this, never guessed at from DOM
      * probes. The page at its own layout, `scale` output pixels per CSS pixel
@@ -85,11 +85,11 @@ export declare class LiveEditor {
      * at, and the result reports its own `size` and `scale`.
      */
     captureEditorChrome(options?: EditorChromeCaptureOptions): Promise<EditorChromeCapture>;
-    /** `'all'` -> `EditorClient.selectAll()` (mirrors `vgai select --all`); otherwise `EditorClient.select(id)` (mirrors `vgai select <entityId>`). */
+    /** `'all'` -> `EditorClient.selectAll()` (mirrors `volter select --all`); otherwise `EditorClient.select(id)` (mirrors `volter select <entityId>`). */
     select(id: string | 'all'): Promise<void>;
-    /** Mirrors `vgai deselect`. */
+    /** Mirrors `volter deselect`. */
     deselect(): Promise<void>;
-    /** No `id` -> focus the current selection (mirrors bare `vgai focus`); `id` given -> focus that entity. */
+    /** No `id` -> focus the current selection (mirrors bare `volter focus`); `id` given -> focus that entity. */
     focus(id?: string): Promise<void>;
     /**
      * Frame the edit viewport camera on one entity. Same framing as
@@ -274,19 +274,19 @@ export declare class LiveEditor {
      * of one table is a second name for one thing, and an agent reading
      * `--list` had to choose between them with nothing to choose on. This door
      * stays because it is strictly wider: it addresses a COMMAND ID, so under
-     * the frame it reaches everything the workbench knows — a `vgai.action.<id>`
+     * the frame it reaches everything the workbench knows — a `volter.action.<id>`
      * editor action, one of VS Code's own — and not only a view. A VIEW is
      * reached by spelling its verb's command id:
      *
-     *     await editor.command('vgai.blender-uv-view.state')
-     *     await editor.command('vgai.blender-uv-view.zoom', { to: 600 })
+     *     await editor.command('volter.blender-uv-view.state')
+     *     await editor.command('volter.blender-uv-view.zoom', { to: 600 })
      *
-     *     await editor.command('vgai.blender-node-view.view-all')
-     *     await editor.command('vgai.blender-node-view.look', { node: 'Principled BSDF' })
+     *     await editor.command('volter.blender-node-view.view-all')
+     *     await editor.command('volter.blender-node-view.look', { node: 'Principled BSDF' })
      *
      * Under the Code-OSS frame this is the workbench's own command service, so
-     * any command id works — ours and VS Code's alike. Standalone `vgai edit`
-     * has no command service and answers the `vgai.<view>.<verb>` shape off the
+     * any command id works — ours and VS Code's alike. Standalone the editor's `edit` command
+     * has no command service and answers the `volter.<view>.<verb>` shape off the
      * SAME verb table the frame's commands call, refusing any other id by name.
      * One table, two doors, exactly like the keymap's.
      *
@@ -406,7 +406,7 @@ export declare class LiveEditor {
     redo(): Promise<HistoryStep>;
     /** Reload the editor's page and resolve once the new document answers. */
     reloadPage(): Promise<void>;
-    /** Mirrors `vgai status` — the full live editor state as JSON. */
+    /** Mirrors the editor's `status` command — the full live editor state as JSON. */
     status(): Promise<EditorState>;
     /** A live viewport PNG (`EditorClient.captureViewport`) — no direct CLI verb exists; this is the closest wire read. */
     screenshot(size?: number): Promise<ViewportCapture>;

package/dist/index.js

@@ -27,7 +27,7 @@ var EditorCommandError = class extends Error {
    * the receipt window closing unanswered, a beating-but-dead tab, and no tab
    * present at all. The last four can fail in milliseconds.
    *
-   * A caller that converges by retrying (`vgai restart`) needs the distinction
+   * A caller that converges by retrying (the editor's `restart` command) needs the distinction
    * because a refusal the editor ANSWERED may go differently next time, while
    * a command the relay abandoned tells you nothing new on a second identical
    * attempt — and when the abandonment was a 120s budget, re-running it three
@@ -205,22 +205,22 @@ var EditorClient = class {
     return data;
   }
   // --- Play control ---
-  /** `opts.seed` (D15/T-D15.6, objection-4 fix) — `vgai play --seed <n>`'s
+  /** `opts.seed` (D15/T-D15.6, objection-4 fix) — the editor's `play --seed <n>` command's
    *  explicit config leg, relayed as `cmd['seed']`; `handleCommand`'s
    *  `'play'` case threads it into `enterPlayMode`'s highest-precedence seed
-   *  argument (beats manifest.determinism.defaultSeed/?vgai-seed=). Omitted,
+   *  argument (beats manifest.determinism.defaultSeed/?volter-seed=). Omitted,
    *  boot seeding falls back to that precedence unchanged.
    *
-   *  `opts.name` (`vgai play --name <text>`) — an OPTIONAL label for this run,
+   *  `opts.name` (the editor's `play --name <text>` command) — an OPTIONAL label for this run,
    *  relayed as `cmd['name']` and slugified server-side into the run's
    *  `logs/play-*.jsonl` filename and its session-journal line. Findability
    *  only: no registry, no uniqueness, no lookup verb — grep and `ls` are the
    *  query engine. Omitted, the filename keeps its exact unnamed shape. */
-  /*  `opts.record` (`vgai play --record <name>`) — NAMES this run's recording
+  /*  `opts.record` (the editor's `play --record <name>` command) — NAMES this run's recording
    *  file. It does not ENABLE recording: every relayed play records, with no
-   *  flag (see `@vgai/game`'s `src/play/play-recording.ts`). Omitted, the clip is named for
+   *  flag (see `@volter/game`'s `src/play/play-recording.ts`). Omitted, the clip is named for
    *  the durable Gameplay Session; named, it becomes an explicit keepsake in
-   *  `.vgai/recordings/<name>.webm`. */
+   *  `.volter/recordings/<name>.webm`. */
   async play(opts) {
     return this.command({
       type: "play",
@@ -321,9 +321,9 @@ var EditorClient = class {
     return { base64: data.base64, mimeType: data.mimeType };
   }
   /**
-   * Unit 4 (live-front-door wave) — capture the RUNNING GAME (`vgai
-   * screenshot`'s wire leg). Sends the SAME `bridge-screenshot` relay op
-   * `@vgai/live`'s `RelayTransport.screenshot` (and therefore
+   * Unit 4 (live-front-door wave) — capture the RUNNING GAME (the editor's
+   * `screenshot`'s wire leg). Sends the SAME `bridge-screenshot` relay op
+   * `@volter/live`'s `RelayTransport.screenshot` (and therefore
    * `game.screenshot()` on the relay path) already sends, so all three
    * surfaces composite the identical full game stack — canvas(es) plus the
    * HUD/react DOM layers — rather than any of them inventing a second,
@@ -341,8 +341,8 @@ var EditorClient = class {
    * refuses it with `BRIDGE_SCREENSHOT_STALE` rather than pass it off as
    * current. Setting this asks the relay to render exactly ONE deterministic
    * tick (`runTicks(1, {render:'last'})`) first — the same escape
-   * `@vgai/live`'s `RelayTransport.screenshot` has always used, which is why
-   * `vgai eval` could recover these frames while `vgai screenshot` could not.
+   * `@volter/live`'s `RelayTransport.screenshot` has always used, which is why
+   * the editor's `eval` command could recover these frames while the editor's `screenshot` command could not.
    * Off by default: a caller who does not ask must never be handed a frame
    * that only exists because the capture drove the game.
    */
@@ -427,8 +427,8 @@ var EditorClient = class {
         ...source,
         ...options
       },
-      // Photographing changes nothing, and this is the relay `vgai screenshot
-      // <module>` / `project.bake.preview` rides — the lane where a momentary
+      // Photographing changes nothing, and this is the relay the editor's `screenshot
+      // <module>` command and `project.bake.preview` ride — the lane where a momentary
       // transport failure cost a cold agent three probe modules.
       { retryTransport: true }
     );
@@ -442,7 +442,7 @@ var EditorClient = class {
     };
   }
   /**
-   * A project-defined labeled shot set (`vgai screenshot <target> --shots <set>`):
+   * A project-defined labeled shot set (the editor's `screenshot <target> --shots <set>` command):
    * the DEFINITION travels with the command (project data — see
    * `AssetPreviewShotSetDefinition`; the CLI resolves it from the registered
    * `project.<set>.previewShots` tool), and the editor's generic
@@ -471,8 +471,8 @@ var EditorClient = class {
     };
   }
   /**
-   * B8.4 — score the asset against a reference GLB (`vgai screenshot
-   * <model.glb> --compare <ref.glb>`): matched orthographic front + side silhouettes
+   * B8.4 — score the asset against a reference GLB (the editor's `screenshot
+   * <model.glb> --compare <ref.glb>` command): matched orthographic front + side silhouettes
    * (equal-height bounding-box framing, both yaw-normalized to face the
    * camera), per-view IoU numbers, and overlay evidence images. The
    * reference GLB's raw bytes travel base64 in the command; the editor
@@ -489,7 +489,7 @@ var EditorClient = class {
     return { width: data.width, height: data.height, views: data.views };
   }
   /**
-   * The STORY lane (`vgai screenshot <file>.stories.tsx`): every CSF export of
+   * The STORY lane (the editor's `screenshot <file>.stories.tsx` command): every CSF export of
    * one project story file rendered in the live session's DOM and captured
    * through the same composite leg {@link captureGame} uses, returned as
    * per-export images plus one variant sheet. `options.story` narrows to a
@@ -621,9 +621,9 @@ var EditorClient = class {
    * Run ONE command by id — the door to everything the command palette lists.
    *
    * Under the Code-OSS frame this is the workbench's own `ICommandService`, so
-   * any command id works: a view's `vgai.<view>.<verb>`, an editor action's
-   * `vgai.action.<id>`, or one of VS Code's own. Standalone `vgai edit` has no
-   * command service and answers the `vgai.<view>.<verb>` shape directly off
+   * any command id works: a view's `volter.<view>.<verb>`, an editor action's
+   * `volter.action.<id>`, or one of VS Code's own. Standalone the editor's `edit` command has no
+   * command service and answers the `volter.<view>.<verb>` shape directly off
    * the views registry, refusing anything else BY NAME.
    *
    * The result is whatever the command answered — a view verb's state, or
@@ -819,7 +819,7 @@ var EditorClient = class {
    * `blender-object-info`, `blender-screenshot-view`, `blender-read-file`,
    * `blender-write-file`, `blender-list-files`, `blender-start`,
    * `blender-status`): Blender runs in the editor tab's worker, and
-   * `vgai blender-mcp` is transport onto these. `blender-status` is the only
+   * `volter blender-mcp` is transport onto these. `blender-status` is the only
    * one that creates nothing — it answers whether this tab already has a
    * session, which is how a caller survives an editor restart.
    */
@@ -893,7 +893,7 @@ var EditorClient = class {
     return data.projects;
   }
   // --- Registered project tools ---
-  /** List tools explicitly registered in `package.json#vgai.tools`.
+  /** List tools explicitly registered in `package.json#volter.tools`.
    * The editor server loads callable metadata in Node; modules never enter the
    * editor browser merely because they were listed. */
   async listProjectTools() {
@@ -1149,13 +1149,13 @@ var LiveEditorDocument = class {
    * `styles` additionally resolves named properties per match — and resolving
    * is the point, because a theme token is an expression until an element
    * paints it. Ask for the standard property to learn the colour a person
-   * sees; ask for a `--vgai-…` custom property to learn what a rule WOULD
+   * sees; ask for a `--volter-…` custom property to learn what a rule WOULD
    * paint, which is the only way to measure a `:hover` colour (`:hover` is a
    * browser state no synthetic event can enter, so there is deliberately no
    * hover verb on this door).
    *
-   *   await editor.document.query('.vgai-tree-row', {
-   *     styles: ['backgroundColor', '--vgai-widget-regular-hover'],
+   *   await editor.document.query('.volter-tree-row', {
+   *     styles: ['backgroundColor', '--volter-widget-regular-hover'],
    *   });
    */
   async query(selector, options) {
@@ -1343,7 +1343,7 @@ var LiveEditor = class {
    * `blender-execute`, `blender-scene-info`, `blender-object-info`,
    * `blender-screenshot-view`, `blender-read-file`, `blender-write-file`,
    * `blender-list-files`, `blender-stop` and `blender-status`. They were
-   * reachable from `@volter/editor-sdk` and through `vgai blender-mcp` but from
+   * reachable from `@volter/editor-sdk` and through `volter blender-mcp` but from
    * no GENERAL door, so driving a session meant writing an MCP client script
    * per question — the same discovery failure `eval-surface.ts`'s header
    * records, in a lane that had not noticed it yet.
@@ -1395,7 +1395,7 @@ var LiveEditor = class {
   }
   /**
    * Photograph the editor PAGE — every panel, tab strip and viewport as the
-   * person sees it. `vgai screenshot editor` is this verb from the shell. The
+   * person sees it. the editor's `screenshot editor` command is this verb from the shell. The
    * one door for judging chrome sighted: a skin, a workspace arrangement or a
    * contributed panel is looked at through this, never guessed at from DOM
    * probes. The page at its own layout, `scale` output pixels per CSS pixel
@@ -1406,7 +1406,7 @@ var LiveEditor = class {
   async captureEditorChrome(options) {
     return this.#client.captureEditorChrome(options);
   }
-  /** `'all'` -> `EditorClient.selectAll()` (mirrors `vgai select --all`); otherwise `EditorClient.select(id)` (mirrors `vgai select <entityId>`). */
+  /** `'all'` -> `EditorClient.selectAll()` (mirrors `volter select --all`); otherwise `EditorClient.select(id)` (mirrors `volter select <entityId>`). */
   async select(id) {
     if (id === "all") {
       await this.#client.selectAll();
@@ -1414,11 +1414,11 @@ var LiveEditor = class {
     }
     await this.#client.select(id);
   }
-  /** Mirrors `vgai deselect`. */
+  /** Mirrors `volter deselect`. */
   async deselect() {
     await this.#client.select(null);
   }
-  /** No `id` -> focus the current selection (mirrors bare `vgai focus`); `id` given -> focus that entity. */
+  /** No `id` -> focus the current selection (mirrors bare `volter focus`); `id` given -> focus that entity. */
   async focus(id) {
     if (id !== void 0) {
       await this.#client.focusEntity(id);
@@ -1641,19 +1641,19 @@ var LiveEditor = class {
    * of one table is a second name for one thing, and an agent reading
    * `--list` had to choose between them with nothing to choose on. This door
    * stays because it is strictly wider: it addresses a COMMAND ID, so under
-   * the frame it reaches everything the workbench knows — a `vgai.action.<id>`
+   * the frame it reaches everything the workbench knows — a `volter.action.<id>`
    * editor action, one of VS Code's own — and not only a view. A VIEW is
    * reached by spelling its verb's command id:
    *
-   *     await editor.command('vgai.blender-uv-view.state')
-   *     await editor.command('vgai.blender-uv-view.zoom', { to: 600 })
+   *     await editor.command('volter.blender-uv-view.state')
+   *     await editor.command('volter.blender-uv-view.zoom', { to: 600 })
    *
-   *     await editor.command('vgai.blender-node-view.view-all')
-   *     await editor.command('vgai.blender-node-view.look', { node: 'Principled BSDF' })
+   *     await editor.command('volter.blender-node-view.view-all')
+   *     await editor.command('volter.blender-node-view.look', { node: 'Principled BSDF' })
    *
    * Under the Code-OSS frame this is the workbench's own command service, so
-   * any command id works — ours and VS Code's alike. Standalone `vgai edit`
-   * has no command service and answers the `vgai.<view>.<verb>` shape off the
+   * any command id works — ours and VS Code's alike. Standalone the editor's `edit` command
+   * has no command service and answers the `volter.<view>.<verb>` shape off the
    * SAME verb table the frame's commands call, refusing any other id by name.
    * One table, two doors, exactly like the keymap's.
    *
@@ -1794,7 +1794,7 @@ var LiveEditor = class {
   async reloadPage() {
     await this.#client.reloadPage();
   }
-  /** Mirrors `vgai status` — the full live editor state as JSON. */
+  /** Mirrors the editor's `status` command — the full live editor state as JSON. */
   async status() {
     return this.#client.getState();
   }
@@ -1811,7 +1811,7 @@ var LiveTools = class {
   constructor(client) {
     this.#client = client;
   }
-  /** Enumerate the exact `package.json#vgai.tools` catalog without executing it. */
+  /** Enumerate the exact `package.json#volter.tools` catalog without executing it. */
   async list() {
     return this.#client.listProjectTools();
   }
@@ -1878,8 +1878,8 @@ import { existsSync } from "node:fs";
 import { join } from "node:path";
 
 // ../editor-project/src/manifest/filename.ts
-var MANIFEST_FILENAME = "vgai.project.json";
-var REMOVED_MANIFEST_FILENAME = "vgai.game.json";
+var MANIFEST_FILENAME = "volter.project.json";
+var REMOVED_MANIFEST_FILENAME = "volter.game.json";
 function removedManifestFilenameMessage(where) {
   return `${where}: found \`${REMOVED_MANIFEST_FILENAME}\` and no \`${MANIFEST_FILENAME}\`. \`${REMOVED_MANIFEST_FILENAME}\` was REMOVED (the legacy-removal doctrine, docs/ARCHITECTURE-CORE.md \xA7Vocabulary) \u2014 nothing reads it any more, and it is deliberately NOT read as a fallback, because a second accepted name is the defect.
 Fix: rename it \u2014 \`git mv ${REMOVED_MANIFEST_FILENAME} ${MANIFEST_FILENAME}\`. The contents are unchanged; only the filename moved.`;
@@ -1901,7 +1901,7 @@ import { existsSync as existsSync2, readFileSync } from "node:fs";
 import { createRequire } from "node:module";
 import { dirname, join as join2 } from "node:path";
 import { pathToFileURL } from "node:url";
-var PRODUCT_DECLARATION_KEY = "vgai.product";
+var PRODUCT_DECLARATION_KEY = "volter.product";
 var PRODUCT_INSTALL_LINES = [
   "  npm install --save-dev @volter/model-editor",
   "  npm install --save-dev @volter/game-editor"
@@ -1916,7 +1916,7 @@ function readProductManifest(packageDir) {
   } catch {
     return null;
   }
-  const declared = manifest.vgai?.product;
+  const declared = manifest.volter?.product;
   if (declared === void 0) return null;
   const entry = declared.entry;
   if (typeof entry !== "string" || !entry.startsWith("./"))
@@ -1961,7 +1961,7 @@ function readProductManifest(packageDir) {
 }
 var SHA256_HEX = /^[0-9a-f]{64}$/;
 function readProductWorkbench(manifestPath, declared) {
-  const example = '  "vgai": { "product": { "workbench": { "release": "<product>-<fork sha 12>-<platform>", "tarballSha256": "<64 hex>" } } }\n`node scripts/workbench/build-release.mjs --publish --out <release dir>` cuts the release and prints exactly that block.';
+  const example = '  "volter": { "product": { "workbench": { "release": "<product>-<fork sha 12>-<platform>", "tarballSha256": "<64 hex>" } } }\n`node scripts/workbench/build-release.mjs --publish --out <release dir>` cuts the release and prints exactly that block.';
   if (typeof declared !== "object" || declared === null || Array.isArray(declared))
     throw new Error(
       `${manifestPath} declares ${PRODUCT_DECLARATION_KEY} but its "workbench" is ${JSON.stringify(declared)}. A product IS the Code-OSS workbench it was compiled into, so it names the published release those bytes are:
@@ -1988,7 +1988,7 @@ ${example}`
     );
   return { release, tarballSha256 };
 }
-function declaredVgaiPackages(projectRoot) {
+function declaredVolterPackages(projectRoot) {
   let manifest;
   try {
     manifest = JSON.parse(
@@ -2024,7 +2024,7 @@ function locatePackage(projectRoot, name) {
 }
 function declaredProducts(projectRoot) {
   const found = [];
-  for (const name of declaredVgaiPackages(projectRoot)) {
+  for (const name of declaredVolterPackages(projectRoot)) {
     const dir = locatePackage(projectRoot, name);
     if (dir === null) continue;
     const product = readProductManifest(dir);
@@ -2064,7 +2064,7 @@ import {
 } from "node:fs";
 import { homedir } from "node:os";
 import { join as join3, resolve } from "node:path";
-var EDITOR_SESSIONS_REGISTRY_FILE = join3(homedir(), ".vgai", "editor-sessions.json");
+var EDITOR_SESSIONS_REGISTRY_FILE = join3(homedir(), ".volter", "editor-sessions.json");
 function isEditorSessionEntry(v) {
   if (typeof v !== "object" || v === null) return false;
   const s = v;
@@ -2190,7 +2190,7 @@ function canonicalPath(path) {
 function readProjectSession(projectRoot) {
   try {
     const value = JSON.parse(
-      readFileSync3(join4(projectRoot, ".vgai", "session.json"), "utf8")
+      readFileSync3(join4(projectRoot, ".volter", "session.json"), "utf8")
     );
     if (typeof value !== "object" || value === null) return null;
     const hint = value;
@@ -2215,7 +2215,7 @@ async function probeServedProject(port) {
 }
 function manifestRefusal(projectRoot, manifestError) {
   return new Error(
-    `@volter/editor-live: the editor session for ${projectRoot} is live, but its vgai.project.json does not load, so there is no editor or game to drive \u2014 the editor page is showing this same error. Fix the manifest and retry; the session recovers on save, no restart needed.
+    `@volter/editor-live: the editor session for ${projectRoot} is live, but its volter.project.json does not load, so there is no editor or game to drive \u2014 the editor page is showing this same error. Fix the manifest and retry; the session recovers on save, no restart needed.
 ${manifestError}`
   );
 }
@@ -2245,7 +2245,7 @@ async function resolveSession(projectDir = process.cwd(), deps = {}) {
   const projectRoot = findRoot(projectDir);
   if (projectRoot === null) {
     throw new Error(
-      `@volter/editor-live: no vgai.project.json found in ${projectDir} or any parent directory \u2014 is this a project?`
+      `@volter/editor-live: no volter.project.json found in ${projectDir} or any parent directory \u2014 is this a project?`
     );
   }
   const localHint = (deps.readProjectSession ?? readProjectSession)(projectRoot);