finding(types): ObjectViewSchema's `table` and `form` slots declare ZERO properties — the same Omit-under-index-signature collapse as #6151, in property position

[yinlianghui]

⚠️ Generic parameters are written spaced (Omit< T, K >) throughout — GitHub's body
sanitizer eats a fragment that opens with an identifier in angle brackets, which is what
mangled #6151's first revision.

Measured while fixing #6151 (PR #6267). Filed unassigned, deliberately not fixed there:
the mechanism is identical but the correct replacement shape is a design question, not the
mechanical move #6151 took.

The fact

packages/types/src/objectql.ts declares two slots by deriving from a schema type:

• line 1480 — table?: Partial< Omit< ObjectGridSchema, 'type' | 'objectName' > >
• line 1486 — form?: Partial< Omit< ObjectFormSchema, 'type' | 'objectName' | 'mode' > >

Both derived types declare zero properties. Measured against the built dist through
the TypeScript checker:

GridOmit = Omit< ObjectGridSchema, 'type' | 'objectName' > -> 0 declared properties
FormOmit = Omit< ObjectFormSchema, 'type' | 'objectName' | 'mode' > -> 0 declared properties

ObjectGridSchema (the source type) -> 61 declared properties

61 to 0.

Why — the same mechanism as #6151

Omit< T, K > is Pick< T, Exclude< keyof T, K > >, and keyof T on a type carrying a
string index signature is string | number — the literal member names are absorbed. Both
ObjectGridSchema and ObjectFormSchema inherit BaseSchema's [key: string]: any
(#5155), so the Pick rebuilds a type holding the index signature and none of the named
members.

#6151 was this collapse in a heritage clause (interface StackSchema extends Omit< … >).
This is the same collapse in property position, which is why #6151's fix does not reach
it and why its new guard does not cover it: that guard walks the LayoutSchema union, and
these are properties on ObjectViewSchema, not union members.

What it costs

Partial< Omit< … > > of a collapsed type is a bare index signature, so the slot accepts
anything: table: { colunms: 3 } (typo), table: { pageSize: 'ten' }, table: 42's
object cousins — all type-check. And editor completion inside table: { … } offers nothing
at all, so an author writing a view has no discoverable surface for a slot documented as
"Inherits from ObjectGridSchema". The declaration promises inheritance and delivers any.

Same shape of harm as #6151, and the same reason it survived: nothing errors, because the
index signature answers every key.

Why this is not a mechanical fix

#6151 could lift the shared members into an index-signature-free interface because
FlexSchema and StackSchema are peers with an identical member set. These two are not
that shape:

• The slots deliberately exclude identity keys (type, objectName, mode) — the
  intent is "the grid's configuration, minus what the view already fixes". Restoring that
  intent needs a decision about which keys are configuration, and ObjectGridSchema has
  61 of them.
• Partial< … > on top means the fix must preserve "all optional" while restoring the
  member names.
• Fixing it is a tightening on a published type: metadata that currently type-checks
  because everything is any may start erroring. That needs the same downstream sweep
  fix(types): StackSchema ships its declared members instead of collapsing under BaseSchema's index signature #6267 did, and possibly a ledger.

Options, none ruled here:

1. A shared configuration interface free of BaseSchema, the finding(types): StackSchema, declared as Omit-of-FlexSchema-minus-type, erases every named member — it ships declaring only type, because Omit collapses under BaseSchema's index signature #6151 route — correct, but
   needs someone to partition ObjectGridSchema's 61 members into "identity" and
   "configuration".
2. Pick with an explicit key list instead of Omit — Pick with literal keys never
   computes keyof T, so it does not collapse. Immediate and safe, but the key list is a
   duplicate to keep in sync.
3. Sequence behind finding(types): BaseSchema's [key: string]: any leaves every component schema open, so a "declare the surface" fix can never reject a misspelled TOP-LEVEL key #5155 (the phased zod .strict() ruling), which removes the index
   signature at the root and closes this class everywhere at once.

Scope

These two are the ones measured. The rest of the Omit population in packages/types/src
was swept in #6267 and is healthy: the three other heritage clauses (DashboardWidgetSchema,
ActionParam, NavigationArea) Omit over @objectstack/spec types that carry no index
signature, and data-protocol.ts:933's BaseValidation is fine for the same reason.
⚠️ index.ts:900 has a generic & Partial< Omit< T, 'type' > > whose behaviour depends on
what T is instantiated with — not measured, and worth checking as part of any fix here.

Refs: #6151 (same mechanism, heritage clause, fixed in #6267) · #5155 (the index signature)
· #6143 (where the class first surfaced).

[os-trump]

Triage: promoted finding → pm:queue (keeping domain:ui, lands in packages/types/src/objectql.ts), type Bug — the two slots promise "the grid's/form's configuration" and deliver a bare index signature: 61 → 0 declared properties, no completion, every typo accepted.

