fix(spec): derive the migration TODO's group list from the schema, not a literal

The semantic migration entry for `translation-per-app-settings-platform-only`
enumerated nine of the ten groups the per-app face declares and omitted
`settingsCommon` — the nearest legitimate neighbour for an author who has just
had `settings` refused. `os migrate meta --from 17` prints this string verbatim
to the operator (`packages/cli/src/commands/migrate/meta.ts` renders
`surface → replacement`), so the omission reached a user-facing surface.

Correcting the literal would leave the construct that produced it. A
hand-maintained copy of a schema's key set already drifted here once, through a
full review of the surrounding change, so the copy is deleted rather than
pinned: `replacement` is now a getter that reads
`Object.keys(TranslationDataSchema.shape)`. There is one spelling of the set,
and a group added to the per-app face reaches this message the day it is
declared, with nothing to remember. Ordered remedy — delete the construct that
permits the error before reaching for a check that only reddens it.

`Object.keys` on a zod object shape returns the declaration order of the literal
it was built from, which is the order the sentence promises; the separator and
the shape of the sentence are unchanged, so the rendered paragraph reads as it
did. A getter rather than an eager template because importing the registry must
not force the lazy translation schema at module load.

The registry is generated by concatenating entry literals, and the generator
treats a file's imports as scaffolding — so `registry.ts` carries its own
hand-written value import outside the generated regions, with a comment saying
why. Verified: it survives `gen:migration-registry`, and
`system/translation.zod.ts`'s own 26-module closure reaches nothing under
`migrations/`, so the edge adds no cycle.

The changeset gains one sentence naming `settingsCommon` as unaffected. The
declared semver level is untouched — both packages stay `minor`; two prose
corrections and one derivation move no published signature.

Claude-Session: https://claude.ai/code/session_01UDXER3sdqfeVYpEWZs5mZx
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/15178-translation-bundle-split-settings-platform-only.md

@@ -28,6 +28,9 @@ included.
 is not application-authorable at all — `settings` is keyed by
 `SettingsManifest.namespace` and only platform code declares a manifest, so the
 only namespaces a per-app entry could ever address were the platform's own.
+`settingsCommon` is **not** affected — the Settings UI shell strings (the source
+badges, under `settingsCommon.sourceLabels`) stay on the per-app face; only the
+per-namespace manifest copy under `settings` leaves.
 Run `os migrate meta --from 17` to list the mechanical edits for existing
 sources; apply them by hand.
 

packages/spec/src/migrations/entries/semantic/18.translation-per-app-settings-platform-only.ts

@@ -1,5 +1,6 @@
 // Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
 
+import { TranslationDataSchema } from '../../../system/translation.zod.js';
 import type { SemanticMigration } from '../../types.js';
 
 // The judgment half of `translation-per-app-settings-removed`. The D2
