✦
English
РусскийEnglish
☰
Enter the grand hallGet answerHallsTarot, Lenormand, runes, dreams, MoonDayQuick daily signOraclesVoices and reading schoolsLibraryCards, symbols, dreambookShopFormats, scrolls, and giftsHowMechanics, briefly
InstallSearch

Gate watch

Production checklist

The master list before letting real users, real payments, and paid traffic into OmenHall.

Launch is ready not when the site is beautiful, but when the core path does not break.

Stripe test flowMobile QA

Check build and environment

Before redeploy, local checks should pass and Vercel should hold current variables without old keys.

  • typecheck, lint, test, links, structure, route audit are green.
  • NEXT_PUBLIC_SITE_URL points to the production domain.
  • Secrets are not in ZIP, GitHub, or README.

Run one paid path

Manually run the customer path: question, card selection, seal, checkout, webhook, AI, email, account, share, and deletion.

  • AI does not run before payment.
  • Webhook changes paid status.
  • Client can recover access.

Check phones

Most users arrive on a phone. Card table, buttons, forms, payment, and account must be understandable without a mouse.

  • iPhone Safari.
  • Android Chrome.
  • Mobile zoom and reduced motion.

checklist

What to check

  • All production keys are fresh and were not exposed in chat or screenshots.
  • Supabase migrations are applied to the production database.
  • Stripe webhook points to the production endpoint and uses the current secret.
  • Resend sender works and receipt email arrives.
  • Data deletion path is clear and does not break the interface.

red flags

When to stop

  • User paid, but AI did not start.
  • Result exposes hash, job id, or internal cost.
  • On phone, card selection or overlay closing fails.
  • Emails arrive from an unverified or alarming sender.

done when

Definition of done

  • One test payment completed from question to ready scroll.
  • Client can open the result on another device through email/account.
  • Support sees enough data, while the client does not see technical machinery.

related doors

VercelEnvironment variables, redeploy, build logs, and domain.SupabaseMigrations, Auth, RLS, storage, and rate limit.Stripe test flowCheckout, webhook, paid status, AI, receipt, and access.Mobile QAiPhone Safari, Android Chrome, card table, and checkout.How it worksThe path of question, method, seal, and scroll.TrustBoundaries, honesty, and safe positioning.