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.
Native hosting qualification
This is a fixed, one-shot probe for an installed Kiln archive. It accepts no user source, has no HTTP endpoint, deploys nothing and contains no cloud credentials. Its output is provider-neutral evidence; the caller must separately record the actual provider deployment and immutable image digest. A local run never proves Cloudflare compatibility.
Build a minimal Docker context containing only these six files:
Dockerfile,native-qualification.mjs,run-native-qualification.mjsfrom this directory.smoke-renderer.mjsfrom the parent scripts directory.- The reviewed npm archive renamed
candidate.tgzand acandidate.sha256file containing its reviewed SHA-256 followed by two spaces andcandidate.tgz.
Use docker build --platform linux/amd64 --tag kiln-native-probe CONTEXT.
Do not send the engine checkout, credentials, authored workspaces or the entire
local cache as the build context. The image checks the archive digest, uses the
pinned Node base and npm toolchain, installs dependencies without lifecycle
scripts, retains the resolved npm lock and OS package inventory, and runs as the
non-root node user. The image's installed dependency graph and final digest still
need review; the archive alone does not pin its transitive dependencies.
Run without host mounts, provider keys or network access. For a local Docker
preflight, use an explicitly named fresh container, --network none, a memory
limit, a CPU limit, and a PID limit. Copy /tmp/qualification out after exit and
inspect its receipt before removing that specific probe container. Do not add
privileged mode, host namespaces, extra capabilities or a looser seccomp profile
to force a pass. Check the current daemon state before a local run; earlier
unavailable-daemon records do not describe its present state.
The separate Native hosting preflight GitHub workflow builds this six-file
context on Linux, records the exact archive/image/dependency identities, and runs
with no network or host mounts, one CPU, 6 GiB memory, 256 PIDs, no capabilities
and no new privileges. Its explicit --expect-unsupported-isolation mode requires
kernel namespace permission denial, readiness rejection and a failed source
request with no artifact. This emits kiln.unsupported-evaluator-rejection.v1,
which records isolatedExecutionAvailable: false; it never counts as successful
isolation. Unexpected readiness success, source execution or a different failure
fails this negative-host test. The separate software-renderer fixture must also
pass. Original failed receipts remain retained; CI evidence does not establish
Cloudflare support.
An additional Installed nested evaluator job tests the archive on an
unprivileged Ubuntu 22.04 VM, with a source-pinned non-setuid Bubblewrap build and
no changes to host security policy. Its explicit --isolation-only mode emits a
different receipt, kiln.nested-evaluator-qualification.v1: all ten readiness
invariants and nine host/evaluation/CPU/limit checks must pass. It uses dedicated
/usr/local/bin/kiln-probe-bwrap and kiln-probe-node binaries, records their
hashes and installs the archive at /app outside the source checkout. This mode
does not test software rendering or qualify Cloudflare. Both the positive VM job
and the restricted Docker refusal/renderer job must pass. The former passed all
nine checks at 5b1094c, with archive and artifact hashes independently verified;
see the preflight evidence.
The negative-host mode is selected explicitly, never as a fallback after failed
positive qualification. The default command still requires complete positive
evaluation and software rendering on a compatible host.
The initial Bookworm image built but Mesa 22.3 failed Dawn's required Vulkan features. The pinned Trixie replacement passes the six-image software fixture. Its separate namespace probe still fails on the GitHub Docker host; an explicit user namespace is required by the engine launch, and unsupported hosts stop before evaluating source. See the execution record for exact run/image/archive identities and retained failures.
The probe stops at the first failure. Successful readiness must contain all ten engine invariants. Only then does it evaluate a fixed box twice through the isolated evaluator, verify matching GLB bytes and a nonblank CPU preview, enforce deadline/cancellation/output limits, and render again after the limit tests. The existing renderer probe separately requires a software adapter and verifies a textured fixture with six retained PNGs. That fixture is trusted; it does not establish the source isolation boundary.
Timing names mean first/repeated evaluator calls, not measured cold/warm provider starts. Deadlines and cancellation include worker startup, so these checks do not prove that native compute was running at interruption. Process resource usage is for the parent only. Available cgroup counters cover the container, and may include startup or earlier work; retain the before/after snapshots without relabeling them as per-job RSS or billed CPU. Load, tenancy, persistence, retention and cost remain separate service tests.
Cloudflare's documented microVM boundary does not guarantee nested namespace support. Kiln's hosted candidate explicitly selects its separately qualified fresh-VM adapter; these generic SDK probes do not qualify that provider boundary. Never silently substitute ordinary subprocess execution when nested isolation fails. Keep provider image/controller, tenancy and whole-instance cleanup evidence separate from these two CI host profiles.
References checked 6 October 2026: container lifecycle, sandbox security, local build prerequisites.