`I18nLabel` now admits an inline per-locale map — audit every read the compiler cannot see, and give Studio a way to author one

[yinlianghui]

Found while bumping @objectstack/spec to 17.0.0-rc.6 for objectstack#7100. Filed rather than fixed: the compile-visible half is repaired in that PR, this is the half a type-check cannot reach.

What changed upstream

I18nLabel was a plain string through rc.5 and became a union in rc.6:

rc.5   declare const I18nLabelSchema: z.ZodString;
       type I18nLabel = z.infer< typeof I18nLabelSchema >;            // string

rc.6   declare const I18nLabelSchema: z.ZodUnion< readonly [z.ZodString, z.ZodRecord< z.ZodString, z.ZodString >] >;
       type I18nLabel = z.input< typeof I18nLabelSchema >;            // string | Record< string, string >

The standalone I18nObject / I18nObjectSchema were retired in the same release and folded into I18nLabel; rc.6 also publishes InlineLocaleMap and a shared resolver, resolveI18nLabel(label, locale). So from rc.6 an author may legitimately write label: { en: 'Owner', 'zh-CN': '负责人' } anywhere the spec accepts an I18nLabel.

Part 1 — the reads the compiler cannot see

Bumping the pin turned up 9 sites where an I18nLabel flows into a string or ReactNode slot, and the compiler named every one of them. Those are fixed. The compiler is blind to the rest: any site where the label reaches a slot typed any, is interpolated into a template string, or is passed through an untyped prop renders [object Object] for the map form and stays green forever. That is the exact harm rc.6's own resolver doc comment calls out.

This needs a deliberate sweep of I18nLabel-typed fields (NavigationArea.label, DashboardWidget.title, nav-item labels, action labels, view/report labels, …) against their read sites, rather than a compile pass.

Note this repo also has its OWN resolveI18nLabel (packages/app-shell/src/utils/index.ts), which resolves a different vocabulary — a translation-key ref { key, defaultValue, params } — and does NOT accept the inline map. Two same-named resolvers over two vocabularies is itself worth a naming decision as part of this.

Part 2 — Studio cannot author the map form

DashboardWidgetInspector's title editor is a single-line Input bound straight to widget.title. Resolving a map into it and writing e.target.value back would silently collapse every other locale on the first keystroke, so objectstack#7100's PR takes the conservative branch: a map-valued title renders resolved and read-only. Nothing can hit that path yet (no stored title can be a map — I18nLabel was string through rc.5), which is why it was safe to take without a ruling, but it is a placeholder rather than an answer.

The real question is what the designer should offer: a per-locale editor, a "translate this label" affordance, or a deliberate decision that Studio only ever authors the string form and the map is API/import-only.

Why not in objectstack#7100's PR

That card is the global_nav retirement; it carries the rc.6 bump only because the two cannot compile apart. Part 1 is an unbounded audit and Part 2 is an authoring-surface design decision — neither is mechanically forced by the bump.

[os-zhuang]

Triage: needs-user-decision — Part 2 is an authoring-surface design call the body itself declines to make: what Studio should offer for a per-locale label map (per-locale editor / "translate this label" affordance / a deliberate string-only authoring decision), with the current read-only rendering explicitly "a placeholder rather than an answer". The two same-named resolveI18nLabel resolvers over two different vocabularies (spec's inline map vs app-shell's { key, defaultValue, params } ref in packages/app-shell/src/utils/index.ts) add a naming decision to the same ruling.

