shipping-and-launch

Release readiness validation requires enforcing preflight checks for lint, type-check, tests, and builds before code moves to a shared branch or production target, ensuring shipping acts as a quality gate rather than an afterthought.

Preflight checks for deploying a feature branch include running lint, type-check, tests, and build validations. You must also confirm documentation updates and perform a secret cleanup to ensure safe releases without leftover credentials.

Creating a rollback plan for production deployment involves assessing risks and reporting explicit blockers during the release gate validation, ensuring any failed deployment can be safely reverted after shipping code changes.

This release gate workflow applies to local development environments, feature branches, and PR release gates, guiding lint, type-check, tests, documentation updates, and risk assessment across all these development contexts.

Documentation and memory notes should be updated during the shipping process when behavior changes are detected, ensuring project docs remain accurate before code moves to a shared branch or production target.