forgecad 0.9.15 → 0.10.0

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

@@ -1,3 +1,5 @@
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit docs/permanent/ instead. -->
+
 # forgecad
 
 ForgeCAD model authoring, editing, debugging, and execution guidance for .forge.js, SVG-import, assembly, and CLI workflows. Use when building or modifying ForgeCAD geometry, structuring multi-file projects, validating scripts, or using ForgeCAD export/render tooling.
@@ -16,26 +18,25 @@ Author or modify ForgeCAD models, sketches, assemblies, and CLI workflows. Prefe
 ### Workflow
 
 1. Identify the artifact: `.forge.js`, SVG asset, or CLI/export task.
-2. If the model has moving parts, load the assembly group and `docs/permanent/guides/joint-design.md` upfront; do not defer the kinematic structure to a refactor pass.
-3. Load only the docs the task needs (see Source Map below). Start from the top group, add others as needed.
+2. **If the model has any moving parts, load the `assembly` group and `docs/permanent/guides/joint-design.md` upfront** — do not defer the kinematic structure to a refactor pass.
+3. Load only the docs the task needs (see Source Map below). Start from the top group, add others as needed, and prefer these docs and recipes over ad-hoc repo examples.
 4. If any two parts are intended to touch or mate in the final model, load `docs/permanent/guides/positioning.md` immediately and default to connectors + `matchTo()`.
-5. Prefer the docs and recipe snippets below over ad-hoc repo examples.
-6. Default to a concrete first pass — easy iteration beats speculative design review.
-7. If an existing model is broken, replace the weak structure rather than preserving bad architecture.
-8. Validate with `forgecad run <file>` (add `--debug-imports` for import chain issues, and pass `--backend manifold|occt|truck` when the backend matters).
-9. For moving assemblies, return the `Assembly` directly so runtime controls re-solve the link/edge kinematics model instead of stacking viewport-only transforms.
-10. Model the physical artifact, not an educational diagram. Do not add explanatory labels, arrows, legends, or text plaques unless the user explicitly asks for a presentation or teaching view. Product markings are allowed only when they would exist on the real object.
-11. Build the real closed CAD first. Do not bake cutaways, sectioned shells, permanently exploded layouts, or hidden-parts views into the default model just to show internals. Use viewer-only cut planes, `explodeView`, object hiding, transparency, or `inspect sections` after the artifact exists.
+5. Default to a concrete first pass — easy iteration beats speculative design review.
+6. If an existing model is broken, replace the weak structure rather than preserving bad architecture.
+7. Validate with `forgecad run <file>` (add `--debug-imports` for import chain issues; pass `--backend manifold|occt|truck` when the backend matters).
+8. For moving assemblies, return the `Assembly` directly so runtime controls re-solve the link/edge kinematics model instead of stacking viewport-only transforms.
+9. Model the physical artifact, not an educational diagram. No explanatory labels, arrows, legends, or text plaques unless the user explicitly asks for a presentation or teaching view; product markings only where the real object would carry them.
+10. Build the real closed CAD first. Never bake cutaways, sectioned shells, permanently exploded layouts, or hidden-parts views into the default model just to show internals — use viewer-only cut planes, `explodeView`, object hiding, transparency, or `inspect sections` after the artifact exists.
 
 #### Import and Composition
 
-- Always include the extension in relative imports: `require("./file.forge.js", { Param: value })` for model files and `require("./helpers.js")` for plain helper modules. Do not write extensionless imports such as `require("./file")`; ForgeCAD resolves project imports by exact path.
-- ForgeCAD APIs are injected globals in `.forge.js` files. Use `bom()`, `box()`, `scene()`, `Shape`, etc. directly; do not destructure those names from helpers with patterns like `const { bom } = require("./bom.js")`. If a helper file is needed, import it under a project-specific name such as `const bomHelpers = require("./bom.js")`.
+- Always include the extension in relative imports: `require("./file.forge.js", { Param: value })` for model files, `require("./helpers.js")` for plain helper modules. Extensionless imports such as `require("./file")` do not resolve; ForgeCAD resolves project imports by exact path.
+- ForgeCAD APIs are injected globals in `.forge.js` files. Use `bom()`, `box()`, `scene()`, `Shape`, etc. directly; never destructure those names from helpers (`const { bom } = require("./bom.js")`). Import helper files under a project-specific name such as `const bomHelpers = require("./bom.js")`.
 - For static multi-part models, connectors + `matchTo()` are the default way to assemble touching parts.
