Improve changeset creation

[isaacroldan]

Why

Changesets are public changelog entries, but they can be added for repo-only work that is not actually user-facing or ready to announce. That creates noisy release notes and makes automated agents more likely to add unnecessary changesets.

What

• Add a pnpm changeset wrapper that asks for confirmation before running changeset add.
• Fail closed for non-interactive changeset add runs so automated agents cannot silently create public changelog entries.
• Delegate non-add Changesets commands, including release/versioning commands, to the upstream Changesets CLI.
• Document when contributors and agents should add changesets in CONTRIBUTING.md, AGENTS.md, and tool-specific agent instruction files.
• Tell agents to keep changeset summaries short, with a one-line maximum.

Testing

• node --check bin/changeset.js
• pnpm exec eslint bin/changeset.js
• pnpm exec prettier --check bin/changeset.js package.json CONTRIBUTING.md AGENTS.md .claude/CLAUDE.md
• pnpm exec prettier --check AGENTS.md
• pnpm changeset --version
• pnpm changeset add non-interactive refusal
• pnpm changeset add TTY prompt with n
• pnpm changeset --message "test" refusal

No changeset: this changes repo contributor tooling and agent guidance, not public Shopify CLI behavior.

[isaacroldan]

• Improve changeset creation #7904 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.