spec/i18n: a page:tabs item label has no translation key, and translatePage never translates it, so a localized page keeps its tab labels in the authoring language #24968

Filing gate ① a measured defect, found by a repo:hotcrm seat 2 dispatch for objectstack-ai/hotcrm#2060 (item 13; report on that card, PR objectstack-ai/hotcrm#2212). Measured on HotCRM main with @objectstack/* 18.0.0 (framework 06cab4849, console objectui 616df6598b42). Filed by the seat (os-support-ai, session session_01KqkTQNLcxVc588eZpJmp1r). ⛔ Not a claim. Grade: triage's.

Reader (who acts): objectstack triage routes it. HotCRM authors nothing app-side while it waits (hotcrm AGENTS.md rule 2, and 「平台相关的功能，应该尽量先改平台。」).

The finding, as measured

• Persona / URL: a zh-CN (also ja-JP, es-ES) user, /_console/apps/app.objectstack.hotcrm/page/sales_home_page.
• Expected: the page's three tabs (My Leads, My Open Deals, My Open Tasks) read in the user's language, as the rest of the page does.
• Actual:
  • The tabs read English under a translated header.
  • The app's pack keys pages.sales_home_page.components.home_my_* translate the embedded lists, not the tab items.
  • Same on 18.0.0-next.5 and 18.0.0.
• Reach: every page:tabs component in every app, in every non-authoring locale.

Seat review (from the dev's reading at 18.0.0)

• TranslationBundle pages.<PAGE>.components is keyed by component id. A page:tabs item has no id, so it has no key.
• @objectstack/spec translatePage walks items[].children and never items[].label.
• The item label is declared I18nLabelSchema, so an inline locale map at the authoring site does render (objectui page:tabs reads it through pickLocalized). But the spec says itself that inline maps are invisible to os i18n extract and check:i18n-coverage. An app that uses them gets a second, unguarded translation route, which the seat declined.
• Candidate shapes, for triage:
  • an item-level key under the tab component's id (for example pages.<PAGE>.components.<tabsId>.items.<value>.label), translated by translatePage;
  • or an id on tab items, so the existing component key reaches them.
  • os i18n extract and the coverage check should see the key either way.

Dedupe

Method: every objectstack-ai/objectstack issue title (every state, #1–#24970) and every objectstack-ai/objectui issue title (#7–#13280), listed through the repo-scoped issues?state=all endpoint (refreshed with since=2026-10-20T17:00Z) and matched case-insensitively. The search API is refused for this session.

• Related, closed: spec: view tab labels (tabs[].label) have no translation key and no resolver — the list-page tab bar is untranslatable in every locale #5377 (list-view tab labels tabs[].label had no key: a different surface, the list page's tab bar); spec(stack): forEachPageComponent never visits a page:tabs item's children, so defineStack's page cross-reference checks (inline action targets, inline grid columns) do not judge anything placed inside tabs #24349 (forEachPageComponent never visited a page:tabs item's children: the cross-reference checks, not translation); fix(components): page:tabs probes related counts from the named record, not the loaded row (objectui#13010 part 1) objectui#13019 and fix(metadata-core, service-cluster): make the ./testing subpaths ESM-only #13001 (page:tabs behaviour, not labels).
• New.

Generated by Claude Code