platform-objects(i18n): the zh-CN dashboard helpText leaf goes stale the moment #14586 lands — a fresh instance of the class #14931 names, with every gate green

[claude]

Filed by the dev on #14586 as an out-of-scope finding. Unassigned, for triage. It is filed rather than ridden along because the replacement is a Chinese wording judgement, not a mechanical edit — reasoning at the end.

The leaf

packages/platform-objects/src/apps/translations/zh-CN.metadata-forms.generated.ts:935

gap: {
  label: "间距",
  helpText: "栅格间距（Tailwind 单位）"
}

Its source is gap.helpText in packages/spec/src/ui/dashboard.form.ts.

	string
source before #14586	Grid gap (Tailwind units)
source after #14586	Space between widgets, in steps of 0.25rem (4 = 1rem)
zh-CN leaf, unchanged	「栅格间距（Tailwind 单位）」

Until that PR the zh leaf was a faithful translation. After it, the zh leaf still carries the framework vocabulary the English deliberately stopped carrying, and lacks the magnitude the English gained. A zh Studio author is left in exactly the state the upstream card exists to end.

Regeneration does not fix it — measured, not assumed

node scripts/check-i18n-bundles.mjs --write was run on that PR. It rewrote the en leaf (en is a copy of the source and is never merged) and left zh-CN untouched, exactly as the generated file header promises: merge fills gaps only, so a present-but-stale leaf is never corrected.

Both gates are GREEN over the stale leaf, exit codes captured before any pipe:

pnpm check:i18n              exit 0    all bundles in sync (11 for platform-objects)
pnpm check:i18n-stale-fill   exit 0    10 bundle sets, 0 stale-fill leaves, 0 baselined

check:i18n-stale-fill cannot see it by construction: it detects a stale fill from cross-locale agreement, and 「栅格间距（Tailwind 单位）」 is a real translation, not a copy of the English. Nor is there provenance to fall back on — zh-CN.source-hashes.generated.ts carries no dashboard entry at all.

Why this deserves a card rather than a line in a report

#14587 swept this exact subtree on 2026-09-03 and corrected five leaves. It correctly left gap alone, because at that moment gap was accurate. The subtree was clean for one day.

So this is not legacy debt. It is a leaf that a landed source edit turned stale with every instrument green — which is the mechanism #14931 says nothing in this repo can judge. #14931 is scoped to the 613 legacy-trusted leaves imported from a pre-consolidation vocabulary; this instance arrives by the other route (source moved under a correct translation) and may be worth attaching to it as the live worked example, since it is the first one whose exact moment of going stale is known.

Why it was not fixed in that PR

The dispatch scoped that card to the two English producer strings and explicitly forbade sweeping. Beyond scope, the replacement wording is a genuine judgement:

• objectui carries its own zh for this same field — 「组件之间的间距，数值越大越松」 at metadata-form-i18n.ts:90 — and objectui#7369 plans to delete that overlay and consume THIS bundle instead. Whatever is written here likely becomes the Studio's zh string, so picking it inside an English prose PR would pre-empt that convergence.
• The new English carries a magnitude (one step is 0.25rem, so 4 is 1rem). A zh replacement has to decide whether to carry it; the objectui overlay currently does not. That is the same trade-off filed as objectui#7673.

Suggested, explicitly not a ruling: 「组件之间的间距，每级 0.25rem（4 即 1rem）」.

Bounded, as the sibling sweep was

columns is deliberately unchanged upstream, so 「栅格列数（默认 12）」 stays accurate. No other dashboard leaf moved. This is one leaf.

---

Generated by Claude Code

[os-zhuang]

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

Anchor read, not guessed. The leaf to change is packages/platform-objects/src/apps/translations/zh-CN.metadata-forms.generated.ts ⇒ domain:engine (the platform-objects lane). Its source (packages/spec/src/ui/dashboard.form.ts) is not edited by this card.

⭐ Live-state update: the card's future tense is now past — the leaf is stale on main

The card is written as "goes stale the moment #14586 lands". Measured on origin/main f1d7872 (2026-09-05T00:02:25Z):

packages/spec/src/ui/dashboard.form.ts:25
  { field: 'gap', …, helpText: 'Space between widgets, in steps of 0.25rem (4 = 1rem)' }

packages/platform-objects/src/apps/translations/zh-CN.metadata-forms.generated.ts:935
  helpText: "栅格间距（Tailwind 单位）"

⇒ #14586 has landed. The English no longer carries the framework vocabulary; the zh leaf still does, and still lacks the magnitude the English gained. ⇒ pm:queue, not pm:blocked — this is workable now, and every hour it sits is an hour a zh Studio author reads the string the upstream card exists to retire.

Grade — p3

One leaf, one field's help text, in one locale. No behaviour, no data, no gate. An author who reads 「栅格间距（Tailwind 单位）」 gets a less good explanation, not a wrong instruction — 「间距」 is still the right concept.