-- Top-level scripts can return `Assembly` or `SolvedAssembly` directly. Do not call `.toGroup()` just to render an assembly; use `.toGroup()` only when you need `ShapeGroup` composition, transforms, or named-child lookup.
-- `importSvgSketch()` for SVG files (file format loader, not a module import).
-- `.placeReference('bottom', [0,0,0])` to align any built-in anchor to a world coordinate; also works with custom `.withReferences()`.
-- Plain `.js` modules for shared helpers/constants (not model imports).
+- Top-level scripts can return `Assembly` or `SolvedAssembly` directly. Do not call `.toGroup()` just to render an assembly; use it only when you need `ShapeGroup` composition, transforms, or named-child lookup.
+- `Import.svgSketch()` loads SVG files (file format loader, not a module import).
+- `.placeReference('bottom', [0,0,0])` aligns any built-in anchor to a world coordinate; also works with custom `.withReferences()`.
+- Plain `.js` modules hold shared helpers/constants (not model imports).
 
 ### Source Map
 
@@ -54,7 +55,6 @@ Execution model, colors, coordinate system, primitives, booleans, patterns, impo
 Axis conventions, winding rules, and placement strategy. If parts should touch in the final model, read this group before writing placement code. Connectors + `matchTo()` are the default for mating interfaces; raw `translate()` and `rotate()` are for free offsets, not assembly contracts.
 
 - `docs/permanent/guides/coordinate-system.md`
-- `docs/permanent/guides/geometry-conventions.md`
 - `docs/permanent/guides/positioning.md`
 
 #### 3. Sketch APIs
@@ -67,6 +67,7 @@ Axis conventions, winding rules, and placement strategy. If parts should touch i
 
 Smooth curves, Hermite splines, lofted and swept solids. For straps, inlays, guards, brace members, vents, or physical bands that live on a carrier surface, use `Carrier` + `SurfaceBody` surface-member primitives before reaching for `variableSweep`, SDF sculpting, or manual boolean overlap recipes.
 
+- `docs/permanent/guides/surface-members.md`
 - `docs/permanent/generated/curves.md`
 
 #### 5. Assemblies and Mechanisms (for joints or kinematics)
@@ -104,7 +105,7 @@ Viewer-only APIs such as cutPlane, explodeView, render labels, comparison refere
 
 Modeling patterns, debugging tactics, copyable snippets.
 
-- `docs/permanent/guides/modeling-recipes.md`
+- `docs/permanent/guides/scene-presentation.md`
 - `docs/permanent/guides/joint-design.md`
 
 #### 11. CLI (for validation/render/export tasks)
@@ -116,6 +117,6 @@ Test-run, export pipelines, debug flags.
 
 #### SDF Modeling (smooth booleans, TPMS, deformations, fromFunction)
 
-Primitives, smooth booleans, TPMS lattices, twist/bend/displace, morph, custom functions, gotchas. SDF is inherently implicit and sampled, not B-rep/exact geometry; use caution for precision-critical parts and exact export workflows.
+Primitives, smooth booleans, TPMS lattices, twist/bend/displace, morph, custom functions, gotchas. The doc preamble's precision caution applies to every SDF workflow.
 
 - `docs/permanent/generated/sdf.md`

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

