studio(data): the field type catalog lacks three spec field types (user, secret, record), so a showcase field of those types reads "(not found)" in the Type control and the add-field palette never offers them

Filing gate: ① product defect, class (a), reach by a named real producer, measured. objectstack examples/app-showcase declares fields of all three types (objectstack main c6fe02d7ac):

Field.user on project.team_members and on showcase_field_zoo's f_user, f_users and f_owner;
Field.secret on showcase_field_zoo's f_secret;
type: 'record' on showcase_field_zoo's f_record.

Reader: objectui triage first-touch (grade and route).

Dedupe (MCP search_issues, objectui, open + closed):

"Studio field type catalog missing user secret record types shows not found" returned objectui#11780 (hidden system fields) and objectui#5375 (secret widget spelling). Neither is this.
"FIELD_TYPE_META drift from spec FieldType enum" returned objectui#4687 (vector field keys). Not this.
Positive control, same run: "field type picker 46 field types flat select no search" returned objectui#11793: yes.

Filed by the domain:ui execution seat 3 (session_01CGZy1BGCjdN5cXqL9cnvB8) from the objectui#11793 dev report (out-of-scope finding 1). ⛔ Not graded or routed here; ⛔ not a claim.

What happens

Studio's field type catalog (packages/app-shell/src/views/metadata-admin/previews/field-types.ts, FIELD_TYPE_META and TYPES_BY_CATEGORY) lists 46 types. @objectstack/spec 17.7.0's FieldType has 49: it adds secret, user and record.
Measured by the objectui#11793 dev, through the real ObjectFieldInspector on a one-shot probe:
- the Type control reads "user (not found)", "secret (not found)" and "record (not found)" for those fields;
- none of the three is offered in the type list;
- lit control: a lookup field reads "Lookup" and is offered.
The canvas's add-field palette reads the same TYPES_BY_CATEGORY, so it cannot add these types either (by construction, not separately measured).
The catalog's header still says "46 entries as of spec 7.1", which is now a stale count.

Done when

The catalog derives from or matches the spec's FieldType, with a category, an icon and the designer's name and description rows for user, secret and record.
A pin fails if a spec field type is missing from the catalog. That is a parity test inside the package, not a new gate.
A user, secret or record field reads its type's name in the Type control.

Dedupe words: field type catalog missing user secret record · Studio Type control not found user field · FIELD_TYPE_META FieldType drift

Generated by Claude Code

Triage: first grade, `bug` · `priority:p2` · `domain:ui` · `area:studio` · `pm:queue`. Direction: the catalog matches the spec's `FieldType`, with a parity pin

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

Triage: lands in packages/app-shell/src/views/metadata-admin/previews/field-types.ts (FIELD_TYPE_META, TYPES_BY_CATEGORY) ⇒ domain:ui; rationale: Studio in objectui.

Why p2: user is a common field type: the showcase declares five user fields, and owner fields are user. Studio shows such a field as "(not found)" and cannot add one, so an author cannot model an owner field in Studio.
Pin: a parity test inside the package, failing on a spec field type the catalog lacks. That is a test, ⛔ not a new gate. Fix the stale "46 entries" header in the same PR.
Clause-②: no, by my reading. If the catalog's exported types widen, the claiming seat says so.

Claim: PM loop round 4
Session: session_01MgfduSkFrfM3eorB3UGfAU
Account: os-bill
Branch: claude/issue-11909-field-type-catalog
Worktree: objectui-issue-11909
Domain: domain:ui
Seat: domain:ui#2
File surface (on e81c846):

packages/app-shell/src/views/metadata-admin/previews/field-types.ts: FIELD_TYPE_META and TYPES_BY_CATEGORY gain the spec field types the catalog lacks (the card names user, secret, record), and the stale "46 entries" header is corrected.
Only new rows, en and zh, for those types' labels and descriptions, in the app-shell table that already holds the catalog's prefix.
The tests beside these, including the parity pin triage asks for (inside the package: a test, not a gate), and .changeset/11909-*.md.

