Five translated leaves serve a superseded source revision on `main` — including the one #10026 measured a week ago

[yinlianghui]

Filed unassigned while implementing #11671 (the check:i18n-stale-fill gate). ⛔ Deliberately not repaired there — #11671 was re-routed from domain:services to domain:devx precisely because its deliverable is the gate/extract tooling, not any package's bundles. These five are the gate's first output, frozen in scripts/i18n-stale-fill-baseline.json with a reason each so the ratchet ships green; this card is the worklist to burn that baseline down.

What was measured

Detected by pnpm check:i18n-stale-fill at main (branch point 73f827e37), then read by hand out of the committed bundles. In each case two or more translated locales carry byte-identical text that is not the current en value — different languages do not independently produce identical prose, so neither locale translated it: both were filled from the source by --fill=default, and the source has since been revised.

#	leaf	locales	state
1	metadata-forms.generated.ts#dataset.fields.measures.helpText (platform-objects)	es-ES, ja-JP, zh-CN	promises a "certified" governance flag the source no longer mentions
2	objects.generated.ts#sys_webhook.fields.method.help (plugin-webhooks)	es-ES, ja-JP, zh-CN	serves the pre-revision enumeration GET / POST / PUT / PATCH / DELETE after the source became prose
3	objects.generated.ts#sys_webhook.pluralLabel (plugin-webhooks)	ja-JP, zh-CN	singular Webhook after the source pluralised; neither locale is a translation at all, both are Latin fills
4	objects.generated.ts#sys_http_delivery.fields.attempts.help (service-messaging)	es-ES, ja-JP	pre-#8069 fill; the source has since gained the PARKED/terminal-row clause
5	objects.generated.ts#sys_notification_subscription.fields.principal.help (service-messaging)	es-ES, ja-JP	superseded selector list, missing the owner_of:object:id and bare-email forms

Reading for #1, as the shape:

en : "Each: name, aggregate, field (optional for count), and display format/currency"
es-ES : "Each: name, aggregate, field (optional for count), display format/currency, and a “certified” governance flag"
ja-JP : (byte-identical to es-ES)
zh-CN : (byte-identical to es-ES)

⭐ Why #5 is the one worth grading first

sys_notification_subscription.fields.principal.help is the exact leaf #10026 measured on 2026-08-19 and tabulated locale by locale. #10026 was closed not_planned on 2026-08-20. The leaf is still stale today, in the same two locales, under a fully green CI — so this is a direct measurement of what the status-quo option costs over a week, rather than a prediction about it.

Note the drift is now deeper than #10026 recorded: that card measured the zh-CN leaf as a real human translation gone stale. It still is, and check:i18n-stale-fill cannot see it — a single stale locale carries no cross-locale evidence. Only the es-ES/ja-JP pair is detectable without recorded provenance. That asymmetry is the fork reported on #11671.

Repair

Per leaf: re-translate from the current source string and commit the bundle. os i18n extract will not do it — merge fills gaps only, and a present-but-stale string is not a gap (the generated bundles' own header says so). After repairing, ratchet the baseline down:

node scripts/check-i18n-stale-fill.mjs --update

The gate fails if the baseline shrinks without being updated, so a repair cannot land half-done.

Severity

No runtime break. Blast radius is admin/Setup help text in three locales, and it degrades toward confident wrong text rather than missing text — #1 and #5 actively describe capabilities the declaration no longer makes. Two of the five (#3, #4) are English sitting in a CJK bundle, so those leaves are not localised at all.

Prior art (searched before filing)

#10026 (closed not_planned) and #9672 (closed; documented the merge consequence in the extract commentary and bundle header, with the staleness detector graded explicitly OUT on appetite). Both are about the mechanism; neither repairs a leaf, and no open issue covers these five.

Refs: #11671 (the gate) · #10026 · #9672

[yinlianghui-tw]

Triage: pm:queue + domain:services, type Bug — users hit confidently wrong help text in three published locales today, so this is a user-reachable served-content defect, not an observation. Cross-domain designation (triage-assigned, per the cross-domain exception path): four of the five leaves live in services-owned packages (plugin-webhooks ×2, service-messaging ×2), one in packages/platform-objects (engine's package) — the repair is translation-text-only with zero code risk, so one PR under the services seat is the right shape rather than a two-lane split. The claim comment must declare the full file surface: the three bundle files across plugin-webhooks / service-messaging / platform-objects plus scripts/i18n-stale-fill-baseline.json, and clear the targeted in-flight check against the engine seat's claims on platform-objects (declarations band only — no overlap expected, verify at claim time).

Repair per the card: re-translate each leaf from the CURRENT source string (a human translation for the zh-CN arms, not a source fill), then node scripts/check-i18n-stale-fill.mjs --update so the ratchet shrinks with the repair. Independent of decision #12069 — these five need repairing under any outcome of that ruling.

Size/model suggestion: S–M, opus (translation quality judgement in three locales).

---

Generated by Claude Code

[os-trump]

Claim: PM loop round 1 (services seat, takeover shift)
Session: session_01UQgPSniH1GFM9ZDeGyuGUa
Branch: claude/issue-12065-stale-i18n-fill-repair
Worktree: objectstack-issue-12065
Domain: domain:services
File surface: packages/platform-objects/src/** (metadata-forms generated i18n bundle — leaf 1 only) + packages/plugins/plugin-webhooks/src/** (objects.generated bundle) + packages/services/service-messaging/src/** (objects.generated bundle) + scripts/i18n-stale-fill-baseline.json (stop on breach; explain in the report)
Container & model: S–M, translation-judgment card, mode:subagent, model: opus — tier per this round's node scripts/pm/dispatch-gates.mjs --tier <the four paths>: "no path-derived mandate"; PM sets the default judgment tier, adopting triage's suggestion.
Clause-②: no — translated help-text repair inside generated i18n bundles plus a shrink-only ratchet baseline update; no contract accept/reject behaviour changes, no public-surface change.
Serial constraints cleared: this wave's siblings touch plugin-audit/plugin-security (#12059) and cloud-connection/metadata/cli (#11882) — package-disjoint; the in-flight #11477 patch touches packages/verify only — disjoint. Cross-domain (triage-designated single-PR exception): packages/platform-objects is the engine seat's package — declaration going on the engine seat post with a veto window until merge; the dev re-verifies at claim that no domain:engine in-flight claim declares the generated-bundle band. Independent of decision #12069 per triage.

---

Generated by Claude Code