Deployment and acceptance
Vercel-first release checks and external acceptance.
Release guardrails
Run lint, format:check, typecheck, test and build. Typecheck prepares generated docs. GitHub Actions uses an isolated PostgreSQL service, migrates it and runs DB tests. TEST_DATABASE_URL is TRUNCATED: never production. Run DB test files serially.
Vercel buildCommand is pnpm verify:deploy: production-env validation, lint/type/unit-test/build guard; no automatic production migration. Configure branch protection and required Actions checks manually; a workflow file alone does not block merges.
Default daily cron uses CRON_SECRET Bearer. Monitor due-grant backlog and adjust cadence/limit for scale/platform plan. A health check is not payment acceptance.
Human rollout checklist
- Independent production DB/backups, review migrations 0009/0010, isolated tests.
- Matching HTTPS origins, login/logout/ban checks, Google callback and email domain.
- Waffo/Creem sandbox checkout/renewal/retries/cancel/refund/dispute/unknown-timeout recovery.
- Replace brand/demos/customer samples and complete/review legal content.
- Explicit optional GA/Clarity/Sentry, verify your own alerts, do not upload tool inputs/payment secrets.
- Confirm cron and annual grants before domain binding/traffic rollout.
Repository files or a local build do not prove hosting/merchant/monitoring acceptance.