Read this before migrating core Beta Access

The supplied beta.2 is a development preview, not approval to remove core Beta Access. Its handoff keeps core_removal_ready=false. A newer core maintainer must not delete the old feature merely because this manual exists.

Safe transition order

1. Back up the database and uploaded files, and record the existing beta category, tester group, approved/pending applications and category grants.
2. Install the same-key addon in staging with the supported core/licensing/schema flow.
3. Check that it adopts the existing category, group and tester memberships instead of creating parallel identities.
4. Test the application lifecycle and reader/tester restrictions with real separate accounts.
5. Compare counts, status and ACLs after retry, failed transaction and upgrade; obtain the product migration acceptance evidence.
6. Remove core ownership only in a later coordinated release after the explicit removal gate is satisfied.

The addon is a generic early-access program, not a promise to gate arbitrary purchases, external services or multiple independent programs. Its provided defaults should be reviewed for your own community. This docs release changes no core feature or migration readiness flag.