@metamesh/generator-sdk 0.18.0 → 0.19.0

package/CHANGELOG.md

@@ -1,5 +1,44 @@
 # @metamesh/generator-sdk
 
+## 0.19.0
+
+### Minor Changes
+
+- c9de510: Extend straight extrusion end finishing to concave outlines, holes, and disconnected regions.
+  Add independent-solid `join` with a feature datum and a smooth (default) or straight width/height
+  transition against validated planar, angled, and curved sampled support patches. Both profiles use
+  the same support, collar, and whole-volume containment proofs.
+
+  Breaking: compiled Generators require Modeling runtime major 12. Rebuild packages for the new
+  host contract; old compiled runtimes are rejected. Joining preserves the supplied operands and
+  does not promise a circular fillet radius or perform automatic placement.
+
+  Replace named lazy `computed` readers with eager `memo(fn, ...args)` values. Stable pure helpers
+  reuse immutable arguments and tracked current params/context reads, with bounded recent histories
+  and native geometry retention. Update Studio diagnostics to warn about fresh function identities.
+  All authored and compiled callers must use the new API; there is no compatibility surface.
+
+- de3d234: Add runtime-neutral STL, 3MF, and GLB export under `@metamesh/modeling/export`, with isolated
+  format entry points and backpressure-aware streaming writers. All formats consume captured local
+  geometry, placement, and appearance, with independent limits, cancellation, and structured
+  information-loss diagnostics. Standard 3MF color groups carry appearance, while base materials
+  and multiproperties retain explicit material identities independently of RGB values. These
+  properties do not assign slicer filaments or physical device trays. Add `mesh.render()` for
+  shared crease-aware display buffers that preserve exact triangle coordinates.
+
+  Breaking: remove `export3mf` and export types from `/engine`, remove SDK export request protocols
+  and `toWorldMeshes`, and return owned `Uint8Array` bytes with format metadata from the shared
+  exporters. Studio uses one export worker for every format. CLI captures use format version 3;
+  replace `run --export-3mf` with `metamesh export RUN_DIRECTORY --format 3mf --output model.3mf`.
+  Captured-run export also supports STL and GLB without rerunning source. No legacy export paths
+  or capture readers are retained.
+
+### Patch Changes
+
+- Updated dependencies [c9de510]
+- Updated dependencies [de3d234]
+  - @metamesh/modeling@0.19.0
+
 ## 0.18.0
 
 ### Minor Changes

package/README.md

@@ -1,14 +1,15 @@
 # `@metamesh/generator-sdk`
 
-Define typed controls, presets, and portable contracts for MetaMesh Generators. Use one definition
-for the editing interface, saved parameter values, and model execution.
+Turn a parametric model into a reusable MetaMesh Generator. Define its controls and presets once,
+then use that definition to infer parameter types, validate saved values, and connect the model
+to an editing interface.
 
 > **Preview:** `0.x` minor releases may break compatibility. Patches remain compatible within the
 > same minor line.
 
 ## Installation
 
-For the modeling example below, install matching SDK and Modeling releases:
+Install matching SDK and Modeling releases to build the Generator below:
 
 ```bash
 pnpm add @metamesh/generator-sdk @metamesh/modeling
@@ -18,13 +19,15 @@ The package publishes ES modules only. Use Node.js 24 or newer. TypeScript consu
 TypeScript 6.0 or newer, `strict` checking, and `NodeNext` or `Bundler` module resolution.
 Browser hosts need an ES2023-compatible runtime; the SDK's data contracts require no WebAssembly.
 
-The SDK can also be used alone for definitions, parameter handling, and package validation.
-Only its optional `/modeling` adapter imports the Modeling runtime.
+You can also use the SDK on its own for definitions, parameter handling, and package validation.
+The optional `/modeling` adapter connects it to Modeling; your application supplies the interface
+and execution host.
 
 ## Define controls
 
-A Generator combines serializable metadata with a synchronous model program. This module defines
-a sleeve, infers its parameter types, and checks the relationship between its diameters:
+A Generator combines a definition with a synchronous model program. This example makes a sleeve
+with two diameter controls. Parameter types come from the definition, and an assertion checks
+that the bore fits inside the outer wall:
 
 ```ts
 import { defineGenerator } from "@metamesh/generator-sdk";
