finding(types): `ObjectKanbanSchema` requires `objectName` on both faces while the renderer reads an undeclared inline `data` ahead of the fetch — the record-source ladder class (#7313) on a fourth view schema

[os-justin]

Finding (observation, awaiting first grading). Filed by the domain:spec @ objectui execution seat (session session_01BAZFhALsQsGqxui8sNqM8s) from the measurement triage 5548431295 on #7313 asked its dev to take ("顺手测一次 ObjectKanbanSchema") — recorded in PR #7777's report (comment 5553458585 on #7313, kanban_reading). ⛔ Not edited there: objectui#7322 / PR #7774 hold the ObjectKanbanSchema block. domain:* and grading are triage's.

What was measured (on origin/main 16a725f9, 2026-09-05T17:1xZ)

• packages/types/src/objectql.ts ObjectKanbanSchema — objectName: string REQUIRED; no data member (and no staticData). Same on the zod face (packages/types/src/zod/objectql.zod.ts, the ObjectKanbanSchema const).
• packages/plugin-kanban/src/ObjectKanban.tsx:283 gates the fetch on schema.objectName && !boundData && !schema.data, and :294 reads rawData = external || boundData || schema.data || fetchedData — an inline data (an any[] of rows on this schema, NOT a ViewData provider block) is read AHEAD of the fetch and is UNDECLARED on ObjectKanbanSchema (it rides BaseSchema's data?: any / passthrough, unexamined). Every objectName read is guarded (:185 ?? '', :205, :247, :283, :601, :630, :723, :768, :976). There is no staticData rung.
• The plugin's own KanbanSchema (packages/plugin-kanban/src/types.ts:89) already spells objectName?: string and data?: any[] — the renderer's declared face and the published @object-ui/types face disagree.
• Ladder shape: external → bind → inline data → fetch by objectName. Different from the map / gantt / calendar ladder (data provider block → staticData → objectName, resolveRecordSourceConfig), so the finding(types): objectName is declared REQUIRED on ObjectGanttSchema and ObjectCalendarSchema while both renderers resolve data and staticData FIRST — the documented static-data route cannot be annotated #7313 fix (requireRecordSource superRefine) is NOT a copy-paste here: the presence rule would be "bind or data or objectName", and data is rows, not a provider config.

Why it is a finding

A bind-only or data-only object-kanban node renders today and is refused by both published faces (missing objectName) — the declared ≠ enforced shape #7296 / #7313 measured on map, gantt and calendar, now on a fourth view schema. No runtime defect; the cost is the type face and the docs gate (any typed bind-only kanban example cannot be annotated).

Boundaries a taker inherits

• ⛔ Wait for PR feat(types): declare ObjectKanbanSchema.groupBy and .limit, retire groupField on both faces (objectui#7322 item 1) #7774 (finding(types,plugin-kanban): ObjectKanbanSchema requires groupField (zero read sites) and declares neither groupBy nor limit — no working object-kanban node is assignable to any declared type #7322 item ①) to land — it rewrites the same block (groupBy / limit declared, groupField tombstone). Read that PR's pin object-kanban-group-by-limit-7322.test.ts first.
• The finding(types): objectName is declared REQUIRED on ObjectGanttSchema and ObjectCalendarSchema while both renderers resolve data and staticData FIRST — the documented static-data route cannot be annotated #7313 pin object-calendar-record-source-7313.test.ts carries a @ts-expect-error control that ObjectKanbanSchema still requires objectName; the fix deletes that line.
• packages/plugin-kanban/** is domain:ui (the ui seat's finding(types/plugin-kanban): an authored kanban document can PASS safeValidateSchema and still render empty — the validator and the renderer honour different faces #7664 holds it) — the types half only here; KanbanSchema in the plugin is theirs.

Not a duplicate of

• finding(types,plugin-kanban): ObjectKanbanSchema requires groupField (zero read sites) and declares neither groupBy nor limit — no working object-kanban node is assignable to any declared type #7322 (items ①, ②: groupBy / limit / groupField and the plugin props type) — different keys on the same schema.
• finding(types): objectName is declared REQUIRED on ObjectGanttSchema and ObjectCalendarSchema while both renderers resolve data and staticData FIRST — the documented static-data route cannot be annotated #7313 (calendar), finding(types): ObjectMapSchema.objectName is declared REQUIRED but ObjectMap treats it as optional — the documented static-data route cannot be annotated #7296 (map, closed), 24 catalog entries fail safeValidateSchema because the Zod mirror names a key its renderer never reads (8 components) #6939 (map + gantt, landed) — the class; this is its fourth member.
• finding(docs): four object-gantt blocks on plugin-gantt.mdx are still bare const literals — ObjectGanttSchema has admitted them since PR #7471, so their keys go unchecked by the doc-snippet gate #7778 (gantt doc blocks unannotated) — docs completion signal for gantt.

Refs: #7313 · PR #7777 · #7322 · PR #7774 · #6939 · PR #7471 · #5155 (BaseSchema's index signature).