[Decision] 80 zh-Hant documentation pages describe an app that has no zh-Hant locale — there is no Traditional pack to source any UI noun from, and #1565 plus the #1758 button question are both downstream of it #1767

Filed by the repo:hotcrm seat (session session_019YKN9TPqDSSXUaYqp2j7MZ, R56). Surfaced by #1758's dev as an out-of-scope observation which it correctly declined to file — as that card's judgement, right. Filed here because reading it against the queue suggests it is a root with cards already sitting on top of it.

Measured on origin/main @ d47e37ac

objectstack.config.ts:206   supportedLocales: ['en', 'zh-CN', 'ja-JP', 'es-ES']
src/translations/           en/  es-ES/  ja-JP/  zh-CN/          ← no zh-Hant, no zh-TW
content/docs/**             80 files matching zh-Hant
content/docs/**             80 files matching zh-Hans            ← control: the two faces are exactly parallel

The console's own i18n bundle agrees independently — it ships en-US, zh-CN, ja-JP, es-ES and no zh-TW (measured by #1758's dev while resolving detail.add).

⇒ 80 documentation pages describe, in Traditional Chinese, an application a reader cannot obtain in Traditional Chinese. The zh-Hans face has a pack behind every UI noun it names. The zh-Hant face has none, because the pack does not exist.

Why this is a root and not just an observation

AGENTS.md §Documentation discipline rule 6 and ruling #1329 say a UI noun takes the zh-CN language-pack wording, never a freshly coined translation. That rule is well-formed for zh-Hans. For zh-Hant it has no source to point at — so every zh-Hant page naming a control faces a question the rule cannot answer, and each card that meets it has had to improvise a local answer.

Two live instances, both stated conservatively:

• Six zh-Hant pages spell English navigation paths and never say why — the convention is explained on seven pages and silent on six more #1565 — six zh-Hant pages spell navigation paths in English and never say why; the convention is explained on seven pages and silent on six. ⇒ Directly downstream. English is what you fall back to when there is no pack, and the silence is that nobody has written down that this is the rule.
• #1731 falsifies two passages #1720 landed: the Products panel now carries an add picker, in all three locales #1758 (landed today, PR docs(sales): the Products panel adds a line item, in all three locales #1762) — the new Products Add button. Simplified 添加 is determinable from the console build artifact; Traditional has no counterpart at all. The dev declined to coin one, on the reasoning that pinning zh-Hans would force a coined Traditional form to keep the two faces parallel. ⭐ The seat affirmed that call, and it was decided per-card, without a governing rule — which is exactly the cost of leaving this open.

⚠️ Stated precisely, so this card is not oversold:

• [Decision] What does a Chinese docs page do with a view name the app's own locale pack does not carry? revenue/approvals names five plugin-owned views in English and #1329's ruling cannot reach them #1552 is adjacent, not identical. It asks what a Chinese docs page does with a view name the app's pack does not carry — same family (a UI name with no pack entry), but its cause is plugin-owned views, not a missing locale. A ruling here would inform it; ⛔ it would not automatically resolve it.
• [Decision] Should a zh docs heading carry the English explicit anchor id, so same-page links work in every locale? The "zh pages drop the anchor" rule was a workaround for a limitation that has since been fixed #1359 (zh docs heading anchors) is ⛔ unrelated — a different mechanism entirely. It is named here only to say it is not claimed.

Four-axis框架

请裁 —— 三选一

⛔ 本席不建议在此代裁:这三条通向不同的产品承诺(我们是否面向繁体中文用户),而本席的档次上限已实测耗尽,不能代裁。

• A — 补一个 zh-Hant 应用 locale。 文档面与应用面重新对齐,规则 6 对两个中文面都成立。⚠️ 代价最大且是持续的:每个新字符串从此要四译变五译,与轴④直接冲突。
• B — 撤掉 zh-Hant 文档面。 80 个文件。⇒ 声明面收缩到实现面,enforce-or-remove 的字面执行。⚠️ 代价:丢掉一个已经写好、且内容质量很高的读者面 —— 这些页面不是机翻,是逐页写的。
• C — 保留,并把规矩写下来。 明写:zh-Hant 文档面没有应用 locale 支撑,因此其 UI 名词按既定顺序取值 —— 例如「有 zh-CN 包则用其对应繁体转写 / 否则保留英文原名」,并在每个 zh-Hant 页面顶部加一句一次性说明。⇒ 成本最低,并且直接关掉 Six zh-Hant pages spell English navigation paths and never say why — the convention is explained on seven pages and silent on six more #1565(它要的就是「说明为什么」)。⚠️ 但这是一条治理面裁决,需落到 AGENTS.md,⛔ 因此排在 PR docs(agents): restate the schema-validation section around where validation happens #1746 之后。

⚠️ 无论选哪条:⛔ 不要加守卫。 自由散文与它叙述的 UI 之间不存在机械关系(#1646 已裁死),而本仓刚测到一个空转的同类守卫(#1755)。

⛔ 不在本卡范围

⛔ 不动 src/。⛔ 不动 content/docs/releases/。⛔ 不改任何 zh-Hant 页面 —— 本卡只求一条裁决;改动是裁决之后另立的卡。

Refs: #1565(直接下游)· #1552(同族,不同成因)· #1758 / PR #1762(即兴决定的实例)· #1329 · #1755(空转守卫的前车)· #1646(拒绝散文守卫)