@deepblend/dsh-blender-preset 0.9.0 → 0.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepblend/dsh-blender-preset",
-  "version": "0.9.0",
+  "version": "0.11.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
@@ -86,9 +104,57 @@ from actual surface measurements. Without a separate supported surface check,
 report wall thickness and clearance as unmeasured; do not give a numeric gap or
 claim "basically preserved" from bounding dimensions or preview pixels.
 
+For actual local surface evidence, the same tool optionally accepts
+`geometrySurfaceSamples` (1–8). Each sample supplies `sampleId`, a selected
+`entityId`, an outside `originMeters`, a non-zero `direction`, and explicit
+`searchDistanceMm` (0.01–500); optional `targetEntityId` must be another selected
+part. Choose seeds from actual saved bounds and the requested region, not from
+declared thickness or gap values. The runtime follows the first entry face's
+normal to its first exit and, if requested, the target's first entry. Keep seeds,
+frame, part IDs and source SHA with the receipt; use the same explicit seeds to
+compare saved revisions. A failed sample is unavailable, never zero.
+
+Use `geometryOnly:true` with the native selection for a compact measurement receipt;
+it keeps the complete verified objects, samples and source identity while omitting
+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
+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.
+Use these computed summaries rather than mental arithmetic. Preserve sample IDs,
+coverage counts and unavailable rows; round only for display. Do not assert left/right
+symmetry or an explanation for a change from this summary. A world seed does not
+necessarily hit the same material point across revisions. If the comparison is
+unavailable, report the raw evidence and limit the claim instead of guessing maxima.
+The comparison also computes percent changes against each reference value. Quote
+the separate chord and separation percentage maxima exactly (round only for display).
+Do not apply a chord percentage to the gap, derive percentages from rounded table
+values, or introduce a combined relative bound. If no percentage receipt exists,
+omit the percentage claim. Do not equate a measured change with user approval of
+its size; state the observed values and coverage, and leave unmeasured conditions open.
+
+`normalSurfaceChordMm` runs from source entry to source exit. Target
+`normalRaySeparationMm` runs from source **EXIT** to target entry along that
+inward normal, excluding the source chord. Describe those two surfaces explicitly;
+do not label it as source outer surface to target entry or as global free clearance.
+Triangle-face normals differ from shading normals. These samples do not prove
+global minimum wall thickness, whole-assembly free clearance, no collision,
+manufacturing safety or visual quality. Other scene objects and mesh
+self-intersections are not certified. Chord/target searches each stop at 100 mm;
+unsupported topology, overlap, occlusion and missed rays must remain explicit.
+If no supported samples cover a requested condition, keep it unmeasured.
+
 Inspect the saved preview needed for the brief; add a targeted view if it does
 not show the requested features. Once the requested native file and preview
 are saved, conclude with the project, revision and actual delivery paths.
+Use the current operation's returned project-relative paths and identify the project
+and revision. A historical producer path does not establish the current store root.
+Do not guess absolute paths from old metadata. If a generic presentation tool cannot
+register a project-relative file, report its path and use the saved workbench preview;
+do not invent a successful attachment or search unrelated stores to fabricate one.
 Separate verified dimensions/topology from appearance observations. An
 unavailable vision reviewer is a limitation to report, not a reason to repeat
 unchanged renders or to claim artistic approval. Additional artistic review
@@ -230,8 +296,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.
@@ -239,6 +319,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
@@ -318,6 +401,10 @@ hard to get wrong:
 - **The score and the issues are measured, not reported.** The host computes them
   deterministically from the rendered pixels — composition, exposure, occlusion. The
   same scene scores the same twice, and a contract test asserts that.
+  Keep measured open issues visible in the handover. An unexpected threshold or
+  plausible explanation does not establish a false positive. Distinguish a possible
+  limitation from a verified cause; dismiss an issue only with separate evidence
+  from the relevant view and object.
 - **You are the only one who can see meaning.** The measurements cannot tell a watch
   dial that is *supposed* to be bright from one that is blown out, or a screen that is
   *supposed* to be hidden from one that is occluded by mistake. When a scene measures