feedback5: Japanese, Korean and Traditional Chinese ship — the official game texts of the JP / KR / TW clients (data/i18n/ja.json 96.5 %, ko.json 97.4 %, zh-TW.json 91.1 % of 22 114 texts, built with build-i18n --lang from ArknightsAssets/ArknightsGamedata) and minimal UI packs public/i18n/ja.json, ko.json, zh-TW.json (a _meta manifest, no UI strings yet): ja / ko fall back to the English UI, zh-TW to the Simplified Chinese UI (no fallback; numbers in 萬 / 億); the owner's decision of 2026-10-07; UI translations welcome from the community; golden: unchanged (client text only)

- The packs: _meta = type lang, the code, its own and English name (日本語 / Japanese, 한국어 / Korean, 繁體中文 /
  Traditional Chinese), version 0.2.0, app >=0.2.0, authors, credits (the official client data, © Hypergryph (/ Yostar
  for JP and KR), via ArknightsAssets/ArknightsGamedata), fallback ["en"] for ja / ko and [] for zh-TW; formatted as
  `node tools/i18n.mjs template` writes them, so a translator runs it on the shipped file and keeps the manifest.
- Built offline from the tables W5AD downloaded and checked today (jp / kr 51.10.0, tw 51.2.0; copied into
  .cache/gamedata-<code>): coverage as W5AD measured; `build-i18n --lang <code> --check` up to date for en, ja, ko,
  zh-TW. `node tools/i18n.mjs check --all --strict`: 0 errors (en complete; ja / ko / zh-TW 0 of 1022 msgids, fallback).
  `node tools/packs.mjs list` lists the four packs with their game texts; `tools/package.mjs --dry-run --list` ships
  data/i18n and public/i18n of all four and the generated packs/index.json.
- With five languages the menu is a list (ui/lang.js SEGMENTED_MAX 4, W5AD's rule): test/ui/i18n.e2e.test.js reads and
  picks either form, expects the shipped languages, and checks each new pack in the browser (its official game text,
  the fallback UI, <html lang>) — SP_E2E=1: 3 / 3; the title page of the five devices (devices.e2e "title page") still
  fits: 5 / 5.
- Docs: docs/I18N.md (intro, §2, §5 "Shipped packs" with the call for UI translations), docs/PLAYING.md (语言),
  DESIGN §25.20 and the §25 intro's decisions of 2026-10-07.

Gate: non-browser suites 5024 / 5024 (test/i18n*, test/package, client-static 358 / 358), npm run golden ok,
test/golden.test.js 9 / 9, lint 0 errors, check:imports ok, typecheck ok.

docs/I18N.md

@@ -4,8 +4,9 @@ Chinese is the default; every other language is a switch (the owner's decision o
 opens in Chinese until the player picks a language on the title screen (top right) or in 设置 / Settings. Every
 language but Chinese is a **language pack** — a file in the language folder, nothing else (the owner's decision of
 2026-10-07; §5 "Adding a language"): the menu lists every pack the server finds, each under its own name (buttons up to
-four languages, a list beyond). English is a pack like any other; it ships with the game and is the complete one. The
-choice is kept in `localStorage` (`sp.pref.lang`); `?lang=<code>` in the address bar (`?lang=en`, `?lang=zh`) sets it
+four languages, a list beyond). English is a pack like any other; it ships with the game and is the complete one.
+Japanese, Korean and Traditional Chinese ship too, with the official game texts and no UI strings yet (§5 "Shipped
+packs"). The choice is kept in `localStorage` (`sp.pref.lang`); `?lang=<code>` in the address bar (`?lang=en`, `?lang=zh`) sets it
 once and is then removed; a stored language whose pack is gone opens in Chinese. A switch re-renders the page in place
 (no reload). Language packs are the first type of the content packs (docs/PACKS.md: the manifest, the registry, the
 index, the pack folders).
@@ -173,8 +174,10 @@ rebuilt.
   22 114 texts — the TW data is older, 51.2, and a Traditional text equal to the Simplified one counts as untranslated
   although it shows the same). The remake's own strings (stage-name composites, the fallback files) are English only;
   for another language the pack's UI file (`public/i18n/<code>.json`) is the fallback dictionary, and what is left falls
-  back per text at run time (the pack's chain, then Chinese). Only English is generated in the repository: a game-text
-  overlay ships with the UI pack of its language (a pack is listed by its UI file).
+  back per text at run time (the pack's chain, then Chinese). A game-text overlay ships with the UI pack of its language
+  (a pack is listed by its UI file): the repository generates English and, since the owner's decision of 2026-10-07,
+  `data/i18n/ja.json`, `ko.json` and `zh-TW.json` (§5 "Shipped packs"). Rebuild them like English after a data change
+  (`--lang <code> --check` says when one is out of date).
 - **A language without an official client** (French, German, Russian …) needs no game texts at all: they follow the
   pack's chain (`"fallback": ["en"]` shows the English ones). To translate some, write a community dictionary — a flat
   JSON `{ "<Chinese data text>": "<translation>" }`; the `names` of `data/i18n/en.json` (every game-data name with its
@@ -237,6 +240,14 @@ which are bilingual on purpose.
 
 ## 5. Adding a language
 
+**Shipped packs** (0.2.0; the owner's decision of 2026-10-07): English (complete) and three packs that carry the
+official game texts but no UI strings yet — 日本語 (`ja`: the JP client, 96.5 % of the game texts), 한국어 (`ko`: KR,
+97.4 %) and 繁體中文 (`zh-TW`: TW, 91.1 %; its data is older, and a Traditional text equal to the Simplified one counts as
+untranslated). Their UI falls back to English (`ja`, `ko`: `"fallback": ["en"]`) or, for `zh-TW`, to the Simplified
+Chinese msgids (no fallback — the owner's choice); `zh-TW` counts large numbers in 萬 / 億. **UI translations are
+welcome from the community**: start from the shipped file — `node tools/i18n.mjs template <code>` keeps its `_meta` and
+adds every msgid with an empty value — then follow the steps below and send a pull request.
+
 A language is a file in the language folder; the server lists it on the next page load (no restart, no build step, no
 code change). For a community translator: