@volter/editor-blender 0.1.150 → 0.1.151

package/contributions/blender.keymap.ts

@@ -1,11 +1,14 @@
 /**
  * The BLENDER keymap (`@volter/sdk/looks`, a `workspace.keymap`
- * contribution). Only the chords that differ from the editor's own are
- * declared; the host fills the rest from its default table.
- *
- * Every chord below is Blender's own, cited to its entry in
- * `scripts/presets/keyconfig/keymap_data/blender_default.py` at the engine's
- * pin (v5.2.0) — the file that IS the "Blender" keyconfig.
+ * contribution). Its chords are this package's `contributes.keybindings`,
+ * gated on `volter.keymap == 'blender'`: only where they differ from the
+ * editor's own, each Blender's in `scripts/presets/keyconfig/keymap_data/
+ * blender_default.py` at the engine's pin (v5.2.0), the file that IS the
+ * "Blender" keyconfig. A Volter chord Blender leaves free is bound there to
+ * `volter.unboundKey`, so it does nothing here as it does in Blender. W arms
+ * `transform.select`, the tool that draws no transform gizmo: Blender's Select
+ * Box, which the 3D View keymap puts on W (`blender_default.py:1950-1955`,
+ * `op_tool_cycle("builtin.select_box", …)`).
  */
 import type { KeymapContribution } from '@volter/sdk/looks';
 
@@ -15,51 +18,6 @@ export const keymap: KeymapContribution = {
   title: 'Blender',
   description:
     'Blender bindings: W select, G/R/S gizmo modes, X delete, Shift+D duplicate, A select all, Alt+A deselect, . frames.',
-  bindings: {
-    // `km_view3d`, `:1950-1955` — `op_tool_cycle("builtin.select_box", {"type": 'W'})`,
-    // bound whenever select is on the left mouse button, which is the default.
-    'transform.select': [{ key: 'w' }],
-    'transform.translate': [{ key: 'g' }],
-    'transform.rotate': [{ key: 'r' }],
-    'transform.scale': [{ key: 's' }],
-    // `km_object_mode`, `:4552` — `object.delete` with `use_global: False`.
-    // Blender's X raises a confirmation popup and ours does not; the deletion
-    // itself is `bpy.ops.object.delete()` either way.
-    'edit.delete': [{ key: 'x' }],
-    // `km_object_mode`, `:4563` — `object.duplicate_move` on Shift+D. Blender
-    // then runs a modal move on the copy; ours leaves it on the original's
-    // pose for the gizmo to move, which is what the Outliner and the `.blend`
-    // both read back.
-    'edit.duplicate': [{ key: 'd', shift: true }],
-    'edit.selectAll': [{ key: 'a' }, { key: 'a', mod: true }],
-    'edit.deselectAll': [{ key: 'a', alt: true }],
-    'viewport.frameSelection': [{ key: '.' }, { key: '', code: 'NumpadDecimal' }],
-    'viewport.cyclePivot': [{ key: ',' }],
-    // Blender's G is Grab (`transform.translate` above); a 2D view's modes keep their buttons.
-    'canvas.panMode': [],
-    'canvas.rulerMode': [],
-    'canvas.toggleGrid': [],
-    // `km_view3d` — `view3d.view_persportho` on NUMPAD_5; Blender has no isometric preset key.
-    'view.perspective': [],
-    'view.projection': [{ key: '', code: 'Numpad5' }],
-    // `km_view3d` — `view3d.view_axis` with Ctrl for the opposite side, `view3d.view_orbit` on
-    // NUMPAD_2/4/6/8 (15°, `pad_rot_angle`) and NUMPAD_9 (π), `view3d.view_roll` on Shift+4/6.
-    // Blender's Ctrl is the Control key on every platform, macOS included (`ctrl`, not `mod`).
-    'view.back': [{ key: '', code: 'Numpad1', ctrl: true }],
-    'view.left': [{ key: '', code: 'Numpad3', ctrl: true }],
-    'view.bottom': [{ key: '', code: 'Numpad7', ctrl: true }],
-    'view.orbitLeft': [{ key: '', code: 'Numpad4' }],
-    'view.orbitRight': [{ key: '', code: 'Numpad6' }],
-    'view.orbitUp': [{ key: '', code: 'Numpad8' }],
-    'view.orbitDown': [{ key: '', code: 'Numpad2' }],
-    'view.opposite': [{ key: '', code: 'Numpad9' }],
-    'view.rollLeft': [{ key: '', code: 'Numpad4', shift: true }],
-    'view.rollRight': [{ key: '', code: 'Numpad6', shift: true }],
-    // `view3d.view_all` on HOME; `view3d.zoom` on NUMPAD_PLUS/NUMPAD_MINUS and Ctrl+=/Ctrl+-.
-    'view.all': [{ key: '', code: 'Home' }],
-    'view.zoomIn': [{ key: '', code: 'NumpadAdd' }, { key: '', code: 'Equal', ctrl: true }],
-    'view.zoomOut': [{ key: '', code: 'NumpadSubtract' }, { key: '', code: 'Minus', ctrl: true }],
-  },
   // `km_view3d` — `view3d.rotate` on MIDDLEMOUSE and `view3d.move` on Shift+MIDDLEMOUSE; the
   // right button is the context menu's, and Shift+Right places the 3D cursor. The factory
   // rotation is Turntable at 0.4° a pixel (`view_rotate_method`,

package/contributions/blender.node-panels.json

@@ -1462,7 +1462,6 @@
   },
   "GeometryNodeForeachGeometryElementOutput": {
     "customSocketOrder": true,
-    "conditional": true,
     "items": [
       {
         "kind": "output",
@@ -1546,7 +1545,6 @@
   },
   "GeometryNodeGridToPoints": {
     "customSocketOrder": true,
-    "conditional": true,
     "items": [
       {
         "kind": "layout"
@@ -1860,7 +1858,6 @@
   },
   "GeometryNodeTransferAttributes": {
     "customSocketOrder": true,
-    "conditional": true,
     "items": [
       {
         "kind": "input",
@@ -1967,7 +1964,6 @@
   },
   "NodeEvaluateClosure": {
     "customSocketOrder": true,
-    "conditional": true,
     "items": [
       {
         "kind": "input",
@@ -2019,8 +2015,7 @@
       },
       {
         "kind": "input",
-        "name": "Weight",
-        "conditional": true
+        "name": "Weight"
       },
       {
         "kind": "panel",
@@ -2087,8 +2082,7 @@
       },
       {
         "kind": "input",
-        "name": "Weight",
-        "conditional": true
+        "name": "Weight"
       },
       {
         "kind": "panel",
@@ -2144,8 +2138,7 @@
       },
       {
         "kind": "input",
-        "name": "Weight",
-        "conditional": true
+        "name": "Weight"
       },
       {
         "kind": "panel",
@@ -2309,7 +2302,6 @@
   },
   "ShaderNodeRaycast": {
     "customSocketOrder": true,
-    "conditional": true,
     "items": [
       {
         "kind": "layout"
@@ -2375,8 +2367,7 @@
       },
       {
         "kind": "input",
-        "name": "Weight",
-        "conditional": true
+        "name": "Weight"
       },
       {
         "kind": "panel",

package/contributions/blender.page.ts

@@ -0,0 +1,63 @@
+/**
+ * EDITOR-BLENDER'S PAGE HALF (`contributes.volter.page`, `docs/adr/plugin-apis.md`): what its
+ * `activate` returns is its API, which a package reads with
+ * `context.extensions.getExtension('volter.@volter/editor-blender')`. It is the model Play seam
+ * this package owns, the parts of the Blender document's bottom area that play's Game panel
+ * draws with, and two generic doors onto the document's Blender: its saves, each running a script on the
+ * scene it wrote whose files reach the project (and a save asked for where it changed), and an asset library in its preferences. Nothing more. Its type is `@volter/editor-blender/api`'s `BlenderPageApi`. It also
+ * registers the package's commands: its session verbs and its views' verbs.
+ */
+import { registerVerbCommands, registerViewCommands } from '@volter/sdk/commands';
+import { registerHierarchyKinds } from '@volter/sdk/hierarchy-kind-icon';
+import type { PluginContext } from '@volter/sdk/plugins';
+import { flushModelDocument, NODE_VIEW_VERBS, setBlenderAssetLibrary, setModelDocumentSaveScript, subscribeModelDocumentSaved } from '../host/blender-runtime-host';
+import { registerModelPlay } from '../src/model-play-extension';
+import {
+  documentOnScreen,
+  modelDocumentSource,
+  modelPlayMode,
+  playModeOf,
+  playModeVersion,
+  servedModelDocument,
+  subscribePlayMode,
+} from '../src/play-mode';
+import { PlayAreaButton, PlayModeSwitch, switchPlayMode } from './blender-play-area';
+import { HEADER_HEIGHT, TIMELINE_CHROME, TIMELINE_THEME } from './blender-timeline-geometry';
+import { TIMELINE_VIEW_VERBS } from './blender-timeline.document';
+import { UV_VIEW_VERBS } from './blender-uv-editor.document';
+import { blenderVerbs } from './blender.verbs';
+import { exportVerbs } from './blender-export.verbs';
+import { gltfExportVerbs } from './blender-gltf-export.verbs';
+
+export function activate(context: PluginContext) {
+  // The Model documents send Blender's kinds: `blender-*`, each its own Outliner glyph, among them the DATA marks for
+  // an object's data, its materials and its shape keys (`tree_element_get_icon_from_id`, `outliner_draw.cc:2479-2610`)
+  // and the value-keyed lamp and probe marks and `OUTLINER_DATA_*` family (`:2508-2521`, `:2578-2589`). Only a Model
+  // document sends them, and its editor is this package's, so they are registered before any of its modules mount.
+  registerHierarchyKinds({
+    namespace: 'blender-',
+    datablocks: ['blender-material-data', 'blender-shapekey-data', 'blender-texture-data', 'blender-image-data'],
+    datablockPrefixes: ['blender-outliner-data-', 'blender-light-', 'blender-lightprobe-'],
+  });
+  // The session verbs and the views' verbs, as the Code-OSS commands package.json declares.
+  registerVerbCommands(context, { ...blenderVerbs, ...exportVerbs, ...gltfExportVerbs });
+  registerViewCommands(context, 'blender-node-view', NODE_VIEW_VERBS);
+  registerViewCommands(context, 'timeline', TIMELINE_VIEW_VERBS);
+  registerViewCommands(context, 'blender-uv-view', UV_VIEW_VERBS);
+  return {
+    registerModelPlay,
+    /** The bottom area's mode, the served model document, its on-screen wait and its source. */
+    playMode: { documentOnScreen, modelDocumentSource, modelPlayMode, playModeOf, playModeVersion, servedModelDocument, subscribePlayMode },
+    PlayAreaButton,
+    PlayModeSwitch,
+    switchPlayMode,
+    /** The Timeline's chrome, which a panel in the same area draws with. */
+    timelineGeometry: { HEADER_HEIGHT, TIMELINE_CHROME, TIMELINE_THEME },
+    /** The model document's `.blend` as a file: a script every save runs in its own turn on the scene it wrote, each
+     *  save that landed it in the project, with what that script did and the carry of its files, and a save of the
+     *  project's `.blend` where Blender holds it changed (`flush`). */
+    modelDocument: { setSaveScript: setModelDocumentSaveScript, subscribeSaved: subscribeModelDocumentSaved, flush: flushModelDocument },
+    /** An asset library every Blender session has, until its removal. */
+    setAssetLibrary: setBlenderAssetLibrary,
+  };
+}

package/contributions/blender.status.tsx

@@ -1,140 +1,29 @@
-/**
- * Blender's MOUSE HINTS, at the left of the status bar (`workspace.status`).
- *
- * Blender's bottom row opens with three tiny mouse glyphs, each with one
- * button lit and the action it performs beside it — `Select`, `Rotate View`,
- * `Options` in the reference (`modeling.png`). It is the one piece of chrome
- * that tells a newcomer what the three buttons DO without a menu.
- *
- * THEY ARE HOVER-DRIVEN THERE, AND ALWAYS-ON HERE. Measured across the whole
- * reference set: `modeling.png` is the ONE frame with any ink left of centre
- * in the status band; `layout`, `modeling-edit-none`, `modeling-edit-all`,
- * `modeling-object-selected`, `sculpting` and `texture-paint` all have ZERO
- * ink before device x 3325 — Blender publishes the keymap for whatever the
- * cursor is over, so a still with the pointer outside the 3D View shows
- * nothing. A still therefore cannot say whether Blender's band is empty by
- * design; it can only say what the hints look like WHEN they are drawn, which
- * is what the geometry below is measured from. Ours are unconditional
- * because the editor has no hover-scoped keymap publisher and inventing one
- * to match a screenshot would be a mechanism with no other reader.
- *
- * THE ACTION NAMES ARE OURS, NOT BLENDER'S. What each button does is a fact
- * about THIS editor, so the labels are read from this editor's own contract,
- * never transcribed from the reference:
- *
- *   - the KEYMAP (`keymap-presets.ts`, `@volter/sdk/looks`) binds no
- *     mouse buttons and structurally cannot: a `KeyChord` is
- *     `{ key, code?, mod?, shift?, alt? }` (`sdk/src/looks.ts:76-82`)
- *     with no button field, so no keymap — the Blender one included — can
- *     move a mouse binding. Nothing to read there.
- *   - so the source is the VIEWPORT's own mouse contract:
- *     `editor-viewport.ts:682-686` sets `orbitControls.mouseButtons` to
- *     `{ LEFT: -1, MIDDLE: PAN, RIGHT: ROTATE }`, and the left button is left
- *     free for the selection raycast (`editor-viewport.ts:3782`,
- *     `if (e.button === 0 && !e.altKey)`).
- *
- * That contract is a constant of the host, not of any document, so the table
- * below is a constant too — with the citations above as its provenance. When
- * a surface ever makes a button mean something else, it publishes that and
- * this reads it; it does not get hardcoded here.
- *
- * The inline styles spell the theme tokens directly (`var(--volter-space-5)`,
- * `var(--volter-font-md)`) instead of importing the host's `spaceVar` /
- * `fontSizeVar` handles: `@volter/editor-blender` is pinned at ZERO host imports
- * (`validate-editor-closure.mjs`). See `blender-version.status.tsx`.
- */
+/** Blender-style status hints describe this editor’s viewport mouse bindings: left selects, middle pans, right rotates. They are always visible because there is no hover-scoped keymap publisher. Use SDK theme variables without importing host implementation. */
 
 export const point = 'workspace.status';
 export const title = 'Mouse hints';
 export const align = 'left';
-/** Front of the contributed band — see the note at the bottom of this file
- *  for why that is not the front of the bar. */
+/** First among contributed left status items, after the host's built-in items. */
 export const order = 0;
 
 /** Which button the glyph lights. */
 type MouseButton = 'left' | 'middle' | 'right';
 
-/**
- * The viewport's three buttons, in Blender's order. Sourced from
- * `editor-viewport.ts:682-686` + `:3782` (see the header) — the editor's
- * contract, which is why the middle/right labels are Pan/Orbit and not
- * Blender's own Rotate View/Options.
- */
+/** Viewport bindings in Blender's button order: left selects, middle pans and right orbits. */
 const HINTS: readonly { readonly button: MouseButton; readonly label: string }[] = [
   { button: 'left', label: 'Select' },
   { button: 'middle', label: 'Pan View' },
   { button: 'right', label: 'Orbit View' },
 ];
 
-/**
- * One mouse glyph in Blender's idiom, TRANSCRIBED FROM THE FRAME rather than
- * estimated: `modeling.png` at native 2x (the only reference frame whose
- * status bar carries the hints — see the note under {@link HINTS}), glyph 1 at
- * device x 12..35, y 2065..2096. Halved, that is a 12 x 16 CSS ink box, and
- * the viewBox IS that box so the SVG needs no scale factor to reason about:
- * one unit is one CSS pixel at the size below.
- *
- * MEASURED BY COVERAGE, NOT BY A THRESHOLD. Every number below is the 50%
- * contour of `(value - 23) / (135 - 23)` — an ink threshold reads a glyph's
- * antialiasing as geometry and got two of these badly wrong on the first cut.
- * Device reading -> CSS (the ink box's left edge is device -0.5, so
- * `css = (device + 0.5) / 2`):
- *
- *   shell stroke       1.98 device, flat on every side row -> {@link STROKE} 1
- *   button row height  16 of 32 device -> {@link BUTTON_H} 8, exactly half
- *   lit button width   left fill ends 9.5 / right fill starts 13.5 device
- *                      -> {@link BUTTON_W} 5, a button at each end
- *   divider            the shell's top edge stops at 11.98 device in the
- *                      left-lit glyph and starts there in the right-lit one
- *                      -> {@link DIVIDER_X} 6.25, ONE boundary, not a gap
- *                      centred on the middle
- *   gap under button   2 device of nothing (fill ends row 15, stroke resumes
- *                      row 18) -> {@link UNDER_GAP} 1
- *   wheel              8 x 14 device at x 8, y 4, ends rounded at r 2.5
- *                      -> 4 x 7 at 4, 2, rx 1.25
- *
- * THE LIT BUTTON IS NOT AN INSET NUB AND NOT A CLIPPED OVERLAY: in the frame
- * the fill REPLACES the shell over its own quadrant (a mid row reads ten solid
- * device px from the very left edge) and the shell stroke is absent for two
- * device rows beneath it and across the divider on the top edge. So the fill
- * is the outer silhouette intersected with the button rect, and the stroke is
- * MASKED OUT over the button's side of the divider down to the hairline —
- * which is why there is a mask here and not the clip the earlier cut used.
- *
- * (Superseded readings, kept so the next round does not re-derive them: a
- * 13x17 box with a 1.7 stroke and a 0.45 hairline, sized to the text's own
- * font size. Both came from a DPR-1 capture against a downscaled reference,
- * which is the instrument WORK.md records as unable to settle stroke weights;
- * at native 2x the glyph measures 16 CSS tall against 9 CSS of cap height,
- * not the ~1:1 that reading reported.)
- *
- * RESIDUE, measured and not fitted away: Blender's TOP edge integrates 3.0
- * device px of coverage where its sides integrate 1.98. One uniform stroke
- * cannot draw both, and a second stroke for the top would be a constant with
- * no reason behind it; the sides are the ones that set the glyph's weight.
- */
+/** The mouse glyph’s viewBox uses CSS pixels. Its lit quadrant replaces the shell fill; mask that quadrant’s shell stroke and preserve the divider and gap beneath it. */
 const STROKE = 1;
 const BUTTON_H = 8;
 const BUTTON_W = 5;
 const UNDER_GAP = 1;
-/**
- * Where the shell's top edge stops for a lit LEFT button and starts again for
- * a lit RIGHT one — ONE boundary, at device 11.98 in both glyphs, not a gap
- * straddling the centre. The button fills stop short of it by 1.25 on the left
- * and start 0.75 past it on the right, which is why modelling this as a
- * symmetric "gap" beside a button could not reproduce either glyph.
- */
+/** Shared shell-stroke boundary; button fills end 1.25 units before it on the left and start 0.75 after it on the right. */
 const DIVIDER_X = 6.25;
-/**
- * The shell's OUTER corner radius, and the number two cuts got wrong — first
- * as a capsule (half the width), then as 2 from an ink threshold. SOLVED on
- * the 50% contour of the middle glyph's bottom-left and top-right corners
- * (`modeling.png`, device x 122..145, y 2065..2096): the contour runs 4.04,
- * 2.39, 1.33, 0.55, 0.05, -0.28 device from the straight edge over successive
- * rows, and a circle of radius 7.16 device reproduces all six to within 0.11.
- * The opposite corner independently gives 7.2. Halved, 3.6 — and both wrong
- * answers were visible at full scale as the wrong SHAPE, not the wrong size.
- */
+/** The mouse shell’s outer corner radius is 3.6 CSS px. */
 const RADIUS = 3.6;
 /** The ink box, in CSS px, and the viewBox. */
 const BOX = { width: 12, height: 16 } as const;
@@ -153,9 +42,7 @@ function MouseGlyph({ button }: { button: MouseButton }) {
       role="presentation"
       aria-hidden="true"
       focusable="false"
-      // 16 CSS px, which is the `lg` icon rung — and Blender's glyph measures
-      // exactly 16 CSS tall in the frame. `width: auto` then resolves to 12
-      // from the viewBox, the measured width, with no second number to drift.
+      // Use the 16-px icon-lg height; the viewBox supplies the 12-px width.
       style={{ height: 'var(--volter-icon-lg)', width: 'auto', display: 'block', flex: '0 0 auto' }}
     >
       <title>{button} mouse button</title>
@@ -211,23 +98,14 @@ export default function BlenderMouseHintsStatus() {
     <span
       className="volter-status-copy"
       data-testid="status-blender-mouse-hints"
-      // Blender's hint-to-hint gap is 9.5 CSS (glyph 1 ends at 51.5, glyph 2
-      // starts at 61; the second gap repeats it to a tenth). `space-5` is 10.
+      // The 10px space-5 token approximates Blender's 9.5px hint gap.
       style={{ display: 'inline-flex', alignItems: 'center', gap: 'var(--volter-space-5)' }}
     >
       {HINTS.map((hint) => (
         <span
           key={hint.button}
           data-mouse-button={hint.button}
-          // NO COLOUR HERE. The band declares its own ink and Blender's status
-          // bar is the DIMMEST text in its window — `#878787` (135) flat, on
-          // every frame, against the 216 its top-bar menus ink. A contribution
-          // that pins `content.muted` (194) makes itself the loudest thing in
-          // the quietest band; inheriting is what keeps the band one voice.
-          //
-          // The SIZE is measured: Blender's status text caps at 9.0 CSS (18
-          // device), which is the `md`/`base` rung (11px -> 8.8), not `sm`
-          // (10px -> 8.0).
+          // Inherit the status band’s colour and base font size.
           style={{
             display: 'inline-flex',
             alignItems: 'center',
@@ -243,17 +121,3 @@ export default function BlenderMouseHintsStatus() {
     </span>
   );
 }
-
-/**
- * ORDER, and the one thing this cannot have. Blender's hints are the
- * LEFTMOST thing in its bottom row. A contributed status item cannot be:
- * `tool-loader.ts:1145` registers it at `contributedSectionOrder(order)`,
- * which is `CONTRIBUTED_SECTION_ORDER + (order ?? 999)`
- * (`tool-loader.ts:359-361`) with `CONTRIBUTED_SECTION_ORDER = 5000`
- * (`inspection/model.ts:475`), while the host's own left items register at
- * -90..40 (`components/status-contributions.tsx`). Every contributed item
- * therefore lands BEHIND every core item, by construction — the band exists
- * precisely so a contribution cannot outrank a built-in. `order = 0` is the
- * front of what the contract allows: first among contributed left items,
- * after the host's save/console/play cluster.
- */

package/contributions/blender.style.ts

@@ -1,45 +1,6 @@
-/**
- * The BLENDER style bundle — Blender's greys and widget blue as a palette
- * document (`blender.palette.json`, the same v3 shape a person imports), its
- * own opaque material, and Blender's chrome regions
- * (`@volter/sdk/looks`, a `workspace.style` contribution).
- *
- * The material transcribes Blender's default theme: widgets round at 0.2 of
- * their height (4px on a 20px widget), areas and panels are flat with no
- * shadow, and only menus and popovers cast one (`menu_shadow_fac` 0.5 over
- * `menu_shadow_width` 4). The `large` radius is our reading — Blender rounds
- * its popovers the same as its menus. The density is measured from Blender
- * 5.2's own frames at 1x:
- * 26px top bar and area headers, 24px status bar, and — re-measured against
- * the frames widget by widget — EVERY widget 20px tall, button/field/toggle
- * alike, so all three control sizes are 20 rather than a 18/20/24 ramp
- * Blender does not have. Its UI face measures 11px (an 8px cap+ascender on
- * "Add Modifier"); the rest of the type scale is our reading.
- *
- * THE ICON SET (`blender.icons.json`) IS PART BLENDER'S, AND THAT IS WHY THIS
- * PACKAGE CARRIES TWO LICENCES. Of its 346 glyphs, 197 are machine-TRACED —
- * byte for byte — from Blender's own vector sources
- * (`release/datafiles/icons_svg/*.svg`, 188 distinct files at the engine's
- * pin): an affine transform of Blender's outline onto a 16-unit grid, nothing
- * re-proportioned or re-centred, so a traced glyph IS Blender's drawing and a
- * derivative of GPL-2.0-or-later artwork. Their provenance — `ICON_*` name,
- * source file and sha256 per glyph — is `blender.icons.traced.json`, written
- * by `blender-icon-trace.mjs`. The other 149 are our own drawings in Blender's
- * idiom: a 16-unit grid, monochrome filled silhouettes, ~1.3-unit round-ended
- * strokes, no outline around a fill.
- *
- * So `@volter/editor-blender` is `AGPL-3.0-only AND GPL-3.0-or-later` — our code AGPL,
- * Blender's artwork GPL, combined under each licence's §13
- * (`packages/blender/LICENSE` carries the notice and both texts). NOTHING
- * TRACED MAY BE COPIED INTO AN APACHE-2.0 OR MIT PART OF THIS REPO;
- * `packages/editor`'s own icon set in particular stays free of it.
- *
- * A glyph is EDITED in `blender-icons.source.mjs` and the JSON re-emitted by
- * running it; a path `d` is not a thing a person edits by hand.
- */
+/** Blender’s workspace style supplies theme colours, opaque material, typography and region geometry. Widgets round at 0.2 of their height; menus and popovers carry the theme shadow. blender-icons.source.mjs generates the icon set. Traced Blender artwork is GPL-3.0-or-later, combined with this package’s AGPL-3.0-only code under both licences’ section 13; preserve LICENSE and per-glyph provenance in blender.icons.traced.json. Do not copy traced artwork into Apache-2.0 or MIT packages. */
 import type { IconSetContribution, StyleContribution } from '@volter/sdk/looks';
 import iconsJson from './blender.icons.json';
-import palette from './blender.palette.json';
 
 /**
  * `resolveJsonModule` widens every string in a JSON import, so each glyph's
@@ -54,7 +15,8 @@ export const point = 'workspace.style';
 export const style: StyleContribution = {
   id: 'blender',
   title: 'Blender',
-  paletteId: 'blender',
+  // Theme role values come from userdef_default_theme.c through scripts/workbench/generate-blender-theme.mjs. JSON carries the palette; constants below define this style’s chrome geometry.
+  colorTheme: 'blender',
   materialId: 'blender',
   material: {
     id: 'blender',
@@ -69,139 +31,47 @@ export const style: StyleContribution = {
     density: {
       control: { compact: 20, default: 20, comfortable: 20 },
       font: { xs: 9, sm: 10, base: 11, md: 11, lg: 12 },
-      // Blender's glyphs, measured at matched scale: 14 px through the
-      // chrome (the Properties tab rail in `properties-data-edit.png`, the
-      // Outliner's row and toggle marks in `outliner.png`).
-      //
-      // `2xl` is now MEASURED too, and it came down from the extrapolated 20.
-      // Its only consumer is the viewport navigation cluster
-      // (`ViewportFurniture.tsx`), and Blender's own cluster in
-      // `modeling-object-none.png` draws 15x15 px of INK at 1x. These glyphs
-      // ink at ~0.85 of their box (`blender-icons.source.mjs`'s `S` dial), so
-      // 15 px of ink is an 18 px box — at 20 the cluster measured 17x17,
-      // two pixels heavier than the frame it is copying.
-      //
-      // `xs` IS MEASURED NOW, and the note it replaces was wrong about the
-      // frames: they do show glyphs below the 14 px chrome rung — the claim
-      // had only ever looked at the status bar. The whole sub-14 inventory,
-      // ink bounding boxes in CSS px (device halved), all at native 2x:
-      //
-      //   `+` Add Modifier      `properties-modifier.png`   9.0 x 9.0
-      //   `+` list add          `properties-data-edit.png`  9.0 x 9.0
-      //   chevron, list button  `properties-data-edit.png`  9.0 x 5.0
-      //   chevron, panel band   `properties-data-edit.png`  9.0 x 5.0
-      //   caret, datablock well `properties-data-edit.png`  6.5 x 4.0
-      //   caret, editor-type    `properties-modifier.png`   6.5 x 4.0
-      //   grip `::::`           `properties-data-edit.png` 10.0 x 4.0
-      //   triangle, list row    `properties-data-edit.png`  6.0 x 5.0
-      //
-      // FOUR of those agree at 9.0 wide and that is the rung. Solved against
-      // the one glyph both sides draw on the same fill (`#535353`, so the
-      // threshold is identical): Blender's `+` arms measure 17.43 and 17.08
-      // device px by sub-pixel coverage, mean 8.63 CSS; ours at `xs` 12
-      // measure 20.75 device (10.38 CSS, against the path's own geometric
-      // bbox of 10.48 — they agree to a tenth). Our glyphs ink 0.865 of the
-      // box, so the box that inks 8.63 is 9.98. Two other estimators on the
-      // same pair — ink MASS (mass scales as the square, ratio 0.8171) and
-      // the pixel bbox (18/22 = 0.818) — give 9.81 and 9.82. The rung is 10.
-      //
-      // THE RUNG WAS CHECKED AGAINST A SECOND GLYPH FAMILY AFTER LANDING,
-      // and it holds: at 10 the dock well's caret inks 5.84 x 3.71 CSS
-      // against Blender's editor-type caret at 6.0 x 4.0 (12 x 8 device,
-      // `properties-modifier.png` x 62..73, y 23..30). Our chevron inks 0.58
-      // of its box where the `+` inks 0.87, so the two agree on the rung
-      // only because each was solved against its own counterpart — which is
-      // why both were measured rather than one inferred from the other.
-      //
-      // RESIDUE, measured not closed: Blender has TWO chevron sizes, the
-      // well caret at 6.0 wide and the panel-band / list-button chevron at
-      // 9.0, and they are not a uniform scale of each other (0.67 wide
-      // against 0.80 tall). One rung cannot serve both; our chevron lands on
-      // the well caret, so a band chevron drawn at `xs` would ink 5.84 where
-      // Blender's inks 9.0. Closing that needs a second glyph, not a rung —
-      // and no expanded band is on screen in the Model document to confirm
-      // it against.
+      // Icon boxes account for each glyph’s optical extent; small controls, ordinary chrome and viewport navigation use distinct rungs.
       icon: { xs: 10, sm: 14, md: 14, lg: 16, xl: 16, '2xl': 18 },
       chrome: {
+        // The top bar's height, traced from Blender 5.2's own frames at 1x.
         commandBar: 26,
         panelHeader: 26,
         localToolbar: 26,
+        // Blender’s Outliner row pitch is 20 CSS pixels.
         treeRow: 20,
-        // The Outliner's tree is a SQUARE grid — one level steps by the row's
-        // own height. Measured on the native 2x `outliner.png`: the type
-        // glyphs of Scene Collection, Collection and Camera centre at x 60.5,
-        // 100.5 and 140.5 device px (30.25 / 50.25 / 70.25 CSS) and each
-        // row's chevron sits one cell to the left of its glyph (Collection's
-        // at 30.25, Camera's at 50.25), so the step is 20 and the chevron and
-        // the glyph each own one cell of it.
+        // Outliner depth steps by one row-height cell; each row’s chevron occupies the cell before its type glyph.
         treeIndent: 20,
         statusBar: 24,
-        // The toolbar, RE-MEASURED 2026-09-18 on the native 2x frame
-        // (`modeling-edit-none.png`, column x=25 and row y=400): a tool is a
-        // 40x35 BORDER BOX — 38x34 of `widget.menu` fill inside a one-pixel
-        // boundary — and the boxes are CONTIGUOUS within a group, sharing that
-        // one pixel, so the pitch down a strip is 35. Plain viewport shows
-        // only BETWEEN groups (four times in Blender's twenty-one-tool rail).
-        // These three numbers are the border box, because that is what the
-        // rail's CSS sets and what the collapse (`margin-block-start: -1px`
-        // in `workspace-dock.css`) measures against: 36 - 1 = the 35 pitch.
-        //
-        // `toolGap` RE-RE-MEASURED 2026-09-19 on the same frame, BOX EDGE TO
-        // BOX EDGE rather than fill to fill: group 1's border box ends at
-        // device y 312 and group 2's begins at 323, so the separation is 10
-        // device px — 5 CSS, not the 7 or 8 the two earlier readings gave.
-        // Both were counting the group's own 1 CSS px emboss (device rows
-        // 313-314, luminance 53 over the viewport's 63) and the two borders
-        // as part of the bare viewport between the groups.
+        // Toolbar dimensions are border boxes. Adjacent tools share a one-pixel boundary; toolGap separates groups.
         toolSize: 36,
         toolWidth: 40,
         toolGap: 5,
-        // THE AREA SEAM, measured on the native 2x `modeling.png`: the
-        // Outliner-to-Properties groove (median over x 2900..3400) runs
-        // y 419..425 as (21,21,21) and the viewport-to-Properties groove
-        // runs x 2836..2842 as the same value — 7 device px, 3.5 CSS px,
-        // both times with a one-pixel lighter emboss on each side. The
-        // colour is the palette's `color.boundary.area`.
+        // The area seam is a 3.5-CSS-px dark groove between docked areas.
         areaSeam: 3.5,
-        // THE EMBOSS on each side of that groove, as percent of white mixed
-        // into the area's OWN fill. SOLVED on the native 2x `modeling.png`
-        // from four fills and their light bands — Properties 47 -> 64
-        // (x=3200, y 426..427), Outliner 39 -> 57/56 (y=300, x 2843..2844),
-        // the Properties tab rail 23 -> 43/42 (y=1500, same columns), the
-        // Outliner's alternate row 42 -> 59/60 (x=3200, y 417..418) — whose
-        // individual alphas are 8.17/8.10/8.62/8.45%, mean 8.14; 8.2 is the
-        // one value that renders all four measured integers. The viewport's
-        // 63 -> 93/94 and the 3D View header's 52 -> 86 are this same lift
-        // applied TWICE; see `theme.ts`'s `areaEmbossValue`.
+        // Emboss mixes white into each area’s own fill; overlapping viewport passes apply the lift twice.
         areaEmboss: 8.2,
+        // Viewport navigation uses its own 28-px button size rather than the 20-px menu/header control height.
+        navigationControl: 28,
+        // Center the collapsed 4.5×9 and expanded 8.5×5 CSS-pixel carets in an 18-pixel cell.
+        treeCaret: 18,
+        // Outliner glyph plates use a 5-CSS-px corner radius.
+        treeGlyphPlateRadius: 5,
+        // Composite Outliner glyphs at 0.80 over the row fill.
+        treeGlyphOpacity: 0.8,
       },
     },
     stage: {
-      // BLENDER'S GIZMO IS A CONSTANT SCREEN SIZE (owner, 2026-09-21: "is
-      // gizmo perhaps the wrong size?"). `U.gizmo_size` is 75
-      // (`DNA_userdef_types.h:1095`; Preferences > Viewport > Gizmos > Size,
-      // `rna_userdef.cc:5415-5419`, range 10..200), and it is px PER GIZMO
-      // UNIT: `wm_gizmo.cc:450-474` sets `scale_final = scale_basis *
-      // UI_SCALE_FAC * U.gizmo_size * ED_view3d_pixel_size_no_ui_scale(...)`,
-      // whose last term is world units per DEVICE px against a
-      // `UI_SCALE_FAC` of device px per UI px — so one gizmo unit is 75 CSS
-      // px whatever the display scale (read back from the engine's own pin
-      // on this box: `ui_scale=2.0 pixel_size=2.0 gizmo_size=75`).
+      // Blender gizmo units stay 75 CSS px at every display scale, using world units per device pixel and UI_SCALE_FAC.
       gizmoSize: 75,
       // A resting handle at 0.6 opacity, a highlighted one opaque in its own colour
       // (`transform_gizmo_3d.cc`, `gizmo_get_axis_color`).
       gizmoOpacity: 0.6,
-      // BLENDER'S OUTLINE IS A HARD LINE, and hidden parts are not drawn: four device pixels
-      // of orange around the cube in `modeling-object-selected.png` (at 2x), no halo.
+      // Blender’s selection outline is a hard 2-CSS-pixel line without a halo; hidden parts are not drawn.
       outlineStyle: 'crisp',
       outlineWidth: 4,
       outlineHidden: false,
-      // BLENDER'S FLOOR LINES, in device pixels, measured across one scanline of
-      // `modeling-object-none.png` at device resolution: the 1 m line is 4 px at half rise and
-      // plateaus at 83, the 10 m line is 6 px and plateaus at 101 — so the major line is wider
-      // (2.25 against 1.5) and carried (102 − 63) / (84 − 63) past the minor's colour from the
-      // background they share. Stated here, the look's, since the editor's own floor is a
-      // single hairline level.
+      // The Blender floor uses distinct major/minor line widths and colour strengths over the shared background.
       gridLineWidth: 1.5,
       gridMajorWidth: 2.25,
       gridMajorContrast: 39 / 21,
@@ -215,5 +85,8 @@ export const style: StyleContribution = {
     },
   },
   icons,
-  palette,
+  typography: {
+    sans: "'Inter', 'DejaVu Sans', system-ui, sans-serif",
+    mono: "'DejaVu Sans Mono', Menlo, monospace",
+  },
 };