FE-1050: Automate npm alpha publishing

[kostandinang]

Summary

• format all files produced by the custom Changesets version command before the action commits its release PR
• lock the version-command ordering with a release workflow contract test
• record explicit non-release intent for this workflow-only correction

Test plan

• npm test -- scripts/release-workflow.contract.test.mjs
• isolated npm run version-packages followed by npm run fmt:check
• git diff --check

Context

PR #350 exposed the gap: changeset version rewrote .changeset/pre.json in Changesets' valid JSON style, but the repository's oxfmt policy expects a different canonical layout. The Changesets action supports custom version scripts and includes all modifications they make, so formatting in version-packages fixes generation rather than patching each release PR.

[kostandinang]

• FE-1050: Automate npm alpha publishing #351 👈 (View in Graphite)
• next

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

[cursor]

PR Summary

Low Risk
Release automation script ordering only; no runtime, auth, or publish logic changes.

Overview
Fixes release PR noise from Changesets rewriting files (e.g. .changeset/pre.json) in a layout that fails oxfmt --check, as seen after PR #350.

The version-packages script is now changeset version && npm run fmt, so anything the custom version step touches is canonicalized before the Changesets action (version: npm run version-packages in release workflow) commits the release PR.

A release workflow contract test locks that script string, and an empty changeset documents that this change is workflow-only (no package version bump).

^{Reviewed by Cursor Bugbot for commit d200771. Bugbot is set up for automated code reviews on this repo. Configure here.}