Workspace crate taxonomy

Workspace members live under crates/ and are grouped by role:

Directory	Crates
crates/core/	xlai-core
crates/runtime/	xlai-runtime
crates/backends/	xlai-backend-openai, xlai-backend-openrouter, xlai-backend-transformersjs, xlai-backend-gemini, xlai-backend-llama-cpp
crates/qts/	xlai-qts-core, xlai-qts-manifest, xlai-qts-cli
crates/sys/	xlai-build-native, xlai-sys-llama, xlai-sys-ggml
crates/platform/	xlai-facade, xlai-native, xlai-wasm, xlai-ffi

This doc classifies crates for dependency and release decisions. Authoritative publish order for crates.io is in Publishing and .github/workflows/publish.yml.

Published to crates.io

Crate	Role
xlai-core	Domain types and provider traits
xlai-runtime	RuntimeBuilder, Chat, Agent, sessions
xlai-backend-openai	OpenAI-compatible HTTP backend
xlai-backend-openrouter	OpenRouter Responses API chat backend
xlai-backend-transformersjs	WASM transformers.js chat backend

Internal only (publish = false)

Crate	Role
xlai-build-native	Internal build-script helpers (CMake, OpenBLAS, Vulkan, llama.cpp patches)
xlai-sys-llama	Vendored llama.cpp build (CMake + bindgen); sources under vendor/native/
xlai-sys-ggml	Vendored standalone ggml build for QTS (CMake + bindgen)
xlai-backend-llama-cpp	Native llama.cpp chat backend
xlai-backend-gemini	Google Gemini HTTP backend (publish = false; not in the crates.io publish chain)
xlai-facade	Internal integration re-exports for xlai-native only (xlai-wasm does not depend on it)
xlai-native	Native app entrypoint
xlai-wasm	wasm-bindgen + npm package base
xlai-ffi	C ABI
xlai-qts-manifest	Browser QTS manifest / capability serde
xlai-qts-core	Native Qwen3 TTS engine + QtsTtsModel
xlai-qts-cli	xlai-qts binary

CI setup

Native Rust jobs share .github/actions/setup-xlai-rust-native (toolchain, sccache, rust-cache, OpenBLAS / vcpkg / shaderc). Jobs that need Vulkan (release build.yml) add Linux glslc / libvulkan-dev and the Vulkan SDK step after that action.

Adding a new workspace member

1. Add the path to [workspace].members in the root Cargo.toml.
2. If the crate should ship to crates.io: set publish = true (default), add a description, wire version.workspace = true, add to [workspace.dependencies] with path + version, and append it to PUBLISH_CRATES_ORDER in publish.yml in dependency order.
3. If internal: set publish = false and list it here and in Publishing under "not published".