flow designer: a number column inside an objectList config field is a text cell, so a screen field's Min / Max are saved as strings the screen contract refuses

[objectstack-fleet]

Filing-gate class ① (a defect with a named location; reach: named real producer, read from source at the pin and measured at the engine, not driven in the designer). Filed by objectstack domain:spec seat 1 (session_01T9u38rswFp5Rw8DswRUReJ, seat post objectstack-ai/objectstack#6017), from the census of objectstack-ai/objectstack#21898 (report on that card). ⛔ Not graded or routed here; ⛔ not a claim. Actionable reader: whoever this repo's triage routes the flow inspector to. objectstack-ai/objectstack#21898 is waiting on the maintainer's call on how its build-time judge treats these values.

What an author sees

In Studio's flow designer, an author adds a number field to a screen node and types Min = 1, Max = 10. The node is saved as fields: [{ name: 'qty', type: 'number', min: '1', max: '10' }], with strings.

The same happens to a code-authored screen: editing any row of its fields list re-saves min: 0 as '0'.

The screen contract declares both bounds as numbers (ScreenFieldConfigSchema.min / .max are z.number()). The engine measured this at objectstack 833d57c9cf: the flow registers, and every run fails at the screen node with:

screen 'ask': config does not satisfy the screen contract — config.fields[0].min: Invalid input: expected number, received string; config.fields[0].max: …

If objectstack-ai/objectstack#21898 lands as recommended, the save itself is refused at nodes.N.config.fields.M.min.

Where (objectui at .objectui-sha 0abd4f9f8769)

• packages/app-shell/src/views/metadata-admin/inspectors/json-schema-to-fields.ts, columnsFor() (about :348-366): an objectList item property maps to reference, select, boolean, or else expression / text. FlowConfigColumn.kind has no number kind, so a type: 'number' / 'integer' property becomes a text column.
• packages/app-shell/src/views/metadata-admin/inspectors/FlowObjectListField.tsx:
  • rowsToList() (about :103-123) commits a text cell as v.trim(), a string;
  • toRows() (about :96) stringifies a stored number with String(v), so a round-trip turns a number into a string.
• The schema the inspector reads: the screen descriptor's published configSchema (objectstack packages/services/service-automation/src/builtin/screen-nodes.ts:134-135), where min / max are type: 'number'.

Fix direction (not ruled)

An objectList column gets a number kind for type: 'number' / 'integer' item properties. The column edits and commits a number, empty clears the key, and a stored number round-trips as a number. Two pins:

• a screen field's min / max authored in the inspector parse under the spec's screen field contract;
• editing another row of a code-authored fields list leaves min: 0 a number.

Dedupe: mcp__github__search_issues (objectstack-ai/objectui, semantic, closed included):

• flow designer objectList number column saved as string screen field min max → 1 hit, console: render the three new flow screen-field keys (numeric bound, help text, lookup target) exactly as the spec declares them — follows objectstack#17306 ruling A #9248 (closed; the runtime screen dialog's rendering, not the designer inspector);
• FlowObjectListField rowsToList number kind text cell → 2 hits, FlowObjectListField.commitCell 在 setRows updater 里 flush,触发 React setState-in-render 告警 #2838 and [P2] ListView 杂项属性实现（description/allowPrinting/rowHeight 补全） #749 (closed, unrelated).

Dedupe words: objectList number column text cell · screen field min max saved as string · columnsFor integer · rowsToList trim

[objectstack-fleet]

Path: approvals and automation — the flow designer | 缺项 (no item round-trips a number column of an objectList config field) | P1

Triage: first grade — bug · priority:p2 · domain:ui · area:workflow · pm:queue. An objectList column gets a number kind, and a stored number round-trips as a number

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-06T00:58Z. ⛔ Not a claim, ⛔ not a dispatch.

Triage: lands in packages/app-shell/src/views/metadata-admin/inspectors/json-schema-to-fields.ts (columnsFor, about :324–:370) and FlowObjectListField.tsx (toRows about :86–:96, rowsToList about :103–:123) ⇒ domain:ui; rationale: the inspector writes a shape the published screen contract refuses.

Verified on objectui main (fc3c2cc1cf):

• columnsFor maps an item property to reference, select, boolean, or else expression/text. There is no number kind, although the top-level field mapper above it (about :275) already has one.
• toRows stores String(v), and rowsToList commits v.trim(), so a number goes in and a string comes out.

Why p2: every run of such a flow fails at the screen node. Once objectstack-ai/objectstack#21898 lands (now domain:spec, re-graded in triage's 6005839208), the save is refused instead. The designer produces the refused shape either way, including when an author re-saves a code-authored screen they did not touch.

Direction:

• FlowConfigColumn gains a number kind for type: 'number'/'integer' item properties, the same mapping the top-level fields already use.
• A number column renders a number input and commits a number. An empty cell commits nothing.
• toRows and rowsToList keep a stored number a number.
• ⛔ No coercion on save of other columns' strings.
• Pins:
  • an inspector-authored screen field with min/max round-trips through the screen descriptor's configSchema with numbers;
  • re-saving a code-authored screen with min: 0 keeps 0.

Family. This is the second "the flow inspector writes a shape the node contract refuses" after objectui#11660 (merged in objectui#11661). A third face gets a closing card with an enumeration pin over every inspector column kind against its node's configSchema.

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 4
Session: session_015W8GBu6sBiqus2L2xjMsAL
Account: os-steve
Branch: claude/issue-11664-objectlist-number-column
Worktree: objectui-issue-11664
Domain: domain:ui
Seat: domain:ui#1
File surface: packages/app-shell/src/views/metadata-admin/inspectors/: json-schema-to-fields.ts (columnsFor, about :324–:370), FlowObjectListField.tsx (toRows about :86–:96, rowsToList about :103–:123, and the cell editor it renders), the FlowConfigColumn kind in flow-node-config.ts, the tests beside them, and .changeset/11664-*.md (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: opus (dispatch-gates --tier: no path-derived mandate; default tier)
Clause-②: no
Thread-read: 6007030030
Serial constraints cleared: none. No open PR and no in-flight claim touches these files. Read 2026-10-06T01:05Z.

Why Clause-②: no: an objectList column gains a number kind, so the inspector stops writing a string the screen contract refuses (triage 6007030030). FlowConfigColumn lives in the inspector's own module, which the @object-ui/app-shell entry does not reach; the dev verifies that on the built .d.ts. No spec key changes, and no export, prop, type member or i18n key is added to anything a package entry reaches.

[objectstack-fleet]

os-dev-report
{
"issue": 11664,
"status": "done",
"branch": "claude/issue-11664-objectlist-number-column",
"pr": "#11670",
"session": "session_015W8GBu6sBiqus2L2xjMsAL",
"premise_still_valid": true,
"summary": "Draft PR objectui#11670 at d8002fe, based on fc3c2cc, with main f9f4a62 merged once as 91d45ca. Zone 1 is implemented as ruled. FlowConfigColumn['kind'] gains 'number'. columnsFor maps number / integer item properties to it through the existing scalarField mapping. The cell is an Input type=number flushed on blur. A typed 0 commits 0; an empty cell drops the key; a non-numeric entry commits nothing. toRows / rowsToList keep stored numbers numbers; a string stored in a number column is kept verbatim; other columns' strings are untouched. The premise held live: the old code saved min '1' / max '10' and the trigger answered 400 FLOW_FAILED (screen contract, expected number, received string). The live drive also found a second reason pin 2 failed, in the claimed file. The inspector renders the hand-written fallback columns until GET /automation/actions answers, and FlowObjectListField built its rows against them. So the first edit of a code-authored screen field dropped min / max, plus options, defaultValue, placeholder, inlineHelpText and reference; on main they were dropped, not stringified. Fixed in 19c1e69: each row keeps its stored item, and a column that arrives later, or changes kind, reads its cell from that item. Nothing is written when the schema arrives. After both fixes, live: authored Min 1 / Max 10 saved as numbers, a code-authored min 0 / max 5 survived a Label edit, and both runs paused at the screen with the bounds. Clause-② no holds: the dist/index.d.ts walk reaches 164 files and no inspector module.",
"tests": "All exits were written to a file as they ran. At final head d8002fe, from the objectui repo root under os-verify-lock: (1) pnpm exec vitest run on FlowNodeInspector.screenNumberBounds-11664.test.tsx, the four FlowObjectListField.* suites and json-schema-to-fields.test.ts: 6 files, 56 tests passed. (2) pnpm exec vitest related --run on FlowObjectListField.tsx: 113 files, 1021 tests passed. This is a DECLARED narrowing: the commits after the merge touch only FlowObjectListField.tsx, its test and the changeset; the full farm is CI's. (3) The full pnpm exec vitest run packages/app-shell/ ran twice. At 14f9b48: 1012 files passed, 1 skipped, 10043 tests passed (VITEST_EXIT=0 captured in-command). At 91d45ca after the merge: 1013 passed, 1 failed, 1 skipped. The failure is AppContent.deniedVsUnpublished.test.tsx 'that way back follows the DECLARED landing': a network-escape guard on reads of /api/v1/meta, /meta/package and /meta/diagnostics under full load. Rerun alone it passed 15/15; this diff does not touch it. (4) turbo build of the app-shell dependency closure, then pnpm --filter @object-ui/app-shell type-check (tsc --noEmit and tsconfig.test.json, whose include covers src//.test.tsx), lint (0 errors; the single FlowObjectListField warning is react-hooks/refs at the rows map, also on main) and build (dist completeness: 984 emitted files): exit 0 each. (5) These check gates exit 0 at d8002fe: check:control-bytes, new-line-citations, changeset-claims, pending-changeset-literals, vi-mock-specifiers, vi-mock-inherit, vi-mock-override-shape, test-path-roots, spec-symbols, designer-field-key-parity, i18n-keys, i18n-designer-parity, installed-pin-claims, unreferenced-sources, action-forward-parity, handler-key-reads, shell-escape-residue, check-changeset-presence.mjs and check-changeset-no-major.mjs. A grep -P for control bytes over the 5 changed files found none. ABLATION: 11 legs with objectstack scripts/ablation-replace.mjs in WRAP mode on the committed head d8002fe. Each leg's anchor went from 1 to 0 and its blob changed on disk; each restore was proven (blob == HEAD, git diff HEAD empty), and a final hash check of both files matched HEAD. No dist is involved: the test imports src. Red counts out of 10: columnsFor number mapping 9; the cell keeps a stored number 7; Number() coercion of a stored string 1; rowsToList commits a number 8; rowsToList keeps a stored string 1; empty commits nothing 4; the cell parses its input 4; a non-finite parse never becomes a string 1; type=number 1; the late-column re-read 7; its kind-change half 1. An earlier 9-leg set on the pre-refactor code was all red too. LIVE: the console vite ran from the worktree on port 5216, against objectstack main faf8dce482's showcase on port 4116 (own worktree, --fresh), in Playwright Chromium at /opt/pw-browsers/chromium with the seeded admin session cookie. A flow was seeded by PUT /api/v1/meta/flow/NAME, edited in the designer, published, read back by GET and run by POST /api/v1/automation/NAME/trigger. BEFORE (the 3 source files swapped to fc3c2cc, restore proven): the authored cells are text; saved min '1' / max '10' strings; trigger 400 FLOW_FAILED 'config.fields[0].min: Invalid input: expected number, received string'. The code-authored min 0 / max 5 are dropped on a Label edit. AFTER (d995c7f FlowObjectListField, = HEAD): the cells are type=number; saved min 1 / max 10 numbers; the trigger pauses at screen ask with the bounds. The code-authored cells show 0 / 5, saved numbers, and the trigger pauses with min 0 / max 5. The served screen configSchema equals the test's transcribed fixture as canonical JSON. CLAUSE-② fence: on the final build, the walk of dist/index.d.ts relative imports reaches 164 declaration files, 22 under views/metadata-admin (positive control). It reaches NOT flow-node-config.d.ts, FlowObjectListField.d.ts, json-schema-to-fields.d.ts or inspectors/index.d.ts, and the built flow-node-config.d.ts carries the new 'number' member. CI at d8002fe when the PR was read: 42 checks, 24 completed with 0 failures, 18 in_progress.",
"mcp_calls": "0 — none (card and PR reads were single-resource REST GETs via gh api)",
"api_writes": "3. (1) pr_create via the scripts/pm/fleet-write relay: POST /repos/objectstack-ai/objectui/pulls, request fw-20261006T040516Z-81f635, run 37412034138, read-back identical (10319 bytes). (2) The PR assignee via scripts/pm/label-write.mjs --assign os-steve through the relay: POST /repos//issues/11670/assignees, request fw-20261006T040601Z-ae849c, run 37412092613; read-back matches. (3) This os-dev-report comment via scripts/pm/post-stamped.mjs --comment=11664: POST /repos//issues/11664/comments. Plus git push of the branch (not REST).",
"gates": [
"vitest targeted (6 files / 56 tests) exit 0 @d8002fe",
"vitest related FlowObjectListField.tsx (113 files / 1021 tests) exit 0 @d8002fe — declared narrowing",
"vitest packages/app-shell/ exit 0 @14f9b48; exit 1 @91d45ca (1 unrelated network-escape flake, 15/15 alone)",
"app-shell type-check exit 0 @d8002fe",
"app-shell lint exit 0 @d8002fe",
"app-shell build exit 0 @d8002fe",
"check: touched set (17) + changeset-presence + changeset-no-major exit 0 @d8002fe",
"ablation 11 legs all red, all restores proven @d8002fe",
"live before/after measured (objectstack main faf8dce482)",
"CI: in_progress at report time (24/42 completed, 0 failed)"
],
"line_budget": "n/a — no skills/ or governed surface touched",
"files_changed": [
".changeset/11664-objectlist-number-column.md",
"packages/app-shell/src/views/metadata-admin/inspectors/FlowNodeInspector.screenNumberBounds-11664.test.tsx",
"packages/app-shell/src/views/metadata-admin/inspectors/FlowObjectListField.tsx",
"packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts",
"packages/app-shell/src/views/metadata-admin/inspectors/json-schema-to-fields.ts"
],
"deviations": [
"Beyond Zone 3's route, inside the claimed file surface: commit 19c1e69 makes FlowObjectListField rows re-read a column that arrives after they were built, or whose kind changed, from the stored item. The live drive showed Zone 1 pin 2 failing in the product without it (first-selected node: min / max dropped). Pinned and ablated; disclosed in the PR body.",
"The final suite was narrowed to vitest related on FlowObjectListField.tsx at d8002fe (113 files). The full app-shell suite ran at 14f9b48 (green) and at 91d45ca (1 unrelated flake). Declared in the PR body.",
"Zone 2 #2: the cell reuses the Input type=number control and the empty-commits-nothing rule of InspectorNumberField, not the wrapper itself. The wrapper renders its own label and commits on each keystroke; the row has its own label and flushes on blur."
],
"open_questions": [],
"out_of_scope_findings": [
"carrier: 承接者:无 · noted, not filed — offline-only path. With no served configSchema, a re-save of a screen fields list drops every key the hand-written columns do not list (min, max, options, defaultValue, placeholder, inlineHelpText, reference). Measured in a scratch test at 14f9b48. No public door measured: a backend that publishes the screen descriptor leaves that table once its answer lands. In PR Acceptance notes. Dedupe words: offline screen fields columns drop keys · fieldsForNodeType screen min max missing · rowsToList drops non-column keys",
"carrier: 承接者:无 · noted, not filed — the descriptor publishes screen options[].value and defaultValue with no type, so they are text columns, and a stored number there still saves as a string through String(v). Spec: both z.unknown(), so nothing refuses it. Outside the ruling, which covers number columns. In PR Acceptance notes. Dedupe words: untyped configSchema property text column stringifies number · options value number saved as string",
"carrier: 承接者:无 · noted, not filed — at 91d45ca, AppContent.deniedVsUnpublished.test.tsx 'that way back follows the DECLARED landing' failed once under full parallel load on the network-escape guard (/api/v1/meta, /meta/package, /meta/diagnostics). Alone it passes 15/15; this diff does not touch it; main's f9f4a62 changed HomePage.tsx. Dedupe words: AppContent deniedVsUnpublished network escape flake · declared landing way back"
]
}

---

Generated by Claude Code

[objectstack-fleet]

Landed: PR objectui#11670 → main 5ba2555, verified by content

domain:ui execution seat 1 @ objectui · session_015W8GBu6sBiqus2L2xjMsAL (os-steve) · 2026-10-06T04:39Z.

• The merge. It went through the merge queue as squash commit 5ba2555 (one parent, a600924), an ancestor of origin/main. Its +/- lines are identical to the PR head d8002fe diffed from its merge base: 5 files, +545/−14.

• Content check against the first parent:

  reading	a600924	5ba2555
  scalarField(prop)?.kind === 'number' in inspectors/json-schema-to-fields.ts (columnsFor's number mapping)	0	1
  | 'number' in FlowConfigColumn['kind'] (flow-node-config.ts)	0	1
  function numberCell in FlowObjectListField.tsx (the cell parses a number; empty commits nothing)	0	1
  source: Record<string, unknown>; on a row (the late-column re-read from the stored item)	0	1
  FlowNodeInspector.screenNumberBounds-11664.test.tsx exists	no	yes
  function rowsToList (control)	1	1

• Closures. The card closed completed through the PR's Fixes line. It was the only issue closed in that window. pm:dispatched is removed in this stroke.

• CI. The full farm on the PR head was 43 checks, 40 green and 3 expected skips. The AppContent.deniedVsUnpublished red the dev saw once under local full load did not recur in CI. The seat carries it as a possible recurrence of the closed objectui#10162.

• Left as noted, not filed:

  • With no served configSchema, the built-in screen form has no min/max column, so an offline re-save drops the keys it does not list.
  • The screen descriptor's untyped options[].value and defaultValue still save a stored number as a string through the text cell. The spec types both as z.unknown(), so this is outside this ruling.

---

Generated by Claude Code