Operator checklist

Deploy with evidence.

A passing build proves compilation. The checks below establish whether a specific deployment can safely accept an external purchase. This page contains no private environment values and does not certify production readiness.

Current acceptance still needs the public sandbox purchase/return, durable receiver and observed scheduled delivery. Email is deferred. Local database, protocol and browser fixtures do not close those gates.
  1. 1

    Isolated resources

    Separate sandbox Supabase/deployment and Paystack test key; exact resource binding and different live reference. No production customer copy.

  2. 2

    Migration rehearsal

    Apply all ordered migrations to a disposable database first. Review only pending files against the intended sandbox. Never reset or blindly replay existing remote migrations.

  3. 3

    Secrets and origins

    Dedicated versioned signing/encryption/cron material, exact APP_URL and partner origins. Keep keys server-side and out of bundles/logs. Rotate exposed values.

  4. 4

    Verified online purchase

    External site → sandbox checkout → Paystack TEST → verified session/order/admissions → partner return. Repeat free/group/cancel/expiry and response-loss retries.

  5. 5

    Tickets and delegated entry

    Claim each group member through the existing flow. Verify independent QR codes and one-time entry, refunds, revoked creator/event grants and foreign application denial.

  6. 6

    Durable notifications

    Persistent public inbox with signature verification, ID/body deduplication, secret rotation and crash recovery. Observe actual Hobby cron and manual retry; daily bounded delivery has no real-time SLA.

  7. 7

    Browser and operational review

    Mobile/desktop/keyboard, host CSS/CSP, blocked third-party cookies, Safari/physical device QR/camera, realistic throughput/backlog and support recovery.

  8. 8

    Rollout and recovery

    Start with minimum scopes/flags in sandbox. Keep live disabled until acceptance is recorded. Suspend abusive apps, monitor errors/exhausted deliveries and preserve verified receipts/history.

Useful local checks

npm test
npm run lint
npx tsc --noEmit --incremental false
VERCEL=1 NITRO_PRESET=vercel npm run build
npm run integrations:readiness

The readiness command prints check names and fixed outcomes, not secrets. A disabled feature is reported as disabled, not accepted. Operator runbooks and evidence live in the repository’s docs folder.