@remit/web-client 0.0.324 → 0.0.326

package/src/routes/mail/brief/$threadId.tsx

@@ -1,16 +0,0 @@
-/**
- * /mail/brief/$threadId — a conversation open in the brief's reading pane.
- *
- * The brief is cross-mailbox, and the thread is still the whole address: the
- * folder its mail is filed in comes from the thread's own data, since
- * `GET /threads/{threadId}/messages` answers with rows that each name their
- * mailbox. A segment for the folder would be a second owner of a fact the
- * thread already carries.
- *
- * A layout, because the message segment nests under it.
- */
-import { createFileRoute, Outlet } from "@tanstack/react-router";
-
-export const Route = createFileRoute("/mail/brief/$threadId")({
-	component: Outlet,
-});

package/src/routes/mail/brief/compose.{-$outboxMessageId}.tsx

@@ -1,22 +0,0 @@
-// biome-ignore lint/style/useFilenamingConvention: TanStack Router convention
-/**
- * /mail/brief/compose — the compose surface, open over the daily brief, and
- * /mail/brief/compose/<outboxMessageId> once it has a draft to write to.
- *
- * A sibling of the thread route, so navigating here unmatches whatever the list
- * had open in the same transition: nothing has to be closed first, and "opened"
- * and "rendered" are one fact.
- *
- * The draft is an optional segment of this one route rather than a child route,
- * because the first autosave adopts the id it just created while the reader is
- * still typing. Two routes would unmount the composer mid-sentence; one route
- * with a param that arrives is a rewritten address and nothing more.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { FullCompose } from "@/components/compose/FullCompose";
-
-export const Route = createFileRoute("/mail/brief/compose/{-$outboxMessageId}")(
-	{
-		component: FullCompose,
-	},
-);

package/src/routes/mail/brief/index.tsx

@@ -1,14 +0,0 @@
-/**
- * The brief's reading pane. It is a route because the pane belongs to the list
- * it was opened from; the thread and message segments arrive under it.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { BriefPane } from "@/components/mail/BriefPane";
-
-function BriefReadingPane() {
-	return <BriefPane.Reading />;
-}
-
-export const Route = createFileRoute("/mail/brief/")({
-	component: BriefReadingPane,
-});

package/src/routes/mail/brief.tsx

@@ -1,52 +0,0 @@
-/**
- * /mail/brief — the daily brief, one of the four list layouts.
- *
- * The route mounts the list and the shell around it, and the reading pane is
- * the `Outlet`, so what the pane shows is whatever route is matched under this
- * one rather than a decision made somewhere above. The open thread and the
- * message inside it are the segments below, which is why nothing here reads a
- * selection out of the query.
- */
-import { ErrorState } from "@remit/ui";
-import {
-	createFileRoute,
-	type ErrorComponentProps,
-	Outlet,
-} from "@tanstack/react-router";
-import { MailShell } from "@/components/layout/MailShell";
-import { BriefPane } from "@/components/mail/BriefPane";
-import { briefSearchSchema } from "@/lib/mail-search";
-import { useOpenThreadPath, useSearchMirror } from "@/routing";
-
-const BriefError = ({ error, reset }: ErrorComponentProps) => (
-	<div className="flex h-full items-center justify-center bg-canvas p-4">
-		<ErrorState
-			title="Couldn't load your mailboxes"
-			error={error}
-			onRetry={reset}
-		/>
-	</div>
-);
-
-function BriefLayout() {
-	const thread = useOpenThreadPath();
-	useSearchMirror({ to: "/mail/brief" });
-
-	return (
-		<BriefPane thread={thread}>
-			<MailShell
-				phone={<BriefPane.Phone />}
-				list={<BriefPane.List />}
-				reading={<Outlet />}
-				intelligence={<BriefPane.Intelligence />}
-				hasThread={Boolean(thread)}
-			/>
-		</BriefPane>
-	);
-}
-
-export const Route = createFileRoute("/mail/brief")({
-	component: BriefLayout,
-	validateSearch: briefSearchSchema,
-	errorComponent: BriefError,
-});

package/src/routes/mail/flagged/$threadId/$messageId/$mode.{-$outboxMessageId}.tsx

