forgecad 0.9.4 → 0.9.6

package/dist/docs-raw/AI/usage.md

@@ -213,7 +213,6 @@ For the full command reference, see [ForgeCAD CLI](../CLI.md).
 | `forgecad-blockout-model` | Making rough concept geometry to explore proportions, layout, motion envelope, or spatial intuition before detailed modeling. |
 | `forgecad-image-replicator` | Recreating an object from reference images as real ForgeCAD geometry through camera-calibrated render/compare/iterate loops. |
 | `forgecad-render-inspect` | Generating and interpreting `forgecad render inspect` bundles for collision, wall thickness, connectivity, masks, depth, normals, and sections. |
-| `forgecad-api-dogfood` | Building a real model while recording API friction and concrete improvement proposals. |
 | `forgecad-visual-spec` | Producing builder-honest image prompts from a concrete model, HLD, LLD, or build brief. |
 | `forgecad-project` | Managing forgecad.io projects from the CLI: init, clone, pull, push, file commands, members, publish, and shares. |
 

package/dist/docs-raw/API/core/concepts.md

@@ -34,7 +34,7 @@ Top-level declarations such as `const bom = ...`, `let scene = ...`, or `class S
 
 - Scripts re-execute on every parameter change (400ms debounce)
 - Geometry operations are **immutable** — shapes, sketches, groups, imported assemblies, and wood boards return new values instead of modifying in place
-- Must return one of: `Shape`, `Sketch`, `ShapeGroup`, `Assembly`, `SolvedAssembly`, `SdfShape`, `Array` of renderables, `Array` of `{ name, shape?, sketch?, group?, color? }`, or a **metadata object** (see below)
+- Must return one of: `Shape`, `Sketch`, `ShapeGroup`, `Assembly`, `SolvedAssembly`, `SdfShape`, `Array` of renderables, `Array` of `{ name, tags?, shape?, sketch?, group?, color? }`, or a **metadata object** (see below)
 
 Top-level assembly scripts can return an unsolved `Assembly` directly; ForgeCAD solves it at default joint values for display. Return `assembly.solve(state)` when you want a specific pose. Do not call `.toGroup()` just to make an assembly render — use `.toGroup()` only when you specifically need `ShapeGroup` composition, group-style transforms, or named-child lookup.
 
@@ -67,6 +67,16 @@ return {
 };
 ```
 
+Named return objects and named `group(...)` children can include `tags`. Tags are viewport metadata: they do not affect geometry, exports, face labels, or BOM rows, but the command palette can hide, show only, or focus every object with a selected tag.
+
+```javascript
+return [
+  { name: 'Base Plate', tags: ['printed', 'structural'], shape: base },
+  { name: 'M4 Bolt A', tags: 'fastener', shape: boltA },
+  { name: 'M4 Bolt B', tags: 'fastener', shape: boltB },
+];
+```
+
 ## Coordinate System
 
 Z-up right-handed: X = left/right, Y = forward/back, Z = up/down.

package/dist/docs-raw/CLI.md

@@ -113,12 +113,14 @@ forgecad run examples/constraints/06-complex-spectrogram.forge.js --solver-debug
 
 ### `forgecad render`
 
-Render a Forge scene. Use a subcommand — `3d`, `inspect`, `section`, `wireframe`, `sketch`, or `hq`.
+Render a Forge scene. Use a subcommand — `3d`, `inspect`, `views`, `section`, `wireframe`, `sketch`, or `hq`.
 
 `forgecad render` is a group of rendering subcommands. Pick one based on what you want:
 
 - `render 3d` — standard viewport PNG, the usual way to visually verify geometry
 - `render inspect` — machine-readable inspection bundle with geometry channels and a manifest
+- `render inspect channels` — list supported inspection channels
+- `render views` — list named cameras declared with `scene({ views })`
 - `render wireframe` — edges only, no shading
 - `render section` — 2D cross-section cut by a plane (SVG or PNG)
 - `render sketch` — 2D sketch script to PNG