@@ -57,21 +60,16 @@ export default defineGeneratorModel(definition, ({ params, assert, part }) => {
 });
 ```
 
-The adapter binds the definition to the model and produces a Generator module. Use
-`defineGeneratorModule({ definition, program })` to bind an existing program. A Generator runtime
-is itself a Modeling program: engines and direct model tests execute `runtime`.
-Format 5 carries the callback and identity in one object; nested
-format-4 runtimes are unsupported. Hosts normalize parameters, prepare assets,
-and execute the model; they own the forms, viewing, persistence, and export.
-Add named, complete starting values with `definePresets(definition, presets)`.
-
-`defineGenerator` validates structural and semantic metadata immediately; `definePresets` validates
-preset metadata and complete canonical parameter values. Invalid input throws
-`GeneratorPackageValidationError` at declaration. Both helpers retain the supplied object or array
-and its inferred literal types. Inline parameter, editor, choice, and preset objects receive
-TypeScript excess-property checks. Structural typing can hide extra fields in variables or generic
-factories; runtime validation checks those fields too. These helpers validate metadata and values,
-not model geometry or cross-parameter assertions.
+`defineGeneratorModel` binds the definition to the model and infers its parameters and services.
+If you already have a program, use `defineGeneratorModule({ definition, program })`. The resulting
+runtime is a Modeling program that an engine or model test can execute directly.
+Add named starting configurations with `definePresets(definition, presets)`; each preset supplies
+a complete parameter map.
+
+Definitions and presets contain serializable data, without callbacks. Hosts normalize parameters,
+prepare assets, and execute the model. They also own forms, viewing, persistence, and export.
+Generator modules use format 5, which carries the callback and identity in one object;
+nested format-4 runtimes are unsupported.
 
 ## Generator capabilities
 
@@ -82,40 +80,51 @@ not model geometry or cross-parameter assertions.
 | Parameters and presets | Inferred TypeScript types, defaults, recovering normalization, strict codecs, and complete serializable presets. |
 | Host integration       | Validated package manifests, module execution, Worker messages, and incremental mesh delivery.                   |
 
-Definitions and presets contain data, not callbacks. Conditional visibility changes the editing
-interface; hidden values remain saved and still require validation. Cross-parameter constraints
-belong in the model's assertions.
+Conditional visibility changes which controls appear. Hidden values remain saved and still
+require validation. Put constraints between parameters in the model's assertions.
+
+## Validate definitions and values
+
+`defineGenerator` checks the definition as soon as you declare it. `definePresets` checks preset
+metadata and complete canonical values. Invalid declarations throw
+`GeneratorPackageValidationError`. These helpers retain the supplied object or array and its
+inferred literal types; they don't execute geometry or model assertions.
+
+Inline parameter, editor, choice, and preset objects receive TypeScript excess-property checks.
+Runtime validation also catches extra fields that structural typing can hide in variables or
+generic factories.
 
 Use `normalizeParameters` to recover saved values: it drops unknown keys, restores defaults, and
-clamps numbers. At strict boundaries, `createParamCodec(definition)` rejects incomplete, unknown, invalid, or
-noncanonical values. The [parameter guide](https://github.com/JasonKoolman/metamesh/blob/main/apps/web/content/docs/develop/parameters-and-validation.mdx)
+clamps numbers. Use `createParamCodec(definition)` when inputs must already be complete and
+canonical; it rejects missing or unknown fields and invalid values. The
+[parameter guide](https://github.com/JasonKoolman/metamesh/blob/main/apps/web/content/docs/develop/parameters-and-validation.mdx)
 covers controls, conditions, and validation.
 
-Use the codec's `parse()` to throw on invalid input, or `safeParse()` for a discriminated result.
-Failure produces issues without substitute parameters. Codec issues use the shared `ParameterIssue`
-shape: `parameterId` names the control, and an optional `path` is relative to that control's value.
-Hosts can pass the issues directly to `aggregateParameterIssues`.
+Use the codec's `parse()` to throw on invalid input, or `safeParse()` for a result you can check
+without catching an exception. A failed parse reports issues without substitute parameters. Each `ParameterIssue` names
+a control with `parameterId`; an optional `path` addresses a field within that control's value.
+Hosts can pass these issues directly to `aggregateParameterIssues`.
+
+## Execute and deliver a model
 
 `executeGenerator` always validates its single `parameters` map against the current definition.
-Hosts may validate before loading assets, but execution does not accept a prior parse result as a
-validation bypass. Modeling hosts use `parseGeneratorModel(value, definition)` from `/modeling`
-to validate an unknown module and infer its executable `GeneratorModel<typeof definition>` type.
-Pass the default export itself for local entries that also export their definition; packaged
-namespaces contain only the default export. The runtime-neutral `parseGeneratorModule` remains
-available from `/runtime`. Invalid envelopes throw `TypeError`. Package validation exposes MetaMesh
-issues and errors, keeping its schema-library adapters private.
-
-Worker model statistics use `signedVolume` in mm³. `generateMs` measures the engine run;
-`timings.totalMs` measures the host workflow and includes stages outside the engine.
-`byteCount` counts finalized world-space position and index buffer bytes, counting shared buffers
-once; it does not measure the local buffers transferred by a Worker.
-Timing stages are optional; hosts report the phases they actually measure. The parameter-processing
-stage is `paramsMs` and finalization is `finalizeMs`.
-
-For Worker hosts, `/modeling` supplies `ModelDeliveryEncoder` and `toWorldMeshes`; `/runtime`
-supplies `PartDeliveryDecoder`. Transfers carry local buffers under `geometry`, with placement
-beside them. Decode resource references before application use and convert to world meshes before
-export. Receiving hosts own the buffers and keep them immutable and attached.
+Hosts can validate before loading assets, but execution still checks the supplied values.
+Modeling hosts use `parseGeneratorModel(value, definition)` from `/modeling` to validate a loaded
+module and infer its executable `GeneratorModel<typeof definition>` type. Pass the default export
+itself for local entries that also export their definition; packaged namespaces contain only the
+default export. Use `parseGeneratorModule` from `/runtime` when you don't need the Modeling adapter.
+Invalid module envelopes throw `TypeError`; package validation reports MetaMesh issues and errors.
+
+For Worker hosts, `/modeling` supplies `ModelDeliveryEncoder`; `/runtime` supplies `PartDeliveryDecoder`.
+Transfers carry local buffers under `geometry`, with placement beside them. Decode resource
+references before application use or export. Receiving hosts own the buffers and keep them immutable
+and attached.
+
+Model statistics use `signedVolume` in mm³. `generateMs` measures the engine run;
+`timings.totalMs` covers the host workflow, including stages outside the engine. Hosts report only
+the timing stages they measure, using `paramsMs` for parameter processing and `finalizeMs` for
+finalization. `byteCount` counts finalized world-space position and index buffer bytes, counting
+shared buffers once; it doesn't measure the local buffers transferred by a Worker.
 
 ## API entry points
 

package/dist/docs/guides/package.md

@@ -1,14 +1,15 @@
 # `@metamesh/generator-sdk`
 
-Define typed controls, presets, and portable contracts for MetaMesh Generators. Use one definition
-for the editing interface, saved parameter values, and model execution.
+Turn a parametric model into a reusable MetaMesh Generator. Define its controls and presets once,
+then use that definition to infer parameter types, validate saved values, and connect the model
+to an editing interface.
 
 > **Preview:** `0.x` minor releases may break compatibility. Patches remain compatible within the
 > same minor line.
 
 ## Installation
 
-For the modeling example below, install matching SDK and Modeling releases:
+Install matching SDK and Modeling releases to build the Generator below:
 
 ```bash
 pnpm add @metamesh/generator-sdk @metamesh/modeling
