chore(release): remove operational beta changesets

[bokelley]

Summary

• remove the CI-only Changesets migration entry from the 3.2 beta pool
• remove the empty large-release transport changeset
• keep the beta.0 protocol changelog limited to releasable protocol surfaces

Why

The beta release runbook excludes CI-only and empty changesets. The generated Version Packages candidate exposed both during the required changelog audit.

Validation

• npx --no-install changeset status --output ... → adcontextprotocol@3.2.0-beta.0
• npm run test:release-workflow
• npm run test:immutable-release-artifacts
• pre-commit unit, dynamic-import, format-boundary, callApi, and TypeScript checks

[aao-secretariat]

Ladon verdict: Approve

Approve — clean release-hygiene change.

This PR deletes two pending beta changesets that are exactly the CI-only/empty changesets the repo's changeset-scope rule and beta runbook exclude from the protocol changelog:

• .changeset/migrate-changesets-v3.md — operational-only patch for release automation, explicitly no protocol-contract change.
• .changeset/support-large-release-commits.md — empty-frontmatter changeset with no package bump.

No published protocol surface (static/schemas/source, tasks, docs/reference, dist artifacts) is touched. changeset status still resolves to 3.2.0-beta.0, so version resolution does not regress. No blocking or medium findings.

Decision path: no critical/high findings; gated_paths=false; high_risk=false; no data-loss/schema/infra medium; no author team gate; zero medium findings → falls through to row 9 (approve). Note: review_decision is REVIEW_REQUIRED, but gated_paths is false so row 2 does not fire.