@@ -127,6 +129,8 @@ Render a Forge scene. Use a subcommand — `3d`, `inspect`, `section`, `wirefram
 ```bash
 forgecad render 3d examples/cup.forge.js
 forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,mask
+forgecad render inspect channels
+forgecad render views examples/cup.forge.js
 forgecad render wireframe examples/cup.forge.js
 forgecad render section examples/furniture/01-table.forge.js --plane XZ
 forgecad render hq examples/cup.forge.js --preset dramatic
@@ -138,7 +142,7 @@ Render a Forge scene to PNG using the real viewport renderer.
 
 Launches a headless Chrome instance, renders the scene with the same WebGL viewport as the editor, and saves a PNG. The output path defaults to `<script-name>.png` next to the input file.
 
-Use `--focus` to isolate specific parts (hides everything else) or `--hide` to remove clutter like mock objects. The `--view` flag selects a named camera declared in `scene({ views })`. The `--camera` flag accepts built-in views (`front`, `top`, `iso`), `azimuth:elevation` angles, or an exact `proj/pos/target/up/fov` camera spec — pass `--camera` multiple times to render several viewpoints in one run.
+Use `--focus` to isolate specific parts (hides everything else) or `--hide` to remove clutter like mock objects. The `--view` flag selects a named camera declared in `scene({ views })`. The `--camera` flag accepts built-in views (`front`, `top`, `iso`), `azimuth:elevation` angles, or an exact `proj/pos/target/up/fov` camera spec — pass `--camera` multiple times to render several viewpoints in one run. Use `--camera-json <file>` or `--scene <file>` for exact reproducible viewport cameras without shell escaping.
 
 Use `--edges=<off|thin|bold>` to control the edge overlay. For a pure wireframe look, use `render wireframe` instead.
 
@@ -152,16 +156,29 @@ forgecad render 3d examples/cup.forge.js --hide "wall,bolt"
 forgecad render 3d model.forge.js --view hero
 forgecad render 3d model.forge.js --camera 45:30
 forgecad render 3d model.forge.js --camera "proj=perspective;pos=200,-160,120;target=0,0,20;up=0,0,1;fov=38"
+forgecad render 3d model.forge.js --camera-json camera.json
+forgecad render 3d model.forge.js --scene scene.json
 forgecad render 3d model.forge.js --camera front --camera side
 forgecad render 3d model.forge.js --edges bold
 forgecad render 3d model.forge.js --edges off
 ```
 
+### `forgecad render views`
+
+List named camera views declared by a model with `scene({ views })`.
+
+Runs the script headlessly and prints every named render view with an exact camera spec that can be passed back to `render 3d`, `render hq`, or `capture`.
+
+```bash
+forgecad render views model.forge.js
+forgecad render views model.forge.js --json
+```
+
 ### `forgecad render inspect`
 
 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, 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, 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.
 
 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.
 
@@ -173,6 +190,15 @@ forgecad render inspect examples/api/static-assembly-connectors.forge.js out/ben
 forgecad render inspect examples/api/static-assembly-connectors.forge.js --channels rgb,mask,collisions --hide "Bench.Slat0" --force
 ```
 
+### `forgecad render inspect channels`
+
+List supported inspection bundle channels.
+
+```bash
+forgecad render inspect channels
+forgecad render inspect channels --json
+```
+
 ### `forgecad render wireframe`
 
 Render a Forge scene as a wireframe (edges only, no shading).
@@ -190,13 +216,15 @@ High-quality render via Blender Cycles — path-traced, HDRI, material presets.
 
 Exports the scene to Blender and renders with Cycles (path tracer). Requires Blender installed and on PATH.
 
