@metamesh/cli 0.16.0 → 0.18.0

package/dist/docs/guides/agent-authoring.md

@@ -2,12 +2,17 @@
 
 Use the CLI to find installed docs, check TypeScript, capture a model, and inspect measurements and rendered views.
 
-Use the `metamesh` CLI to look up the installed API, check TypeScript, generate a model, and inspect
-the captured result. It runs trusted local source with your ordinary Node permissions. Its
-disposable child process is not a security sandbox.
+Use the `metamesh` CLI to build a model and check what it actually produced. You or your agent can
+look up the installed API, check TypeScript, run the model, and inspect measurements and views of
+the captured result. The CLI runs trusted local source with your ordinary Node permissions. Its
+disposable child process isn't a security sandbox.
 
 ## Install and discover the environment
 
+Use Node.js 24 or newer. The package APIs publish ES modules only. TypeScript API consumers
+use TypeScript 6.0 or newer with `strict` checking and `NodeNext` or `Bundler` resolution;
+the CLI includes its source-checking compiler.
+
 Install Modeling for your model code and the CLI for the local authoring workflow:
 
 ```bash
@@ -19,13 +24,12 @@ pnpm exec metamesh setup
 
 `environment` reports project-resolved versions, documentation locations, available capabilities,
 and `authoringProtocolVersion: 1`. An agent integration should check that protocol value before
-using the commands. Missing packages, mismatched releases, or an unsupported protocol need an
-environment fix before authoring.
+using the commands. Fix missing packages, mismatched releases, or an unsupported protocol before
+authoring.
 
 Add the Generator SDK as a direct dependency when defining Generators, and Testkit when writing
-automated tests.
-Ordinary models need only Modeling and the CLI as direct dependencies. Keep installed MetaMesh
-packages on matching releases.
+automated tests. Ordinary models need only Modeling and the CLI as direct dependencies. Keep
+installed MetaMesh packages on matching releases.
 
 | Component                 | Responsibility                                                                                |
 | ------------------------- | --------------------------------------------------------------------------------------------- |
@@ -44,10 +48,10 @@ pnpm exec metamesh docs search "cylinder"
 pnpm exec metamesh docs show modeling/reference/model/cylinder
 ```
 