@@ -10,17 +11,31 @@ import type { SemanticMigration } from '../../types.js';
 export const entry: SemanticMigration = {
   id: 'translation-per-app-settings-platform-only',
   surface: 'stack.translations[].<locale>.settings — the per-app bundle’s settings group',
-  replacement:
-    'Delete the group from the per-app bundle. There is no per-app replacement key: settings copy '
-    + 'is not application-authorable at all. `settings` is keyed by `SettingsManifest.namespace`, '
-    + 'and only platform code declares a manifest '
-    + '(`packages/services/service-settings/src/manifests/*.manifest.ts`), so the only namespaces a '
-    + 'per-app entry could ever address were the platform’s own. Platform settings copy is '
-    + 'translated in the PLATFORM bundle — `@objectstack/service-settings`’s '
-    + '`settingsBuiltinTranslations`, typed `PlatformTranslationData` — which is where a correction '
-    + 'to a platform string belongs. An application’s own copy goes in the groups the per-app bundle '
-    + 'still declares: `objects`, `apps`, `pages`, `dashboards`, `datasets`, `flows`, '
-    + '`globalActions`, `metadataForms`, `messages`.',
+  // The group names are DERIVED from `TranslationDataSchema.shape`, never typed
+  // out beside it. A hand-maintained copy of a schema's key set is the construct
+  // that drifted to nine-of-ten in this very message, so the copy is deleted
+  // rather than pinned: there is one spelling of the set, and a group added to
+  // the per-app face reaches this sentence the day it is declared.
+  // `Object.keys` on a zod object shape yields the declaration order of the
+  // literal it was built from — the order this sentence promises the operator.
+  // A getter, not an eager template: importing the registry must not force the
+  // lazy translation schema at module load.
+  get replacement(): string {
+    const groups = Object.keys(TranslationDataSchema.shape);
+    return 'Delete the group from the per-app bundle. There is no per-app replacement key: settings copy '
+      + 'is not application-authorable at all. `settings` is keyed by `SettingsManifest.namespace`, '
+      + 'and only platform code declares a manifest '
+      + '(`packages/services/service-settings/src/manifests/*.manifest.ts`), so the only namespaces a '
+      + 'per-app entry could ever address were the platform’s own. Platform settings copy is '
+      + 'translated in the PLATFORM bundle — `@objectstack/service-settings`’s '
+      + '`settingsBuiltinTranslations`, typed `PlatformTranslationData` — which is where a correction '
+      + 'to a platform string belongs. An application’s own copy goes in the '
+      + `${groups.length} groups the per-app bundle still declares, in the order it declares them: `
+      + groups.map((g) => `\`${g}\``).join(', ')
+      + '. Note `settingsCommon` among them: it IS on this face, so the Settings UI shell strings an '
+      + 'application may translate (the source badges, under `settingsCommon.sourceLabels`) are NOT '
+      + 'what is being removed here — only the per-namespace manifest copy under `settings` is.';
+  },
   reason:
     'Not losslessly convertible, and NOT because the content was inert — but not because it '
     + 'overrode anything either. Measured on this tree before the split: '

packages/spec/src/migrations/registry.ts

@@ -38,6 +38,13 @@
  * hand-written and still merges as text.
  */
 
+// A VALUE import, and the only one here: an entry literal below derives its
+// group enumeration from this schema's own keys rather than restating them
+// (`translation-per-app-settings-platform-only`). Entry files carry their own
+// copy of this import, but the generator treats a file's imports as scaffolding
+// and concatenates only the literal — so an entry that references a value needs
+// that value in scope HERE, hand-written, outside the generated regions.
+import { TranslationDataSchema } from '../system/translation.zod.js';
 import type { MigrationStep } from './types.js';
 
 /**
@@ -12238,17 +12245,31 @@ const step18: MigrationStep = {
     {
       id: 'translation-per-app-settings-platform-only',
       surface: 'stack.translations[].<locale>.settings — the per-app bundle’s settings group',
-      replacement:
-        'Delete the group from the per-app bundle. There is no per-app replacement key: settings copy '
-        + 'is not application-authorable at all. `settings` is keyed by `SettingsManifest.namespace`, '
-        + 'and only platform code declares a manifest '
-        + '(`packages/services/service-settings/src/manifests/*.manifest.ts`), so the only namespaces a '
-        + 'per-app entry could ever address were the platform’s own. Platform settings copy is '
-        + 'translated in the PLATFORM bundle — `@objectstack/service-settings`’s '
-        + '`settingsBuiltinTranslations`, typed `PlatformTranslationData` — which is where a correction '
-        + 'to a platform string belongs. An application’s own copy goes in the groups the per-app bundle '
-        + 'still declares: `objects`, `apps`, `pages`, `dashboards`, `datasets`, `flows`, '
-        + '`globalActions`, `metadataForms`, `messages`.',
+      // The group names are DERIVED from `TranslationDataSchema.shape`, never typed
+      // out beside it. A hand-maintained copy of a schema's key set is the construct
+      // that drifted to nine-of-ten in this very message, so the copy is deleted
+      // rather than pinned: there is one spelling of the set, and a group added to
+      // the per-app face reaches this sentence the day it is declared.
+      // `Object.keys` on a zod object shape yields the declaration order of the
+      // literal it was built from — the order this sentence promises the operator.
+      // A getter, not an eager template: importing the registry must not force the
+      // lazy translation schema at module load.
+      get replacement(): string {
+        const groups = Object.keys(TranslationDataSchema.shape);
+        return 'Delete the group from the per-app bundle. There is no per-app replacement key: settings copy '
+          + 'is not application-authorable at all. `settings` is keyed by `SettingsManifest.namespace`, '
+          + 'and only platform code declares a manifest '
+          + '(`packages/services/service-settings/src/manifests/*.manifest.ts`), so the only namespaces a '
+          + 'per-app entry could ever address were the platform’s own. Platform settings copy is '
+          + 'translated in the PLATFORM bundle — `@objectstack/service-settings`’s '
+          + '`settingsBuiltinTranslations`, typed `PlatformTranslationData` — which is where a correction '
+          + 'to a platform string belongs. An application’s own copy goes in the '
+          + `${groups.length} groups the per-app bundle still declares, in the order it declares them: `
+          + groups.map((g) => `\`${g}\``).join(', ')
+          + '. Note `settingsCommon` among them: it IS on this face, so the Settings UI shell strings an '
+          + 'application may translate (the source badges, under `settingsCommon.sourceLabels`) are NOT '
+          + 'what is being removed here — only the per-namespace manifest copy under `settings` is.';
+      },
       reason:
         'Not losslessly convertible, and NOT because the content was inert — but not because it '
         + 'overrode anything either. Measured on this tree before the split: '