fix(react): carry the 18 form-view spec keys the bridge silently dropped (#6365)

`spec-bridge/bridges/form-view.ts` states in its own docblock that "every
serializable spec key is either mapped onto the `object-form` node or listed
here with an explicit reason for being ignored — the bridge must never silently
drop spec configuration (#2545)". Measured against `@objectstack/spec` 17.2.0
that was false for 18 keys: 2 on `FormViewSchema`, 2 on `FormSectionSchema`,
14 on `FormFieldSchema`.

Seventeen have a real destination the receiving layer already reads, so they are
mapped; the eighteenth is an explained refusal, which is what "not silently"
asks for:

  buttons / defaults      -> `ObjectFormSchema` declares both slots and
                             `ObjectForm` folds them at render.
  section.pane            -> `ObjectFormSection.pane`, read by `SplitForm`'s
                             `paneOf`; dropped, every authored placement fell
                             back to the positional rule.
  section.visibleOn       -> folded onto `visibleWhen`, reproducing the
                             contract's own `normalizeVisibleWhen` for the
                             never-parsed input class this bridge serves.
  13 field keys           -> same-name copies onto the runtime FormField, at the
                             destinations `normalizeSectionField` already pins.
  field.publicPicker      -> NOT carried: a server-side public-lookup
                             authorization opt-in with no client destination.

The conformance test is why it stayed green: its completeness loop iterated
`Object.keys(FIXTURE)`, so a key nobody remembered to write into the fixture was
a key it never asked about. Its key set is now derived from the contract's own
shape at all three levels, every key must be claimed by a behavioral row or a
reasoned ignore entry, and the fixture is asserted spec-valid before any row
runs.


Claude-Session: https://claude.ai/code/session_011SfZeFWrhGLHmfq61xbz4q

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

Author: os-support-ai

.changeset/tidy-forms-carry-spec-keys.md

@@ -0,0 +1,35 @@
+---
+'@object-ui/react': patch
+---
+
+fix(react): stop the form-view bridge silently dropping 18 spec keys
+
+`spec-bridge/bridges/form-view.ts` promised (#2545) that "every serializable
+spec key is either mapped onto the `object-form` node or listed here with an
+explicit reason for being ignored". Measured against `@objectstack/spec` 17.2.0
+the promise was false for 18 keys, because the conformance test enforcing it ran
+its completeness loop over its own hand-written fixture rather than the
+contract's key set.
+
+Seventeen of them now reach the node, at the destinations the receiving layer
+already reads:
+
+- `FormViewSchema.buttons` / `.defaults` — `ObjectFormSchema` declares both and
+  `ObjectForm` folds them at render (action-button visibility/labels, and
+  create-mode initial values).
+- `FormSection.pane` — explicit split-pane placement; without it a spec-authored
+  split form fell back to the positional rule, so reordering sections moved them
+  across the divider.
+- `FormSection.visibleOn` — the deprecated spelling now folds onto `visibleWhen`,
+  matching the contract's own parse-time normalisation and the field path.
+- Thirteen `FormFieldSchema` keys — `maxLength`, `minLength`, `min`, `max`,
+  `precision`, `scale`, `multiple`, `immutable`, `span`, `language`, `keyField`,
+  `disclosure`, `fields` — so authored constraints, composite config and field
+  width survive the bridge instead of ending there.
+
+`publicPicker` is deliberately not carried and now says so: it is a server-side
+public-lookup authorization opt-in with no client destination.
+
+The conformance test's key set is now derived from the contract's own shape at
+all three levels, so a spec key that is neither mapped nor explained fails the
+suite by construction.