Add changeset requirement to package guidelines

[jln13x]

Document that package changes require a changeset generated via pnpm changeset with patch version.

This ensures all package modifications have corresponding version bump records.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
jlnstack	Ready	Preview, Comment	Jan 24, 2026 9:25am

[greptile-apps]

Greptile Overview

Greptile Summary

Added a new "Changesets" section under Package Guidelines documenting the requirement for package changes to include a changeset. The addition specifies running pnpm changeset, selecting affected packages, and choosing patch version.

• Simple documentation addition that aligns with the repository's existing changeset workflow (confirmed by .changeset/config.json and package.json scripts)
• Well-placed within the Package Guidelines section after type and export guidance
• Clear and concise instructions for contributors

Confidence Score: 5/5

• This PR is completely safe to merge with no risk
• This is a documentation-only change that adds a clear guideline about changesets. The instruction is accurate (verified against the repository's changeset configuration), well-formatted, and appropriately placed in the document structure. No code changes, no potential bugs, and follows the existing documentation style.
• No files require special attention