docs(spec): resolveMetadataFormLabels' docblock states the label-slug section lookup

The docblock said a section without a stable `name` is returned unchanged
for section-level attributes. `translateSection` does otherwise: with no
`name` it looks the section up under a slug of its string `label`, and only
a section with neither keeps its section-level text. Fields are translated
either way. The docblock ships in `dist/system/index.d.ts`, so the changeset
gains one sentence. Comment only: no code, no `.describe()`.

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

Author: claude

.changeset/23756-section-translation-tsdoc.md

@@ -4,4 +4,4 @@
 
 Clause-②: no
 
-The published TSDoc now sends a form section's translations to the right key. `FormSectionSchema.name` used to name only `metadataForms.<type>.sections.<name>`, which is the key for a metadata-editing form (`defineForm({ schemaId })`, read by `resolveMetadataFormLabels`). A section of an object-bound form view is keyed at `objects.<object>._sections.<name>`, where `<object>` is the form's own `data.object`, else its view's. The docblock now names both keys and which form each one serves. `TranslationDataSchema._sections` now names the three surfaces that author its key (form-view sections, `record:details` sections, object `fieldGroups`) and its readers (`walkObjectSections`, `collectViewRecord`, `translateView`). These are comment changes only: no key, `.describe()` text or behaviour changes. An object-form translation bundle written from the old docblock under `metadataForms.…` never translated anything. Move its section entries to `objects.<object>._sections.<name>`.
+The published TSDoc now sends a form section's translations to the right key. `FormSectionSchema.name` used to name only `metadataForms.<type>.sections.<name>`, which is the key for a metadata-editing form (`defineForm({ schemaId })`, read by `resolveMetadataFormLabels`). A section of an object-bound form view is keyed at `objects.<object>._sections.<name>`, where `<object>` is the form's own `data.object`, else its view's. The docblock now names both keys and which form each one serves. `TranslationDataSchema._sections` now names the three surfaces that author its key (form-view sections, `record:details` sections, object `fieldGroups`) and its readers (`walkObjectSections`, `collectViewRecord`, `translateView`). `resolveMetadataFormLabels`' docblock no longer says that a section without a `name` keeps its section-level text: such a section is looked up under a slug of its `label`, as the function has always done. These are comment changes only: no key, `.describe()` text or behaviour changes. An object-form translation bundle written from the old docblock under `metadataForms.…` never translated anything. Move its section entries to `objects.<object>._sections.<name>`.

packages/spec/src/system/i18n-resolver.ts

@@ -3916,9 +3916,13 @@ function translateFormField(
  * Translate the labels, descriptions, helpTexts, and placeholders of a
  * metadata-type configuration form against the active translation bundle.
  *
- * Sections without a stable `name` are returned unchanged for section-level
- * attributes — only field labels are translated (field names are always
- * stable identifiers).
+ * A section's `label` and `description` are looked up at
+ * `metadataForms.<type>.sections.<section_name>`, where `<section_name>` is
+ * the section's own `name` or, when it has none, a slug of its string `label`
+ * (lowercased, `&` → `and`, each run of non-alphanumerics → `_`, edge
+ * underscores trimmed). Only a section with neither keeps its section-level
+ * text. Its fields are translated either way, since field names are always
+ * stable identifiers.
  *
  * Returns a new form object; the input is not mutated.
  *