changeset

# Create a Changeset Generate a properly formatted changeset file in `.changeset/` describing the work on the current branch / PR. Follow the project's changeset conventions in `.cursor/rules/090-changesets.mdc`. ## Instructions ### 1. Gather Context Determine what changed on the current branch versus the default branch: ```bash echo "=== BRANCH ===" && git rev-parse --abbrev-ref HEAD && echo "=== CHANGED FILES ===" && git diff --name-only origin/main...HEAD && echo "=== DIFF SUMMARY ===" && git diff --stat origin/main...HEAD ``` If `origin/main` is not available, fall back to staged + unstaged changes (`git status` and `git diff`). ### 2. Decide If A Changeset Is Needed Create one for: new features, bug fixes, breaking changes, performance improvements, security fixes. Skip for: refactors with no user impact, formatting, docs-only, tests-only, internal tooling, dev dependency bumps. If a changeset is not needed, tell the user and stop. ### 3. Determine Affected Packages Map changed file paths to package names from `package.json` files. Common mappings: | Path | Package name | | ---------------------- | --------------------------- | | `packages/core/**` | `@transcripts-mcp/core` | | `packages/adapters/**` | `@transcripts-mcp/adapters` | | `packages/search/**` | `@transcripts-mcp/search` | | `apps/mcp/**` | `@transcripts-mcp/mcp` | | `packages/<name>/**` | `@transcripts-mcp/<name>` | Only include pack...