forgecad 0.9.7 → 0.9.9

package/dist-skill/CONTEXT.md

@@ -9425,9 +9425,9 @@ Setting `KNUCK_R = H / 2` exactly makes the body cross-section a stadium that pe
 
 `forgecad render inspect` writes a deterministic directory bundle for agents,
 tests, and automation. Use it when a single shaded PNG is too ambiguous and the
-consumer needs geometry-aware signals such as depth, normals, surface roughness,
-part identity, physical connected components, collisions, local thickness, or
-cross-sections.
+consumer needs geometry-aware signals such as depth, normals, Zebra stripes,
+surface roughness, part identity, physical connected components, collisions,
+local thickness, or cross-sections.
 
 ## When To Use It
 
@@ -9467,7 +9467,7 @@ with patterns such as `Bench.*`.
 
 ## Bundle Layout
 
-A bundle that asks for `--channels rgb,depth,normals,mask,section` has this
+A bundle that asks for `--channels rgb,depth,normals,zebra,mask,section` has this
 layout:
 
 ```text
@@ -9489,6 +9489,11 @@ model-inspect/
       right.png
       top.png
       iso.png
+    zebra/
+      front.png
+      right.png
+      top.png
+      iso.png
     mask/
       front.png
       right.png
@@ -9514,13 +9519,15 @@ implemented channel in one bundle:
 
 ```bash
 forgecad render inspect model.forge.js --channels depth,normals
+forgecad render inspect model.forge.js --channels rgb,zebra,normals
 forgecad render inspect model.forge.js --channels rgb,roughness
 forgecad render inspect model.forge.js --channels rgb,mask,collisions
 forgecad render inspect model.forge.js --channels rgb,section,thickness
 ```
 
-Supported channels are `rgb`, `depth`, `normals`, `roughness`, `mask`,
-`connectivity`, `distance`, `collisions`, `thickness`, and `section`.
+Supported channels are `rgb`, `depth`, `normals`, `zebra`, `roughness`, `mask`,
+`connectivity`, `floating`, `distance`, `collisions`, `thickness`, and
+`section`.
 
 ## Channel Semantics
 
@@ -9547,6 +9554,17 @@ normal = normalize((rgb / 255) * 2 - 1)
 
 Background pixels are black and should be treated as `null`.
 
+`zebra` emits reflective black-and-white stripe renders for visual
+surface-continuity inspection. Stripes are generated from the visible
+camera-view normal and simulated reflection direction, so smooth surfaces show
+smooth flowing bands while normal discontinuities, faceting, and unexpected
+creases kink or break the bands.
+
+Use Zebra with `rgb` and `normals` when judging lofts, fillets, swept surfaces,
+and skin-like forms. It is a human-readable shader diagnostic, not an exact
+curvature-continuity proof; mesh tessellation quality and available smooth
+normals determine how faithfully it represents the underlying surface.
+
 `roughness` emits a mesh-dihedral surface-quality heatmap. Smooth and gently
 curved triangles render as a faint translucent shadow over black, while
 triangles adjacent to sharp, harsh, boundary, or non-manifold mesh edges render
@@ -9588,21 +9606,58 @@ Connectivity is computed from visible scene objects:
 
 ```text
 bbox candidate = bbox interiors overlap or bbox contact gap <= 0.05 model units
