@instruktlabs/kiln 1.1.0 → 1.2.0

package/dist/mcp-server.mjs

@@ -2085,7 +2085,7 @@ import { readFile } from "node:fs/promises";
 var KILN_ASSET_WIDGET_URI = "ui://kiln/asset-v5.html";
 
 // src/engine-identity.ts
-var ENGINE_VERSION = "1.1.0";
+var ENGINE_VERSION = "1.2.0";
 var ENGINE_INSTALL_URL = new URL("../", import.meta.url).href;
 
 // src/requirements-json.ts

package/docs/sdk.md

@@ -136,6 +136,29 @@ the stability of the helpers it uses. Exact details retain the same structured
 `stability` field. Implicit modeling remains available without a new opt-in switch;
 the community exporter retains its explicit selection.
 
+## Named operation presentation
+
+In package version 1.2.0 and later, embeddings can select
+`createKilnMcpServer(context, { toolPresentation: 'operations' })`, or obtain the
+same definitions through `createKilnOperationToolRegistry(context)` from `tools`.
+The default MCP and native interfaces retain their existing grouped tools.
+
+With asset and material storage, and without project/review or renderer-control
+callbacks, the named presentation exposes 21 tools. Asset browsing becomes
+`kiln_assets_search` with an optional collection; material browsing becomes
+`kiln_material_search` with `scope: 'all' | 'presets' | 'saved'`. Material creation
+uses `kiln_material_create` with a required `definition` discriminated by
+`kind: 'preset' | 'procedural'`. Saving, importing, retrieval and source restoration
+remain explicit operations. Renderer controls appear only when their callbacks
+exist. Connected `tools/list` remains authoritative.
+
+Action requirements and field constraints come from the shared engine registry.
+Generation rejects unclassified action/field additions and missing required
+fields. Hosts select supported operations and add their actual execution and
+persistence policy; do not copy domain schemas or assume a local read hint
+describes a quota-admitted cloud job. This API change does not publish a package
+or deploy a hosted service. Actual client acceptance is still required.
+
 ## Maintainer qualification
 
 `node scripts/build-runtime.mjs all` builds both executable bundles and the ESM SDK.