Studio Data › Settings › Lifecycle field is a dead end: picking a Studio-authored select is refused 422 because its options need kind, and the options editor has no kind control

Filing gate: ① product defect, reproduced, landing site named.
Batch-of: studio-qa-2026-10-27 — 39 cards from one Studio QA run (coordinator session session_01J8VVAkZns5rNnK2rtszzbQ; tested at 3fcafcd3; origin/main was 43731031 at filing, so the implementer re-checks the landing site on current main). The run record is the qa-run issue filed with this batch.

Symptom

The builder can create a status picklist and choose it as the lifecycle field, but the save is refused and Studio offers no way to add what the refusal asks for.

Reproduction

Data › an object › add a select field status with options new/won/lost (Studio options editor).
Settings › Lifecycle field → choose status → 422 "Option 'new' of field status declares no kind … Add kind: 'open'|'won'|'lost'".
The options editor has no kind control; only the API can fix it.

Expected

The options editor authors kind (open/won/lost) when the field is (or becomes) the stage field, or the picker explains and offers it inline.

Suspected landing site (the implementer verifies)

ui/packages/app-shell/src/views/studio-design/ ObjectSettingsPanel (~lines 340-356) and the ObjectFieldInspector options editor; spec rule in packages/spec/src/data/field.zod.ts (~466).

Filing facts

