@instruktlabs/kiln 1.0.0 → 1.2.0

package/plugins/kiln-engine/{scripts/setup-workspace.mjs → bin/kiln-setup-workspace.mjs}

@@ -232,14 +232,15 @@ async function installRuntime(data, pin, archive, archiveHash, options) {
 
 export async function setupPluginWorkspace(options = {}) {
   const harness = options.harness || 'claude';
-  if (!['claude', 'codex'].includes(harness)) throw new Error('Choose harness claude or codex.');
   const mode = options.mode || 'create';
-  if (!['create', 'check', 'upgrade', 'repair'].includes(mode))
+  if (!['create', 'check', 'upgrade', 'repair', 'recover'].includes(mode))
     throw new Error('Unknown workspace setup mode.');
+  if (mode === 'recover' && (options.adopt || options.skills))
+    throw new Error('Use --recover alone before retrying setup.');
   if (!options.directory) throw new Error('Provide a workspace directory.');
   if (
     options.skills &&
-    (mode !== 'create' ||
+    ((mode !== 'create' && !(mode === 'check' && options.adopt)) ||
       !Array.isArray(options.skills) ||
       options.skills.some((name) => !['compose', 'batch'].includes(name)))
   )
@@ -251,6 +252,18 @@ export async function setupPluginWorkspace(options = {}) {
   if (pin.name !== packageName) throw new Error(`The plugin must pin package ${packageName}.`);
   if (typeof pin.version !== 'string' || !exactVersion.test(pin.version))
     throw new Error('The plugin runtime needs an exact stable, rc.N or dev.N version.');
+  // New bundles derive adapters from their pinned engine's initializer. Keep the
+  // original two-client contract for older bundles that have no capability list.
+  const harnesses = pin.harnesses === undefined ? ['claude', 'codex'] : pin.harnesses;
+  if (
+    !Array.isArray(harnesses) ||
+    !harnesses.length ||
+    harnesses.some((name) => typeof name !== 'string' || !/^[a-z][a-z0-9-]{0,63}$/.test(name)) ||
+    new Set(harnesses).size !== harnesses.length
+  )
+    throw new Error('Invalid workspace harness capabilities in the plugin runtime pin.');
+  if (!harnesses.includes(harness))
+    throw new Error(`Choose a supported workspace harness: ${harnesses.join(', ')}.`);
   const directory = await canonical(options.directory);
   const data = await canonical(options.dataDirectory || defaultDataDirectory());
   for (const [a, b] of [
@@ -260,7 +273,7 @@ export async function setupPluginWorkspace(options = {}) {
   ])
     if (inside(a, b) || inside(b, a))
       throw new Error('Keep workspace, runtime data and plugin cache in separate directories.');
-  if (mode === 'create' && (await exists(directory))) {
+  if (mode === 'create' && !options.adopt && (await exists(directory))) {
     if (!(await lstat(directory)).isDirectory() || (await readdir(directory)).length)
       throw new Error(
         'The workspace destination must be an empty directory; no existing files were changed.',
@@ -273,13 +286,22 @@ export async function setupPluginWorkspace(options = {}) {
     { name: pin.name, version: pin.version },
     archive,
     archiveHash,
-    { ...options, mode },
+    { ...options, mode: mode === 'recover' ? 'check' : mode },
   );
-  const { createWorkspace } = await import(
+  const { createWorkspace, workspaceSetupCapabilities } = await import(
     pathToFileURL(join(runtime, 'scripts/create-workspace.mjs')).href
   );
+  if (options.adopt && workspaceSetupCapabilities?.projectAdoption !== 1)
+    throw new Error(
+      'The pinned engine does not support project adoption. Use a plugin release that pins a supporting engine; no project files were changed.',
+    );
+  if (mode === 'recover' && workspaceSetupCapabilities?.recovery !== 1)
+    throw new Error(
+      'The pinned engine does not support project recovery. No project files were changed.',
+    );
   const workspace = await createWorkspace(directory, harness, {
     installation: runtime,
+    ...(options.adopt ? { adopt: true } : {}),
     ...(mode === 'create' ? {} : { [mode]: true }),
     ...(options.skills ? { skills: options.skills } : {}),
   });
@@ -302,9 +324,13 @@ export function parseSetupArguments(args) {
   };
   while (values.length) {
     const flag = values.shift();
-    if (['--check', '--upgrade', '--repair'].includes(flag)) {
-      if (result.mode) throw new Error('Choose only one of --check, --upgrade or --repair.');
+    if (['--check', '--upgrade', '--repair', '--recover'].includes(flag)) {
+      if (result.mode)
+        throw new Error('Choose only one of --check, --upgrade, --repair or --recover.');
       result.mode = flag.slice(2);
+    } else if (flag === '--adopt') {
+      if (result.adopt) throw new Error('Repeated option --adopt.');
+      result.adopt = true;
     } else if (Object.hasOwn(valueFlags, flag)) {
       const value = values.shift();
       if (!value || value.startsWith('--')) throw new Error(`Missing value for ${flag}.`);
@@ -312,6 +338,8 @@ export function parseSetupArguments(args) {
       result[valueFlags[flag]] = flag === '--skills' ? value.split(',') : value;
     } else throw new Error(`Unknown option ${flag}.`);
   }
+  if (result.mode === 'recover' && (result.adopt || result.skills))
+    throw new Error('Use --recover alone before retrying setup.');
   return result;
 }
 
@@ -323,7 +351,7 @@ if (
     const options = parseSetupArguments(process.argv.slice(2));
     if (options.help)
       console.log(
-        'Usage: node scripts/setup-workspace.mjs <directory> [--harness claude|codex] [--skills compose,batch]\n       node scripts/setup-workspace.mjs <managed-workspace> --check|--upgrade|--repair\nOptions: --data-dir <persistent-directory>, --archive <qualification.tgz>, --npm-cli <npm-cli.js>',
+        'Usage: node bin/kiln-setup-workspace.mjs <directory> [--harness NAME] [--skills compose,batch]\n       node bin/kiln-setup-workspace.mjs <project-or-new-workspace> --adopt [--check]\n       node bin/kiln-setup-workspace.mjs <managed-workspace> --check|--upgrade|--repair|--recover\nOptions: --data-dir <persistent-directory>, --archive <qualification.tgz>, --npm-cli <npm-cli.js>\nWorkspace adapters are declared by the pinned engine in runtime.json.',
       );
     else {
       const result = await setupPluginWorkspace(options);

package/plugins/kiln-engine/package-provenance.json

@@ -1,15 +1,22 @@
 {
   "schemaVersion": 1,
   "kind": "kiln-local-plugin",
-  "engineVersion": "1.0.0",
+  "pluginVersion": "1.2.0",
+  "engineVersion": "1.2.0",
+  "executables": [
+    "bin/kiln-setup-workspace.mjs"
+  ],
   "files": {
-    ".claude-plugin/plugin.json": "sha256:c40c7eafed4c0822faef83178633f3bf3449311220f709d5155aed4a9c74cd6b",
+    ".claude-plugin/icon.png": "sha256:b4b651c402793b7e27cab780f04b14f80daec6d0cd5b7e4e90313930581a54e9",
+    ".claude-plugin/plugin.json": "sha256:616a6a61da072fcfdd4d0e1cf513e0e91bf1e56fb61b9b02d23e72fa291556bc",
+    "bin/kiln-setup-workspace.mjs": "sha256:3d9a30236919a6ca91acb6b26f808cec442e6edc3dd88fe010645b010d76e838",
     "LICENSE": "sha256:cdba278ebf1d6de618869936226bf03be4887179c128efc7aaa13d22034826a5",
-    "plugin.json": "sha256:f80ecc90d141adf45e5fadfe5092c325e9174f02b364c1e0059cd5bd345eaaf1",
-    "README.md": "sha256:3a9482e4e8e47b8ef7fb27d2d880253397a7f903b7ccdd64794995fd3075d2dd",
-    "runtime.json": "sha256:18129a1d310c468aeba0966792940242f0359ab14c41a4c9ef240310d07d3bd2",
-    "scripts/setup-workspace.mjs": "sha256:0936f482a213706cf1576da11e57d40993b90f42b486f262e55d38d8d27b2e4d",
-    "skills/kiln-setup-workspace/references/plugin-install.md": "sha256:84f4ce4c9620aae1e6b37a6a04f5c874feae507c9e7a2f24fe62e48bbe6c09bd",
-    "skills/kiln-setup-workspace/SKILL.md": "sha256:9dbcb66514e21ea11b097bb1cd4b27b616834ded3e8182ea804f370add37a69f"
+    "plugin.json": "sha256:3437107d46ad4fef4a710a8e821e56b43894cc1722504fe4e8ff0120fa6a8d8d",
+    "PRIVACY.md": "sha256:5f58d981667e40441e21c2dec411f269a9a67a6141cec61976d27088fb12573b",
+    "README.md": "sha256:0b82e6eb8b679f8b991c1a5567957574ed7b3341a87ef989403e5521f83ab50e",
+    "runtime.json": "sha256:5ebac8387f4bedcc7cac02a36f73c5ffba969ce6c8c6e2b0e356ef569168d0a5",
+    "skills/kiln-setup-workspace/references/plugin-install.md": "sha256:c338fb792e7fad0364c3e1a13c94c506afa1395489ec1b6e83b36d04728935fb",
+    "skills/kiln-setup-workspace/references/renderer-setup.md": "sha256:b743b1b2827fa814385990e1e5b849391cb427413e9c016d273aa19cebd46031",
+    "skills/kiln-setup-workspace/SKILL.md": "sha256:65ed926b3503a33f4fe793e84e4a045ce36e3967f0e6b340e456a15dd010ce54"
   }
 }

package/plugins/kiln-engine/plugin.json

@@ -1,10 +1,11 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "kiln-engine",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "Set up a local Kiln workspace to create, inspect and revise editable 3D assets with Claude Code or Codex.",
   "author": {
-    "name": "Instrukt Labs"
+    "name": "Instrukt Labs",
+    "email": "support@instruktlabs.com"
   },
   "homepage": "https://github.com/instruktlabs/kiln",
   "repository": "https://github.com/instruktlabs/kiln",
@@ -19,10 +20,14 @@
   "extensions": {
     "com.openai": {
       "interface": {
-        "displayName": "Kiln Engine",
+        "displayName": "Kiln",
         "shortDescription": "Create editable 3D assets in a local workspace",
         "longDescription": "Install the pinned Kiln engine and set up a workspace with local MCP tools and maintained authoring skills. Your coding agent supplies the model.",
         "developerName": "Instrukt Labs",
+        "websiteURL": "https://github.com/instruktlabs/kiln/tree/main/plugins/kiln-engine",
+        "supportURL": "https://github.com/instruktlabs/kiln/blob/main/plugins/kiln-engine/README.md#support-and-security",
+        "privacyPolicyURL": "https://github.com/instruktlabs/kiln/blob/main/docs/local-plugin-privacy.md",
+        "termsOfServiceURL": "https://github.com/instruktlabs/kiln/blob/main/LICENSE",
         "category": "Developer Tools",
         "capabilities": [
           "Read",
@@ -30,7 +35,8 @@
         ],
         "defaultPrompt": [
           "Set up a Kiln workspace for this coding agent.",
-          "Check and upgrade my existing Kiln workspace."
+          "Check my existing Kiln workspace without changing it.",
+          "Upgrade my managed Kiln workspace while preserving my assets."
         ]
       }
     }

package/plugins/kiln-engine/runtime.json

@@ -1,4 +1,13 @@
 {
   "name": "@instruktlabs/kiln",
-  "version": "1.0.0"
+  "version": "1.2.0",
+  "harnesses": [
+    "claude",
+    "codex",
+    "opencode",
+    "hermes",
+    "agy",
+    "copilot",
+    "cursor-agent"
+  ]
 }

package/plugins/kiln-engine/skills/kiln-setup-workspace/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: kiln-setup-workspace
-description: Create and verify a Kiln asset workspace for a chosen coding-agent harness. Use before authoring when the current directory is the engine repository, an empty folder, or any project without a working kiln_workspace server.
+description: Configure and verify Kiln in an existing project or a new asset workspace for the selected coding agent. Use before authoring when the project has no working kiln_workspace server or needs another agent integration; engine development stays in the engine checkout.
 license: MIT
 metadata:
   kiln-workflow: workspace
@@ -18,15 +18,18 @@ Do not author assets inside the engine checkout. The authoring skills assume a w
 
 ## Create the workspace
 
-When this skill comes from the **Kiln Engine local plugin**, its plugin root contains `runtime.json` and `scripts/setup-workspace.mjs`. Follow [plugin installation and upgrades](references/plugin-install.md) to install the pinned engine and configure a separate workspace. Do not run the checkout command below from a plugin cache. The plugin registers setup only; the workspace supplies its authoring skills and `kiln_workspace` server.
+When this skill comes from the **Kiln local plugin**, its plugin root contains `runtime.json` and `bin/kiln-setup-workspace.mjs` (plugin 1.0.0 used `scripts/setup-workspace.mjs`). Follow [plugin installation and upgrades](references/plugin-install.md) to install the pinned engine and configure a separate workspace. Do not run the checkout command below from a plugin cache. The plugin registers setup only; the workspace supplies its authoring skills and `kiln_workspace` server.
 
-Choose an absolute path to an empty directory outside the checkout.
+Choose the user's existing project or an absolute path for a new workspace outside the engine installation. Check the installed initializer's `--help`: this setup version supports `--adopt`; older engines support only empty destinations. Upgrade an older installation explicitly before adopting a populated project.
 
 ```bash
-node scripts/create-workspace.mjs /absolute/empty-workspace --harness claude
+node scripts/create-workspace.mjs /absolute/project --adopt --harness claude --check
+node scripts/create-workspace.mjs /absolute/project --adopt --harness claude
 ```
 
-From an installed package, the equivalent is `kiln-init /absolute/empty-workspace --harness claude`. Author, refine and QA skills are installed by default; `--skills compose,batch` adds the optional scene-composition and trial-dispatch workflows. Use the harness already selected by the user or current host; ask only when it is unknown. The choice writes different configuration and cannot be changed afterwards without a fresh workspace.
+From an installed package, use `kiln-init` with the same arguments. Check reports planned changes and exits 1 when changes are needed; it writes nothing. Adoption preserves existing instruction files, unrelated settings, assets and skills. Read the returned `instructions` file (`.kiln/AGENTS.md`) and `.kiln/START.md`, alongside the project's existing instructions. Conflicts stop setup before writes; do not delete or replace owner configuration to make the command pass.
+
+Author, refine and QA skills are installed by default; `--skills compose,batch` adds the optional workflows. Use the agent selected by the user or current host; ask only when it is unknown. Repeat `--adopt --harness codex` (or another supported adapter) to add that integration around the same program store. It explicitly migrates a legacy managed workspace while preserving assets. A combination whose config formats conflict is reported before changes; do not force one client's configuration into another. The plain empty-directory setup command remains compatible with older workflows.
 
 CLI/MCP workspaces use the shared skills under `skills/`. Kiln's optional built-in Strands agent adds its workflow internally, outside that directory. Do not copy its system prompt, native workflow skill or completion protocol into another harness's skills or instructions. This applies to manual setup and plugin installs too; the engine's `src/agent/` directory is not a skill source.
 
@@ -37,24 +40,18 @@ CLI/MCP workspaces use the shared skills under `skills/`. Kiln's optional built-
 | `cursor-agent` | `cursor-agent` |
 | `opencode` | `opencode` |
 | `agy` | `node agy.mjs` |
-| `codex` | `node codex.mjs` |
+| `codex` | `codex` after project trust; `node codex.mjs "TASK"` for a headless run |
 | `hermes` | `node hermes.mjs` |
 
-**Use the launcher where the table names one, and read the workspace's own START.md over this table.** Antigravity, Codex and Hermes keep all configuration in a user-level home and read nothing from a project directory, so their workspace configuration is applied per invocation by the generated launcher. Running their bare command inside the workspace reaches no Kiln tools at all. None of the three writes outside the workspace, and none touches the user's existing configuration or authentication.
+Read `.kiln/START.md` for an adopted project, or `START.md` in a legacy workspace. Codex reads trusted project configuration from `.codex/config.toml`; its optional headless launcher supplies the same settings per invocation without relocating authentication. Antigravity and Hermes use their generated launchers for the measured workspace flow. Setup does not grant project trust or edit global credentials. Skill registration is client-specific: Claude uses `.claude/skills`, Codex uses `.agents/skills`, and OpenCode uses its configured skills path, all copied from the same maintained Kiln skills.
 
 Hermes needs one user-level registration for the MCP server, because it has no project-scoped equivalent and no per-invocation flag for one. Its START.md prints the exact `hermes mcp add` command; offer to run it, and verify with `hermes mcp list`. Never redirect `HERMES_HOME` at the workspace: that one variable resolves the configuration path and the credential path together, so pointing it at a workspace leaves the run with no provider.
 
-## Start the GPU render service
-
-Setup asks for render mode `auto`: textured or metallic scenes use a compatible GPU service, starting one lazily when available. Ordinary untextured scenes with zero metalness and no advanced material extensions use CPU views, even with a GPU available. CPU views support silhouette, proportion and contact review, but cannot confirm PBR appearance. Use CLI `--render gpu` when material review is required, including roughness on nonmetallic surfaces.
-
-The renderer code is included with Kiln; its native GPU dependency is optional at the Kiln package root. For material-dependent tasks, check `node kiln.mjs service status` before starting the authoring session. If dependencies are missing or incompatible, reinstall the official Kiln package with optional dependencies enabled. npm 11 may print an `install-scripts` warning for the optional `webgpu` package; its postinstall only clears the macOS download quarantine from the prebuilt Dawn binary the package ships, so Windows and Linux need nothing and the warning is not an install failure. Read `runtime` from `.kiln/workspace.json` to identify the installation. A source checkout uses `bun install --frozen-lockfile` at that root. Setup checks dependency resolution without loading native code; ready dependencies alone do not prove the device can render.
+## Check rendering readiness
 
-Once dependencies are available, local CLI/MCP auto mode starts a managed service lazily for a view that needs PBR shading. Compatible clients share it; it survives the initiating session and exits after five minutes without admitted uploads, queued jobs or active renders. From the installation root, `node --import ./render-service/src/register-hooks.mjs render-service/src/server.mjs` starts a manual service that remains running while idle. It binds loopback; widening `HOST` requires `RENDER_SERVICE_TOKEN`.
+Setup selects render mode `auto`. Textured or metallic scenes use a compatible render service; plain scenes use CPU geometry views. CPU views cannot confirm PBR appearance. Check `node kiln.mjs service status` before material-dependent work and require a real `viewFidelity` result before claiming material evidence.
 
-`node kiln.mjs service status` reports installation, verified health and lifetime. `node kiln.mjs service start` joins a compatible service or starts a managed one the way an on-demand view does, and prints its port, renderer, pid, lifetime and build; it starts nothing when a stale, foreign or unknown listener holds the socket. After dependency repair or a cached startup failure, call `kiln_renderer({action:"reprobe"})` inside the MCP session to refresh its existing route. It neither installs dependencies nor starts a renderer; the next view starts one if needed. CLI `service reprobe` checks only its own process. Restart the session after changing Kiln, environment variables or credentials. Unknown or incompatible listeners are reported and left alone. `service stop` explicitly stops a verified local service. If no usable GPU is available, report the material-review limitation and continue on CPU views when that fits the task.
-
-A `KILN_RENDER_PORT_URL` whose origin is exactly the shared local socket (`http://127.0.0.1:8000` by default) takes the local route: it starts on demand and restarts after an idle exit. For rendering on another device, configure the MCP server process's `KILN_RENDER_PORT_URL` and, when needed, `KILN_RENDER_TOKEN` through the chosen harness. CLI accepts `--render-port URL` and reads `KILN_RENDER_TOKEN`. Start a compatible Kiln renderer on that device; its wider bind requires `RENDER_SERVICE_TOKEN` unless an authenticated proxy is explicitly configured. Manage the remote service on its own device. Verify the selected route with capabilities and require an actual `viewFidelity` receipt for material evidence.
+Read [local renderer setup](references/renderer-setup.md) when dependencies are missing, a service is unavailable, or the task uses a renderer on another device. It covers dependency repair, shared-service lifetime, reprobe and authenticated remote rendering. Do not replace an unknown listener or install dependencies merely to clear a diagnostic.
 
 ## Verify the loadout before authoring
 
@@ -97,7 +94,9 @@ node /current/kiln/scripts/create-workspace.mjs /absolute/empty-workspace --repa
 
 Repair rewrites generated runtime paths only. It preserves copied skills, saved revisions and assets, refuses configuration that was edited by hand, and does not upgrade the skills.
 
-For an existing workspace, stop its harness/MCP session and run setup from the desired installation with `--check`, then `--upgrade`. Check returns JSON and exits 1 when an update is required. Upgrade refreshes unchanged configuration, instructions and all registered skill copies while preserving assets and source stores. Conflicting local edits stop the whole upgrade before writing. Older instruction files without ownership hashes also require explicit resolution: preserve them separately, compare against a fresh temporary workspace, then move them aside or supply the current version before retrying. Reapply compatible customizations after upgrading. Do not overwrite an edited file merely to clear a conflict.
+For an existing workspace, stop its harness/MCP session and run setup from the desired installation with `--check`, then `--upgrade`. Check returns JSON and exits 1 when an update is required. Upgrade refreshes unchanged owned configuration, instructions and registered skill copies while preserving assets and source stores. Conflicting local edits stop the whole upgrade before writing. Adopted projects preserve unrelated configuration changes and leave pre-existing instruction files alone. Legacy instruction files without ownership hashes can require explicit resolution; preserve them before resolving the named conflict. Do not overwrite an edited file merely to clear a diagnostic.
+
+If adopted-project setup stops partway through writing, it attempts rollback. When it reports recovery required, preserve the project and run `kiln-init /absolute/project --recover` after confirming setup has stopped. Recovery refuses conflicting edits and retains its private snapshots outside the project. Resolve named conflicts explicitly; do not delete a lock or journal to force another setup. Recovery is for interrupted setup, not a general asset backup.
 
 New managed launchers reject runtime/skill mismatches before serving tools; older workspaces need this explicit check first. Restart the harness/MCP session after upgrading so cached tool schemas and instructions match. `--repair` alone does not refresh copied skills or a running session. For independent model evaluations, create a fresh workspace from the candidate.
 
@@ -105,4 +104,4 @@ Discovery replaces the removed `kiln_list_primitives` tool; its old `name`, `nam
 
 ## What isolation means
 
-A separate workspace limits task context. It is not an operating-system sandbox, and it is not a git repository. User-level instructions, memory, authentication and filesystem permissions still apply. For comparing harnesses or models, read `skills/kiln-batch-dispatch/references/clean-room-evaluation.md` in the engine checkout, which covers recording inherited context and reporting trials.
+A separate workspace limits task context; an adopted project retains its existing application context and Git repository. Neither is an operating-system sandbox. User-level instructions, memory, authentication and filesystem permissions still apply. For comparing harnesses or models, use a fresh workspace and read `skills/kiln-batch-dispatch/references/clean-room-evaluation.md`, which covers inherited context and reporting trials.

package/plugins/kiln-engine/skills/kiln-setup-workspace/references/plugin-install.md

@@ -4,19 +4,27 @@ The local `kiln-engine` plugin installs Kiln's exact pinned npm version and crea
 an asset workspace. It carries setup guidance and a small installer; the engine,
 source stores and authored assets live outside the plugin cache. It needs a
 supported Node.js installation with npm, network access for first installation,
-and no separate model API key.
+and no separate model API key. Use it in Claude Code or Codex; it requires a local
+shell and persistent filesystem and is not a Claude chat or Cowork plugin.
 
 Resolve the plugin root from this installed skill's absolute path: it is two
 directories above `skills/kiln-setup-workspace`. Confirm `runtime.json` and
-`scripts/setup-workspace.mjs` exist there. Do not assume plugin path variables are
+`bin/kiln-setup-workspace.mjs` exist there. Do not assume plugin path variables are
 available in an ordinary shell, and do not substitute an engine checkout.
 
+Plugin version 1.0.0 used `scripts/setup-workspace.mjs`; if using that older
+installation, confirm and use that file instead. Plugin and engine versions are
+independent. `runtime.json` always names the exact engine to install.
+
 For a fresh workspace, use an absolute empty destination outside both the plugin
-and its runtime data directory. Select `claude` or `codex` from the current host
-or the user's stated choice:
+and its runtime data directory. Select the current host or the user's stated
+adapter. New bundles list the engine's supported adapters in `runtime.json`;
+older bundles without that list accept `claude` or `codex` only. The plugin itself
+is installed in Claude Code or Codex, but its helper can configure another adapter
+supported by the pinned engine:
 
 ```sh
-node "/absolute/plugin/scripts/setup-workspace.mjs" "/absolute/my-assets" --harness codex
+node "/absolute/plugin/bin/kiln-setup-workspace.mjs" "/absolute/my-assets" --harness codex
 ```
 
 The installer verifies the package name and exact version from `runtime.json`.
@@ -27,11 +35,23 @@ or `$XDG_DATA_HOME/instruktlabs/kiln` on other systems, falling back to
 Do not place it or the asset workspace inside a removable plugin version directory.
 
 Read the returned workspace's `START.md`. Open Claude Code in that workspace, or
-launch Codex there with `node codex.mjs`. Accept the host's ordinary project/MCP
+launch Codex there with `codex`. The `node codex.mjs "TASK"` launcher is for
+headless execution with an explicit prompt. Accept the host's ordinary project/MCP
 trust prompts, then call `kiln_discover({capabilities:true})` on `kiln_workspace`.
 Compare its installation identity to `.kiln/workspace.json`; a config file alone
 does not prove the server loaded. The plugin itself starts no global MCP server.
 
+For an existing project, use a plugin whose helper advertises `--adopt` and whose
+pinned engine supports project adoption. The published engine 1.0.0 predates this
+feature. The helper checks the engine capability and refuses unsupported adoption
+instead of silently falling back to empty-folder setup. Preview with
+`--adopt --check --harness codex`, then apply with `--adopt --harness codex`.
+Use the same path with another `--harness` to add an integration around the same
+assets. Read the returned `instructions` path and `.kiln/START.md`; existing project
+instruction files remain intact. The helper still leaves normal client trust
+prompts to the host. No manual changes to a plugin's runtime pin are needed or
+appropriate.
+
 If the current workspace already has a working `kiln_workspace`, keep it. Do not
 create a second server. Use its installed authoring skills, which come from its
 engine version. The plugin supplies only setup, so authoring instructions are not
@@ -43,8 +63,8 @@ For an existing managed workspace, stop its harness session and run the new
 plugin's helper with `--check`, then `--upgrade` when an update is intended:
 
 ```sh
-node "/absolute/plugin/scripts/setup-workspace.mjs" "/absolute/my-assets" --check
-node "/absolute/plugin/scripts/setup-workspace.mjs" "/absolute/my-assets" --upgrade
+node "/absolute/plugin/bin/kiln-setup-workspace.mjs" "/absolute/my-assets" --check
+node "/absolute/plugin/bin/kiln-setup-workspace.mjs" "/absolute/my-assets" --upgrade
 ```
 
 Check is read-only and reports a missing pinned engine without installing it.

package/plugins/kiln-engine/skills/kiln-setup-workspace/references/renderer-setup.md

@@ -0,0 +1,11 @@
+# Local renderer setup
+
+Setup asks for render mode `auto`: textured or metallic scenes use a compatible GPU service, starting one lazily when available. Ordinary untextured scenes with zero metalness and no advanced material extensions use CPU views, even with a GPU available. CPU views support silhouette, proportion and contact review, but cannot confirm PBR appearance. Use CLI `--render gpu` when material review is required, including roughness on nonmetallic surfaces.
+
+The renderer code is included with Kiln; its native GPU dependency is optional at the Kiln package root. For material-dependent tasks, check `node kiln.mjs service status` before starting the authoring session. If dependencies are missing or incompatible, reinstall the official Kiln package with optional dependencies enabled. npm 11 may print an `install-scripts` warning for the optional `webgpu` package; its postinstall only clears the macOS download quarantine from the prebuilt Dawn binary the package ships, so Windows and Linux need nothing and the warning is not an install failure. Read `runtime` from `.kiln/workspace.json` to identify the installation. A source checkout uses `bun install --frozen-lockfile` at that root. Setup checks dependency resolution without loading native code; ready dependencies alone do not prove the device can render.
+
+Once dependencies are available, local CLI/MCP auto mode starts a managed service lazily for a view that needs PBR shading. Compatible clients share it; it survives the initiating session and exits after five minutes without admitted uploads, queued jobs or active renders. From the installation root, `node --import ./render-service/src/register-hooks.mjs render-service/src/server.mjs` starts a manual service that remains running while idle. It binds loopback; widening `HOST` requires `RENDER_SERVICE_TOKEN`.
+
+`node kiln.mjs service status` reports installation, verified health and lifetime. `node kiln.mjs service start` joins a compatible service or starts a managed one the way an on-demand view does, and prints its port, renderer, pid, lifetime and build; it starts nothing when a stale, foreign or unknown listener holds the socket. After dependency repair or a cached startup failure, call `kiln_renderer({action:"reprobe"})` inside the MCP session to refresh its existing route. It neither installs dependencies nor starts a renderer; the next view starts one if needed. CLI `service reprobe` checks only its own process. Restart the session after changing Kiln, environment variables or credentials. Unknown or incompatible listeners are reported and left alone. `service stop` explicitly stops a verified local service. If no usable GPU is available, report the material-review limitation and continue on CPU views when that fits the task.
+
+A `KILN_RENDER_PORT_URL` whose origin is exactly the shared local socket (`http://127.0.0.1:8000` by default) takes the local route: it starts on demand and restarts after an idle exit. For rendering on another device, configure the MCP server process's `KILN_RENDER_PORT_URL` and, when needed, `KILN_RENDER_TOKEN` through the chosen harness. CLI accepts `--render-port URL` and reads `KILN_RENDER_TOKEN`. Start a compatible Kiln renderer on that device; its wider bind requires `RENDER_SERVICE_TOKEN` unless an authenticated proxy is explicitly configured. Manage the remote service on its own device. Verify the selected route with capabilities and require an actual `viewFidelity` receipt for material evidence.

package/scripts/create-workspace.mjs

@@ -22,11 +22,24 @@ import { assertNodeRuntime } from '../src/runtime-support.mjs';
 const installation = resolve(dirname(fileURLToPath(import.meta.url)), '..');
 const quote = JSON.stringify;
 const hash = (value) => createHash('sha256').update(value).digest('hex');
-const harnesses = ['claude', 'codex', 'opencode', 'hermes', 'agy', 'copilot', 'cursor-agent'];
+const harnesses = Object.freeze([
+  'claude',
+  'codex',
+  'opencode',
+  'hermes',
+  'agy',
+  'copilot',
+  'cursor-agent',
+]);
+export const workspaceSetupCapabilities = Object.freeze({
+  projectAdoption: 1,
+  recovery: 1,
+  harnesses,
+});
 /**
  * Where the chosen harness looks for project skills, relative to the workspace, as
- * measured on the installed CLIs (docs/harnesses.md). Claude Code names `.claude/skills`
- * and `.agents/skills`, so a workspace that carried both registered every skill twice;
+ * measured on the installed CLIs (docs/harnesses.md). Fresh-profile probes on
+ * 2026-10-07 load Claude skills from `.claude/skills`, not `.agents/skills`;
  * codex, hermes, agy, copilot and cursor-agent name `.agents/skills`; opencode reads only
  * the `skills.paths` its generated config names, which is `skills/` itself. One registry
  * per harness: every copy is bytes an upgrade must track and a reader may edit.
@@ -304,7 +317,7 @@ try {
 }
 
 function startGuide(root, runtime, harness, nodeExecutable, server) {
-  const launchers = { agy: 'node agy.mjs', codex: 'node codex.mjs', hermes: 'node hermes.mjs' };
+  const launchers = { agy: 'node agy.mjs', hermes: 'node hermes.mjs' };
   const command = launchers[harness] ?? harness;
   const launch =
     harness === 'hermes'
@@ -573,13 +586,30 @@ export async function renderServiceNotice(runtime) {
 /** Preflight first; create a complete project in a staging directory before installing it. */
 export async function createWorkspace(directory, harness = 'claude', options = {}) {
   let root = resolve(directory);
+  if (options.recover) {
+    if (options.repair || options.upgrade || options.check || options.adopt || options.skills)
+      throw new Error('Use --recover alone before retrying setup.');
+    const { recoverProjectEdits } = await import('./workspace-transaction.mjs');
+    return recoverProjectEdits(root, { stateDirectory: options.stateDirectory });
+  }
   const runtime = await realpath(resolve(options.installation ?? installation));
   if ([options.repair, options.upgrade, options.check].filter(Boolean).length > 1)
     throw new Error('Choose only one of --repair, --upgrade or --check.');
-  if ((options.repair || options.upgrade || options.check) && options.skills)
+  if ((options.repair || options.upgrade || (options.check && !options.adopt)) && options.skills)
     throw new Error('Maintenance does not change the installed skill selection.');
-  const previous =
-    options.repair || options.upgrade || options.check ? await readManifest(root) : undefined;
+  let previous;
+  if (options.adopt) {
+    const bytes = await workspaceFile(root, '.kiln/workspace.json');
+    if (bytes !== undefined) {
+      try {
+        previous = JSON.parse(bytes.toString('utf8'));
+        if (!previous || typeof previous !== 'object' || Array.isArray(previous)) throw new Error();
+      } catch {
+        throw new Error('Invalid Kiln workspace manifest; no files were changed.');
+      }
+    }
+  } else if (options.repair || options.upgrade || options.check)
+    previous = await readManifest(root);
   // A read-only check validates the configured interpreter, not whichever supported
   // Node the caller's shell selected. Setup/repair/upgrade deliberately repin it.
   // A missing recorded executable remains drift; do not silently accept that case.
@@ -588,17 +618,20 @@ export async function createWorkspace(directory, harness = 'claude', options = {
     options.check && typeof previous?.node === 'string' && existsSync(previous.node)
       ? previous.node
       : realpathSync(process.execPath);
-  if (previous) harness = previous.harness;
+  if (previous && !options.adopt) harness = previous.harness;
   if (!harnesses.includes(harness)) throw new Error(`Choose ${harnesses.join(', ')}.`);
   const extras = options.skills ?? [];
   if (extras.some((name) => !Object.hasOwn(optional, name)))
     throw new Error('Optional skills: compose,batch.');
-  const skills = previous?.skills ?? [...core, ...new Set(extras.map((name) => optional[name]))];
+  const previousSkills = previous?.skills ?? core;
   if (
-    !Array.isArray(skills) ||
-    skills.some((name) => ![...core, ...Object.values(optional)].includes(name))
+    !Array.isArray(previousSkills) ||
+    !core.every((name) => previousSkills.includes(name)) ||
+    new Set(previousSkills).size !== previousSkills.length ||
+    previousSkills.some((name) => ![...core, ...Object.values(optional)].includes(name))
   )
     throw new Error('Invalid workspace skill manifest.');
+  const skills = [...new Set([...previousSkills, ...extras.map((name) => optional[name])])];
   const pkg = await preflightRuntime(runtime, skills, !options.check);
   let exists = false;
   try {
@@ -631,7 +664,7 @@ export async function createWorkspace(directory, harness = 'claude', options = {
   }
   if (inside(runtime, root) || inside(runtime, ancestor))
     throw new Error('Choose a directory outside the Kiln installation.');
-  if (!previous && exists && (await readdir(root)).length)
+  if (!options.adopt && !previous && exists && (await readdir(root)).length)
     throw new Error('The destination must be empty; no existing files were changed.');
   const { files, store, server } = managedFiles(root, runtime, harness, nodeExecutable);
   const manifest = {
@@ -660,6 +693,29 @@ export async function createWorkspace(directory, harness = 'claude', options = {
       : undefined,
     generated: Object.fromEntries(Object.entries(files).map(([name, body]) => [name, hash(body)])),
   };
+  if (options.adopt || previous?.schemaVersion === 2) {
+    const { setupProject } = await import('./workspace-project.mjs');
+    return setupProject({
+      root,
+      runtime,
+      harness,
+      previous,
+      metadata: manifest,
+      exists,
+      options,
+      guide,
+      allowedHarnesses: harnesses,
+      projectFiles: (selected) => managedFiles(root, runtime, selected, nodeExecutable).files,
+      startGuide: (selected) => startGuide(root, runtime, selected, nodeExecutable, server),
+      skillFiles: async () => {
+        const result = {};
+        for (const skill of skills)
+          for (const name of Object.keys(await fileHashes(join(runtime, 'skills', skill))).sort())
+            result[`${skill}/${name}`] = await readFile(join(runtime, 'skills', skill, name));
+        return result;
+      },
+    });
+  }
   if (previous && (options.upgrade || options.check))
     return upgradeWorkspace(root, runtime, previous, manifest, files, options.check);
   if (previous) {
@@ -773,7 +829,7 @@ if (isDirectSetupEntry()) {
     const args = process.argv.slice(2);
     if (args.includes('--help') || args.includes('-h')) {
       console.log(
-        `Usage: kiln-init <empty-directory> [--harness ${harnesses.join('|')}] [--skills compose,batch]\n       kiln-init <managed-workspace> --repair|--check|--upgrade`,
+        `Usage: kiln-init <empty-directory> [--harness ${harnesses.join('|')}] [--skills compose,batch]\n       kiln-init <project-or-new-workspace> --adopt [--harness NAME] [--check]\n       kiln-init <managed-workspace> --repair|--check|--upgrade\n       kiln-init <project> --recover`,
       );
     } else {
       const directory = args.shift();
@@ -786,6 +842,8 @@ if (isDirectSetupEntry()) {
         if (flag === '--repair') options.repair = true;
         else if (flag === '--upgrade') options.upgrade = true;
         else if (flag === '--check') options.check = true;
+        else if (flag === '--adopt') options.adopt = true;
+        else if (flag === '--recover') options.recover = true;
         else if (flag === '--harness' || flag === '--skills') {
           const value = args.shift();
           if (!value || value.startsWith('--')) throw new Error(`${flag} requires a value.`);