forgecad 0.9.13 → 0.9.14

package/dist-skill/CONTEXT.md

@@ -9189,13 +9189,13 @@ Overloads:
 - `offset?: number` — Optional offset along the plane normal (primarily for object-form overload).
 - `exclude?: CutPlaneExcludeInput` — Object names to keep uncut for this plane.
 
-#### `mock()` — Register a mock (context) object for visualization and collision checking.
+#### `mock()` — Register a mock (context) object for visualization and inspection.
 
-Mock objects appear in the viewport and spatial analysis when you run a file directly, but are excluded when the file is imported via [`require()`](/docs/core#require). This lets you model the surrounding context — walls, bolts, mating parts — without polluting the module's exports.
+Mock objects appear in the viewport and inspection analysis when you run a file directly, but are excluded when the file is imported via [`require()`](/docs/core#require). This lets you model the surrounding context — walls, bolts, mating parts — without polluting the module's exports.
 
 The shape is returned unchanged, so you can reference it for alignment, dimensioning, and `verify` checks.
 
-Mock objects participate in `forgecad run --spatial bounded|exact` collision detection and spatial analysis. Their names appear with a `(mock)` suffix in reports.
+Mock objects participate in focused inspection commands such as `forgecad inspect fit interference` and `forgecad inspect physical gaps`. Their names appear with a `(mock)` suffix in reports.
 
 In the viewport, mock objects render at reduced opacity so they are visually distinct from real geometry.
 

package/dist-skill/docs/CLI.md

@@ -32,7 +32,7 @@ forgecad project push
 forgecad project open
 ```
 
-Most CLI commands require a ForgeCAD account. Run `forgecad login` and choose email/password or API token when prompted. Use `FORGECAD_TOKEN=fc_pat_... forgecad <command>` only for CI/CD and one-off automation. `forgecad studio` always requires an explicit project path; use `.` for the current project.
+Local modeling, inspection, export, and skill-install commands do not require a ForgeCAD account. Hosted project sync, publishing, token management, and license activation require sign-in. Run `forgecad login` and choose email/password or API token when prompted. Use `FORGECAD_TOKEN=fc_pat_... forgecad <hosted-command>` only for CI/CD and one-off automation. `forgecad studio` always requires an explicit project path; use `.` for the current project.
 
 You can also start from the hosted starter project with `forgecad project clone start-here`, then `cd start-here` and `forgecad studio .`.
 
@@ -66,13 +66,13 @@ Execute scripts and produce images headless — no browser window. Renders use C
 
 ### `forgecad run`
 
-Execute a Forge script quickly and print the inner-loop build summary: returned objects, verification results, parameters, and timing.
+Execute a Forge script quickly and print the inner-loop build summary: build count, verification results, parameters, and timing.
 
-The fast validation command. Runs your script with the real geometry kernel (no browser needed) and reports whether it built, which objects came back, any `verify.*` results, parameter values, script logs, and elapsed script time. This is the command agents should run frequently while editing a model.
+The fast validation command. Runs your script with the real geometry kernel (no browser needed) and reports whether it built, how many objects came back, any `verify.*` results, parameter values, script logs, and elapsed script time. This is the command agents should run frequently while editing a model.
 
-**Fast by default** — a bare `forgecad run model.forge.js` does not compute per-object volumes, bounding boxes, construction history, feature tallies, spatial relationships, collision intersections, or solver profiles. Those diagnostics are useful, but they are no longer part of the hot path.
+**Fast by default** — a bare `forgecad run model.forge.js` does not compute per-object volumes, bounding boxes, construction history, feature tallies, or solver profiles. Those run diagnostics are useful, but they are no longer part of the hot path.
 
-**Opt-in diagnostics** — use `--details` for volume/bounding-box/object geometry summaries, `--history` for the construction tree, `--features` for feature tallies, or `--solver-profile` for constraint solver timing. Use `--spatial bounded|exact` only when you want directional relationships and collision intersections from the run command itself.
+**Opt-in diagnostics** — use `--details` for volume/bounding-box/object geometry summaries, `--history` for the construction tree, `--features` for feature tallies, or `--solver-profile` for constraint solver timing. Use `inspect fit interference`, `inspect physical gaps`, or `inspect mechanical-integrity --collisions` for spatial and collision evidence.
 
 **Verification results** — runs any `verify.*` checks in the script and reports pass/fail with expected vs actual values. Verification failures remain non-fatal so the model can still render and be inspected.
 
@@ -90,7 +90,6 @@ forgecad run examples/api/static-assembly-connectors.forge.js --focus
 forgecad run examples/api/static-assembly-connectors.forge.js --focus "Bench.Slat*"
 forgecad run examples/api/static-assembly-connectors.forge.js --hide "Bench.Slat0,Bench.Slat1"
 forgecad run examples/api/static-assembly-connectors.forge.js --details --history
-forgecad run examples/api/static-assembly-connectors.forge.js --spatial bounded
 forgecad run examples/products/cup.forge.js --connectivity
 forgecad run examples/products/cup.forge.js --journeys
 forgecad run examples/products/cup.forge.js --backend occt
@@ -100,14 +99,45 @@ forgecad run examples/products/cup.forge.js -p "Wall Thickness=3" -p "Body Heigh
 forgecad run examples/constraints/06-complex-spectrogram.forge.js --solver-debug-out tmp/spectrogram-debug
 ```
 
+### `forgecad ls`
+
+List targetable scene objects for a model.
+
+Runs the model headlessly and prints the exact object paths that CLI tools can target. Use this before focused renders or inspections when object names, groups, or assembly paths are not obvious.
+
+The default output is a compact line-oriented list. Use `--tree` for an indented hierarchy, `--long` for geometry metrics, or `--json` for automation.
+
+```bash
+forgecad ls examples/api/static-assembly-connectors.forge.js
+forgecad ls examples/api/static-assembly-connectors.forge.js --tree
+forgecad ls examples/api/static-assembly-connectors.forge.js Bench
+forgecad ls examples/api/static-assembly-connectors.forge.js "Bench/Slat0" --long
+forgecad ls examples/api/static-assembly-connectors.forge.js --json
+```
+
+### `forgecad show`
+
+Render a quick target-focused viewport PNG.
+
+The main quick visual path for agents. Pass a model and, optionally, a target path from `forgecad ls`; ForgeCAD resolves the target and renders that object or group through the existing viewport renderer. Use `--from` for fast camera directions, or pass the lower-level render camera flags when you need exact reproducibility.
+
+Without a target, `show` renders the whole scene and behaves like a shorter, intent-first wrapper around `render 3d`.
+
+```bash
+forgecad show examples/api/static-assembly-connectors.forge.js
+forgecad show examples/api/static-assembly-connectors.forge.js Bench
+forgecad show examples/api/static-assembly-connectors.forge.js "Bench/Slat0" --from front --out slat-front.png
+forgecad show model.forge.js --camera "proj=perspective;pos=200,-160,120;target=0,0,20;up=0,0,1;fov=38"
+```
+
 ### Object Filtering: `--focus` and `--hide`
 
-Several CLI commands can filter the visible object set without changing model code: `run`, `render 3d`, `render wireframe`, `inspect <family> <mode>`, `capture`, and `check print`.
+Several CLI commands can filter the visible object set without changing model code: `render 3d`, `render wireframe`, `inspect <family> <mode>`, `capture`, and `check print`.
 
-Use `forgecad run model.forge.js --quality live` to list returned object names quickly, then pass those names to `--focus` or `--hide`.
+Use `forgecad ls model.forge.js` to list exact object paths quickly, then pass those names or globs to `--focus` or `--hide` on render and inspection commands.
 
 ```bash
-forgecad run examples/api/static-assembly-connectors.forge.js --quality live
+forgecad ls examples/api/static-assembly-connectors.forge.js --tree
 forgecad render 3d examples/api/static-assembly-connectors.forge.js bench.png --focus "Bench.*"
 forgecad render 3d examples/api/static-assembly-connectors.forge.js slats.png --focus "Bench.Slat*"
 forgecad inspect fit interference examples/api/static-assembly-connectors.forge.js --focus "Bench.*"
@@ -327,7 +357,7 @@ forgecad render section examples/furniture/01-table.forge.js out/bold.svg --edge
 | `--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\|inspection\|precision\|hybrid\|scan>` | Visual render style (render default: classic; inspect default: inspection) |
-| `--scan-granularity <12-72>` | Scan cells across the scene longest axis |
+| `--scan-granularity <12-144>` | Scan cells across the scene longest axis |
 | `--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 |
@@ -641,7 +671,7 @@ The CLI is free for personal non-commercial use. Pro covers human-operated comme
 | `run`, `dev`, `studio`, `render 3d`, `export stl`, `export 3mf`, `export svg`, `compare 3d`, `check print`, `inspect fit interference`, `inspect mechanical-integrity` for personal non-commercial use | `cut-list`, `export sketch-pdf`, `export step`, `export brep`, `export gcode`, `export sdf`, `export urdf`, `export report`, `export cutting-layout` are free to run for personal non-commercial use; Pro covers human-operated commercial CAD work | `render hq`, `capture gif`, `capture mp4` plus commercial coverage for client/customer work | Backend, hosted, embedded, or application workflows that call ForgeCAD automatically |
 
 ```bash
-forgecad license                    # Check signed-in account status
+forgecad license                    # Check local license status
 forgecad license activate           # Activate Pro for the signed-in account
 forgecad license deactivate         # Remove license
 ```

package/dist-skill/docs/generated/viewport.md

@@ -384,13 +384,13 @@ Overloads:
 - `offset?: number` — Optional offset along the plane normal (primarily for object-form overload).
 - `exclude?: CutPlaneExcludeInput` — Object names to keep uncut for this plane.
 
-#### `mock()` — Register a mock (context) object for visualization and collision checking.
+#### `mock()` — Register a mock (context) object for visualization and inspection.
 
-Mock objects appear in the viewport and spatial analysis when you run a file directly, but are excluded when the file is imported via [`require()`](/docs/core#require). This lets you model the surrounding context — walls, bolts, mating parts — without polluting the module's exports.
+Mock objects appear in the viewport and inspection analysis when you run a file directly, but are excluded when the file is imported via [`require()`](/docs/core#require). This lets you model the surrounding context — walls, bolts, mating parts — without polluting the module's exports.
 
 The shape is returned unchanged, so you can reference it for alignment, dimensioning, and `verify` checks.
 
-Mock objects participate in `forgecad run --spatial bounded|exact` collision detection and spatial analysis. Their names appear with a `(mock)` suffix in reports.
+Mock objects participate in focused inspection commands such as `forgecad inspect fit interference` and `forgecad inspect physical gaps`. Their names appear with a `(mock)` suffix in reports.
 
 In the viewport, mock objects render at reduced opacity so they are visually distinct from real geometry.
 

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

@@ -32,7 +32,7 @@ forgecad project push
 forgecad project open
 ```
 
-Most CLI commands require a ForgeCAD account. Run `forgecad login` and choose email/password or API token when prompted. Use `FORGECAD_TOKEN=fc_pat_... forgecad <command>` only for CI/CD and one-off automation. `forgecad studio` always requires an explicit project path; use `.` for the current project.
+Local modeling, inspection, export, and skill-install commands do not require a ForgeCAD account. Hosted project sync, publishing, token management, and license activation require sign-in. Run `forgecad login` and choose email/password or API token when prompted. Use `FORGECAD_TOKEN=fc_pat_... forgecad <hosted-command>` only for CI/CD and one-off automation. `forgecad studio` always requires an explicit project path; use `.` for the current project.
 
 You can also start from the hosted starter project with `forgecad project clone start-here`, then `cd start-here` and `forgecad studio .`.
 
@@ -66,13 +66,13 @@ Execute scripts and produce images headless — no browser window. Renders use C
 
 ### `forgecad run`
 
-Execute a Forge script quickly and print the inner-loop build summary: returned objects, verification results, parameters, and timing.
+Execute a Forge script quickly and print the inner-loop build summary: build count, verification results, parameters, and timing.
 
-The fast validation command. Runs your script with the real geometry kernel (no browser needed) and reports whether it built, which objects came back, any `verify.*` results, parameter values, script logs, and elapsed script time. This is the command agents should run frequently while editing a model.
+The fast validation command. Runs your script with the real geometry kernel (no browser needed) and reports whether it built, how many objects came back, any `verify.*` results, parameter values, script logs, and elapsed script time. This is the command agents should run frequently while editing a model.
 
-**Fast by default** — a bare `forgecad run model.forge.js` does not compute per-object volumes, bounding boxes, construction history, feature tallies, spatial relationships, collision intersections, or solver profiles. Those diagnostics are useful, but they are no longer part of the hot path.
+**Fast by default** — a bare `forgecad run model.forge.js` does not compute per-object volumes, bounding boxes, construction history, feature tallies, or solver profiles. Those run diagnostics are useful, but they are no longer part of the hot path.
 
-**Opt-in diagnostics** — use `--details` for volume/bounding-box/object geometry summaries, `--history` for the construction tree, `--features` for feature tallies, or `--solver-profile` for constraint solver timing. Use `--spatial bounded|exact` only when you want directional relationships and collision intersections from the run command itself.
+**Opt-in diagnostics** — use `--details` for volume/bounding-box/object geometry summaries, `--history` for the construction tree, `--features` for feature tallies, or `--solver-profile` for constraint solver timing. Use `inspect fit interference`, `inspect physical gaps`, or `inspect mechanical-integrity --collisions` for spatial and collision evidence.
 
 **Verification results** — runs any `verify.*` checks in the script and reports pass/fail with expected vs actual values. Verification failures remain non-fatal so the model can still render and be inspected.
 
@@ -90,7 +90,6 @@ forgecad run examples/api/static-assembly-connectors.forge.js --focus
 forgecad run examples/api/static-assembly-connectors.forge.js --focus "Bench.Slat*"
 forgecad run examples/api/static-assembly-connectors.forge.js --hide "Bench.Slat0,Bench.Slat1"
 forgecad run examples/api/static-assembly-connectors.forge.js --details --history
-forgecad run examples/api/static-assembly-connectors.forge.js --spatial bounded
 forgecad run examples/products/cup.forge.js --connectivity
 forgecad run examples/products/cup.forge.js --journeys
 forgecad run examples/products/cup.forge.js --backend occt
@@ -100,14 +99,45 @@ forgecad run examples/products/cup.forge.js -p "Wall Thickness=3" -p "Body Heigh
 forgecad run examples/constraints/06-complex-spectrogram.forge.js --solver-debug-out tmp/spectrogram-debug
 ```
 
+### `forgecad ls`
+
+List targetable scene objects for a model.
+
+Runs the model headlessly and prints the exact object paths that CLI tools can target. Use this before focused renders or inspections when object names, groups, or assembly paths are not obvious.
+
+The default output is a compact line-oriented list. Use `--tree` for an indented hierarchy, `--long` for geometry metrics, or `--json` for automation.
+
+```bash
+forgecad ls examples/api/static-assembly-connectors.forge.js
+forgecad ls examples/api/static-assembly-connectors.forge.js --tree
+forgecad ls examples/api/static-assembly-connectors.forge.js Bench
+forgecad ls examples/api/static-assembly-connectors.forge.js "Bench/Slat0" --long
+forgecad ls examples/api/static-assembly-connectors.forge.js --json
+```
+
+### `forgecad show`
+
+Render a quick target-focused viewport PNG.
+
+The main quick visual path for agents. Pass a model and, optionally, a target path from `forgecad ls`; ForgeCAD resolves the target and renders that object or group through the existing viewport renderer. Use `--from` for fast camera directions, or pass the lower-level render camera flags when you need exact reproducibility.
+
+Without a target, `show` renders the whole scene and behaves like a shorter, intent-first wrapper around `render 3d`.
+
+```bash
+forgecad show examples/api/static-assembly-connectors.forge.js
+forgecad show examples/api/static-assembly-connectors.forge.js Bench
+forgecad show examples/api/static-assembly-connectors.forge.js "Bench/Slat0" --from front --out slat-front.png
+forgecad show model.forge.js --camera "proj=perspective;pos=200,-160,120;target=0,0,20;up=0,0,1;fov=38"
+```
+
 ### Object Filtering: `--focus` and `--hide`
 
-Several CLI commands can filter the visible object set without changing model code: `run`, `render 3d`, `render wireframe`, `inspect <family> <mode>`, `capture`, and `check print`.
+Several CLI commands can filter the visible object set without changing model code: `render 3d`, `render wireframe`, `inspect <family> <mode>`, `capture`, and `check print`.
 
-Use `forgecad run model.forge.js --quality live` to list returned object names quickly, then pass those names to `--focus` or `--hide`.
+Use `forgecad ls model.forge.js` to list exact object paths quickly, then pass those names or globs to `--focus` or `--hide` on render and inspection commands.
 
 ```bash
-forgecad run examples/api/static-assembly-connectors.forge.js --quality live
+forgecad ls examples/api/static-assembly-connectors.forge.js --tree
 forgecad render 3d examples/api/static-assembly-connectors.forge.js bench.png --focus "Bench.*"
 forgecad render 3d examples/api/static-assembly-connectors.forge.js slats.png --focus "Bench.Slat*"
 forgecad inspect fit interference examples/api/static-assembly-connectors.forge.js --focus "Bench.*"
@@ -327,7 +357,7 @@ forgecad render section examples/furniture/01-table.forge.js out/bold.svg --edge
 | `--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\|inspection\|precision\|hybrid\|scan>` | Visual render style (render default: classic; inspect default: inspection) |
-| `--scan-granularity <12-72>` | Scan cells across the scene longest axis |
+| `--scan-granularity <12-144>` | Scan cells across the scene longest axis |
 | `--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 |
@@ -641,7 +671,7 @@ The CLI is free for personal non-commercial use. Pro covers human-operated comme
 | `run`, `dev`, `studio`, `render 3d`, `export stl`, `export 3mf`, `export svg`, `compare 3d`, `check print`, `inspect fit interference`, `inspect mechanical-integrity` for personal non-commercial use | `cut-list`, `export sketch-pdf`, `export step`, `export brep`, `export gcode`, `export sdf`, `export urdf`, `export report`, `export cutting-layout` are free to run for personal non-commercial use; Pro covers human-operated commercial CAD work | `render hq`, `capture gif`, `capture mp4` plus commercial coverage for client/customer work | Backend, hosted, embedded, or application workflows that call ForgeCAD automatically |
 
 ```bash
-forgecad license                    # Check signed-in account status
+forgecad license                    # Check local license status
 forgecad license activate           # Activate Pro for the signed-in account
 forgecad license deactivate         # Remove license
 ```

package/dist-skill/docs-dev/generated/viewport.md

@@ -384,13 +384,13 @@ Overloads:
 - `offset?: number` — Optional offset along the plane normal (primarily for object-form overload).
 - `exclude?: CutPlaneExcludeInput` — Object names to keep uncut for this plane.
 
-#### `mock()` — Register a mock (context) object for visualization and collision checking.
+#### `mock()` — Register a mock (context) object for visualization and inspection.
 
-Mock objects appear in the viewport and spatial analysis when you run a file directly, but are excluded when the file is imported via [`require()`](/docs/core#require). This lets you model the surrounding context — walls, bolts, mating parts — without polluting the module's exports.
+Mock objects appear in the viewport and inspection analysis when you run a file directly, but are excluded when the file is imported via [`require()`](/docs/core#require). This lets you model the surrounding context — walls, bolts, mating parts — without polluting the module's exports.
 
 The shape is returned unchanged, so you can reference it for alignment, dimensioning, and `verify` checks.
 
-Mock objects participate in `forgecad run --spatial bounded|exact` collision detection and spatial analysis. Their names appear with a `(mock)` suffix in reports.
+Mock objects participate in focused inspection commands such as `forgecad inspect fit interference` and `forgecad inspect physical gaps`. Their names appear with a `(mock)` suffix in reports.
 
 In the viewport, mock objects render at reduced opacity so they are visually distinct from real geometry.
 

package/dist-skill/library/forgecad-3d-reconstruction/SKILL.md

@@ -31,13 +31,13 @@ Do not solve reconstruction by returning `importMesh("reference.stl")` or `impor
    No wrapper script is needed. Use the local checkout CLI:
 
    ```bash
-   node dist-cli/forgecad.js run path/to/source.stl --quality live --details
+   node dist-cli/forgecad.js ls path/to/source.stl --quality live --long
    node dist-cli/forgecad.js render 3d path/to/source.stl /tmp/<slug>-source.png --camera iso --edges thin --size 900
    node dist-cli/forgecad.js inspect visual objects path/to/source.stl /tmp/<slug>-source-objects --camera iso --size 700 --force
    node dist-cli/forgecad.js inspect sections sample path/to/source.stl /tmp/<slug>-source-sections --count 5 --size 700 --force
    ```
 
-   For 3MF sources, `run --details` also prints the source archive's build
+   For 3MF sources, `forgecad run` prints the source archive's build
    items/resource objects with stable refs such as
    `3mf:build:001:object:2`, automatic names, per-item bounding boxes, and
    triangle counts. Use that item table to avoid missing hidden multi-part

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

@@ -60,7 +60,7 @@ Use today's date for the directory. Use the user's current ForgeCAD project when
    - Return the final geometry (single shape, array, or named objects array)
    - Treat `fillet(shape, r)` and `chamfer(shape, r)` as experimental edge treatments: Manifold can produce incorrect results and OCCT can be very slow. Prefer simpler primitive profiles, lower segment counts, targeted edge selectors, and inspection before relying on the result.
 4. Validate — run `forgecad run <file>` to check for errors. For multi-file projects, always validate `main.forge.js`.
-5. Verify geometry — render a multi-angle visual evidence set before final delivery: whole-model context plus agent-chosen orthographic, oblique, underside, or hidden-object views that expose the relevant components and interfaces. Choose camera directions from the model's shape and likely failure modes, not from a fixed recipe. Use those views to look for internals that are accidentally visible, parts that visibly do not fit, floating details, blocked access, missing seats, and unexpected interference. Run `forgecad run --connectivity` when the model has multiple returned objects or visible attachments, run `forgecad debug assembly --fail-on warning` when the script uses `assembly()`, run `forgecad inspect mechanical-integrity <project-or-file> --collisions` before sharing generated mechanical work, and run the targeted `forgecad inspect <family> <mode>` commands that match the task (see Final Acceptance Gate and Render-Verify Loop below). For multi-file projects, render and inspect `main.forge.js`. Collision findings are model work, not FYI: remove unexpected overlaps before delivery.
+5. Verify geometry — render a multi-angle visual evidence set before final delivery: whole-model context plus agent-chosen orthographic, oblique, underside, or hidden-object views that expose the relevant components and interfaces. Choose camera directions from the model's shape and likely failure modes, not from a fixed recipe. Use those views to look for internals that are accidentally visible, parts that visibly do not fit, floating details, blocked access, missing seats, and unexpected interference. Run `forgecad inspect physical components` when the model has multiple returned objects or visible attachments, run `forgecad debug assembly --fail-on warning` when the script uses `assembly()`, run `forgecad inspect mechanical-integrity <project-or-file> --collisions` before sharing generated mechanical work, and run the targeted `forgecad inspect <family> <mode>` commands that match the task (see Final Acceptance Gate and Render-Verify Loop below). For multi-file projects, render and inspect `main.forge.js`. Collision findings are model work, not FYI: remove unexpected overlaps before delivery.
 6. Iterate from visual and inspection feedback — treat every render and inspection bundle as model evidence, not a checkbox. Read the normal PNGs, manifest, and evidence PNGs; convert each unexpected collision, thin region, missing section detail, wrong component count, floating body, distance gap, confusing object-color result, accidentally exposed internal structure, bad fit, or visually unsupported interface into a concrete model edit; then rerun the same targeted evidence pass until the result matches the intended physical component graph.
 
 ## Manufacturing Process Is Not Assumed
@@ -183,7 +183,7 @@ Before telling the user the model is done, prove both technical validity and vis
 1. State the intended physical component graph. Decide whether the final artifact should be one connected component, several intentionally separate components, or a selected assembly plus named ghosts. Then run:
 
    ```bash
-   forgecad run model.forge.js --connectivity
+   forgecad inspect physical components model.forge.js --camera iso
    ```
 
    The reported component count must match the design intent. Treat unexpected islands, accidental fusion, or bbox-only "touching" that does not make physical sense as model bugs.
@@ -292,7 +292,7 @@ For important components, collect both:
 - Context view — neighbors present, proving the part belongs in the final assembly.
 - Focus view — only the relevant objects visible, making small gaps, intersections, missing seats, and floating parts easy to see.
 
-Prefer CLI `--focus` / `--hide` filters, named views, or parameter-selected diagnostic modes over changing production geometry. Use the object names from `node dist-cli/forgecad.js run model.forge.js --quality live` when you are unsure what the filters should target.
+Prefer CLI `--focus` / `--hide` filters, named views, or parameter-selected diagnostic modes over changing production geometry. Use the object paths from `node dist-cli/forgecad.js ls model.forge.js --tree` when you are unsure what the filters should target.
 
 ### Structured inspection bundles
 

package/dist-skill/library/forgecad-reconstruction-benchmark/SKILL.md

@@ -72,13 +72,13 @@ ForgeCAD commands.
    inference.
 
    ```bash
-   ./bin/forgecad run task/reference/<asset> --quality live --details
+   ./bin/forgecad ls task/reference/<asset> --quality live --long
    ./bin/forgecad render 3d task/reference/<asset> outputs/reference.png --camera iso --edges thin --size 900
    ./bin/forgecad inspect sections sample task/reference/<asset> outputs/reference-sections --count 5 --size 700
    ./bin/forgecad inspect section task/reference/<asset> --plane yz --offset 0 --ray width:-50,0:50,0 --size 700
    ```
 
-   For 3MF references, the `run --details` output includes a source structure
+   For 3MF references, the `forgecad run` output includes a source structure
    table with stable `3mf:build:...:object:...` refs, automatic item names,
    per-item bounding boxes, and triangle counts. Treat that table as part of
    the evidence: the final model may be one part or many parts, but you should
@@ -88,7 +88,7 @@ ForgeCAD commands.
    unique probe directory with `result.json`; later you can replay that probe
    against the candidate with `./bin/forgecad inspect replay <result.json>
    --source submission/main.forge.js`.
-   For 3MF references, the `run --details` output includes a source structure
+   For 3MF references, the `forgecad run` output includes a source structure
    table with stable `3mf:build:...:object:...` refs, automatic item names,
    per-item bounding boxes, and triangle counts. Treat that table as part of
    the evidence: the final model may be one part or many parts, but you should

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forgecad",
-  "version": "0.9.13",
+  "version": "0.9.14",
   "description": "Code-first parametric CAD for JavaScript/TypeScript, in the browser and CLI.",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://forgecad.io",
@@ -137,11 +137,6 @@
     "build:skill:forgecad": "node scripts/build-forgecad-skill.mjs",
     "sync:public-skills": "node scripts/sync-public-skills.mjs",
     "build:docs": "node scripts/build-docs-site.mjs",
-    "harbor:reconstruction:refresh": "node scripts/refresh-reconstruction-dataset.mjs",
-    "harbor:reconstruction:check": "node scripts/refresh-reconstruction-dataset.mjs --check",
-    "harbor:reconstruction:smoke": "uvx --from harbor harbor run -p ai-labs/reconstruction/tasks --include-task-name ball-bearing --agent nop --n-concurrent 1 --jobs-dir \"$HOME/Projects/CAD/ForgeCAD-RL-Agent-Runs/harbor/smoke\" --force-build",
-    "harbor:reconstruction:pack-local": "node scripts/pack-reconstruction-local-package.mjs",
-    "harbor:reconstruction:clean-local": "node scripts/pack-reconstruction-local-package.mjs --clean",
     "benchmark:reconstruction": "node scripts/forgecad-internal.mjs benchmark reconstruction",
     "benchmark:reconstruction:list": "node scripts/forgecad-internal.mjs benchmark reconstruction list-tasks",
     "benchmark:reconstruction:import-harbor": "node scripts/forgecad-internal.mjs benchmark reconstruction import-harbor",