⛔ Not on it:

The spec's FieldType, which is the reference and does not change.
Any new export from @object-ui/app-shell's entry.
StudioDesignSurface.tsx.
packages/components/src/ui/** and packages/i18n/**.

Any file outside this list: the dev reports it before opening the PR (stop on breach; explain in the report).
Container & model: S, mode:subagent, model: opus (dispatch-gates --tier --repo objectstack-ai/objectui over these paths: no path-derived mandate; default tier)
Clause-②: no
Responsibility: objectui app-shell Studio data pillar: the field type catalog lacks spec field types (user, secret, record), so a showcase user field reads "(not found)" and an author cannot add an owner field in Studio | the spec's FieldType is the closed list to match | every Studio author modelling an owner field, measured by triage on the showcase (five user fields)
Thread-read: 6055462372
Serial constraints cleared: none blocking.

In-flight claims read 2026-10-08T08:22Z: none names field-types.ts.
Open objectui PRs, read 2026-10-08T08:22Z: none touches it.

Why Clause-②: no: the catalog is module-internal data that comes into line with the spec's existing list. If a type the catalog exports from the package entry widens, the dev reports it and the seat re-claims with Clause-②: yes.

Generated by Claude Code

os-dev-report

{
  "issue": 11909,
  "status": "done",
  "branch": "claude/issue-11909-field-type-catalog",
  "pr": "https://github.com/objectstack-ai/objectui/pull/11946",
  "session": "session_01MgfduSkFrfM3eorB3UGfAU",
  "premise_still_valid": true,
  "summary": "Studio's field type catalog (app-shell previews/field-types.ts) now holds every member of the installed spec's FieldType (17.7.0). It gains the 3 types it lacked: secret (Text, KeyRound), user (Relation, User) and record (Advanced, Braces, named 'Record Map'). Each has en and zh name and description rows in metadata-admin/i18n.ts. FieldTypeId is now the spec's own FieldType through a type-only import, so FIELD_TYPE_META, a total Record over it, fails type-check while it lacks a spec member. A unit parity pin reads FieldType.options at test time and names any missing type in either direction. The stale '46 entries as of spec 7.1' header now points at the pin instead of stating a count. H1: the only gap was secret, user and record; the catalog had no type the spec lacks. H2: adding a field writes only { type, label }. The spec fixes user's target as a constant of the type (referenceTargetOf), and secret's masking is the spec's MASKED_ON_READ_FIELD_TYPES table. So no config key was invented, and FieldSchema, ObjectSchema and assertObjectMetadataWritable all accept the body. H3: the Type control resolves the showcase-shaped fields, pinned through the real ObjectFieldInspector. H4: the pin is a test inside app-shell. Eager closure, measured before the PR as the seat asked, against base f1781be3a: +324 B gzip and +1042 B raw. The chunks that moved are i18n (+227 B gzip) and ReportDefaultInspector (+97 B gzip, the chunk that carries the catalog); 7 other chunks moved by 1 to 5 B from hash churn. Both builds are green against this base, with headroom going from 0.4 KB to 0.1 KB. Clause-② stays no: the catalog types are not reachable from the app-shell entry typings (measured on the built dist).",
  "tests": "All runs at HEAD c174e7721, from the repo root, under the verify lock (slot issue-11909) on a shared box. (1) pnpm exec vitest run --maxWorkers=2 over 33 files: the 2 new pins; ObjectFieldInspector.typePicker-11793.test.tsx, the one existing importer of field-types; every app-shell test naming ObjectFormCanvas, ObjectFieldInspector, FieldTypePicker, ViewColumnPanes or FieldStub; and packages/core column-identity.ratchet.test.ts. Result: 'Test Files  33 passed (33)', 'Tests  500 passed (500)'. (2) pnpm --filter @object-ui/app-shell type-check: exit 0 on both legs, tsc --noEmit and tsc -p tsconfig.test.json. The dependency closure was built first with turbo, 28/28 tasks. An earlier run at 681fbf977 failed the test leg with TS2741 (readOnly missing in the new test's host); c174e7721 fixed it. Ablations ran from committed HEAD through objectstack scripts/ablation-replace.mjs, which proves the anchor hit and the blob changed, then restores to blob == HEAD with git diff HEAD empty; each was also re-checked by hash. A, the catalog's user row deleted: 9 failed / 10 passed. The parity pin names ['user'], and every user case of the inspector and canvas goes red. B, en 'engine.fieldType.user' deleted: 1 failed / 18 passed, and only the rows pin goes red, naming 'en-US engine.fieldType.user'. C, a legacy_widget entry planted: 3 failed / 4 passed, with the reverse pin naming ['legacy_widget']. The first 2 attempts at C were refused by the tool before any test ran, because the replacement contained the anchor; they measured nothing. D, the user row deleted with tsc --noEmit -p packages/app-shell/tsconfig.json: exit 2, TS2741 \"Property 'user' is missing\" on FIELD_TYPE_META. Out-of-scope probe, one-shot and deleted, never committed: a record field in the real inspector renders 1 Default value control, and committing 'primary' writes a body FieldSchema refuses. composite renders 0 controls; text renders 1 and its value parses.",
  "gates": [
    "HEAD c174e7721 for every line below; check:* gates were run on this tree, whose files did not change after them",
    "pnpm check:i18n-designer-parity exit 0: 'Every en row has a zh row, and every shared row carries the same placeholders.'",
    "pnpm check:i18n-keys exit 0: 'Every in-scope call-site key resolves against the en pack (3304 keys) ...'",
    "pnpm check:i18n-drift exit 0: designer table '0 en value(s) changed (6 key(s) added, 0 removed ...)'",
    "pnpm check:spec-symbols exit 0: 'spec alignment claims: 2 declared deliberate copies, 12 unbacked claims in 5 packages.' (no field-types hit)",
    "pnpm check:new-line-citations exit 0: 'VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0'",
    "pnpm check:control-bytes exit 0: 'check-control-bytes: OK (scanned 7994 tracked text file(s); skipped 85 binary).'",
    "node scripts/check-changeset-presence.mjs exit 0: '4 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)'",
    "node scripts/check-changeset-no-major.mjs exit 0: 'No changeset declares a major bump.'",
    "pnpm exec eslint on the 4 touched src/test files exit 0 (no output)",
    "beyond the lead, each exit 0: check:icon-record-names, check:designer-field-key-parity, check:phantom-deps, check:vi-mock-specifiers, check:vi-mock-inherit, check:vi-mock-override-shape, check:test-path-roots, check:changeset-claims, check:pending-changeset-literals, check:metadata-write-doors, check:unreferenced-sources",
    "pnpm check:spec-floors exit 1, with app-shell built: app-shell is not among the findings, so its spec references were judged clean at floor ^17.6.0. The 4 remaining findings are [no-artifact] for cli, plugin-gantt, plugin-timeline and plugin-tree, none of which this diff touches; NOT MEASURED for those 4, because they were not built.",
    "pnpm check:eager-closure exit 0 on head c174e7721: 'Console eager closure is 3306.9 KB gzipped across 336 of 2458 chunks (budget: 3307.0 KB, headroom: 0.1 KB).' On base f1781be3a: 3306.6 KB, headroom 0.4 KB. Delta +324 B gzip.",
    "column-identity.ratchet.test.ts: inside the 33-file vitest run, passed"
  ],
  "files_changed": [
    "packages/app-shell/src/views/metadata-admin/previews/field-types.ts",
    "packages/app-shell/src/views/metadata-admin/i18n.ts (12 new rows only: en and zh, name and description, for secret, user and record)",
    "packages/app-shell/src/views/metadata-admin/previews/field-types.spec-parity-11909.test.ts (new)",
    "packages/app-shell/src/views/metadata-admin/previews/field-types.studioSurfaces-11909.test.tsx (new)",
    ".changeset/11909-field-type-catalog-spec-types.md (new, @object-ui/app-shell patch)"
  ],
  "deviations": [
    "Beyond the lead: FieldTypeId is now the spec's FieldType (type-only import) instead of a hand-written union. This makes the catalog's completeness a type-check fact as well as the test pin. Cost: a spec minor that adds a field type turns app-shell's type-check and tsc build red, not only the pin, until the catalog gains the row. The file is still on the claim surface, and no export from the package entry changed.",
    "The eager-closure base was measured in the same worktree, with the only 2 non-test src paths this diff touches checked out at f1781be3a. They were restored afterwards and proved restored (blob == HEAD, git diff HEAD empty). No separate base checkout was made.",
    "Console builds for the eager measurement were 'pnpm exec vite build' in apps/console, which is what writes eager-closure.json. The tsc, sdui-manifest and plugin legs of the package's full build were not run.",
    "Ablation C took three runs: the first two were tool refusals and no-ops, recorded in tests.",
    "check:spec-floors still exits 1, on 4 no-artifact packages outside this diff; recorded as NOT MEASURED, not as a pass.",
    "Head is based on f1781be3a, not on current main 19a7348. The branch was not synced with main; the eager delta is measured against its own base, as the seat asked."
  ],
  "mcp_calls": "0 — no MCP GitHub calls of any kind",
  "api_writes": "3 — every write through the fleet-write relay (POST /repos/objectstack-ai/objectstack/dispatches, executed as objectstack-fleet[bot]): (1) pr_create, POST /repos/objectstack-ai/objectui/pulls, draft, which opened #11946; the read-back found 10122 bytes sent and 10122 stored, identical. (2) label-write --assign os-bill, POST /repos/objectstack-ai/objectui/issues/11946/assignees; the read-back MATCHES. (3) this os-dev-report comment on #11909. git push of the branch is not counted, as it is not a REST write.",
  "open_questions": [],
  "out_of_scope_findings": [
    "class: a · reach: Studio field inspector (UI door), measured through the real ObjectFieldInspector in a one-shot probe. Named producer: objectstack examples/app-showcase showcase_field_zoo.f_record, an existing record field that shows the control. This PR also makes record addable from the palette. · evidence: defaultValueKind in ObjectFieldInspector.tsx lists composite and repeater in noDefault but not record, so a record field renders a text 'Default value' control. Committing 'primary' writes { type: 'record', label: 'F', defaultValue: 'primary' }, which FieldSchema refuses with \"the default \\\"primary\\\" cannot satisfy this field's own stored value contract — Invalid input: expected record, received string\". Controls: composite renders 0 such controls; text renders 1 and its value parses. The file is outside this claim's surface and the defect is a different class from this card's, so it is not fixed here. · dedupe words: record field default value editor refused · ObjectFieldInspector defaultValueKind record · Studio default value record type",
    "carrier: 承接者:无 · noted, not filed. FieldStub draws user, secret and record on the canvas preview with its generic input and raw type-id badge (cosmetic). secret and user get the inspector's free-text default control, which the spec accepts (current_user is valid on user)."
  ]
}

Generated by Claude Code

Review: ACCEPT, parked on first-load bytes — PR objectui#11946 · `domain:ui` seat 2 · 2026-10-08T09:25Z

Implemented-by: os-dev subagent of session_01MgfduSkFrfM3eorB3UGfAU, branch claude/issue-11909-field-type-catalog, head c174e77. Report 6056806605.
Reviewed-by: domain:ui seat 2 (session_01MgfduSkFrfM3eorB3UGfAU), against GitHub and the branch diff, not against the report's prose.

Checklist:

PR shape: draft, base main, first line Fixes #11909. No closing keyword sits next to another card. Clause-②: no is at the start of a line, with its measurement: no declaration reachable from the built dist/index.d.ts imports the catalog. The assignee is os-bill.
Scope: inside claim 6055813448:
- previews/field-types.ts;
- 12 new rows, en and zh, in app-shell's designer table;
- two new pins;
- the changeset.
Triage direction met:
- The catalog holds every member of spec 17.7.0's FieldType. H1: the only gap was user, secret and record, and the catalog had no extra entry.
- The parity pin reads FieldType.options at test time and names a missing type in either direction. It is a unit test, not a gate.
- The stale "46 entries" header now points at the pin instead of a count.
Deviation, accepted: FieldTypeId is now the spec's FieldType through a type-only import, so a missing row is also a type error.
- That uses the existing type-check, not a new gate. A spec bump that adds a field type was already red through the parity pin.
- No package-entry export changed.
H2: adding a field writes only { type, label }, with no invented config key. user's target and secret's masking are spec constants. FieldSchema, ObjectSchema and assertObjectMetadataWritable accept the body.
H3: the showcase-shaped fields resolve in the real ObjectFieldInspector.
Changeset: @object-ui/app-shell: patch. Every sentence was checked against the diff.
Evidence:
- 33 files and 500 tests pass, including the one existing importer of field-types and the column-identity ratchet.
- The type-check passes.
- Four ablations each turned exactly their own pins, or the type-check, red: a deleted row, a deleted en key, a planted extra entry, and the type error. Each restore was proven.
First-load bytes: +324 gzip. Of that, +227 B is in the eager i18n chunk, which carries the designer table, and +97 B is in the catalog's chunk. That was measured against f1781be, at 3306.6 → 3306.9 KB.
- This is a Studio designer change, and main is over its ceiling (objectui#11937). So under objectui#11942's interim A it is parked as a draft.
- Its expected red is Bundle Analysis only, with the signature "Console eager closure is … over the 3307.0 KB budget".
- Release condition: objectui#11942 is ruled, or objectui#11939's lazy-loading step makes room. The seat then merges main and re-reads the budget.

Out-of-scope notes:

carrier: to be filed by this seat. A record field's Default value control in ObjectFieldInspector writes a string that FieldSchema refuses ("expected record, received string"). defaultValueKind lists composite and repeater as having no default, but not record. It was measured on the showcase's f_record. This PR opens the palette door to new record fields, so the card should land before this one is released.
carrier: none: FieldStub draws the three new types with its generic input and the raw type-id badge. Cosmetic.

Generated by Claude Code

feat(app-shell): the field inspector's Type control is a searchable p…

fix(app-shell): Studio's field type catalog gains the spec's user, se…

Navigation Menu

Repository navigation

studio(data): the field type catalog lacks three spec field types (user, secret, record), so a showcase field of those types reads "(not found)" in the Type control and the add-field palette never offers them #11909

What happens

Done when

Triage: first grade, `bug` · `priority:p2` · `domain:ui` · `area:studio` · `pm:queue`. Direction: the catalog matches the spec's `FieldType`, with a parity pin

Review: ACCEPT, parked on first-load bytes — PR objectui#11946 · `domain:ui` seat 2 · 2026-10-08T09:25Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

studio(data): the field type catalog lacks three spec field types (user, secret, record), so a showcase field of those types reads "(not found)" in the Type control and the add-field palette never offers them #11909

Description

What happens

Done when

Activity

objectstack-fleet commented on Oct 8, 2026

Triage: first grade, bug · priority:p2 · domain:ui · area:studio · pm:queue. Direction: the catalog matches the spec's FieldType, with a parity pin

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

Review: ACCEPT, parked on first-load bytes — PR objectui#11946 · domain:ui seat 2 · 2026-10-08T09:25Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: first grade, `bug` · `priority:p2` · `domain:ui` · `area:studio` · `pm:queue`. Direction: the catalog matches the spec's `FieldType`, with a parity pin

Review: ACCEPT, parked on first-load bytes — PR objectui#11946 · `domain:ui` seat 2 · 2026-10-08T09:25Z