Docs and changeset base branch guidance are inconsistent

[matthewcorven]

Summary

CONTRIBUTING.md tells contributors from forks to target dev, but .changeset/config.json still declares main as the base branch.

Why this matters

This creates conflicting contributor guidance:

• PR workflow says to branch from and target dev
• Changesets are configured against main

That mismatch makes it unclear which branch is authoritative for docs-only and package-impacting changes, and it increases the chance of malformed PRs or confusing changeset behavior.

Current references

• CONTRIBUTING.md: PRs from forks must target dev
• .changeset/config.json: "baseBranch": "main"

Suggested resolution

Pick one canonical contribution base branch and align:

• CONTRIBUTING.md
• .changeset/config.json
• any CI or release docs that describe the PR flow