@volter/editor-blender 0.1.150 → 0.1.152

package/contributions/properties-modifiers.inspector.tsx

@@ -1,32 +1,4 @@
-/**
- * BLENDER'S MODIFIERS TAB, as a Properties section (WORK.md §Blender in the
- * tab is Blender, "Inspection parity", I2): the STACK, each modifier its own
- * panel with its own settings, with the generic view beneath under "All
- * properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_data_modifier.py` at
- * the engine's pin, and reading it is what decided the shape here. That file
- * is barely a panel list at all: `DATA_PT_modifiers.draw` is `Add Modifier`
- * plus `layout.template_modifiers()`, and the per-modifier panels are built in
- * C from each type's own RNA (`MOD_*.cc`'s `panel_draw`). There is no Python
- * table of sixty modifier types to transcribe — and transcribing one would be
- * a COPY of Blender's layout, which the ruling forbids, and would go stale the
- * first time a modifier gained a property.
- *
- * So the stack is derived instead: each member of `ob.modifiers` is a panel
- * headed by the four toggles every modifier has (`ModifierData`'s own
- * `show_viewport` / `show_render` / `show_in_editmode` / `show_on_cage`,
- * which is the header row `template_modifiers` draws), followed by every
- * property THIS MODIFIER'S OWN struct declares — `andDeclared`, which reads
- * `BlenderRnaRow.group`, RNA's own answer to "which struct declares this".
- * For a Subdivision modifier that is exactly `SubsurfModifier`'s levels,
- * render_levels, quality, uv_smooth and the rest, in RNA's order.
- *
- * The ACTIVE modifier (`buttons_context_path_modifier`, which the door reports
- * as `activeModifier`) is marked, the way Blender outlines the active panel.
- *
- * It stands when: the object's type is in `buttons_context.cc`'s modifier set.
- */
+/** Blender’s Modifiers Properties tab follows scripts/startup/bl_ui/properties_data_modifier.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 
@@ -37,7 +9,7 @@ const CURATED: readonly BlenderCuratedPanel[] = [
     collection: true,
     active: 'activeModifier',
     // `ModifierData`'s own, in the order `template_modifiers` heads a panel
-    // with them; everything after these is the type's own (see the header).
+    // with them; everything after these is the type's own.
     properties: [
       'name',
       'type',

package/contributions/properties-object.inspector.tsx

@@ -1,34 +1,4 @@
-/**
- * BLENDER'S OBJECT TAB, as a Properties section (WORK.md §Blender in the tab
- * is Blender, "Inspection parity", I2). The body is Blender's own panels, in
- * Blender's own order, over the RNA door; the generic view of every property
- * the object has stays beneath them under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_object.py`, read at
- * the engine's pin. Its `classes` tuple at the foot of the file is the panel
- * ORDER, each class's `bl_label` the title, each `layout.prop(ob, "x")` an
- * entry below in the order the draw function lists it, and `bl_options =
- * {'DEFAULT_CLOSED'}` a `closed: true`. Blender's UI layer is never run,
- * ported or recorded — the Python is read as a statement of WHICH properties
- * this tab shows, and our widgets draw them from the door's rows.
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS:
- *  - type-only `poll`/`if` branches. `show_all_edges` is mesh-only in Python; here
- *    it is simply not on a Camera's RNA, so it does not draw. Same outcome,
- *    from the datablock rather than from a copy of Blender's conditions.
- *    Rotation mode is a value on every object, so its draw branch is retained.
- *  - `OBJECT_PT_context_object` (`bl_label = ""`) — the breadcrumb row, which
- *    is the host's identity row here.
- *  - the four panels whose datablock is NOT the object: Motion Paths reads
- *    `ob.animation_visualization` and `ob.motion_path`, Light/Shadow Linking
- *    their collections. The context door names the object, so those are
- *    reached by drilling their POINTER row in the generic view beneath — a
- *    curated panel addresses one of the TAB's own datablocks, and inventing a
- *    second addressing scheme to reach a sub-struct is the kind of machinery
- *    the generic view exists to make unnecessary.
- *
- * It stands when: `buttons_context_path_object` — there is an active object.
- */
+/** Blender’s Object Properties tab follows scripts/startup/bl_ui/properties_object.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
@@ -196,19 +166,7 @@ export const order = 70;
  *  object group (Object … Material), then Texture. The presentation draws a
  *  separator wherever this changes. */
 export const railGroup = 'object';