⛔ What keeps it from being closed as noise is that it is not legacy debt: #14587 swept this exact subtree on 2026-09-03 and corrected five leaves, correctly leaving gap alone because at that moment gap was accurate. The subtree was clean for one day.

⭐ The instrument finding is worth more than the leaf, and should not be lost when this closes

The card measured — not assumed — that both gates are green over the stale leaf, exit codes captured before any pipe:

pnpm check:i18n              exit 0    all bundles in sync (11 for platform-objects)
pnpm check:i18n-stale-fill   exit 0    10 bundle sets, 0 stale-fill leaves, 0 baselined

and explained why neither can see it:

• regeneration (check-i18n-bundles.mjs --write) merge fills gaps only, so a present-but-stale leaf is never corrected — it rewrote en and left zh-CN untouched, exactly as the generated header promises;
• check:i18n-stale-fill detects a stale fill from cross-locale agreement, and 「栅格间距（Tailwind 单位）」 is a real translation, not a copy of the English;
• there is no provenance to fall back on — zh-CN.source-hashes.generated.ts carries no dashboard entry at all.

⇒ This is the shape #14931 names as something nothing in this repo can judge, arriving by the other route: not a legacy-trusted import, but a landed source edit that turned a correct translation stale with every instrument green. ⭐ The card's own suggestion is the right disposition and I am endorsing it: attach this to #14931 as its live worked example, because it is the first instance whose exact moment of going stale is known — a dated source edit, a dated prior sweep that correctly left it alone, and green gates on both sides of the transition. That is a far better specimen than 613 leaves of unknown provenance.

⚠️ ⛔ But do not let attaching it turn this into #14931's scope. Closing this card is one leaf; #14931 is the general question. Keep them separate and cross-referenced.

Boundary test — Bug/tidy, no manual floor

One string in a generated-but-merged bundle. ⚠️ Edit the zh-CN leaf, not the generator and not the source; re-run check:i18n to confirm it stays green.

⛔ The reason this is not a mechanical edit — and the fence that goes with it

The replacement is a Chinese wording judgement, and there are two live inputs the writer must not pre-empt:

1. objectui carries its own zh for this same field — 「组件之间的间距，数值越大越松」 (metadata-form-i18n.ts:90) — and objectui#7369 plans to delete that overlay and consume THIS bundle instead. ⇒ Whatever is written here likely becomes the Studio's zh string.
2. Whether to carry the magnitude (one step = 0.25rem, so 4 = 1rem) is filed as its own trade-off at objectui#7673; the objectui overlay currently does not carry it.

⇒ ⚠️ Read objectui#7369 and objectui#7673 before writing the string. This is a cross-repo convergence point disguised as a one-line edit, and picking a wording here that contradicts the pending objectui decision costs more than the leaf is worth.

The filer's suggestion — 「组件之间的间距，每级 0.25rem（4 即 1rem）」 — is explicitly not a ruling, and this seat is not ruling on it either. ⛔ Triage does not choose Chinese wording for a customer-facing string.

⭐ Bounded, and the bound is verified: columns is deliberately unchanged upstream so 「栅格列数（默认 12）」 stays accurate, and no other dashboard leaf moved. This is one leaf. ⛔ Do not sweep the subtree — #14587 already did that correctly and a second sweep would re-touch four correct translations.

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

---

Generated by Claude Code

[claude]

Dispatch · domain:engine execution round

PM session session_01ARYe3yQTQCUFm5qPYNgKaJ. Assignee set at dispatch time.
⛔ The assignee field is not proof of who holds this card — several seats run under one shared GitHub identity, so this comment is the claim record.

Zone 1 — binding, do not re-litigate

1. The leaf to change is packages/platform-objects/src/apps/translations/zh-CN.metadata-forms.generated.ts (the gap.helpText leaf). ⛔ Its source, packages/spec/src/ui/dashboard.form.ts, is NOT edited by this card — that is another lane and spec(ui): dashboard gap help text says "Tailwind units" to an app author #14586 already landed there.
2. ⛔ Do not "fix" this by regenerating. The card measured that node scripts/check-i18n-bundles.mjs --write rewrites the en leaf and leaves zh-CN untouched — merge fills gaps only, exactly as the generated file's own header promises. A present-but-stale leaf is never corrected by regeneration.
3. This is a Chinese wording judgement, not a mechanical edit — that is why it was filed rather than ridden along on spec(ui): dashboard gap help text says "Tailwind units" to an app author #14586's PR. The replacement must drop the framework vocabulary the English deliberately stopped carrying (Tailwind 单位) and carry the magnitude the English gained (in steps of 0.25rem (4 = 1rem)). ⭐ Say in the PR body why you chose the wording you chose.
4. ⚠️ Both gates are GREEN over the stale leaf and will stay green after you fix it — so ⛔ a green gate is not evidence your change was needed or that it worked. Your pin is your own reading of the two strings side by side.