@@ -1,15 +0,0 @@
-// biome-ignore lint/style/useFilenamingConvention: TanStack Router convention
-/**
- * The reply, reply-all or forward under a conversation opened from Starred.
- *
- * The same shape as the brief's: a child of the message so the source is the
- * address, the mode as one param rather than three literal routes, and the
- * draft as an optional segment so recording it does not unmount the composer.
- * The conversation reads it off the address and opens it at its head.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { replySearchSchemas } from "@/lib/mail-search";
-
-export const Route = createFileRoute(
-	"/mail/flagged/$threadId/$messageId/$mode/{-$outboxMessageId}",
-)({ validateSearch: replySearchSchemas.flagged });

package/src/routes/mail/flagged/$threadId/$messageId.tsx

@@ -1,23 +0,0 @@
-/**
- * /mail/flagged/$threadId/$messageId — the same conversation, with one of its
- * messages expanded and scrolled to.
- *
- * A message is not addressable on its own: `GET /messages/{messageId}` answers
- * with no thread, so the pane has nothing to fetch by. The segment names which
- * message inside the thread the reader pointed at, and the surface it renders is
- * the thread's.
- *
- * It mounts the pane rather than delegating to an index route, because the
- * reply is a segment under it: a conversation that came back on a child match
- * would collapse and scroll to the top the moment someone pressed Reply.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { FlaggedPane } from "@/components/mail/FlaggedPane";
-
-function FlaggedMessagePane() {
-	return <FlaggedPane.Reading />;
-}
-
-export const Route = createFileRoute("/mail/flagged/$threadId/$messageId")({
-	component: FlaggedMessagePane,
-});

package/src/routes/mail/flagged/$threadId/index.tsx

@@ -1,14 +0,0 @@
-/**
- * The thread with no message named. The pane opens on the newest message, the
- * same as for a thread whose row the reader never pointed at.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { FlaggedPane } from "@/components/mail/FlaggedPane";
-
-function FlaggedThreadPane() {
-	return <FlaggedPane.Reading />;
-}
-
-export const Route = createFileRoute("/mail/flagged/$threadId/")({
-	component: FlaggedThreadPane,
-});

package/src/routes/mail/flagged/$threadId.tsx

@@ -1,16 +0,0 @@
-/**
- * /mail/flagged/$threadId — a conversation open in the flagged list's reading
- * pane.
- *
- * Starred mail spans accounts and folders, and the thread is still the whole
- * address: the folder its mail is filed in comes from the thread's own data,
- * since `GET /threads/{threadId}/messages` answers with rows that each name
- * their mailbox.
- *
- * A layout, because the message segment nests under it.
- */
-import { createFileRoute, Outlet } from "@tanstack/react-router";
-
-export const Route = createFileRoute("/mail/flagged/$threadId")({
-	component: Outlet,
-});

package/src/routes/mail/flagged/compose.{-$outboxMessageId}.tsx

@@ -1,13 +0,0 @@
-// biome-ignore lint/style/useFilenamingConvention: TanStack Router convention
-/**
- * /mail/flagged/compose — the compose surface, open over the starred list, and
- * /mail/flagged/compose/<outboxMessageId> once it has a draft to write to.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { FullCompose } from "@/components/compose/FullCompose";
-
-export const Route = createFileRoute(
-	"/mail/flagged/compose/{-$outboxMessageId}",
-)({
-	component: FullCompose,
-});

package/src/routes/mail/flagged/index.tsx

@@ -1,10 +0,0 @@
-import { createFileRoute } from "@tanstack/react-router";
-import { FlaggedPane } from "@/components/mail/FlaggedPane";
-
-function FlaggedReadingPane() {
-	return <FlaggedPane.Reading />;
-}
-
-export const Route = createFileRoute("/mail/flagged/")({
-	component: FlaggedReadingPane,
-});

package/src/routes/mail/flagged.tsx

@@ -1,51 +0,0 @@
-/**
- * /mail/flagged — the Flagged virtual mailbox, one of the four list layouts.
- *
- * A flat starred list across accounts; same slots as the brief, intelligence
- * rail included. The reading pane is the `Outlet`, so what it shows is whatever
- * route matched below this one, and the open thread and the message inside it
- * are the segments there rather than a selection read out of the query.
- */
-import { ErrorState } from "@remit/ui";
-import {
-	createFileRoute,
-	type ErrorComponentProps,
-	Outlet,
-} from "@tanstack/react-router";
-import { MailShell } from "@/components/layout/MailShell";
-import { FlaggedPane } from "@/components/mail/FlaggedPane";
-import { flaggedSearchSchema } from "@/lib/mail-search";
-import { useOpenThreadPath, useSearchMirror } from "@/routing";
-
-const FlaggedError = ({ error, reset }: ErrorComponentProps) => (
-	<div className="flex h-full items-center justify-center bg-canvas p-4">
-		<ErrorState
-			title="Couldn't load your starred mail"
-			error={error}
-			onRetry={reset}
-		/>
-	</div>
-);
-
-function FlaggedLayout() {
-	const thread = useOpenThreadPath();
-	useSearchMirror({ to: "/mail/flagged" });
-
-	return (
-		<FlaggedPane thread={thread}>
-			<MailShell
-				phone={<FlaggedPane.Phone />}
-				list={<FlaggedPane.List />}
-				reading={<Outlet />}
-				intelligence={<FlaggedPane.Intelligence />}
-				hasThread={Boolean(thread)}
-			/>
-		</FlaggedPane>
-	);
-}
-
-export const Route = createFileRoute("/mail/flagged")({
-	component: FlaggedLayout,
-	validateSearch: flaggedSearchSchema,
-	errorComponent: FlaggedError,
-});