-overlap edge = exact boolean intersection volume > 0.1 model units^3
-component = transitive closure over exact overlap edges
+mesh contact edge = minimum mesh-surface distance <= contactTolerance
+overlap edge = exact boolean intersection volume > 0.1 model units^3 for positive-volume overlap
+component = transitive closure over mesh contact and exact overlap edges
 ```
 
 The manifest stores the edge list, component list, per-object body counts, and
-warnings. Component colors group scene objects; if one scene object contains
-multiple disconnected kernel bodies and the caller supplied a body count, the
-manifest reports `bodyCount > 1` but the PNG cannot color those internal bodies
-separately yet.
+warnings. Component colors group scene objects and mesh body entries. If one
+scene object contains multiple disconnected mesh islands, those islands are
+reported and colored separately as entries such as `Part body 1` and
+`Part body 2`.
+
+Connectivity uses bbox only as a broadphase. Bbox contact alone is not enough to
+merge separate scene objects by default, but mesh surfaces within contact
+tolerance count as physically connected. This keeps concave assemblies such as
+cages and captive balls from being falsely colored as one component while still
+allowing stacked or nearly touching parts to share a component. Use the
+`collisions` channel when you need positive-volume overlap evidence as a defect
+report rather than a component grouping.
+
+`floating` emits one disconnected-body highlight image per view. Black is
+background or ground-reachable geometry. The highlight color marks physical
+components that have no contact path to the ground plane.
+
+Floating body detection splits visible meshes into disconnected body islands,
+links bodies only when their minimum mesh-surface distance is within contact
+tolerance (or exact positive-volume overlap when only shape evidence is
+available), treats any connected component whose lower Z reaches the viewport
+ground plane plus bed tolerance as grounded, then highlights every ungrounded
+component. The default ground plane is the visible model's minimum Z;
+`scene({ ground: { offset } })` moves it below that by the configured offset.
 
-Connectivity uses bbox only as a broadphase. Bbox contact is not enough to merge
-separate scene objects, which keeps concave assemblies such as cages and captive
-balls from being falsely colored as one component. Use the `collisions` channel
-when you need positive-volume overlap evidence as a defect report rather than a
-component grouping.
+```text
+grounded = component bbox minZ <= groundZ + bedTolerance
+floating body = !grounded
+```
+
+This means a `union()` result with two disconnected mesh islands is inspected as
+two separate bodies instead of being treated as one safe object. Bbox overlap or
+bbox face contact alone is not support evidence. Use `connectivity`, `distance`,
+or `collisions` when you need the full physical graph, rooted gap distances, or
+collision defects.
+
+`thickness` emits one local wall-thickness heatmap per view. Black is
+background. Red/orange pixels are below the configured critical/warning
+thresholds, green-to-blue pixels are acceptable/thick, and gray means the local
+raycast could not resolve an opposite surface.
+
+Thickness uses the same physical-contact edges as `connectivity` and `floating`.
+When a ray crosses from one object to a direct physical-contact neighbor, hits
+within `contactTolerance` are treated as contact seams and the ray continues to
+the next surface. This prevents a tiny modeled gap between touching parts from
+being reported as a paper-thin wall.
 
 `distance` emits one rooted physical-component-distance heatmap per view. Black
 is background. Non-black pixels resolve through
@@ -9651,6 +9706,10 @@ with the ghosted source geometry. If `--focus PartA,PartB` is used, everything
 except those objects is hidden, `PartA` and `PartB` are ghosted, and their
 overlap volume is highlighted if present.
 
+Collision broadphase prunes exact boolean checks when the bbox intersection
+volume is already below the overlap threshold. This does not change findings:
+the real intersection volume cannot exceed the bbox intersection volume.
+
 `thickness` emits one local wall-thickness heatmap per view. The renderer places
 deterministic area-weighted point samples across visible mesh surfaces, casts
 through the object along each sample normal, and colors each point by the first
@@ -9734,8 +9793,7 @@ per-view depth ranges, and object-mask mappings live.
   guarantee. Open meshes, concave geometry, very coarse tessellation, or low
   `--thickness-samples` values can leave gray/unresolved or approximate regions.
 - Section atlases use five default interior slices today.
-- Zebra/reflection-line inspection is a follow-up channel, not part of the v1
-  bundle.
+- Zebra is a shader-based visual continuity aid, not exact curvature analysis.
 
 ---
 

package/dist-skill/docs/CLI.md

@@ -191,7 +191,7 @@ forgecad render views model.forge.js --json
 
 Render a machine-readable inspection bundle with geometry channels and a manifest.
 
-Launches the headless viewport renderer and writes a directory bundle for agent and automation workflows. Every channel is opt-in with `--channels`; there is no default bundle. Selected channels emit canonical `front`, `right`, `top`, and `iso` views for RGB, depth, normals, surface roughness, object masks, physical connectivity, rooted component distance, collisions, and wall thickness, or a principal-plane section atlas, plus a root `manifest.json` with scene metadata, filters, object visibility, and relative file paths.
+Launches the headless viewport renderer and writes a directory bundle for agent and automation workflows. Every channel is opt-in with `--channels`; there is no default bundle. Selected channels emit canonical `front`, `right`, `top`, and `iso` views for RGB, depth, normals, Zebra surface-continuity stripes, surface roughness, object masks, physical connectivity, floating body highlights, rooted component distance, collisions, and wall thickness, or a principal-plane section atlas, plus a root `manifest.json` with scene metadata, filters, object visibility, and relative file paths.
 
 Use `--focus` to isolate specific parts or hide mocks, and `--hide` to remove named clutter. Output defaults to `<script-name>-inspect/` next to the input file.
 
@@ -199,6 +199,7 @@ For bundle layout, channel encodings, and manifest semantics, see [Inspection Bu
 
 ```bash
 forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,mask
+forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,zebra,normals
 forgecad render inspect examples/api/static-assembly-connectors.forge.js out/bench-inspect --channels collisions --focus "Bench.*"
 forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,mask,collisions --hide "Bench.Slat0" --force
 ```
@@ -299,21 +300,21 @@ forgecad render section examples/furniture/01-table.forge.js out/bold.svg --edge
 | `--background <color>` | Canvas background override |
 | `--render-mode <solid\|wireframe>` | Shaded solid (default) or wireframe only |
 | `--edges <off\|thin\|bold>` | Edge overlay preset in solid mode (default: off) |
-| `--render-style <classic\|studio\|fast\|glass>` | Visual render style (default: classic) |
+| `--render-style <classic\|studio\|fast\|glass\|precision\|hybrid>` | Visual render style (default: classic) |
 | `--port <n>` | Vite dev server port |
 | `--fresh-server` | Start a fresh renderer instead of reusing an existing one |
 | `--chrome-path <path>` | Chrome or Chromium executable path |
 | `--output <path>` | Output file path |
 | `--json` | Print machine-readable JSON |
 | `--quality <default\|live\|high>` | Mesh quality preset |
-| `--backend <manifold\|occt\|truck>` | Geometry backend |
-| `--channels <rgb,depth,normals,roughness,mask,connectivity,distance,collisions,thickness,section>` | Required inspection channels to emit; no default |
+| `--backend <manifold\|occt\|truck>` | Geometry backend (default: manifold) |
+| `--channels <rgb,depth,normals,zebra,roughness,mask,connectivity,floating,distance,collisions,thickness,section>` | Required inspection channels to emit; no default |
 | `--force` | Replace an existing bundle directory |
 | `--min-thickness <mm>` | Critical thickness threshold in model units |
 | `--warn-thickness <mm>` | Warning thickness threshold in model units |
 | `--max-thickness <mm>` | Thick/blue heatmap threshold in model units |
-| `--thickness-samples <n>` | Maximum thickness point samples per object |
-| `--roughness-samples <n>` | Maximum roughness point samples per object |
+| `--thickness-samples <n>` | Override default scene budget with max thickness point samples per object |
+| `--roughness-samples <n>` | Override default scene budget with max roughness point samples per object |
 | `--preset <name>` | Material/lighting preset |
 | `--width <px>` | Output width in pixels |
 | `--height <px>` | Output height in pixels |
@@ -400,7 +401,7 @@ forgecad export sdf rover.forge.js --output out/forge_scout
 |--------|-------------|
 | `--output <path>` | Output STEP path |
 | `--quality <default\|live\|high>` | Forge quality preset |
-| `--backend <manifold\|occt\|truck>` | Geometry backend |
+| `--backend <manifold\|occt\|truck>` | Geometry backend (default: manifold) |
 | `-o <path>` | Output file path |
 | `--dim-angle-tol <deg>` | Dimension routing tolerance in degrees |
 | `--sheet-width <mm>` | Stock sheet width in mm |
@@ -548,7 +549,7 @@ forgecad skill flattened-files ~/Desktop/forgecad-skills
 
 ## Validation
 
-Check printability, test parameter ranges, and run invariant suites.
+Check printability, test parameter ranges, and run focused model invariants.
 
 ### `forgecad check print`
 
@@ -601,7 +602,6 @@ forgecad check params path/to/model.forge.js --samples 12
 
 | Command | Description |
 |---------|-------------|
-| `check suite` | Run the repo invariant suite, with smoke and full profiles for the fast merge lane vs the broader regression sweep. |
 | `inspect mechanical-integrity` | Inspect generated ForgeCAD models for mechanical integrity failures. |
 | `check runtime-globals` | Ensure the script sandbox does not add new lowercase injected globals. |
 | `check transforms` | Run transform and assembly invariants. |
@@ -646,7 +646,7 @@ The CLI is free for core workflows and exports. Production outputs are free to r
 
 | Free | Production outputs | Pro |
 |------|--------------------|-----|
-| `run`, `dev`, `studio`, `render 3d`, `export stl`, `export 3mf`, `export svg`, `check print`, `check params`, `inspect mechanical-integrity`, `check suite` | `cut-list`, `export sketch-pdf`, `export step`, `export brep`, `export gcode`, `export sdf`, `export urdf`, `export report`, `export cutting-layout` are free to run; Pro covers commercial use. | `render hq`, `capture gif`, `capture mp4` |
+| `run`, `dev`, `studio`, `render 3d`, `export stl`, `export 3mf`, `export svg`, `check print`, `check params`, `inspect mechanical-integrity` | `cut-list`, `export sketch-pdf`, `export step`, `export brep`, `export gcode`, `export sdf`, `export urdf`, `export report`, `export cutting-layout` are free to run; Pro covers commercial use. | `render hq`, `capture gif`, `capture mp4` |
 
 ```bash
 forgecad license                    # Check signed-in account status

