✦
English
РусскийEnglish
☰
Get answerStartFirst entranceGet answerAnswer gateMy dayDaily hallHallsOmenHall chambersAppAdd to home screenOraclesOracle voicesGuideScriptoriumSearchNavigation lanternPricingScroll shopAccountSeeker quarters
Sign inRegister

Final watch

Final Launch QA

One pre-launch verification for OmenHall: environment, payments, email, Supabase, legal, mobile, SEO, support, and rollback.

Only launch a site whose pages and payment consequences have both been checked.

Environment lockDo not launch if

Gather evidence

Do not mark a critical item ready from memory. Each one needs fresh evidence: screenshot, log, test receipt, deployment URL, or launch diary entry.

  • Deployment URL recorded.
  • Test payment or controlled live check recorded.
  • Support recovery path checked.

Check real integration points

Stripe, Supabase, Resend, analytics, and AI gating must be checked as a chain, not as separate pretty bulbs.

  • Webhook updates payment status.
  • Result is created only after payment.
  • Email delivers access and recovery.

Make the go / no-go decision

If any red flag touches payment, privacy, email delivery, or result access, launch moves later.

  • No critical blockers.
  • Rollback exists.
  • Support is ready on launch day.

checklist

What to check

  • Production env uses fresh keys, and old keys are no longer used.
  • Stripe live/test modes are not mixed.
  • Supabase RLS and deletion path are checked.
  • Resend sender verified and emails do not obviously land in spam.
  • Public SEO pages index, internal sections noindex.
  • Mobile path passes without horizontal scroll or CTA overlap.
  • Legal, refund, disclaimer, and entertainment disclosure are available before payment.

red flags

When to stop

  • Checkout works, but webhook does not update status.
  • Email does not arrive or arrives from an unverified sender.
  • AI output can be generated before payment.
  • A public page exposes internal admin/support/real-data content.
  • Support cannot recover access by email/payment reference.

done when

Definition of done

  • One full path from question to result and email passed in a production-like environment.
  • All critical checks have a date and evidence.
  • A written go / no-go decision exists.

related doors

Environment lockWhich variables must be set, which are forbidden, and what to rotate before live.Live payment drillThe minimal live/test Stripe drill: checkout, webhook, receipt, refund, and recovery.Delivery drillResend, result email, recovery email, sender reputation, and fallback support path.Data and privacy drillSupabase, RLS, storage, deletion, support access, and no-secret output.Do not launch ifA hard stop-signal list before ads and real users.