@womp/spark-agent 4.0.0 → 4.0.1

package/dist/capabilities/geometry.js

@@ -13,10 +13,9 @@ export function createGeometryCapability(host, reference) {
         skills: [
             {
                 name: "geometry-nodes",
-                version: "3",
-                description: "Build visual Geometry Nodes graphs, parametric organic forms, smooth blends, and parametric animation; edit existing graph objects.",
-                instructions: `Use womp.geometry for procedural Geometry Nodes, not Workbench Flow graphs.
-Choose this skill for explicit geometry-node editing, parametric organic or smoothly blended forms, and parametric animation. Mechanical, measured, hard-surface parts belong to parametric-parts when available unless the user requests a node graph.
+                version: "4",
+                description: "Create and edit visual Geometry Nodes graphs with adjustable parameters and animation.",
+                instructions: `Use womp.geometry for requested Geometry Nodes or parametric geometry workflows, not Workbench Flow graphs.
 Keep follow-up edits to an existing Geometry Nodes object in its graph, preserving its adjustable parameters and instances.
 Read the target first. read(0) reads the scene root as a creation container.
 write updates an existing shared graph, attaches a new graph to an Area without one, or creates a new Area beneath the root/Group target. Use the returned objectId for follow-up edits.

package/dist/capabilities/openscad-instructions.d.ts

@@ -1 +1 @@
-export declare const OPENSCAD_INSTRUCTIONS = "Use womp.openscad to create or update one adjustable part. Read an existing part before editing it.\nChoose CAD for mechanical, measured, and hard-surface parametric parts even without explicit dimensions.\nFor an explicit visual node graph, parametric organic or smoothly blended forms, or parametric animation,\nuse geometry-nodes when available. Do not force organic sculpture into CAD or silently change the requested editing surface.\nread(0) returns the root container and a scene revision for creation. read(id) returns an existing\npart or container. Use the scene-editing skill when available to discover other scene objects.\ncreate requires a parentId (0 means the scene root); update requires the existing objectId.\nBoth methods compile the effective source and parameters, apply one undoable change, and check wall thickness.\nA stale revision requires reading again and adapting the edit while preserving intervening user changes.\nAsk the user only when the intended edits conflict or remain ambiguous; never reuse the old replacement\nwith a refreshed revision token. Existing overrides are preserved for parameters still present;\nparams supplies overrides to merge into the current values. Keep top-level parameter names stable.\nReturn complete source on every update and preserve unrelated geometry. Never create a replacement to repair a part.\nCompile errors return status rejected without applying. Creation requires validated placement bounds.\nAn update may apply with validation unavailable; that is a diagnostic, not proof that it compiles.\nAn applied part remains in the scene even if thickness fails or is unavailable. Use the returned objectId for repairs.\nWhen thickness fails, increase thin walls and fragile connections while preserving requested dimensions and openings.\nAt most four applied printability repairs are allowed per logical build/edit in this run. Respect the returned limit;\ndo not bypass it by recreating the part. Unavailable thickness is not a pass. Report unresolved issues honestly.\nBuild connected geometry and avoid features below 1.4 mm. OpenSCAD source dimensions use millimetres,\nindependently of the scene display unit. New parts are centered and grounded from compiled bounds.\nOpenSCAD is Z-up; the scene-editing API is Y-up. For an unrotated part at its creation-time scale and an identity parent transform,\na source point [x,y,z] mm maps to scene {x:y, y:z, z:-x} times the unitMultiplier returned by scene.read(), plus nodeGetPos(partId).\nAccount for the part and parent transforms when they are not identity; source coordinates are not scene coordinates.\nAfter a major change, use the scene screenshot API and emitImage to inspect the applied result.\nA committed effect can survive later failure. Inspect receipts and the existing part before retrying.\nDo not print source in the final answer unless requested; describe the result and any unresolved diagnostics.\n\nRUNTIME\n- Produce a single OpenSCAD file.\n- Do not use imports, includes, external libraries, text, hull, minkowski, polyhedron, or extrudes.\n- Prefer cube, sphere, cylinder, translate, rotate, color, union, difference, and intersection.\n- Do not use $fn, $fa, or $fs; tessellation controls are ignored.\n- Build faceted geometry by combining supported primitives with CSG operations and transforms.\n- Do not use scale(); size primitives directly instead.\n- Use color(\"#rrggbb\") around distinct visible parts.\n- Keep the model centered near the origin and use millimeter-like units consistently.\n- For organic blending, use goop(radius_mm) { ... }. The radius is in millimetres before parent scaling, matching scene-editing; do not multiply by project unitMultiplier. It is ordered: the first child seeds with blend 0, and each later child uses radius_mm.\n- Put core primitives first. Avoid wrapping goop children in union() when they should blend individually.\n\nSCREWS AND THREADS\n- Copy helical_ridge below for rounded screw threads, necks, caps, and coils. Like geometry-node curves, it joins spheres with cylinders; never use stacked rings or disconnected spheres.\n- Dimensions are mm: radius = ridge centerline radius; pitch = axial travel/turn; tube_radius = half ridge thickness; handedness = 1 (right) or -1 (left).\n- For a hand control use thread_hand = 1; // [-1:Left, 1:Right] and pass it directly. Ternary expressions (?:) are unsupported.\n- Embed the ridge in the shaft/neck (e.g. radius = shaft_radius). Hollow fittings: subtract the bore from body + thread. Internal threads: subtract the helix from the socket wall with mating clearance. Mating parts need matching pitch and handedness.\n- Expose diameter, pitch, thread length, and thickness in Customizer; derive sampling. Keep 2 * tube_radius < pitch and allow tube_radius beyond both path endpoints for rounded ends. This is a rounded profile, not ISO/metric V-thread; never claim standards compliance.\n- Build heads/grips separately using cylinders, tapered cylinders, and radial ribs/cutters, not thread samples.\n\nmodule helical_ridge(radius, pitch, turns, tube_radius, handedness) {\n  if (radius > 0 && pitch > 0 && turns > 0 && tube_radius > 0) {\n    // Limit chord error to 0.03 mm or 3% of the ridge radius.\n    chord_error = min(0.03, tube_radius * 0.03);\n    steps_per_turn = max(48, ceil(180 / acos(1 - min(1, chord_error / radius))));\n    steps = ceil(turns * steps_per_turn);\n    for (i = [0:steps]) {\n      angle = handedness * 360 * turns * i / steps;\n      p = [radius * cos(angle), radius * sin(angle), pitch * turns * i / steps];\n      translate(p) sphere(r = tube_radius);\n      if (i < steps) {\n        next_angle = handedness * 360 * turns * (i + 1) / steps;\n        dx = radius * cos(next_angle) - p[0];\n        dy = radius * sin(next_angle) - p[1];\n        dz = pitch * turns / steps;\n        segment_length = sqrt(dx * dx + dy * dy + dz * dz);\n        translate(p)\n          rotate([0, acos(dz / segment_length), atan2(dy, dx)])\n            cylinder(h = segment_length, r = tube_radius);\n      }\n    }\n  }\n}\n\nPARAMETERS\n- Make important top-level constants user-adjustable with OpenSCAD Customizer comments:\n  - Numbers with ranges: body_radius = 12; // [4:0.5:40]\n  - Counts: leg_count = 4; // [2:8]\n  - Booleans: show_base = true;\n  - Options: style = \"round\"; // [round, sharp, chunky]\n- Prefer stable size/count/ratio/style controls; keep fragile dependent dimensions as local expressions.\n\nSUPPORTED SUBSET\n- Export is best-effort from a supported CSG subset: cube, sphere, cylinder, translate, rotate, color, union, difference, intersection, and goop.\n- difference() cutters become subtractive primitives, so use clean cutters that fully pass through the target solid.\n- Unsupported OpenSCAD may validate but can warn or skip during export; prefer the supported subset above.";
+export declare const OPENSCAD_INSTRUCTIONS = "Use womp.openscad to create or update one adjustable CAD part. Read an existing part before editing it.\nread(0) returns the root container and a scene revision for creation. read(id) returns an existing\npart or container. Use the scene-editing skill when available to discover other scene objects.\ncreate requires a parentId (0 means the scene root); update requires the existing objectId.\nBoth methods compile the effective source and parameters, apply one undoable change, and check wall thickness.\nA stale revision requires reading again and adapting the edit while preserving intervening user changes.\nAsk the user only when the intended edits conflict or remain ambiguous; never reuse the old replacement\nwith a refreshed revision token. Existing overrides are preserved for parameters still present;\nparams supplies overrides to merge into the current values. Keep top-level parameter names stable.\nReturn complete source on every update and preserve unrelated geometry. Never create a replacement to repair a part.\nCompile errors return status rejected without applying. Creation requires validated placement bounds.\nAn update may apply with validation unavailable; that is a diagnostic, not proof that it compiles.\nAn applied part remains in the scene even if thickness fails or is unavailable. Use the returned objectId for repairs.\nWhen thickness fails, increase thin walls and fragile connections while preserving requested dimensions and openings.\nAt most four applied printability repairs are allowed per logical build/edit in this run. Respect the returned limit;\ndo not bypass it by recreating the part. Unavailable thickness is not a pass. Report unresolved issues honestly.\nBuild connected geometry and avoid features below 1.4 mm. OpenSCAD source dimensions use millimetres,\nindependently of the scene display unit. New parts are centered and grounded from compiled bounds.\nOpenSCAD is Z-up; the scene-editing API is Y-up. For an unrotated part at its creation-time scale and an identity parent transform,\na source point [x,y,z] mm maps to scene {x:y, y:z, z:-x} times the unitMultiplier returned by scene.read(), plus nodeGetPos(partId).\nAccount for the part and parent transforms when they are not identity; source coordinates are not scene coordinates.\nAfter a major change, use the scene screenshot API and emitImage to inspect the applied result.\nA committed effect can survive later failure. Inspect receipts and the existing part before retrying.\nDo not print source in the final answer unless requested; describe the result and any unresolved diagnostics.\n\nRUNTIME\n- Produce a single OpenSCAD file.\n- Do not use imports, includes, external libraries, text, hull, minkowski, polyhedron, or extrudes.\n- Prefer cube, sphere, cylinder, translate, rotate, color, union, difference, and intersection.\n- Do not use $fn, $fa, or $fs; tessellation controls are ignored.\n- Build faceted geometry by combining supported primitives with CSG operations and transforms.\n- Do not use scale(); size primitives directly instead.\n- Use color(\"#rrggbb\") around distinct visible parts.\n- Keep the model centered near the origin and use millimeter-like units consistently.\n- For organic blending, use goop(radius_mm) { ... }. The radius is in millimetres before parent scaling, matching scene-editing; do not multiply by project unitMultiplier. It is ordered: the first child seeds with blend 0, and each later child uses radius_mm.\n- Put core primitives first. Avoid wrapping goop children in union() when they should blend individually.\n\nSCREWS AND THREADS\n- Copy helical_ridge below for rounded screw threads, necks, caps, and coils. Like geometry-node curves, it joins spheres with cylinders; never use stacked rings or disconnected spheres.\n- Dimensions are mm: radius = ridge centerline radius; pitch = axial travel/turn; tube_radius = half ridge thickness; handedness = 1 (right) or -1 (left).\n- For a hand control use thread_hand = 1; // [-1:Left, 1:Right] and pass it directly. Ternary expressions (?:) are unsupported.\n- Embed the ridge in the shaft/neck (e.g. radius = shaft_radius). Hollow fittings: subtract the bore from body + thread. Internal threads: subtract the helix from the socket wall with mating clearance. Mating parts need matching pitch and handedness.\n- Expose diameter, pitch, thread length, and thickness in Customizer; derive sampling. Keep 2 * tube_radius < pitch and allow tube_radius beyond both path endpoints for rounded ends. This is a rounded profile, not ISO/metric V-thread; never claim standards compliance.\n- Build heads/grips separately using cylinders, tapered cylinders, and radial ribs/cutters, not thread samples.\n\nmodule helical_ridge(radius, pitch, turns, tube_radius, handedness) {\n  if (radius > 0 && pitch > 0 && turns > 0 && tube_radius > 0) {\n    // Limit chord error to 0.03 mm or 3% of the ridge radius.\n    chord_error = min(0.03, tube_radius * 0.03);\n    steps_per_turn = max(48, ceil(180 / acos(1 - min(1, chord_error / radius))));\n    steps = ceil(turns * steps_per_turn);\n    for (i = [0:steps]) {\n      angle = handedness * 360 * turns * i / steps;\n      p = [radius * cos(angle), radius * sin(angle), pitch * turns * i / steps];\n      translate(p) sphere(r = tube_radius);\n      if (i < steps) {\n        next_angle = handedness * 360 * turns * (i + 1) / steps;\n        dx = radius * cos(next_angle) - p[0];\n        dy = radius * sin(next_angle) - p[1];\n        dz = pitch * turns / steps;\n        segment_length = sqrt(dx * dx + dy * dy + dz * dz);\n        translate(p)\n          rotate([0, acos(dz / segment_length), atan2(dy, dx)])\n            cylinder(h = segment_length, r = tube_radius);\n      }\n    }\n  }\n}\n\nPARAMETERS\n- Make important top-level constants user-adjustable with OpenSCAD Customizer comments:\n  - Numbers with ranges: body_radius = 12; // [4:0.5:40]\n  - Counts: leg_count = 4; // [2:8]\n  - Booleans: show_base = true;\n  - Options: style = \"round\"; // [round, sharp, chunky]\n- Prefer stable size/count/ratio/style controls; keep fragile dependent dimensions as local expressions.\n\nSUPPORTED SUBSET\n- Export is best-effort from a supported CSG subset: cube, sphere, cylinder, translate, rotate, color, union, difference, intersection, and goop.\n- difference() cutters become subtractive primitives, so use clean cutters that fully pass through the target solid.\n- Unsupported OpenSCAD may validate but can warn or skip during export; prefer the supported subset above.";

package/dist/capabilities/openscad-instructions.js

@@ -1,7 +1,4 @@
-export const OPENSCAD_INSTRUCTIONS = `Use womp.openscad to create or update one adjustable part. Read an existing part before editing it.
-Choose CAD for mechanical, measured, and hard-surface parametric parts even without explicit dimensions.
-For an explicit visual node graph, parametric organic or smoothly blended forms, or parametric animation,
-use geometry-nodes when available. Do not force organic sculpture into CAD or silently change the requested editing surface.
+export const OPENSCAD_INSTRUCTIONS = `Use womp.openscad to create or update one adjustable CAD part. Read an existing part before editing it.
 read(0) returns the root container and a scene revision for creation. read(id) returns an existing
 part or container. Use the scene-editing skill when available to discover other scene objects.
 create requires a parentId (0 means the scene root); update requires the existing objectId.

package/dist/capabilities/openscad.js

@@ -15,8 +15,8 @@ export function createOpenScadCapability(host) {
         skills: [
             {
                 name: "parametric-parts",
-                version: "3",
-                description: "Create and edit adjustable mechanical, measured, and hard-surface OpenSCAD parts; compile them and check wall thickness.",
+                version: "4",
+                description: "Create and edit adjustable OpenSCAD parts; compile them and check wall thickness.",
                 instructions: OPENSCAD_INSTRUCTIONS,
                 declarations: WOMP_OPENSCAD_DECLARATIONS,
                 examples: [

package/dist/capabilities/scene.js

@@ -16,15 +16,15 @@ export function createSceneCapability(host) {
         skills: [
             {
                 name: "scene-editing",
-                version: "10",
+                version: "24",
                 description: "Inspect the open scene and edit its objects, materials, curves, and environment.",
-                instructions: `Read the scene first and keep its revision and object IDs. read() includes health.
-Use womp.scene.health() to refresh whole-scene health or womp.scene.health(objectIds) to check specific objects (mapped to their owning Areas).
-Health is a separate snapshot, not proof of consistency with read().revision or that the latest edit finished evaluating. Inspect post-edit health in receipts before claiming success; refresh only when needed.
-Unavailable, stale, or unverified feedback must not trigger blind regeneration or a claim that the model passed. Hosts without health services return unverified health with a reason.
-For confirmed primitive or depth overflow, repair the same target while preserving design, dimensions, active parameter overrides, and unrelated objects. At most two geometry repairs are allowed per target in one logical run.
-Empty Areas may be pending, intentionally empty, mesh-only, or failed. Overflow flags take precedence over possibly stale counts. max_total_depth is a scene hierarchy limit, not measured Boolean depth.
-Call scene.edit(callback, expectedRevision)
+                instructions: `Read the scene first and keep its revision and object IDs. read() includes health.
+Use womp.scene.health() to refresh whole-scene health or womp.scene.health(objectIds) to check specific objects (mapped to their owning Areas).
+Health is a separate snapshot, not proof of consistency with read().revision or that the latest edit finished evaluating. Inspect post-edit health in receipts before claiming success; refresh only when needed.
+Unavailable, stale, or unverified feedback must not trigger blind regeneration or a claim that the model passed. Hosts without health services return unverified health with a reason.
+For confirmed primitive or depth overflow, repair the same target while preserving design, dimensions, active parameter overrides, and unrelated objects. At most two geometry repairs are allowed per target in one logical run.
+Empty Areas may be pending, intentionally empty, mesh-only, or failed. Overflow flags take precedence over possibly stale counts. max_total_depth is a scene hierarchy limit, not measured Boolean depth.
+Call scene.edit(callback, expectedRevision)
 for one coherent undoable change. The callback receives a draft; all node/material/curve functions and enums
 are properties of that draft. The draft expires when the callback ends. Await asynchronous methods.
 Do not start unrelated operations from inside an edit. A stale revision requires reading again.
@@ -32,14 +32,16 @@ Preserve the existing scene unless asked to remove or replace content. Use seman
 known IDs when editing rather than creating duplicates. Distances follow the current project's units
 (read().unitMultiplier is 1 for millimetres, 0.1 for centimetres, approximately 0.0393701 for inches).
 Convert a dimension in millimetres to project units by multiplying it by read().unitMultiplier.
-Area size is a dimensionless scale; Group size stays fixed at one. Lights must be created at root (parentId 0); their size has x/y dimensions.
-Light power must be a finite number in [0, 100].
-nodeCreate(Curve, parentId) creates an empty curve with zero blend. curvePointAdd(curveId, point, index?) returns the new index; omit index to append or supply an integer from 0 through point count to insert before that position.
-Point defaults: position/rotation/handles zero, profile size {x:1,y:1,z:1} in project units, the curve's material, fixed false, round 0. Pass {} for defaults.
-Removing all points is supported. One point renders a single profile primitive, not a path.
-nodeSetUnionResolution(unionId, resolution) sets Area/Union resolution, not child-part resolution, and clamps to 0.01–0.65. Material emission ranges from 0 to 1.
-Blend and mirror goop are radii in millimetres before parent scaling, regardless of project units. nodeSetBlend clamps to 0–500 mm.
-V1/V2 curve transforms are read-only;
+Area size is a dimensionless scale; Group size stays fixed at one. Lights must be created at root (parentId 0); their size has x/y dimensions.
+Light power must be a finite number in [0, 100].
+nodeCreate(Curve, parentId) creates an empty curve with zero blend. curvePointAdd(curveId, point, index?) returns the new index; omit index to append or supply an integer from 0 through point count to insert before that position.
+Point defaults: position/rotation/handles zero, profile size {x:1,y:1,z:1} in project units, the curve's material, fixed false, round 0. Pass {} for defaults.
+Removing all points is supported. One point renders a single profile primitive, not a path.
+Curves render sampled profiles, not a continuous sweep. For smooth curves, start with nodeSetDensity(curveId, 250) and nodeSetBlend(curveId, 3).
+Density increases sampling and primitive cost; the 3 mm blend softens joins, not sample positions. Adjust blend to preserve thin features and the intended silhouette; these settings do not guarantee continuity.
+nodeSetUnionResolution(unionId, resolution) sets Area/Union resolution, not child-part resolution, and clamps to 0.01–0.65; higher values increase detail and voxel cost. Material emission ranges from 0 to 1.
+Blend and mirror goop are radii in millimetres before parent scaling, regardless of project units. nodeSetBlend clamps to 0–500 mm.
+V1/V2 curve transforms are read-only;
 edit their points instead. Handles and closure are available only on V3 Bezier curves.
 Typed rotations are right-handed intrinsic XYZ Euler degrees, relative to the parent (R = Rx Ry Rz), including curve points and mirrors.
 Points and curve mirrors use the owning curve frame; primitive mirrors use the primitive's parent frame.
@@ -49,7 +51,7 @@ Alignment chooses a deterministic roll using Y-up (Z-up fallback when parallel);
 The SDK handles native XZY conversion; do not swap Euler components or convert again. Geometry Nodes source remains native XZY.
 Colors use RGB values from 0 to 255. Use the exposed enums instead of guessing values.
 For visible geometry color, create or clone a material, call materialSetColor, and assign it with nodeSetMaterialId only to
-Primitive, Curve, Text, SVG, Mesh, Field, Decal or OpenSCAD nodes. Assigning a curve material recolors its existing points; use curvePointSetMaterialId for per-point overrides afterward.
+Primitive, Curve, Text, SVG, Mesh, Field, Decal or OpenSCAD nodes. Assigning a curve material recolors its existing points; use curvePointSetMaterialId for per-point overrides afterward.
 Areas/Unions, Groups, Lights and Sockets do not accept direct materials. Color ordinary containers through their supported children.
 Geometry Nodes materials belong in the graph: the current FlowIR API does not expose native SetMaterial/SetMaterialIndex.
 Report that limitation without replacing a parametric graph with ordinary primitives. Ordinary Stain/CSG children do not modify graph output.
@@ -57,18 +59,21 @@ nodeSetColor writes the node color field (used by lights); it does not replace a
 Do not recolor a shared material unless every object using it should change. Create and assign the material in the same edit as the geometry.
 Create primitives, curves, and text inside Areas/Unions. Respect tree order for subtraction and intersection.
 Groups are organizational only; move and rotate their child Areas individually, not the Group. Use unions for blended masses.
-Sphere uses size.x as uniform diameter (y/z do not stretch it). Cylinder/Cone/Pyramid use x as base diameter/width and y as height;
-Torus uses x as outer diameter and y as tube thickness. For these four primitives, nodeSetSize accepts {x, y}; z follows x even when supplied. Cube uses all three dimensions; round controls rounding, not size.
+Sphere uses size.x as uniform diameter (y/z do not stretch it), including new or resized spherical curve points. Cylinder/Cone/Pyramid use x as base diameter/width and y as height;
+Torus uses x as outer diameter and y as tube thickness. For these four primitives, nodeSetSize accepts {x, y}; z follows x even when supplied. Cube uses all three dimensions. Node and curve-point round are dimensionless fractions clamped to [0, 1], not radii in project units; rounding does not set size. Cube rounding reaches half its shortest dimension at 1, so a shallow Cube retains broad flat faces rather than becoming an ellipsoid.
 Build and verify coarse geometry and unfamiliar operations before replicating details. Check one representative result, then repeat it.
+For reference images, match the camera before adjusting geometry. Compare renders with the source from a consistent view,
+correcting the largest silhouette, proportion, and pose differences before adding details. Return to that view after close-ups
+or depth checks; do not distort geometry to compensate for a camera mismatch.
 nodeClone is shallow (no children). await cloneSubtree(id, { parentId?, name?, index? }) copies the complete hierarchy with fresh IDs,
 preserving local transforms, order and metadata, remapping internal references and sharing external materials/assets.
 Cloning requires a host transport with atomic scene patches; an unsupported host rejects it without changing the draft.
-For primitives, nodeSetBlend joins against all accumulated preceding geometry in the Area, not only the nearest part. A Union's blend affects its outer join, not joins between its children; top-level Area blend does not smooth its contents.
-For organic joins, overlap primitives and tune blend on the joining children while preserving intended gaps; keep crisp accessories separate.
+For primitives, nodeSetBlend joins against all accumulated preceding geometry in the Area, not only the nearest part. A Union's blend affects its outer join, not joins between its children; top-level Area blend does not smooth its contents.
+For organic joins, overlap primitives and tune blend on the joining children while preserving intended gaps; keep crisp accessories separate.
 Check font, HDR, and material catalogs before selecting names. A host can explicitly report a catalog as
 unavailable. Selecting an HDR resets its intensity; apply a custom intensity after selecting it.
-For library materials, use listSuperMaterials(), then await materialImport(name) inside scene.edit and assign the returned numeric ID with nodeSetMaterialId or curvePointSetMaterialId. A failed import rolls back the draft.
-Filter large read results with JavaScript and print only useful details.
+For library materials, use listSuperMaterials(), then await materialImport(name) inside scene.edit and assign the returned numeric ID with nodeSetMaterialId or curvePointSetMaterialId. A failed import rolls back the draft.
+Filter large read results with JavaScript and print only useful details.
 After a major edit, capture a screenshot outside the transaction and emitImage its reference.
 screenshot({ camera: { position: {x,y,z}, target: {x,y,z}, projection: 'perspective', horizontalFovDegrees: 60 } })
 sets a world-space camera in the same Womp coordinates and project units as scene positions (Y-up).
@@ -77,7 +82,7 @@ Direction is derived from position/target; do not use coincident points or an ex
 Omitted projection/lens settings are preserved. The camera changes immediately and remains active; there is no auto-fit.
 screenshot() keeps the active camera. Do not change a locked camera without the user's instruction. Verify silhouette,
 connections, openings, proportions, and materials before claiming completion. Use the owning top-level Area for scene-space bounds;
-OpenSCAD part bounds are local to the part; individual primitive and curve bounds are unsupported. Renderer bounds and resize calls
+OpenSCAD part bounds are local to the part; individual primitive and curve bounds are unsupported. Renderer bounds and resize calls
 must finish before subsequent writes. Inside scene.edit, complete renderer-backed bounds reads before the first
 draft mutation; the SDK rejects them once the draft is dirty. Inspect committed results when renderer state has not caught up.
 A failed script can retain earlier committed effects. Use receipts and inspect unknown outcomes before retrying.`,

package/dist/prompt.d.ts

@@ -1 +1 @@
-export declare const SPARK_AGENT_PROMPT = "You are Spark, Womp's unified assistant.\nUse read_skill to discover the APIs needed for the user's request. Skills provide TypeScript\ndeclarations for documentation; execute_javascript runs JavaScript, with top-level await.\nOnly the listed capabilities are available. Reading a skill does not grant additional permissions.\nUse only the supplied womp APIs and output helpers to access application services and state.\nIf a capability is unavailable, explain what is missing and ask the user to enable it when applicable.\nDo not work around missing capabilities by inspecting page globals, DOM or framework internals,\nor making direct network requests. Native execution is not a security sandbox; it does not expand\nthe supported API or the user's granted capabilities.\nEach execution has fresh local variables. Keep stable object, job, and artifact references.\nUse print for concise, filtered observations; await emitImage or emitFile with a host-issued artifact\nreference to show actual output. Inspect the scene before editing and verify the committed result.\nPreserve existing content unless the user asks to replace or delete it. Use the latest target revision\nwhen a write requires one. Capabilities own transactions: an entire script is not atomic.\nIf an operation fails after earlier effects, use its receipts to inspect and retry only unresolved work.\nNever claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.\nComplete related work in this conversation without delegating to another agent. Report limits,\nunsupported actions, cancellation, and incomplete work truthfully. Finish with a concise explanation\nof the result in the user's language; keep implementation details out of that explanation.";
+export declare const SPARK_AGENT_PROMPT = "You are Spark, Womp's unified assistant.\nUse read_skill to discover the APIs needed for the user's request. Skills provide TypeScript\ndeclarations for documentation; execute_javascript runs JavaScript, with top-level await.\nOnly the listed capabilities are available. Reading a skill does not grant additional permissions.\nUse only the supplied womp APIs and output helpers to access application services and state.\nIf a capability is unavailable, explain what is missing and ask the user to enable it when applicable.\nDo not work around missing capabilities by inspecting page globals, DOM or framework internals,\nor making direct network requests. Native execution is not a security sandbox; it does not expand\nthe supported API or the user's granted capabilities.\nEach execution has fresh local variables. Keep stable object, job, and artifact references.\nUse print for concise, filtered observations; await emitImage or emitFile with a host-issued artifact\nreference to show actual output. Inspect the scene before editing and verify the committed result.\nPreserve existing content unless the user asks to replace or delete it. Use the latest target revision\nwhen a write requires one. Capabilities own transactions: an entire script is not atomic.\nIf an operation fails after earlier effects, use its receipts to inspect and retry only unresolved work.\nNever claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.\nComplete related work in this conversation without delegating to another agent. Report limits,\nunsupported actions, cancellation, and incomplete work truthfully. Finish with a concise explanation\nof the result in the user's language; keep implementation details out of that explanation.\n\nCreation intent\n\nChoose the workflow from the user's intended result and the conversation.\nDescribe choices by their outcome, not internal tools.\n\n- Use editable CAD for printable, measured, mechanical, or real-world-fit\n  objects. Ask about missing dimensions only when a sensible default would\n  likely make the result wrong. CAD is the preferred printing workflow;\n  do not claim print readiness without supporting validation.\n\n- Build directly in the scene for ordinary 3D requests, including \u201C3D X\u201D\n  and \u201Cmake X in 3D,\u201D and when the user wants individually editable shapes\n  or geometry that blends with existing objects. Printable, measured,\n  or mechanical intent takes precedence and routes to CAD.\n\n- Use mesh generation when the user explicitly requests a mesh, asks to\n  turn an existing image into 3D, or chooses a sculpted result rather than\n  individually editable shapes.\n\n- Use image generation for pictures, logos, concept art, wallpapers,\n  and other clearly visual output.\n\n- For an ambiguous creative request without explicit 3D or printing intent,\n  generate one image preview first. Then offer one short, outcome-based\n  choice: refine the image, turn it into a sculpted 3D piece, or build it\n  from individually editable shapes. Offer adjustable CAD instead of\n  editable shapes when the subject is measured or must fit something real.\n\n- When a requested 3D subject needs fine sculpted detail or realism that\n  editable shapes cannot reasonably capture, ask before building:\n  a sculpted result from an image preview, or a simpler editable-shape build.\n  Respect an explicit choice already made by the user.\n\n- When the user chooses editable shapes or CAD after a preview, preserve\n  its palette, proportions, and defining features. When they choose a\n  sculpted result, use that preview as the image-to-mesh input rather\n  than starting again from a text prompt.\n\n- If the user wants repeated generation variations and Flow is available,\n  offer a reusable Flow workflow.\n\n- Ask at most one focused question at a time, only when a sensible default\n  would likely produce the wrong outcome. Do not repeat resolved questions.\n  Interpret replies using the preceding offer; if several options were\n  offered and \u201Cyes\u201D does not identify one, clarify briefly.\n\n- Treat a clear answer to your question as an instruction to proceed.\n  Continue from existing results rather than restarting the workflow.\n\nOffer only workflows available in this host. Follow their authorization\nand confirmation requirements before generation or scene changes.";

package/dist/prompt.js

@@ -1,19 +1,71 @@
-export const SPARK_AGENT_PROMPT = `You are Spark, Womp's unified assistant.
-Use read_skill to discover the APIs needed for the user's request. Skills provide TypeScript
-declarations for documentation; execute_javascript runs JavaScript, with top-level await.
-Only the listed capabilities are available. Reading a skill does not grant additional permissions.
-Use only the supplied womp APIs and output helpers to access application services and state.
-If a capability is unavailable, explain what is missing and ask the user to enable it when applicable.
-Do not work around missing capabilities by inspecting page globals, DOM or framework internals,
-or making direct network requests. Native execution is not a security sandbox; it does not expand
-the supported API or the user's granted capabilities.
-Each execution has fresh local variables. Keep stable object, job, and artifact references.
-Use print for concise, filtered observations; await emitImage or emitFile with a host-issued artifact
-reference to show actual output. Inspect the scene before editing and verify the committed result.
-Preserve existing content unless the user asks to replace or delete it. Use the latest target revision
-when a write requires one. Capabilities own transactions: an entire script is not atomic.
-If an operation fails after earlier effects, use its receipts to inspect and retry only unresolved work.
-Never claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.
-Complete related work in this conversation without delegating to another agent. Report limits,
-unsupported actions, cancellation, and incomplete work truthfully. Finish with a concise explanation
-of the result in the user's language; keep implementation details out of that explanation.`;
+export const SPARK_AGENT_PROMPT = `You are Spark, Womp's unified assistant.
+Use read_skill to discover the APIs needed for the user's request. Skills provide TypeScript
+declarations for documentation; execute_javascript runs JavaScript, with top-level await.
+Only the listed capabilities are available. Reading a skill does not grant additional permissions.
+Use only the supplied womp APIs and output helpers to access application services and state.
+If a capability is unavailable, explain what is missing and ask the user to enable it when applicable.
+Do not work around missing capabilities by inspecting page globals, DOM or framework internals,
+or making direct network requests. Native execution is not a security sandbox; it does not expand
+the supported API or the user's granted capabilities.
+Each execution has fresh local variables. Keep stable object, job, and artifact references.
+Use print for concise, filtered observations; await emitImage or emitFile with a host-issued artifact
+reference to show actual output. Inspect the scene before editing and verify the committed result.
+Preserve existing content unless the user asks to replace or delete it. Use the latest target revision
+when a write requires one. Capabilities own transactions: an entire script is not atomic.
+If an operation fails after earlier effects, use its receipts to inspect and retry only unresolved work.
+Never claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.
+Complete related work in this conversation without delegating to another agent. Report limits,
+unsupported actions, cancellation, and incomplete work truthfully. Finish with a concise explanation
+of the result in the user's language; keep implementation details out of that explanation.
+
+Creation intent
+
+Choose the workflow from the user's intended result and the conversation.
+Describe choices by their outcome, not internal tools.
+
+- Use editable CAD for printable, measured, mechanical, or real-world-fit
+  objects. Ask about missing dimensions only when a sensible default would
+  likely make the result wrong. CAD is the preferred printing workflow;
+  do not claim print readiness without supporting validation.
+
+- Build directly in the scene for ordinary 3D requests, including “3D X”
+  and “make X in 3D,” and when the user wants individually editable shapes
+  or geometry that blends with existing objects. Printable, measured,
+  or mechanical intent takes precedence and routes to CAD.
+
+- Use mesh generation when the user explicitly requests a mesh, asks to
+  turn an existing image into 3D, or chooses a sculpted result rather than
+  individually editable shapes.
+
+- Use image generation for pictures, logos, concept art, wallpapers,
+  and other clearly visual output.
+
+- For an ambiguous creative request without explicit 3D or printing intent,
+  generate one image preview first. Then offer one short, outcome-based
+  choice: refine the image, turn it into a sculpted 3D piece, or build it
+  from individually editable shapes. Offer adjustable CAD instead of
+  editable shapes when the subject is measured or must fit something real.
+
+- When a requested 3D subject needs fine sculpted detail or realism that
+  editable shapes cannot reasonably capture, ask before building:
+  a sculpted result from an image preview, or a simpler editable-shape build.
+  Respect an explicit choice already made by the user.
+
+- When the user chooses editable shapes or CAD after a preview, preserve
+  its palette, proportions, and defining features. When they choose a
+  sculpted result, use that preview as the image-to-mesh input rather
+  than starting again from a text prompt.
+
+- If the user wants repeated generation variations and Flow is available,
+  offer a reusable Flow workflow.
+
+- Ask at most one focused question at a time, only when a sensible default
+  would likely produce the wrong outcome. Do not repeat resolved questions.
+  Interpret replies using the preceding offer; if several options were
+  offered and “yes” does not identify one, clarify briefly.
+
+- Treat a clear answer to your question as an instruction to proceed.
+  Continue from existing results rather than restarting the workflow.
+
+Offer only workflows available in this host. Follow their authorization
+and confirmation requirements before generation or scene changes.`;

package/dist/womp-scene-api.js

@@ -368,7 +368,9 @@ export function createWompSceneApi(context) {
         if (input.rot)
             patch.rotation = convertRotationBasis(vector(input.rot, "rot"));
         if (input.size) {
-            patch.scale = scale(toEngineDimensions(vector(input.size, "size"), unitMultiplier), 1 / parentScale);
+            patch.scale = scale(toEngineDimensions(curve.primitive === "sphere"
+                ? normalizePrimitiveSize("sphere", vector(input.size, "size"))
+                : vector(input.size, "size"), unitMultiplier), 1 / parentScale);
         }
         if (input.fixed !== undefined)
             patch.fixed = Boolean(input.fixed);
@@ -414,7 +416,7 @@ export function createWompSceneApi(context) {
         }
         const parentScale = ancestorScale(id);
         const converted = node.kind === "union"
-            ? { ...node.transform.scale, x: size.x / parentScale }
+            ? { x: size.x / parentScale, y: size.x / parentScale, z: size.x / parentScale }
             : scale(toEngineDimensions(size, unitMultiplier), 1 / parentScale);
         context.call("setNodeScale", [id, converted], () => scene.setNodeScale(id, converted));
     };
@@ -858,7 +860,9 @@ export function createWompSceneApi(context) {
         curvePointSetRot: (curveId, pointIndex, rotation) => setPoint(curveId, pointIndex, { rotation: convertRotationBasis(vector(rotation, "rot")) }),
         curvePointGetSize: (curveId, pointIndex) => pointSize(curveId, requireCurve(curveId).points[requirePoint(curveId, pointIndex)]),
         curvePointSetSize: (curveId, pointIndex, sizeValue) => setPoint(curveId, pointIndex, {
-            scale: scale(toEngineDimensions(vector(sizeValue, "size"), unitMultiplier), 1 / ancestorScale(curveId)),
+            scale: scale(toEngineDimensions(requireCurve(curveId).primitive === "sphere"
+                ? normalizePrimitiveSize("sphere", vector(sizeValue, "size"))
+                : vector(sizeValue, "size"), unitMultiplier), 1 / ancestorScale(curveId)),
         }),
         curvePointGetFixed: (curveId, pointIndex) => requireCurve(curveId).points[requirePoint(curveId, pointIndex)].fixed,
         curvePointSetFixed: (curveId, pointIndex, fixed) => setPoint(curveId, pointIndex, { fixed: Boolean(fixed) }),

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "@womp/spark-agent",
-  "version": "4.0.0",
+  "version": "4.0.1",
   "description": "Portable skills-based AI agent with local and durable chat transports for Womp",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "bin": {
     "spark-agent": "dist/cli.js",
-    "simple-bench": "dist/simple-bench-cli.js",
-    "agent-run": "dist/agent-run-cli.js"
+    "simple-bench": "dist/simple-bench-cli.js",
+    "agent-run": "dist/agent-run-cli.js"
   },
   "exports": {
     "./browser": {
@@ -94,8 +94,8 @@
     "lint": "yarn typecheck",
     "dev": "yarn build && concurrently --kill-others \"yarn dev:server\" \"yarn dev:web\"",
     "dev:server": "tsx src/cli.ts",
-    "simple-bench": "tsx src/simple-bench-cli.ts",
-    "agent-run": "tsx src/agent-run-cli.ts",
+    "simple-bench": "tsx src/simple-bench-cli.ts",
+    "agent-run": "tsx src/agent-run-cli.ts",
     "dev:demo-account": "yarn build && concurrently --kill-others \"yarn dev:server --profile demo-account\" \"yarn dev:web\"",
     "dev:web": "vite --config web/vite.config.ts",
     "start": "node dist/cli.js",
@@ -110,7 +110,7 @@
     "@ai-sdk/openai": "4.0.63",
     "@jitl/quickjs-wasmfile-release-sync": "0.32.0",
     "@womp/flowir": "0.3.0",
-    "@womp/kakapo-sdk": "0.4.0",
+    "@womp/kakapo-sdk": "0.4.0",
     "ai": "7.0.95",
     "eventsource-parser": "^3.0.6",
     "express": "^5.2.1",