RELEASES

What changed for users

Read release notes when you want the practical summary: what changed, why it matters, and whether your team should update anything.

Read This When You Want To Know

• what improved for day-to-day users
• whether a release changes the default path or support expectations
• what to update in your repo, workflow, or install guidance

v1.0.6

Shared runtime-package delivery became a clearer public option, and the release clarified how to replace the main generated entrypoint safely.

v1.0.5

Compatibility policy, support wording, and generated docs became easier to read and safer to standardize.

v1.0.4

Newcomer setup became simpler by removing avoidable first-time setup friction and tightening the first-time workflow.

v1.0.0

The project declared its first stable public contract and shipped the baseline the later releases keep refining.