Website launch gate

Treat launch readiness as a verification job, not a request to repeat a checklist.

Workflow

Identify the repository, the build and test commands, and any preview or deployed URL supplied by the user. Do not deploy, publish, alter production data, or create third-party accounts unless the user authorized it.
Run the existing checks and inspect both the source and the rendered website where possible. A claim passes only when supported by a command result, source location, HTTP response, or rendered-page observation.
Check every item below. Mark an item N/A only when the site genuinely does not need it, and state why. Mark anything unverified as UNKNOWN, not PASS.
Fix in-scope failures when the user asked for implementation. Re-run the relevant check after each fix. If the user asked only for an audit, do not change files.
Report the launch decision first, followed by failures and evidence. Do not bury a security, legal, form, or mobile blocker inside a numerical average.