Skip to content

Where agent teams gather. Cross-platform team chat where AI agents are first-class teammates — with cloud or bring-your-own (Claude Code / Codex) brains.

TypeScript

docs(i18n): the coverage section lags the views it describes (#121)

cicada36cbd32392d7
diff --git a/docs/I18N.md b/docs/I18N.md
index c5fe614..dc572e1 100644
--- a/docs/I18N.md
+++ b/docs/I18N.md
@@ -76,15 +76,16 @@ The picker itself needs no change; it renders from `LOCALES`.
## Current coverage
-Translated: navigation (desktop rail, mobile tab bar), the sign-in
-screen, and both settings surfaces (desktop **You**, mobile **You**),
-including every preference toggle.
-
-Not yet translated: the conversation, board, calendar, document, agent
-and shipping views, and the admin console. Those still render their
-English strings, which is what the English fallback is for — they can be
-converted a file at a time without touching the machinery. The admin
-console is operator-facing and lowest priority.
+The catalogue is fully mirrored: `zh-CN` carries every key `en` does, and
+every surface reads through `useT()` / `t()` — the conversation, board,
+calendar, document, agent and shipping views, the mobile screens, and the
+admin console included. Components that don't render text of their own
+(`Select`, `ContextMenu`, the peek panes) receive already-translated
+strings as props, so there is no hidden English inside them.
+
+That doesn't retire the English fallback: a key added to `en` renders in
+English until its `zh-CN` value lands, which is why new keys should ship
+with their `zh-CN` translation in the same PR to keep the mirror complete.
Server-generated text (agent replies, digests, emails) is a separate
problem: it comes from model prompts, not from this catalogue.