package/dist-skill/docs/guides/inspection-bundles.md

@@ -7,9 +7,9 @@ skill-order: 2
 
 `forgecad render inspect` writes a deterministic directory bundle for agents,
 tests, and automation. Use it when a single shaded PNG is too ambiguous and the
-consumer needs geometry-aware signals such as depth, normals, surface roughness,
-part identity, physical connected components, collisions, local thickness, or
-cross-sections.
+consumer needs geometry-aware signals such as depth, normals, Zebra stripes,
+surface roughness, part identity, physical connected components, collisions,
+local thickness, or cross-sections.
 
 ## When To Use It
 
@@ -49,7 +49,7 @@ with patterns such as `Bench.*`.
 
 ## Bundle Layout
 
-A bundle that asks for `--channels rgb,depth,normals,mask,section` has this
+A bundle that asks for `--channels rgb,depth,normals,zebra,mask,section` has this
 layout:
 
 ```text
@@ -71,6 +71,11 @@ model-inspect/
       right.png
       top.png
       iso.png
+    zebra/
+      front.png
+      right.png
+      top.png
+      iso.png
     mask/
       front.png
       right.png
@@ -96,13 +101,15 @@ implemented channel in one bundle:
 
 ```bash
 forgecad render inspect model.forge.js --channels depth,normals
+forgecad render inspect model.forge.js --channels rgb,zebra,normals
 forgecad render inspect model.forge.js --channels rgb,roughness
 forgecad render inspect model.forge.js --channels rgb,mask,collisions
 forgecad render inspect model.forge.js --channels rgb,section,thickness
 ```
 
-Supported channels are `rgb`, `depth`, `normals`, `roughness`, `mask`,
-`connectivity`, `distance`, `collisions`, `thickness`, and `section`.
+Supported channels are `rgb`, `depth`, `normals`, `zebra`, `roughness`, `mask`,
+`connectivity`, `floating`, `distance`, `collisions`, `thickness`, and
+`section`.
 
 ## Channel Semantics
 
@@ -129,6 +136,17 @@ normal = normalize((rgb / 255) * 2 - 1)
 
 Background pixels are black and should be treated as `null`.
 
+`zebra` emits reflective black-and-white stripe renders for visual
+surface-continuity inspection. Stripes are generated from the visible
+camera-view normal and simulated reflection direction, so smooth surfaces show
+smooth flowing bands while normal discontinuities, faceting, and unexpected
+creases kink or break the bands.
+
+Use Zebra with `rgb` and `normals` when judging lofts, fillets, swept surfaces,
+and skin-like forms. It is a human-readable shader diagnostic, not an exact
+curvature-continuity proof; mesh tessellation quality and available smooth
+normals determine how faithfully it represents the underlying surface.
+
 `roughness` emits a mesh-dihedral surface-quality heatmap. Smooth and gently
 curved triangles render as a faint translucent shadow over black, while
 triangles adjacent to sharp, harsh, boundary, or non-manifold mesh edges render
@@ -170,21 +188,58 @@ Connectivity is computed from visible scene objects:
 
 ```text
 bbox candidate = bbox interiors overlap or bbox contact gap <= 0.05 model units
-overlap edge = exact boolean intersection volume > 0.1 model units^3
-component = transitive closure over exact overlap edges
+mesh contact edge = minimum mesh-surface distance <= contactTolerance
+overlap edge = exact boolean intersection volume > 0.1 model units^3 for positive-volume overlap
+component = transitive closure over mesh contact and exact overlap edges
 ```
 
 The manifest stores the edge list, component list, per-object body counts, and
-warnings. Component colors group scene objects; if one scene object contains
-multiple disconnected kernel bodies and the caller supplied a body count, the
-manifest reports `bodyCount > 1` but the PNG cannot color those internal bodies
-separately yet.
+warnings. Component colors group scene objects and mesh body entries. If one
+scene object contains multiple disconnected mesh islands, those islands are
+reported and colored separately as entries such as `Part body 1` and
+`Part body 2`.
+
+Connectivity uses bbox only as a broadphase. Bbox contact alone is not enough to
+merge separate scene objects by default, but mesh surfaces within contact
+tolerance count as physically connected. This keeps concave assemblies such as
+cages and captive balls from being falsely colored as one component while still
+allowing stacked or nearly touching parts to share a component. Use the
+`collisions` channel when you need positive-volume overlap evidence as a defect
+report rather than a component grouping.
+
+`floating` emits one disconnected-body highlight image per view. Black is
+background or ground-reachable geometry. The highlight color marks physical
+components that have no contact path to the ground plane.
+
+Floating body detection splits visible meshes into disconnected body islands,
+links bodies only when their minimum mesh-surface distance is within contact
+tolerance (or exact positive-volume overlap when only shape evidence is
+available), treats any connected component whose lower Z reaches the viewport
+ground plane plus bed tolerance as grounded, then highlights every ungrounded
+component. The default ground plane is the visible model's minimum Z;
+`scene({ ground: { offset } })` moves it below that by the configured offset.
 
-Connectivity uses bbox only as a broadphase. Bbox contact is not enough to merge
-separate scene objects, which keeps concave assemblies such as cages and captive
-balls from being falsely colored as one component. Use the `collisions` channel
-when you need positive-volume overlap evidence as a defect report rather than a
-component grouping.
+```text
+grounded = component bbox minZ <= groundZ + bedTolerance
+floating body = !grounded
+```
+
+This means a `union()` result with two disconnected mesh islands is inspected as
+two separate bodies instead of being treated as one safe object. Bbox overlap or
+bbox face contact alone is not support evidence. Use `connectivity`, `distance`,
+or `collisions` when you need the full physical graph, rooted gap distances, or
+collision defects.
+
+`thickness` emits one local wall-thickness heatmap per view. Black is
+background. Red/orange pixels are below the configured critical/warning
+thresholds, green-to-blue pixels are acceptable/thick, and gray means the local
+raycast could not resolve an opposite surface.
+
+Thickness uses the same physical-contact edges as `connectivity` and `floating`.
+When a ray crosses from one object to a direct physical-contact neighbor, hits
+within `contactTolerance` are treated as contact seams and the ray continues to
+the next surface. This prevents a tiny modeled gap between touching parts from
+being reported as a paper-thin wall.
 
 `distance` emits one rooted physical-component-distance heatmap per view. Black
 is background. Non-black pixels resolve through
@@ -233,6 +288,10 @@ with the ghosted source geometry. If `--focus PartA,PartB` is used, everything
 except those objects is hidden, `PartA` and `PartB` are ghosted, and their
 overlap volume is highlighted if present.
 
+Collision broadphase prunes exact boolean checks when the bbox intersection
+volume is already below the overlap threshold. This does not change findings:
+the real intersection volume cannot exceed the bbox intersection volume.
+
 `thickness` emits one local wall-thickness heatmap per view. The renderer places
 deterministic area-weighted point samples across visible mesh surfaces, casts
 through the object along each sample normal, and colors each point by the first
@@ -316,5 +375,4 @@ per-view depth ranges, and object-mask mappings live.
   guarantee. Open meshes, concave geometry, very coarse tessellation, or low
   `--thickness-samples` values can leave gray/unresolved or approximate regions.
 - Section atlases use five default interior slices today.
-- Zebra/reflection-line inspection is a follow-up channel, not part of the v1
-  bundle.
+- Zebra is a shader-based visual continuity aid, not exact curvature analysis.

package/dist-skill/docs-dev/CLI.md

@@ -191,7 +191,7 @@ forgecad render views model.forge.js --json
 
 Render a machine-readable inspection bundle with geometry channels and a manifest.
 
-Launches the headless viewport renderer and writes a directory bundle for agent and automation workflows. Every channel is opt-in with `--channels`; there is no default bundle. Selected channels emit canonical `front`, `right`, `top`, and `iso` views for RGB, depth, normals, surface roughness, object masks, physical connectivity, rooted component distance, collisions, and wall thickness, or a principal-plane section atlas, plus a root `manifest.json` with scene metadata, filters, object visibility, and relative file paths.
+Launches the headless viewport renderer and writes a directory bundle for agent and automation workflows. Every channel is opt-in with `--channels`; there is no default bundle. Selected channels emit canonical `front`, `right`, `top`, and `iso` views for RGB, depth, normals, Zebra surface-continuity stripes, surface roughness, object masks, physical connectivity, floating body highlights, rooted component distance, collisions, and wall thickness, or a principal-plane section atlas, plus a root `manifest.json` with scene metadata, filters, object visibility, and relative file paths.
 
 Use `--focus` to isolate specific parts or hide mocks, and `--hide` to remove named clutter. Output defaults to `<script-name>-inspect/` next to the input file.
 
@@ -199,6 +199,7 @@ For bundle layout, channel encodings, and manifest semantics, see [Inspection Bu
 
 ```bash
 forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,mask
+forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,zebra,normals
 forgecad render inspect examples/api/static-assembly-connectors.forge.js out/bench-inspect --channels collisions --focus "Bench.*"
 forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,mask,collisions --hide "Bench.Slat0" --force
 ```
@@ -299,21 +300,21 @@ forgecad render section examples/furniture/01-table.forge.js out/bold.svg --edge
 | `--background <color>` | Canvas background override |
 | `--render-mode <solid\|wireframe>` | Shaded solid (default) or wireframe only |
 | `--edges <off\|thin\|bold>` | Edge overlay preset in solid mode (default: off) |
-| `--render-style <classic\|studio\|fast\|glass>` | Visual render style (default: classic) |
+| `--render-style <classic\|studio\|fast\|glass\|precision\|hybrid>` | Visual render style (default: classic) |
 | `--port <n>` | Vite dev server port |
 | `--fresh-server` | Start a fresh renderer instead of reusing an existing one |
 | `--chrome-path <path>` | Chrome or Chromium executable path |
 | `--output <path>` | Output file path |
 | `--json` | Print machine-readable JSON |
 | `--quality <default\|live\|high>` | Mesh quality preset |
-| `--backend <manifold\|occt\|truck>` | Geometry backend |
-| `--channels <rgb,depth,normals,roughness,mask,connectivity,distance,collisions,thickness,section>` | Required inspection channels to emit; no default |
+| `--backend <manifold\|occt\|truck>` | Geometry backend (default: manifold) |
+| `--channels <rgb,depth,normals,zebra,roughness,mask,connectivity,floating,distance,collisions,thickness,section>` | Required inspection channels to emit; no default |
 | `--force` | Replace an existing bundle directory |
 | `--min-thickness <mm>` | Critical thickness threshold in model units |
 | `--warn-thickness <mm>` | Warning thickness threshold in model units |
 | `--max-thickness <mm>` | Thick/blue heatmap threshold in model units |
-| `--thickness-samples <n>` | Maximum thickness point samples per object |
-| `--roughness-samples <n>` | Maximum roughness point samples per object |
+| `--thickness-samples <n>` | Override default scene budget with max thickness point samples per object |
+| `--roughness-samples <n>` | Override default scene budget with max roughness point samples per object |
 | `--preset <name>` | Material/lighting preset |
 | `--width <px>` | Output width in pixels |
 | `--height <px>` | Output height in pixels |
@@ -400,7 +401,7 @@ forgecad export sdf rover.forge.js --output out/forge_scout
 |--------|-------------|
 | `--output <path>` | Output STEP path |
 | `--quality <default\|live\|high>` | Forge quality preset |
-| `--backend <manifold\|occt\|truck>` | Geometry backend |
+| `--backend <manifold\|occt\|truck>` | Geometry backend (default: manifold) |
 | `-o <path>` | Output file path |
 | `--dim-angle-tol <deg>` | Dimension routing tolerance in degrees |
 | `--sheet-width <mm>` | Stock sheet width in mm |
@@ -548,7 +549,7 @@ forgecad skill flattened-files ~/Desktop/forgecad-skills
 
 ## Validation
 
-Check printability, test parameter ranges, and run invariant suites.
+Check printability, test parameter ranges, and run focused model invariants.
 
 ### `forgecad check print`
 
@@ -601,7 +602,6 @@ forgecad check params path/to/model.forge.js --samples 12
 
 | Command | Description |
 |---------|-------------|
-| `check suite` | Run the repo invariant suite, with smoke and full profiles for the fast merge lane vs the broader regression sweep. |
 | `inspect mechanical-integrity` | Inspect generated ForgeCAD models for mechanical integrity failures. |
 | `check runtime-globals` | Ensure the script sandbox does not add new lowercase injected globals. |
 | `check transforms` | Run transform and assembly invariants. |
@@ -646,7 +646,7 @@ The CLI is free for core workflows and exports. Production outputs are free to r
 
 | Free | Production outputs | Pro |
 |------|--------------------|-----|
-| `run`, `dev`, `studio`, `render 3d`, `export stl`, `export 3mf`, `export svg`, `check print`, `check params`, `inspect mechanical-integrity`, `check suite` | `cut-list`, `export sketch-pdf`, `export step`, `export brep`, `export gcode`, `export sdf`, `export urdf`, `export report`, `export cutting-layout` are free to run; Pro covers commercial use. | `render hq`, `capture gif`, `capture mp4` |
+| `run`, `dev`, `studio`, `render 3d`, `export stl`, `export 3mf`, `export svg`, `check print`, `check params`, `inspect mechanical-integrity` | `cut-list`, `export sketch-pdf`, `export step`, `export brep`, `export gcode`, `export sdf`, `export urdf`, `export report`, `export cutting-layout` are free to run; Pro covers commercial use. | `render hq`, `capture gif`, `capture mp4` |
 
 ```bash
 forgecad license                    # Check signed-in account status

