fix(spec): changeset names core's warn text; objectql test comment follows the snake_case naming

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WGufzhKYT8L13Bgj8icT3i

Author: claude

.changeset/26128-translation-item-snake-case-name.md

@@ -1,5 +1,6 @@
 ---
 '@objectstack/spec': patch
+'@objectstack/core': patch
 ---
 
 fix(spec): `TranslationItemSchema.name` no longer tells authors to name a translation item after its locale tag
@@ -8,3 +9,5 @@ Clause-②: no
 Metadata-protocol: none
 
 The `name` describe said a translation item was "conventionally the locale code (`zh-CN`)", but the metadata save door's item-name grammar refuses `zh-CN` (uppercase and a hyphen), so an author or agent following the describe got a 400 `INVALID_REQUEST` on the first save. The describe now says a translation item is named in snake_case like every metadata item (e.g. `zh_cn`), with the BCP-47 tag in `locale`. The save door and the runtime sync's read-side name fallback for rows stored before `locale` became required are unchanged; the sync's skip warning now points authors at `locale` only.
+
+`@objectstack/core`: the authored-translation sync's no-locale skip warning now tells authors to set `locale` to the item's BCP-47 tag (e.g. `zh-CN`), instead of suggesting they name the item after it.

packages/objectql/src/protocol-publish-canonical-fold.test.ts

@@ -265,8 +265,8 @@ async function refusalOf(fn: () => Promise<unknown>): Promise<{ code?: string; s
 
 /**
  * A `translation` body. `TranslationItemSchema` requires `locale`; `name` is
- * declared and optional, and is deliberately NOT snake_case-constrained for
- * this type (translation items are conventionally named after their locale).
+ * declared and optional; like every metadata item it is named in snake_case
+ * (`zh_cn`), with the BCP-47 tag in `locale`.
  */
 const translationBody = (label: string) => ({ locale: 'zh-CN', name: 'zh_cn', label });