feat: promote staging localization and UI updates

[BWJ2310-backup]

Summary

Promotes the current staging branch to upstream/main.

This includes:

• Adds next-intl localization for public, auth, admin, workspace, chat, invite, changelog, unsubscribe, workflow, monitor, records, widget, and email surfaces.
• Moves visible app routes behind locale-aware routing with English, Spanish, and Chinese message bundles.
• Persists preferred locale for authenticated settings and waitlist records.
• Localizes transactional emails, metadata, sitemap, auth redirects, invite flows, and callback handling.
• Adds grouped sidebar/dropdown UI updates and monitor kanban header actions.
• Updates workflow editor, trigger, block, listing selector, market/charting, records, and monitor copy/behavior.
• Adds/updates focused tests across i18n, auth, routing, proxy, emails, monitor, records, workflow editor, selectors, and widgets.
• Updates Vitest/Vite/Turborepo tooling and adds a generated DB migration for locale fields.

Why

This promotes the staging integration that prepares TradingGoose for localized product surfaces, durable language preference handling, and cleaner dropdown/navigation UI before merging into main.

It also consolidates several staging fixes around auth redirects, invite callbacks, market search defaults, monitor layout, workflow/editor copy, and settings behavior.

Affected Areas

• apps/tradinggoose
• apps/docs
• packages/*
• Workflows / execution
• Realtime / sockets
• Market data / charting
• Dev tooling / CI / infra
• Documentation only
• Other: i18n/localization, DB migration, changelog

Issue Links( if any )

Refs #133

Includes staging merges:

• feat(i18n): add locale-aware routing and localized app copy #135
• feat(ui): add grouped sidebar dropdown menus #136

Validation

Branch/diff validation performed while preparing this PR:

git fetch upstream main
# fetched upstream/main successfully

git status --short --branch
# ## staging...upstream/staging
# no staged or unstaged file changes shown

git rev-parse HEAD upstream/main FETCH_HEAD
# HEAD: e167f5f69ea2859fad66ee20fa56bda2792b3a2f
# upstream/main/FETCH_HEAD: f6a7da47075a5e4d546480130b493532f7e275af

git diff --shortstat upstream/main...HEAD
# 633 files changed, 104960 insertions(+), 13071 deletions(-)

git log --oneline --decorate upstream/main..HEAD
# reviewed staging commits, including PR #135 i18n and PR #136 dropdown UI

Automated validation not run while drafting this PR body:

bun run test
bun run type-check
bun run build

Risk / Rollout Notes

This is a broad staging promotion with routing, localization, schema, and visible UI impact.

Primary rollout risks:

• Locale-aware routing changes may affect bookmarks, auth callbacks, invite links, metadata, sitemap output, and protected-route redirects.
• Email copy/rendering is centralized and localized, so transactional email rendering should be checked in staging before production rollout.
• Preferred locale persistence adds DB columns and changes settings/waitlist behavior.
• Dropdown and workflow/monitor UI changes are visible and should be smoke-tested on desktop and mobile.

Backout approach:

• Revert the merge if runtime issues appear before DB migration rollout.
• If the DB migration has already been applied, coordinate rollback separately or leave the added preferred_locale columns inert until a follow-up migration.

Config / Data Changes

• Env vars added or changed: None found.
• Database schema or migration impact: Adds preferred_locale to settings and waitlist through generated migration 0035_marvelous_avengers.
• External services or provider behavior changed: Localized email output and localized auth/invite URL generation now rely on existing site URL configuration; market listing search defaults now send normalized filter payloads.

Screenshots / Video

Recommended before merge:

• Locale switching on public/auth/workspace surfaces.
• Sidebar grouped dropdown menus.
• Monitor kanban header actions.
• Workflow editor dropdown/combobox behavior.

Checklist

• I kept the change focused and reviewed my own diff
• I validated the change locally and documented the results above
• I updated docs, examples, or copy if behavior/user-facing flows changed
• I called out any env, schema, provider, or rollout impact
• I did not include secrets, tokens, or private credentials in this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
studio (staging)	Ready	Preview, Comment	Jun 5, 2026 9:25pm

[greptile-apps]

Too many files changed for review. (633 files found, 500 file limit)