-Choose a `--preset` for the look: `studio` (neutral product shot), `dramatic` (high-contrast), `clay` (matte, no color), `glass`, `metallic`, `toon`, `xray`, `normals`, `silhouette`, and more. Control quality vs speed with `--samples` (default 256). Use `--transparent` for a transparent background (compositing-ready).
+Choose a `--preset` for the look: `studio` (neutral product shot), `dramatic` (high-contrast), `clay` (matte, no color), `glass`, `metallic`, `toon`, `xray`, `normals`, `silhouette`, and more. Control quality vs speed with `--samples` (default 256). Use `--view`, `--camera`, `--camera-json`, or `--scene <file>` for still camera control, matching `render 3d`. Use `--transparent` for a transparent background (compositing-ready).
 
 Output defaults to `<script-name>-hq.png`. Great for documentation, marketing renders, and social media.
 
 ```bash
 forgecad render hq examples/cup.forge.js
 forgecad render hq examples/cup.forge.js hero.png --preset dramatic --samples 1024
+forgecad render hq examples/cup.forge.js hero.png --view hero
+forgecad render hq examples/cup.forge.js hero.png --camera-json camera.json
 forgecad render hq examples/cup.forge.js --preset clay --size 2048
 forgecad render hq examples/cup.forge.js --transparent --preset glass
 ```
@@ -205,16 +233,20 @@ forgecad render hq examples/cup.forge.js --transparent --preset glass
 
 Animated orbit or joint playback.
 
-Renders an animated sequence by either orbiting the camera around the model or playing back a `jointsView` animation. Use `--capture orbit` (default) for a turntable rotation, `--capture animation --animation <name>` to play a named joints clip, or `--capture section-sweep` to move a clipping plane through the model. Supports `--cut-plane` to animate with a static cross-section visible.
+Renders an animated sequence by either orbiting the camera around the model or playing back a `jointsView` animation. Use `--capture orbit` (default) for a turntable rotation, `--capture animation --animation <name>` to play a named joints clip, or `--capture section-sweep` to move a clipping plane through the model. Supports `--cut-plane` to animate with a static cross-section visible. Use `--view`, `--camera`, `--camera-json`, or `--scene <file>` to choose the orbit base camera or the fixed camera for animations and section sweeps.
 
 ```bash
 forgecad capture gif examples/cup.forge.js
 forgecad capture gif examples/3d-printer.forge.js out/section.gif --cut-plane "Front Section"
 forgecad capture gif model.forge.js out/raw.gif --param "Output=raw-sdf"
+forgecad capture gif model.forge.js out/front.gif --camera front
+forgecad capture gif model.forge.js out/hero.gif --view hero
 forgecad capture gif examples/3d-printer.forge.js out/sweep.gif --capture section-sweep --sweep-plane YZ
 forgecad capture mp4 examples/cup.forge.js
 forgecad capture mp4 examples/api/runtime-joints-view.forge.js out/step.mp4 --capture animation --animation Step
 forgecad capture mp4 model.forge.js out/raw.mp4 --param "Output=raw-sdf"
+forgecad capture mp4 model.forge.js out/front.mp4 --camera front
+forgecad capture mp4 model.forge.js out/hero.mp4 --view hero
 forgecad capture mp4 examples/3d-printer.forge.js out/sweep.mp4 --capture section-sweep --sweep-plane YZ --sweep-frames 180
 ```
 
@@ -247,18 +279,22 @@ forgecad render section examples/furniture/01-table.forge.js out/bold.svg --edge
 | `--focus <names>` | Focus: no arg hides mocks; comma-separated names shows only those |
 | `--hide <names>` | Hide comma-separated object names |
 | `--camera <front\|back\|side\|right\|top\|iso\|az:el\|az:el:dist\|spec>` | Camera preset, spherical (az:el), or full spec such as `proj=perspective;pos=x,y,z;target=x,y,z;up=x,y,z;fov=45`. Repeatable. |
