Developer's deploy scripts passed all checks while shipping broken code for weeks

A software developer discovered that their deployment pipeline consistently reported success while silently failing to apply critical code changes in production. A Celery Beat scheduler container was excluded from the deploy script, meaning it ran two-week-old code through multiple deployments without any alert. A separate incident saw an annual billing feature ship dead because new environment variables were added after containers had already started. All automated checks passed in both cases because they verified general server state and uptime, not whether the intended changes had actually taken effect. The developer notes the core problem is a gap between checks that confirm system health and checks that confirm deployment intent.