@deepblend/dsh-blender-contracts 0.2.14 → 0.2.15

package/lib/scene-spec.js

@@ -185,6 +185,10 @@ export function validateSceneSpec(spec) {
   // ---- uniqueness ---------------------------------------------------------
   const collections = [
     ['assets', document.assets ?? []],
+    // ARMATURES ARE A COLLECTION LIKE ANY OTHER: they have ids, they can collide, and other things
+    // reference them by id. Leaving them out of this list meant the cross-reference check had nothing to
+    // look in, so a skinned entity was reported as naming a rig that does not exist — its own rig.
+    ['armatures', document.armatures ?? []],
     ['materials', document.materials ?? []],
     ['entities', document.entities],
     ['lights', document.lights ?? []],
@@ -279,6 +283,11 @@ export function validateSceneSpec(spec) {
       })
     }
     requiresId('materials', entity.materialId, `${at}.materialId`, 'material')
+    // AND THE RIG IT IS SKINNED TO. MEASURED: this check was missing at first, and the contract suite
+    // caught it — the schema can say `armatureId` is a string, but only a cross-reference can say it
+    // names something the scene declares. An entity skinned to an armature nobody declares would render
+    // as a static object while the file says it is rigged, which is the failure this code exists for.
+    requiresId('armatures', entity.armatureId, `${at}.armatureId`, 'armature')
     if (entity.type !== 'empty' && entity.materialId === undefined) {
       notices.push({
         severity: 'notice', code: 'SCENE_ENTITY_MATERIAL_DEFAULTED', path: at,

package/lib/schemas/scene-spec.schema.json

@@ -31,7 +31,7 @@
       "items": {
         "$ref": "#/$defs/armature"
       },
-      "description": "Armatures this scene declares (SPEC \u00a720 M6, character animation). Each is one skeleton, created as its own object and named `<prefix><id>` like every other product object. WHAT THIS SLICE DOES NOT DO YET: bind a mesh to a bone (skinning) and animate a bone \u2014 those are the next two slices, and a rig that exists but drives nothing is honest about being exactly that."
+      "description": "Armatures this scene declares (SPEC \u00a720 M6, character animation). Each is one skeleton, created as its own object and named `<prefix><id>` like every other product object. WHAT THIS DOES NOT DO YET: animate a bone. Entities ARE skinned to an armature now (`entity.armatureId`, with Blender's automatic weights), so a rig drives its mesh \u2014 but nothing moves the rig until animation tracks can target bones, which is the next slice."
     },
     "materials": {
       "type": "array",
@@ -473,6 +473,10 @@
           "type": "string",
           "description": "Required when type is asset-instance."
         },
+        "armatureId": {
+          "type": "string",
+          "description": "The armature this entity is skinned to, named by `armatures[].id`. The compiler binds the mesh with Blender's own automatic weights, so the entity follows the bones with no weight table to write by hand. A name the scene does not declare is refused rather than ignored, because an entity that is silently unskinned renders as a static object while the file says it is rigged."
+        },
         "generator": {
           "$ref": "#/$defs/generator"
         },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepblend/dsh-blender-contracts",
-  "version": "0.2.14",
+  "version": "0.2.15",
   "type": "module",
   "description": "DeepBlend Studio Service Definition, protocol contracts, and stable error codes.",
   "main": "lib/index.js",