package/src/routes/mail/index.tsx

@@ -1,14 +0,0 @@
-/**
- * `/mail` has no view of its own: the daily brief is one of the four lists and
- * lives at its own path, so every link into the mail app that names no list
- * lands here and is sent on to the brief carrying whatever it arrived with.
- */
-import { createFileRoute, redirect } from "@tanstack/react-router";
-import { mailIndexSearchSchema } from "@/lib/mail-search";
-
-export const Route = createFileRoute("/mail/")({
-	validateSearch: mailIndexSearchSchema,
-	beforeLoad: ({ search }) => {
-		throw redirect({ to: "/mail/brief", search, replace: true });
-	},
-});

package/src/routes/mail/outbox/compose.{-$outboxMessageId}.tsx

@@ -1,17 +0,0 @@
-// biome-ignore lint/style/useFilenamingConvention: TanStack Router convention
-/**
- * /mail/outbox/compose — the compose surface, open over the outbox, and
- * /mail/outbox/compose/<outboxMessageId> for the draft it is editing.
- *
- * `draft/<outboxMessageId>` beside it reads an outbox message; this writes one.
- * The two are separate addresses because they are separate surfaces, and "Edit
- * as draft" is the move from one to the other.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { FullCompose } from "@/components/compose/FullCompose";
-
-export const Route = createFileRoute(
-	"/mail/outbox/compose/{-$outboxMessageId}",
-)({
-	component: FullCompose,
-});

package/src/routes/mail/outbox/draft/$outboxMessageId.tsx

@@ -1,19 +0,0 @@
-/**
- * /mail/outbox/draft/$outboxMessageId — one outbox message open in the
- * reading pane.
- *
- * An outbox message is addressable on its own: it belongs to no thread and no
- * folder, so the id is the whole address. The `draft/` prefix keeps the id in a
- * named segment, so the literal siblings the outbox will grow stay
- * distinguishable from it.
- */
-import { createFileRoute } from "@tanstack/react-router";
-import { OutboxPane } from "@/components/mail/OutboxPane";
-
-function OutboxDraftPane() {
-	return <OutboxPane.Reading />;
-}
-
-export const Route = createFileRoute("/mail/outbox/draft/$outboxMessageId")({
-	component: OutboxDraftPane,
-});

package/src/routes/mail/outbox/index.tsx

@@ -1,10 +0,0 @@
-import { createFileRoute } from "@tanstack/react-router";
-import { OutboxPane } from "@/components/mail/OutboxPane";
-
-function OutboxReadingPane() {
-	return <OutboxPane.Reading />;
-}
-
-export const Route = createFileRoute("/mail/outbox/")({
-	component: OutboxReadingPane,
-});

package/src/routes/mail/outbox.tsx

@@ -1,32 +0,0 @@
-/**
- * /mail/outbox — one of the four list layouts. Two panes, list and reading;
- * there is no intelligence rail for mail that has not been sent yet.
- *
- * The open message is the segment below this one, which is why nothing here
- * reads a selection out of the query.
- */
-import { createFileRoute, Outlet } from "@tanstack/react-router";
-import { MailShell } from "@/components/layout/MailShell";
-import { OutboxPane } from "@/components/mail/OutboxPane";
-import { outboxSearchSchema } from "@/lib/mail-search";
-import { useOutboxDraftId, useSearchMirror } from "@/routing";
-
-function OutboxLayout() {
-	const outboxMessageId = useOutboxDraftId();
-	useSearchMirror({ to: "/mail/outbox" });
-
-	return (
-		<OutboxPane outboxMessageId={outboxMessageId}>
-			<MailShell
-				phone={<OutboxPane.Phone />}
-				list={<OutboxPane.List />}
-				reading={<Outlet />}
-			/>
-		</OutboxPane>
-	);
-}
-
-export const Route = createFileRoute("/mail/outbox")({
-	component: OutboxLayout,
-	validateSearch: outboxSearchSchema,
-});

