Authoring a changeset

This repo releases with Changesets: every PR that changes a publishable package carries a small .changeset/*.md file declaring which packages bump and by how much. changeset version later consumes those files into per-package CHANGELOG.mds and version bumps. No changeset → no release for that change; changeset-bot comments a reminder on the PR (a nudge, not a hard block — the maintainer-reviewed Version PR is the real gate). Your job here is to write a correct changeset for the work in progress.

Steps

See what changed. Fetch and diff against the base branch:
```
git fetch origin main
git diff --name-only origin/main...HEAD
```
(Use the working tree too if changes aren't committed yet: git status.)