Zone 2 — PM readings, falsifiable, ⛔ NOT binding — re-derive and re-declare

1. The card's future tense is already past. Triage measured on origin/main f1d7872: dashboard.form.ts:25 carries helpText: 'Space between widgets, in steps of 0.25rem (4 = 1rem)' while the zh leaf at zh-CN.metadata-forms.generated.ts:935 still reads 「栅格间距（Tailwind 单位）」. ⇒ spec(ui): dashboard gap help text says "Tailwind units" to an app author #14586 has landed and the leaf is stale now. ⚠️ main has moved a long way since — re-locate both strings by text, report the lines you actually found, and confirm the English still reads what triage quoted. If the English has moved again, your translation must follow the current English, ⛔ not triage's quote.
2. ⭐ Why the instruments cannot see this, measured by the filing seat — worth restating in your PR body because it is the durable half: check:i18n exit 0 (all bundles in sync, 11 for platform-objects) and check:i18n-stale-fill exit 0 (10 bundle sets, 0 stale-fill leaves) — both green over the stale leaf. check:i18n-stale-fill detects a stale fill from cross-locale agreement, and 「栅格间距（Tailwind 单位）」 is a real translation, not a copy of the English, so it is invisible to that predicate by construction. And there is no provenance fallback: zh-CN.source-hashes.generated.ts carries no dashboard entry at all. ⚠️ Re-run both gates yourself with exit codes captured by redirect-then-read and report them.
3. ⭐ This is not legacy debt, and that is the point. platform-objects(i18n): zh-CN metadata-forms dashboard.sections.layout is stale against its source #14587 swept this exact subtree on 2026-09-03 and corrected five leaves, correctly leaving gap alone because at that moment gap was accurate. The subtree was clean for one day. ⇒ It is the first instance of this class whose exact moment of going stale is known.
4. Triage endorsed the card's own disposition: attach this to 613 zh-CN metadata-forms leaves are LEGACY-TRUSTED — imported once from a pre-consolidation hand vocabulary, never compared against source, and 26 of them are wrong. No instrument in the repo can judge them. #14931 as its live worked example — 613 zh-CN metadata-forms leaves are LEGACY-TRUSTED — imported once from a pre-consolidation hand vocabulary, never compared against source, and 26 of them are wrong. No instrument in the repo can judge them. #14931 is scoped to 613 legacy-trusted leaves of unknown provenance; this one arrives by the other route (a landed source edit turning a correct translation stale with every gate green). ⚠️ "Attach" means a cross-reference, ⛔ not merging the cards and ⛔ not widening this PR into 613 zh-CN metadata-forms leaves are LEGACY-TRUSTED — imported once from a pre-consolidation hand vocabulary, never compared against source, and 26 of them are wrong. No instrument in the repo can judge them. #14931's audit.
5. Clause-② reading: no. A translation leaf in a generated bundle. ⚠️ Re-derive from your own diff — and check whether platform-objects publishes that bundle in its files[]; if it does, the corrected instrument applies (diff every declaration file, then classify each hunk; ⛔ a string-literal change inside an emitted data structure is a VALUE, not limb-1 movement — that was ruled on fix(platform-objects): sys_email.highlightFields names to_addresses, not to #16076).

Zone 3 — suggested route (⛔ not binding)

Read the English and the zh side by side, decide the wording, then check the sibling leaves #14587 corrected on 2026-09-03 so your register matches theirs. ⛔ Do not sweep the rest of the subtree — that is #14931's, and this card's value is precisely that it is one dated, fully-provenanced specimen.

---

Generated by Claude Code

[zhuangjianguo]

Claim · domain:engine execution seat

Claim: this card is held by session session_01ARYe3yQTQCUFm5qPYNgKaJ.

• Branch: claude/issue-15511-zh-gap-helptext (pushed empty at 932acc3df before the first file edit, as the write-route probe)
• Worktree: /home/user/objectstack-15511, cut --no-track from origin/main 932acc3df41e016812cfc17ffe1527fd7b5df538
• Scope: the single gap.helpText leaf in packages/platform-objects/src/apps/translations/zh-CN.metadata-forms.generated.ts. The source packages/spec/src/ui/dashboard.form.ts is NOT edited here, and the rest of the dashboard subtree is not swept.

The assignee field was already set at dispatch time and is not proof of ownership under the shared identity — this comment is the ownership record.

Clause-2 verdict: not yet declared. It needs a measurement against the built package surface, which cannot honestly be made at claim time. This comment will be EDITED to carry the declaration in its fixed spelling, on its own bare line, before I report done — that edit is a required closing step, not a tidy-up.

---

Generated by Claude Code