• Note for the deciding pass: Part 1 (the sweep of I18nLabel-typed fields against read sites the compiler cannot see — any-typed slots, template interpolation, untyped props rendering [object Object]) does not depend on the Part 2 ruling and could be split out as its own queue card if the ruling stalls; no stored map-form label can exist yet (the type was string through rc.5), so there is slack, but the audit is the half that prevents silent [object Object] regressions once maps appear.
• Dup check: no open card covers the inline-map audit or Studio map authoring (local filter over cached open lists; the many open i18n cards — Analytics surfaces resolve select-option labels but never apply the i18n bundle — reports and dashboards show English while lists and forms show the translation #4030/objectui: dashboard KPI cards drop the translated widget title/description — the self-contained metric path bypasses tWidgetTitle, and the plugin's private resolveLabel never calls t() #4032/Console: AddressField sub-labels and placeholders are hardcoded English literals — an address field is untranslatable on any non-English console #4028/[Studio i18n] 表单布局设计器未解析已有的对象字段和分组翻译 #3134 etc. — are bundle-application defects, different family). Track the @objectstack family at 17.0.0-rc.6 — the adaptation surface beyond what objectstack#7100 could carry #4167 cross-references this card as the deliberate split.
• Premise: rc.6 type shapes quoted from the resolved dist today; filed 15:12Z, current by construction.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[yinlianghui]

Part 1 inventory, measured: 13 sites in 5 packages, all of them tsc errors today

Found while doing #4167 (the rc.6 spec-symbol collisions) on the same stacked branch. Not claiming this card — recording the worklist, because part 1 turns out to be enumerable rather than an open-ended audit, and every site announces itself as a compile error.

Why these were not visible before

PR #4169 repaired eight widened-I18nLabel render sites and reported a green turbo run build (44/44) plus 14,609 passing tests. These thirteen were in neither number, for a mechanical reason worth writing down: these five packages build through vite/rolldown, not tsc, so turbo run build never type-checks their sources. Only turbo run type-check compiles them. A bump can therefore be build-green, test-green, and still carry a double-digit type-error count in exactly the packages that render labels.

The list

pnpm exec turbo run type-check --concurrency=2 --continue, at @objectstack/spec@17.0.0-rc.6:

package	file:line	what reaches the slot
layout	src/AppSchemaRenderer.tsx:169,173	NavigationArea.label → objectui's KEYED resolver (resolveLabel)
plugin-list	src/components/TabBar.tsx:140,200,216	ViewTab.label → ReactNode
plugin-dashboard	src/DashboardGridLayout.tsx:398,399	DashboardWidget.title → a string | undefined prop, then ReactNode
plugin-designer	src/DashboardEditor.tsx:143,231,341	widget title → ReactNode twice, and an input value once
app-shell	src/utils/resolveActionParams.test.ts:245,345,358	ActionParam.label → RawActionParam.label, declared string | undefined

All thirteen are the same fact — string | Record< string, string > where string was expected.

Three notes that change the shape of the work

1. plugin-designer/src/DashboardEditor.tsx:231 is an authoring WRITE, not a read. It is an input value, which is the same data-destroying path #4169 flagged and deliberately declined on DashboardWidgetInspector ("resolving a map into a single-line input and writing e.target.value back collapses every other locale on the first keystroke"). So this one is part 2's design question, not part 1's mechanical repair — the same conservative branch, or the real answer.

2. @object-ui/layout has NO i18n dependency, on purpose. NavigationRenderer.tsx says so at its own read points: "Enables convention-based i18n auto-resolution without coupling the layout package to i18n" — it takes t and the label resolvers as injected arguments. So "call resolveI18nLabel(label, language)" is not available there the way it was in app-shell's two sidebars; where the locale comes from is a design call in that package. @objectstack/spec is currently a devDependency of layout too (this PR moves it to dependencies for an unrelated re-export, so that part is already done).

3. app-shell's three are in a test file, and the underlying declaration is the real target. RawActionParam.label is string | undefined in src/utils/resolveActionParams.ts, so the test only surfaces it — the spec's ActionParam no longer fits the local raw shape. Widening RawActionParam.label is the fix, and then whatever paramToField does with a map form is the actual question.

Also worth knowing: element:record_picker.emptyText is a 14th site, of a different kind

rc.6 widened that key to I18nLabel too, and record-picker.tsx:213 passes it straight into a text node — but it is typed unknown-ish locally, so it does not show up as a tsc error. #4167 declares it as an authoring input with the narrowing named in its description and a KNOWN GAP pointing here, rather than advertising a shape the renderer drops. So the compile-error list above is a lower bound, not the whole surface: sites that read through any / unknown are silent.

Status

Left entirely alone by #4167 — this is your card's scope and the scope guard on that dispatch is explicit. Consequence to expect: the stacked chain's TypeScript Type Check job stays red until this lands, even though #4167's own gate (check:spec-symbols) is green. Measured on a second worktree at the untouched base db9dad961: base has 16 errors in 7 packages, #4167's branch has 13 in 5 — the same 13, minus 3 unrelated ones it repaired, none introduced.

---

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui]

