Fixes a production crash-loop (PostHog issue 019eb68e): ktx mcp start
--foreground on a uv-less container eagerly installed the managed Python
runtime at boot, failed, and was restarted by its supervisor every ~62s
(122 exceptions from one install).
- MCP server factory now wires a lazy semantic-layer compute port that
defers the runtime install to the first call, mirroring the already-lazy
SQL-analysis port; the server boots and serves non-Python tools without
the runtime.
- ktx no longer requires uv on PATH: it downloads its own pinned,
sha256-verified uv build under the runtime root (KTX_RUNTIME_ROOT aware),
always musl-static on Linux. PATH uv is never consulted.
- uv is acquired before the version dir is wiped, so a failed download
cannot destroy an existing runtime.
- Acquisition failures (offline, intercepted download, unsupported
platform) throw KtxExpectedError and stay out of Error Tracking; a
missing binary inside a checksum-verified archive remains a plain Error.
- scripts/refresh-uv-manifest.mjs regenerates the pinned manifest
(packages/cli/src/managed-uv-release.ts) on uv bumps.
- Setup consent prompt now discloses the uv download; docs updated.
