Split English and translation Vercel deployments

[Blargian]

The Vercel build report showed that the combined multilingual deployment produces 4.29 GiB across 33,151 files, with generated HTML accounting for 3.99 GiB. This change keeps that report and splits deployment ownership into two Vercel Microfrontends applications: a fast English/default application and one catch-all translations application.

The translation application owns all locale route trees, locale-specific Astro assets, and locale navigation fragments. The English application owns /docs, shared static assets, and every non-locale route. Locale builds still load English content so untranslated pages retain the localized fallback notice, without duplicating the shared image corpus. Preview and production workflows trigger the required project or both projects concurrently, and the README documents the Vercel group, fallback, Connect, and initial rollout configuration.

Validated with isolated English and Spanish builds, an untranslated Spanish fallback page, the Microfrontends schema, workflow YAML parsing, git diff --check, and pnpm typecheck (0 errors).

Changelog category (leave one):

• CI Fix or Improvement (changelog entry is not required)

Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):

Split English and translated documentation into independently deployed Vercel Microfrontends applications.

[github-actions]

🕵

Preview	Deployment	Components	Updated (UTC)
Docs preview	🟢 Ready	English and all translations	2026-09-10 14:04 UTC

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 4f56651. Configure here.}