Claim (PART 1 ONLY): PM loop round 6 — the fourth car of the rc.6 stacked train; part 2 (Studio authoring for inline locale maps) stays UNCLAIMED pending design input.
Session: session_017Qqyix2QcnpUC9XeYVDzx3 · Branch: claude/issue-4163-i18nlabel-render-sites · Worktree: objectui-issue-4163
File surface: the 13-site inventory the #4167 dev posted above (layout/AppSchemaRenderer, plugin-list/TabBar, plugin-dashboard/DashboardGridLayout, plugin-designer/DashboardEditor, app-shell/resolveActionParams.test) + tests. Serial constraints: stacks on claude/issue-4167-rc6-adaptation-remainder (PR #4189); stacked PRs trigger NO CI here — all gates local with output quoted, per #4189's worked precedent.
Container & model: M, mode:subagent, model: opus

Binding rulings for the two design edges the inventory flagged:

1. DashboardEditor:231 is a WRITE path — it does NOT get "fixed to compile" by flattening a locale map into a string (that is part 2's data-destroying hazard made real). It gets the same conservative treatment PR retire(studio): drop the global_nav designer surfaces with the rc.6 spec bump (objectstack#7100) #4169 took for the title editor: guard the write to strings-only, preserve an existing map untouched (read-only passthrough), and the type error dies from the guard, not from a cast. Pin: an inline map survives an unrelated edit-and-save round trip.
2. @object-ui/layout carries no i18n dependency BY DESIGN — its resolution uses the PRODUCER's own resolver from @objectstack/spec (post-Track the @objectstack family at 17.0.0-rc.6 — the adaptation surface beyond what objectstack#7100 could carry #4167 spelling: the spec export, not the renamed consumer-side one), locale threaded from props/context where the component already receives one, spec-default fallback otherwise; the choice and its reason documented at the call site. No new package dependency.
   The remaining sites are read-path rendering correctness: resolve the map to the right locale string, never [object Object], each site pinned red→green (the pre-fix red IS the tsc error — capture it per site). app-shell's target is RawActionParam.label per the inventory note, fixed at the type not the test.

---

Generated by Claude Code

[yinlianghui]

ACCEPT — part 1 (objectui seat PM, session session_017Qqyix2QcnpUC9XeYVDzx3, review of record) — PR #4208, the rc.6 train's tail (base = #4189's branch). Stays DRAFT and rides the train (#4169 → #4189 → #4208), all blocked solely on the #4165 ruling.

Premise re-verified from scratch at the stacked base (all 13 inventory sites reproduce, 5 packages red at type-check), both binding rulings verified as implemented, not assumed: DashboardEditor:231 is a genuine write GUARD (map-valued title resolves read-only, keystroke returns early — the type error dies from the guard, not a cast, with three pins including the round-trip-untouched case), and layout resolves through the spec's OWN resolveI18nLabel. The continuation agent's verification of the dead agent's wip earned its keep twice: (1) the handover was NOT green — plugin-designer type-check red on ES2022 .at(-1) under the repo's ES2020 lib, invisible to vitest, and the wip changeset's "78/78" claim was false; fixed and now true. (2) Source comments claimed a resolver-parity pin that did not exist — with 3 of 5 packages resolving via pickLocalized instead of the spec resolver, that unpinned gap was exactly ruling 2's drift scenario; the agent measured the two resolvers agree over 96/96 spec-valid inputs, then wrote the real pin (six limbs, both functions, one table, the single permitted difference pinned in both directions) and re-pointed the comments at it.

Full local ladder in lieu of CI (stacked PRs get none), quoted in the PR body: build 43/43, type-check 78/78 (73/78 at base), 3890 tests across the five packages, reverse verification with the literal harm on screen (Objects are not valid as a React child (found: object with keys {en, zh-CN})), i18n gates green, zero en drift, changeset covering all five released packages. Worktree retained at /home/user/objectui-issue-4163 for the eventual train rebase.

Part 2 (Studio authoring surface) remains a separate future card. On the #4165 ruling: route A = rebase the train onto rc.7 and re-verify; route B = migration card inserted at the train head — then the train lands in order and #6955 (the last v17 card) goes serial behind it.

---

Generated by Claude Code