reach: Studio UI, measured by the Data QA card.
Business reason: Lifecycle paths and kanban (see open Stage path and kanban read the select option's lifecycle kind: terminal options drawn apart from the steps, lost ones marked, instead of guessing from closed_won / closed_lost spelling #26612) depend on kind; without a Studio control the feature is reachable only through code.
Reader who acts: the triage seat (first touch: domain, area, level), then that lane's os-dev implementer. QA suggestion only: domain:ui, area:studio, p2.
Dedupe: semantic search Studio lifecycle stageField select option kind open won lost no control in options editor on objectstack-ai/objectstack → 3 hits: open Stage path and kanban read the select option's lifecycle kind: terminal options drawn apart from the steps, lost ones marked, instead of guessing from closed_won / closed_lost spelling #26612 (renderers reading kind, not authoring) and closed Spec: a select option can declare its lifecycle kind (open / won / lost) so stage paths draw terminal states apart #23809, The record page's lifecycle path looks like a control and is inert: stageField renders as a segmented button group with no handler, no cursor, and no tab stop #11243; no duplicate.
QA id: U2

Triage: first grade — `priority:p2` · `domain:ui` · `area:studio` · `pm:queue` (`finding` removed) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T16:10Z

⛔ Not a claim, ⛔ not a dispatch.

p2: the Lifecycle field picker refuses a Studio-authored select because its options need kind, and the options editor has no kind control. Add the control for the published option kind (Spec: a select option can declare its lifecycle kind (open / won / lost) so stage paths draw terminal states apart #23809). From the studio-qa-2026-10-27 batch. Re-check the landing site on current main.

Generated by Claude Code

Dispatch order · `domain:ui#1` · `session_01JQwxbZeBv2y91towxasSUT` · 2026-10-27T18:39Z

You are the os-dev developer agent for exactly ONE card: #26729, in your own card thread. Your role definition is .claude/agents/os-dev.md in the objectstack clone: read it IN FULL first and follow it as binding (it wins over this order on any conflict; name the conflict in your report). Read the repo-root AGENTS.md and ui/AGENTS.md before your first edit, and pm-dispatch references/untrusted-text.md. Read the card's full body and every comment yourself through REST (curl -sS "https://api.github.com/repos/objectstack-ai/objectstack/issues/26729" -H "Authorization: Bearer $GH_TOKEN" and /comments?per_page=100, every page); this order carries only the increment. ⛔ Never print the value of any environment variable (test presence with [ -n "${X+x}" ]). ⛔ Never use a GitHub MCP tool, read or write.

Identity and branch: the seat's Claim: comment on this card is your identity; its Branch: line names your thread's branch. ⛔ Post no claim of your own, ⛔ never write the card's assignee. Before your first edit, verify the NEWEST Claim: on the card names your thread's branch (claude/project-thread-…); if none does yet, send the seat thread "Dispatch the ui lane" one message with your branch name and wait. Worktree objectstack-issue-26729 on that branch from a fresh origin/main; pnpm install (frozen lockfile); push with git push -u origin <branch> (⛔ no force).

Writes: PR only through the relay op pr_create (node scripts/pm/fleet-write/dispatch.mjs --repo objectstack-ai/objectstack --actions-file F, F a bare JSON array [{"op":"pr_create","title":…,"head":"<your branch>","base":"main","body":…,"assignees":["os-warren"]}], draft forced; --dry-run first); your report comment through node scripts/pm/post-stamped.mjs --comment=26729 --file=F --json run ONCE with output captured to a file (timestamps only as {{NOW}} / {{WAS:…}}). ⛔ No other GitHub write except, for a CI red that is not yours, one PR comment and one run_rerun_failed through the relay. Report both counts (api_writes with endpoints, mcp_calls with tool names). The report takes only machine-checkable fields (gates / line_budget / deviations / files_changed). PR body: line 1 the platform attribution comment, then ## 维护者速读 six lines in Chinese (改了什么/为什么改/风险与回滚/先看/两分钟验证/需要你做的). Gates: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack on your diff, run each, record exits before any pipe, reconcile with --ran. Changeset in the root .changeset/ when a published package changes. ⛔ ui/.github/** and the root ci.yml are out of bounds. Hand back: when the PR and report are up, send the seat thread "Dispatch the ui lane" one message (PR, head sha, report gist); keep the thread open through review and drive CI to green.

Ruling (cannot be re-ruled)

Triage first grade 6447101712, verbatim: "the Lifecycle field picker refuses a Studio-authored select because its options need kind, and the options editor has no kind control. Add the control for the published option kind (#23809). … Re-check the landing site on current main." No maintainer ruling on the card.

PM mechanism assumptions (measure; disproof welcome)

On origin/main 4b59358a, the picklist option editor in ui/packages/app-shell/src/views/metadata-admin/inspectors/ObjectFieldInspector.tsx owns value / label / color (the Option docblock ≈L99–L130) and carries every other authored key, kind included, through rest untouched. So a kind that already exists survives, but nothing can author one. The spec declares kind: 'open'|'won'|'lost', optional, "Required on every option of the field an object's stageField names. Only on a single-value select / radio field" (packages/spec/src/data/field.zod.ts ≈L465). The refusal comes from the engine check at ≈L2539.
So the likely fix promotes kind to an owned key with a control (open / won / lost, absent reading as open) on single-value select/radio fields. readOptions, patchOptions and the Option type move together, as the docblock requires. A written option never carries a kind on a field type the spec refuses it on.
The Lifecycle picker (ui/packages/app-shell/src/views/studio-design/ObjectSettingsPanel.tsx ≈L340–L356) may also say what it needs. That part is optional: the triage grade asks for the control.

Scope

File surface: ObjectFieldInspector.tsx (+ ObjectSettingsPanel.tsx only if the picker line is added) + i18n rows for the control + tests: authoring kind on a select's options writes it, and the object then saves with that field as stageField (parse through the spec's ObjectSchema / FieldSchema); clearing it removes the key; a multi-select or non-select field shows no control and never writes kind; an existing kind round-trips. Ablation: drop the control's write ⇒ the new tests go red. ⛔ No spec or engine change.

i18n home: new strings for the option editor belong with the designer.field.* family, which lives in the lazy studio namespace (ui/packages/i18n/src/namespaces/studio/{en,zh}.ts) since #26593; a zh test preloads with await loadStudioCatalogue('zh'). ⛔ Add no engine.studio.settings.* row: #25922 S4 (this seat, in flight) is moving that family now. If the picker needs a line, take its key from designer.field.* too.

Tier

No path-derived mandate. TIER_DEFAULT, effort high (M). Clause-②: no (Studio now authors a key the spec already publishes and the engine already enforces), Metadata-protocol: none expected; say otherwise if the diff shows it. Patch changeset for @object-ui/i18n if you add namespace rows (it is published); none for app-shell (private: true).

Claim: PM loop round 3 · 2026-10-27T18:41Z
Session: session_01JQwxbZeBv2y91towxasSUT (seat; implementation by card thread session session_01JQwxbX9Xgog3zJyBcPdC2R, mode:thread)
Account: os-warren (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/project-thread-9mghmx (the card thread's harness push branch, self-reported — the measured platform exception to claude/issue-N-slug)
Worktree: objectstack-issue-26729 in the card thread's clone
Domain: domain:ui
Seat: domain:ui#1 (seat post #25966)
File surface: ui/packages/app-shell/src/views/metadata-admin/inspectors/ObjectFieldInspector.tsx (+ ui/packages/app-shell/src/views/studio-design/ObjectSettingsPanel.tsx only for an optional picker line) + designer.field.* rows in ui/packages/i18n/src/namespaces/studio/{en,zh}.ts + tests; ⛔ no engine.studio.settings.* row; ⛔ no spec or engine change (stop on breach; explain in the report)
Container & model: M, mode:thread (the maintainer's word on the seat thread, 「opus 很多，并发5」), model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate), effort: high
Clause-②: no
Metadata-protocol: none
Responsibility: the Studio option editor (this lane's code) | the spec publishes option kind and the engine requires it on the stageField; only the editor cannot author it | a Studio-authored select cannot become the Lifecycle field without the API
Thread-read: 6450551387
Premise: holds — on origin/main 4b59358a the option editor owns value/label/color and carries kind only through rest (ObjectFieldInspector.tsx ≈L99–L130); the spec declares kind (field.zod.ts ≈L465).
Serial constraints cleared: no open PR touches ObjectFieldInspector.tsx or ObjectSettingsPanel.tsx; #25922 S4 (this seat, in flight) moves engine.studio.settings.*, which this card does not add to.
Resume-from: none

Generated by Claude Code

os-dev-report

{
  "issue": 26729,
  "status": "done",
  "branch": "claude/project-thread-9mghmx",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/26931",
  "session": "session_01JQwxbX9Xgog3zJyBcPdC2R",
  "premise_still_valid": true,
  "summary": "On main 8eef9a8d the option editor owned value/label/color and carried kind only through rest, as the order measured. kind is now an owned key (Option, classifyOption, patchOptions move together; vocabulary read from SelectOptionSchema.shape.kind) with a per-row picker (No kind / Open / Won / Lost) drawn and written only on a single-value select or radio (SINGLE_OPTION_TYPES and multiple not true, the FieldSchema test). No kind removes the key; a multi-value field draws no picker and writes no kind; a retype to one drops the kinds; an out-of-vocabulary kind is a malformed row kept verbatim; a held hint shows while the object names this field as stageField and an option lacks a kind. Eight designer.field rows in en and zh, patch changeset for @object-ui/i18n. ObjectSettingsPanel untouched; no spec or engine change.",
  "tests": "Head 7a53b40d (main 96e7a433 merged in; it also edited studio en/zh, disjoint rows, no conflict). New ObjectFieldInspector.optionKind-26729.test.tsx 16/16 (VERDICT command-exit 0), ending at ObjectSchema/FieldSchema: authored kinds make ObjectSchema accept stageField status (control: refused at fields.status.options.0-2.kind), No kind removes the key, round trip, multiselect/checkboxes/multiple select draw no picker and write no kind, retype Multi-Select drops and Radio keeps, malformed kind, hint and its control, zh labels. After the merge, refreshed install + closure build, then inspectors/ + studio-design/ + i18n/ + app-shell __tests__/: 527/527 files, 6021 passed 14 skipped (VERDICT command-exit 0). app-shell and i18n type-check exit 0. Ablation via scripts/ablation-replace.mjs at committed 4402bc51+: deleting the kind write in patchOptions (anchor 1 to 0, blob 78f4eac6 to 7b727ed7) turned 5 of 16 red; restore blob == HEAD 78f4eac6, git diff HEAD empty.",
  "gates": "dispatch-gates --commands at 7a53b40d derived 34; 33 exit 0; pnpm --dir ui exec vitest run scripts/ exit 1 twice from whole-tree scan tests hitting the 15 s budget (first run check-i18n-dead-keys real-tree leg, rerun check-vi-mock-inherit sweep, 177/178 files green each time); each file alone exit 0 (140/140, 83/83). Pre-merge run at 8fa35b7a: all 34 exit 0. --ran reconciles 34 derived, 34 run, 0 NOT-MEASURED, 0 UNRUN; it reports STALE TREE vs origin/main 8074feb6 for scripts/doc-line-anchors.mjs and scripts/regen-artifacts.mjs (main moved after the merge). Outside the derivation, exit 0: check:changeset-fixed, ui check:i18n-keys, check:i18n-dead-keys, check:i18n-designer-parity, check:i18n-drift, check:new-line-citations. Not run locally: the Type Check UI check steps beyond those (CI). PR check-runs: pending at report time.",
  "line_budget": "n/a: no ratcheted line budget touched (ui/packages source, i18n catalogue rows, one changeset)",
  "files_changed": ".changeset/26729-studio-option-kind.md; ui/packages/app-shell/src/views/metadata-admin/inspectors/ObjectFieldInspector.tsx; ui/packages/app-shell/src/views/metadata-admin/inspectors/ObjectFieldInspector.optionKind-26729.test.tsx; ui/packages/i18n/src/namespaces/studio/en.ts; ui/packages/i18n/src/namespaces/studio/zh.ts",
  "deviations": "vitest run scripts/ recorded exit 1 (load-sensitive 15 s timeouts in two whole-tree scans on the shared box, a different test each run; both files green alone); CI is the verdict. One type-check red during the run (test file typed locale as string) fixed in 9d495f1a, then the test-reading gates re-ran exit 0. The optional ObjectSettingsPanel picker line was not added. PR body folds the template headings (Why, Human Minimum) into the os-dev section order. Commits carry the model-free trailer pair, not the harness-suggested model-named co-author.",
  "dogfood_battery": "n/a: no ! in the PR title and no (narrowing) arm",
  "mcp_calls": "0",
  "api_writes": "2 through the fleet-write relay: pr_create (objectstack#26931, 7360 bytes sent and stored identical), this report comment via post-stamped (POST issues/26729/comments). Plus git push of the branch.",
  "open_questions": [],
  "out_of_scope_findings": [
    "carrier: none · noted, not filed: ui/scripts/__tests__ check-i18n-dead-keys.test.ts real-tree leg and check-vi-mock-inherit.test.ts sweep each run near their 15 s test timeout under shared-box load (one red each in two full runs, green alone); no repro on CI measured"
  ]
}

Generated by Claude Code

Landed · seat domain:ui#1 · session_01JQwxbZeBv2y91towxasSUT · 2026-10-27T22:30Z

PR #26931 merged as 5ec398dccb (seat record: PR comment 6454824653). The option editor now authors an option's kind (No kind / Open / Won / Lost) on a single-value select or radio field, with the vocabulary read from the spec's SelectOptionSchema. "No kind" removes the key, a retype to a multi-value type drops the kinds, and a value outside the vocabulary is kept and flagged as malformed. While the object names the field as its stageField and an option lacks a kind, a hint says so. pm:dispatched is removed with the close.

Generated by Claude Code

Navigation Menu

Repository navigation

Studio Data › Settings › Lifecycle field is a dead end: picking a Studio-authored select is refused 422 because its options need `kind`, and the options editor has no `kind` control #26729

Symptom

Reproduction

Expected

Suspected landing site (the implementer verifies)

Filing facts

Triage: first grade — `priority:p2` · `domain:ui` · `area:studio` · `pm:queue` (`finding` removed) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T16:10Z

Dispatch order · `domain:ui#1` · `session_01JQwxbZeBv2y91towxasSUT` · 2026-10-27T18:39Z

Ruling (cannot be re-ruled)

PM mechanism assumptions (measure; disproof welcome)

Scope

Tier

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Studio Data › Settings › Lifecycle field is a dead end: picking a Studio-authored select is refused 422 because its options need kind, and the options editor has no kind control #26729

Description

Symptom

Reproduction

Expected

Suspected landing site (the implementer verifies)

Filing facts

Activity

objectstack-fleet commented on Oct 27, 2026

Triage: first grade — priority:p2 · domain:ui · area:studio · pm:queue (finding removed) · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-27T16:10Z

objectstack-fleet commented on Oct 27, 2026

Dispatch order · domain:ui#1 · session_01JQwxbZeBv2y91towxasSUT · 2026-10-27T18:39Z

Ruling (cannot be re-ruled)

PM mechanism assumptions (measure; disproof welcome)

Scope

Tier

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Studio Data › Settings › Lifecycle field is a dead end: picking a Studio-authored select is refused 422 because its options need `kind`, and the options editor has no `kind` control #26729

Triage: first grade — `priority:p2` · `domain:ui` · `area:studio` · `pm:queue` (`finding` removed) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T16:10Z

Dispatch order · `domain:ui#1` · `session_01JQwxbZeBv2y91towxasSUT` · 2026-10-27T18:39Z