ktx/examples/package-artifacts
Andrey Avtomonov a0d3ddbbc2 chore: standardize daemon naming on "KTX daemon"
Replace inconsistent names ("KTX Python daemon", "KTX local embeddings
daemon", "KTX managed daemon", "Python daemon") with the single name
"KTX daemon" in CLI output, errors, command descriptions, test
assertions, smoke scripts, docs, AGENTS.md, issue templates, and
codecov flags. The daemon is a portable compute server with endpoints
for SQL analysis, semantic layer, LookML, database introspection, and
embeddings; the previous labels misrepresented it as embeddings-only or
exposed implementation details ("Python", "managed").

The "KTX Python runtime" concept (installed interpreter + packages) is
deliberately left as-is — it is a separate concept from the daemon
process.
2026-05-20 11:10:27 +02:00
..
README.md chore: standardize daemon naming on "KTX daemon" 2026-05-20 11:10:27 +02:00

Package artifact smoke checks

The package artifact smoke checks create temporary projects instead of storing sample projects in this directory. Run the checks from ktx/:

pnpm run artifacts:check

The npm smoke project installs the generated public @kaelio/ktx tarball, imports the package entry point, and runs installed ktx commands against a generated local project.

The managed Python runtime smoke requires uv on PATH, isolates KTX_RUNTIME_ROOT, verifies ktx admin runtime status, runs ktx sl query --yes to install the core runtime from the bundled wheel, checks ktx admin runtime status, starts and reuses the KTX daemon, and stops it.

The artifact manifest contains the public @kaelio/ktx npm tarball and the bundled kaelio-ktx runtime wheel. The smoke does not install standalone Python packages directly; Python-backed behavior is verified through the managed runtime installed from the npm package.