Support Boundary

This page answers one practical question: what can you safely promise today, and what should you describe more carefully?

Safe Defaults

• Go is the recommended production path.
• validate --strict is the main readiness check for local Python and Node runtime projects.
• The CLI install wrappers are ways to install the CLI, not runtime APIs.
• One repo can cover many supported outputs, but support depth still depends on the target.

Stable By Default

• the main public CLI contract
• the recommended Go SDK path
• the stable local Python and Node subset on supported runtime targets
• the targets explicitly marked stable in the generated support matrix

Use Carefully

• beta paths that are still evolving
• workspace-configuration and packaging targets when what you really need is executable plugin behavior
• install wrappers when what you really want is a runtime or SDK API

Out Of Scope

• treating every target as if it had the same runtime guarantees
• treating wrapper packages as SDKs or runtime contracts
• assuming experimental surfaces carry long-term compatibility promises

Pair this page with Version And Compatibility Policy, Target Support, and Stability Model.