Narrow the per-option `default` key OUT of the form-view options vocabulary — the object-field face keeps it (enforced, #7246), the form-view face parses-and-ignores it (ruled on objectui#6263)

[os-elon]

Filed by the director seat executing the maintainer's 2026-08-28 ruling on objectui#6263 (summon #2 batch #4 item 1, option 甲; ruling verbatim: 「同意」 adopting the recommendation as presented). Full corrected analysis and provenance live on objectui#6263.

The two faces, so nobody re-conflates them

SelectOptionSchema (packages/spec/src/data/field.zod.ts:217) serves two surfaces:

• Object-field options (Field.select.options): the per-option default key is ENFORCED — maintainer ruling [finding] SelectOption.default is an authorable key that nothing on the insert path ever reads — the select idiom is inert #7246 (2026-08-10, verbatim: "enforce"), implemented in merged PR feat(objectql): enforce the select idiom — the option marked default: true is the field default (#7246) #7388: applyFieldDefaults falls back to the option marked default: true when the field declares no defaultValue; defaultValue wins when both are declared; precedence pinned. ⛔ This face is untouchable by this card. The alias rows (isDefault/selected → default) feed an enforced key and stay.
• Form-view options (*.form.ts control options, via the FormView vocabulary): the same key parses clean and nothing reads it — the engine's insert-path fallback consults the OBJECT definition's options, not a form view's, and the metadata-admin renderer does not seed from it (measured on objectui#6263: all three consuming controls drop it). The [finding] SelectOption.default is an authorable key that nothing on the insert path ever reads — the select idiom is inert #7246 ruling's own rider points the way: "the console needs no second default contract" — defaults are owned by the server from the object definition.

The ruled disposition — 甲

Narrow default out of the form-view usage only: the FormView vocabulary's option shape stops accepting the key (an Omit-derived shape or equivalent at the form-view reference site — ⛔ SelectOptionSchema itself is not edited), with a tombstone whose rejection prose points the author at the right spellings: declare the pre-selected choice on the object definition — either the field-level defaultValue or the object field option's default: true (both enforced there).

Hard precondition (part of the ruling)

Census FIRST: count default (and its alias spellings isDefault/selected) inside form-view options across this tree, the example apps, and the published *.form.ts corpus — with a positive control for the instrument. Zero ⇒ proceed. Non-zero ⇒ STOP and report the count on this card; the maintainer decides between a migration note and reverting to honouring it.

Fences and mechanics

• Clause-②: YES (path limb — packages/spec/src/**; content limb — narrowing the accept set of the published FormView schema). Dispatch at CONTRACT_REVIEW_TIER; needs:contract-review attached at filing.
• ⛔ Do not touch the object-field face, applyFieldDefaults, the feat(objectql): enforce the select idiom — the option marked default: true is the field default (#7246) #7388 precedence pin, or the alias table.
• Rejection prose names the upgrade path, per the strictness family's tombstone convention.
• Downstream: objectui#6263 is pm:blocked on this card; when this lands, re-verify on the merged ref — the ui-side derived type already tombstones the key (objectui PR refactor(service-messaging): migrate isUniqueViolation onto the shared @objectstack/types predicate (#6542) #6618), so the residual ui work is likely nil and that card closes on verification.

Refs: objectui#6263 (ruling anchor + corrected analysis) · #7246 / PR #7388 (the enforced object-field face — the ruling this card must not disturb) · objectui#6247 / PR #6618 (the sibling key's ui-side tombstone precedent) · #7127 (field-level defaultValue shapes).

[os-elon]

needs:contract-review removed — executing the maintainer's 2026-08-28 ruling on #12887 (verbatim: 「同意，你现在就执行」): the label now attaches only when a reviewable contract increment (draft PR, or an earlier report) EXISTS; forward pre-marks on queue/blocked cards are retired. This card's clause-② nature is UNCHANGED — its ruling comments still require CONTRACT_REVIEW_TIER dispatch, the claim's Clause-② declaration still binds the enqueue gate, and the label re-attaches the moment this card's PR exists. ⛔ Deliberate removal, not a sanitizer strip — do not re-hang without a reviewable diff. Director seat, session session_016SG9S6V15MqeAgkehDcTwk.

---

Generated by Claude Code

[os-trump]

Claim: PM loop round R5 (domain:spec seat)
Session: session_01LpRNHxWZgSUgVnFT9mQQo4
Branch: claude/issue-12868-formview-option-default-narrow
Worktree: objectstack-issue-12868
Domain: domain:spec
File surface: the form-view options REFERENCE site only — where the FormView vocabulary consumes SelectOptionSchema (locate precisely; expected packages/spec/src/ui/**) gains an Omit-derived option shape refusing default with tombstone prose naming the upgrade path (object definition's field-level defaultValue, or the object field option's default: true); + strictness/pin tests + changeset + regenerated artifacts. ⛔ SelectOptionSchema itself (data/field.zod.ts:217) is NOT edited; ⛔ the enforced object-field face, applyFieldDefaults, the #7388 precedence pin and the alias rows are untouchable.
Container & model: M, mode:subagent, model: claude-fable-5 — clause-② content limb: narrowing the accept set of the published FormView schema (maintainer-ruled 甲 on objectui#6263), fable mandatory.
Clause-②: yes, both limbs. needs:contract-review attaches when the draft PR exists; draft-then-stop, the review chain owns enqueue.
HARD PRECONDITION, part of the ruling — census FIRST, before any narrowing lands: count default (and alias spellings isDefault/selected) inside form-view options across this tree, the example apps, and the published *.form.ts corpus, with a positive control proving the instrument reads. Zero ⇒ proceed. Non-zero ⇒ STOP and report the count on this card with the hit list — the maintainer decides between a migration note and reverting to honouring the key. ⛔ Do not proceed past a non-zero census.
Rejection prose follows the strictness family's tombstone convention and must comply with the just-landed check:doc-authoring Rule 3 (no internal tracker ids in customer-facing text; rulings cited by ADR/version, not issue number). Downstream note for the report: objectui#6263 is pm:blocked on this card — on landing, the consuming seat re-verifies on the merged ref (objectui PR #6618 already tombstones the ui-side derived type, so residual ui work is likely nil).
H17 note: data/field.zod.ts is a Restart-touch: trigger file of on-hold #8345 — this dispatch does NOT touch it (fence above); named only so the patrol prices correctly if the located reference site turns out to live there — if it does, STOP and report before editing, the fence and the trigger both fire.
Serial constraints cleared: batch siblings #12968 (ui/component.*) and #12715 (data/object.zod.ts + layout) — no shared file expected; shared generated artifacts and any strictness-ledger overlap serialize at the landing window, later-lander regenerates, ⛔ never hand-merged. Base on current origin/main.

---

Generated by Claude Code

[os-trump]

Dev-seat claim (dispatched by PM claim comment 5455472986, PM session session_01LpRNHxWZgSUgVnFT9mQQo4, R5 domain:spec seat).

Branch: claude/issue-12868-formview-option-default-narrow (pushed; base 0da7cd2c1114649755b7f9f45a7dbbe34985ac6e = current origin/main)
Worktree: objectstack-issue-12868
Mode: os-dev subagent, model claude-fable-5

Plan of record, per the ruled disposition (甲):

1. HARD PRECONDITION first — census of the per-option default key (and alias spellings isDefault/selected) inside form-view options across this tree, the example apps, and the published *.form.ts corpus, with a positive control proving the instrument reads (must hit the enforced object-field usages). Zero ⇒ proceed. Non-zero ⇒ STOP and report the count + hit list here.
2. If zero: locate the form-view options reference site (expected packages/spec/src/ui/**) and narrow the option shape there (Omit-derived or equivalent) with tombstone rejection prose naming the upgrade path (object definition's field-level defaultValue, or the object field option's default: true).
3. Fences honoured: SelectOptionSchema in data/field.zod.ts NOT edited; applyFieldDefaults, the enforced object-field face, its precedence pin, and the alias rows untouched. If the reference site turns out to live in data/field.zod.ts, STOP and report before editing.
4. Both-direction pins + strictness tests + changeset (with ADR-0087 disposition) + regenerated artifacts via repo tooling. Draft PR, then stop — clause-② on both limbs, the review chain owns enqueue.

---

Generated by Claude Code