@@ -1,3 +1,5 @@
+<!-- Generated by scripts/build-forgecad-skill.mjs — do not edit. Edit agent-skill-library/*/SKILL.md instead. -->
+
 # ForgeCAD Skills
 
 These are the agent skills shipped in the ForgeCAD npm package. The default install path installs the core `forgecad` skill plus the companion workflow skills listed here.

package/dist/docs-raw/welcome.md

@@ -31,6 +31,8 @@ forgecad studio .
 
 `forgecad studio .` opens the local editor around the current project folder. The `.` is not optional; `forgecad studio` requires a project path.
 
+Keep one long-running `forgecad studio <project-path> [project-path ...]` process open with every active project folder listed in its arguments; the user opens the single printed localhost port once, and AI agents should only create or edit files under those folders so the browser updates live without starting more servers.
+
 ### Create A New Local Project
 
 Use this when you want a fresh model instead of the starter project:
@@ -45,7 +47,7 @@ forgecad new adapter --template part
 forgecad studio .
 ```
 
-`forgecad project init` creates the hosted project, writes `forgecad.json`, and uploads any existing local `.forge.js`, `.js`, and `.svg` files. After that, `forgecad project push` syncs changes back to the hosted project.
+`forgecad project init` creates the hosted project, writes `forgecad.json`, and uploads existing local model files, helper code, Markdown notes, SVG/DXF assets, and other supported text project files. After that, `forgecad project push` syncs changes back to the hosted project.
 
 `forgecad project push` does not create a remote project from an arbitrary folder. If a folder has no `forgecad.json`, initialize it with `forgecad project init` or clone an existing project first.
 
@@ -56,7 +58,7 @@ ForgeCAD commands need a project root so imports, helper files, SVGs, and genera
 A single loose `.forge.js` file is fine for a tiny experiment, but it is not the best workflow for useful AI-generated CAD. A project folder gives the agent and CLI enough context to work well:
 
 - `forgecad.json` links the folder to the hosted project.
-- `.forge.js`, `.js`, and `.svg` files stay together.
+- `.forge.js`, helper code, Markdown notes, and SVG/DXF assets stay together.
 - `forgecad run` and render commands resolve local imports from the intended root.
 - `forgecad project push` knows exactly which remote project to update.
 - Inspection bundles, screenshots, and export outputs can live beside the model without mixing with unrelated files.

package/dist/index.html

@@ -83,7 +83,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-D3kDkggg.js"></script>
+    <script type="module" crossorigin src="/assets/app-DSYrDg0V.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/app-CE3sYcV7.css">
   </head>
   <body>

package/dist/llms.txt

@@ -31,9 +31,8 @@ For coding agents, start with the welcome guide and AI Usage guide, then read th
 ## Guides
 
 - [Coordinate system](https://forgecad.io/docs-raw/guides/coordinate-system.md): Axes, units, orientation, and workspace conventions.
-- [Geometry conventions](https://forgecad.io/docs-raw/guides/geometry-conventions.md): Modeling assumptions and practical shape-building rules.
 - [Positioning](https://forgecad.io/docs-raw/guides/positioning.md): Translation, rotation, alignment, and placing geometry predictably.
-- [Modeling recipes](https://forgecad.io/docs-raw/guides/modeling-recipes.md): Common parametric CAD patterns and example approaches.
+- [Scene presentation](https://forgecad.io/docs-raw/guides/scene-presentation.md): Worked scene() lighting and camera recipes for polished renders.
 - [Joint design](https://forgecad.io/docs-raw/guides/joint-design.md): Designing assemblies and moving mechanisms with connectors and joints.
 - [Inspection bundles](https://forgecad.io/docs-raw/guides/inspection-bundles.md): How to use render-inspect outputs for debugging and verification.
 - [Component model](https://forgecad.io/docs-raw/component-model.md): Recommended structure for multi-part assemblies and reusable parts.

package/dist/sitemap.xml

@@ -2,79 +2,79 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://forgecad.io/</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>1.0</priority>
   </url>
   <url>
     <loc>https://forgecad.io/docs</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.8</priority>
   </url>
   <url>
     <loc>https://forgecad.io/docs/ai-native-cad</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.9</priority>
   </url>
   <url>
     <loc>https://forgecad.io/docs/ai-usage</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.8</priority>
   </url>
   <url>
     <loc>https://forgecad.io/docs/cli</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.7</priority>
   </url>
   <url>
     <loc>https://forgecad.io/docs/skills/forgecad-make-a-model</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.7</priority>
   </url>
   <url>
     <loc>https://forgecad.io/benchmark</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.7</priority>
   </url>
   <url>
     <loc>https://forgecad.io/blog</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>weekly</changefreq>
     <priority>0.6</priority>
   </url>
   <url>
     <loc>https://forgecad.io/pricing</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>monthly</changefreq>
     <priority>0.5</priority>
   </url>
   <url>
     <loc>https://forgecad.io/terms</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>yearly</changefreq>
     <priority>0.3</priority>
   </url>
   <url>
     <loc>https://forgecad.io/privacy</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>yearly</changefreq>
     <priority>0.3</priority>
   </url>
   <url>
     <loc>https://forgecad.io/license</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>yearly</changefreq>
     <priority>0.3</priority>
   </url>
   <url>
     <loc>https://forgecad.io/blog/hello-forgecad-io</loc>
-    <lastmod>2026-06-05</lastmod>
+    <lastmod>2026-06-10</lastmod>
     <changefreq>monthly</changefreq>
     <priority>0.5</priority>
   </url>

package/dist-cli/{check-compiler-SDX5QIXI.js → check-compiler-JTVBITCR.js}

@@ -9,7 +9,7 @@ import {
   resolvePackagePath,
   runDirectCliMain,
   setActiveBackend
-} from "./chunk-N4O47JLF.js";
+} from "./chunk-OAN5T4XD.js";
 
 // cli/check-compiler.ts
 import assert from "assert/strict";

package/dist-cli/{check-query-propagation-EAYEFT77.js → check-query-propagation-3FFLSMVN.js}

@@ -12,7 +12,7 @@ import {
   resolvePackagePath,
   runDirectCliMain,
   setActiveBackend
-} from "./chunk-N4O47JLF.js";
+} from "./chunk-OAN5T4XD.js";
 
 // cli/check-query-propagation.ts
 import assert from "assert/strict";