[Tosd0]

Exits the next pre-release mode. After this merges, the Release workflow refreshes the "Version Packages" PR into stable versions; merging that PR publishes them to latest.

Versions

Package	Last stable	This release
@rei-standard/amsg-server	2.5.3	3.0.0
@rei-standard/amsg-client	2.8.0	2.9.0
@rei-standard/amsg-sw	2.3.2	2.4.0
@rei-standard/amsg-instant	0.10.0	0.11.0
@rei-standard/amsg-shared	0.3.0	0.4.0
@rei-standard/blob-store	–	0.1.0

Why amsg-server is a major

• POST /schedule-message and PUT /update-message reject a pushSubscription in the body (400 PUSH_SUBSCRIPTION_NOT_ACCEPTED). The subscription is registered once per user with PUT /push-subscription. Under 2.5.3 the field was required, so existing callers break.
• The root exports deriveUserEncryptionKey / decryptPayload / encryptForStorage / decryptFromStorage are now async.

Upgrade steps are in .changeset/amsg-server-3-0-major.md, which becomes the first 3.0.0 entry in the server CHANGELOG, and in the server README's "从 2.x 升级" section.

Docs

• Root README: stable install command, no @next.
• Package READMEs, standards/, and docs/ checked against the code: exports, endpoints, error codes, version annotations, and the user-level push subscription flow.

Verification

• npm run ci: all packages pass.
• changeset version dry run gives the versions above. All pending changesets are consumed and pre.json is removed.
• Not exercised against live Postgres / Neon.