docs(objectui): layout-dsl teaches only shapes the live schemas accept (#13337)

* docs(objectui): layout-dsl teaches only shapes the live schemas accept

Every YAML fence on the page is now validated by check:yaml-examples: 18
tagged / 0 untagged, up from 6 tagged / 17 untagged. Each of the 17 untagged
fences was refused by every live schema it could plausibly claim (re-derived
by safeParse on this base); each is now either rewritten to the declared shape
and tagged, or removed with a Callout recording what it taught and why it is
gone.

Rewritten and tagged: the two page templates (no `context:` key; `name` +
`label` are required), custom span widths (`span: auto|full`, not twelfths),
the field-group examples (section `columns` + per-field `span`), related lists
and widgets (page components with `properties`, not form sections), the
master-detail and kanban blocks (`object-master-detail-form` / `object-kanban`,
not a page-level `layout:` mapping), Customer 360 (`regions` is an array), and
the onboarding wizard (a `tabbed` form view).

Removed rather than implemented, per ADR-0049 enforce-or-remove in the docs
direction: the `steps:` wizard template, section `variant:`, related-list
`mode: inline_edit`, and the `card_grid` block (whose per-breakpoint `columns`
map is the same defect class already removed from this page).

No packages/spec source is touched — the docs move to the spec, not the
reverse.

* docs(objectui): point the wizard Callout at the real flows route

The replacement Callout linked /docs/protocol/automation/flow, a route that
does not exist — the page is content/docs/automation/flows.mdx, which 18 other
links already spell /docs/automation/flows. Caught by the Check Documentation
Links job (lychee --offline resolves root-relative links against content/);
check:doc-anchors did not, because it judges in-page #fragments rather than
route destinations.

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: claude[bot]