@volter/editor-blender 0.1.12 → 0.1.13

package/contributions/blender-icon-trace.mjs

@@ -19,7 +19,7 @@
  * ## Licence
  *
  * Blender's icon sources are GPL-2.0-or-later, like the rest of the Blender
- * tree, and a trace of one is a derivative of it. `@volter/blender` therefore
+ * tree, and a trace of one is a derivative of it. `@volter/editor-blender` therefore
  * carries BOTH licences — its SPDX expression is
  * `AGPL-3.0-only AND GPL-3.0-or-later` (`packages/blender/LICENSE`): our code
  * AGPL-3.0-only, Blender's traced artwork conveyed under GPL-3.0-or-later on

package/contributions/blender-icons.source.mjs

@@ -4,13 +4,13 @@
  * sources and are GPL-2.0-or-later artwork (see "GPL PATHS, DELIBERATELY"
  * below, `blender-icon-trace.mjs`, and the provenance file
  * `blender.icons.traced.json`); the other 149 are drawn HERE in Blender's
- * IDIOM. That mixture is why `@volter/blender` is
+ * IDIOM. That mixture is why `@volter/editor-blender` is
  * `AGPL-3.0-only AND GPL-3.0-or-later` (`packages/blender/LICENSE`).
  * The idiom is what a screenshot conveys: a 16-unit grid, monochrome filled
  * silhouettes, ~1.3-unit strokes rendered as filled capsules with round ends,
  * no outline around a fill, optical size ~12 units inside the 16 box.
  *
- * Run `node packages/blender/contributions/blender-icons.source.mjs` to rewrite
+ * Run `node packages/editor-blender/contributions/blender-icons.source.mjs` to rewrite
  * the JSON. The JSON is the artifact the style bundle imports; THIS is where a
  * glyph is edited, because a path `d` is not a thing a person edits by hand.
  *
@@ -2752,7 +2752,7 @@ g(
     dataVertex(10, 20),
 );
 
-// The Outliner's DATABLOCK row (`@volter/blender`'s datablock hierarchy) —
+// The Outliner's DATABLOCK row (`@volter/editor-blender`'s datablock hierarchy) —
 // the same MESH_DATA mark the Properties rail's Data tab draws, under its own
 // name because the two sites composite differently: `outliner.png`'s data
 // glyph is #07b189 over the row's #272727 and `properties-object.png`'s tab is
@@ -2783,7 +2783,7 @@ g('outliner-data', glyphs['properties-data'].path);
  * justify one shape.
  *
  * GPL PATHS, DELIBERATELY — AND THE PACKAGE'S SPDX SAYS SO. Blender's icon
- * sources are GPL-2.0-or-later, and `@volter/blender` is
+ * sources are GPL-2.0-or-later, and `@volter/editor-blender` is
  * `AGPL-3.0-only AND GPL-3.0-or-later` (`packages/blender/LICENSE`, whose
  * notice block names this set, its provenance file and the §13 combination):
  * our code is AGPL, these 197 paths are Blender's artwork conveyed as GPL-3.0,

package/contributions/blender-node-panels.source.mjs

@@ -63,7 +63,7 @@
  * ## Running it
  *
  * ```
- * node packages/blender/contributions/blender-node-panels.source.mjs \
+ * node packages/editor-blender/contributions/blender-node-panels.source.mjs \
  *   [--checkout <path>] [--check]
  * ```
  * writes (or, with `--check`, verifies) `blender.node-panels.json` beside
@@ -74,7 +74,7 @@
  * ## Licence
  *
  * What lands in the JSON is a table of PANEL NAMES and SOCKET NAMES read out
- * of GPL-2.0-or-later sources. `@volter/blender` is AGPL-3.0-only, which that
+ * of GPL-2.0-or-later sources. `@volter/editor-blender` is AGPL-3.0-only, which that
  * is compatible with (relicense to GPL-3.0, then §13), and the package
  * already carries Blender itself — the same standing this file's sibling
  * `blender-icon-trace.mjs` records for the icon paths. Nothing traced here

package/contributions/blender-palette.source.mjs

@@ -5,7 +5,7 @@
  * ARCHITECTURE-CORE §Blender north star, "The reference is Blender's SOURCE as
  * well as its frames").
  *
- * Run `node packages/blender/contributions/blender-palette.source.mjs` to
+ * Run `node packages/editor-blender/contributions/blender-palette.source.mjs` to
  * rewrite the JSON; `--check` reports what would change and exits non-zero if
  * anything would. It reads
  * `release/datafiles/userdef/userdef_default_theme.c` from a Blender checkout

package/contributions/blender-properties-tab.tsx

@@ -5,7 +5,7 @@
  *
  * WHY A TAB IS A SECTION, and not a rail of our own: under the `properties`
  * presentation the inspector's sections ARE the vertical icon rail, 1:1
- * (`packages/editor/src/components/InspectionProjection.tsx`,
+ * (`packages/editor-sdk/src/kit/components/InspectionProjection.tsx`,
  * `PropertiesColumn`). So the way to make Blender's tab rail appear is to
  * contribute Blender's tabs as sections — which is also exactly the shape I2
  * needs, because each of these modules then grows a CURATED body over the same

package/node/blender-mcp.ts

@@ -6,7 +6,7 @@
  * No modeling happens in this process. `execute_blender_code`,
  * `get_scene_info`, `get_object_info` and `get_viewport_screenshot` become
  * `blender-*` control commands answered by the tab's worker
- * (`packages/blender/contributions/blender.command.ts`, the engine's own
+ * (`packages/editor-blender/contributions/blender.command.ts`, the engine's own
  * `workspace.command` contribution); the screenshot is the tab
  * photographing its own Model document. The 24 integration tools answer as
  * an add-on with no integrations, exactly as the Python server did.

package/package.json

@@ -2,7 +2,7 @@
   "name": "@volter/editor-blender",
   "author": "Volter AI, Inc.",
   "license": "AGPL-3.0-only AND GPL-3.0-or-later",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "publishConfig": {
     "access": "public"
   },
@@ -69,14 +69,14 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "1.30.0",
-    "@volter/blender-engine": "0.1.10",
-    "@volter/editor-threejs": "0.5.69",
+    "@volter/blender-engine": "0.1.11",
+    "@volter/editor-threejs": "0.5.70",
     "zod": "^4.3.6"
   },
   "peerDependencies": {
-    "@volter/editor-sdk": "0.5.69",
-    "@volter/editor-live": "0.5.69",
-    "@volter/editor-project": "0.5.69",
+    "@volter/editor-sdk": "0.5.70",
+    "@volter/editor-live": "0.5.70",
+    "@volter/editor-project": "0.5.70",
     "react": "^19.0.0",
     "three": "^0.180.0",
     "vite": "^6.4.3"