@metamesh/generator-sdk 0.15.0 → 0.17.0

package/CHANGELOG.md

@@ -1,5 +1,68 @@
 # @metamesh/generator-sdk
 
+## 0.17.0
+
+### Minor Changes
+
+- Add `defineGeneratorModel(definition, callback)` through the optional
+  `@metamesh/generator-sdk/modeling` adapter. It infers controls, synchronous services, and diagnostic
+  parameter IDs while leaving the SDK root independent of the Modeling runtime.
+
+  Add `runner.withModel(parameters, callback)` and Testkit's `withModel(program, parameters, callback,
+options?)` for scoped assertions. Both await synchronous or asynchronous callbacks and release
+  their snapshot in `finally`; the plain-model helper also releases its temporary session.
+  Generator validation failures throw the existing structured `GenerationError` diagnostics.
+
+  Migration tip: replace private definition-plus-`generate` wrappers with the SDK adapter, and use
+  scoped callbacks instead of repeated successful-result narrowing and snapshot disposal. Keep
+  `runner.execute` and direct engine sessions for tests that inspect invalid results, cache behavior,
+  or explicit snapshot ownership. Prepared services are required for plain models that declare them.
+
+  Scoped callbacks retain snapshot parts without eagerly copying their buffers. For cross-run
+  geometry comparisons, select manufacturing fields rather than transient geometry resource IDs.
+  Capture `positions` and `indices` once before dense traversal: each accessor read returns a copy.
+
+- Add deferred `holeCutter` recipes for circular screw holes and existing Section pocket profiles.
+  Circular cutters support counterbores and countersinks; convex single-contour profiles support
+  45-degree entry chamfers. Explicit `overrun.bottom` and `overrun.top` preserve blind-pocket floors
+  unless the caller deliberately extends the cutter.
+  Circular entry chamfers retain nominal circular radii; Section entry chamfers offset the supplied
+  sampled contour's edges.
+
+  Advance the Modeling host runtime to major 9 for hole cutters and fitted SVG recipe options.
+  Rebuild Generator packages against the new library set; old host/runtime packages are rejected.
+
+  Migration tip: reuse `regularPolygon`, `rectangle`, or other Section constructors as the cutter's
+  `profile`. Position a blind cutter at its intended floor and set only `overrun.top` for opening
+  padding. Keep allowances, minimum floor thickness and feature-specific assertions in your model.
+
+### Patch Changes
+
+- Updated dependencies
+- Updated dependencies [d0cc194]
+- Updated dependencies
+- Updated dependencies
+  - @metamesh/modeling@0.17.0
+
+## 0.16.0
+
+### Minor Changes
+
+- fbd7276: Standardize immutable value interchange on domain names, Data representations, Input construction
+  forms, and toData(). Rename vector tuples and transform matrices to Vector2Data/Vector3Data and
+  Transform2Data/Transform3Data. Path2Data and Path3Data now preserve dimension, points, and closure;
+  path factories accept complete data records as well as coordinate collections. Advance the host
+  runtime to major 8 for the new value protocol, and update consumers, examples, and references.
+- 1585391: Add immutable `bounds2()` and `bounds3()` values with fluent measurements, positioned containment,
+  and plain-data conversion. Path bounds now return these values. Rename plain bounds records to
+  `Bounds2Data` and `Bounds3Data` across geometry, model snapshots, CLI captures, and Testkit contracts.
+  Bounds values in recipe inputs and computed data use the runtime 8 value interchange protocol.
+- 29e19a5: Add portable knuckle hinge joint recipes and a pure layout resolver, with captive, inserted-pin,
+  and lift-off construction, independent per-half mounting webs, and shared bounded physical sampling.
+  Per-half `barrelChamfer` sets the 45-degree outer-rim setback at both ends of every barrel;
+  web `zMin` places the lower face in the pin-centered frame, both in millimetres.
+  The operation uses the runtime 8 modeling contract.
+
 ## 0.15.0
 
 ### Minor Changes

package/README.md

@@ -22,7 +22,7 @@ A definition describes the Generator and its editable parameters. Literal IDs an
 you exact parameter types:
 
 ```ts
