showcase: eight authored validation messages on showcase_account / showcase_task are not on the translation channel, so they refuse in English on a zh-CN session #14518

Activity

1. huangyiirene

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   pm:queueReady for the PM dispatch loopReady for the PM dispatch loop

   domain:engineRetired 2026-10-22, alias of domain:server (engine surface); in-flight cards keep it until they landRetired 2026-10-22, alias of domain:server (engine surface); in-flight cards keep it until they land

   i18n

   priority:p3

   on Sep 2, 2026
2. huangyiirene commented on Sep 2, 2026

   

   huangyiirene

   on Sep 2, 2026 – with Claude

   Collaborator

   More actions

   Triage — graded. Confirmed at origin/main 4a37870, with one correction to the count.

   Confirmed

   All eight rule names are where you say they are:

   • examples/app-showcase/src/data/objects/account.object.ts — :121 account_lifecycle, :138 tax_id_format, :150 billing_email_format, :162 support_config_shape, :184 churn_reason_consistency with :191 churn_reason_present and :199 churn_reason_absent.
   • examples/app-showcase/src/data/objects/task.object.ts:102 — task_status_flow.

   The channel is real and the control fires: packages/spec/src/system/i18n-resolver.ts:1863 returns `objects.${objectName}._validations.${ruleName}.message` (#14253), read by packages/objectql/src/validation/rule-validator.ts:396,2168.

   Correction — the population today is twelve, not eight

   git grep -rn "_validations" origin/main -- examples/app-showcase/ returns zero matches. Nothing in the showcase is on that channel yet.

   PR #14517 has not landed — it is open, draft, head 120d1d066, base a40c0f966. So showcase_project's four rules (end_after_start, spent_within_budget, project_status_flow, project_health_progression) are in the same position on main today as the eight you listed.

   That does not weaken the card — your eight are genuinely additional, and filing them separately rather than widening #14517 was right. But it changes two things for whoever picks this up:

   • The "mirror what PR fix(objectql,showcase): keep the state-machine refusal's facts with an authored message, and stop the New Project wizard offering statuses it refuses #14517 did" instruction has nothing to mirror yet. Take this card serially after fix(objectql,showcase): keep the state-machine refusal's facts with an authored message, and stop the New Project wizard offering statuses it refuses #14517 merges, or — if it stalls — absorb all twelve here rather than leaving four behind a draft.
   • Re-count before starting. If fix(objectql,showcase): keep the state-machine refusal's facts with an authored message, and stop the New Project wizard offering statuses it refuses #14517 has landed by then the population is your eight; if not, it is twelve.

   Scope ruled

   Add en + zh-CN _validations entries for every authored rule message on showcase_account and showcase_task, including a separate entry for each nested conditional branch — your note that a branch carries its own name and is addressed by it, while the wrapping rule's message never reaches a user, is the detail most likely to be missed, and it is correct.

   Prefer your second option for the pin: a bundle-wide check rather than extending the per-object one. There is already a lint rule in this area (packages/lint/src/validate-translation-references.ts) — establish whether it can carry "an authored validations[].message with no bundle entry" before writing a bespoke test. A per-object pin extended twice is on its way to being extended a third time, and this card exists because the first extension stopped at one object.

   Out of scope, as you framed it: examples/app-crm. You are right not to assume the CRM demo is meant to be localised at all — that is a separate question and it should not be answered by a translation PR. If someone wants it, separate card.

   Routing

   domain:engine — examples/* anchors to the subsystem it exercises (lane table), and the subsystem here is validation-rule message resolution (rule-validator.ts + the spec's i18n resolver). i18n, documentation.

   priority:p3: example-app content, no customer-facing runtime defect, and the channel already exists so nothing is blocked. It is a real card rather than nothing because the showcase is what people read to learn a correct app, and a mixed-language error envelope teaches the wrong thing — your argument, and it holds. pm:queue.

   ---

   Generated by Claude Code