spec(ui): RecordRelatedListProps.parentDataSource still says [PLANNED — not yet rendered] and the liveness note says nothing reads it — objectui renders it since objectui PR #12407 #23585

Restart-when: npm view @object-ui/plugin-detail@next version names a release built from objectui d81e46043 (PR objectstack-ai/objectui#12407) or later, i.e. objectui ships the parentDataSource renderer.

Filing gate: cross-repo rule 3. An accepted objectui PR's product makes three statements in this repository false, and the seat that accepted it files the follow-up where the fix lands.

• Filed by: objectui domain:ui seat 1 (seat post [PM seat] domain:ui @ objectui — 🟢 os-tesla · session_011K9g23W67dy2zwnyzaoB6o · batch 8 · 31 landed · dev #12757 #12774 #12780 · PR #12802 objectui#5560) · session_01JZnppgHRp4sREcouhkQYDB. ⛔ Not a claim.
• Reader who acts: triage, to route to the domain:spec seat. The spec seat filed and landed the key (spec(page): record:related_list declares its parent record with a binding key of its own, beside the child-row dataSource — the spec half of objectstack-ai/objectui#12294's related-list leg (ruled B on objectstack-ai/objectui#12296) #23134, PR feat(spec): record:related_list declares its parent record with parentDataSource, beside the child-row dataSource (#23134) #23205).
• Executable criterion: git grep -n "PLANNED — not yet rendered" -- packages/spec/src/ui/component.zod.ts names no line on RecordRelatedListProps.parentDataSource, and packages/spec/liveness/page.json's _note no longer carries the PLANNED RECORD (#23134 …) sentence as planned.

What landed

objectstack-ai/objectui#12294 (ruling B on objectstack-ai/objectui#12296, ruling comment 6137226306) landed as objectui PR #12407, merged as d81e46043 on objectui main (landing note: objectui#12294 comment 6182685360):

• @object-ui/plugin-detail: record:related_list reads its parent record from properties.parentDataSource. It takes the first row by sort under the caller's identity, and draws a loud absence when no row answers, never an empty list. When the key is absent, the record page's record is the parent, as before.
• @object-ui/types: RecordRelatedListComponentProps declares parentDataSource as ElementDataSource, by reference.
• The registration publishes it as an input, and objectui validate's limit: 1 warning covers it.

It ships in the next objectui 18.0.0-next.N. The version PR objectstack-ai/objectui#11600 is not merged yet, so its release is the maintainer's act.

What is now false here, read at objectstack origin/main

1. packages/spec/src/ui/component.zod.ts:1889: the parentDataSource describe opens [PLANNED — not yet rendered].
2. packages/spec/src/ui/component.zod.ts:1885: the docblock above it ties the marker's removal to the renderer landing.
3. packages/spec/liveness/page.json, _note: the PLANNED RECORD (#23134, 2026-10-13 …) sentence says "PLANNED, not live … nothing reads the key", with carrier "the related-list leg of record blocks honour the per-element dataSource the spec already declares — record:details / record:highlights / record:quick_actions / record:related_list on an app page bind their record from the component's dataSource, so a product page composes without the record shell (maintainer ruling cloud#2839 Q1 D, 2026-10-13) objectui#12294". That carrier has landed. The sentence itself says: "When that leg lands, the marker leaves and this sentence is rewritten."

Timing (for triage)

The renderer is merged in objectui but not yet in a published objectui release. If the spec seat's rule is to retire the marker when the consumer is installable rather than when it is merged, this card waits for objectui's next 18.0.0-next.N on npm. Probe: npm view @object-ui/plugin-detail@next version names a version published after objectui d81e46043. Otherwise it is ready now.

Dedupe: REST list of open and closed objectstack issues for parentDataSource in the title → 0 hits. The spec card #23134 is closed.

Generated by Claude Code