Organize Codebase & Stabilize Auth

My current e-commerce repository has grown into a single, bloated root folder. I need it broken out into clean, permanent directories—/home, /market, /orders, /purchase, /wallet and /profile—while preserving every existing route exactly as it works today. That means updating the router, adding any necessary aliases or redirects, and proving with a quick regression pass that nothing 404s.

At the same time, the Supabase authentication flow needs to be bullet-proof. Sign-up, log-in, email verification, Termii SMS verification, forgot-password and password-reset are already wired up, but delivery is hit-or-miss. Both email and SMS must succeed before an account is activated, and all messages have to originate from our own sender domain / Termii sender ID rather than the Supabase default.

Deliverables
• Repository refactored into the six folders above, committed with clear paths and a short README describing the structure.
• Routing or server configuration updated so every legacy URL continues to resolve.
• Supabase configured for reliable dual-channel verification: custom SMTP + Termii keys in place, resend logic and logs showing successful delivery.
• Acceptance test script (manual or automated) demonstrating that a fresh user can register, receive both confirmations, complete activation, log in, and perform a password reset without failures.

If this sounds straightforward to you, let’s get the repo cleaned up and the auth rock-solid.