REFERENCE

Stable Facts

Reference pages keep the public rules discoverable: install options, support matrices, and the exact behavior you can rely on.

Use This Section When

you need the exact contract, not a tutorial
you are checking what is stable versus beta
you want the shortest answer about install channels, support, validation, or repository shape

Understand Homebrew, npm, PyPI, and the verified script without confusing install paths with runtime APIs.

Keep release baselines, stable-versus-beta promises, wrappers, and SDK/runtime expectations in one place.

See the canonical `init -> generate -> validate --strict -> test -> handoff` flow.

See what a healthy plugin repo should look like and which files are source of truth versus generated outputs.

See what is stable, what is beta, and what you should not treat as a long-term contract.

See which targets are runtime-ready, package-only, or intentionally outside the main stable runtime path.

Answer the common questions about wrappers, runtime choice, and strict validation.

Unblock the most common install, runtime, generate, and validation failures.

Normalize the core terms so target, source of truth, wrapper, and handoff mean one thing across the docs.