package/dist-skill/docs-dev/coding-best-practices.md

@@ -65,7 +65,7 @@ npm run lint:fix      # auto-fix lint issues
 npm run format        # auto-format all files
 ```
 
-Biome runs as part of `forgecad check suite`. Configuration lives in `biome.json` at the repo root.
+Biome runs as part of `npm run check:suite`. Configuration lives in `biome.json` at the repo root.
 
 ## Self-Review Before Commit
 

package/dist-skill/docs-dev/guides/inspection-bundles.md

@@ -7,9 +7,9 @@ skill-order: 2
 
 `forgecad render inspect` writes a deterministic directory bundle for agents,
 tests, and automation. Use it when a single shaded PNG is too ambiguous and the
-consumer needs geometry-aware signals such as depth, normals, surface roughness,
-part identity, physical connected components, collisions, local thickness, or
-cross-sections.
+consumer needs geometry-aware signals such as depth, normals, Zebra stripes,
+surface roughness, part identity, physical connected components, collisions,
+local thickness, or cross-sections.
 
 ## When To Use It
 
@@ -49,7 +49,7 @@ with patterns such as `Bench.*`.
 
 ## Bundle Layout
 
-A bundle that asks for `--channels rgb,depth,normals,mask,section` has this
+A bundle that asks for `--channels rgb,depth,normals,zebra,mask,section` has this
 layout:
 
 ```text
@@ -71,6 +71,11 @@ model-inspect/
       right.png
       top.png
       iso.png
+    zebra/
+      front.png
+      right.png
+      top.png
+      iso.png
     mask/
       front.png
       right.png
@@ -96,13 +101,15 @@ implemented channel in one bundle:
 
 ```bash
 forgecad render inspect model.forge.js --channels depth,normals
+forgecad render inspect model.forge.js --channels rgb,zebra,normals
 forgecad render inspect model.forge.js --channels rgb,roughness
 forgecad render inspect model.forge.js --channels rgb,mask,collisions
 forgecad render inspect model.forge.js --channels rgb,section,thickness
 ```
 
-Supported channels are `rgb`, `depth`, `normals`, `roughness`, `mask`,
-`connectivity`, `distance`, `collisions`, `thickness`, and `section`.
+Supported channels are `rgb`, `depth`, `normals`, `zebra`, `roughness`, `mask`,
+`connectivity`, `floating`, `distance`, `collisions`, `thickness`, and
+`section`.
 
 ## Channel Semantics
 
@@ -129,6 +136,17 @@ normal = normalize((rgb / 255) * 2 - 1)
 
 Background pixels are black and should be treated as `null`.
 
+`zebra` emits reflective black-and-white stripe renders for visual
+surface-continuity inspection. Stripes are generated from the visible
+camera-view normal and simulated reflection direction, so smooth surfaces show
+smooth flowing bands while normal discontinuities, faceting, and unexpected
+creases kink or break the bands.
+
+Use Zebra with `rgb` and `normals` when judging lofts, fillets, swept surfaces,
+and skin-like forms. It is a human-readable shader diagnostic, not an exact
+curvature-continuity proof; mesh tessellation quality and available smooth
+normals determine how faithfully it represents the underlying surface.
+
 `roughness` emits a mesh-dihedral surface-quality heatmap. Smooth and gently
 curved triangles render as a faint translucent shadow over black, while
 triangles adjacent to sharp, harsh, boundary, or non-manifold mesh edges render