@@ -18,13 +19,15 @@ The package publishes ES modules only. Use Node.js 24 or newer. TypeScript consu
 TypeScript 6.0 or newer, `strict` checking, and `NodeNext` or `Bundler` module resolution.
 Browser hosts need an ES2023-compatible runtime; the SDK's data contracts require no WebAssembly.
 
-The SDK can also be used alone for definitions, parameter handling, and package validation.
-Only its optional `/modeling` adapter imports the Modeling runtime.
+You can also use the SDK on its own for definitions, parameter handling, and package validation.
+The optional `/modeling` adapter connects it to Modeling; your application supplies the interface
+and execution host.
 
 ## Define controls
 
-A Generator combines serializable metadata with a synchronous model program. This module defines
-a sleeve, infers its parameter types, and checks the relationship between its diameters:
+A Generator combines a definition with a synchronous model program. This example makes a sleeve
+with two diameter controls. Parameter types come from the definition, and an assertion checks
+that the bore fits inside the outer wall:
 
 ```ts
 import { defineGenerator } from "@metamesh/generator-sdk";
@@ -57,21 +60,16 @@ export default defineGeneratorModel(definition, ({ params, assert, part }) => {
 });
 ```
 
-The adapter binds the definition to the model and produces a Generator module. Use
-`defineGeneratorModule({ definition, program })` to bind an existing program. A Generator runtime
-is itself a Modeling program: engines and direct model tests execute `runtime`.
-Format 5 carries the callback and identity in one object; nested
-format-4 runtimes are unsupported. Hosts normalize parameters, prepare assets,
-and execute the model; they own the forms, viewing, persistence, and export.
-Add named, complete starting values with `definePresets(definition, presets)`.
-
-`defineGenerator` validates structural and semantic metadata immediately; `definePresets` validates
-preset metadata and complete canonical parameter values. Invalid input throws
-`GeneratorPackageValidationError` at declaration. Both helpers retain the supplied object or array
-and its inferred literal types. Inline parameter, editor, choice, and preset objects receive
-TypeScript excess-property checks. Structural typing can hide extra fields in variables or generic
-factories; runtime validation checks those fields too. These helpers validate metadata and values,
-not model geometry or cross-parameter assertions.
+`defineGeneratorModel` binds the definition to the model and infers its parameters and services.
+If you already have a program, use `defineGeneratorModule({ definition, program })`. The resulting
+runtime is a Modeling program that an engine or model test can execute directly.
+Add named starting configurations with `definePresets(definition, presets)`; each preset supplies
+a complete parameter map.
+
+Definitions and presets contain serializable data, without callbacks. Hosts normalize parameters,
+prepare assets, and execute the model. They also own forms, viewing, persistence, and export.
+Generator modules use format 5, which carries the callback and identity in one object;
+nested format-4 runtimes are unsupported.
 
 ## Generator capabilities
 
