Onboarding Entry Gate + Deploy Readiness + Regression Tests

Shipped

• Added Onboarding Entry Gate to route users based on auth state + local data presence
• Enhanced onboarding handling for different entry sources (including marketing campaigns)
• Improved identity handling and created a utility to resolve onboarding requirements from identity/session state
• Added regression + unit tests:
  • Account prompt triggers in saved routines (first routine + preset forking)
  • Entry gate scenarios to ensure stable onboarding behavior
• Deployment/readiness improvements:
  • Deployment scripts for marketing + training with Vercel target checks
  • Vercel config verification checks
  • Readiness tests now dynamically seed demo routines into local storage for consistent test conditions
• Additional hardening:
  • Safer local storage serialization in seed application
  • Improved routine snapshot parsing error handling
  • Playwright config tuned to ignore debug-only tests

Why

• Entry gating prevents inconsistent onboarding across auth/local-first states
• Seeded readiness tests reduce “it worked on my machine” failures before launches
• Regression coverage protects the post-value account prompt strategy from drifting

Next

• Expand e2e coverage around “new user → first workout → prompt → account creation”
• Add a thin “diagnostics” surface for QA (seed status, route state, gating decisions)