A metadata-form tooltip spells a strict enum's legal values in translated locales, so the value an author is shown is one the schema refuses #19430

Path: P1 | 那条路第 1 步「写元数据」 | 严格枚举的合法值被翻译成本地词:在译文区工作的作者被告知写 下拉,而 schema 拒收它
分诊重测与定级:2026-09-20T20:53Z

What is wrong

A metadata-form tooltip names the legal values of a strict enum, and all three translated locales render those values as ordinary words. ⇒ an author — or an AI — working in a translated locale is told the option is 下拉, writes it, and the schema refuses it. ⚠️ That tooltip is the only place the panel names them.

⭐ This is the inverse of #19403's defect: there, English leaked into translated UI; here, translation leaked into a machine token that must stay English to be writable.

Measured on origin/main

⇒ the English tooltip spells what an author may write. The three translations spell what an author may not.

Seam: spec:UserFiltersSchema.element (packages/spec/src/ui/view.zod.ts:1506) → renderer: objectui plugin-list/src/UserFilters.tsx

⚠️ There are TWO element enums — ⛔ do not assume one schema

Measured by this filer, ⛔ not present in the originating report:

packages/spec/src/ui/view.zod.ts:1506   element: z.enum(['dropdown', 'tabs', 'toggle']).default('dropdown')
packages/spec/src/ui/view.zod.ts:4193   element: z.enum(['dropdown', 'toggle']).default('dropdown')

⇒ the second has ⛔ no tabs. Whoever takes this card must establish which schema each tooltip describes before rewriting either, and check whether a tooltip on the second surface has the same defect or a worse one (naming a value its own enum does not accept).

Why it is a card rather than a rider

Found during #19403 round 2 (PR #19428), whose dev declined the in-place fix and named the failing condition: the bounded-fix exemption requires the same defect class as the card, and this is the opposite one. ⭐ That refusal is also what made that round deliberately keep None / Tabs / Dropdown in English — the decision and this finding are one reading.

The class, and its boundary — ⛔ both recorded so the taker does not over-reach

⚠️ In class: a tooltip that spells a strict enum's values in a translated locale, so the spelled value is unwritable.

⛔ NOT in class, and measured as the boundary: page.fields.interfaceConfig.appearance.helpText writes renderer tokens capitalised (Grid / Kanban / Calendar) while page.fields.type.helpText on the same panel writes them lower-case, matching VisualizationTypeSchema. ⭐ That is softer — the sentence reads as display names, and the neighbouring helpText spells the values correctly one row up. ⇒ recorded as the edge of this class, ⛔ deliberately not swept in.

Suggested shape (⛔ not a ruling)

Keep the enum values verbatim and English inside the translated sentence, exactly as #19403 round 2 did for None / Tabs / Dropdown, and translate the prose around them. ⚠️ Then ask whether a pin can see this class at all — ⛔ no existing pin does, and a census over .label leaves ⛔ cannot reach a helpText.

⭐ The instrument that would work, and its control: for each schema key whose tooltip names enum values, assert the tooltip contains each value verbatim in every locale, with a positive control (a tooltip that legitimately translates its prose) so the assertion cannot pass vacuously.

Dedupe words (⛔ the filer does not dedupe)

helpText translates enum values · userFilters element dropdown tabs toggle · translated locale names illegal value · metadata form tooltip enum spelling · strict enum rejects translated token

Provenance

Surfaced as an out-of-scope finding by the os-dev agent on #19403 round 2 (PR #19428) with a Seam: line, and independently verified by the domain:engine execution PM seat — the enum at view.zod.ts:1506, the en tooltip naming the writable tokens, and the zh-CN tooltip naming untranslatable ones, all read on origin/main. The second enum at :4193 is this filer's own additional reading.

Generated by Claude Code