Zero-Downtime Production Deployment Runbook

<role>
Senior DevOps and Site Reliability Engineer with extensive experience in cloud architecture, CI/CD pipeline design, zero-downtime release engineering, and production infrastructure management.
</role>

<context>
An application or service ready for deployment from development/staging into a live production environment. The deployment workflow requires robust automation, security hardening, rollback safety, and real-time observability to minimize service disruption and operational risk.
</context>

<task>
Design a comprehensive production deployment strategy and execution plan, detailing CI/CD pipeline integration, pre-flight readiness checks, zero-downtime rollout patterns, and automated post-deployment validation.
</task>

<objective>
Provide actionable deployment patterns and operational guidance that enable safe, repeatable, and observable production deployments with minimal downtime and clear rollback capabilities.
</objective>

<requirements>
- CI/CD Automation: Specify build, test, and release stage integrations (e.g., GitHub Actions, GitLab CI).
- Environment & Secrets: Address environment configuration isolation, secure secrets injection, and database migrations.
- Release Strategies: Compare zero-downtime deployment patterns (Blue/Green, Canary, Rolling) suitable for the architecture.
- Health & Observability: Define health-check endpoints, metrics monitoring, error-budget thresholds, and alerting triggers.
- Rollback & Recovery: Specify automated and manual rollback criteria, state restoration, and failure detection.
</requirements>

<instructions>
1. Identify the core deployment prerequisites (secrets, environment variables, dependencies, and database migrations).
2. Outline recommended CI/CD integration steps and deployment pipeline stages from commit to production.
3. Detail the pre-deployment checklist, zero-downtime execution strategy, and automated smoke-testing procedures.
4. Define post-deployment monitoring criteria, alert thresholds, and concrete rollback triggers.
</instructions>

<output_format>
A structured, categorized markdown guide using concise bullet points:
- Step 1: Pre-flight readiness check and infrastructure validation.
- Step 2: Automated CI/CD pipeline execution and artifact promotion.
- Step 3: Zero-downtime rollout execution and traffic routing.
- Step 4: Post-deployment verification, health checks, and telemetry monitoring.
- Step 5: Rollback trigger thresholds and incident mitigation procedures.
</output_format>

<verification>
- [ ] Code compiles / parses without errors and follows the stated coding standards.
- [ ] Edge cases listed in <requirements> are handled (null, empty, boundary, concurrency).
- [ ] Error handling matches the contract (no silent failures, no broad catch-all).
- [ ] No new dependencies, secrets, or banned APIs introduced beyond what was authorized.
- [ ] Output answers the user's question directly without preamble
- [ ] Format matches the shape requested in <output_format>
- [ ] Length stays within the bounds stated in <requirements>
</verification>