Skip to content

armgit / kiln

Public Imported from GitHub
0

Build and revise procedural 3D assets with your coding agent. Local MCP server, CLI and TypeScript engine with rendered review, editable source and GLB export.

4.8 KB
Raw Blame

Package platform checks

Short-reference update — 5 September 2026

The newer short-reference runtime passes 16 package checks on each platform:

Platform Receipt
Windows x64 Local Node package
Linux x64 Isolated Node package
macOS ARM64 Hosted native Node package
macOS x64 Hosted native Node package

Windows/Linux used tarball 19add77366f489f078ca50f58d6d0bcb4c4d3e86a18df4bc8da387285ab90822. The GitHub CI run built and tested tarball eddff8da662dd69f5f241d91eada7cca33400cefd5e9028422fd68bcd02bb78e on both Mac architectures. These are distinct archives; the receipts retain their exact identities. The checks cover CPU rendering, CLI/MCP editing and persistence, not optional GPU rendering or a complete desktop-harness setup on a physical Mac.

Earlier runtime candidate — 5 September 2026

The actual @kiln/engine 0.6.0 candidate installed without development dependencies and passed all 15 distribution checks on Windows and Linux x64. Both used Node 22.23.1 and npm 12.0.1, with spaces and Unicode in install/workspace paths.

Platform Result Exact receipt
Windows x64 15 checks passed Windows
Linux x64 15 checks passed Linux
macOS Deferred to community verification No support-validation claim

The exact tarball SHA-256 is:

0d457e8f8763730079da013abfa6662aadc02843f090fcae594c0f711399d16c

CLI and MCP bundle hashes, and original/edited source references, match across the two receipts. The check covers packaged plugin manifests; direct Node and npm CLI entry points; kiln-init; CSG and UV WASM; CPU PNG; source references from another working directory; the packaged Node worker; MCP discovery; reference edits with images; source persistence across restart; and exact source export.

The final two checks exercise --capture from the installed CLI: a JSON recipe selects two part-relative views and produces a 332×168 PNG; changing a camera changes the image; the exported GLB remains byte-identical; camera-only export reports reuse of the evaluated build. These checks pass a saved reference, not source code.

No providers or GPU services were called by these package tests. They verify the CPU distribution workflow, not GPU setup, model quality, or an operating-system sandbox for untrusted source. Actual GPU evidence is tracked in the camera guide and model-run receipts. The Windows install is retained outside the checkout; the Linux container was removed after its JSON receipt was retained.

Linux environment and reproduction

The Linux container uses two CPUs, a 2 GiB memory limit and this pinned official image:

node:22.23.1-bookworm-slim@sha256:6c74791e557ce11fc957704f6d4fe134a7bc8d6f5ca4403205b2966bd488f6b3

With Docker running, from the repository:

node scripts/smoke-package-linux.mjs /absolute/candidate.tgz /absolute/receipt.json

The wrapper mounts only the tarball and smoke scripts read-only, installs npm 12.0.1 inside the temporary container, and verifies platform, versions and the tarball hash. It may download the pinned image and dependencies. It installs nothing globally on the host and publishes nothing.

Earlier candidates and failures

The earlier 614b1c9e candidate passed its then-current 13-check smoke on Windows and Linux. Those receipts remain historical evidence; they do not cover the subsequently added camera-file export.

The first candidate ran directly through Node, but the npm CLI symlink skipped its entry point and exited without help output. The next candidate exposed the same error in kiln-init. Both guards now compare resolved filesystem paths. A focused regression exercises linked entries and verifies direct imports stay inert; the final Linux package check exercises actual npm symlinks successfully.

The capture check also rejects a missing shortened subject name with the canonical reason and confirms recovery using an exact returned part path. This closes the CLI diagnostic gap seen during the Muse run. The three model recertifications remain attributed to package 833b9bf1; the final package only adds that CLI error message. MCP, worker, agent runtime and provider bundles are byte-identical. See the package delta receipt.