forgecad 0.9.5 → 0.9.7

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

@@ -366,7 +366,7 @@ Mock objects appear in the viewport and spatial analysis when you run a file dir
 
 The shape is returned unchanged, so you can reference it for alignment, dimensioning, and `verify` checks.
 
-Mock objects participate in `forgecad run` collision detection and spatial analysis. Their names appear with a `(mock)` suffix in reports.
+Mock objects participate in `forgecad run --spatial bounded|exact` collision detection and spatial analysis. 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/docs-raw/guides/inspection-bundles.md

@@ -26,7 +26,7 @@ cross-sections.
 forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,mask
 forgecad render inspect model.forge.js out/model-inspect --channels rgb,section --force
 forgecad render inspect model.forge.js --channels rgb,mask,section
-forgecad render inspect model.forge.js --channels collisions --focus Bench
+forgecad render inspect model.forge.js --channels collisions --focus "Bench.*"
 forgecad render inspect model.forge.js --channels rgb,mask --hide "Bench.Slat0,Bench.Slat1"
 forgecad render inspect model.forge.js --channels thickness --min-thickness 1.2 --warn-thickness 2.0
 forgecad render inspect channels
@@ -43,7 +43,9 @@ question so heavy analyses do not run unnecessarily.
 `--focus` and `--hide` use the same object-name filtering semantics as
 `forgecad run` and `forgecad render 3d`. A bare `--focus` hides mock objects;
 `--focus name1,name2` emits only matching objects; `--hide name1,name2` removes
-matching objects from an otherwise visible scene.
+matching objects from an otherwise visible scene. Matching is case-insensitive
+and supports `*` / `?` globs, so grouped child objects are usually best matched
+with patterns such as `Bench.*`.
 
 ## Bundle Layout
 
@@ -148,6 +150,12 @@ defects. Use this channel to spot spiky tessellation, accidental faceting,
 jagged boolean residue, and dense sharp-corner regions without losing the
 silhouette of otherwise smooth surfaces.
 
+The channel also writes `channels/roughness/point-cloud.json`. Each point sample
+stores object identity, object-local position, normal, dihedral angle, class,
+RGB color, and represented surface area. The PNG renders those samples over
+muted source geometry so the visual evidence stays point-level instead of
+painting a whole object.
+
 `mask` emits one object-color image per view. Black is background. Non-black
 pixels resolve through `manifest.channels.mask.objects`, which includes object
 index, RGB color, object id, name, group, tree path, and mock flag. Edge pixels
@@ -161,9 +169,9 @@ background. Non-black pixels resolve through
 Connectivity is computed from visible scene objects:
 
 ```text
-bbox overlap edge = bbox interiors overlap
-touching edge = bbox contact gap <= 0.05 model units
-component = transitive closure over overlap/touching edges
+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
 ```
 
 The manifest stores the edge list, component list, per-object body counts, and
@@ -172,8 +180,11 @@ 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.
 
-Connectivity is a fast bbox-neighborhood graph. Use the `collisions` channel
-when you need exact positive-volume boolean overlap evidence.
+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.
 
 `distance` emits one rooted physical-component-distance heatmap per view. Black
 is background. Non-black pixels resolve through
@@ -190,9 +201,15 @@ root = largest component by body count, object count, then bbox volume
 rootDistance = shortest accumulated gap distance from root component
 ```
 
+For large scenes the manifest does not materialize the complete component gap
+graph, because that graph is quadratic in the number of components. The
+`gapEdgeCount` field reports the logical complete-graph edge count used by the
+analysis. `gapEdges` stores a compact evidence subset containing nearest-gap
+and root-parent edges.
+
 The PNG colors components from green at the root/near distances through yellow to
 red at the farthest rooted component. The manifest stores the root component,
-maximum rooted distance, complete component gap edge list, nearest-gap data, and
+maximum rooted distance, compact gap edge evidence, nearest-gap data, and
 shortest-path parent fields. The current v1 metric is bbox-based: it measures air
 gaps between component bounding boxes, not exact closest mesh-surface distance.
 
@@ -209,16 +226,17 @@ collision = boolean intersection volume > 0.1mm^3
 ```
 
 The manifest stores the inspected objects, collision pair names/ids, overlap
-volume, warnings, render style, and each collision finding's `groupIndex`,
-`color`, and `hex`. Exact interior pixels can be matched against
+volume, broadphase counters, warnings, render style, and each collision finding's
+`groupIndex`, `color`, and `hex`. Exact interior pixels can be matched against
 `manifest.channels.collisions.collisions[].color`; antialiased edges may blend
 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.
 
-`thickness` emits one local wall-thickness heatmap per view. The renderer
-samples visible mesh triangles, casts through the object along each triangle
-normal, and colors the surface by the first opposite-surface distance:
+`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
+opposite-surface distance:
 
 ```text
 red    = thickness <= minThickness
