@instruktlabs/kiln 1.0.0-rc.1 → 1.1.0

package/.claude-plugin/marketplace.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
   "name": "instruktlabs",
-  "description": "Instrukt Labs developer tools, including Kiln Engine for editable 3D assets.",
+  "description": "Instrukt Labs developer tools, including Kiln for editable 3D assets.",
   "owner": {
     "name": "Instrukt Labs"
   },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "kiln",
   "description": "Build and revise 3D assets with your coding agent. Write JavaScript, inspect selected views, edit saved source revisions, and export GLB files locally.",
-  "version": "1.0.0-rc.1",
+  "version": "1.1.0",
   "author": {
     "name": "Matthew Kissinger"
   },

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "kiln",
-  "version": "1.0.0-rc.1",
+  "version": "1.1.0",
   "description": "Create, review, save, and refine procedural 3D assets with portable source and GLB collections.",
   "author": {
     "name": "Matthew Kissinger"

package/CHANGELOG.md

@@ -1,14 +1,61 @@
 # Changelog
 
 Changes to `@instruktlabs/kiln` (previously the private `@kiln/engine` package).
-Source releases and installable package publication are
-separate milestones. The package is not published on the npm registry.
-
-## Unreleased
-
-Changes since the 0.10.0 tagged package release. The checkout uses the unpublished
-`1.0.0-rc.1` release candidate. Source/main and website deployment are separate
-from publishing a new installable package.
+Source releases and installable package publication are separate milestones.
+Published versions and tags are recorded by the npm registry; changing this file
+does not publish a package.
+
+## 1.1.0
+
+Existing-project setup, public host interfaces and simpler onboarding. Hosted
+deployment and directory submissions remain deferred.
+
+- `kiln-init --adopt` configures an existing project or a new workspace through
+  the same initializer. Preview with `--adopt --check`; existing instructions,
+  unrelated configuration, saved assets and customized skills remain intact.
+- Multiple compatible client registrations share one program store. Managed
+  upgrades retain narrow configuration ownership and recover interrupted setup
+  writes without putting recovery snapshots inside the project.
+- Explicit migration of a copied legacy OpenCode workspace replaces its old
+  owned skill path instead of loading both original and copied instructions.
+- The local plugin's setup helper uses the pinned engine's adapter list. Plugin
+  installation remains specific to Claude Code and Codex; those clients can also
+  configure another supported workspace adapter through the shared helper.
+- Public `mcp`, `discovery/portable`, `tools/input` and `views/port` SDK entries
+  expose existing host contracts without requiring imports of internal package
+  files. Portable Discovery accepts an engine-generated catalog without loading
+  Node's catalog builder. The local stdio entry keeps lazy engine loading.
+- The release verifier accepts versioned 1.x follow-ups and release candidates,
+  retaining exact-archive evidence and owner promotion approval. Development
+  builds and unsupported prerelease tags remain ineligible for staging.
+- Concurrent captures rejoin a replacement local renderer when a delayed failure
+  arrives from the old connection. Startup failures preserve their bounded child
+  error output instead of reporting only the stack footer.
+- The README and maintained guides lead with npm installation and distinguish
+  released local functionality from deferred hosting. Real Troy captures join the
+  existing scene and vehicle previews. Global and project-local CLI instructions
+  explain the workspace launcher and avoid PowerShell argument forwarding errors.
+  Historical examples move out of the active source tree;
+  pinned Git-history restoration preserves the website archive and regression corpus.
+- The optional Linux isolated evaluator no longer passes an unsupported
+  `--preserve-fds` option to Bubblewrap. Its explicit fd3 protocol pipe uses
+  inherited descriptors; namespace, capability, filesystem and resource limits
+  remain required by readiness qualification.
+- Isolated readiness compares the child's namespace and non-root identity with
+  the parent, accounting for Bubblewrap's nested mapping when further user
+  namespaces are disabled. The final worker environment is cleared again to
+  remove Bubblewrap's injected `PWD` while retaining the exact allowed variables.
+- The isolated worker removes Node's legacy `__proto__` accessor instead of
+  throwing on reads, allowing Khronos glTF validation to initialize. Readiness
+  verifies that the accessor is absent; a regression also checks that assigning
+  a JSON `__proto__` key cannot change an object's prototype.
+
+## 1.0.0
+
+Published on npm as `@instruktlabs/kiln@1.0.0` under `latest`, following the public
+`1.0.0-rc.1` prerelease. These are the changes since the 0.10.0 tagged package.
+Future publication follows the separate release gates in [the runbook](docs/releasing.md).
+Hosted deployment and vendor directory acceptance remain separate milestones.
 
 - **Breaking:** the npm identity is now `@instruktlabs/kiln`, with compiled ESM and
   TypeScript declarations for its public subpaths. The root is a library entrypoint;

package/CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to Kiln
 
-Small fixes, clear bug reports, examples and documentation improvements are welcome.
+Small fixes, clear bug reports, minimal reproductions and documentation improvements are welcome.
 For a behavior bug, include a minimal `.kiln.js` program, the command or tool call,
 and the error or image you saw. Include your OS, Node version and whether rendering
 used CPU or GPU. Remove credentials and private paths from shared logs.
@@ -15,6 +15,7 @@ bun install --frozen-lockfile
 bun run check:toolchain
 bun run check:skills
 bun run build:sdk
+node scripts/example-archive.mjs --fetch
 bun run typecheck
 bun run lint
 bun run test
@@ -27,6 +28,12 @@ separate npm project with its own lockfile and a native dependency.
 `bun run test:render-service` does, after `npm --prefix render-service ci
 --ignore-scripts` once. This suite needs no GPU or Dawn build; CI requires it.
 
+The archive preparation restores pinned historical programs into ignored
+`.cache/example-archive/` for the regression corpus and website archive. It makes
+no model calls, changes no working files and verifies the original Git blob bytes.
+Run it once after cloning; subsequent tests are offline. Old showcase assets are
+not current teaching examples or part of the npm package.
+
 The maintained scenes have a separate lockfile and validation commands:
 
 ```sh
@@ -37,12 +44,11 @@ bun run check:pins
 bun run typecheck
 bun run lint
 bun run test
-bun test ./scripts/tests --timeout 20000
 ```
 
 The pin check reads the engine, render service and site from the same checkout.
-The portable test runner covers scene source contracts; the separate script-test
-command covers the validation and evidence tooling. Asset and browser qualification
+The portable test runner covers scene source contracts and script tests for
+validation and evidence tooling. Asset and browser qualification
 require staged inputs; see [scenes/README.md](scenes/README.md).
 
 `lint` reports **nothing** on a clean tree, and a warning fails it. There is no
@@ -65,8 +71,10 @@ archive qualification, npm staging and owner promotion.
 ahead of that release go in the changelog's `Unreleased` section and can retain the
 released version until the next release is prepared. A new release must bump the
 version before producing its tarball: two different releases must never share a
-package version. Patch for a fix, minor for changed or added capability; this
-package is pre-1.0 and unpublished, so a minor is the normal case.
+package version. Use a patch for compatible fixes, a minor for compatible added
+capabilities, and a major for breaking changes to stable APIs. Kiln 1.0.0 is
+published; the [SDK stability contract](docs/sdk.md#stability-in-1x) identifies
+the explicitly experimental exceptions.
 
 Bumping it means rebuilding: `runtimeBuildIdentity` hashes the version into each
 entry's `identity` in `dist/build.json`, which is the value a build receipt cites. Run
@@ -96,7 +104,8 @@ must be empty and outside the engine installation. Setup copies project-local
 skills and configuration without changing global agent settings or authentication.
 
 In a pull request, describe the problem, resulting behavior and checks you ran.
-Keep generated source examples and their provenance together. If you change a
+Keep generated showcase assets in separate authoring workspaces; include only the
+small reproduction or regression fixture needed for an engine fix. If you change a
 public tool, update its shared registry definition rather than duplicating a
 transport-specific definition.