package/src/routes/mail.tsx

@@ -1,262 +0,0 @@
-import {
-	configOperationsGetConfigOptions,
-	unifiedThreadOperationsListAllThreadsOptions,
-} from "@remit/api-http-client/@tanstack/react-query.gen.ts";
-import {
-	ErrorState,
-	KeyboardShortcutsModal,
-	useTriageKeyboard,
-} from "@remit/ui";
-import { useQuery } from "@tanstack/react-query";
-import {
-	createFileRoute,
-	Outlet,
-	useNavigate,
-	useRouterState,
-} from "@tanstack/react-router";
-import { useCallback, useEffect, useMemo } from "react";
-import { z } from "zod";
-import { ComposeFab } from "@/components/layout/ComposeFab";
-import { MailShellProvider } from "@/components/layout/MailShell";
-import { MailTopBar } from "@/components/layout/MailTopBar";
-import { MailNav } from "@/components/mail/MailNav";
-import { useKeyboardNavigation } from "@/hooks/useKeyboardNavigation";
-import { isSinglePaneTier, useLayoutTier } from "@/hooks/useLayoutTier";
-import { useMailboxNameIndex } from "@/hooks/useMailboxNameIndex";
-import { useRailPanels } from "@/hooks/useRailPanels";
-import { useResultFolderIndex } from "@/hooks/useResultFolderIndex";
-import { useStaleAccountSync } from "@/hooks/useStaleAccountSync";
-import { MailContext } from "@/lib/mail-context";
-import { MailFreshnessProvider } from "@/lib/mail-freshness";
-import { mailListRoute } from "@/lib/mail-route";
-import { buildAccountNameIndex } from "@/lib/search-token-index";
-import {
-	useIsComposing,
-	useOpenCompose,
-	useSearchField,
-	wizardEntryValue,
-	wizardStepValue,
-} from "@/routing";
-import "@/lib/client";
-
-// `MailContext` / `useMailContext` live in `@/lib/mail-context` so the provider
-// here and the child-route consumers resolve to a single module instance — see
-// that file for why the alias-vs-relative route-tree import split otherwise
-// breaks context.
-export { useMailContext } from "@/lib/mail-context";
-
-const mailSearchSchema = z.object({
-	q: z.string().optional(),
-	// The selection wizard's step (#477 clause 1.6). The router owns history, so
-	// the step is a validated search param rather than a raw pushState entry.
-	wizard: wizardStepValue,
-	// Which affordance opened it, so a reload lands back on the walk it was in.
-	wizardFrom: wizardEntryValue,
-});
-
-export const Route = createFileRoute("/mail")({
-	// Kick off config and the cross-account thread list together, without
-	// awaiting either — the route paints its skeleton shell immediately and the
-	// queries resolve in parallel rather than serialized behind config. The
-	// zero-account onboarding redirect moved into the component (see
-	// MailLayout), so a cold load no longer blocks first paint on the network.
-	loader: ({ context: { queryClient } }) => {
-		void queryClient.prefetchQuery(configOperationsGetConfigOptions());
-		void queryClient.prefetchQuery({
-			...unifiedThreadOperationsListAllThreadsOptions(),
-			staleTime: 60_000,
-		});
-	},
-	component: MailLayout,
-	validateSearch: mailSearchSchema,
-});
-
-function MailLayout() {
-	const navigate = useNavigate();
-	const tier = useLayoutTier();
-	// Below the reading boundary (phone AND tablet) the shell shows a SINGLE
-	// pane — there is no reading pane to host the thread or the compose surface.
-	// So both tiers use the single-pane view, which swaps the pane in place
-	// between list, open thread, and compose. Keying this off "phone" alone left
-	// tablet with no compose surface (compose lives in the reading pane, which
-	// tablet doesn't mount) — the "c" shortcut / FAB opened nothing.
-	const isSinglePane = isSinglePaneTier(tier);
-	// What the address, the stored preference and the two rail verbs come to
-	// (`hooks/useRailPanels`): a raise surfaces the rail for the thread in hand,
-	// the reader's own toggle is the one that stores where they want it (#778).
-	const {
-		openOverlay,
-		intelligenceOpen,
-		showOverlay,
-		toggleIntelligence,
-		raiseIntelligence,
-	} = useRailPanels();
-	const showShortcuts = openOverlay === "shortcuts";
-	const drawerOpen = openOverlay === "nav";
-
-	// The one search field and the query it commits (`useSearchField`): seeded
-	// from the URL, mirrored back by each list route's own `useSearchMirror`,
-	// and re-seeded from the address whenever the reader leaves the view (#47).
-	const { searchInput, committedQuery, viewKey, setSearchInput } =
-		useSearchField();
-
-	const {
-		data: config,
-		isLoading,
-		isError: isConfigError,
-		error: configError,
-		refetch: refetchConfig,
-	} = useQuery({
-		...configOperationsGetConfigOptions(),
-		// Config only changes when accounts are added/edited/removed; those
-		// mutations explicitly invalidate this query.
-		staleTime: Infinity,
-	});
-
-	// First-run guard: a zero-account user goes to the onboarding wizard. This
-	// lives here (not a blocking beforeLoad) so a cold load paints the skeleton
-	// shell immediately; the redirect fires once config arrives. It guards the
-	// /mail parent so it holds for every child route — index redirect, daily
-	// brief (#426/#484), etc.
-	const hasNoAccounts = Boolean(config && (config.accounts?.length ?? 0) === 0);
-	useEffect(() => {
-		if (!hasNoAccounts) return;
-		navigate({ to: "/onboarding", replace: true });
-	}, [hasNoAccounts, navigate]);
-
-	// Global keyboard shortcut for help
-	useKeyboardNavigation({
-		enabled: !showShortcuts,
-		bindings: [
-			{
-				key: "?",
-				action: "help",
-				handler: () => showOverlay("shortcuts"),
-				noModifiers: false, // Allow shift+/
-				preventDefault: true,
-			},
-		],
-	});
-
-	// `c` / ⌘N off the mailbox routes — the brief, Flagged, the outbox. On a
-	// mailbox the pane's own triage layer owns the key, so this is disabled there
-	// rather than firing a second compose alongside it, and while the composer is
-	// up the key belongs to whatever is being typed. An open modal contains the
-	// key through the shared overlay stack, so this layer never opens compose out
-	// from under one (#959).
-	const openCompose = useOpenCompose();
-	const isComposing = useIsComposing();
-	const onMailbox = useRouterState({
-		select: (s) => mailListRoute(s.matches)?.list === "mailbox",
-	});
-	const composeHandlers = useMemo(
-		() => ({ compose: openCompose }),
-		[openCompose],
-	);
-	useTriageKeyboard({
-		enabled: !onMailbox && !isComposing,
-		handlers: composeHandlers,
-	});
-
-	// Clears the search field; the list route's mirror drops `q` from the URL
-	// after the debounce settles.
-	const handleSearchClear = useCallback(() => {
-		setSearchInput("");
-	}, [setSearchInput]);
-
-	// Esc inside the search field clears only the query (#489).
-	const handleSearchClearQuery = useCallback(() => {
-		setSearchInput("");
-	}, [setSearchInput]);
-
-	const accounts = config?.accounts ?? [];
-	const accountIds = useMemo(
-		() => accounts.map((account) => account.accountId),
-		[accounts],
-	);
-	const mailboxNameIndex = useMailboxNameIndex(accounts);
-	const resultFolderIndex = useResultFolderIndex(accounts).index;
-	const accountNameIndex = useMemo(
-		() => buildAccountNameIndex(accounts),
-		[accounts],
-	);
-
-	// Auto-trigger a mailbox-list sync for any account whose lastSyncAt is
-	// older than 15 minutes (or unset). Fires once per accountId per session
-	// — re-mounts of MailLayout will not retrigger. See #205.
-	useStaleAccountSync(accounts);
-
-	const handleMailboxSelect = useCallback(() => {
-		// Auto-collapse the mobile drawer after the user picks an inbox from the
-		// sidebar (#199). Above the slide-over the sidebar is a pane, and there is
-		// no overlay of its own to take down.
-		if (openOverlay !== "nav") return;
-		showOverlay(undefined);
-	}, [openOverlay, showOverlay]);
-
-	const mailContextValue = {
-		accounts,
-		mailboxNameIndex,
-		accountNameIndex,
-		resultFolderIndex,
-		// The committed local value is the source of truth for search; it is
-		// mirrored to the URL for shareable links.
-		searchQuery: committedQuery,
-		searchInput,
-		searchViewKey: viewKey,
-		onSearchChange: setSearchInput,
-		onSearchClear: handleSearchClear,
-		onSearchClearQuery: handleSearchClearQuery,
-		intelligenceOpen,
-		onToggleIntelligence: toggleIntelligence,
-		onRaiseIntelligence: raiseIntelligence,
-	};
-
-	// Single nav node: the kit renders it as a pane (≥1024px) or inside its
-	// own slide-over Dialog (narrow), never both — so there is exactly one
-	// "Mailboxes" nav landmark at any width. `MailNav` adds the mobile
-	// Settings + bug-report footer when it detects the slide-over context.
-	const shellChrome = {
-		isSinglePane,
-		isLoading: isLoading || hasNoAccounts,
-		intelligenceOpen,
-		nav: <MailNav accounts={accounts} onMailboxSelect={handleMailboxSelect} />,
-		// Desktop only. Below 1024px the single pane keeps its own header search
-		// and the phone takeover; there is no room for a bar spanning panes that do
-		// not exist side by side.
-		topBar: isSinglePane ? undefined : <MailTopBar accounts={accounts} />,
-		// Single-pane only, where the FAB is the compose entry point. Above it the
-		// top bar owns compose.
-		overlay: isSinglePane ? <ComposeFab /> : undefined,
-		navOpen: drawerOpen,
-		onOpenNav: () => showOverlay("nav"),
-		onCloseNav: () => showOverlay(undefined),
-	};
-
-	return (
-		<MailContext.Provider value={mailContextValue}>
-			<MailFreshnessProvider accountIds={accountIds}>
-				{isConfigError ? (
-					<div className="flex h-full items-center justify-center bg-canvas p-4">
-						<ErrorState
-							title="Couldn't load your account"
-							error={configError}
-							onRetry={() => {
-								refetchConfig();
-							}}
-						/>
-					</div>
-				) : (
-					// Each list route mounts its own shell around its own panes.
-					<MailShellProvider chrome={shellChrome}>
-						<Outlet />
-					</MailShellProvider>
-				)}
-				<KeyboardShortcutsModal
-					isOpen={showShortcuts}
-					onClose={() => showOverlay(undefined)}
-				/>
-			</MailFreshnessProvider>
-		</MailContext.Provider>
-	);
-}

