Arnas Donauskas 8bbbe0a471 fix(settings): wrap useSearchParams pages in Suspense so nav works in prod ... The settings page derived its active panel from `useSearchParams()` but wasn't wrapped in a Suspense boundary. In Next 16 that fails the production build ("missing Suspense with CSR bailout") and forces the page to bail to full client-side rendering — shipping a settings screen whose rail click handlers never wire up. Because the account-menu Settings link targets `?tab=whatsapp`, users land on the WhatsApp panel and can't navigate to any other section ("locked on WhatsApp"). Wrap the `useSearchParams` consumer in `<Suspense>` on the three affected dashboard pages — settings, inbox, automations/new — mirroring the split login/signup already use. Also add the missing `Settings.sections.quick-replies` label, which was rendering as a raw translation key in the settings rail. Verified: production build now succeeds (previously errored out during static generation); every settings rail section navigates correctly in a production build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-17 15:08:25 +03:00
..
en.json	fix(settings): wrap useSearchParams pages in Suspense so nav works in prod	2026-07-17 15:08:25 +03:00
ko.json	feat(i18n): add Korean (ko) translation	2026-07-12 00:06:31 +07:00