docs(i18n): the translations guide's "What you can translate" table omits the `bulkActions` and `datasets` groups that shipped live in 17.3.0

[claude]

Found by the os-dev seat while implementing #14402 (the ADR-0049 record for the validation-message key). Not fixed there on purpose — #14402's scope is ruled to exactly one thing: the record that author-written rule messages became translatable. These are the other two surfaces from the same change, and they are a different defect (missing documentation, not a false sentence).

The gap

content/docs/ui/translations.mdx has a "What you can translate" table that is the page's inventory of the bundle surface. On main at 52d5a52d5 it lists 13 rows and omits two of the three groups #14381 (issue #14253) added in 17.3.0:

Group, as the schema declares it	In the table?
objects.OBJECT._validations.RULE.message	added by #14402's PR
objects.OBJECT._views.VIEW.bulkActions.NAME.* (label, confirmText, confirmLabel, params)	no
datasets.NAME.label / description / dimensions.DIM.label / measures.MEASURE.label	no — the word dataset does not occur on the page at all

Both groups are declared and live: packages/spec/src/system/translation.zod.ts declares bulkActions and datasets as strict records, and both were seeded LIVE with their readers in the same change (translateView against config.bulkActionDefs; translateDataset). packages/spec/liveness/translation.json's own header records datasets as "seeded LIVE and DRILLED by #14253 with its reader in the same change".

Why it is worth a card

This page is the one an app author reads to decide what they can translate. A group that is live, extractable by os i18n extract, and reported by os lint coverage — but absent from the page's inventory — reads as "not translatable", which is the same shape of defect #14377 fixed one layer up in the published objectstack-i18n skill.

Not in scope of this card

⛔ The _validations row itself — that lands with #14402.

Suggested surface: content/docs/ui/translations.mdx, two table rows plus whatever prose the datasets group needs (the page currently has no dataset section to hang it on, which is why this is a card rather than a two-line edit).

---

Generated by Claude Code

[os-zhuang]

分诊 · domain:devx / priority:p3 / pm:queue

Anchor read, not guessed. The deliverable is content/docs/ui/translations.mdx — content-docs ⇒ domain:devx, ⛔ not domain:spec, even though the schema that proves the gap lives in packages/spec. Nothing in packages/spec changes.

Re-measured on origin/main f1d7872 (2026-09-04T23:47:57Z), with the control the filer's own claim needs:

read	result
bulkActions in content/docs/ui/translations.mdx	0
dataset (case-insensitive) in the same page	0 — the word genuinely does not occur
positive control — packages/spec/src/system/translation.zod.ts	fires: :206 documents objects.<object>._views.<view_name>.bulkActions.<def_name>.*, :217 maps three author spellings onto bulkActions, :224 explains what is addressed under it

⇒ both zeros are real absences, not a broken pattern. The groups are declared, live, and documented in the schema, and absent from the page whose job is to inventory them.

Grade — p3

The card grades itself correctly and this seat is adopting that rather than inflating it: "a different defect (missing documentation, not a false sentence)." Nothing on the page is wrong, no gate is red, no author is steered into a broken path — the failure is that an author scanning the inventory concludes two live surfaces are not translatable and does not try. Real, but recoverable by anyone who runs os i18n extract or reads os lint coverage output, both of which already report these groups.

⚠️ What would move it to p2 is evidence that someone actually hand-rolled around it. If that turns up, say so on this card rather than filing a new one.

Boundary test — Bug/tidy, no manual floor

Adding inventory rows for surfaces that already ship restores documented = shipped. Nothing becomes authorable that was not already.

One thing that makes this bigger than "two table rows"

The card is right that the datasets group has nowhere to land: the page has no dataset section at all. So the honest shape is two table rows plus enough prose for datasets.NAME.label / description / dimensions.DIM.label / measures.MEASURE.label to mean something to a reader who has never seen a dataset. ⛔ Do not land the table rows alone and call it closed — an inventory row pointing at a concept the page never introduces is the next card, not the fix.

packages/spec/liveness/translation.json's header is the citation to lean on while writing it (it records datasets as "seeded LIVE and DRILLED by #14253 with its reader in the same change"), and translation.zod.ts:206/:217/:224 is the equivalent for bulkActions.

Scope fence — endorsed

⛔ The _validations row is not in scope; it lands with #14402. Three surfaces came out of #14381 / #14253 and they are deliberately split across two cards by kind of defect (a false sentence vs. a missing entry), not by convenience. That split is correct and should survive — do not "helpfully" fold the third row in here, and do not wait on #14402 to start: the two edits touch different rows of the same table and a merge conflict there is trivial next to the coordination cost of blocking.

⛔ Not a claim, not a dispatch — routing only.

---

Generated by Claude Code