package/src/routes/onboarding.tsx

@@ -1,47 +0,0 @@
-import { useQueryClient } from "@tanstack/react-query";
-import { createFileRoute, useNavigate } from "@tanstack/react-router";
-import { useCallback } from "react";
-import { OnboardingWizard } from "@/components/onboarding/OnboardingWizard";
-import { completeOnboarding } from "@/lib/onboarding-completion";
-import { useTelemetry } from "@/lib/telemetry-context";
-
-/**
- * /onboarding — full-screen wizard for first-run users (zero accounts).
- *
- * Redirected to automatically by the /mail route when config.accounts is empty.
- * After completing the wizard the user is sent to /mail (inbox).
- */
-export const Route = createFileRoute("/onboarding")({
-	component: OnboardingPage,
-});
-
-function OnboardingPage() {
-	const telemetry = useTelemetry();
-	const queryClient = useQueryClient();
-	const navigate = useNavigate();
-
-	// A client-side navigation carries the query cache with it, and the /mail
-	// first-run guard reads config from that cache — a stale zero-account entry
-	// bounces the user straight back into the wizard. A document load starts
-	// from an empty cache, so the guard sees the account that was just created.
-	const handleComplete = useCallback(
-		(_accountId: string) => {
-			void completeOnboarding({
-				queryClient,
-				recordCompleted: () => telemetry.recordEvent("onboarding.completed"),
-				navigateToInbox: () => {
-					window.location.assign("/mail");
-				},
-			});
-		},
-		[telemetry, queryClient],
-	);
-
-	return (
-		<OnboardingWizard
-			skipWelcome={false}
-			onComplete={handleComplete}
-			onImportConfig={() => void navigate({ to: "/import" })}
-		/>
-	);
-}