changesets-releaselisted

# Changesets Release Use this for consumer-installed packages. Do not require Changesets for a single deployed application unless its owner chooses release versions. ## Decide Scope - Use it for libraries, SDKs, CLIs, plugins, and packages published independently. - In a monorepo, include every changed consumer package; let Changesets calculate internal dependency bumps. - For internal-only work, use the repository's explicit `no-changeset` convention. Do not add an empty changeset merely to satisfy CI. - Before first adoption, confirm the owner wants Changesets, then initialize it with the repository's package manager. Do not introduce a release dependency unilaterally. ## Add Release Intent 1. Read `.changeset/config.json`, package metadata, and the consumer contract before choosing a bump. 2. Use `patch` for compatible fixes, `minor` for compatible capabilities, and `major` for breaking behavior, removed APIs, or required consumer changes. 3. Run the configured `changeset` command and commit its generated `.changeset/<name>.md` with the implementation PR. 4. Write the entry for consumers: what changed, why it matters, and migration steps when needed. Never copy a commit subject as the release note. ## CI And Version PR - Require a changeset or an approved `no-changeset` marker on releaseable PRs; `changeset status` is the non-interactive CI check. - Use the Changesets GitHub Action to create/update a version-packages PR. Review generated versions and changelogs befo