+| `--camera-json <file>` | Exact viewport camera JSON file |
 | `--view <name>` | Named camera view declared by the model with scene({ views }) |
 | `--size <px>` | Image size in pixels |
-| `--scene <json>` | Viewport scene state JSON |
+| `--scene <json\|file>` | Viewport scene state JSON or JSON file |
 | `--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: thin) |
+| `--edges <off\|thin\|bold>` | Edge overlay preset in solid mode (default: off) |
 | `--render-style <classic\|studio\|fast\|glass>` | 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 |
-| `--channels <rgb,depth,normals,mask,connectivity,distance,collisions,thickness,section>` | Required inspection channels to emit; no default |
-| `--quality <default\|live\|high>` | Mesh/render quality |
+| `--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 |
 | `--force` | Replace an existing bundle directory |
 | `--min-thickness <mm>` | Critical thickness threshold in model units |
 | `--warn-thickness <mm>` | Warning thickness threshold in model units |
@@ -276,7 +312,6 @@ forgecad render section examples/furniture/01-table.forge.js out/bold.svg --edge
 | `--frames <n>` | Video frames per revolution |
 | `--fps <n>` | Video frame rate |
 | `--pitch <deg>` | Camera pitch angle in degrees |
-| `--backend <manifold\|occt\|truck>` | Geometry backend |
 | `--format <gif\|mp4>` | Output format |
 | `--capture <orbit\|animation\|section-sweep>` | Capture preset |
 | `--animation <name>` | Named jointsView animation clip |
@@ -330,6 +365,7 @@ forgecad cut-list examples/api/sheet-stock-cut-list.forge.js
 forgecad export cutting-layout examples/api/sheet-stock-cut-list.forge.js --sheet-width 420 --sheet-height 594 --kerf 3
 
 # 3D printing
+forgecad check print bracket.forge.js
 forgecad export stl bracket.forge.js
 forgecad export 3mf bracket.forge.js --quality high
 
@@ -494,11 +530,26 @@ forgecad skill one-file ~/Desktop/forgecad-context.md
 forgecad skill flattened-files ~/Desktop/forgecad-skills
 ```
 
-> **Workflow:** Agent writes the model -> `forgecad run` validates it -> `forgecad render inspect` produces evidence -> `forgecad check params` sweeps the parameter range -> export ships the result. All in the terminal.
+> **Workflow:** Agent writes the model -> `forgecad run` validates it -> `forgecad check print` catches printability risks -> `forgecad render inspect` produces visual evidence -> `forgecad check params` sweeps parameter robustness -> export ships the result. All in the terminal.
 
 ## Validation
 
-Test parameter ranges and run invariant suites.
+Check printability, test parameter ranges, and run invariant suites.
+
+### `forgecad check print`
+
+Run fast 3D-print readiness checks for collisions, mesh health, walls, overhangs, and bed contact.
+
+Runs a Forge script with the headless kernel and emits a slicer-adjacent printability report without launching a browser. The check is designed for agents: JSON is stable, failures name the specific print risk, and the default profile is conservative for FDM PLA on a 0.4mm nozzle.
+
+Checks include script `verify.*` results, exact positive-volume object collisions, physical component count, mesh topology, sampled wall thickness, unsupported overhang budget, and bed-contact area. Use `--json` for automation and `--output` to save the full report while keeping the readable terminal summary.
+
+```bash
+forgecad check print examples/api/attachTo-basics.forge.js
+forgecad check print examples/api/verification-demo.forge.js --json
+forgecad check print model.forge.js --min-wall 1.2 --warn-wall 2
+forgecad check print model.forge.js --expect-components 1 -p "Wall Thickness=3"
+```
 
 ### `forgecad check params`
 
@@ -566,7 +617,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 params`, `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`, `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` |
 
 ```bash
 forgecad license                    # Check signed-in account status

package/dist/docs-raw/beta-operations.md

@@ -36,6 +36,10 @@ All of these are thin wrappers around `scripts/beta.sh` /
 `scripts/beta-local.sh`. They exist for operator ergonomics only; regular
 ForgeCAD users never see them in the public product CLI.
 
+Production has the matching `npm run prod:*` shortcuts in `scripts/prod.sh`
+for the same reason: muscle memory should be environment-prefixed, even though
+production is normally deployed by GitHub Actions on `mainline`.
+
 **Useful overrides**:
 - `FORGE_BETA_DEPLOY_CONFIG` — alternate Kamal config path
 - `FORGE_BETA_DESTINATION` — alternate Kamal destination name (default `beta`)

package/dist/docs-raw/deployment.md

@@ -55,26 +55,25 @@ All containers share the `kamal` Docker network. The web container reaches the b
 
 ```bash
 # Deploy prod web app (zero-downtime rolling update)
