deploy-verify

# Post-Deploy Verification Automated post-deploy health check across all services. Run after every deploy to catch regressions before users do. Works with **any project** — auto-detects configuration. ## Critical Rules > **Run within 15 minutes of deploy.** The sooner you check, the smaller the blast radius. > **Parallel where possible.** Sentry, Supabase, and Langfuse checks are independent — run them in parallel to save time. > **The verdict must be binary.** SHIP, ROLLBACK, or MONITOR (with clear criteria for when MONITOR escalates to ROLLBACK). > **Evidence over opinion.** Every check produces a PASS/FAIL with specific data. Never say "looks fine." > **Always use the `browser-anti-stall` protocol** when using Playwright browser MCP tools. --- ## Phase 0: Auto-Detect Deployment Context ### 0a. Detect Deployment Platform ``` Grep(pattern: "vercel\\.json|netlify\\.toml|fly\\.toml|render\\.yaml|railway\\.json|Dockerfile|docker-compose|appspec\\.yml", output_mode: "files_with_matches") Grep(pattern: "VERCEL_URL|RENDER_EXTERNAL_URL|FLY_APP_NAME|RAILWAY_STATIC_URL", glob: ".env*") ``` ### 0b. Find Production URL ``` Grep(pattern: "NEXT_PUBLIC_APP_URL|NEXT_PUBLIC_BASE_URL|VITE_APP_URL|PUBLIC_URL|PRODUCTION_URL|APP_URL", glob: ".env*") Grep(pattern: "https://.*\\.vercel\\.app|https://.*\\.netlify\\.app|https://.*\\.fly\\.dev|https://.*\\.railway\\.app", glob: ".env*") ``` Also check framework config files: ``` Grep(pattern: "url|domain|hostname", glob: "{vercel.json...