docs(objectui): give the 3 singular section: examples in layout-dsl.mdx a name anchor

`layout-dsl.mdx` teaches form sections both as a `sections:` sequence and as a
singular `section:` mapping. The sequence examples were given `name` anchors in
the YAML-arm sweep; the three singular ones were outside that population and
stayed nameless, so each renders its authored label in every locale on a page
whose job is to teach the opposite.

The third site is not a copy of the other two -- it carries no `label:` at all,
so it takes a descriptive `name` and no invented label: the "Rendered Grid"
diagram directly below it draws no section header.

`FormSectionSchema.name` stays `.optional()`; no schema moves.

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

Author: claude

.changeset/docs-layout-dsl-singular-section-name.md

@@ -0,0 +1,39 @@
+---
+"@objectstack/docs": patch
+---
+
+fix(docs): give the three singular `section:` form-section examples in `layout-dsl.mdx` a `name` i18n anchor (#13759)
+
+`content/docs/protocol/objectui/layout-dsl.mdx` teaches form sections twice over: as a
+`sections:` **sequence**, and as a singular `section:` **mapping** — one section on its
+own. The sequence examples were given `name` anchors in the sweep that added the gate's
+YAML arm (#13761); the three singular ones were outside that sweep's population and stayed
+nameless. `FormSectionSchema.name` is the "Stable identifier for translation lookup", so a
+nameless section has no anchor and renders its authored label in every locale — on pages
+whose whole job is to teach the convention.
+
+Three sites, and they are **not** three copies of one edit:
+
+| fence | before | added |
+|:---|:---|:---|
+| `### Basic Grid Layout` | `label: Contact Information` | `name: contact_information` |
+| `### Custom Span Widths` | `label: Product Details` | `name: product_details` |
+| `### Responsive Breakpoints` | **no `label:`** — only `columns:` + `fields:` | `name: responsive_grid` |
+
+The first two take the snake_case of their own label, which is the convention #13761 used
+for the sequence examples on this same page (`contact_information`, `basic_info`,
+`billing_information`). The third has no label to snake_case: it is deliberately minimal so
+the breakpoint discussion is about `columns` collapsing, and none of the three fences' ASCII
+"Rendered Grid" diagrams draw a section header. So it gets a descriptive `name` and **no
+invented `label:`** — adding one would have desynchronised the diagram directly below it,
+and the i18n symptom the other two carry does not even arise for a section with no heading
+to mis-render.
+
+`FormSectionSchema.name` stays `z.string().optional()` — no schema moves here, per #10709
+and #10830.
+
+**These three sites are correct now and still unguarded**, deliberately.
+`check-docs-section-name` judges `sections:` sequences in both of its arms; a singular
+`section:` mapping is outside both, which is how these three drifted in the first place.
+Widening the gate means deciding which YAML keys introduce a form section at all — a
+population question fenced out of this PR by the #13759 triage ruling and filed separately.

content/docs/protocol/objectui/layout-dsl.mdx

@@ -232,6 +232,7 @@ All layouts use a responsive grid that divides space into columns.
 {/* os:check-yaml FormSectionSchema key=section */}
 ```yaml
 section:
+  name: contact_information
   label: Contact Information
   columns: 2  # two fields per row (50% width each)
   fields:
@@ -260,6 +261,7 @@ field from its widget type and the current column count.
 {/* os:check-yaml FormSectionSchema key=section */}
 ```yaml
 section:
+  name: product_details
   label: Product Details
   columns: 3
   fields:
@@ -292,6 +294,7 @@ Grid automatically collapses on smaller screens:
 {/* os:check-yaml FormSectionSchema key=section */}
 ```yaml
 section:
+  name: responsive_grid
   columns: 3  # Desktop: 3 columns, Tablet: 2 columns, Mobile: 1 column
   fields: [field_a, field_b, field_c, field_d, field_e, field_f]
 ```