smoke-prod-evidence

What problem does it solve?

Prevents premature claims like “it’s working” by requiring unambiguous production evidence using curl -sv status codes and redirect hops, especially after deploys and runtime-critical edits.

Core Features & Use Cases

• Production-first verification: Checks that redirect, middleware, routing, cache/assets, and web-server behavior work in the real prod environment (not just local smoke).
• Evidence-grade curl output: Enforces literal hop-by-hop status codes and locations (e.g., 301/302/200) rather than relying on redirect counts or “final URL” outcomes.
• Regression-adjacent testing: Validates that changes to one path do not break similar neighboring routes or login/auth flows.
• Honest failure messaging: Produces compliant, non-overconfident responses when evidence is missing, including a clear “prod not verified yet” stance.

Quick Start

Ask to verify the fix by running the prod smoke protocol with curl -sv for the relevant paths you changed, including one negative case and one adjacent regression case, and return the collected status-code hop evidence.