Production readiness review

Most production failures come from assumptions nobody checked. Start by turning assumptions into facts.

1. Ask about the target

Ask in one round, with recommended options first. Skip what the repo already answers.

Question	Why it matters
Where does it run (VPS, container, PaaS, serverless)? Is the disk persistent across deploys?	Data loss when state is stored on local disk
Is there a reverse proxy or load balancer? Which address does the app see?	Client IP for rate limits, trusted proxy settings
Is HTTPS terminated before the app?	Secure cookies, HSTS
How many instances?	In-memory state, stores that allow one writer, shared secrets
How are secrets and environment variables set?	Missing or weak secrets, the production mode of the runtime or framework
Where do logs go? Is there alerting?	Silent failures
How is it deployed and rolled back? Is there CI?	Broken builds, untested merges