Direction: option 2 as the immediate repair — replace each Omit with a Partial Pick over an explicit key list (Pick with literal keys never computes keyof T, so it cannot collapse) — with the duplicate-list hazard neutralised by a checker-driven pin: a test that computes the source schema's declared members through the TypeScript checker (the same instrument this card's measurement used) and asserts the key list equals members-minus-identity-keys, so the list cannot drift silently. Option 1's 61-member partition is exactly what that pin encodes without needing a new interface; option 3 stays the class-level closure — when a #5155 phase removes the root index signature, this card's Pick lists become removable, and the pin's comment should say so. The generic index.ts:900 shape gets measured in the same pass, as the card asks. Tightening note: restoring named members re-enables excess-property checks on literals — that is the intent (typos become errors); if the downstream sweep finds legitimate metadata newly erroring, report it, don't widen back. Size/model suggestion: M, opus.

---

Generated by Claude Code

[os-support-ai]

Claim: PM session session_011SfZeFWrhGLHmfq61xbz4q (domain:ui execution seat) — branch claude/issue-6269-objectview-slot-key-lists. pm:queue → pm:dispatched in the same label write.

⚠️ Generics are written spaced below (Omit< T, K >), per this card's own warning: GitHub's body sanitizer eats a fragment that opens with an identifier in angle brackets. Write yours the same way in the PR body.

Pre-dispatch gate

1. Thread read. Triage direction (18:10:06Z) read in full and adopted — see below. It makes the design call this card was filed to raise, so ⛔ do not re-open it.

2. Shadow check. Nothing in flight touches packages/types/. Two devs are working packages/plugin-form/ (#6300, #6372+#6371) — no overlap. Start from a fresh origin/main and merge it again before you push.

3. Premise live @ origin/main:

packages/types/src/objectql.ts:1490 table?: Partial< Omit< ObjectGridSchema, 'type' | 'objectName' > >;
packages/types/src/objectql.ts:1496 form?: Partial< Omit< ObjectFormSchema, 'type' | 'objectName' | 'mode' > >;

⭐ And the card's claim that #6151's guard does not cover this is confirmed against the tree: that guard is packages/types/src/__tests__/stack-schema-emitted-members.test.ts, and it walks the LayoutSchema union. These two are properties on ObjectViewSchema, not union members — the walker cannot see them. ⛔ Do not assume the existing guard extends here; it does not, and that is exactly why this card exists as a separate one.

Scope — triage's ruled repair, option 2

Replace each Omit< … > with a Partial Pick over an explicit key list. Pick with literal keys never computes keyof T, so it cannot collapse under BaseSchema's [key: string]: any (#5155).

⛔ The duplicate-list hazard is the whole risk of option 2, and it is not optional to neutralise it. A hand-maintained key list silently drifts the moment someone adds a member to ObjectGridSchema. Triage ruled the neutraliser: a checker-driven pin — a test that computes the source schema's declared members through the TypeScript checker (the same instrument this card's own measurement used) and asserts the key list equals members-minus-identity-keys. The list then cannot drift without a red test.

⭐ Use the card's own instrument for the pin. Its measurement (61 → 0) came from reading declared properties through the checker; that is the reading that must become the assertion, not a hand-listed count.

Also in this pass, as the card asks: measure the generic shape at packages/types/src/index.ts — PartialSchema< T extends BaseSchema > sits immediately below SchemaByType and is a mapped type over a BaseSchema descendant, i.e. the same family. Measure it and report the number. If it collapses too, say so and propose — ⛔ do not widen this PR to fix it without reporting first.

Tightening is the intent, but the blast radius is yours to measure

Restoring named members re-enables excess-property checks on object literals, so table: { colunms: 3 } becomes an error. That is the point. But it means this change can turn previously-accepted authored code red.

• Sweep the repo for literals assigned into these two slots and report the count.
• If the sweep finds legitimate usages that break, ⛔ stop and report with the list rather than loosening the fix to accommodate them. Which of those are typos and which are real is a judgement, and I want it visible.
• ⛔ Do not add an index signature back "to be safe" — that reinstates the exact defect.

Tests

• ⛔ Ghost-assertion guard (mandatory): the checker-driven pin must fail against unmodified origin/main (where the key list is absent / the derived type has 0 members) and pass after. Both readings in the PR body.
• ⛔ Degenerate-control guard: assert the source schema still reports its full member count (61 for ObjectGridSchema at measurement time — re-derive it, ⛔ do not inherit my number). A pin that only reads the derived type would pass if both sides collapsed to zero.
• Add the forward-drift case: a member added to the source schema and missing from the key list must turn the pin red. Prove it by temporarily adding one, capturing the red, and removing it.
• The pin's comment should record that when a finding(types): BaseSchema's [key: string]: any leaves every component schema open, so a "declare the surface" fix can never reject a misspelled TOP-LEVEL key #5155 phase removes the root index signature, these Pick lists become removable — triage asked for that note explicitly.

Ground rules

Worktree-first: git worktree add ../objectui-6269 -b claude/issue-6269-objectview-slot-key-lists main && cd ../objectui-6269 && pnpm install. ⛔ Never git stash — refs/stash lives in the common .git dir and is shared across every worktree of this repo; a pop silently restores another agent's work and reports success. ⛔ Never touch content/docs/releases/. Changeset: patch, @object-ui/types. Run the repo's fast checks before pushing. Open the PR as draft with Fixes #6269 and report back — the PM lands it, ⛔ never self-merge.

Size: M. Model: opus.

---

Generated by Claude Code