@@ -231,7 +249,7 @@ gray   = unresolved sample
 The default thresholds are `minThickness=1.2`, `warnThickness=2.0`, and
 `maxThickness=6.0` model units. Override them with `--min-thickness`,
 `--warn-thickness`, and `--max-thickness`. Use `--thickness-samples` to raise or
-lower the maximum sampled triangles per object.
+lower the maximum thickness point samples per object.
 
 The manifest stores the method, thresholds, palette, object list, per-object
 triangle counts, sampled-triangle counts, minimum, p05, median, mean, maximum,
@@ -239,6 +257,17 @@ critical-area percentage, warning-area percentage, below-warning percentage, and
 unresolved-area percentage. This makes the PNG useful for visual debugging while
 the manifest remains the machine-readable source of truth.
 
+The channel also writes `channels/thickness/point-cloud.json`. Each point sample
+stores object identity, object-local position, normal, measured thickness,
+class, RGB color, and represented surface area. The PNG renders those samples
+over muted source geometry, so local evidence survives even when neighboring
+triangles have very different values.
+
+`roughness` uses the same area-weighted point placement. Point colors are local
+to nearby physical feature edges: smooth tessellation diagonals do not become
+visible roughness lines. Use `--roughness-samples` to raise or lower the maximum
+roughness point samples per object.
+
 `section` emits five interior slices per principal plane. The current slicing
 policy is:
 
@@ -276,8 +305,8 @@ per-view depth ranges, and object-mask mappings live.
   not infer identity from object order alone.
 - Connectivity is object-level. It reports disconnected kernel bodies in the
   manifest, but the PNG does not split a single scene object into per-body colors.
-- Bbox contact is intentionally simple and may over-connect concave shapes whose
-  bounding boxes touch while surfaces do not. Boolean-overlap edges are exact.
+- Bbox contact is only broadphase evidence and does not merge separate scene
+  objects by default. Boolean-overlap edges are exact.
 - Distance is a physical-component bbox-gap metric in v1, not exact nearest
   mesh-surface distance. Concave components and loose bounding boxes can make the
   reported gap smaller than the real closest-surface distance.

package/dist/docs-raw/platform/auth.md

@@ -75,6 +75,8 @@ FORGECAD_TOKEN=fc_pat_... forgecad project push
 
 Passing the token directly as `forgecad login --token fc_pat_...` is accepted for non-interactive setup, but the interactive prompt is preferred so tokens do not land in shell history.
 
+For local development or self-hosted experiments, `forgecad login --server <url>` accepts a clean server origin only. Use HTTPS for remote servers; plain HTTP is accepted only for localhost. License activation remains tied to forgecad.io accounts.
+
 ---
 
 ## API Endpoints

package/dist/docs-raw/platform/google-oauth-setup.md

@@ -39,6 +39,10 @@ This is what users see when they click "Sign in with Google."
 
 ## 3. Create OAuth Credentials
 
+Use the Google Auth Platform / Credentials page for ForgeCAD web sign-in.
+The `gcloud iam oauth-clients` command is for IAM/IAP OAuth application
+resources and is not the right client type for this app's Google Sign-In flow.
+
 1. In the left sidebar: **APIs & Services → Credentials**
 2. Click **+ Create Credentials → OAuth client ID**
 3. **Application type**: Web application

package/dist/docs-raw/runbook.md