@@ -170,21 +188,58 @@ Connectivity is computed from visible scene objects:
 
 ```text
 bbox candidate = bbox interiors overlap or bbox contact gap <= 0.05 model units
-overlap edge = exact boolean intersection volume > 0.1 model units^3
-component = transitive closure over exact overlap edges
+mesh contact edge = minimum mesh-surface distance <= contactTolerance
+overlap edge = exact boolean intersection volume > 0.1 model units^3 for positive-volume overlap
+component = transitive closure over mesh contact and exact overlap edges
 ```
 
 The manifest stores the edge list, component list, per-object body counts, and
-warnings. Component colors group scene objects; if one scene object contains
-multiple disconnected kernel bodies and the caller supplied a body count, the
-manifest reports `bodyCount > 1` but the PNG cannot color those internal bodies
-separately yet.
+warnings. Component colors group scene objects and mesh body entries. If one
+scene object contains multiple disconnected mesh islands, those islands are
+reported and colored separately as entries such as `Part body 1` and
+`Part body 2`.
+
+Connectivity uses bbox only as a broadphase. Bbox contact alone is not enough to
+merge separate scene objects by default, but mesh surfaces within contact
+tolerance count as physically connected. This keeps concave assemblies such as
+cages and captive balls from being falsely colored as one component while still
+allowing stacked or nearly touching parts to share a component. Use the
+`collisions` channel when you need positive-volume overlap evidence as a defect
+report rather than a component grouping.
+
+`floating` emits one disconnected-body highlight image per view. Black is
+background or ground-reachable geometry. The highlight color marks physical
+components that have no contact path to the ground plane.
+
+Floating body detection splits visible meshes into disconnected body islands,
+links bodies only when their minimum mesh-surface distance is within contact
+tolerance (or exact positive-volume overlap when only shape evidence is
+available), treats any connected component whose lower Z reaches the viewport
+ground plane plus bed tolerance as grounded, then highlights every ungrounded
+component. The default ground plane is the visible model's minimum Z;
+`scene({ ground: { offset } })` moves it below that by the configured offset.
 
-Connectivity uses bbox only as a broadphase. Bbox contact is not enough to merge
-separate scene objects, which keeps concave assemblies such as cages and captive
-balls from being falsely colored as one component. Use the `collisions` channel
-when you need positive-volume overlap evidence as a defect report rather than a
-component grouping.
+```text
+grounded = component bbox minZ <= groundZ + bedTolerance
+floating body = !grounded
+```
+
+This means a `union()` result with two disconnected mesh islands is inspected as
+two separate bodies instead of being treated as one safe object. Bbox overlap or
+bbox face contact alone is not support evidence. Use `connectivity`, `distance`,
+or `collisions` when you need the full physical graph, rooted gap distances, or
+collision defects.
+
+`thickness` emits one local wall-thickness heatmap per view. Black is
+background. Red/orange pixels are below the configured critical/warning
+thresholds, green-to-blue pixels are acceptable/thick, and gray means the local
+raycast could not resolve an opposite surface.
+
+Thickness uses the same physical-contact edges as `connectivity` and `floating`.
+When a ray crosses from one object to a direct physical-contact neighbor, hits
+within `contactTolerance` are treated as contact seams and the ray continues to
+the next surface. This prevents a tiny modeled gap between touching parts from
+being reported as a paper-thin wall.
 
 `distance` emits one rooted physical-component-distance heatmap per view. Black
 is background. Non-black pixels resolve through
@@ -233,6 +288,10 @@ with the ghosted source geometry. If `--focus PartA,PartB` is used, everything
 except those objects is hidden, `PartA` and `PartB` are ghosted, and their
 overlap volume is highlighted if present.
 
+Collision broadphase prunes exact boolean checks when the bbox intersection
+volume is already below the overlap threshold. This does not change findings:
+the real intersection volume cannot exceed the bbox intersection volume.
+
 `thickness` emits one local wall-thickness heatmap per view. The renderer places
 deterministic area-weighted point samples across visible mesh surfaces, casts
 through the object along each sample normal, and colors each point by the first
@@ -316,5 +375,4 @@ per-view depth ranges, and object-mask mappings live.
   guarantee. Open meshes, concave geometry, very coarse tessellation, or low
   `--thickness-samples` values can leave gray/unresolved or approximate regions.
 - Section atlases use five default interior slices today.
-- Zebra/reflection-line inspection is a follow-up channel, not part of the v1
-  bundle.
+- Zebra is a shader-based visual continuity aid, not exact curvature analysis.