Release governance

Version the website
without versioning the store by accident.

Website overlay v9.0.0 is an independent delivery artifact. Release metadata must never imply that a commerce application, database or provider adapter is on the same version.

Keep release streams independent

Website overlay, commerce application, database schema and provider contracts can change on different schedules. Compatibility should be asserted only when an implementation has evidence for it.

Publish required website gates

The release-policy model defines package-only controls: generated metadata, checksum verification, route ownership, rollback, baseline and post-deploy proof.

Archive a DeployPro report

bin/thonem-cloudpanel report /tmp/thonem-release.json

Keep history explicit

The public changelog records website changes. Application migration history should remain in the application repository and release process.