internal/

Package backend selects between the two ways mcp-server can talk to a Tiny Systems cluster: directly via kubeconfig, or indirectly through the hosted platform-api with a developer token.

Package catalog resolves a module NAME to the coordinates `tiny` needs to install it, using the public, unauthenticated Tiny Systems catalog at api.tinysystems.io.

Package kube wires up the Kubernetes client used by all adapters.

Package mcp implements a minimal Model Context Protocol server.

Package prompt holds the public-MCP-specific appendix that is appended to the SDK's core prompt when get_instructions is called.

Package provision installs the Tiny Systems runtime and capability modules onto a cluster by embedding the Helm Go SDK (via mittwald's go-helm-client) — no shelling out to a `helm` binary, no hosted platform.