Staging Deployment Readiness

Sprint 23 prepared Submicron Central System to leave localhost safely. Sprint 24 uses the documented Docker-host/VPS staging assumption for https://staging-app.submicrons.net until a managed platform is explicitly selected. It does not deploy production, commit secrets, use real customer data, or connect external integrations.

Staging readiness means the app can be built, configured, checked, migrated, backed up, smoke tested, and reviewed with demo/sample data only. External Email, WhatsApp, SMS, Google Drive sync, WooCommerce, social, payment gateway, and autonomous AI behavior remain disabled.

Required Order

1. Prepare an untracked staging environment file or platform secret store from .env.staging.example.
2. Run pnpm env:check:staging against the template and run node scripts/env-check.mjs staging --file=.env.staging against the real staging values before launch.
3. Run pnpm db:generate, migration status, backup, migration deploy, migration status again, seed only when approved, and smoke checks.
4. Check /api/health and /api/ready.
5. Run a demo-user login check and verify docs.

Sprint 24 Documents

• Actual staging deployment and QA
• Sprint 24 manual test runbook
• Staging smoke QA
• Manager staging rehearsal guide
• External integrations disabled checklist

Safety Boundaries

• No production deployment is performed by this repository.
• No production secrets are committed.
• No destructive reset, truncate, or automatic rollback is added.
• No external messages are sent.
• No live Google Drive, Gmail, WhatsApp, WooCommerce, social, or payment integration is connected.
• No autonomous agent actions are enabled.

Use sample/demo data until production data migration is explicitly approved.