A select / radio field with neither options nor picklist: refuse it at the FieldSchema door (an accept-set narrowing), or keep it at the ADR-0078 completeness gate? (split from #19518)

Ruled: 5910124148 · letter A — a select / radio with neither options nor picklist is refused at the FieldSchema door (lookup precedent), after #19518 lands; census of stored rows and the Studio create-field order first · 2026-09-30T11:25Z

Filed by the domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1, seat post #19357), from the #19518 dev report 5908082075 (open question 1) on PR #20823. The line is split from #19518 so that the picklist kind can land without it. ⛔ Not a claim. The decision analysis is the first comment.

Governing text

picklist metadata kind — spec: picklist collection, Field.select({ picklist }), server-resolved options, translation face (phase 1 of objectstack#18164) #19518, Scope item 2: "Field.select({ picklist: 'industry' }), mutually exclusive with options: both or neither on a select type is refused at the schema door with a prescription." Its Acceptance line reads: "picklist + options together refused, neither refused".
ADR-0078 (docs/adr/0078-no-silently-inert-metadata.md) puts field/choice-without-options (error for select / radio) in the author-time completeness gate that os build, os validate and os lint enforce. Its registration-time twin in packages/objectql/src/registry.ts "warns and never throws".
Precedent for moving a completeness rule into the schema door: commit 0fb8760bec (fix(spec): require a non-empty reference on lookup/master_detail fields #13927) refused a lookup / master_detail without reference at parse. It shipped as a minor with a BREAKING header and an ADR-0087 not-required marker.

What the #19518 dev measured (branch `claude/issue-19518-picklist-kind`)

A schema-door refusal of a select / radio with neither key was implemented and then withdrawn. With it in place, 4 packages/spec fixtures and 9 tests in @objectstack/metadata-protocol's stored-conversions and stored-migration suites went red: a stored select row with no options stops validating, and migrateStoredMetadata stops rewriting it.
Not measured: how many stored rows in real deployments carry such a field, and whether Studio saves a select field before its options exist. The dev's report says such a save "would 422"; that is inferred, not measured.
On main today, a select with an empty option list at runtime turns off server-side value validation (record-validator.ts, the reason the ADR-0078 rule gives).

Dedupe words: choice-without-options, select without options, picklist neither, FieldSchema select refuse

Blocked-by: objectstack-ai/objectui#11253

Triage: grade completed — `enhancement` · `priority:p2` · `area:records` added beside `domain:spec` · `pm:blocked`

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-30T19:55Z. ⛔ Not a claim, ⛔ not a dispatch.

This card went from the decision box to the queue, then to a claim and to pm:blocked, without a type or priority label.

The grade follows picklist metadata kind — spec: picklist collection, Field.select({ picklist }), server-resolved options, translation face (phase 1 of objectstack#18164) #19518, the card it was split from (priority:p2 · area:records).
It is an accept-set narrowing, so its type is enhancement.
The state (pm:blocked on Studio autosaves a new select / radio before it has options; once objectstack#20827 refuses such a field at the FieldSchema door, that save answers 422: guard or complete the write first objectui#11253) is unchanged.

The objectui half is graded: objectstack-ai/objectui#11253 is enhancement · p2 · domain:ui · area:studio · pm:queue (5917874517). Its direction is a choice-type write guard at MetadataClient.save, and plugin-designer hides the choice types.

Unlock. Once objectstack-ai/objectui#11253 lands, this card goes pm:blocked → pm:on-hold, with Restart-when: .objectui-sha carrying that merge. That is the install face step two needs.

Generated by Claude Code

Triage: objectstack-ai/objectui#11253 landed (objectui `1563d3e10b`, PR objectui#11287). By the pin rule, `pm:blocked` → `pm:on-hold`, not `pm:queue`

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-01T01:03Z. ⛔ Not a claim, ⛔ not a dispatch.

Restart-when: .objectui-sha on main contains objectui 1563d3e10b (PR objectui#11287, objectui#11253), through a pin bump.

Why on-hold. Step two closes the FieldSchema door. Ruling A's execution parameter is that "the objectui side changes its order first … and the door closes after". The console this repo ships is the pinned objectui (db11afd4967c), which does not carry the guard yet. Closing the door before the pin moves would put Studio's 422 into this repo's own console.

This applies the rule triage re-stated in R68: an unlock keys on the pin, not on the upstream merge.
The bump: Bump .objectui-sha past objectui f4ed2387e9 (objectui#11163, related-list actions), which also carries objectui#11199: unblocks #20936 and #20299 #20949 (pm:dispatched) names objectui#11253 as a later rider. If it lands carrying 1563d3e10b, this card frees then. Otherwise the next bump carries it.

Unchanged: enhancement · p2 · domain:spec · area:records.

Generated by Claude Code

Unlock scan: the restart condition holds, so `pm:on-hold` → `pm:queue`

domain:spec seat 2 (session_01YDt3PzwfrkuFzUBF89WPmM) · 2026-10-02T07:40Z · ⛔ not a claim; no assignee.

Double check, both legs:
- ① The condition is the one in the most recent transition comment, 5922609922: .objectui-sha covers objectui 1563d3e10b.
- ② No merged PR is cross-referenced on this card after that comment.
Reading: .objectui-sha on main is 31971ff1e28f. REST compare 1563d3e10b...31971ff1e28f on objectstack-ai/objectui answers ahead, ahead_by 30, behind_by 0. The pin carries the commit, so the console this repo ships has the objectui half.
Next: this card is a candidate again (p2, domain:spec). The dispatch shape is the one pre-written in 5922609922.

Generated by Claude Code

Claim: PM loop round 1 (ruling A 5910124148, step two: the FieldSchema door)
Session: session_01YDt3PzwfrkuFzUBF89WPmM
Account: os-tesla (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-20827-choice-door
Worktree: objectstack-issue-20827
Domain: domain:spec
Seat: domain:spec#2
File surface:

packages/spec/src/data/field.zod.ts: the FieldSchema superRefine (the door beside the lookup reference check, about :2116), the options / picklist TSDoc and describes, and the "neither" comment at :2131.
The four fixtures named in step one (5917187437): field.test.ts, field-autonumber-default-unique.test.ts, filter-number-comparand-declared-type.ts, filter-text-operator-declared-type.ts. The pin at picklist.test.ts:129 is rewritten as a refusal pin.
packages/metadata-protocol: the one legacyObjectRow fixture row (protocol.stored-conversions.test.ts, protocol.stored-migration.test.ts).
New door pins in packages/spec/src/data/*.test.ts.
The regenerated spec artefacts and reference pages.
Prose in content/docs/** that states an optionless select parses.
One .changeset/20827-*.md: minor, a BREAKING header, and an ADR-0087 disposition marker.
⛔ No objectui edit. ⛔ ADR-0078's author-time rule and the registration warning are not edited.
Stop on breach and explain in the report.

Container & model: M, mode:subagent, model: opus (dispatch-gates --tier at 16eefc6c0e: no path-derived mandate; floor sonnet · default opus · ceiling CONTRACT_REVIEW_TIER). The at-tier contract review is owed and runs as a separate isolated subagent after the PR opens.
Clause-②: yes
Thread-read: 5947557233
Serial constraints cleared:

The two named in 5913459642 have both landed: picklist metadata kind — spec: picklist collection, Field.select({ picklist }), server-resolved options, translation face (phase 1 of objectstack#18164) #19518 is closed, and fields: number rendering honours the authored useGrouping (1 key) #20313 (useGrouping) is closed.
At 2026-10-02T07:46Z, none of the 10 open PRs touches this surface. chore: version packages #21352 (Version Packages) matched only a changeset file name.
packages/spec/src: 1,277 comment lines still cite 170 deleted tracker numbers (1,295 sites) — the staged remainder of ruling C+D on #19123, measured by PR #20226 #20234 (seat 5, off shift) has stage 11 in migrations/registry.ts's hand-written parts. That region is disjoint from this surface.
The verify lock is free.

Execution, as the ruling and step one fix it:

The objectui order landed (objectui#11253), and the pin 31971ff1e28f carries it (5947557233).
The door follows the lookup precedent (0fb8760bec, fix(spec): require a non-empty reference on lookup/master_detail fields #13927). Its prescription names both keys.
Stored rows are named through /meta/diagnostics or the boot log (field/choice-without-options), not the os migrate meta --stored preview.
Step one's side finding is checked and reported: whether the door reaches blueprint output (solution-blueprint.zod.ts:88 / :320).

Generated by Claude Code

os-dev-report

{
 "issue": 20827,
 "status": "done",
 "branch": "claude/issue-20827-choice-door",
 "pr": "https://github.com/objectstack-ai/objectstack/pull/21390",
 "session": "session_01YDt3PzwfrkuFzUBF89WPmM (subagent run; the PM's session id, identity = branch claude/issue-20827-choice-door per claim 5947645436)",
 "premise_still_valid": true,
 "summary": "FieldSchema's superRefine now refuses a select / radio with neither a non-empty options list nor a picklist, at the options path, with a custom issue naming the type and both remedies, beside the reference check (precedent 0fb8760bec). The door applies the ADR-0078 completeness predicate itself (checkFieldCompleteness: a field/choice-without-options finding at error severity), so options: [] is the same hole, a picklist is a source, and the type set is exactly select / radio; no export is added and functional-completeness.ts is not edited. The census matched step one exactly (4 oversight fixtures + the picklist pin in spec, 9 metadata-protocol tests from one row); every red is fixed, the picklist pin is a refusal pin, the stored-row disposition is pinned in metadata-protocol, and a spec minor BREAKING changeset carries the not-required (no-migration-prescription) marker. Draft PR 21390 is open on head ee5b089bbe (origin/main merged in), assigned os-tesla.",
 "tests": "Full @objectstack/spec suite at head ee5b089bbe: 646 files, 18391 passed, 1 todo (VERDICT command-exit 0). Spec typecheck incl. check:test-typecheck green; check:generated: all 15 artifacts up to date; metadata-protocol typecheck green. Consumer suites with the door on, at a9473b8d91 (the merge brought no change to their sources): metadata-protocol 201 files / 2983 passed / 19 skipped; objectql 363 / 7277 (incl. both engine door suites that consume the changed spec fixtures); lint 119 / 5575; metadata 56 / 836; runtime 306 / 5081 / 11 skipped. Red census at base 5fd4855a9a: spec 6 failed in 5 files, metadata-protocol 9 failed in 2 files. Ablation (reverse verification): scripts/ablation-replace.mjs swapped FIELD_CHOICE_WITHOUT_OPTIONS for the literal 'ablation-20827-never' (anchor 1 to 0, blob ea9313c768 to 9654443823), the spec rebuild was proved by ablation-dist-preflight (marker in 24 built files), and the mutate leg was RED: 8 spec pins and 3 metadata-protocol pins, positive controls green. The restore leg used git checkout HEAD (blob equal to HEAD, git diff HEAD empty); after a rebuild, preflight --absent reported 0 of 230 built files and a clean tree; 325/325 spec and 56/56 metadata-protocol passed. Expected direction red, observed red.",
 "mcp_calls": "0 — no MCP GitHub tool called",
 "api_writes": "3 relay writes as objectstack-fleet[bot], each one repository_dispatch to the board relay: (1) pr_create, POST /repos/objectstack-ai/objectstack/pulls (draft, PR 21390), run 36993732961; (2) label-write assign, POST /repos/objectstack-ai/objectstack/issues/21390/assignees (os-tesla), run 36993794660; (3) the os-dev-report comment, POST /repos/objectstack-ai/objectstack/issues/20827/comments via post-stamped.mjs. Plus 8 git pushes, which are not REST writes.",
 "open_questions": [],
 "out_of_scope_findings": [
  "class: c · reach: measured at a public door — ObjectSchema.safeParse on the exact os:check block 'The v17-canonical shapes, compiled' at skills/objectstack-upgrade/references/examples-upgrade.md:105 (status: { type: 'select', required: true, storage: { notNull: true } }) answers success:false, fields.status.options custom, against this branch's built spec; producer: the published objectstack-upgrade skill. Evidence: the block is only type-checked (check:skill-examples green), so no gate sees the parse refusal, and the block's own claim 'cannot rot into teaching a shape that no longer compiles' is false at parse. This change makes the published text false, so it is owed a fix, but skills/** is Tier H and the dispatch barred it. Fix: one options entry on status, in a skills-lane PR landing with this door. · dedupe words: examples-upgrade select options, objectstack-upgrade skill choice door, v17-canonical shapes select, crm_lead status select",
  "class: c · reach: named producer — StrictField (packages/spec/src/ai/solution-blueprint.zod.ts:320, options .nullable()) and BlueprintFieldSchema (:88, options optional), the AI structured-output target that apply_blueprint expands; apply_blueprint lives outside objectstack and objectui (objectui only renders its progress and plan cards; nothing in packages/** or examples/** of either repo expands a blueprint into FieldSchema input). The module header says the expansion is validated by the per-type schema at write time, so an optionless blueprint select is now refused there, loudly, one step after the AI emitted it. Not measured end to end. Fix direction: align BlueprintFieldSchema / StrictField options with the door for select / radio. · dedupe words: blueprint select options, StrictField options nullable, BlueprintFieldSchema options, apply_blueprint choice door",
  "carrier: the objectui lane on its next @objectstack/spec bump — packages/data-objectstack/src/object-metadata-write-guard.derivation.test.ts, describe 'the installed server still ACCEPTS a choice with no options', turns red by design once the installed spec carries this door; its own comment prescribes the rewrite into a refusal pin at options · noted, not filed"
 ],
 "gates": [
  "dispatch-gates --repo objectstack-ai/objectstack --commands at ee5b089bbe: 110 families; each exit code written to ran.list; --ran: exit 0, '110 derived famil(ies) accounted for — 109 run, 1 NOT-MEASURED (0 DERIVED from a recorded exit 3, 1 claimed)'",
  "pnpm --filter @objectstack/spec build: exit 0 (VERDICT command-exit 0)",
  "pnpm --filter @objectstack/spec check:generated: exit 0, 'All 15 generated artifacts are up to date' (pre-merge run: exit 1, 1 stale check:docs, then --fix regenerated only that: content/docs/references/data/field.mdx, data/object.mdx, system/migration.mdx)",
  "pnpm --filter @objectstack/spec test (vitest run): exit 0, 646 files / 18391 passed / 1 todo",
  "pnpm --filter @objectstack/spec typecheck: exit 0, 'check:test-typecheck: OK … 52 file(s) / 246 error(s) / 135 pinned signature(s) held'",
  "pnpm --filter @objectstack/metadata-protocol test: exit 0, 201 passed / 3 skipped files, 2983 passed / 19 skipped tests; typecheck exit 0",
  "objectql exit 0 (7277); lint exit 0 (5575); metadata exit 0 (836); runtime exit 0 (5081 / 11 skipped)",
  "pnpm check:adr-0087-registration: exit 0, '1 declared-breaking changeset(s), each carrying an ADR-0087 disposition' · [BREAKING+bang] not-required (no-migration-prescription)",
  "node scripts/check-changeset-no-major.mjs --event (draft body): exit 0, 'This diff introduces no major bump' · 'LEVEL AXIS: this PR declares clause-② yes, and no package whose packages/**/src/** it moves is graded patch'",
  "node scripts/check-empty-changeset.mjs: exit 0, 'No empty-frontmatter changeset introduced by this diff (1 declaring changeset(s) added)'",
  "pnpm check:changeset-gate-self-tests: exit 0",
  "pnpm check:doc-authoring: exit 0, '17226 customer-facing string(s) across 1229 spec sources clean — no internal issue-id references'",
  "pnpm check:nul-bytes: exit 0, 'scanned 9679 text file(s) … no raw ASCII control bytes'",
  "pnpm --filter @objectstack/spec run check:api-surface: exit 0, 'public API surface + factory signatures unchanged'",
  "pnpm --filter @objectstack/spec run check:skill-examples: first exit 3 (client dist missing), re-run after the dists existed: exit 0, '259 prose examples type-check across 3 surface(s)'",
  "NOT MEASURED: pnpm check:dual-build-cjs-loads, reason: exit 3 PREREQUISITE NOT MET (it needs every published package's dist). Declared narrowing: all 19 require-condition entries of @objectstack/spec dist load under CJS, and the door is live through dist/data/index.js. The full gate is CI's.",
  "CI on PR 21390: in_progress at report time (not awaited, per contract)"
 ],
 "line_budget": "344 changed lines (+307 / -37) over 16 files vs the 5000 human-merge threshold: under (dispatch-gates at ee5b089bbe). No skills/** or other governed-surface file is touched, so no line ratchet applies and the PR is not Tier S/H.",
 "deviations": [
  "Clause-② line copied verbatim from the claim ('yes') into the PR body and the changeset. The diff narrows FieldSchema's accept set (BREAKING, carried by the changeset banner) and also widens one published type: the two exported door-fixture interfaces gain an optional options member. So 'yes (narrowing)' is the fuller spelling. Not self-amended; both gates pass on 'yes'.",
  "Conflict between the standing rule (a published defect this change makes false must be fixed) and the dispatch's '⛔ No skills/** edit': the dispatch was followed. The skills example is listed in Acceptance notes and out_of_scope_findings with a measured reach, for a skills-lane (Tier H) PR.",
  "Beyond the census: canonicalObjectRow (protocol.stored-migration.test.ts) got the same one option. It caused no red, but its doc ('already canonical') is false under the door. Three new stored-row disposition pins were added in the two metadata-protocol files the claim names.",
  "origin/main (11905a4f8b) was merged into the branch before the PR opened (AGENTS.md §10). Spec build, check:generated, the full spec suite, typecheck and the gate union ran at merged head ee5b089bbe. The consumer suites ran before the merge, at a9473b8d91; the merge brought no change to their package sources.",
  "The full spec suite takes about 25 minutes, past the foreground cap. It ran under the verify lock as a background job, waited on in the foreground with tail --pid.",
  "Labels: the dispatch named no label beyond the PR assignee, and skip-changeset does not apply (a changeset exists), so only --assign os-tesla was written. size/m was added by the size labeler, not by this run.",
  "Commit trailers use the model-free pair AGENTS.md requires (Claude-Session + Co-authored-by: Claude), not the harness reminder's model-named Co-Authored-By. The pre-push hook accepted all 8 pushes.",
  "A4 precision: migrateStoredMetadata marks such a row failed only when the row also carries an older spelling to lower (pinned). A row whose only defect is the missing option source has nothing to convert, so the pass counts it canonical. The changeset says so and names /meta/diagnostics and the boot log as the census tools."
 ],
 "files_changed": [
  ".changeset/20827-choice-door-select-radio-needs-options.md (+50)",
  "packages/spec/src/data/field.zod.ts (+68 -7): the door, import of checkFieldCompleteness / FIELD_CHOICE_WITHOUT_OPTIONS, options / picklist TSDoc and describes, exclusivity comment",
  "packages/spec/src/data/field.test.ts (+77 -1): Choice-source pin block, and one option on the :2155 radio fixture",
  "packages/spec/src/data/picklist.test.ts (+14 -6): the neither pin rewritten as a refusal pin",
  "packages/spec/src/data/field-autonumber-default-unique.test.ts (+2 -1)",
  "packages/spec/src/data/filter-number-comparand-declared-type.ts (+3)",
  "packages/spec/src/data/filter-text-operator-declared-type.ts (+3)",
  "packages/metadata-protocol/src/protocol.stored-conversions.test.ts (+37 -1)",
  "packages/metadata-protocol/src/protocol.stored-migration.test.ts (+28 -2)",
  "content/docs/references/data/field.mdx, data/object.mdx, system/migration.mdx (regenerated)",
  "content/docs/deployment/troubleshooting.mdx, data-modeling/validation-rules.mdx, data-modeling/field-types.mdx, data-modeling/formulas.mdx (prose)"
 ],
 "fixture_census": [
  "spec field.test.ts:2155 (radio + multiple:false): oversight; +1 option",
  "spec field-autonumber-default-unique.test.ts:45 (minimalField): oversight; select / radio get 1 option",
  "spec filter-number-comparand-declared-type.ts fixtureFieldFor (:705-713): oversight; SINGLE_OPTION_TYPES get 1 option, and the interface gains optional options",
  "spec filter-text-operator-declared-type.ts fixtureFieldFor (:417-423): same",
  "spec picklist.test.ts:129 (2 tests): FLIPPED. It pinned the old acceptance ('neither is the completeness gate's error, not a parse refusal') and is now a refusal pin at options; its checkFieldCompleteness assertions are unchanged",
  "metadata-protocol: 9 tests (stored-conversions 2, stored-migration 7) from legacyObjectRow's status select: oversight (the row tests conditionalRequired); +1 option {label: 'Sent', value: 'sent'} in both files",
  "beyond the census, no red: canonicalObjectRow +1 option (its doc says canonical)",
  "every other suite run (objectql, lint, metadata, runtime, the rest of metadata-protocol and spec): 0 reds caused by the door"
 ],
 "semver": "@objectstack/spec minor with a BREAKING header and a bang summary. Gate lines: 'check-adr-0087-registration: 1 declared-breaking changeset(s), each carrying an ADR-0087 disposition'; 'This diff introduces no major bump'; 'LEVEL AXIS: this PR declares clause-② yes, and no package whose packages/**/src/** it moves is graded patch'. No other package publishes a change.",
 "a6_blueprint": "Inside objectstack and objectui, nothing expands a blueprint into FieldSchema input. The only in-repo mentions are the spec schema, its tests, the cli eval harness's doc comment, and objectui's chat progress UI. apply_blueprint is outside both repos. solution-blueprint.zod.ts's own header says the expansion is validated by the per-type schema at write time, so the door reaches blueprint output at that write: refused loudly, not stored. The gap is that the blueprint schema accepts what the door refuses (BlueprintFieldSchema.options optional :88; StrictField.options nullable :320). It is named in Acceptance notes for the PM to file; solution-blueprint.zod.ts is not edited.",
 "adr_0087_marker": "not-required (no-migration-prescription). The change narrows the validity of two existing keys (options, picklist) and removes, renames or re-shapes none, so there is no tombstone and nothing for objectstack migrate meta to rewrite. Which choices a sourceless select meant is authoring intent no conversion can invent. It is the precedent 0fb8760bec's category. Production sys_metadata is unmeasurable here, so the marker text takes the ruling's 'some rows exist' arm: new writes are refused at parse; stored rows keep their bytes and are read and named (_diagnostics.valid false, /meta/diagnostics, counted invalid at boot, the field/choice-without-options boot line). That arm is pinned in metadata-protocol. The other categories are closed on facts: the package publishes; no id covers this rule; it is a schema narrowing, not a runtime-interface-only or type-surface-only change. The gate accepted it."
}

Generated by Claude Code

ACCEPT — PR #21390 @ `ee5b089b`

domain:spec seat 2 (session_01YDt3PzwfrkuFzUBF89WPmM), holder of claim 5947645436 · 2026-10-02T10:29Z

Shape (read on GitHub): a draft against main. The first line is Fixes #20827, and Clause-②: yes sits at a line start. 16 files, all inside the claim surface, plus canonicalObjectRow's one option in a metadata-protocol file the claim names (its doc said "already canonical").
Contract review: at-tier PASS 5950368115 on this exact head.
CI on ee5b089b: 33 success and 2 skipped by design (Console Pin Gate with no .objectui-sha change, and the opt-in packed-tarball smoke).
Governed surface: check-governed-merges --pr 21390 reads NOT governed, 344 changed lines.
Ruling A (5910124148), item by item:
- The door: at FieldSchema's superRefine, on the options path, beside the reference check (0fb8760bec), with a prescription naming both keys.
- The predicate: checkFieldCompleteness's own, read rather than restated. So options: [] is the same hole, a picklist is a source, and the types are exactly select / radio.
- Release: minor with a BREAKING header and the ADR-0087 marker not-required (no-migration-prescription), the precedent's category. The stored-row arm is the ruling's "some" arm, pinned in @objectstack/metadata-protocol.
- Unchanged: ADR-0078's author-time rule and the registration warning.
The census matched step one (5917187437) exactly. Every red is fixed by one option, and the picklist pin is now a refusal pin. The ablation went red as predicted (8 spec and 3 metadata-protocol pins), and the restore went green.
Prose read sentence by sentence by this seat:
- the changeset, including the stored-row paragraph, which names /meta/diagnostics and the boot log and states what the --stored preview does and does not count;
- the door's comment and message;
- the options / picklist TSDoc and describes;
- the four hand-written docs pages. The multiselect row now says options are optional (free-form), which is the completeness module's measured NON-rule; the old "Required" was wrong.
Accepted as is:
- Clause-②: yes, where yes (narrowing) would be fuller;
- the PR title feat! against the changeset's fix!.
The review judged both optional.

Out-of-scope findings:

The objectstack-upgrade skill's os:check block teaches an optionless select (skills/objectstack-upgrade/references/examples-upgrade.md:105), which this door refuses at parse (check:skill-examples only type-checks). → filed as finding(skills): the objectstack-upgrade skill's "v17-canonical shapes, compiled" block authors a select with no options, which FieldSchema refuses once PR #21390 lands #21392 for the skills lane (Tier H). It should ship in the same release as this PR.
The blueprint schema accepts what the door refuses: solution-blueprint.zod.ts:88 (BlueprintFieldSchema.options optional) and :320 (StrictField.options nullable). → noted, not filed: nothing in either repo expands a blueprint into FieldSchema input; apply_blueprint lives outside both, so reach is not measured. The module header says the expansion is validated per type at write, so the refusal is loud there.
ADR-0078's § 4 sentence and its first Non-goal ("No hard Zod .refine() …") now trail two maintainer rulings that put a parse refusal in front of the author-time rule: this one, and the reference door (0fb8760bec). The ruling governs. → carrier: the maintainer. docs/adr/** is Tier H; this seat raises it in its report to the maintainer, not as a card.
objectui's derivation test (object-metadata-write-guard.derivation.test.ts, "the installed server still ACCEPTS a choice with no options") turns red by design on objectui's next @objectstack/spec bump, and its own comment prescribes the rewrite. → carrier: the objectui lane at that bump. It is not a hazard for this repo's main: the Console Pin Gate builds without running objectui tests.

Next: ready, auto-merge, the queue.

Generated by Claude Code

Landed: PR #21390 → `c52c49d96e`

domain:spec seat 2 (session_01YDt3PzwfrkuFzUBF89WPmM), holder of claim 5947645436 · 2026-10-02T10:55Z

Landed: PR feat(spec)!: FieldSchema refuses a select / radio with neither options nor picklist #21390 went through the merge queue as c52c49d96e, with one parent (69a12a0952). This card closed completed by its Fixes line.
Blob check against the ACCEPTed head ee5b089b (ACCEPT 5950415930, at-tier PASS 5950368115): 16 of 16 files are blob-equal, the three generated reference pages included.
Delivered (ruling A, 5910124148, step two): FieldSchema refuses a select / radio with neither a non-empty options nor a picklist, at parse, on the options path, with a prescription naming both keys.
- The predicate is ADR-0078's completeness check, read rather than restated.
- Stored rows keep their bytes and are read and named (_diagnostics, /meta/diagnostics, the boot log).
- Studio's half (objectui#11253) was already in the pinned console.
Ships in the same release as: finding(skills): the objectstack-upgrade skill's "v17-canonical shapes, compiled" block authors a select with no options, which FieldSchema refuses once PR #21390 lands #21392 (domain:skills). The objectstack-upgrade skill's os:check block authors an optionless select, which this door refuses at parse. Neither publishes on merge.
Carried elsewhere:
- objectui's derivation pin, which turns red on objectui's next @objectstack/spec bump, belongs to the objectui lane at that bump;
- ADR-0078 § 4 and its first Non-goal trail this ruling and the reference one. They are raised to the maintainer (docs/adr/** is Tier H);
- the blueprint schema's looser options is noted, not filed: reach was not measured, because the expansion lives outside both repos.
State: pm:dispatched is removed in this act. Domain, area and type labels stay.

Generated by Claude Code

feat(spec): the `picklist` metadata kind — a shared option list selec…

docs(spec): field.useGrouping is live at the objectui pin, and its do…

feat(spec)!: FieldSchema refuses a select / radio with neither option…

docs(skills): the upgrade skill's v17-canonical Lead declares its sel…

Navigation Menu

Repository navigation

A `select` / `radio` field with neither `options` nor `picklist`: refuse it at the `FieldSchema` door (an accept-set narrowing), or keep it at the ADR-0078 completeness gate? (split from #19518) #20827

Governing text

What the #19518 dev measured (branch `claude/issue-19518-picklist-kind`)

Triage: grade completed — `enhancement` · `priority:p2` · `area:records` added beside `domain:spec` · `pm:blocked`

Triage: objectstack-ai/objectui#11253 landed (objectui `1563d3e10b`, PR objectui#11287). By the pin rule, `pm:blocked` → `pm:on-hold`, not `pm:queue`

Unlock scan: the restart condition holds, so `pm:on-hold` → `pm:queue`

ACCEPT — PR #21390 @ `ee5b089b`

Landed: PR #21390 → `c52c49d96e`

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

A select / radio field with neither options nor picklist: refuse it at the FieldSchema door (an accept-set narrowing), or keep it at the ADR-0078 completeness gate? (split from #19518) #20827

Description

Governing text

What the #19518 dev measured (branch claude/issue-19518-picklist-kind)

Activity

objectstack-fleet commented on Sep 30, 2026

Triage: grade completed — enhancement · priority:p2 · area:records added beside domain:spec · pm:blocked

objectstack-fleet commented on Oct 1, 2026

Triage: objectstack-ai/objectui#11253 landed (objectui 1563d3e10b, PR objectui#11287). By the pin rule, pm:blocked → pm:on-hold, not pm:queue

objectstack-fleet commented on Oct 2, 2026

Unlock scan: the restart condition holds, so pm:on-hold → pm:queue

objectstack-fleet commented on Oct 2, 2026

objectstack-fleet commented on Oct 2, 2026

objectstack-fleet commented on Oct 2, 2026

ACCEPT — PR #21390 @ ee5b089b

objectstack-fleet commented on Oct 2, 2026

Landed: PR #21390 → c52c49d96e

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

A `select` / `radio` field with neither `options` nor `picklist`: refuse it at the `FieldSchema` door (an accept-set narrowing), or keep it at the ADR-0078 completeness gate? (split from #19518) #20827

What the #19518 dev measured (branch `claude/issue-19518-picklist-kind`)

Triage: grade completed — `enhancement` · `priority:p2` · `area:records` added beside `domain:spec` · `pm:blocked`

Triage: objectstack-ai/objectui#11253 landed (objectui `1563d3e10b`, PR objectui#11287). By the pin rule, `pm:blocked` → `pm:on-hold`, not `pm:queue`

Unlock scan: the restart condition holds, so `pm:on-hold` → `pm:queue`

ACCEPT — PR #21390 @ `ee5b089b`

Landed: PR #21390 → `c52c49d96e`