@deepblend/dsh-blender-preset 0.10.0 → 0.12.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepblend/dsh-blender-preset",
-  "version": "0.10.0",
+  "version": "0.12.0",
   "type": "module",
   "description": "DeepBlend Agent-preset plane: ships the DeepBlend Studio agent presets and the deployer row that installs them into the DSH home.",
   "main": "lib/index.js",

package/presets/deepblend/agent.cordis.yml

@@ -86,6 +86,13 @@
       a SceneSpec document, every accepted change is an immutable revision, and you
       look at a scene with previews before you commit hours to a final render.
       Load the deepblend-studio skill before starting real work.
+      For an existing dimension edit, finish with only a compact factual receipt:
+      saved project/revisions, requested native overall spans, protected timing/appearance,
+      registered files, and remaining score findings or unmeasured conditions.
+      Do not add component tables or a retelling of movement groups. Do not claim all
+      part sizes stayed unchanged when generatorChangedEntityIds is nonempty.
+      Beauty images do not certify no floating, no interpenetration, topology or clearance;
+      do not add those claims to the handoff without explicit corresponding measurements.
     suffix: Your working directory is {{cwd}}.
 
 - id: agent-instructions

package/presets/deepblend/skills/deepblend-studio/SKILL.md

@@ -54,6 +54,24 @@ checkpoint and preview together. When a result says its image was not attached,
 the model has not seen those pixels; retain the saved artifact and report that
 limit. Additional views still need to show the features required by the brief.
 
+For an existing assembly dimension edit, the final handoff must be a compact receipt:
+- project/current revision and the retained original;
+- only the requested overall dimensions, from the saved native span receipt;
+- saved custom keyframe timing and protected cameras when requested;
+- the actual registered native file and primary/back images;
+- the remaining score findings and unmeasured global conditions.
+Do not add component tables, inferred margins, or a prose retelling of movement groups.
+Do not infer no floating, no interpenetration, topology or clearance from beauty previews.
+Without corresponding measurements those conditions remain unassessed, even if a view looks good.
+The save receipt and scene document contain the detailed part changes for inspection.
+The save receipt's generatorChangedEntityIds explicitly lists structurally resized parts.
+When it is nonempty, never say "no part size changed" or "all part geometry unchanged".
+Preservation applies to the original revision and independent hand edits, not to the
+structural generator dimensions requested to change.
+Structural shells, openings, baffles and panels grow: the recipe's fixed-part wording is
+not a claim that those structural dimensions stay unchanged. If the user explicitly asks
+for a detailed component report, quote actual receipt fields individually and retain gaps.
+
 For a later dimensional change, read `blender_recipe_parameters`, then save
 only the changed parameter IDs with the current base revision and preview
 enabled. This preserves independent appearance, the original revision and
@@ -101,8 +119,22 @@ it keeps the complete verified objects, samples and source identity while omitti
 the scene catalogue. Read the scene separately when selecting parts or seeds.
 It cannot be combined with `full:true`.
 
-For before/after comparisons, supply `geometryCompareRevision` with the old saved
-revision and the same explicit samples on the current read. The tool verifies both
+For saved native size/movement comparisons, use `geometryCompareRevision` with the
+old saved revision, the selected `geometryEntityIds`, and explicit `geometryFrame`.
+Without surface samples, `geometryComparison.objects` gives current-minus-reference
+world-axis span and object-origin changes. Use these computed values instead of
+subtracting rounded displays. This does not identify their cause or certify contact.
+
+For explicit attachment endpoint origins, add `geometryAssemblyPairs` (1–8 pairs),
+each with a distinct `pairId`, selected `entityId` and different selected
+`anchorEntityId`. `geometryAssemblyOrigins` joins native OBJECT ORIGINS in world XYZ:
+entity minus anchor. With a reference revision, `geometryComparison.assemblyOriginComparison`
+also returns the offset changes. These are not surface protrusion, seating depth,
+contact or clearance. World offsets change with rotation; do not call them intrinsic
+or anchor-local dimensions. Preserve unavailable endpoints without inventing zero.
+
+For local surface before/after comparisons, supply `geometryCompareRevision` with the
+old saved revision and the same explicit samples on the current read. The tool verifies both
 sources and computes `geometryComparison.samples` changes (current minus reference)
 and maxima over **all** comparable requested samples. Chord-only samples still count
 in the chord maximum. Unavailable pairs are omitted from numeric changes, never zero.
@@ -278,8 +310,22 @@ the current revision and repeat the affected views with the same settings.
    the first revision is `r0001`. If no recipe fits, use a supplied scene or the minimal scaffold route.
    For an existing assembly, use **`blender_recipe_parameters`** with `action:read` first.
    Use the returned revision, numeric parameter IDs and allowed ranges in `action:save`.
+   Read/save receipts include linkedAnimationTracks from the selected saved SceneSpec. Use its
+   actual keyframe frames and values to verify custom timing and travel; recipe defaults, shot
+   prose and the observation/render frame are not the current animation keyframe list.
    This creates one revision in the same project, using ordinary patches internally; it preserves
    independent materials, bevels, photography and history. Do not recreate the project to resize it.
+   Save receipts include placementChanges: groups of actual saved object-origin deltas in mm,
+   with entity IDs and from/to revision. Quote the group containing each named part; front
+   controls and rear connectors may move in opposite directions. These SceneSpec deltas
+   are not native surface distances or clearances.
+   A part following an assembly edge can change its offset from the cabinet centre. Do not
+   describe all relative offsets as invariant. A world-coordinate endpoint is not an exposure
+   or clearance distance. If no returned field defines a relationship measurement, leave it
+   unmeasured instead of deriving an attachment distance or margin in the final answer.
+   Pinned speaker 2.0/2.1 assemblies can retain a complete manual translation, including the
+   button rest anchor, while resizing. Partial moves and rotated dimension-controlled parts
+   remain conflicts. Keep custom photography; verify its framing after the size change.
    Controlled geometry conflicts require resolving the named parts before saving. Old recipes
    without geometry controls return available:false. Use a fresh idempotencyKey for each new
    intent, including edits after restoring history; reuse it only for the same retry.
@@ -287,6 +333,9 @@ the current revision and repeat the affected views with the same settings.
    Declare its returned asset descriptor in a patch, then bind its intended use:
    a model instance, material map, environment, or review reference. See the model
    workflow below and the reference image guide above.
+   `blender_project_get.projectDirectory` is the active project directory, including after
+   relocation or restore. Combine it with returned project-relative artifact paths for file
+   registration. Do not guess a producer's old absolute directory from historical metadata.
 4. **`blender_scene_get`** — read before writing. Patching without reading is how a
    stale `baseRevision` produces a refusal you then have to diagnose.
 5. **`blender_scene_patch`** — submit ordinary scene edits as bounded operations. There is no free-form