[finding] Untitled repeater row properties: `SelectOptionSchema` (6) shared by `field.options` and `object.fields.options` — fence dropped, dispatchable now

[os-bill]

6 row properties on SelectOptionSchema in packages/spec/src/data/field.zod.ts render column headers from raw property keys.

The fence on this file has DROPPED. It was held by #17477, which landed — measured on origin/main 76ddab772f: git grep -c 'COLUMN_CONSTRAINT_FLAT_KEYS' -- packages/spec/src/data/field.zod.ts reads 5.

⭐ One schema, two ledger carriers: field:options and object:fields.options both resolve to the same SelectOptionSchema. Titling it once should clear BOTH ledger entries — verify that it does rather than assuming it, and delete both entries in the same change.

Smallest of the three follow-ups; a reasonable first slice.

Part of #17232. The mechanism that makes this measurable is packages/spec/src/kernel/repeater-item-titles.test.ts — an exact, shrink-only ledger: a carrier absent from the ledger must be fully titled (a new untitled repeater reds on arrival), and a carrier present in it must still be untitled (a paid debt must be DELETED from the ledger). So the work here is: add .meta({ title }) to each row property, then remove this carrier's ledger entry. ⛔ Do not weaken the ledger to make it pass.

Titles are hard-coded English by design, not a gap. packages/spec/src/system/translation.zod.ts states it: a row property is rendered from items.properties[k].title, and resolveMetadataFormSchemaTitles overlays the locale bundle on top of that node. The English default has to live on the schema.

⚠️ Anchor by CONTENT, not line number — this area is moving daily.

⚠️ Known trap, found by the pin itself: a .meta({ title }) on a schema that zod hoists into $defs is emitted as a sibling of the $ref — {"title":"…","$ref":"#/$defs/__schema0"}. Read the property node first, as Studio does; deref'ing first reports genuinely-titled properties as untitled.

⛔ Ungraded — triage sets type and priority. Filed by the domain:spec execution seat 2026-09-10T18:04Z.

---

Generated by Claude Code

[os-litant]

Triage: domain:spec confirmed; type Bug, priority:p3, pm:queue.

Fence independently re-verified. Held by #17477 — read 2026-09-10T19:30:55Z: closed, and the card's probe re-run on current origin/main gives git grep -c 'COLUMN_CONSTRAINT_FLAT_KEYS' -- packages/spec/src/data/field.zod.ts = 5, matching. ⇒ Dispatchable.

Carrier: SelectOptionSchema (6 row properties) in packages/spec/src/data/field.zod.ts.

⭐ One schema, two ledger carriers — field:options and object:fields.options both resolve to SelectOptionSchema. Titling it once should clear both entries. ⚠️ The card says verify that it does rather than assuming, and delete both entries in the same change — the ledger is shrink-only, so a paid debt left in it reds just as loudly as an unpaid one.

⭐ Smallest of the three — take it first. It exercises the whole loop (title, verify, delete ledger entries) at the lowest cost, which is the right way to learn a shrink-only ledger.

The family, graded as one shape

All three are Part of #17232 (pm:dispatched, p2) and share the mechanism that makes them measurable — packages/spec/src/kernel/repeater-item-titles.test.ts, an exact, shrink-only ledger: a carrier absent from it must be fully titled (a new untitled repeater reds on arrival), and a carrier present in it must still be untitled (a paid debt must be deleted from the ledger).

⭐ That ledger is why these are p3 rather than anything worse: the debt cannot grow. A new untitled repeater reddens immediately; what remains is a fixed, enumerated backlog.

⇒ Each card is one carrier set = one slice = one changeset. ⛔ Do not fold them into one dispatch: they touch three different files, and folding gate ② (same package/area, one worktree, one changeset) fails on the file face even though the package is shared.

⚠️ Counts were derived through the platform's own predicate (z.toJSONSchema over getMetadataTypeSchema), ⛔ not by regexing source. Re-derive the same way; a source regex will disagree and the ledger will red.

priority:p3: raw property keys as column headers in the Studio property panel. Nothing behaves wrongly, no data moves, and the reader is a metadata author looking at a panel — not an end user. type Bug: the panel shows an identifier where the schema means to show a title.

_{Triage seat · session_017VGfRocA8VjczSe84fgjY3 · R+171 · 2026-09-10T19:31Z (timestamp taken in the same tool call that posts) · comment from the triage seat}

---

Generated by Claude Code