Blog sets <html lang> to a language it doesn't support (ko from the Wallet) while rendering English texts

Follow-up to #1205 (closed), found during its live check on https://denser.discuss.peerverity.info (2026-10-15).

Problem and intended result

The Wallet supports ko (apps/wallet/i18n/settings.ts); the Blog does not (apps/blog/i18n/settings.ts: ar en es fr it ja pl ru zh). Since #1205 (closed), both apps share one NEXT_LOCALE cookie. After a user picks Korean in the Wallet, /blog/trending renders English UI texts (i18next falls back) but <html lang="ko">, because apps/blog/app/layout.tsx takes lang from the raw cookie value. The Blog's start-up ensureLocaleCookie keeps any non-empty value. Screen readers then read English text with Korean pronunciation, the same symptom #1205 (closed) fixed for the localStorage mismatch.

Intended result: the Blog's <html lang>, its flag and its switcher's selected value name the language its texts are actually rendered in. The shared cookie is not rewritten, so the Wallet keeps Korean.

Required behavior

  • The Blog resolves its effective locale as the cookie value when it is in the Blog's languages, else defaultLocale. It uses that effective locale for <html lang>, dir, the LocaleProvider value, the flag and i18n.
  • The Blog does not overwrite a cookie value it does not support (the Wallet's choice survives a Blog visit).

Acceptance criteria

  • Under cookie ko, /blog/trending renders English texts with <html lang="en"> and the GB flag, and the cookie is still ko afterwards.
  • Under cookie ko, the Wallet still renders Korean.
  • Under cookie pl, the Blog is unchanged (Polish, lang="pl").

Verification

Blog fixture spec with the cookie preset to ko. Live check on peerverity after promote.

Integration points

  • apps/blog/app/layout.tsx — effective locale for lang/LocaleProvider
  • apps/blog/features/layouts/site-header/client-effects.tsx — no rewrite of an unsupported cookie

Scope boundary

Adding Korean translations to the Blog is out of scope.