@@ -82,40 +80,51 @@ not model geometry or cross-parameter assertions.
 | Parameters and presets | Inferred TypeScript types, defaults, recovering normalization, strict codecs, and complete serializable presets. |
 | Host integration       | Validated package manifests, module execution, Worker messages, and incremental mesh delivery.                   |
 
-Definitions and presets contain data, not callbacks. Conditional visibility changes the editing
-interface; hidden values remain saved and still require validation. Cross-parameter constraints
-belong in the model's assertions.
+Conditional visibility changes which controls appear. Hidden values remain saved and still
+require validation. Put constraints between parameters in the model's assertions.
+
+## Validate definitions and values
+
+`defineGenerator` checks the definition as soon as you declare it. `definePresets` checks preset
+metadata and complete canonical values. Invalid declarations throw
+`GeneratorPackageValidationError`. These helpers retain the supplied object or array and its
+inferred literal types; they don't execute geometry or model assertions.
+
+Inline parameter, editor, choice, and preset objects receive TypeScript excess-property checks.
+Runtime validation also catches extra fields that structural typing can hide in variables or
+generic factories.
 
 Use `normalizeParameters` to recover saved values: it drops unknown keys, restores defaults, and
-clamps numbers. At strict boundaries, `createParamCodec(definition)` rejects incomplete, unknown, invalid, or
-noncanonical values. The [parameter guide](https://github.com/JasonKoolman/metamesh/blob/main/apps/web/content/docs/develop/parameters-and-validation.mdx)
+clamps numbers. Use `createParamCodec(definition)` when inputs must already be complete and
+canonical; it rejects missing or unknown fields and invalid values. The
+[parameter guide](https://github.com/JasonKoolman/metamesh/blob/main/apps/web/content/docs/develop/parameters-and-validation.mdx)
 covers controls, conditions, and validation.
 
-Use the codec's `parse()` to throw on invalid input, or `safeParse()` for a discriminated result.
-Failure produces issues without substitute parameters. Codec issues use the shared `ParameterIssue`
-shape: `parameterId` names the control, and an optional `path` is relative to that control's value.
-Hosts can pass the issues directly to `aggregateParameterIssues`.
+Use the codec's `parse()` to throw on invalid input, or `safeParse()` for a result you can check
+without catching an exception. A failed parse reports issues without substitute parameters. Each `ParameterIssue` names
+a control with `parameterId`; an optional `path` addresses a field within that control's value.
+Hosts can pass these issues directly to `aggregateParameterIssues`.
+
+## Execute and deliver a model
 
 `executeGenerator` always validates its single `parameters` map against the current definition.
-Hosts may validate before loading assets, but execution does not accept a prior parse result as a
-validation bypass. Modeling hosts use `parseGeneratorModel(value, definition)` from `/modeling`
-to validate an unknown module and infer its executable `GeneratorModel<typeof definition>` type.
-Pass the default export itself for local entries that also export their definition; packaged
-namespaces contain only the default export. The runtime-neutral `parseGeneratorModule` remains
-available from `/runtime`. Invalid envelopes throw `TypeError`. Package validation exposes MetaMesh
-issues and errors, keeping its schema-library adapters private.
-
-Worker model statistics use `signedVolume` in mm³. `generateMs` measures the engine run;
-`timings.totalMs` measures the host workflow and includes stages outside the engine.
-`byteCount` counts finalized world-space position and index buffer bytes, counting shared buffers
-once; it does not measure the local buffers transferred by a Worker.
-Timing stages are optional; hosts report the phases they actually measure. The parameter-processing
-stage is `paramsMs` and finalization is `finalizeMs`.
-
-For Worker hosts, `/modeling` supplies `ModelDeliveryEncoder` and `toWorldMeshes`; `/runtime`
-supplies `PartDeliveryDecoder`. Transfers carry local buffers under `geometry`, with placement
-beside them. Decode resource references before application use and convert to world meshes before
-export. Receiving hosts own the buffers and keep them immutable and attached.
+Hosts can validate before loading assets, but execution still checks the supplied values.
+Modeling hosts use `parseGeneratorModel(value, definition)` from `/modeling` to validate a loaded
+module and infer its executable `GeneratorModel<typeof definition>` type. Pass the default export
+itself for local entries that also export their definition; packaged namespaces contain only the
+default export. Use `parseGeneratorModule` from `/runtime` when you don't need the Modeling adapter.
+Invalid module envelopes throw `TypeError`; package validation reports MetaMesh issues and errors.
+
+For Worker hosts, `/modeling` supplies `ModelDeliveryEncoder`; `/runtime` supplies `PartDeliveryDecoder`.
+Transfers carry local buffers under `geometry`, with placement beside them. Decode resource
+references before application use or export. Receiving hosts own the buffers and keep them immutable
+and attached.
+
+Model statistics use `signedVolume` in mm³. `generateMs` measures the engine run;
+`timings.totalMs` covers the host workflow, including stages outside the engine. Hosts report only
+the timing stages they measure, using `paramsMs` for parameter processing and `finalizeMs` for
+finalization. `byteCount` counts finalized world-space position and index buffer bytes, counting
+shared buffers once; it doesn't measure the local buffers transferred by a Worker.
 
 ## API entry points
 

package/dist/docs/guides/parameters.md

@@ -87,7 +87,7 @@ and `items.ui.step`.
 A Font value contains the selected face and weight. Pass the whole value, rather than a family-name
 string, in `services.text.layout(text, { font, fontSize })` inside generation, then pass its layout to
 `textSection(layout)`. Studio loads declared fonts before generation. See the
-[text recipe](https://metamesh.studio/docs/develop/geometry-recipes#text-from-a-font-parameter) for the setup and offline
+[text recipe](https://metamesh.studio/docs/develop/svg-and-text#text-from-a-font-parameter) for the setup and offline
 limits.
 
 ## Show controls side by side
@@ -269,7 +269,7 @@ with a `parameterId` and positive `factor`, such as `{ "parameterId": "width", "
 Bindings describe the coordinate envelope; they never rescale the saved value. Without them,
 the editor displays percentages.
 
-Inside generation or a computed value, pass `params.crossSection` to
+Inside generation or a memo helper, pass `params.crossSection` to
 [`sampleContour()`](https://metamesh.studio/docs/reference/geometry/sampleContour) with physical `widthScale`,
 `heightScale`, and a millimetre resolution policy. It returns an immutable counterclockwise
 XY `Contour` without a duplicated seam, rejecting invalid sampled topology and exhausted budgets.
@@ -382,10 +382,10 @@ than your model's recommended minimum. A zero wall stops generation; a 0.5 mm wa
 with a warning. Choose that minimum for the model and manufacturing process. A failed edit leaves
 the last valid preview and its export available. Warnings allow a current model to generate and export.
 
-Checks follow JavaScript order: reading a computed value evaluates it when needed, and measuring
+Checks follow JavaScript order: `memo` calls run their helper on a cache miss, and measuring
 geometry evaluates its input first. Draft validation checks declarations and reached assertions
-without finalizing parts; it doesn't prove full geometric validity. Use optional `computed`
-values to reuse expensive layouts or shared calculations across unrelated edits. There is no
+without finalizing parts; it doesn't prove full geometric validity. Use optional `memo`
+calls to reuse expensive layouts or shared calculations across unrelated edits. There is no
 separate preparation callback.
 
 ## Test the definition as a contract

package/dist/docs/manifest.json

@@ -1,7 +1,7 @@
 {
   "formatVersion": 1,
   "packageName": "@metamesh/generator-sdk",
-  "packageVersion": "0.18.0",
+  "packageVersion": "0.19.0",
   "documents": [
     {
       "id": "sdk/guide/authoring",
@@ -1144,20 +1144,6 @@
         "parseGeneratorModel"
       ]
     },
-    {
-      "id": "sdk/reference/modeling/toWorldMeshes",
-      "title": "toWorldMeshes",
-      "summary": "Converts received local geometry and placement into owned world meshes for manufacturing export.",
-      "path": "reference/modeling/toWorldMeshes.md",
-      "importPath": "@metamesh/generator-sdk/modeling",
-      "availability": "Portable Generator contracts",
-      "canonical": "https://metamesh.studio/docs/develop/agent-authoring#generator-entries",
-      "keywords": [
-        "reference",
-        "modeling",
-        "toWorldMeshes"
-      ]
-    },
     {
       "id": "sdk/reference/packages/compareSemanticVersions",
       "title": "compareSemanticVersions",
@@ -1900,62 +1886,6 @@
         "ExecuteGeneratorOptions"
       ]
     },
-    {
-      "id": "sdk/reference/runtime/Export3mfRequest",
-      "title": "Export3mfRequest",
-      "summary": "Export3mfRequest exported from @metamesh/generator-sdk/runtime.",
-      "path": "reference/runtime/Export3mfRequest.md",
-      "importPath": "@metamesh/generator-sdk/runtime",
-      "availability": "Portable Generator contracts",
-      "canonical": "https://metamesh.studio/docs/develop/agent-authoring#generator-entries",
-      "keywords": [
-        "reference",
-        "runtime",
-        "Export3mfRequest"
-      ]
-    },
-    {
-      "id": "sdk/reference/runtime/ExportedFile",
-      "title": "ExportedFile",
-      "summary": "ExportedFile exported from @metamesh/generator-sdk/runtime.",
-      "path": "reference/runtime/ExportedFile.md",
-      "importPath": "@metamesh/generator-sdk/runtime",
-      "availability": "Portable Generator contracts",
-      "canonical": "https://metamesh.studio/docs/develop/agent-authoring#generator-entries",
-      "keywords": [
-        "reference",
-        "runtime",
-        "ExportedFile"
-      ]
-    },
-    {
-      "id": "sdk/reference/runtime/ExportError",
-      "title": "ExportError",
-      "summary": "ExportError exported from @metamesh/generator-sdk/runtime.",
-      "path": "reference/runtime/ExportError.md",
-      "importPath": "@metamesh/generator-sdk/runtime",
-      "availability": "Portable Generator contracts",
-      "canonical": "https://metamesh.studio/docs/develop/agent-authoring#generator-entries",
-      "keywords": [
-        "reference",
-        "runtime",
-        "ExportError"
-      ]
-    },
-    {
-      "id": "sdk/reference/runtime/ExportSuccess",
-      "title": "ExportSuccess",
-      "summary": "ExportSuccess exported from @metamesh/generator-sdk/runtime.",
-      "path": "reference/runtime/ExportSuccess.md",
-      "importPath": "@metamesh/generator-sdk/runtime",
-      "availability": "Portable Generator contracts",
-      "canonical": "https://metamesh.studio/docs/develop/agent-authoring#generator-entries",
-      "keywords": [
-        "reference",
-        "runtime",
-        "ExportSuccess"
-      ]
-    },
     {
       "id": "sdk/reference/runtime/GenerateRequest",
       "title": "GenerateRequest",

package/dist/docs/reference/fonts/FontSelection.md

@@ -2,7 +2,7 @@
 
 An immutable catalog face; revision is the SHA-256 digest of the complete font file.
 
-Import from `@metamesh/generator-sdk/fonts` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk/fonts` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 /** An immutable catalog face; revision is the SHA-256 digest of the complete font file. */

package/dist/docs/reference/fonts/isFontSelection.md

@@ -2,7 +2,7 @@
 
 Checks only the portable value, without consulting a catalog or substituting fonts.
 
-Import from `@metamesh/generator-sdk/fonts` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk/fonts` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 /** Checks only the portable value, without consulting a catalog or substituting fonts. */

package/dist/docs/reference/index/ArrayParameterDefinition.md

@@ -2,7 +2,7 @@
 
 ArrayParameterDefinition exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface ArrayParameterDefinition extends ArrayParameterBase {

package/dist/docs/reference/index/BaseParameterDefinition.md

@@ -2,7 +2,7 @@
 
 BaseParameterDefinition exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface BaseParameterDefinition {

package/dist/docs/reference/index/BooleanParameterDefinition.md

@@ -2,7 +2,7 @@
 
 BooleanParameterDefinition exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface BooleanParameterDefinition extends BaseParameterDefinition {

package/dist/docs/reference/index/ChoiceOption.md

@@ -2,7 +2,7 @@
 
 ChoiceOption exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface ChoiceOption {

package/dist/docs/reference/index/ChoiceParameterDefinition.md

@@ -2,7 +2,7 @@
 
 ChoiceParameterDefinition exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface ChoiceParameterDefinition extends BaseParameterDefinition {

package/dist/docs/reference/index/ChoiceSetParameterDefinition.md

@@ -2,7 +2,7 @@
 
 ChoiceSetParameterDefinition exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface ChoiceSetParameterDefinition extends BaseParameterDefinition {

package/dist/docs/reference/index/ColorParameterDefinition.md

@@ -2,7 +2,7 @@
 
 ColorParameterDefinition exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface ColorParameterDefinition extends BaseParameterDefinition {

package/dist/docs/reference/index/ConditionExpression.md

@@ -2,7 +2,7 @@
 
 ConditionExpression exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export type ConditionExpression = {

package/dist/docs/reference/index/ContourAnchor.md

@@ -2,7 +2,7 @@
 
 Editing intent accompanies the explicit curve controls; no tangent is inferred at runtime.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 /** Editing intent accompanies the explicit curve controls; no tangent is inferred at runtime. */

package/dist/docs/reference/index/ContourParameterDefinition.md

@@ -2,7 +2,7 @@
 
 ContourParameterDefinition exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface ContourParameterDefinition extends BaseParameterDefinition {

package/dist/docs/reference/index/ContourParameterUi.md

@@ -2,7 +2,7 @@
 
 ContourParameterUi exported from @metamesh/generator-sdk.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 export interface ContourParameterUi extends ParameterUi {

package/dist/docs/reference/index/ContourPoint.md

@@ -2,7 +2,7 @@
 
 Normalized planar coordinates, with X rightward and Y upward, in the unit square.
 
-Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.18.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.19.0).
 
 ```ts
 /** Normalized planar coordinates, with X rightward and Y upward, in the unit square. */