Safe recovery
Verify access
Finish signup or email verification inside the same public auth lane before entering the app.
Checking verification
Validating the verification token and preparing the next entry route.
Verification completion proof
Verification trust chain
Verification keeps OTP validation, backend session exchange, signup handoff, recovery correction, accessibility, and static performance evidence visible in the public auth lane.
- 01OTP verification
POST /auth/v1/verify validates signup, magic link, email, and recovery tokens before protected workspace routing can begin.
Review verification state - 02Backend session exchange
POST /api/v1/auth/login completes the app session, then GET /api/v1/projects and GET /api/v1/onboarding/status decide the first safe destination.
Open login lane - 03Signup handoff
Confirmed signup verification moves to /onboarding so first-use activation starts with a verified identity.
Preview onboarding - 04Recovery correction
Recovery verification redirects to /auth/reset-password instead of silently entering the workspace with an unfinished password update.
Open recovery lane - 05Accessibility and performance
Landmarks, status announcements, keyboard links, and responsive CSS stay visible without route-owned runtime observers.
Inspect route