-kamal deploy
+npm run prod:deploy
 
 # Deploy prod backend compute server
-kamal deploy -c config/deploy.backend.yml
+npm run prod:deploy:backend
 
 # Deploy both prod services
-kamal deploy && kamal deploy -c config/deploy.backend.yml
+npm run prod:deploy:all
 
 # Deploy the same commit to beta (run BEFORE prod)
-kamal deploy -d beta
-
-# Same flow via the beta operator wrapper
 npm run beta:deploy
+
+# Open the environment after a deploy
 npm run beta:smoke
+npm run prod:smoke
 ```
 
-Recommended flow for a change: merge to `mainline` → `kamal deploy -d beta`
-→ verify on `beta.forgecad.io` → `kamal deploy`
-(prod). See [beta-operations.md](beta-operations.md) for the full beta
-runbook.
+Recommended flow for a change: merge to `mainline` → `npm run beta:deploy`
+→ verify on `beta.forgecad.io` → `npm run prod:deploy`.
+See [beta-operations.md](beta-operations.md) for the full beta runbook.
 
 Kamal builds the Docker image on the server via SSH (`builder: remote:`), pushes to GHCR, pulls on the server, starts the new container, waits for healthcheck, switches traffic, stops old container. Zero downtime.
 
@@ -90,16 +89,16 @@ Push to `mainline` triggers `.github/workflows/deploy.yml` which runs `kamal dep
 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/"'
 
 # Roll the web app back to the last known-good version:
-kamal rollback <VERSION>
+npm run prod:rollback -- <VERSION>
 
 # Backend rollback:
-kamal rollback -c config/deploy.backend.yml <VERSION>
+npm run prod:rollback:backend -- <VERSION>
 ```
 
 Example:
 
 ```bash
-kamal rollback db9c49b058aaa379d9d622456cb249f9b0ddc335
+npm run prod:rollback -- db9c49b058aaa379d9d622456cb249f9b0ddc335
 ```
 
 Use the most recent healthy version from the `docker ps -a` output above. The
@@ -126,10 +125,22 @@ version is the hex suffix in the Kamal container name, e.g.
 
 ## Operator Shortcuts
 
-Routine beta admin work is wrapped by repo-local scripts so the flow stays
-safe and memorable without changing the public ForgeCAD user CLI:
+Routine production and beta admin work is wrapped by repo-local scripts so the
+flow stays safe and memorable without changing the public ForgeCAD user CLI:
 
 ```bash
+npm run prod:deploy
+npm run prod:smoke
+npm run prod:deploy:backend
+npm run prod:deploy:all
+npm run prod:rollback -- <VERSION>
+npm run prod:logs
+npm run prod:logs:backend
+npm run prod:shell
+npm run prod:db
+npm run prod:health
+npm run prod:errors -- web 1000
+
 npm run beta:setup
 npm run beta:deploy
 npm run beta:smoke
@@ -142,6 +153,10 @@ npm run beta:local
 `FORGE_ENVIRONMENT=beta` backend on localhost, so you can open the browser and
 judge the UX without touching Cloudflare.
 