-/** THE TAB THE RAIL OPENS ON. Blender's Properties editor stores its context
- *  per screen in the startup file, and at factory settings the Layout
- *  workspace's is OBJECT:
- *
- *    bpy.data.screens['Layout'].areas[PROPERTIES].spaces[0].context -> 'OBJECT'
- *
- *  (measured against Blender 5.2.0 LTS at `--factory-startup`, walk 5 parity
- *  row 3; the other screens read OBJECT, MODIFIER, WORLD, DATA, TOOL, OUTPUT
- *  and RENDER, so a per-workspace default is the next fidelity step and this
- *  one declaration is the Layout/Model answer). Without it the rail opened on
- *  Render — the first tab in `ED_buttons_tabs_list`'s order — and a person
- *  selecting the cube got Sampling and Light Paths where Blender shows
- *  Transform. */
+/** The Model Properties rail opens on Object, matching the factory Layout workspace’s context. */
 export const railDefault = true;
 export const match = blenderPropertiesTabMatch(TAB);
 export default blenderPropertiesTabSection(TAB);

package/contributions/properties-output.inspector.tsx

@@ -1,30 +1,4 @@
-/**
- * BLENDER'S OUTPUT TAB, as a Properties section (WORK.md §Blender in the tab
- * is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_output.py` at the
- * engine's pin — `classes` (`:728-748`) is the panel order, `bl_label` the
- * title, each `layout.prop(rd, "x")` an entry in the order the draw function
- * lists it. Blender's UI layer is never run, ported or recorded.
- *
- * THE TAB'S DATABLOCK IS `scene.render`, and three panels reach past it: Frame
- * Range is the SCENE's own `frame_start`/`frame_end`/`frame_step` (`:151`),
- * Output's Color Management is `rd.image_settings` (`:371`), and Encoding is
- * `rd.ffmpeg` (`:499`). The context door names each beside the render
- * settings as one of this tab's paths and the rows say which they come from
- * ({@link BlenderCuratedProperty}).
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS:
- *  - the preset menus (`RENDER_PT_format_presets` `:15`,
- *    `RENDER_MT_framerate_presets` `:28`, `RENDER_PT_ffmpeg_presets` `:22`)
- *    and `template_image_settings`/`template_image_views` — operator and
- *    template widgets. Inspection parity, not editing parity.
- *  - `RENDER_PT_output_pixel_density` (`:396`), whose body is a preset menu
- *    plus two properties behind it; the two are named here.
- *
- * It stands when: `buttons_context_path_scene` — the same path as Render.
- */
+/** Blender’s Output Properties tab follows scripts/startup/bl_ui/properties_output.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 

package/contributions/properties-particles.inspector.tsx

@@ -1,48 +1,4 @@
-/**
- * BLENDER'S PARTICLES TAB, as a Properties section (WORK.md §Blender in the
- * tab is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_particle.py` at the
- * engine's pin — `classes` (`:2248-2302`) is the panel order, `bl_label` the
- * title, each `layout.prop(part, "x")` an entry. Blender's UI layer is never
- * run, ported or recorded.
- *
- * NEARLY EVERY PANEL DRAWS `psys.settings`, NOT THE SYSTEM. `part` in these
- * draw functions is `particle_get_settings(context)` (`:40-46`), which is the
- * active system's ParticleSettings — a datablock of its own. The system
- * itself carries only a handful (`seed`, `parent`, `child_seed`, the
- * vertex-group names, `use_hair_dynamics`). The context door names both, plus
- * the hair-dynamics cloth settings, as this tab's paths, and each row says
- * which it comes from.
- *
- * THE TYPE POLLS ARE READ, and this tab is why `when` exists. Blender gates
- * these panels on values rather than on structure: `settings.type == 'HAIR'`
- * (Hair Dynamics `:362`, Hair Shape `:2205`), `settings.physics_type` in
- * NEWTON/FLUID or == BOIDS (`:1161`, `:1195`, `:1222`, `:934`),
- * `settings.render_type` (`:1449`, `:1507`, `:1536`), `settings.child_type`
- * (`:1743`, `:1778`), `settings.is_fluid` (`:272`). Every one of those
- * properties is on the same struct under every mode, so RNA cannot answer the
- * poll and the condition is read from the ENGINE's live value instead — a copy
- * of Blender's test, never of its branching.
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS:
- *  - `PARTICLE_PT_context_particles` (`:156`, `bl_label = ""`) — the systems
- *    list plus the settings ID template. The list itself is the first panel
- *    here, as a collection with the active system marked; the `template_ID`
- *    row is an editing widget.
- *  - the Boids panels (`:931`-`:1045`) and the fluid-spring panels
- *    (`:835`-`:928`): both read sub-structs of the settings (`part.boids`,
- *    `part.fluid`), which stand as POINTER rows in the Physics panel and
- *    drill. Naming a fourth and fifth datablock on this tab to reach a mode
- *    almost nothing uses is the machinery the generic view exists to avoid.
- *  - `PARTICLE_PT_boidbrain` (`:1254`) — a rules list with per-rule operators.
- *  - `template_curve_mapping` (the clump and roughness curves) — a curve
- *    widget this view does not draw.
- *  - `PARTICLE_PT_custom_props` (`:2243`), IDProperties rather than RNA.
- *
- * It stands when: `buttons_context_path_particle` — `ob->type == OB_MESH`.
- */
+/** Blender’s Particles Properties tab follows scripts/startup/bl_ui/properties_particle.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 
@@ -193,7 +149,7 @@ const CURATED: readonly BlenderCuratedPanel[] = [
   },
   {
     // PARTICLE_PT_physics, :730. `boids` and `fluid` are the two mode
-    // sub-structs whose own panels are one drill away (see the header).
+    // sub-structs whose own panels are one drill away.
     title: 'Physics',
     closed: true,
     from: 'Settings',

package/contributions/properties-physics.inspector.tsx

@@ -1,42 +1,4 @@
-/**
- * BLENDER'S PHYSICS TAB, as a Properties section (WORK.md §Blender in the tab
- * is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS SEVEN FILES, not one: `properties_physics_common.py`
- * carries the tab's own header block, and `properties_physics_rigidbody.py`,
- * `_rigidbody_constraint.py`, `_cloth.py`, `_softbody.py`, `_field.py`
- * (Force Fields AND Collision), `_fluid.py` and `_dynamicpaint.py` each carry
- * one simulation. Each panel below cites its file and line. Blender's UI
- * layer is never run, ported or recorded.
- *
- * THE "ENABLE BUTTONS" ROW IS NOT DRAWN, AND WHAT IT SAYS STILL IS.
- * `PHYSICS_PT_add` (`properties_physics_common.py:55`) is a grid of
- * `object.modifier_add` / `rigidbody.object_add` OPERATORS — editing, not
- * inspection (ARCHITECTURE-CORE §Blender north star), and this view draws
- * properties. What that row COMMUNICATES is which simulations the object has,
- * and that is exactly which panels stand here: the context door resolves a
- * path per simulation the way `physics_add`/`physics_add_special` test for
- * one — the data for `obj.rigid_body`, `obj.rigid_body_constraint`,
- * `obj.soft_body`, `obj.collision` and `obj.field`, and a MODIFIER of the
- * right type for cloth, fluid and dynamic paint (Blender's `context.cloth` is
- * the ClothModifier, and the panels read its `settings` structs). An absent
- * simulation is an absent path and its panels do not draw.
- *
- * FLUID AND DYNAMIC PAINT STOP AT THEIR TYPE. Both are a modifier whose whole
- * panel set is per-`fluid_type` / per-`ui_type` — domain, flow and effector
- * are three different property surfaces, and dynamic paint's canvas splits
- * again per surface. What stands here is the modifier's type row and the
- * pointer to the settings struct the type selects, which drills into the
- * generic view; transcribing three or four alternative panel sets each is the
- * machinery the generic view exists to make unnecessary. Stated, not
- * silently partial.
- *
- * It stands when: `buttons_context_path_object` — Physics shares Object's
- * path, so the engine grants it whenever it grants Object. It is
- * context-gated rather than standing because the Properties editor follows
- * the ACTIVE OBJECT, not the row that was clicked.
- */
+
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 
@@ -578,8 +540,7 @@ const CURATED: readonly BlenderCuratedPanel[] = [
     ],
   },
   {
-    // properties_physics_fluid.py — see the header for why this stops at the
-    // type and the settings pointer.
+    // properties_physics_fluid.py: show the type and settings pointers; each pointer drills into its properties.
     title: 'Fluid',
     from: 'Fluid',
     properties: ['fluid_type', 'domain_settings', 'flow_settings', 'effector_settings'],

package/contributions/properties-render.inspector.tsx

@@ -1,48 +1,4 @@
-/**
- * BLENDER'S RENDER TAB, as a Properties section (WORK.md §Blender in the tab
- * is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_render.py` at the
- * engine's pin — `classes` (`:1186-1236`) is the panel order, `bl_label` the
- * title, each `layout.prop(…)` an entry, `bl_parent_id` a `sub`. Blender's UI
- * layer is never run, ported or recorded.
- *
- * THIS TAB IS WHERE THE ENGINE POLLS BECOME REAL, and it is the ONE `poll`
- * this transcription reads. Every other condition is dropped because RNA
- * already answers it — a property a datablock does not carry does not draw.
- * `COMPAT_ENGINES` is different in kind: `scene.eevee` and `scene.display`
- * exist under every engine, so nothing about the datablock says whether
- * Blender would draw the panel. Each panel below carries Blender's own LIST
- * (`COMPAT_ENGINES`, once per class) and it is checked against the ENGINE's
- * live answer — `rna_context`'s `engine`, which is `scene.render.engine`,
- * which is what `context.engine` is. The three ids a script can name here are
- * CYCLES, BLENDER_EEVEE and BLENDER_WORKBENCH (`session.py::_register_engine`);
- * the factory engine is BLENDER_EEVEE (`wasm/BUNDLE.json`), so the EEVEE
- * panels are what a fresh file draws. Cycles' own panels are the add-on's, not
- * `bl_ui`'s, and are therefore not in this file's specification.
- *
- * SEVERAL PANELS DRAW TWO DATABLOCKS IN ONE LIST — `RENDER_PT_eevee_film`
- * (`:757`) takes `filter_size` and `film_transparent` off `scene.render` and
- * `use_overscan`/`overscan_size` off `scene.eevee`, in that order. The
- * qualified property form keeps the row in Blender's position while naming
- * the datablock it comes from (`BlenderCuratedProperty`); the context door
- * names every one of them as this tab's own paths.
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS:
- *  - every operator and preset menu: `RENDER_PT_format_presets`,
- *    `RENDER_PT_eevee_raytracing_presets` (`:380`), the light-probe bake
- *    buttons. Inspection parity, not editing parity.
- *  - `template_curve_mapping` (the motion-blur shutter curve `:283`, the
- *    colour-management curves `:185`) and `template_colormanaged_view_settings`
- *    — curve widgets, which this view does not draw; the datablock is one
- *    drill away in the generic view beneath.
- *  - `RENDER_PT_hydra_debug` (`:1165`): its engine is HYDRA_STORM, which this
- *    build does not register, and its poll also wants a developer-UI
- *    preference.
- *
- * It stands when: `buttons_context_path_scene` — a scene always resolves.
- */
+/** Blender’s Render Properties tab follows scripts/startup/bl_ui/properties_render.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 

package/contributions/properties-scene.inspector.tsx

@@ -1,38 +1,4 @@
-/**
- * BLENDER'S SCENE TAB, as a Properties section (WORK.md §Blender in the tab
- * is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_scene.py` at the
- * engine's pin — its `classes` tuple (`:471-488`) is the panel order,
- * `bl_label` the title, each `layout.prop(scene, "x")` an entry in the order
- * the draw function lists it, `bl_options = {'DEFAULT_CLOSED'}` a `closed`
- * and `bl_parent_id` a `sub`. Blender's UI layer is never run, ported or
- * recorded.
- *
- * SEVERAL OF THESE PANELS DRAW A SUB-STRUCT RATHER THAN THE SCENE: Units is
- * `scene.unit_settings`, Rigid Body World is `scene.rigidbody_world`, Light
- * Probes is `scene.eevee`. The context door names each of those beside the
- * scene as one of this tab's own datablocks (`session.py::rna_context`), the
- * way it already named the Output tab's `image_settings`, and each panel says
- * which it reads with `from`. An absent one — a file with no rigid body world
- * — is an absent path, and the panel does not draw: the same answer
- * `RigidBodySubPanel.poll` gives (`:361-367`), from the door rather than from
- * a copy of its condition.
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS:
- *  - `SCENE_PT_context_scene` (`:37`, `bl_label = ""`) — the scene ID
- *    template, which is the host's identity row here.
- *  - the operator rows: `rigidbody.world_add`/`_remove` (`:357-359`), the
- *    keying-set list's add/remove, `object.lightprobe_cache_bake` (`:447`).
- *    Inspection parity, not editing parity (ARCHITECTURE-CORE §Blender north
- *    star) — an operator is not a property and this view draws properties.
- *  - `SCENE_PT_custom_props` (`:467`). Custom properties are IDProperties;
- *    they are not in `bl_rna.properties` and the door answers RNA. Same
- *    reading as the Object tab's.
- *
- * It stands when: `buttons_context_path_scene` — a scene always resolves.
- */
+
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 import { resolveBlenderSubject } from './blender-properties-model';

package/contributions/properties-texture.inspector.tsx

@@ -1,52 +1,4 @@
-/**
- * BLENDER'S TEXTURE TAB, as a Properties section (WORK.md §Blender in the tab
- * is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_texture.py` at the
- * engine's pin — `classes` (`:958-986`) is the panel order and `bl_label` the
- * title — AND `space_buttons/buttons_texture.cc`, which is the only thing
- * that can say WHICH texture this tab is about. Blender's UI layer is never
- * run, ported or recorded.
- *
- * THIS TAB HAS NO DATABLOCK OF ITS OWN; IT HAS A USER.
- * `buttons_texture_users_from_context` (`buttons_texture.cc:244-366`) walks
- * the context for every struct holding a texture pointer, in this order: the
- * scene's compositing node tree ("Compositor"), the active line style's slots
- * and node tree ("Line Style"), the object's modifiers ("Modifiers"), the
- * ACTIVE particle system's `part.mtex[]` ("Particles"), the object's force
- * field when its type is TEXTURE ("Fields"), and the active paint brush's own
- * two slots ("Brush"). `buttons_texture_context_compute` (`:369`) then takes
- * user `ct->index` — 0 unless a person picks another from the menu — and the
- * texture it points at is `context.texture`. The door mirrors that walk in
- * the C's own order and names the resolved texture as this tab's first path,
- * the holder as its second, and `bpy.data.textures` as its third; the whole
- * user list is on the context as `textureUsers` for anything that wants it.
- *
- * A LIGHT IS NOT A TEXTURE USER AT THIS PIN, and it is worth saying because
- * older Blenders make it a reasonable guess: the C never looks at `ob->data`.
- * Lamp textures went with 2.8's renderer rewrite. Measured, not remembered.
- *
- * THE TYPE PANELS ARE THE `when` MECHANISM'S OTHER HOME. `TextureTypePanel`
- * (`:167`) is `tex.type == cls.tex_type and not tex.use_nodes`, once per type
- * — every one of those properties lives on the same `Texture` struct under
- * every type, so RNA cannot answer it and the condition is read from the
- * engine's live value.
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS:
- *  - `TEXTURE_PT_preview` (`:68`) and `TEXTURE_PT_context` (`:99`) — a
- *    `template_preview` render and the user-picker/ID templates. The picker
- *    is an editing widget; what it selects is the context door's answer here.
- *  - `TEXTURE_PT_node` (`:143`), `template_node_view` over the active texture
- *    node — the read-only node view is I5.
- *  - `template_image` (`:404`) and `template_color_ramp` (`:910`) — an image
- *    browser and a ramp widget; the `image` pointer and the `color_ramp`
- *    pointer stand and drill.
- *  - `TEXTURE_PT_custom_props` (`:953`), IDProperties rather than RNA.
- *
- * It stands when: the door's mirror of `buttons_texture_context_compute`
- * finds a user, or the file holds textures at all.
- */
+/** Blender’s Texture Properties tab follows scripts/startup/bl_ui/properties_texture.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 

package/contributions/properties-view-layer.inspector.tsx

@@ -1,32 +1,4 @@
-/**
- * BLENDER'S VIEW LAYER TAB, as a Properties section (WORK.md §Blender in the
- * tab is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_view_layer.py` at the
- * engine's pin — `classes` (`:345-360`) is the panel order, `bl_label` the
- * title, each `layout.prop(view_layer, "x")` an entry. Blender's UI layer is
- * never run, ported or recorded.
- *
- * THE PASSES PANEL IS TWO PANELS UNDER TWO ENGINES, and that is why this tab
- * reads `COMPAT_ENGINES`. `VIEWLAYER_PT_eevee_layer_passes_data` (`:111`) and
- * `VIEWLAYER_PT_workbench_layer_passes_data` (`:137`) carry the SAME
- * `bl_label` ("Data") and differ only by engine — Workbench shows three
- * passes where EEVEE shows seven, off the same `ViewLayer` datablock. Nothing
- * about the datablock could say which; `rna_context`'s `engine` does. The
- * Light panel (`:156`) is EEVEE-only for the same reason, and it also reads
- * `view_layer.eevee`, which the context door names beside the layer.
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS: `VIEWLAYER_PT_context_layer`
- * (`:51`, `bl_label = ""`) — the layer search template, the host's identity
- * row here; `VIEWLAYER_PT_layer_custom_props` (`:340`), IDProperties rather
- * than RNA; and the AOV / light-group add-remove operators, which are
- * editing rather than inspection. The two lists themselves are here as their
- * collections.
- *
- * It stands when: `buttons_context_path_view_layer` — the window's view layer
- * always resolves.
- */
+/** Blender’s View Layer Properties tab follows scripts/startup/bl_ui/properties_view_layer.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 

package/contributions/properties-world.inspector.tsx

@@ -1,48 +1,11 @@
-/**
- * BLENDER'S WORLD TAB, as a Properties section (WORK.md §Blender in the tab
- * is Blender, "Inspection parity", I2). Blender's own panels over the RNA
- * door, with the generic view beneath under "All properties".
- *
- * THE SPECIFICATION IS `scripts/startup/bl_ui/properties_world.py` at the
- * engine's pin — `classes` (`:266-278`) is the panel order, `bl_label` the
- * title, each `layout.prop(world, "x")` an entry. Blender's UI layer is never
- * run, ported or recorded.
- *
- * SURFACE AND VOLUME ARE A NODE TREE, AND THIS IS NOT THE NODE VIEW.
- * `EEVEE_WORLD_PT_surface` (`:109`) asks the world's node tree for its EEVEE
- * output node and draws that node's `Surface` input with
- * `template_node_view`; Volume (`:140`) is the same call on the `Volume`
- * input. Reading those values as a flat list means walking the tree back
- * through its links, which is I5's read-only node view (§Inspection parity,
- * I5) — half of it here would be a second, worse implementation of the same
- * walk. Exactly the reading the Material tab already made for its own Surface
- * panel. What stands in these two panels is what the WORLD datablock itself
- * holds: `use_nodes` and the `node_tree` pointer, which drills into the
- * generic view, plus the volume flag Blender's own panel reads off the world
- * (`use_eevee_finite_volume`, `:159`).
- *
- * THE TAB'S TONE IS THE SHADING RED. `UI_icons.hh:193` declares WORLD under
- * `DEF_ICON_SHADING`, the same group as Material — corrected from a guess
- * during I2's first landing, and the reason the scene group is four tabs
- * rather than six.
- *
- * WHAT THE TRANSCRIPTION DELIBERATELY DROPS: `WORLD_PT_context_world`
- * (`:24`, `bl_label = ""`) — the world ID template, the host's identity row
- * here; the `world.convert_volume_to_mesh` operator (`:165`); and
- * `WORLD_PT_custom_props` (`:99`), IDProperties rather than RNA.
- *
- * It stands when: `buttons_context_path_world` returns true from the scene
- * alone, so the tab stands even when the scene holds no world — and then
- * every panel here finds no datablock and none of them draw.
- */
+/** Blender’s World Properties tab follows scripts/startup/bl_ui/properties_world.py at the engine pin. Curated panels read the RNA context’s datablocks; the generic view remains under All properties. Match tab availability and engine-specific panels against the live context. */
 import { blenderPropertiesTabMatch, blenderPropertiesTabSection } from './blender-properties-tab';
 import type { BlenderCuratedPanel } from './blender-properties-view';
 
 /** `properties_world.py`, panel by panel. Line numbers are that file's. */
 const CURATED: readonly BlenderCuratedPanel[] = [
   {
-    // EEVEE_WORLD_PT_surface, :109 — see the header for why this is the
-    // world's own node properties rather than the shader's inputs.
+    // EEVEE_WORLD_PT_surface, :109. Read the world’s node properties; shader inputs belong to its node tree.
     title: 'Surface',
     engine: ['BLENDER_EEVEE'],
     properties: ['use_nodes', 'node_tree'],

package/contributions/shading.layout.ts

@@ -1,56 +1,4 @@
-/**
- * The SHADING workspace — Blender's own: the 3D viewport over the Shader
- * Editor, with the Outliner above the Properties editor on the right.
- *
- * THE PROPORTIONS ARE BLENDER'S, MEASURED THROUGH bpy on the engine in the
- * tab (2026-09-19), not eyeballed from a screenshot:
- * `bpy.data.workspaces['Shading'].screens[0].areas` answers, in a 1920-wide
- * window, PROPERTIES `x1579 y23 w339 h839`, OUTLINER `x1579 y865 w339 h189`,
- * VIEW_3D `x294 y540 w1282 h514`, NODE_EDITOR `x294 y23 w1282 h514`,
- * FILE_BROWSER `x2 y540 w289 h514` and IMAGE_EDITOR `x2 y23 w289 h514`.
- *
- * AND THE ARRANGEMENT IS A LIVE CAPTURE, not a hand-derived one
- * (`workspace-preset-layouts.ts`: "Shipped defaults are authored by arranging
- * live and snapshotting `toJSON`" — never hand-written JSON). Hand-deriving it
- * from Model's cost exactly what that rule exists to prevent: sizes authored
- * against Model's 928-px grid were applied to an 824-px container, the dock
- * measured `grid 1920×802 in a 1920×824 container` and warned that it was
- * "forcing one relayout" (measured live, 2026-09-19 — and measured again on
- * three Model/Sculpt switches with no Shading in them, which raised nothing,
- * so the warning was this arrangement's own). What ships is the settled grid,
- * with two sizes set back to the measurement: the vertical split to an exact
- * 50/50 of the grid's own height, and the right column to Model's 306/173/755,
- * which is the same column and already carries Blender's 0.177/0.184.
- *
- * Two readings out of that, and both are in `shading-arrangement.json`:
- * the right column is 339/1920 = 0.177 of the window with the Outliner taking
- * 189/1028 = 0.184 of it — the SAME column the Modeling workspace has, which
- * is why this arrangement is Model's with one change; and the centre column is
- * split EXACTLY 50/50, 514 over 514 of the 1031 px between the top bar and the
- * status bar. On the captured 928-px grid that is 464/464, which is the size
- * `volter:bottom-center` was already carrying at `"visible": false`.
- *
- * WHICH AREA THE SHADER EDITOR IS, AND WHAT IT IS MADE OF. Blender's node
- * editor is the area BELOW the viewport — and an AREA IS AN EDITOR GROUP
- * (orchestrator ruling 2026-09-19), not the bottom utility drawer. So Shading
- * declares it as an `areas` entry holding the `blender-node-editor.document`
- * contribution, the dock puts it in `volter:area:shader` below the centre at
- * Blender's own 50/50, and the frame's layout host puts the same document in
- * a second VS Code editor group. The drawer is `hidden` here, as it is in
- * Model: Blender's Shading screen has no utility strip.
- *
- * WHAT IS NOT REPRODUCED, named rather than silently dropped: Blender's
- * Shading workspace also carries a File Browser over an Image Editor in a
- * 289-px LEFT column (15.0 % of the window). Neither editor exists here yet —
- * the image/texture view is I5's Texture Paint unit and the asset browser is
- * a different surface — and §Editor chrome's rule is that a reserved panel
- * ships WITH its capability, never as empty chrome. The column arrives with
- * the editors that fill it.
- *
- * THE STRIP GROWS ONLY AS A VIEW LANDS (§Editor chrome; WORK.md I5). Shading
- * appears in the workspace strip because this contribution exists, and this
- * contribution exists because the node view does.
- */
+/** The Shading workspace places the Shader Editor below the 3D view in equal halves, with Outliner over Properties at right. The arrangement is a captured dock layout. File Browser and Image Editor areas are omitted until their editors exist. */
 
 import type { WorkspaceLayoutContribution } from '@volter/sdk/looks';
 import { BLENDER_REGIONS } from '../src/regions';
@@ -71,32 +19,9 @@ export const layout: WorkspaceLayoutContribution = {
     header: 'shown',
     shelf: 'shown',
     inspector: 'properties',
-    // THE SAME AS MODEL: no drawer. Blender's Shading screen has no fourth
-    // area beyond the viewport, the node editor and the right column, and the
-    // node editor is not a drawer utility — it is an AREA, which is an EDITOR
-    // GROUP (the ruling below). Leaving the drawer `shown` would paint an
-    // empty utility strip Blender's own screen does not have.
+    // Hide the utility drawer; the Shader Editor is a document area.
     drawer: 'hidden',
   },
-  // THE NODE EDITOR IS AN EDITOR GROUP BELOW THE MODEL DOCUMENT.
-  //
-  // RULED 2026-09-19 (orchestrator): "A Blender editor AREA is an editor
-  // group; the drawer holds utilities." Blender's Shading screen splits the
-  // centre TOP AND BOTTOM — VIEW_3D `x294 y540 w1282 h514` over NODE_EDITOR
-  // `x294 y23 w1282 h514`, measured through bpy on the engine — and both the
-  // dock and the Code-OSS frame have exactly that shape in editor groups. So
-  // the Shader Editor is a `workspace.document` this workspace opens into
-  // `volter:area:shader`, not a `workspace.utility` in the drawer.
-  //
-  // AND THAT IS WHAT RETIRED THE DRAWER RACE BY CONSTRUCTION. Switching to UV
-  // Editing kept opening the Shader Editor — and the cause was NOT the dock
-  // ordering the previous landing named: `uv-editing-arrangement.json`'s
-  // mechanical substitution had missed two of the seven occurrences (the
-  // panel record's `params.utilityId` and its `title`), so the leaf carrying
-  // the UV panel's id rendered the NODE editor and called itself "Shader
-  // Editor". A view that is not in the drawer cannot have that defect at all.
-  //
-  // THE RATIO IS BLENDER'S OWN: 514 of the 1028 px the centre column spans,
-  // an exact 0.5 to within the 1-px splitter.
+  // Open the Shader Editor in the bottom editor group at half the centre-column height.
   areas: [{ id: 'shader', document: 'blender-node-editor.document', place: 'below', ratio: 0.5 }],
 };