fix(dashboard): Improve verify-email UX: auth shell layout and clearer modal

[motunrayokoyejo]

• Put /verify-email on the shared auth shell to match login/signup.
• Tighten the in-app verify-email modal copy and close it after a successful resend so it doesn’t stay stuck.

---

Note

Medium Risk
Touches auth-related guest routes and resend targeting by verification token, which could mis-route resends if token handling is wrong; UI and config preload changes are lower risk.

Overview
Improves the verify-email flow end-to-end: public page matches login/signup via auth shell, and users can resend from the link page or the in-app modal without getting stuck after success or refresh.

Backend: POST /users/resend_verification_email is a guest route with optional auth. The handler prefers ?token= so resends target the user on the verification link (not whoever is signed in). getUser uses a safe context read so guest routes don’t panic. Cooldown errors now say to wait 1 minute.

Frontend: /verify-email is registered at the app root (not under legacy public chrome). After verify, the URL token is cleared and a sessionStorage flag preserves success on refresh; failed verify can resend with the token query param. The dashboard modal closes after a successful resend and keeps tighter copy. ConfigService dedupes the default auth config fetch and falls back to defaults on failure (with hideNotification on preload).

^{Reviewed by Cursor Bugbot for commit ba4708a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mekilis]

Looks good otherwise. One ask on the failed-state button.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ba4708a. Configure here.}