-import { defineGenerator, type GeneratorParams } from "@metamesh/generator-sdk";
+import { defineGenerator } from "@metamesh/generator-sdk";
 
 export const definition = defineGenerator({
   id: "sleeve",
@@ -34,7 +34,6 @@ export const definition = defineGenerator({
     { id: "boreDiameter", label: "Bore diameter", type: "number", default: 10, min: 1 },
   ],
 });
-type Parameters = GeneratorParams<typeof definition>;
 ```
 
 Definitions are serializable. Optional `ui` metadata describes grouping, visibility, hints, and
@@ -45,14 +44,14 @@ for the full set of controls.
 
 ## Generate a model
 
-Add a synchronous generation program to the same module. Assertions describe relationships
-between controls; the module helper binds the program to its definition:
+Add a synchronous generation program to the same module. The Modeling adapter infers controls,
+prepared services, and diagnostic parameter IDs from the definition:
 
 ```ts
-import { defineGeneratorModule } from "@metamesh/generator-sdk";
-import { generate, tube } from "@metamesh/modeling";
+import { defineGeneratorModel } from "@metamesh/generator-sdk/modeling";
+import { tube } from "@metamesh/modeling";
 
-const model = generate<Parameters>(({ params, assert, part }) => {
+export default defineGeneratorModel(definition, ({ params, assert, part }) => {
   assert(
     params.boreDiameter < params.outerDiameter,
     "The bore must be smaller than the outside diameter.",
@@ -67,7 +66,6 @@ const model = generate<Parameters>(({ params, assert, part }) => {
     })
   );
 });
-export default defineGeneratorModule({ definition, generate: model });
 ```
 
 Return a single `part(...)` or a readonly array of parts. The host normalizes parameters and prepares
@@ -75,6 +73,9 @@ assets before generation. Modeling manages geometry, sessions, and snapshots; th
 portable definitions, module envelopes, and validated runtime messages. Unsupported package formats
 reject before executable bytes are evaluated.
 
+The optional `/modeling` adapter imports Modeling's program helper; other SDK entry points remain
+independent of its runtime. Use `defineGeneratorModule` when binding an existing model program.
+
 ## Work with saved values
 
 Use `normalizeParameters` from `/parameters` to recover saved values: it drops unknown keys,
@@ -95,6 +96,7 @@ completion; SDK validation also checks references, defaults, and cross-field rul
 | `@metamesh/generator-sdk/runtime`    | Module execution, mesh data, and Worker messages |
 | `@metamesh/generator-sdk/packages`   | Package, catalog, and installation parsing       |
 | `@metamesh/generator-sdk/fonts`      | Immutable font selection values                  |
+| `@metamesh/generator-sdk/modeling`   | Definition-inferred Modeling programs            |
 
 Incremental Worker hosts can use `GeneratedPartsDecoder` from `/runtime` to hydrate validated
 geometry resources while checking part metadata and aggregate limits on every delivery. Keep

package/dist/docs/guides/authoring.md

@@ -1,6 +1,6 @@
 # Design reusable controls
 
-Make a code Project useful to someone else with clear inputs, tested defaults, focused validation, and portable files.
+Design clear controls, useful defaults, and recoverable validation for a reusable code Project.
 
 Turn a working authored Project into a model someone can adjust without reading its source.
 If you need a working model first, follow [Build your first code Project](https://metamesh.studio/docs/develop/code-projects).
@@ -37,7 +37,7 @@ for supported control types and their configuration.
 
 ## Make labels and units unambiguous
 
-Use labels that describe the finished model, such as **Outer Diameter**, rather than a variable
+Use labels that describe the finished model, such as **Outer diameter**, rather than a variable
 name like `d2`. Add a short description when a measurement could have more than one interpretation:
 for example, whether Length includes an end cap.
 
@@ -50,8 +50,8 @@ messages; a clearer label should not require a different identifier.
 
 ## Choose defaults that demonstrate the model
 
-Choose representative defaults that produce a useful, recognizable result without validation
-errors and show the important features without requiring several edits.
+Choose defaults that produce a useful, recognizable model without errors and show its important
+features immediately.
 
 Try the model from the parameter panel with the code editor closed. Confirm that:
 
@@ -70,13 +70,11 @@ range depends on another control, such as a hole that must fit inside a plate.
 
 A helpful message identifies the problem and gives a next action: "Reduce Hole diameter or increase
 Width" is more useful than "Invalid parameters." Associate the message with the relevant control.
-Use an error for unsupported combinations and a warning for a trade-off the person can choose to
-accept. The [validation guide](parameters.md#add-cross-field-validation-in-typescript)
+Use errors for unsupported combinations and warnings for trade-offs the reader can accept. The [validation guide](parameters.md#add-cross-field-validation-in-typescript)
 explains the implementation with examples.
 
-Test more than the default combination. Check the smallest and largest supported dimensions,
-optional features, and any choice or list combinations. After an error, confirm that the suggested
-correction produces a current model again.
+Test the smallest and largest supported dimensions, optional features, and choice or list
+combinations. After an error, confirm that the suggested correction generates a new model.
 
 For the plate above, test these decisions separately:
 
@@ -90,9 +88,8 @@ For the plate above, test these decisions separately:
 
 ## Keep related parts understandable
 
-Use named parts when one set of controls produces related outputs, such as a lid and its container.
-Give them stable, descriptive IDs so inspection and export remain understandable as dimensions
-change. The [part contract](https://metamesh.studio/docs/develop/code-project-contract#parts-and-placement) describes the
+Use stable, descriptive part IDs for related outputs, such as a lid and container, so readers can
+identify them during inspection and export as dimensions change. The [part contract](https://metamesh.studio/docs/develop/code-project-contract#parts-and-placement) describes the
 supported output shape.
 
 Inspect each output and check the exported model in its intended downstream tool. A valid solid
@@ -114,10 +111,9 @@ test runner; the CLI owns compilation and capture tools.
 
 ## Keep a portable copy
 
-Save the authored Project as a `.metamesh.json` file, then
-[import the Project file](https://metamesh.studio/docs/use/projects-and-offline#save-and-import-an-authored-project) to check its source,
-controls, and values. Keep the file in storage you control; browser storage is local to the device
-and profile.
+Save a `.metamesh.json` file, then [import it](https://metamesh.studio/docs/use/projects-and-offline#save-and-import-an-authored-project)
+to check its source, controls, and values. Keep the file in storage you control; browser storage
+belongs to one device and profile.
 
 A saved Project is not a published catalog Generator. Check
 [publishing availability](https://metamesh.studio/docs/create/publishing-status) if you intend to distribute through

package/dist/docs/guides/package.md

@@ -22,7 +22,7 @@ A definition describes the Generator and its editable parameters. Literal IDs an
 you exact parameter types:
 
 ```ts
-import { defineGenerator, type GeneratorParams } from "@metamesh/generator-sdk";
+import { defineGenerator } from "@metamesh/generator-sdk";
 
 export const definition = defineGenerator({
   id: "sleeve",
@@ -34,7 +34,6 @@ export const definition = defineGenerator({
     { id: "boreDiameter", label: "Bore diameter", type: "number", default: 10, min: 1 },
   ],
 });
-type Parameters = GeneratorParams<typeof definition>;
 ```
 
 Definitions are serializable. Optional `ui` metadata describes grouping, visibility, hints, and
@@ -45,14 +44,14 @@ for the full set of controls.
 
 ## Generate a model
 
-Add a synchronous generation program to the same module. Assertions describe relationships
-between controls; the module helper binds the program to its definition:
+Add a synchronous generation program to the same module. The Modeling adapter infers controls,
+prepared services, and diagnostic parameter IDs from the definition:
 
 ```ts
-import { defineGeneratorModule } from "@metamesh/generator-sdk";
-import { generate, tube } from "@metamesh/modeling";
+import { defineGeneratorModel } from "@metamesh/generator-sdk/modeling";
+import { tube } from "@metamesh/modeling";
 
-const model = generate<Parameters>(({ params, assert, part }) => {
+export default defineGeneratorModel(definition, ({ params, assert, part }) => {
   assert(
     params.boreDiameter < params.outerDiameter,
     "The bore must be smaller than the outside diameter.",
@@ -67,7 +66,6 @@ const model = generate<Parameters>(({ params, assert, part }) => {
     })
   );
 });
-export default defineGeneratorModule({ definition, generate: model });
 ```
 
 Return a single `part(...)` or a readonly array of parts. The host normalizes parameters and prepares
@@ -75,6 +73,9 @@ assets before generation. Modeling manages geometry, sessions, and snapshots; th
 portable definitions, module envelopes, and validated runtime messages. Unsupported package formats
 reject before executable bytes are evaluated.
 
+The optional `/modeling` adapter imports Modeling's program helper; other SDK entry points remain
+independent of its runtime. Use `defineGeneratorModule` when binding an existing model program.
+
 ## Work with saved values
 
 Use `normalizeParameters` from `/parameters` to recover saved values: it drops unknown keys,
@@ -95,6 +96,7 @@ completion; SDK validation also checks references, defaults, and cross-field rul
 | `@metamesh/generator-sdk/runtime`    | Module execution, mesh data, and Worker messages |
 | `@metamesh/generator-sdk/packages`   | Package, catalog, and installation parsing       |
 | `@metamesh/generator-sdk/fonts`      | Immutable font selection values                  |
+| `@metamesh/generator-sdk/modeling`   | Definition-inferred Modeling programs            |
 
 Incremental Worker hosts can use `GeneratedPartsDecoder` from `/runtime` to hydrate validated
 geometry resources while checking part metadata and aggregate limits on every delivery. Keep

package/dist/docs/guides/parameters.md

@@ -1,10 +1,10 @@
 # Define parameters and validation
 
-Define model controls, side profiles, closed cross sections, fonts, conditional visibility, and cross-field validation for an authored Project.
+Define typed controls, editable profiles, conditional visibility, and validation for an authored Studio Project.
 
-A reusable code Project exposes meaningful design decisions through controls. Studio stores the
-control definition as JSON-safe Project data, types `params` through the imported `generate`
-helper, and runs executable cross-field validation from `model.ts`.
+Define controls so readers can adjust a model without editing its source. Studio stores the
+definition as JSON-safe Project data, infers `params` through `generate`, and runs cross-field
+validation in `model.ts`.
 
 The JSON document contains required `groups` and `parameters` arrays. A parameter's `type`,
 default, units, bounds, and choices describe its value. Its optional `ui` object describes
@@ -13,11 +13,10 @@ Number and Slider both use `type: "number"`; a Slider also declares `ui.control:
 Options use `type: "choice"`, Side profile uses `type: "side-profile"`, and a closed outline uses
 `type: "contour"`. Changing a numeric widget does not change its saved value or valid range.
 
-JSON editing provides field completion, help, and inline validation. Reference completion suggests
-declared groups, parameters, and choice values. Errors prevent applying the draft; returning to
-Visual requires fixing or discarding invalid JSON.
-For other editors, the SDK ships `@metamesh/generator-sdk/parameters.schema.json`; the SDK parser
-also checks cross-field rules that JSON Schema cannot express.
+JSON editing offers field completion, help, and inline validation, including references to declared
+groups, parameters, and choice values. Fix or discard invalid JSON before applying it or returning
+to Visual. For other editors, use `@metamesh/generator-sdk/parameters.schema.json`; the SDK parser
+also checks rules that JSON Schema cannot express.
 
 ## Open the control editor
 
@@ -34,19 +33,19 @@ The Model controls editor's **Visual** and **JSON** views edit the same draft. C
 
 Preview values are temporary; they do not change the default or the Project's current values.
 
-Use labels to name the decision and descriptions for supplementary help. Defaults should produce a useful model immediately;
-minimum and maximum values should describe the supported input range rather than compensate for a
-missing cross-field rule.
+Use labels to name the decision and descriptions for more detail. Defaults should produce a useful
+model immediately. Use minimum and maximum values for supported field ranges and cross-field
+rules for constraints between controls.
 
 ## Separate help from essential instructions
 
-Keep `description` for explanations, terminology, and examples. Studio shows it on demand when the
-user hovers, focuses, or taps the question-mark help button. Clicking the label focuses the input;
-hovering it does not open help.
-Use one optional static `ui.hint` for a short, essential instruction shown inline whenever the
-control is visible. Omit it when the label is enough. Put guidance covering multiple modes in
-`description`; hints have no conditions. Errors, warnings, and explanations for unavailable
-controls remain visible too.
+Use `description` for explanations, terminology, and examples. Studio shows it when the reader
+hovers, focuses, or taps the question-mark help button. Clicking the label focuses the input;
+hovering the label does not open help.
+
+Use optional `ui.hint` for one short, essential instruction beside the control. Omit it when the
+label is enough. Hints are static and appear whenever the control is visible; put guidance for
+multiple modes in `description`. Errors, warnings, and reasons a control is unavailable stay visible.
 
 In **Visual**, edit **Hint (optional)** as ordinary text. **Visual**, **JSON**, and the live preview
 use the same string field. Clearing it omits the hint when applying the definition. For example,
@@ -81,9 +80,9 @@ avoid repeating labels, units, or descriptions. A declared hint must be non-empt
 | Cross section            | One closed XY outline for extrusion or a swept section          |
 | Number List or Text List | An ordered sequence the user may add, remove, edit, and reorder |
 
-A Slider requires `min`, `max`, and a positive `ui.step`. Multiple choice may require a minimum or maximum
-selection count. List controls can bound their item count; number-list items can also have their own
-unit, limits, and `items.ui.step`.
+A Slider requires `min`, `max`, and a positive `ui.step`. Multiple choice can limit the number of
+selections. Lists can limit their item count; number-list items can also declare units, limits,
+and `items.ui.step`.
 
 A Font value is a structured selection, not a family-name string. Pass the whole value in
 `services.text.layout(text, { font, fontSize })` inside generation, then pass its layout to
@@ -124,15 +123,14 @@ In **JSON**, give the controls the same `ui.row` identifier:
 ]
 ```
 
-These entries belong in the definition's `parameters` array. Row identifiers are local to each
-section, and controls in a row must remain adjacent within that section. Omit `ui.row` for an ordinary
-full-width control. Shared rows support number inputs, `choice`, and `text`; sliders and other control types use
-their own rows. Prefer full width for long option names or text values.
+Add these entries to the definition's `parameters` array. Row IDs are local to each section, and
+shared controls must stay adjacent. Omit `ui.row` for full width. Shared rows support number
+inputs, `choice`, and `text`; sliders and other controls use their own rows. Prefer full width
+for long option names or text.
 
-Shared fields have equal widths and compact labels. They stack when the panel is too
-narrow; when one field is hidden, the remaining field fills the row. Each field keeps its own
-value, units, validation, and history; `params.width` and `params.height` remain
-separate numbers.
+Fields share equal widths and stack in narrow panels. If one is hidden, the other fills the row.
+Each retains its own value, units, validation, and history; `params.width` and `params.height`
+remain separate numbers.
 
 ## Define an editable side profile
 
@@ -310,20 +308,17 @@ In **JSON**, add `"role": "curve-resolution"` to a Number or Slider control to g
 }
 ```
 
-The control remains a saved parameter on `params`. Your source must apply it to geometry,
-for example by passing `resolution: { maxChordError: params.curveResolution }` to each
-affected primitive or Section operation. Share that ordinary options value where several curves
-use the same policy. The declaration alone
-does not change sampling. Keep supported limits and any feature-specific sampling in your model.
-
-Studio groups these fields under **Curve resolution** in Parameters, including the mobile sheet
-where draft validation errors can be corrected. The chosen value affects preview and export through
-the same generation path. Visual editing
-preserves the role; duplicating the control creates an ordinary numeric control. A Project may
-declare multiple Curve resolution controls, shown together in definition order.
-For example, declare separate **Coil path** and **Wire cross-section** values and pass each to the
-appropriate sampler. Your Generator decides which curves or parts each value affects; Studio saves
-the values without assigning them to parts automatically.
+Your source must apply the saved parameter to geometry, for example by passing
+`resolution: { maxChordError: params.curveResolution }` to each affected primitive or Section
+operation. Share the options value when several curves use the same policy. The declaration alone
+does not change sampling; keep supported limits and feature-specific sampling in your model.
+
+Studio groups these controls under **Curve resolution** in definition order, including in the
+mobile sheet. Visual editing preserves the role; duplicating a control creates an ordinary numeric
+control. Each value saves with the Project and affects preview and export through generation.
+
+You can declare separate values for **Coil path** and **Wire cross-section**, then pass each to its
+sampler. Your source decides which curves or parts it affects; Studio does not assign it to parts.
 
 ## Reveal a control only when it applies
 
@@ -350,9 +345,9 @@ array; this example shows Hole diameter only while Add hole is enabled:
 }
 ```
 
-Use `eq` or `ne` for scalar comparisons, `gt`, `gte`, `lt`, or `lte` for numbers, and `contains`
-for Multiple choice membership. Combine conditions with `all`, `any`, or `not`. Font, Side profile, Cross section,
-Number List, and Text List values cannot be the referenced value in a condition.
+Use `eq` or `ne` for scalar comparisons; `gt`, `gte`, `lt`, or `lte` for numbers; and `contains`
+for Multiple choice membership. Combine conditions with `all`, `any`, or `not`. Conditions cannot
+reference Font, Side profile, Cross section, Number List, or Text List values.
 
 The JSON root accepts only `groups` and `parameters`. Project identity, title, and version are
 managed separately by Studio.
@@ -387,11 +382,11 @@ 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 run in JavaScript order. Reading a computed value evaluates it when necessary, and a
-geometry observation must realize its input first. This also applies to draft validation: it runs
-declaration and reached assertions, without finalizing the returned parts. It does not prove full
-geometric validity. Keep exact layouts and shared dimensions in optional `computed` values so
-unrelated edits do not repeat expensive work. There is no separate preparation callback.
+Checks follow JavaScript order: reading a computed value evaluates it when needed, and observing
+geometry evaluates its input first. Draft validation checks declarations and reached assertions
+without finalizing parts; it does not prove full geometric validity. Use optional `computed`
+values 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,12 +1,12 @@
 {
   "formatVersion": 1,
   "packageName": "@metamesh/generator-sdk",
-  "packageVersion": "0.15.0",
+  "packageVersion": "0.17.0",
   "documents": [
     {
       "id": "sdk/guide/authoring",
       "title": "Design reusable controls",
-      "summary": "Make a code Project useful to someone else with clear inputs, tested defaults, focused validation, and portable files.",
+      "summary": "Design clear controls, useful defaults, and recoverable validation for a reusable code Project.",
       "path": "guides/authoring.md",
       "importPath": "@metamesh/generator-sdk",
       "availability": "Reusable controls in Studio code Projects",
@@ -15,7 +15,15 @@
         "guide",
         "authoring",
         "studio",
-        "how-to"
+        "how-to",
+        "design-reusable-controls",
+        "choose-the-decisions-to-expose",
+        "make-labels-and-units-unambiguous",
+        "choose-defaults-that-demonstrate-the-model",
+        "explain-constraints-where-they-matter",
+        "keep-related-parts-understandable",
+        "use-the-same-design-in-a-local-module",
+        "keep-a-portable-copy"
       ]
     },
     {
@@ -35,7 +43,7 @@
     {
       "id": "sdk/guide/parameters",
       "title": "Define parameters and validation",
-      "summary": "Define model controls, side profiles, closed cross sections, fonts, conditional visibility, and cross-field validation for an authored Project.",
+      "summary": "Define typed controls, editable profiles, conditional visibility, and validation for an authored Studio Project.",
       "path": "guides/parameters.md",
       "importPath": "@metamesh/generator-sdk/parameters",
       "availability": "Shared parameter contracts; control editing examples use Studio",
@@ -44,7 +52,18 @@
         "guide",
         "parameters",
         "studio",
-        "how-to"
+        "how-to",
+        "define-parameters-and-validation",
+        "open-the-control-editor",
+        "separate-help-from-essential-instructions",
+        "choose-the-right-control",
+        "show-controls-side-by-side",
+        "define-an-editable-side-profile",
+        "define-an-editable-cross-section",
+        "expose-curve-resolution-in-parameters",
+        "reveal-a-control-only-when-it-applies",
+        "add-cross-field-validation-in-typescript",
+        "test-the-definition-as-a-contract"
       ]
     },
     {
@@ -498,7 +517,7 @@
     {
       "id": "sdk/reference/index/GeneratorProgram",
       "title": "GeneratorProgram",
-      "summary": "Structural program boundary; the SDK never imports a Modeling runtime or kernel.",
+      "summary": "Structural program boundary; the SDK root never imports a Modeling runtime or kernel.",
       "path": "reference/index/GeneratorProgram.md",
       "importPath": "@metamesh/generator-sdk",
       "availability": "Portable Generator contracts",
@@ -1069,6 +1088,20 @@
         "UNPREPARED_GENERATOR_SERVICES"
       ]
     },
+    {
+      "id": "sdk/reference/modeling/defineGeneratorModel",
+      "title": "defineGeneratorModel",
+      "summary": "Defines a Generator model with parameters and prepared services inferred from its definition. The callback stays synchronous; hosts own normalization, assets, execution and cleanup. Import this adapter from `@metamesh/generator-sdk/modeling` with matching Modeling installed.",
+      "path": "reference/modeling/defineGeneratorModel.md",
+      "importPath": "@metamesh/generator-sdk/modeling",
+      "availability": "Portable Generator contracts",
+      "canonical": "https://metamesh.studio/docs/develop/agent-authoring#generator-entries",
+      "keywords": [
+        "reference",
+        "modeling",
+        "defineGeneratorModel"
+      ]
+    },
     {
       "id": "sdk/reference/packages/compareSemanticVersions",
       "title": "compareSemanticVersions",

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.15.0).
+Import from `@metamesh/generator-sdk/fonts` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk/fonts` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.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.15.0).
+Import from `@metamesh/generator-sdk` (@metamesh/generator-sdk@0.17.0).
 
 ```ts
 /** Editing intent accompanies the explicit curve controls; no tangent is inferred at runtime. */