forgecad 0.9.7 → 0.9.8

package/dist-skill/docs-dev/guides/skill-maintenance.md

@@ -132,7 +132,7 @@ Use a `skill-group` with a `dev-` prefix (e.g. `dev-compiler`, `dev-solver`, `de
 | Does a model author need this to build `.forge.js` files? | Standard |
 | Does it describe internal architecture (compiler, solver, pipeline)? | Dev only |
 | Does it cover team process (coding standards, releases, CI)? | Dev only |
-| Is it a CLI command only developers run (`check suite`, `sdf`, debug flags)? | Dev only |
+| Is it repo-only developer tooling (`npm run check:suite`, `sdf`, debug flags)? | Dev only |
 
 ## Orphan files
 

package/dist-skill/library/forgecad-make-a-model/SKILL.md

@@ -261,6 +261,17 @@ After the normal PNG render, run `forgecad render inspect` and read both the cha
 forgecad render inspect model.forge.js /tmp/model-inspect --channels rgb,mask,collisions --force --size 700
 ```
 
+### Keep CLI inspection scenes small
+
+When using CLI inspection commands, make the scene as few returned/named objects as the requirement allows. The goal is not to hide required geometry; it is to keep the evidence small enough that the agent can reason about it properly.
+
+- Return one selected configuration, not every variant, option bundle, or debug lineup.
+- Include only the parts, ghosts, and fixtures needed to prove the current risk. If a collision, clearance, thickness, or section check concerns three objects, inspect those three objects instead of the whole shop floor.
+- Prefer `--focus` / `--hide` and parameter-selected diagnostic modes over adding permanent extra objects to the default scene.
+- Collapse decorative or already-proven subassemblies into fewer named objects when their internal boundaries are irrelevant to the inspection. Keep separate names only where object identity matters for collisions, masks, clearances, BOM roles, or mechanical contracts.
+
+Small inspection scenes make `manifest.json`, mask colors, collision pairs, component counts, and section images cognitively tractable. If the agent cannot hold the scene in its head, it cannot debug the model honestly.
+
 For faster iteration, request the channels that match the current risk:
 
 - `collisions` — final multi-part assemblies, fixtures, enclosures, ghost fit checks, moving clearances, and any parts intended to touch without overlapping. Visually inspect this channel; do not rely only on the count.

package/dist-skill/library/forgecad-render-inspect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: forgecad-render-inspect
-description: Run and interpret ForgeCAD `render inspect` bundles for model verification. Use when asked to inspect a ForgeCAD model, analyze an inspection bundle, validate collisions, wall thickness, connectivity, sections, masks, depth, normals, or choose inspection channels.
+description: Run and interpret ForgeCAD `render inspect` bundles for model verification. Use when asked to inspect a ForgeCAD model, analyze an inspection bundle, validate collisions, wall thickness, connectivity, floating bodies, sections, masks, depth, normals, Zebra stripes, or choose inspection channels.
 forgecad-public: true
 ---
 
@@ -18,7 +18,7 @@ Use this skill for:
 
 - inspecting an existing `.forge.js` model
 - analyzing a previously generated inspection bundle
-- validating collisions, wall thickness, section cuts, connectivity, distance, object masks, depth, or normals
+- validating collisions, wall thickness, section cuts, connectivity, floating bodies, distance, object masks, depth, normals, or Zebra stripes
 - deciding which `render inspect` channels to run
 - producing evidence before calling a model complete
 
@@ -70,6 +70,7 @@ Routing:
    jq '.channels.collisions | {collisionCount, collisions, warnings}' /tmp/model-inspect/manifest.json
    jq '.channels.thickness.objects[] | {name, minThickness, p05Thickness, criticalAreaPercent, warningAreaPercent, unresolvedAreaPercent}' /tmp/model-inspect/manifest.json
    jq '.channels.connectivity | {componentCount, edges, warnings}' /tmp/model-inspect/manifest.json
+   jq '.channels.floating | {floatingBodyCount, floatingObjectCount, warnings}' /tmp/model-inspect/manifest.json
    ```
 
 6. Inspect the PNGs, not only the JSON.
@@ -90,9 +91,11 @@ Routing:
 | Multi-part interference, fit checks, ghost parts, moving clearances | `rgb,mask,collisions` |
 | Final multi-part mechanical or manufactured model | `rgb,mask,collisions` plus `section`, `thickness`, `connectivity`, or `distance` only when those risks apply |
 | Printability, shell walls, ribs, bosses, snaps, slots | `rgb,section,thickness` |
-| Floating parts, accidental fusion, connected solids | `rgb,mask,connectivity` |
+| Parts without a mesh-contact path to the ground | `rgb,mask,floating` |
+| Accidental fusion, connected solids | `rgb,mask,connectivity` |
 | Air gaps between physical components | `rgb,mask,distance` |
 | Surface orientation, occlusion, faceting, strange protrusions | `rgb,depth,normals` |
+| Loft, fillet, skin, and sweep surface continuity | `rgb,zebra,normals` |
 
 ## Command Patterns
 
@@ -144,6 +147,7 @@ Manifest fields to check first:
 - `channels.collisions.collisionCount`: investigate every unexpected positive-volume overlap.
 - `channels.thickness.objects`: inspect `minThickness`, `p05Thickness`, critical/warning percentages, and unresolved area.
 - `channels.connectivity.componentCount`: compare to the expected number of physical components.
+- `channels.floating.floatingBodyCount`: investigate every body without a mesh-contact path to the ground plane, especially body entries from one unioned object.
 - `channels.distance.maxRootDistance` and per-object `nearestGap`: check suspicious isolation or spacing.
 - `channels.section.planes`: look for missing slices, wrong path counts, or empty internal cuts. These are inspection views, not instructions to section the returned production geometry.
 
@@ -158,11 +162,13 @@ PNG review order:
 ## Interpretation Rules
 
 - Collision findings are positive-volume boolean overlaps. Face-touching is not a collision.
-- Connectivity uses bbox as a broadphase, then exact overlap evidence for component grouping. Bbox-only contact does not merge separate scene objects by default; use the collisions channel for positive-volume overlap evidence.
+- Connectivity uses bbox as a broadphase, then shared physical-contact detection for component grouping: mesh surfaces within contact tolerance count as connected, exact positive-volume overlap is used when needed, and bbox-only contact does not merge separate scene objects by default. Use the collisions channel for positive-volume overlap evidence.
+- Floating uses the same shared physical-contact detection plus scene-ground reachability. Mesh gaps within contact tolerance count as connected, bbox overlap or bbox face contact alone does not, and every component without a contact path to ground is reported. Disconnected mesh islands inside one object are inspected separately.
 - Distance is a bbox-gap metric between physical components, not exact closest surface distance.
-- Thickness is a mesh/raycast approximation. Gray or high unresolved area means the visual heatmap is incomplete, not that the model is safe.
+- Thickness is a contact-aware mesh/raycast approximation. It uses the same physical-contact edges as connectivity/floating, so rays jump over direct-neighbor contact seams within contact tolerance before measuring the next surface. Gray or high unresolved area means the visual heatmap is incomplete, not that the model is safe.
 - Depth is a visual heatmap, not raw floating-point depth data.
 - Normals are camera-view normals, not world-space normals.
+- Zebra is a reflective stripe shader for visual continuity inspection, not an exact curvature-continuity proof.
 - Mask colors are stable within a bundle and resolved through the manifest.
 
 ## Source Map
@@ -177,4 +183,4 @@ Read these only when needed:
 | Browser-side channel rendering | `cli/render.ts` |
 | Collision semantics | `cli/collision-inspection.ts` |
 | Thickness semantics | `cli/thickness-inspection.ts` |
-| Connectivity and distance semantics | `cli/physical-connectivity.ts` and `cli/distance-inspection.ts` |
+| Connectivity, floating, and distance semantics | `cli/physical-connectivity.ts`, `cli/floating-inspection.ts`, and `cli/distance-inspection.ts` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forgecad",
-  "version": "0.9.7",
+  "version": "0.9.8",
   "description": "Code-first parametric CAD for JavaScript/TypeScript, in the browser and CLI.",
   "license": "BUSL-1.1",
   "type": "module",
@@ -56,9 +56,10 @@
     "lint:fix": "npx biome check . --write",
     "format": "npx biome format . --write",
     "test:llms": "vitest run test/llmsTxt.test.ts",
+    "check:suite": "npm run test:prepare && tsx cli/check-suite.ts",
     "test": "npm run test:smoke",
-    "test:smoke": "npm run test:prepare && node dist-cli/forgecad.js check suite --profile smoke",
-    "test:full": "npm run test:prepare && node dist-cli/forgecad.js check suite",
+    "test:smoke": "npm run check:suite -- --profile smoke",
+    "test:full": "npm run check:suite",
     "test:unit": "vitest run",
     "test:prepare": "npm run build:solver:if-missing && npm run build:geometry:if-missing && tsc --noEmit && npm run build:cli",
     "test:compiler": "npm run test:prepare && node dist-cli/forgecad.js check compiler",
@@ -120,6 +121,7 @@
     "prod:errors": "bash scripts/prod/errors.sh",
     "prod:promote-beta": "fish scripts/promote-beta-to-prod.fish",
     "prod:help": "bash scripts/prod.sh help",
+    "paid-user-note": "node scripts/create-paid-user-note.mjs",
     "gen:types": "node scripts/gen-forge-types.mjs",
     "gen:docs": "node scripts/gen-api-docs.mjs",
     "gen:cli-docs": "node scripts/gen-cli-docs.mjs",
@@ -183,6 +185,7 @@
     "react-dom": "^19.1.0",
     "three": "^0.175.0",
     "tsup": "^8.5.0",
+    "tsx": "^4.21.0",
     "vite": "^6.3.5",
     "vitest": "^4.1.2",
     "zustand": "^5.0.5"