[baozhoutao]

Refs #25176

Clause-②: no
Metadata-protocol: none

What

Setup → People & Organization carries nav_organization (the active organization's record page) and nav_organizations (the organization list, shown where org-scoping is mounted). Both translated to 「组织」 in zh-CN and 「組織」 in ja-JP, so a multi-organization deployment showed two identical entries that open different pages.

• zh-CN: 「当前组织」 / 「所有组织」
• ja-JP: 「現在の組織」 / 「すべての組織」
• New setup-nav-distinct-labels.test.ts: fails when two entries in one Setup nav group read the same in any shipped locale (en / zh-CN / ja-JP / es-ES). Verified red on the old translations, green after.
• patch changeset for @objectstack/platform-objects.

Only translated-locale values change; no translation keys are added or dropped, and the English source (and so the source hashes) is unchanged.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RDdLaUJMtzFXcrF3gyzpJD

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 1 name(s) were too generic to anchor anything (single lowercase words)
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 3 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 72a302a9dde3347e15a971c5da28df205496a217 → packageMentionDocs.