+These package scripts are thin wrappers around `scripts/prod.sh`,
+`scripts/beta.sh`, and Kamal. Use raw Kamal commands when debugging Kamal
+itself; otherwise prefer the environment-prefixed shortcuts.
+
 ---
 
 ## Environment Variables
@@ -267,10 +282,10 @@ Use the observability stack first for incidents:
 SSH access: `ssh hetzner` (see `~/.ssh/config`).
 
 ```bash
-# Kamal commands (run from project root locally)
-kamal app logs                                     # web app logs
-kamal app logs -c config/deploy.backend.yml        # backend logs
-kamal app exec -i bash                             # shell into web container
+# Kamal-backed commands (run from project root locally)
+npm run prod:logs                                  # web app logs
+npm run prod:logs:backend                          # backend logs
+npm run prod:shell                                 # shell into web container
 kamal proxy details                                # proxy routing info
 
 # Direct SSH
@@ -281,10 +296,10 @@ ssh hetzner "df -h / && free -h"
 ### Production scripts
 
 ```bash
-bash scripts/prod/health.sh                # containers, disk, memory
-bash scripts/prod/logs.sh [lines] [pattern]  # app logs
-bash scripts/prod/errors.sh [lines]        # error logs only
-bash scripts/prod/db.sh "SELECT ..."       # run SQL query
+npm run prod:health                        # containers, disk, memory
+npm run prod:errors -- web 1000            # error logs only
+npm run prod:db                            # interactive psql via Kamal
+bash scripts/prod/db.sh "SELECT ..."       # one-shot SQL query
 ```
 
 ### Email not delivered

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

@@ -29,7 +29,12 @@ bomToCsv(rows: BomRow[]): string
 
 **`BomRow`**: `part: string`, `qty: number`, `material?: string`, `process?: string`, `tolerance?: string`, `notes?: string`, `metadata?: PartMetadata`
 
-**`PartMetadata`**: `material?: string`, `process?: string`, `tolerance?: string`, `qty?: number`, `notes?: string`, `densityKgM3?: number`, `massKg?: number`
+**`PartMetadata`**
+
+| Option | Type | Description |
+|--------|------|-------------|
+| `tags?` | `string \| readonly string[]` | Viewport organization tags applied to scene objects produced from this part. |
+| `material?`, `process?`, `tolerance?`, `qty?`, `notes?`, `densityKgM3?`, `massKg?` | | — |
 
 #### `assembly()` — Create an assembly container with named parts and joints for kinematic mechanisms.
 
@@ -670,13 +675,13 @@ toGroup(): ShapeGroup
 Each part becomes `{ name, shape }` or `{ name, group: [...] }` if the part is a [`ShapeGroup`](/docs/core#shapegroup). Top-level scripts should normally return the `SolvedAssembly` directly. Use `toGroup()` when you need [`ShapeGroup`](/docs/core#shapegroup) behavior; use this method only for advanced scene-graph control where you need access to the flat per-part array with metadata.
 
 ```ts
-toSceneObjects(): Array<{ name: string; shape?: Shape; group?: Array<{ name: string; shape: Shape; }>; metadata?: PartMetadata; }>
+toSceneObjects(): Array<{ name: string; shape?: Shape; group?: Array<{ name: string; shape: Shape; tags?: string[]; }>; metadata?: PartMetadata; }>
 ```
 
 #### `toScene()` — Backward-compatible alias for `toSceneObjects()`.
 
 ```ts
-toScene(): Array<{ name: string; shape?: Shape; group?: Array<{ name: string; shape: Shape; }>; metadata?: PartMetadata; }>
+toScene(): Array<{ name: string; shape?: Shape; group?: Array<{ name: string; shape: Shape; tags?: string[]; }>; metadata?: PartMetadata; }>
 ```
 
 #### [`bom()`](/docs/output#bom) — Generate a bill of materials for all parts in the solved assembly.