Trussium CLI

The installed trussium command operates the core runtime. It does not manage Kubernetes resources or the separate Trussium operator.

Use trussium --help to inspect the command surface. The global --version option and the version command both print the installed runtime version.

trussium serve
trussium config validate
trussium health --url http://127.0.0.1:9000
trussium capabilities --url http://127.0.0.1:9000
trussium diagnostics --url http://127.0.0.1:9000
trussium diagnostics --url http://127.0.0.1:9000 --provider openai
trussium diagnostics --url http://127.0.0.1:9000 --format text
trussium version

serve uses the existing runtime settings and server lifecycle. config validate exits with code 2 for invalid settings. health checks /health/ready and exits with code 1 when the runtime is unavailable. version prints the installed package version. capabilities prints the runtime's public capability metadata as stable, sorted JSON and exits with code 1 when the runtime is unavailable or returns invalid JSON. These commands are read-only; the CLI does not install or manage the runtime, Helm chart, or operator.

diagnostics collects bounded readiness, component health, provider health, and capability availability reports. It prints one stable JSON object and exits with code 1 if any report cannot be retrieved. It does not expose credentials or provider payloads. Use --provider NAME to limit the provider section to a single registered provider; all other health sections remain unchanged. Use --format text for a concise human-readable status summary. Provider details include only validated provider names, known health statuses, and stable reason codes; unknown statuses become unknown, unknown reason codes become health_check_failed, and invalid provider names are omitted. This prevents untrusted provider health strings from leaking endpoints, credentials, or arbitrary exception text into terminal output. JSON remains the default for scripts and applies the same provider-field allowlist, dropping extra provider fields and replacing unknown reason codes with health_check_failed. Component and capability details remain bounded by their runtime health contracts.

For Kubernetes and Helm operations, use the separate public trussiumctl binary. Its initial release establishes the command boundary; install, upgrade, rollback, and cluster-diagnostics commands are planned there. The runtime CLI and trussiumctl intentionally remain independently versioned.