Release and environment policy: alpha, beta, and production

[lwnmengjing]

mss-boot-io uses separate environments so development, public beta, and production releases do not get mixed.

Current policy:

• alpha/dev: used for active development and local frontend integration.
• beta: public-facing preview environment. It should only expose functionality that has passed smoke testing.
• production: tag-based releases only, with stronger compatibility expectations.

Frontend publishing is intentionally more conservative because public Cloudflare deployments should represent a tested version. Backend beta can move faster, but public beta should remain coherent for users.

Community feedback is welcome on:

• release notes clarity
• environment naming
• upgrade notes
• rollback expectations
• compatibility matrix between backend, admin backend, frontend, and docs

We will keep improving this policy as the project moves toward stronger release traceability.