-The [standalone model example](https://metamesh.studio/docs/develop/standalone-model) is a short starting point.
-Use the [construction map](https://metamesh.studio/docs/develop/geometry-package#choose-a-modeling-path) to choose an
-approach, or search for a shape or symbol and read its recipe or reference. Search matches distinct
-words in titles, headings, keywords, and summaries. Exact titles, IDs, and imports take priority;
+Start with the [standalone model example](https://metamesh.studio/docs/develop/standalone-model), or use the
+[construction map](https://metamesh.studio/docs/develop/geometry-package#choose-a-modeling-path) to choose an approach
+for your shape. You can also search for a shape or symbol and read its recipe or reference.
+Search matches distinct words in titles, headings, keywords, and summaries. Exact titles, IDs, and imports take priority;
 equally complete intent matches favor guides.
 
 Documentation is resolved from the selected project through package exports. No global installation
@@ -63,7 +67,7 @@ covers authoring and verification; `metamesh-docs` covers documentation. Both ar
 Use a reviewed skill snapshot provided by your project or installed through your agent's skill
 tooling. The printed GitHub installation source must be published before that command can work;
 a skill is optional for the CLI workflow below. Skills teach the process. The installed npm
-documentation owns exact signatures, import paths, units, lifecycle, and availability.
+documentation supplies exact signatures, import paths, units, execution rules, and availability.
 
 Project instructions should require environment discovery, relevant documentation lookup, source
 checking and execution, then measurement inspection and useful rendered views from that same run.
@@ -72,8 +76,8 @@ targeting another directory so every step resolves the same installation.
 
 ## Model entries
 
-A model entry default-exports an ordinary `ModelProgram`. It imports the real package; Studio's
-virtual `@metamesh/project` module is not available in local Node projects.
+A model entry default-exports a `ModelProgram` and imports the installed package directly.
+Studio's virtual `@metamesh/project` module isn't available in local Node projects.
 
 
 
@@ -83,7 +87,7 @@ import { box, cylinder, generate } from "@metamesh/modeling";
 export default generate<Record<never, never>>(({ part }) => {
   const body = box({ size: [30, 20, 6] });
   const bore = cylinder({ height: 8, radius: 3, sizing: "face" });
-  return part("plate", body.subtract([bore]));
+  return part("plate", body.subtract(bore));
 });
 ```
 
@@ -92,27 +96,27 @@ export default generate<Record<never, never>>(({ part }) => {
 Save this as `model.ts`, then check and run it:
 
 ```bash
-pnpm exec metamesh check model.ts --kind model
+pnpm exec metamesh typecheck model.ts --kind model
 pnpm exec metamesh run model.ts --kind model --export-3mf
 ```
 
-Both commands perform semantic TypeScript checking. They use the nearest project TypeScript
-configuration, or an explicit `--tsconfig`, with strict checking enforced. Ordinary local imports
-and installed dependencies are supported. `check` does not evaluate your source.
+Both commands check TypeScript types using the nearest project TypeScript configuration, or an
+explicit `--tsconfig`, with strict checking enforced. You can use ordinary local imports and
+installed dependencies. `typecheck` doesn't evaluate your source.
 
 Use `--params values.json` for a model's JSON parameter map; the default is `{}`. Models do not
 receive injected Generator services. A standalone module can prepare licensed local fonts before
 constructing its synchronous generation program.
 
-For standalone font provenance, also pass `--font-fixtures fonts.json`. The CLI verifies those local
+To record which local fonts you used, also pass `--font-fixtures fonts.json`. The CLI verifies those
 bytes and records their declared font selections and immutable revisions in the capture; the model
 still prepares its own fonts and receives no injected services. Arbitrary filesystem or network
-reads are not intercepted, so their asset identities cannot be inferred. The source fingerprint
+reads aren't intercepted, so the CLI can't infer their asset identities. The source fingerprint
 covers bundled source, while fixture descriptors provide explicit asset provenance.
 
 ## Generator entries
 
-Install the Generator contract layer in addition to Modeling and the CLI:
+Install the Generator SDK alongside Modeling and the CLI to define controls and package metadata:
 
 ```bash
 pnpm add @metamesh/generator-sdk
@@ -123,12 +127,9 @@ A Generator entry named-exports `definition` and default-exports its module enve
 
 
 ```ts
-import {
-  defineGenerator,
-  defineGeneratorModule,
-  type GeneratorParams,
-} from "@metamesh/generator-sdk";
-import { box, generate } from "@metamesh/modeling";
+import { defineGenerator } from "@metamesh/generator-sdk";
+import { defineGeneratorModel } from "@metamesh/generator-sdk/modeling";
+import { box } from "@metamesh/modeling";
 
 export const definition = defineGenerator({
   id: "plate",
@@ -138,18 +139,20 @@ export const definition = defineGenerator({
   parameters: [{ id: "width", label: "Width", type: "number", default: 30, min: 1 }],
 });
 
-const model = generate<GeneratorParams<typeof definition>>(({ params, part }) =>
+export default defineGeneratorModel(definition, ({ params, part }) =>
   part("plate", box({ size: [params.width, 20, 6] }))
 );
-
-export default defineGeneratorModule({ definition, generate: model });
 ```
 
 
 
+`defineGeneratorModel` from the optional SDK `/modeling` adapter infers controls, prepared services,
+and assertion parameter IDs. It declares the ordinary Modeling program and package identity;
+the host still owns normalization, asset preparation, execution, and cleanup.
+
 ```bash
-pnpm exec metamesh check generator.ts --kind generator
-pnpm exec metamesh run generator.ts --kind generator --params values.json
+pnpm exec metamesh typecheck generator.ts --kind generator
+pnpm exec metamesh run generator.ts --kind generator --overrides values.json
 ```
 
 Generator runs merge declared defaults with explicit overrides, then validate strictly. Unknown
@@ -173,10 +176,11 @@ pnpm exec metamesh render RUN_DIRECTORY
 pnpm exec metamesh render RUN_DIRECTORY --views top --format webp --transparent
 ```
 
-Inspection reads finalized part IDs, placements, colors, measurements, diagnostics, and execution
-provenance. Rendering uses the same captured buffers without rerunning the model. Captures remain
+Inspection reads the completed model's part IDs, placements, colors, measurements, diagnostics,
+and execution provenance. Rendering uses the same captured buffers without rerunning the model,
+so the dimensions you inspect and the views you render belong to the same result. Captures remain
 usable after the engine session is disposed or the directory moves. Corrupt or incomplete
-artifacts reject.
+artifacts are rejected.
 
 Rendering requires the separately installed pinned Chromium. It is never downloaded implicitly;
 checking, generation, and inspection work without it. Standard orthographic views are isometric,
@@ -184,7 +188,7 @@ front, top, and right. The default is an isometric 1024 × 1024 PNG on a neutral
 lossless; PNG and WebP both support explicit transparent output. Images record their run, camera,
 renderer, and browser versions. Compare pixels only within the pinned capture environment.
 
-`--export-3mf` exports that run's finalized snapshot. A failed attempt never exposes an older
+`--export-3mf` exports the completed model from that run. A failed attempt never exposes an older
 successful result as its output. Match the captured parameters and source fingerprint to the
 revision you intended to verify.
 
@@ -196,32 +200,50 @@ Install Testkit separately when you want assertions and fixtures for your existi
 pnpm add -D @metamesh/testkit
 ```
 
+Use `await runModel(({ part }) => part("body", box({ size: 2 })))` for a one-off model, or
+pass an existing program directly with `await runModel(program, parameters)`. Use
+`await runModel({ definition, runtime }, parameters)` for a Generator. The returned result remains
+usable after the helper releases its temporary session; no cleanup is required.
+For cached Generators, exercise representative edits through
+`createGeneratorTestRunner(definition, runtime, { verifyCache: true })` and its `run` method.
+One-shot tests and declaration checks do not verify reuse across edits. Use `cache: false` for
+an uncached output baseline; keep prepared services stable when testing reuse in the same session.
+Callbacks run synchronously and return a part or an array of parts. Declare typed inline inputs
+with `runModel<Parameters, Services>(callback, parameters, options)`, or reuse a
+`GenerateCallback<Parameters, Services>`. Parameterless callbacks and Generator defaults can omit parameters. Options stay in the third
+argument: use `undefined` for omitted parameters when supplying a test-owned engine, generation
+policy, prepared model services, or a Generator's asynchronous `prepareServices` adapter.
+
+For Generator integration tests, import the definition and default runtime from the real entry
+point instead of repeating its input resolution and builder calls. Use direct callbacks to isolate
+construction, reconstruct a mesh, or deliberately bypass schema validation.
+
 Use `createGeneratorTestRunner(definition, runtime)` for a Generator's persistent generation
-session. Its `execute` method returns a discriminated result: handle `type: "invalid"` before
-reading a generated `model`. Dispose each successful `model` when finished and dispose the runner
-separately; snapshots remain usable after the runner is disposed.
-Unexpected execution or malformed-output errors reject instead of returning an `invalid` result.
-For an ordinary `ModelProgram`, use an [engine session](https://metamesh.studio/docs/engine/hosting) and the same assertions
-against its completed snapshot.
+session. `runner.run(parameters)` normalizes inputs, prepares assets, and returns a discriminated
+result. Handle `type: "invalid"`
+before reading a generated `model`. Successful results remain usable after later runs and runner
+disposal. Dispose the runner to release its session and caches. Use `engine.createSession(program, options)`
+for repeated plain-model edits or cache tests and dispose the session in `finally`; its returned
+results also remain usable. Unexpected execution or malformed-output errors reject.
 
 The runner normalizes saved values. To probe deliberately invalid typed inputs without that
-recovery, call `runner.validate(parameters, { normalize: false })`. Validation checks declarations
+recovery, call `runner.check(parameters, { validateInput: false })`. Validation checks declarations
 and reached assertions without finalizing output; execute representative valid combinations too.
 The CLI's strict overrides serve a different purpose: they reject invalid or unknown values
 before execution instead of recovering saved state.
 
-| Helper                         | What to check                                                      |
-| ------------------------------ | ------------------------------------------------------------------ |
-| `expectSerializableDefinition` | Strict definition parsing and a canonical JSON round trip          |
-| `expectValidDefaults`          | Strict parameter decoding and agreement with defaults              |
-| `expectValidPresets`           | Serializable preset metadata; execute presets for domain rules     |
-| `expectValidParts`             | Part metadata, closed oriented topology, and native reconstruction |
-| `expectMeshMeasurements`       | Bounds, area, signed volume, and connected-component count         |
-
-Compare physical measurements with explicit absolute tolerances; bounds use millimetres, area
-square millimetres, and volume cubic millimetres. Component counts are exact. Rendered views
-complement those assertions. A valid solid alone does not prove a suitable fit or manufacturable
-wall thickness.
+| Helper                   | What to check                                                      |
+| ------------------------ | ------------------------------------------------------------------ |
+| `assertValidDefinition`  | Strict definition parsing and a canonical JSON round trip          |
+| `assertValidDefaults`    | Strict parameter decoding and agreement with defaults              |
+| `assertValidPresets`     | Serializable preset metadata; execute presets for domain rules     |
+| `assertValidParts`       | Part metadata, closed oriented topology, and native reconstruction |
+| `assertMeshMeasurements` | Bounds, area, signed volume, and connected-component count         |
+
+Compare physical measurements with explicit absolute tolerances: bounds use millimetres, area
+square millimetres, and volume cubic millimetres. Component counts are exact. Use rendered views
+alongside those assertions to check the shape. A valid solid alone doesn't prove a suitable fit or
+manufacturable wall thickness.
 
 For Font controls, supply the runner's `prepareServices` option using checked-in licensed bytes.
 `prepareFontTestServices` from `@metamesh/testkit/fonts` verifies immutable font revisions and

package/dist/docs/guides/package.md

@@ -1,71 +1,91 @@
 # `@metamesh/cli`
 
-Check, execute, inspect, and render trusted local MetaMesh source. The `metamesh` executable and
-Node-only `/authoring` functions use the production engine and version-matched installed documentation.
+Check, run, inspect, and render local MetaMesh models. The `metamesh` executable brings
+version-matched documentation, TypeScript checks, and captured geometry into one authoring workflow.
+The same tools are available through a Node API.
 
 > **Preview:** `0.x` minor releases may break compatibility. Patches remain compatible within the
 > same minor line.
 
 ## Installation
 
-Install the same exact release of each MetaMesh package in the project where you author models:
+Install matching Modeling and CLI releases in your authoring project:
 
 ```bash
 pnpm add @metamesh/modeling
 pnpm add -D @metamesh/cli
 ```
 
-Add `@metamesh/generator-sdk` when your source defines Generators. Add `@metamesh/testkit` as a
-development dependency when importing testing helpers. CLI internally reuses Testkit font fixtures
-and its SDK contracts; neither package needs to be directly declared for standalone model authoring.
-The compiler, bundler, Three renderer, and Playwright belong to CLI; Testkit does not install them.
-Chromium is installed separately and never downloaded by checking or generation.
+The executable and Node API require Node.js 24 or newer. The API publishes ES modules only.
+TypeScript source and API consumers need TypeScript 6.0 or newer with `strict` checking and
+`NodeNext` or `Bundler` module resolution. The CLI includes its source-checking compiler.
+
+Add Generator SDK for Generator source and Testkit when importing testing helpers directly.
+Standalone model authoring needs neither as a direct dependency. Chromium setup is separate;
+checking, generation, and inspection work without a browser.
 
 ## Local workflow
 
+Save a model entry as `model.ts`, default-exporting a `ModelProgram` from Modeling. Then discover
+the installed environment, look up the API, and build a captured result:
+
 ```bash
 pnpm exec metamesh environment --json
+pnpm exec metamesh docs search "sweep"
 pnpm exec metamesh docs show modeling/guide/concepts
-pnpm exec metamesh docs search "extrude"
-pnpm exec metamesh docs show TOPIC_ID
-pnpm exec metamesh check model.ts --kind model
-pnpm exec metamesh run model.ts --kind model
+pnpm exec metamesh typecheck model.ts --kind model
+pnpm exec metamesh run model.ts --kind model --export-3mf
 pnpm exec metamesh inspect RUN_DIRECTORY
+```
+
+Replace `RUN_DIRECTORY` with the path reported by `run`. Commands resolve packages and paths
+from the current project; use `--project PATH` to select another. `environment` reports the
+supported authoring protocol, package versions, and local documentation. Version mismatches fail
+before generation.
+
+For Generators, use `--kind generator` with a named `definition` export and a default Generator
+module. Pass `--overrides parameters.json` for input values. Generator overrides merge with defaults
+and undergo strict validation; standalone model parameters pass through directly. Studio's virtual
+`@metamesh/project` import is unavailable in local entries.
+
+## Authoring tools
+
+| Command                     | Purpose                                                                                |
+| --------------------------- | -------------------------------------------------------------------------------------- |
+| `environment`               | Discover project-local packages, capabilities, and documentation.                      |
+| `docs search` / `docs show` | Find and read exact-version guides and API references offline.                         |
+| `typecheck`                 | Check TypeScript and entry-point export types without executing the model.             |
+| `run`                       | Check and execute source, capture geometry and diagnostics, and optionally export 3MF. |
+| `inspect`                   | Read captured parts, bounds, measurements, and diagnostics.                            |
+| `render`                    | Create standard views from a capture.                                                  |
+| `setup`                     | Print skill installation and project-instruction guidance.                             |
+
+`run` uses a disposable child process with a 30-second default deadline and saves attempts under
+`.metamesh/runs`. Captures retain source identity, effective parameters, and hashed geometry.
+`inspect` and `render` validate those saved buffers without rerunning the source.
+
+Source executes with your account's permissions; this is trusted local execution, not a security
+sandbox. Use `--json` for structured stdout; bounded author logs go to stderr. Exit codes are
+0 for success, 1 for source or generation failure, and 2 for invocation, environment, artifact,
+or tooling failure. Each command's `--help` lists its options and limits.
+
+Use `--params values.json` for a standalone model's complete input map. For a Generator,
+use `--overrides values.json`; those values merge with definition defaults before strict
+validation. The Node API uses the matching `params` and `overrides` fields, discriminated by `kind`.
+
+## Render a capture
+
+Install the pinned Chromium explicitly, then choose views of the captured model:
+
+```bash
 pnpm exec metamesh browser install
 pnpm exec metamesh render RUN_DIRECTORY --views isometric,front,top,right
 ```
 
-`environment` reports `authoringProtocolVersion: 1`, installed package versions, capabilities,
-and documentation manifest paths. Mixed package versions or stale documentation fail before
-generation. Commands resolve packages and relative paths from the current project; pass
-`--project PATH` to select another project explicitly. `TOPIC_ID` comes from documentation search;
-`RUN_DIRECTORY` comes from a successful run.
-
-The concepts guide starts with a compact construction map. Search matches distinct words in
-titles, guide headings, keywords, and summaries. Exact titles, topic IDs, and import paths take
-priority; equally complete intent matches favor guides over reference entries.
-
-`run` includes semantic TypeScript checking and executes in a disposable child process with a
-30-second default deadline. It saves each attempt beneath `.metamesh/runs` with source identity,
-parameters, diagnostics, measurements, and hashed geometry buffers. `inspect` and `render` validate
-those captured buffers without importing the original source. Use `--json` for one structured stdout
-result; bounded author logs go to stderr. Exit codes are 0 for success, 1 for source or generation
-failure, and 2 for invocation, environment, artifact, or tooling failure. This executes trusted local
-code and is not a security sandbox.
-
-For Generators, use `--kind generator`. Entries named-export `definition` and default-export the
-Generator module envelope. Defaults merge with `--params parameters.json`, then strict validation
-rejects unknown or invalid overrides. Standalone model entries default-export a `ModelProgram` and
-receive no injected services. Both support normal local imports and installed dependencies; Studio's
-virtual `@metamesh/project` module is unavailable.
-
-Use `--help` on each command for parameters, fonts, resource limits, export, and image options.
-`metamesh setup` prints installation guidance for `metamesh-developer` from the canonical
-`metamesh-studio/metamesh-skills` repository and a project-instruction suggestion without modifying
-files. Its printed GitHub installation command becomes usable when that repository is published;
-the skill supplies the workflow, while installed package documentation supplies exact API facts.
-
-## Programmatic API and documentation
+Rendering supports PNG and lossless WebP, transparent backgrounds, and standard orthographic views.
+Checking and generation never download a browser.
+
+## Node API and agent workflows
 
 ```ts
 import { inspectCapturedRun, runAuthoringSource } from "@metamesh/cli/authoring";
@@ -76,16 +96,19 @@ if (result.success) {
 }
 ```
 
-Resolve `@metamesh/cli/docs/manifest.json` for the installed Markdown reference, or run
-`pnpm exec metamesh docs show cli/guide/agent-authoring` for the complete authoring workflow.
-The [authoring guide source](https://github.com/JasonKoolman/metamesh/blob/main/apps/web/content/docs/develop/agent-authoring.mdx)
-also covers local font fixtures, artifacts, rendering, and agent integration. Until the public
-documentation site launches, use installed documentation, repository sources, or
-[run the docs locally](https://github.com/JasonKoolman/metamesh/blob/main/apps/web/README.md#local-use).
+`@metamesh/cli/authoring` also exposes environment discovery, documentation lookup, source checking,
+and rendering. `metamesh setup` prints guidance without changing project files. The portable
+`metamesh-developer` skill supplies the workflow; installed package documentation supplies API facts.
+Install a reviewed skill snapshot from the canonical `metamesh-studio/metamesh-skills` repository
+or its local checkout when public installation is unavailable.
+
+## Documentation
 
-The reusable authoring functions and command implementation stay in this package; geometry and
-Generator contracts retain their existing owners. Testing assertions and font-fixture adapters
-remain in Testkit.
+Resolve `@metamesh/cli/docs/manifest.json` for exact-version Markdown guidance and API references,
+or run `pnpm exec metamesh docs show cli/guide/agent-authoring`. The
+[authoring guide](https://github.com/JasonKoolman/metamesh/blob/main/apps/web/content/docs/develop/agent-authoring.mdx)
+covers entry contracts, parameters, fonts, captures, and rendering. See
+[Contributing](https://github.com/JasonKoolman/metamesh/blob/main/CONTRIBUTING.md) for package development.
 
 ## License
 

package/dist/docs/manifest.json

@@ -1,7 +1,7 @@
 {
   "formatVersion": 1,
   "packageName": "@metamesh/cli",
-  "packageVersion": "0.16.0",
+  "packageVersion": "0.18.0",
   "documents": [
     {
       "id": "cli/guide/agent-authoring",

package/dist/docs/reference/authoring/AUTHORING_PROTOCOL_VERSION.md

@@ -2,7 +2,7 @@
 
 Version of the CLI authoring protocol, independent of package SemVer and engine compatibility.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 AUTHORING_PROTOCOL_VERSION = 1

package/dist/docs/reference/authoring/AuthoringDiagnostic.md

@@ -2,7 +2,7 @@
 
 A structured issue with optional source location, parameter association, and geometry context.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** A structured issue with optional source location, parameter association, and geometry context. */

package/dist/docs/reference/authoring/AuthoringEnvironment.md

@@ -2,7 +2,7 @@
 
 The selected project's supported protocol, matching package releases, and available workflows.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** The selected project's supported protocol, matching package releases, and available workflows. */

package/dist/docs/reference/authoring/AuthoringError.md

@@ -2,7 +2,7 @@
 
 A classified authoring exception retaining its workflow phase, stable code, and exit status.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** A classified authoring exception retaining its workflow phase, stable code, and exit status. */

package/dist/docs/reference/authoring/AuthoringFailure-type.md

@@ -2,7 +2,7 @@
 
 An unsuccessful command outcome; a failure directory does not establish a complete capture.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** An unsuccessful command outcome; a failure directory does not establish a complete capture. */

package/dist/docs/reference/authoring/AuthoringKind.md

@@ -2,7 +2,7 @@
 
 Selects a standalone ModelProgram entry or an SDK Generator module with a definition.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** Selects a standalone ModelProgram entry or an SDK Generator module with a definition. */

package/dist/docs/reference/authoring/AuthoringPhase.md

@@ -2,7 +2,7 @@
 
 The workflow stage that rejected an invocation, source, asset, or captured artifact.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** The workflow stage that rejected an invocation, source, asset, or captured artifact. */

package/dist/docs/reference/authoring/CapturedBuffer.md

@@ -2,7 +2,7 @@
 
 A captured file's relative path, byte length, and SHA-256 integrity digest.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** A captured file's relative path, byte length, and SHA-256 integrity digest. */

package/dist/docs/reference/authoring/CapturedGeometry.md

@@ -2,7 +2,7 @@
 
 Validated local-space mesh buffers loaded from a completed captured resource.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** Validated local-space mesh buffers loaded from a completed captured resource. */

package/dist/docs/reference/authoring/CapturedPart.md

@@ -2,18 +2,16 @@
 
 Semantic part identity and appearance referencing a shared mesh with separate placement.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** Semantic part identity and appearance referencing a shared mesh with separate placement. */
 export interface CapturedPart {
     readonly id: string;
     readonly resourceId: string;
-    /** World translation in millimetres, applied after rotation. */
-    readonly position: Vector3Data;
-    /** Global XYZ rotation in degrees, applied once to local geometry. */
-    readonly rotation: Vector3Data;
+    /** Rigid row-major local-to-world matrix, with translation in millimetres. */
+    readonly transform: Transform3Data;
     readonly color?: string;
-    readonly measurements: SnapshotPart["measurements"];
+    readonly measurements: ModelPart["measurements"];
 }
 ```

package/dist/docs/reference/authoring/CapturedResource.md

@@ -2,7 +2,7 @@
 
 A shared local-space mesh resource and its measurements, before per-part placement.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** A shared local-space mesh resource and its measurements, before per-part placement. */
@@ -10,6 +10,6 @@ export interface CapturedResource {
     readonly id: string;
     readonly positions: CapturedBuffer;
     readonly indices: CapturedBuffer;
-    readonly measurements: SnapshotPart["measurements"];
+    readonly measurements: ModelPart["measurements"];
 }
 ```

package/dist/docs/reference/authoring/CapturedRun.md

@@ -2,7 +2,7 @@
 
 A validated successful capture with its manifest and shared local geometry buffers.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** A validated successful capture with its manifest and shared local geometry buffers. */

package/dist/docs/reference/authoring/CapturedRunManifest.md

@@ -2,12 +2,12 @@
 
 A completed attempt's provenance, effective inputs, diagnostics, and captured geometry.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** A completed attempt's provenance, effective inputs, diagnostics, and captured geometry. */
 export interface CapturedRunManifest {
-    readonly formatVersion: 1;
+    readonly formatVersion: 2;
     readonly status: "complete";
     readonly runId: string;
     readonly createdAt: string;
@@ -31,7 +31,7 @@ export interface CapturedRunManifest {
     };
     readonly diagnostics: readonly GenerationDiagnostic[];
     readonly bounds: Bounds3Data;
-    readonly stats: FinalizedModel["stats"];
+    readonly stats: ModelResult["stats"];
     readonly dependencies: ModelDependencies;
     readonly resources: readonly CapturedResource[];
     readonly parts: readonly CapturedPart[];

package/dist/docs/reference/authoring/CheckOptions.md

@@ -2,7 +2,7 @@
 
 Source entry contract and project-local resolution settings for semantic checking.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** Source entry contract and project-local resolution settings for semantic checking. */

package/dist/docs/reference/authoring/CheckSuccess.md

@@ -2,7 +2,7 @@
 
 A successful semantic check; source has not been evaluated and no geometry is captured.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** A successful semantic check; source has not been evaluated and no geometry is captured. */

package/dist/docs/reference/authoring/DocumentationEntry.md

@@ -2,7 +2,7 @@
 
 Metadata for one installed Markdown guide or public API symbol.
 
-Import from `@metamesh/cli/authoring` (@metamesh/cli@0.16.0).
+Import from `@metamesh/cli/authoring` (@metamesh/cli@0.18.0).
 
 ```ts
 /** Metadata for one installed Markdown guide or public API symbol. */