All feedback from my earlier review rounds has been addressed in bf0a68d and d954357 — versions reset to a uniform 2.0.0-beta.0, published READMEs/codemod instructions now point at @beta, and the remaining forward-looking alpha prose is corrected — so this looks good to me.

Overview

This PR switches the changesets prerelease tag from alpha to beta (.changeset/pre.json), resets every workspace package.json from 2.0.0-alpha.* to 2.0.0-beta.0, adds one changeset so the regenerated Version Packages PR has content, and sweeps published instructions (package READMEs, codemod README, migration guides) from @alpha install/codemod commands and alpha-release banners to beta wording. No runtime or library code is touched — the diff is version strings, JSON release metadata, and documentation prose.

Security risks

None. There is no executable code change; the only operational effect is on the release pipeline (the next publish goes out under the npm beta dist-tag). Publishing itself still requires merging the separate Version Packages PR and approving the release environment, so there is a human gate downstream of this merge.

Level of scrutiny

Moderate. Release-mechanics changes can have non-obvious consequences in changesets internals (my earlier review rounds flagged exactly that: the prerelease counter is derived from package.json, and the published READMEs ship in the tarballs). Both rounds of feedback — the two blocking issues (stale @alpha install instructions in published READMEs/migration docs; the counter not resetting, which would have produced beta.5/beta.3 instead of a uniform first beta) and the three follow-up nits (remaining "until the next published alpha" passages in upgrade-to-v2.md, the over-broad alpha-typings claim in support-2026-07-28.md, and the missed examples/package.json) — are addressed by commits bf0a68d and d954357. With all package versions at 2.0.0-beta.0, the next changeset version run produces a uniform 2.0.0-beta.1, matching the PR description.

Other factors

The bug hunting system found no issues on the latest revision. The decision to enter beta is itself a maintainer-level release decision that the PR title embodies; the mechanics of executing it are now consistent and mechanical. The consumed-changeset history in pre.json is preserved, so the prior alpha changesets will not re-apply.