@@ -25,7 +25,7 @@ For platform feature docs (auth, projects, sharing, admin, email) see [platform/
 | SSH to production | `ssh hetzner` |
 | Open observability UI | Connect to Tailscale, then open `http://100.118.68.93:3000` |
 | Check observability stack | `bash scripts/prod/observability-status.sh` |
-| Roll back bad web deploy | `kamal rollback <VERSION>` |
+| Roll back bad web deploy | `npm run prod:rollback -- <VERSION>` |
 | Verify npm tarball in Docker | `npm run release:docker:all` |
 
 ---
@@ -375,13 +375,13 @@ user flows, roll back to the previous healthy web version immediately:
 
 ```bash
 ssh hetzner 'docker ps -a --format "{{.Names}}\t{{.Status}}" | grep "^forgecad-web-" | sed -E "s/^forgecad-web-([a-f0-9]+)(_replaced_[^[:space:]]+)?\t/\1\t/"'
-kamal rollback <VERSION>
+npm run prod:rollback -- <VERSION>
 ```
 
 Example:
 
 ```bash
-kamal rollback db9c49b058aaa379d9d622456cb249f9b0ddc335
+npm run prod:rollback -- db9c49b058aaa379d9d622456cb249f9b0ddc335
 ```
 
 After rollback, verify a real user-facing path, not just `/api/health`. For

package/dist/docs-raw/skills/forgecad-make-a-model.md

@@ -1,6 +1,6 @@
 # forgecad-make-a-model
 
-Create new ForgeCAD (.forge.js) models in the active CAD project. Handles file placement, invokes the forgecad skill for API guidance, and validates the result.
+Create manufacture-realistic prototype ForgeCAD (.forge.js) models in the active CAD project. Handles file placement, invokes the forgecad skill for API guidance, and validates the result.
 
 | Field | Value |
 | --- | --- |
@@ -13,6 +13,17 @@ Create new ForgeCAD (.forge.js) models in the active CAD project. Handles file p
 
 Create new ForgeCAD models in the user's active ForgeCAD project.
 
+### Default Output Standard
+
+Unless the user explicitly asks for a rough blockout, toy, pure visual study, mass-production release package, or specific manufacturing process, the output is a **manufacture-realistic prototype**.
+
+That means the model should look and behave like a serious prototype someone could fabricate, buy parts for, assemble, inspect, and iterate in a real shop or product lab. It is not a casual concept sketch, not a universal 3D-printing exercise, and not a claim of certified production readiness.
+
+- Choose processes that fit the artifact: machined, sheet-metal, tube, wood/composite, laser-cut, molded-look prototype, printed, or hybrid purchased-hardware construction as appropriate.
+- Include prototype-real features: wall thickness, fastener stacks, bosses, ribs, flanges, bends, seats, bushings, gaskets, cable exits, service access, toleranced clearances, and believable purchased parts.
+- Use production cues only when they help prototype realism. Do not invent expensive production tooling details, certification claims, or safety ratings unless the user asked for that level.
+- If the user asks for `production-realistic`, push toward manufacturing DFM and production-intent materials. If they ask for `printable`, make the selected printed parts honest. If they ask for `visual-CAD`, keep it clearly visual rather than pretending it is build-ready.
+
 ### File Placement
 
 All new `.forge.js` files go under the date-based directory structure:
@@ -40,6 +51,7 @@ Use today's date for the directory. Use the user's current ForgeCAD project when
 1. Load the ForgeCAD skill — always invoke the `forgecad` skill first to get API docs and authoring guidance. Read at minimum the Core API reference. If any two parts are intended to touch or mate in the final model, read the positioning guide immediately and default to connectors + `matchTo()`.
 2. Create the directory — `mkdir -p YYYY/MM/DD/[folder]` as needed.
 3. Write the model — create the `.forge.js` file(s) following ForgeCAD conventions:
+   - Treat the default build profile as `manufacture-realistic prototype`; choose and encode the artifact's manufacturing/process cues before adding styling detail
    - Declare `param()` / `boolParam()` for all tunable dimensions
    - If the model is split across files, use `main.forge.js` as the primary entry point, import renderable parts from neighboring `.forge.js` files, and keep only pure helpers/constants in plain `.js` modules
    - When there are multiple versions of the same object, expose the version as a choice parameter and render one selected version at a time
@@ -52,12 +64,12 @@ 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 the result, run `forgecad run --connectivity` when the model has multiple returned objects or visible attachments, and run `forgecad render inspect` with the relevant channels for the task (see Final Acceptance Gate and Render-Verify Loop below). For multi-file projects, render and inspect `main.forge.js`.
+5. Verify geometry — render the result, 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 `forgecad render inspect` with the relevant channels for the task (see Final Acceptance Gate and Render-Verify Loop below). For multi-file projects, render and inspect `main.forge.js`.
 
 ### Manufacturing Process Is Not Assumed
 
 Do not interpret every ForgeCAD model as a printable object.
-Choose the manufacturing/process cues that fit the artifact unless the user explicitly asked for a specific process.
+Choose the manufacturing/process cues that fit the artifact unless the user explicitly asked for a specific process. A manufacture-realistic prototype can be CNC-machined, bent sheet, tube-and-plate, wood/composite, molded-look low-volume, printed, or hybrid; the right answer depends on the load path and operating story.
 
 - For rideable products such as scooters, bikes, skateboards, carts, or mobility-adjacent devices, use realistic metal/composite/wood structural members, purchased wheels/bearings/axles/brakes/grips, and standard hardware unless the user asked for a printable toy/model.
 - For furniture and load-bearing structures, consider wood, sheet goods, tube, metal brackets, conventional joinery, and printed parts only where they are honest secondary components.
@@ -109,6 +121,52 @@ Do not reveal hidden structure by permanently cutting away the production geomet
 
 When internals are hidden by the final exterior, verify them with exploration tools instead of changing the artifact: render underside or alternate camera views, use `render inspect` section channels, use viewer-only cut planes or explode controls, temporarily make a shell transparent, or add named ghost objects for fit checks. Those views are diagnostic/presentation modes; they must not replace the real model unless the user explicitly asked for a cutaway teaching model.
 
+### Mechanical Assembly Contract
+
+For mechanical models, a ForgeCAD script is not done when it merely looks assembled. Every visible piece must have a believable physical reason to be where it is: fused material, contact faces, a screw stack, a pin in a bore, a tab in a slot, a gasket on a land, a bearing in a seat, a cable in a channel, or a named intentional ghost.
+
+- For bespoke fixed assemblies that do not match an existing `lib.*` helper, start from `examples/api/static-assembly-connectors.forge.js`: build each part in local coordinates, pick one root part, place every other touching part with `matchTo()`, and verify the mate with `verify.connectorDistance(...)`. Do not use final `translate()` calls as assembly contracts.
+- If you use `assembly().addPart()`, do not treat `addFixed()`, `addRevolute()`, or `addPrismatic()` with a manual `frame: Transform.identity().translate(...)` as a physical contract. Manual joint frames are acceptable only as a temporary scaffold. Before delivery, convert mating interfaces to connectors with `connect()` / `match()` where the interfaces physically meet, or prove the manual joint with `forgecad debug assembly --fail-on warning` and documented geometry.
+- A named assembly part should not contain unintentional disconnected bodies. If a "cover plate" contains floating pull tabs, loose screw heads, or a separate gasket, either boolean-join the manufactured features, model the fasteners/seals as separate named parts, or provide the receiving holes/lands that explain the separation.
+- Screws are not decoration. A screw needs a clearance/counterbore in the cover, a receiving threaded hole/boss or through stack in the parent, enough material around both, and aligned axes from one shared bolt pattern.
+- Handles and levers need a load path. Model the hub-to-arm connection, pivot pin/bore, thrust washers or shoulders, stops/detents where relevant, and the connected follower/contact surface. A handle tangent to a hub is a failed mechanism.
+- Covers, doors, cartridges, and service panels need seats. Model ledges, gasket grooves, bosses, snap hooks, tabs, or hinge barrels, then show how the removable part is retained.
+- Cables, wires, and tubes need receiving geometry. Model a gland, grommet, clamp, socket, ferrule, routed channel, or hose barb; do not let a cylinder end in open space.
+- Purchased loose parts may remain separate bodies, but they should be named as purchased hardware or consumables and should sit in believable sockets, bores, races, guides, or fastener stacks.
+- Encode interface intent with `verify.*`, not only comments. Use `verify.clearanceBetween("cover is seated on gasket", cover, gasket, -0.01, 0.05)` for contact/seated fits and clearance bands, `verify.minClearance(...)` or `verify.notColliding(...)` for keep-out/running gaps, and `verify.connectorDistance(...)` for connector-authored mates. Part counts and generic dimensions are useful supporting checks, but they do not prove an interface by themselves.
+
+For ordinary removable covers, prefer `lib.boltedServiceCover(...)` before hand-placing plates, tabs, screw heads, gaskets, and holes. It creates the parent ledge, gasket, cover plate with fused pull tabs, shared bolt pattern, and installed screws as one mechanically accountable interface.
+
+For electronics boxes, backplates, service-stack housings, and camera/monitor enclosures, prefer `lib.datumEnclosureAssembly(...)` before independently placing panels, ribs, bosses, ports, covers, and screws. It creates the tray, ledges, standoffs, ribs, service port, gasket, cover, and screws from one shared datum system.
+
+For PCB-mounted terminal blocks, thermostat backplates, control boards, and wire-entry electronics panels, prefer `lib.pcbTerminalBlockAssembly(...)` before placing a loose green block near a board or cover. It creates the backplate, fused standoffs, PCB mounting screws, PCB pin holes, terminal pins, and seated purchased terminal block from one shared datum system.
+
+For snap-retained covers, cartridges, small clasps, and housings, prefer `lib.snapLatchCoverAssembly(...)` before drawing decorative snap tabs. It creates latch windows, underside catch lands, fused snap hooks, barbs, and clearance checks so the cover is retained by real geometry.
+
+For ordinary pinned handles, cam levers, release levers, and latch arms, prefer `lib.pinnedLeverAssembly(...)` before hand-placing a hub, arm, washers, and pin. It creates a fused lever body, aligned pivot bore, retained pin, thrust washers, support land, and low stop land as one mechanically accountable pivot stack.
+
+For trunnions, side knobs, adjustable pivots, and clamp shafts, prefer `lib.retainedShaftAssembly(...)` before hand-placing rods, washers, and knobs. It creates bored support cheeks, a through shaft, thrust washers, knobs, retaining heads, and shared bore dimensions as one mechanically accountable stack.
+
+For thumb screws, desk clamps, vise screws, capo pressure screws, and small fixture hold-downs, prefer `lib.thumbScrewClampAssembly(...)` before hand-placing a knob, screw cylinder, pressure pad, and bracket jaw. It creates the C-frame, threaded boss/bore, captive pressure pad, hand knob, and seated workpiece contact from one shared datum system.
+
+For drawer slides, quick-release plates, and guided linear carriages, prefer `lib.capturedLinearSlide(...)` before hand-placing rails and a block. It creates a U-channel rail with return lips, end stops, a captured carriage, and explicit travel/clearance dimensions.
+
+For pump cartridges, filter cassettes, battery cartridges, skeg cassettes, and removable slide-in modules, prefer `lib.capturedCartridgeGuideAssembly(...)` before placing a loose tray and block. It creates return lips, a rear stop, a captured cartridge flange, pull tab, insertion travel, and explicit clearance dimensions.
+
+For molded flexible battery doors, sample covers, blister latches, and polypropylene-style service flaps, prefer `lib.livingHingeCoverAssembly(...)` before drawing two plates with a decorative hinge strip. It creates one fused molded strip with fixed leaf, thin flexible web, moving cover leaf, pull lip, snap barb, catch land, and web-thickness checks.
+
+For doors, barn-door leaves, lids, locket leaves, and small hinged access panels, prefer `lib.knuckledHingeAssembly(...)` before hand-placing barrels and a pin. It creates alternating fused knuckles, two leaves, a shared bore, and a retained pin as one mechanically accountable hinge.
+
+For crank links, damper rod ends, crossheads, and clevis-yoke pivots, prefer `lib.clevisPinJointAssembly(...)` before hand-placing an eyelet and pin. It creates bored clevis ears, a captured center link eye, a rear bridge, and a retained pin as one mechanically accountable load path.
+
+For bearings, rollers, burr cartridges, spindle supports, and purchased radial bearings, prefer `lib.seatedBearingAssembly(...)` before hand-placing a ring and shaft near a block. It creates a bored housing, counterbore pocket, bearing shoulder, seated bearing, shaft, collars, and shared clearance dimensions as one mechanically accountable support.
+
+For cables, wires, hoses, pump tubes, and panel pass-throughs, prefer `lib.cableGlandAnchorAssembly(...)` before hand-placing a loose cylinder near a wall. It creates the panel clearance hole, hollow gland body, compression nut, and routed cable/tube as one mechanically accountable pass-through.
+
+For routed cables, wires, hoses, pump tubes, and sensor leads that run along a surface, prefer `lib.routedTubeClipAssembly(...)` before drawing a tube that floats between endpoints. It creates a base panel, saddle clip bores, clip screw holes, installed screws, and the retained tube route from one shared datum system.
+
+For fluid hoses, pump inlets/outlets, filter ports, and lab tubing, prefer `lib.hoseBarbPortAssembly(...)` before drawing a tube that stops at a block. It creates the bored receiver, raised boss, hollow barbed fitting, installed hose, and clamp band as one accountable hose-port interface.
+
 ### Final Geometry Should Be Physically Plausible
 
 Treat each returned part as real matter occupying space. In the final build, separate parts should not intersect unless the intersection is the actual manufacturing intent, such as a welded/fused region, an overmolded insert, or a boolean-unioned solid that is no longer a separate part.
@@ -117,7 +175,9 @@ Do not use final interpenetration as a placement shortcut. For joints and interf
 
 Temporary collisions during construction are fine when they are part of how the model is made or verified: oversized cutter solids before `difference()`, overlapping primitives before `union()`, transparent ghost parts for fit checks, or exploratory joint layouts. Those temporary bodies should be consumed, hidden, named as ghosts, or isolated with inspection filters so final collision findings stay meaningful.
 
-Before delivery on any multi-part, internal, or mechanical model, run the collision inspection, read the collision channel PNGs, and check `manifest.json`. Fix unexpected overlaps. If a collision is intentional, document it in the model naming/comments or isolate that inspection with `--focus` / `--hide` so the remaining collision report proves the final assembly is real.
+If a final overlap is real manufacturing intent, document the exact visible object pair with `verify.intentionalOverlap("rubber grip is overmolded on handle core", rubberGrip, handleCore, "overmolded bonded grip")`. Use this only for welded, fused, overmolded, cast-in, potted, or bonded matter. The mechanical-integrity gate honors it only when the same visible object pair has a confirmed exact collision; unused or non-visible declarations still fail.
+
+Before delivery on any multi-part, internal, or mechanical model, run the collision inspection, read the collision channel PNGs, and check `manifest.json`. Fix unexpected overlaps. If a collision is intentional, declare the exact visible pair with `verify.intentionalOverlap(...)` or isolate that inspection with `--focus` / `--hide` so the remaining collision report proves the final assembly is real.
 
 ### Final Acceptance Gate
 
@@ -131,6 +191,24 @@ Before telling the user the model is done, prove both technical validity and vis
 
    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.
 
+   If the script uses `assembly()`, also run:
+
+   ```bash
+   forgecad debug assembly model.forge.js --fail-on warning
+   ```
+
+   Fix warnings about multiple roots, manual joint contracts, disconnected bodies inside parts, unused connectors, solve warnings, and collisions before delivery. If a warning is truly intentional, rename the part or add a short code comment so a reviewer can see the physical reason.
+
+   For generated mechanical projects or batches, also run:
+
+   ```bash
+   forgecad inspect mechanical-integrity . --collisions
+   ```
+
+   This is the shareability gate. It fails on missing `verify.*` checks, missing mechanical-interface verification, fragmented named groups, uncontracted manual assemblies, positive-volume object collisions, timeouts, and runtime failures. Do not share a generated mechanical model while this gate is red unless the user explicitly asked for a rough concept/blockout.
+
+   The model should include at least one verification that proves a mechanical interface, not just object count. Prefer checks such as `verify.clearanceBetween("bearing is seated in pocket", bearing, housing, -0.01, 0.1)`, `verify.minClearance("carriage clears rail", carriage, rail, 0.15)`, `verify.notColliding("cover screw clears parent hole", screw, parent)`, or `verify.connectorDistance("leg connector is seated", bench, "Rail.leg_0", "Leg0.head", 0, 0.01)`.
+
 2. Run a collision bundle and read both the manifest and images:
 
    ```bash
@@ -245,13 +323,14 @@ return [
 
 This immediately reveals: does it fit? Does it collide with walls? Does the shaft clear the opening?
 
-#### Use console.log for dimension checks
+#### Use verify for acceptance, console.log for traces
 
-Print derived dimensions and clearances to verify arithmetic before rendering:
+Use `verify.*` for dimensions and clearances that decide whether the model is acceptable. Use `console.log()` only for explanatory traces that help you read the run output.
 
 ```js
-console.log("wall remaining:", ((outerW - slotW) / 2).toFixed(1));  // must be > 0
-console.log("hole clearance from edge:", (flangeW/2 - holeX - holeDia/2).toFixed(1));
+verify.greaterThan("wall remains around slot", (outerW - slotW) / 2, 1.6);
+verify.greaterThan("hole clears flange edge", flangeW / 2 - holeX - holeDia / 2, 2.0);
+console.log("wall remaining:", ((outerW - slotW) / 2).toFixed(1));
 ```
 
 Output appears under "Script output:" in `forgecad run`.

package/dist/docs-raw/skills/forgecad-prepare-prompt.md

@@ -1,6 +1,6 @@
 # forgecad-prepare-prompt
 
-Turn a fuzzy physical product, mechanism, or CAD artifact request into a concrete ForgeCAD build brief and a single master prompt for the modeling pass. Use when the engineering brief is incomplete, manufacturing/process choice is underspecified, or the work needs a specific operating story to avoid generic toy solutions.
+Turn a fuzzy physical product, mechanism, or CAD artifact request into a concrete manufacture-realistic prototype ForgeCAD build brief and a single master prompt for the modeling pass. Use when the engineering brief is incomplete, manufacturing/process choice is underspecified, or the work needs a specific operating story to avoid generic toy solutions.
 
 | Field | Value |
 | --- | --- |
@@ -11,7 +11,7 @@ Turn a fuzzy physical product, mechanism, or CAD artifact request into a concret
 
 ## Prepare ForgeCAD Prompt
 
-Use this skill before modeling when the user wants something physically real, manufacturing-aware, and buildable, but their request sounds like:
+Use this skill before modeling when the user wants something physically real, manufacturing-aware, and buildable as a manufacture-realistic prototype, but their request sounds like:
 
 - "make me a robot gripper"
 - "design a real mechanism"
@@ -30,6 +30,10 @@ Choose the manufacturing/process stack from the artifact family, load path, scal
 For example: scooters, bikes, skateboards, and rideable vehicles usually point toward metal/composite frames, wood/composite decks, urethane/rubber wheels, bearings, brakes, and standard hardware; furniture often points toward wood, sheet goods, tube, metal brackets, or conventional joinery; enclosures may point toward injection molding, sheet metal, CNC, or printing depending on quantity and ruggedness; fixtures may be machined, laser-cut, welded, printed, or hybrid.
 If the user asks for "printable", "3D printed", "laser cut", "CNC", or another process, honor that process while still warning when it is unsafe or dishonest for the duty.
 
+The default output posture is **manufacture-realistic prototype** unless the user asks for a different posture.
+This means a serious prototype build candidate with real manufacturing cues, purchased-part boundaries, assembly logic, and validation loops. It is stronger than a visual concept or hobby sketch, but it does not claim final production tooling, certification, rider safety, medical compliance, or release-ready DFM.
+Use `production-realistic` only when the user wants production intent, `printable` only when printing is actually the selected process, and `visual-CAD` only for visual/form studies.
+
 Do not let the modeling prompt sound like a casual hobby sketch when the requested artifact belongs to a serious product domain.
 Give the model a specific operating story: a named company or lab, named program, named prototype/revision, review moment, test setting, and concrete reason the part matters.
 If the user did not provide this story, invent plausible non-famous names and details.
@@ -66,6 +70,7 @@ By the end of this skill, there should be:
 - an artifact family classification
 - an assumption bundle with units
 - a clear build profile and manufacturing/process stack
+- a stated output posture, defaulting to manufacture-realistic prototype unless the user chose otherwise
 - a specific operating story
 - a motion / load / size target
 - a BOM boundary
@@ -129,8 +134,9 @@ By the end of this skill, there should be:
 
 4. Choose manufacturing/process posture.
    Treat process selection as part of the brief.
-   Use `production-realistic`, `prototype-realistic`, `printable`, `visual-CAD`, or a more specific process such as `sheet-metal`, `CNC-machined`, `laser-cut`, `welded tube`, `injection-molded`, `cast`, or `hybrid purchased-hardware`.
-   Default to the posture that is honest for the artifact rather than the easiest CAD surface to make.
+   Default to `manufacture-realistic prototype`.
+   Use `production-realistic`, `prototype-realistic`, `printable`, `visual-CAD`, or a more specific process such as `sheet-metal`, `CNC-machined`, `laser-cut`, `welded tube`, `injection-molded`, `cast`, or `hybrid purchased-hardware` only when the brief justifies that more specific posture.
+   Choose the posture that is honest for the artifact rather than the easiest CAD surface to make.
 
 5. Pick qualitative levers, not raw numbers.
    Start from:
@@ -146,7 +152,7 @@ By the end of this skill, there should be:
    - for a gripper: object style, opening band, cost/performance posture
    - for a table: use style, span band, load style
    - for an enclosure: electronics size, ruggedness, cooling posture
-   - for an underspecified product: production-realistic, prototype-realistic, printable, or visual-CAD posture
+   - for an underspecified product: manufacture-realistic prototype, production-realistic, printable, or visual-CAD posture
 
 7. Convert choices into an engineering brief.
    The brief must include:
@@ -156,6 +162,7 @@ By the end of this skill, there should be:
    - production reason
    - test setting
    - what generic output would miss
+   - output posture, defaulting to manufacture-realistic prototype unless changed by the user
    - intended objects / loads
    - rough size envelope
    - motion style and degrees of freedom
@@ -189,7 +196,7 @@ Good:
 - "Which target feels closest: a light desk demo, a useful hobby tool, or a sturdier bench mechanism?"
 - "Will it mostly handle soft/light things, mixed household parts, or rigid/tool-like objects?"
 - "Should we bias for cheapest parts, balanced practicality, or stronger hardware?"
-- "Should this be production-realistic, prototype-realistic, printable, or just a visual CAD study?"
+- "Should this be a manufacture-realistic prototype, production-realistic, printable, or just a visual CAD study?"
 - "Is this more like a gripper, a fixture, an enclosure, a chassis, or furniture?"
 - "Will the table mostly hold decor, laptop-and-books, or workshop abuse?"
 
@@ -206,6 +213,7 @@ If the user says "I don't know" or gives only a broad goal:
 - infer the nearest artifact family from the request
 - invent a specific operating story for the artifact
 - infer the manufacturing/process stack from the artifact family and operating story
+- default the output posture to `manufacture-realistic prototype`
 - choose `general-duty`
 - choose `medium`
 - choose `balanced`

package/dist/docs-raw/skills/forgecad-render-inspect.md

@@ -163,7 +163,7 @@ PNG review order:
 ### Interpretation Rules
 
 - Collision findings are positive-volume boolean overlaps. Face-touching is not a collision.
-- Connectivity is a fast bbox-neighborhood component graph. Concave shapes can over-connect through bounding boxes; use the collisions channel for exact overlap evidence.
+- 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.
 - 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.
 - Depth is a visual heatmap, not raw floating-point depth data.

package/dist/docs-raw/skills/index.md

@@ -14,8 +14,8 @@ forgecad skill install
 | [forgecad-high-level-spec](/docs/skills/forgecad-high-level-spec) | `forgecad skill install` | Write a high-level design document (HLD) for a model, mechanism, or assembly before detailed specification or coding. Use when starting a new design, rethinking an existing one, or when the user asks to spec out, plan, or think through a model at a high level. Works backwards from requirements — defines the problem, explores alternatives, records decisions. Produces a right-sized design document for review and iteration. |
 | [forgecad-image-replicator](/docs/skills/forgecad-image-replicator) | `forgecad skill install` | Build real ForgeCAD geometry from one or more reference images by treating images as evidence, inferring the object, then validating against both reference-matched and canonical views. |
 | [forgecad-lld](/docs/skills/forgecad-lld) | `forgecad skill install` | Write a Low-Level Design (LLD) for a CAD model — exact dimensions, constraints, parameters, and verification criteria. Use after a High-Level Design (HLD) exists and decisions are locked, or for simple parts that don't need an HLD. The detailed design document that code implements. |
-| [forgecad-make-a-model](/docs/skills/forgecad-make-a-model) | `forgecad skill install` | Create new ForgeCAD (.forge.js) models in the active CAD project. Handles file placement, invokes the forgecad skill for API guidance, and validates the result. |
-| [forgecad-prepare-prompt](/docs/skills/forgecad-prepare-prompt) | `forgecad skill install` | Turn a fuzzy physical product, mechanism, or CAD artifact request into a concrete ForgeCAD build brief and a single master prompt for the modeling pass. Use when the engineering brief is incomplete, manufacturing/process choice is underspecified, or the work needs a specific operating story to avoid generic toy solutions. |
+| [forgecad-make-a-model](/docs/skills/forgecad-make-a-model) | `forgecad skill install` | Create manufacture-realistic prototype ForgeCAD (.forge.js) models in the active CAD project. Handles file placement, invokes the forgecad skill for API guidance, and validates the result. |
+| [forgecad-prepare-prompt](/docs/skills/forgecad-prepare-prompt) | `forgecad skill install` | Turn a fuzzy physical product, mechanism, or CAD artifact request into a concrete manufacture-realistic prototype ForgeCAD build brief and a single master prompt for the modeling pass. Use when the engineering brief is incomplete, manufacturing/process choice is underspecified, or the work needs a specific operating story to avoid generic toy solutions. |
 | [forgecad-project](/docs/skills/forgecad-project) | `forgecad skill install` | ForgeCAD project CLI workflow — creating, managing, syncing projects and files on forgecad.io. Covers init, push, pull, file operations, member management, publishing, and sharing. |
 | [forgecad-render-inspect](/docs/skills/forgecad-render-inspect) | `forgecad skill install` | 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. |
 | [forgecad-visual-spec](/docs/skills/forgecad-visual-spec) | `forgecad skill install` | Turn a concrete ForgeCAD artifact, build brief, HLD, or existing model into builder-honest image prompts for AI image models. Use when the user wants visual-spec renders that show the final product while keeping mechanisms, seams, hardware, and build cues visible instead of drifting into concept art. |

package/dist/index.html

@@ -55,7 +55,7 @@
       * { margin: 0; padding: 0; box-sizing: border-box; }
       html, body, #root { width: 100%; min-height: 100%; background: var(--fc-bg); color: var(--fc-text); font-family: system-ui, -apple-system, sans-serif; }
     </style>
-    <script type="module" crossorigin src="/assets/app-CFy7g5WP.js"></script>
+    <script type="module" crossorigin src="/assets/app-BE2nD6Yz.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/app-CsHnaBWt.css">
   </head>
   <body>

package/dist/sitemap.xml

@@ -2,37 +2,37 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://forgecad.io/</loc>
-    <lastmod>2026-05-16</lastmod>
+    <lastmod>2026-05-19</lastmod>
     <changefreq>weekly</changefreq>
     <priority>1.0</priority>
   </url>
   <url>
     <loc>https://forgecad.io/docs</loc>
-    <lastmod>2026-05-16</lastmod>
+    <lastmod>2026-05-19</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.8</priority>
   </url>
   <url>
     <loc>https://forgecad.io/blog</loc>
-    <lastmod>2026-05-16</lastmod>
+    <lastmod>2026-05-19</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.7</priority>
   </url>
   <url>
     <loc>https://forgecad.io/pricing</loc>
-    <lastmod>2026-05-16</lastmod>
+    <lastmod>2026-05-19</lastmod>
     <changefreq>monthly</changefreq>
     <priority>0.6</priority>
   </url>
   <url>
     <loc>https://forgecad.io/examples</loc>
-    <lastmod>2026-05-16</lastmod>
+    <lastmod>2026-05-19</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.6</priority>
   </url>
   <url>
     <loc>https://forgecad.io/blog/hello-forgecad-io</loc>
-    <lastmod>2026-05-16</lastmod>
+    <lastmod>2026-05-19</lastmod>
     <changefreq>monthly</changefreq>
     <priority>0.5</priority>
   </url>