usertour

This release polishes the sign-in flow and the routing layer that supports it. Auth pages now respect the user's locale, sign-in remembers the page the user was trying to reach before being bounced, and the app lands on an environment the user actually
has access to instead of the hardcoded /env/1/flows. Under the hood the auth router is rebuilt around a single state machine and @usertour/hooks's monolithic gql.ts gets its first domain split.

What's Changed

🌐 Localization on auth pages

Eight auth pages and their shared components — sign-in, sign-up, registration, invite, password reset, set-up admin, and the two 2FA screens — now go through useTranslation('ui') under a new auth.* namespace. Switching to zh-Hans flips every label,
button, placeholder, and validation message; English remains the default.

🔗 Deep-link return after sign-in

When a not-yet-logged-in user opens a deep link (e.g. a /env/X/users URL shared from elsewhere), they're bounced to sign-in with the original URL preserved as ?next=…. After signing in, they land back on the original page instead of the default
home. Same applies on the way through 2FA — ?next= is carried across the challenge step.

🧭 Environment-aware landing

The "where do I go after sign-in?" decision is no longer a hardcoded env id baked into server config. The SPA now picks the landing env from useAppContext().environment → localStorage → primary env → first env in the user's list, so a user who only
belongs to env 7 is no longer dumped on env 1.

🪟 404 stays inside the admin shell

Hitting an unknown URL while logged in used to drop the user on a fullscreen blank 404 with no way back to the app. The 404 now renders inside the same shell, with the sidebar still visible, so navigation is one click away. Hitting an unknown URL while
not logged in funnels through the same sign-in flow as any other protected page (preserving ?next=); hitting it on a still-being-set-up self-host instance redirects to /auth/setup-admin like the rest of the routes.

🎨 Sign-in visual refresh

The sign-in / sign-up / 2FA / password-reset cards now sit on a subtle grid-and-glow background keyed off the site's brand HSL variable, replacing the flat indigo gradient. Adjusting the brand colour in the future will carry these pages along
automatically.

🐛 Fixes

• Admin nav highlight restored. Users / Companies / Settings were no longer highlighted in the sidebar after navigating into them. Fixed by switching active-state detection from the (now wrong) inner-route id to URL pattern matching.
• OAuth failure lands on the sign-in page, not the API. Split-origin deploys (API and SPA on different hosts) used to dump OAuth-failure traffic onto a non-existent /auth/signin route on the API host. The redirect now prefixes the SPA host
  correctly.

🛠️ Under the hood

The apps/web auth surface was reorganised end-to-end. The bullets above are the visible deltas; here's the architectural shape behind them:

• The hand-rolled CustomRoute if-chain in routes/index.tsx is replaced by <AuthGuard mode='guest' | 'user' | 'setup'>, a single three-mode state machine that owns every auth-related redirect (setup-admin enforcement, sign-in bounce with ?next=,
  2FA enrolment). routes/config.ts becomes a nested RouteObject tree with React.lazy per-page chunks; page-area providers (Environment / Attribute / Subscription) mount once at the user-area parent and stop remounting on every navigation.
• Seven hand-rolled <Card> + <CardHeader> blocks across the auth pages collapse into one <AuthCard> shell that owns the title chrome, description, footer slot, and loading skeleton. The three legacy React contexts that shadowed react-hook-form's
  <Form> (SignInContext / RegistrationContext / InviteContext) are dropped — the same data flows through useFormContext() and props.
• The Auth.redirectUrl field on the GraphQL schema and the LOGIN_REDIRECT_URL env var that fed it are gone. The SPA now owns the post-login destination decision: ?next= (validated as same-origin) wins, otherwise LandingRedirect resolves the env.
  OAuth callbacks redirect to the SPA root through the same handler.
• packages/hooks/src/hooks/gql.ts had grown to 1306 lines; the auth domain (13 hooks + 3 new mutation wrappers) splits out to a new hooks/auth.ts module. The why, and the triggers that should pull more domains out in the future, are documented in
  docs/adr/0002-hook-domain-boundary.md. The package also gets a README with the decision tree for adding new hooks.

Full Changelog: https://github.com/usertour/usertour/compare/v0.7.7...v0.7.8