@object-ui/i18n 17.6.0 → 17.7.0

package/dist/useObjectLabel.d.ts

@@ -100,15 +100,17 @@ export declare function useObjectLabel(): {
      * reaches this client — so nav labels arrive already localized. One
      * owner, not two. To translate a sidebar group, translate it there.
      *
-     * History (objectui#5197): until then this docstring promised
+     * History (`9c60144b5`): until then this docstring promised
      * `"Sales" → "销售"` for sidebar groups, and `NavigationRenderer`
      * accepted `resolveGroupLabel`/`resolveItemLabel` to wire it up. Those
      * props could never fire — the renderer's `isCustomized` guard compared a
      * node's authored label against its own `id` (`Workspace` vs
      * `grp_workspace`), which never match, so the guard was true for every
-     * real entry. The props are gone; the promise was false, not merely
-     * unused. This helper is kept as a plain key reader for a consumer that
-     * renders navigation itself — it has no first-party caller.
+     * real entry. The props are gone, and so is the guard itself
+     * (objectui#11201: the renderer no longer matches a label's text against
+     * any name); the promise was false, not merely unused. This helper is kept
+     * as a plain key reader for a consumer that renders navigation itself — it
+     * has no first-party caller.
      */
     navGroupLabel: (appName: string, groupId: string, fallback: string) => string;
     /**
@@ -194,11 +196,6 @@ export declare function useObjectLabel(): {
      * that spells the prefix out does not resolve (see `viewSuffixes`).
      */
     viewLabel: (objectName: string, viewName: string, fallback: string) => string;
-    /**
-     * Resolve translated list-view description.
-     * Convention: `{ns}.objects.{objectName}._views.{viewName}.description`.
-     */
-    viewDescription: (objectName: string, viewName: string, fallback?: string) => string | undefined;
     /**
      * Resolve translated list-view emptyState. Returns a {title, message}
      * tuple with each field independently translated. Convention:
@@ -241,6 +238,20 @@ export declare function useObjectLabel(): {
      * falling back to `{ns}.globalActions.{actionName}.successMessage`.
      */
     actionSuccess: (objectName: string | undefined, actionName: string, fallback?: string) => string | undefined;
+    /**
+     * Resolve the translated success copy for ONE handler outcome — an entry of
+     * the action's `outcomeMessages` (`@objectstack/spec` 17.6.0, objectui#11344).
+     * Convention: `{ns}.objects.{objectName}._actions.{actionName}.outcomeMessages.{outcome}`,
+     * falling back to `{ns}.globalActions.{actionName}.outcomeMessages.{outcome}`
+     * — the address the spec's translation bundle declares for the key.
+     * Returns undefined when no translation and no fallback exist.
+     *
+     * Like `actionSuccess`, the answer is a TEMPLATE: a `${result.*}` token in a
+     * bundle entry passes through untouched (i18next interpolates its own
+     * `{{…}}` form, never `${…}`), and the action runner fills it in from the
+     * handler's answer once the action has run.
+     */
+    actionOutcome: (objectName: string | undefined, actionName: string, outcome: string, fallback?: string) => string | undefined;
     /**
      * Resolve translated action description (the explanatory line shown in the
      * action's param dialog / sheet / drawer header).
@@ -360,15 +371,17 @@ export declare function useSafeFieldLabel(): {
      * reaches this client — so nav labels arrive already localized. One
      * owner, not two. To translate a sidebar group, translate it there.
      *
-     * History (objectui#5197): until then this docstring promised
+     * History (`9c60144b5`): until then this docstring promised
      * `"Sales" → "销售"` for sidebar groups, and `NavigationRenderer`
      * accepted `resolveGroupLabel`/`resolveItemLabel` to wire it up. Those
      * props could never fire — the renderer's `isCustomized` guard compared a
      * node's authored label against its own `id` (`Workspace` vs
      * `grp_workspace`), which never match, so the guard was true for every
-     * real entry. The props are gone; the promise was false, not merely
-     * unused. This helper is kept as a plain key reader for a consumer that
-     * renders navigation itself — it has no first-party caller.
+     * real entry. The props are gone, and so is the guard itself
+     * (objectui#11201: the renderer no longer matches a label's text against
+     * any name); the promise was false, not merely unused. This helper is kept
+     * as a plain key reader for a consumer that renders navigation itself — it
+     * has no first-party caller.
      */
     navGroupLabel: (appName: string, groupId: string, fallback: string) => string;
     /**
@@ -454,11 +467,6 @@ export declare function useSafeFieldLabel(): {
      * that spells the prefix out does not resolve (see `viewSuffixes`).
      */
     viewLabel: (objectName: string, viewName: string, fallback: string) => string;
-    /**
-     * Resolve translated list-view description.
-     * Convention: `{ns}.objects.{objectName}._views.{viewName}.description`.
-     */
-    viewDescription: (objectName: string, viewName: string, fallback?: string) => string | undefined;
     /**
      * Resolve translated list-view emptyState. Returns a {title, message}
      * tuple with each field independently translated. Convention:
@@ -501,6 +509,20 @@ export declare function useSafeFieldLabel(): {
      * falling back to `{ns}.globalActions.{actionName}.successMessage`.
      */
     actionSuccess: (objectName: string | undefined, actionName: string, fallback?: string) => string | undefined;
+    /**
+     * Resolve the translated success copy for ONE handler outcome — an entry of
+     * the action's `outcomeMessages` (`@objectstack/spec` 17.6.0, objectui#11344).
+     * Convention: `{ns}.objects.{objectName}._actions.{actionName}.outcomeMessages.{outcome}`,
+     * falling back to `{ns}.globalActions.{actionName}.outcomeMessages.{outcome}`
+     * — the address the spec's translation bundle declares for the key.
+     * Returns undefined when no translation and no fallback exist.
+     *
+     * Like `actionSuccess`, the answer is a TEMPLATE: a `${result.*}` token in a
+     * bundle entry passes through untouched (i18next interpolates its own
+     * `{{…}}` form, never `${…}`), and the action runner fills it in from the
+     * handler's answer once the action has run.
+     */
+    actionOutcome: (objectName: string | undefined, actionName: string, outcome: string, fallback?: string) => string | undefined;
     /**
      * Resolve translated action description (the explanatory line shown in the
      * action's param dialog / sheet / drawer header).

package/dist/useObjectLabel.js

@@ -242,8 +242,8 @@ export function useObjectLabel() {
          * name under `_views` — the runtime view identity's own name, stripped of the
          * object prefix. That single spelling is canonical per the objectstack#5164
          * ruling A (2026-08-06): the i18n extractor asks the view composer for the key
-         * (objectstack#6124) and `packages/lint` enforces exactly that spelling
-         * (objectstack#6038), so this resolver accepts exactly what those produce.
+         * (objectstack `b3c1f3cd5`) and `packages/lint` enforces exactly that spelling
+         * (objectstack `7618ee814`), so this resolver accepts exactly what those produce.
          *
          * Deliberately NOT a second candidate: the prefixed full name
          * (`_views.<objectName>.<viewName>`). Accepting it made this client more
@@ -328,15 +328,17 @@ export function useObjectLabel() {
              * reaches this client — so nav labels arrive already localized. One
              * owner, not two. To translate a sidebar group, translate it there.
              *
-             * History (objectui#5197): until then this docstring promised
+             * History (`9c60144b5`): until then this docstring promised
              * `"Sales" → "销售"` for sidebar groups, and `NavigationRenderer`
              * accepted `resolveGroupLabel`/`resolveItemLabel` to wire it up. Those
              * props could never fire — the renderer's `isCustomized` guard compared a
              * node's authored label against its own `id` (`Workspace` vs
              * `grp_workspace`), which never match, so the guard was true for every
-             * real entry. The props are gone; the promise was false, not merely
-             * unused. This helper is kept as a plain key reader for a consumer that
-             * renders navigation itself — it has no first-party caller.
+             * real entry. The props are gone, and so is the guard itself
+             * (objectui#11201: the renderer no longer matches a label's text against
+             * any name); the promise was false, not merely unused. This helper is kept
+             * as a plain key reader for a consumer that renders navigation itself — it
+             * has no first-party caller.
              */
             navGroupLabel: (appName, groupId, fallback) => resolve(`apps.${appName}.navigation.${groupId}.label`, fallback),
             /**
@@ -422,15 +424,27 @@ export function useObjectLabel() {
              * that spells the prefix out does not resolve (see `viewSuffixes`).
              */
             viewLabel: (objectName, viewName, fallback) => resolve(viewSuffixes(objectName, viewName, 'label'), fallback),
-            /**
-             * Resolve translated list-view description.
-             * Convention: `{ns}.objects.{objectName}._views.{viewName}.description`.
+            /*
+             * There is deliberately NO `viewDescription` member here, and no
+             * `{ns}.objects.{objectName}._views.{viewName}.description` convention for
+             * it to resolve (objectui#7219, maintainer ruling 2026-09-02, option B).
+             *
+             * A list view's description has exactly ONE channel: the `I18nLabel` value
+             * authored on the view entry -- a string or an inline locale map -- which
+             * `ObjectView` relays and the render site resolves with `pickLocalized`
+             * (objectui#7199). The catalog key used to be declared and resolved right
+             * here, between its two wired-up siblings, but had zero callers and zero
+             * in-repo bundle usage: a bundle entry written under it reached no screen.
+             *
+             * Wiring it in instead was weighed and NOT taken -- two vocabularies for
+             * one concept plus a precedence rule is the ambiguity, not the fix. Leaving
+             * it declared and unfulfilled was not taken either; the standing rule is
+             * remove, not phase out, when a surface has measured zero use.
+             *
+             * `viewSuffixes` is NOT retired with it: `viewLabel` above and
+             * `viewEmptyState` below share that helper and keep resolving. Only the
+             * `'description'` tail passed to it is gone.
              */
-            viewDescription: (objectName, viewName, fallback) => {
-                const fb = fallback ?? '';
-                const resolved = resolve(viewSuffixes(objectName, viewName, 'description'), fb);
-                return resolved || undefined;
-            },
             /**
              * Resolve translated list-view emptyState. Returns a {title, message}
              * tuple with each field independently translated. Convention:
@@ -483,6 +497,24 @@ export function useObjectLabel() {
                 const resolved = resolve(actionSuffixes(objectName, actionName, 'successMessage'), fb);
                 return resolved || undefined;
             },
+            /**
+             * Resolve the translated success copy for ONE handler outcome — an entry of
+             * the action's `outcomeMessages` (`@objectstack/spec` 17.6.0, objectui#11344).
+             * Convention: `{ns}.objects.{objectName}._actions.{actionName}.outcomeMessages.{outcome}`,
+             * falling back to `{ns}.globalActions.{actionName}.outcomeMessages.{outcome}`
+             * — the address the spec's translation bundle declares for the key.
+             * Returns undefined when no translation and no fallback exist.
+             *
+             * Like `actionSuccess`, the answer is a TEMPLATE: a `${result.*}` token in a
+             * bundle entry passes through untouched (i18next interpolates its own
+             * `{{…}}` form, never `${…}`), and the action runner fills it in from the
+             * handler's answer once the action has run.
+             */
+            actionOutcome: (objectName, actionName, outcome, fallback) => {
+                const fb = fallback ?? '';
+                const resolved = resolve(actionSuffixes(objectName, actionName, `outcomeMessages.${outcome}`), fb);
+                return resolved || undefined;
+            },
             /**
              * Resolve translated action description (the explanatory line shown in the
              * action's param dialog / sheet / drawer header).

package/dist/useSafeTranslation.js

@@ -6,21 +6,38 @@
  * returning raw i18n keys — and, for a key the `defaults` map does not carry,
  * to the call site's own inline `t(key, { defaultValue })` (objectui#3865).
  * The lookup order is i18next's, so a provider-less host and a provider-mounted
- * one render the same string: `defaults[key]` (the pack value's stand-in here)
+ * one render the same string: `defaults[key_<category>]` for a numeric `count`
+ * (objectui#11445), then `defaults[key]` (the pack value's stand-in here)
  * -> `defaultValue` -> the key.
  *
  * @param defaults - Fallback English translations keyed by i18n key
  * @param testKey - A key to test if i18n is properly configured (must be in defaults)
  */
 import { useObjectTranslation } from './provider.js';
+import { DEFAULT_VALUE_OPTION, interpolateFallback } from './fallbackInterpolation.js';
 /**
- * The i18next option that names the string to use when the lookup misses.
+ * The plural rules the defaults tables are written in. Every table is English
+ * (the `en` pack's stand-in), so English selects the slot.
+ */
+const DEFAULTS_PLURAL_RULES = new Intl.PluralRules('en');
+/**
+ * The `defaults` row a count family answers from, the way i18next walks a pack
+ * (objectui#11445): `key_<category>` first, then the base `key`.
  *
- * It is a LOOKUP CONTROL, not interpolation data (objectui#3865): it chooses
- * which string is rendered, so it must never also be spliced into a
- * `{{defaultValue}}` hole in the string it chose — or in any other.
+ * i18next plural-selects only for a NUMERIC `count` (`needsPluralHandling` in
+ * i18next 26 is `count !== undefined && !isString(count)`), so a string count
+ * reads the base row on both paths. `_zero` is not looked up: no English row
+ * spells one, because `en` selects no `zero` category.
  */
-const DEFAULT_VALUE_OPTION = 'defaultValue';
+function defaultsRowFor(defaults, key, options) {
+    const count = options?.count;
+    if (typeof count === 'number' && Number.isFinite(count)) {
+        const slot = defaults[`${key}_${DEFAULTS_PLURAL_RULES.select(count)}`];
+        if (slot)
+            return slot;
+    }
+    return defaults[key];
+}
 export function createSafeTranslation(defaults, testKey) {
     // Factory-level fallback: one stable reference per defaults map, so
     // downstream useMemo/useCallback deps don't invalidate every render in
@@ -47,43 +64,24 @@ export function createSafeTranslation(defaults, testKey) {
         // `string`, and i18next itself declines a `null` default. `||` (not `??`)
         // keeps the whole chain consistent with the pre-existing `defaults[key] ||`
         // step: an empty string at any position falls through to the next.
+        //
+        // A count family's suffixed rows are reached here too (objectui#11445):
+        // `t('detail.replyCount', { count: 3 })` reads `detail.replyCount_other`
+        // before the base row, exactly as i18next reads the `en` pack. Before that
+        // card a family's `_one` / `_other` rows were unreachable on this path, so
+        // the code-selected `xxxCountOne` pairs were the only way a provider-less
+        // host rendered "1 reply" — the card retired those pairs.
         const inlineDefault = options?.[DEFAULT_VALUE_OPTION];
-        let value = defaults[key] || (typeof inlineDefault === 'string' ? inlineDefault : '') || key;
-        if (options) {
-            for (const [k, v] of Object.entries(options)) {
-                // Reserved: see DEFAULT_VALUE_OPTION. Skipped whatever its type, so an
-                // ignored non-string default cannot re-enter through this loop.
-                //
-                // This is the one deliberate divergence from i18next on this path, and
-                // it is unreachable with today's strings: i18next passes the whole
-                // options object to its interpolator, so it WOULD render
-                // `'Fallback: {{defaultValue}}'` as `'Fallback: INLINE'` (measured on
-                // 26.3.6) — but no value in this repo spells that hole (zero hits for
-                // `{{defaultValue` across packages/apps/examples), and splicing a
-                // fallback string into a hole named after itself has no sensible
-                // reading. The alternative — letting a call site's fallback text leak
-                // into an unrelated table value — is the worse of the two.
-                if (k === DEFAULT_VALUE_OPTION)
-                    continue;
-                // `split(needle).join(value)` — deliberately not `replace`, and not
-                // `replaceAll` either (objectui#3418). This path must agree with
-                // i18next, which serves the *provider* path; any divergence is a
-                // silent fork that only shows up on provider-less hosts, where we are
-                // least likely to see it:
-                //   1. `replace` with a string needle substitutes only the FIRST
-                //      occurrence. i18next substitutes every one, so a sentence that
-                //      repeats a placeholder ("Selected {{count}} of {{count}} items"
-                //      — natural in many locales, and often required by RTL /
-                //      agglutinative word order) leaked literal braces to users.
-                //   2. `replace` AND `replaceAll` both interpret `$&`, `` $` ``, `$'`
-                //      and `$$` in the *replacement* string. i18next does not. Values
-                //      here are runtime data — record labels, search terms — so this
-                //      one is reachable today, unlike (1).
-                // split/join is literal on both sides, which is exactly i18next's
-                // behaviour, and needs no regex escaping of the placeholder name.
-                value = value.split(`{{${k}}}`).join(String(v));
-            }
-        }
+        let value = defaultsRowFor(defaults, key, options) ||
+            (typeof inlineDefault === 'string' ? inlineDefault : '') ||
+            key;
+        // The interpolation itself lives in `fallbackInterpolation.ts` — ONE
+        // function, shared with `useObjectTranslation`'s not-ready path
+        // (objectui#6219). Both provider-less renderers therefore fill exactly
+        // the `{{name}}` spelling objectui#3512 holds the copy to, and the
+        // reserved-name rule for `defaultValue` (objectui#3865) is stated once.
+        // The behaviour pinned by `useSafeTranslation.test.tsx` is unchanged.
+        value = interpolateFallback(value, options);
         return value;
     };
     return function useSafeTranslation() {

package/dist/utils/formatting.d.ts

@@ -2,6 +2,17 @@
  * @object-ui/i18n - Date and currency formatting utilities
  *
  * Uses the native Intl API for locale-aware formatting.
+ *
+ * Every date helper below reads a string through `toDisplayDate`
+ * (`@object-ui/core`), the one parse step behind the date faces
+ * (objectui#10110, objectui#10183). The engine's own parse reads a date-only
+ * `2026-09-01` as UTC midnight, so each helper named August 31st for every
+ * viewer west of UTC (objectui#10866). The shared step tells the two shapes
+ * apart by the value: a date-only string is rebuilt at local midnight of the
+ * day it names, and a value with a time part keeps its instant. It also
+ * refuses a day its month does not have (`2026-02-30`, objectui#10026), which
+ * each helper then renders as the raw string, its face for any unparsable
+ * value.
  */
 export interface DateFormatOptions {
     locale?: string;
@@ -33,6 +44,11 @@ export declare function formatDate(date: Date | string | number, options?: DateF
 export declare function formatDateTime(date: Date | string | number, options?: DateFormatOptions): string;
 /**
  * Format a relative time (e.g., "2 days ago", "in 3 hours")
+ *
+ * A date-only value counts from now to the START of the day it names (local
+ * midnight), the same distance in every zone at the same wall-clock time.
+ * An unparsable value comes back as its string, as it does from
+ * {@link formatDate}; `Intl.RelativeTimeFormat` would throw on it.
  */
 export declare function formatRelativeTime(date: Date | string | number, locale?: string): string;
 /**

package/dist/utils/formatting.js

@@ -2,13 +2,25 @@
  * @object-ui/i18n - Date and currency formatting utilities
  *
  * Uses the native Intl API for locale-aware formatting.
+ *
+ * Every date helper below reads a string through `toDisplayDate`
+ * (`@object-ui/core`), the one parse step behind the date faces
+ * (objectui#10110, objectui#10183). The engine's own parse reads a date-only
+ * `2026-09-01` as UTC midnight, so each helper named August 31st for every
+ * viewer west of UTC (objectui#10866). The shared step tells the two shapes
+ * apart by the value: a date-only string is rebuilt at local midnight of the
+ * day it names, and a value with a time part keeps its instant. It also
+ * refuses a day its month does not have (`2026-02-30`, objectui#10026), which
+ * each helper then renders as the raw string, its face for any unparsable
+ * value.
  */
+import { toDisplayDate } from '@object-ui/core';
 /**
  * Format a date according to locale conventions
  */
 export function formatDate(date, options = {}) {
     const { locale = 'en', style = 'medium' } = options;
-    const d = date instanceof Date ? date : new Date(date);
+    const d = toDisplayDate(date);
     if (isNaN(d.getTime())) {
         return String(date);
     }
@@ -28,7 +40,7 @@ export function formatDate(date, options = {}) {
  */
 export function formatDateTime(date, options = {}) {
     const { locale = 'en', style = 'medium' } = options;
-    const d = date instanceof Date ? date : new Date(date);
+    const d = toDisplayDate(date);
     if (isNaN(d.getTime())) {
         return String(date);
     }
@@ -42,9 +54,17 @@ export function formatDateTime(date, options = {}) {
 }
 /**
  * Format a relative time (e.g., "2 days ago", "in 3 hours")
+ *
+ * A date-only value counts from now to the START of the day it names (local
+ * midnight), the same distance in every zone at the same wall-clock time.
+ * An unparsable value comes back as its string, as it does from
+ * {@link formatDate}; `Intl.RelativeTimeFormat` would throw on it.
  */
 export function formatRelativeTime(date, locale = 'en') {
-    const d = date instanceof Date ? date : new Date(date);
+    const d = toDisplayDate(date);
+    if (isNaN(d.getTime())) {
+        return String(date);
+    }
     const now = new Date();
     const diffMs = d.getTime() - now.getTime();
     const diffSec = Math.round(diffMs / 1000);

package/dist/utils/spec-formatters.d.ts

@@ -5,29 +5,6 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
-/**
- * @object-ui/i18n - locale formatting helpers
- *
- * ## Provenance of the four shapes below (objectui#4597)
- *
- * They were authored against `@objectstack/spec/ui`, which exported
- * `PluralRuleSchema`, `DateFormatSchema`, `NumberFormatSchema` and
- * `LocaleConfigSchema` up to and including 17.0.0-rc.5. The pinned
- * 17.0.0-rc.6 removed all four under ADR-0049 enforce-or-remove
- * (objectstack#5055, maintainer ruling 2026-08-06): they carried no key on any
- * authorable shape and nothing ever parsed them, so the vocabulary was retired
- * rather than given a door. The key sets here were faithful to the retired
- * schemas — this is a retirement, not a drift.
- *
- * Nothing in the pinned protocol models locale formatting today, so the
- * interfaces below are declarations this package owns outright, not a view onto
- * a protocol type. The retirement note records that localisation returns as
- * authorable metadata through a new ADR — "the formatter that reads a
- * LocaleConfig first, the vocabulary second" — so re-derive these at that point
- * instead of assuming they still track anything upstream.
- *
- * @module spec-formatters
- */
 /**
  * Plural forms for a single translation key, in CLDR categories.
  *
@@ -83,6 +60,19 @@ export interface SpecDateFormat {
 /**
  * Format a date using a {@link SpecDateFormat} configuration.
  *
+ * A string is read through `toDisplayDate` (`@object-ui/core`), the one parse
+ * step behind the date faces (objectui#10866): a date-only `2026-09-01` names
+ * a calendar day and is rebuilt at local midnight of that day, while a value
+ * with a time part keeps its instant. The engine's own parse read the
+ * date-only form as UTC midnight, so it named August 31st west of UTC, and
+ * for every viewer once `timeZone` was west of UTC.
+ *
+ * `timeZone` therefore applies to an instant only. A date-only value carries
+ * no instant for a zone to place, and the local midnight the shared step
+ * built reads back as its day only in the local zone, so it is formatted
+ * there. A value the shared step refuses, such as a day its month does not
+ * have (objectui#10026), comes back as its string.
+ *
  * @example
  * ```ts
  * formatDateSpec(new Date(), {

package/dist/utils/spec-formatters.js

@@ -5,6 +5,30 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
+/**
+ * @object-ui/i18n - locale formatting helpers
+ *
+ * ## Provenance of the four shapes below (objectui#4597)
+ *
+ * They were authored against `@objectstack/spec/ui`, which exported
+ * `PluralRuleSchema`, `DateFormatSchema`, `NumberFormatSchema` and
+ * `LocaleConfigSchema` up to and including 17.0.0-rc.5. The pinned
+ * 17.0.0-rc.6 removed all four under ADR-0049 enforce-or-remove
+ * (objectstack#5055, maintainer ruling 2026-08-06): they carried no key on any
+ * authorable shape and nothing ever parsed them, so the vocabulary was retired
+ * rather than given a door. The key sets here were faithful to the retired
+ * schemas — this is a retirement, not a drift.
+ *
+ * Nothing in the pinned protocol models locale formatting today, so the
+ * interfaces below are declarations this package owns outright, not a view onto
+ * a protocol type. The retirement note records that localisation returns as
+ * authorable metadata through a new ADR — "the formatter that reads a
+ * LocaleConfig first, the vocabulary second" — so re-derive these at that point
+ * instead of assuming they still track anything upstream.
+ *
+ * @module spec-formatters
+ */
+import { isRealCalendarDate, toDisplayDate } from '@object-ui/core';
 /**
  * Resolve a plural form based on count, following CLDR plural rules.
  * Uses the Intl.PluralRules API for correct locale-aware pluralization.
@@ -38,6 +62,19 @@ export function resolvePlural(rule, count, locale = 'en') {
 /**
  * Format a date using a {@link SpecDateFormat} configuration.
  *
+ * A string is read through `toDisplayDate` (`@object-ui/core`), the one parse
+ * step behind the date faces (objectui#10866): a date-only `2026-09-01` names
+ * a calendar day and is rebuilt at local midnight of that day, while a value
+ * with a time part keeps its instant. The engine's own parse read the
+ * date-only form as UTC midnight, so it named August 31st west of UTC, and
+ * for every viewer once `timeZone` was west of UTC.
+ *
+ * `timeZone` therefore applies to an instant only. A date-only value carries
+ * no instant for a zone to place, and the local midnight the shared step
+ * built reads back as its day only in the local zone, so it is formatted
+ * there. A value the shared step refuses, such as a day its month does not
+ * have (objectui#10026), comes back as its string.
+ *
  * @example
  * ```ts
  * formatDateSpec(new Date(), {
@@ -48,15 +85,17 @@ export function resolvePlural(rule, count, locale = 'en') {
  * ```
  */
 export function formatDateSpec(date, format, locale = 'en') {
-    const d = date instanceof Date ? date : new Date(date);
+    const d = toDisplayDate(date);
     if (isNaN(d.getTime()))
         return String(date);
+    // The value's shape tells the two apart, the same test the shared step makes.
+    const dateOnly = typeof date === 'string' && isRealCalendarDate(date);
     const options = {};
     if (format.dateStyle)
         options.dateStyle = format.dateStyle;
     if (format.timeStyle)
         options.timeStyle = format.timeStyle;
-    if (format.timeZone)
+    if (format.timeZone && !dateOnly)
         options.timeZone = format.timeZone;
     if (format.hour12 !== undefined)
         options.hour12 = format.hour12;

package/dist/utils/spec-translations.d.ts

@@ -50,9 +50,22 @@ export interface SpecTranslationData {
 /**
  * Detect whether the given record uses the spec `TranslationData` format.
  *
- * Returns `true` when `data.objects` exists and at least one entry has a
- * nested `fields` object (the distinguishing trait vs. an already-flattened
- * namespace tree).
+ * Returns `true` when the payload carries at least one spec translation group
+ * (see {@link SPEC_TRANSLATION_GROUPS}) whose value is an object — every spec
+ * group is a record or an object. A bundle is recognised by ANY group it
+ * carries: one that translates only object labels, apps, pages, dashboards or
+ * flows, with no field label anywhere, is as much a spec payload as one that
+ * translates fields (objectui#10235 — this used to require an
+ * `objects.<n>.fields` entry, and such a bundle was returned untransformed and
+ * read by nothing).
+ *
+ * What stays `false` is the other shape the console's loader accepts: an
+ * i18next resource tree that is already namespaced, as a mock or local-dev
+ * server may return it. Its top-level keys are namespace names — a built-in
+ * pack namespace such as `common`, an app namespace such as `crm`, or `app`,
+ * the one {@link transformSpecTranslations} itself emits — and none of them
+ * is a spec group, so feeding the transform's output back in never wraps it
+ * twice. A group-named key holding a string or an array is not a group either.
  */
 export declare function isSpecTranslationData(data: Record<string, unknown> | null | undefined): data is SpecTranslationData;
 /**

package/dist/utils/spec-translations.js

@@ -23,25 +23,64 @@
  * console transform forgets to copy it, leaving lookups to fall back to the
  * untranslated source label.
  */
+/**
+ * The top-level groups of the translation document the server serves at
+ * `/api/v1/i18n/translations/:locale` — the keys of the `translations` shape
+ * of `@objectstack/spec`'s `GetTranslationsResponseSchema`: every per-app
+ * `TranslationData` group plus the platform-only `settings`, because the
+ * served document is the merge of the app's bundle and the platform's.
+ *
+ * Written out rather than imported: `@object-ui/i18n` deliberately does not
+ * depend on `@objectstack/spec`. The console does, so the pin lives beside
+ * its loader — `apps/console/src/loadLanguage.test.tsx` walks the spec's own
+ * key list and requires a payload carrying any one group, alone, to take the
+ * transform branch. A group the spec adds and this list lacks turns that test
+ * red instead of dropping the group's bundles silently (objectui#10235).
+ */
+const SPEC_TRANSLATION_GROUPS = [
+    'objects',
+    'apps',
+    'messages',
+    'globalActions',
+    'dashboards',
+    'datasets',
+    'pages',
+    'flows',
+    'settings',
+    'metadataForms',
+    'settingsCommon',
+    // `@objectstack/spec` 17.6.0 serves `picklists` (objectstack `addbbf02`, the
+    // `picklist` metadata kind); added at that bump (objectui#11438). The
+    // transform below copies it through onto `app` like any other group.
+    'picklists',
+];
+function isPlainObject(value) {
+    return typeof value === 'object' && value !== null && !Array.isArray(value);
+}
 /**
  * Detect whether the given record uses the spec `TranslationData` format.
  *
- * Returns `true` when `data.objects` exists and at least one entry has a
- * nested `fields` object (the distinguishing trait vs. an already-flattened
- * namespace tree).
+ * Returns `true` when the payload carries at least one spec translation group
+ * (see {@link SPEC_TRANSLATION_GROUPS}) whose value is an object — every spec
+ * group is a record or an object. A bundle is recognised by ANY group it
+ * carries: one that translates only object labels, apps, pages, dashboards or
+ * flows, with no field label anywhere, is as much a spec payload as one that
+ * translates fields (objectui#10235 — this used to require an
+ * `objects.<n>.fields` entry, and such a bundle was returned untransformed and
+ * read by nothing).
+ *
+ * What stays `false` is the other shape the console's loader accepts: an
+ * i18next resource tree that is already namespaced, as a mock or local-dev
+ * server may return it. Its top-level keys are namespace names — a built-in
+ * pack namespace such as `common`, an app namespace such as `crm`, or `app`,
+ * the one {@link transformSpecTranslations} itself emits — and none of them
+ * is a spec group, so feeding the transform's output back in never wraps it
+ * twice. A group-named key holding a string or an array is not a group either.
  */
 export function isSpecTranslationData(data) {
-    if (!data)
+    if (!isPlainObject(data))
         return false;
-    const objects = data.objects;
-    if (!objects || typeof objects !== 'object' || Array.isArray(objects))
-        return false;
-    for (const obj of Object.values(objects)) {
-        if (obj && typeof obj === 'object' && !Array.isArray(obj) && 'fields' in obj) {
-            return true;
-        }
-    }
-    return false;
+    return SPEC_TRANSLATION_GROUPS.some((group) => isPlainObject(data[group]));
 }
 /** Top-level keys that are copied through unchanged onto the `app` namespace. */
 const PASSTHROUGH_TOP_LEVEL_KEYS = [