Repository navigation
Studio Part A quick wins: wire the already-registered action and dataset previews into the Interfaces pillar rail (#2657 ruling) #6411
Description
Follow-up filed from the 2026-08-07 maintainer ruling on #2657 (decision batch accepted via the PM session). Unclaimed; no labels applied — routing belongs to the triage seat (the work lands in objectui packages/app-shell Studio ⇒ expected repo:objectui routing; flagged, not self-applied).
Ruling context
#2657 Part A (surfacing already-registered metadata types in Studio, per the pillar placement plan in its body) was approved; Part B (promoting un-typed concepts) stays blocked on #6234 / #6245 and is not this card.
Scope — the two quick wins only
action and dataset are registered types with Zod schemas whose previews are already registered in metadata-admin/previews; per the #2657 audit, only the Interfaces-pillar rail load is missing. Wire both into the Interfaces pillar (alongside view/page/dashboard/app/report), reusing the generic SchemaForm path.
Explicitly out of scope: the other Part A placements (job / role / seed / mapping / datasource, new AI pillar, new System pillar) — those are follow-on cards once this pattern lands; and everything in Part B.
Acceptance
- Studio's Interfaces pillar lists and opens
actionanddatasetitems with the standard editor surface; no framework/spec change required (per the audit, spec is already complete for both). - Verify against current objectui main first — the audit is from July; re-check the rail/preview registration state before implementing (stale-premise discipline).
Refs: #2657 (ruling comment 2026-08-07), objectui packages/app-shell metadata-admin/previews.
Activity
os-zhuang commentedon Aug 7, 2026
Triage:
pm:queue+repo:objectui.Routing: the work is entirely in objectui
packages/app-shell(Interfaces pillar rail + the already-registeredmetadata-admin/previews), and the card states no framework/spec change is needed — the audit found spec complete for both types. So this is a routed backlog card in the main backlog, executed in objectui:repo:objectui, nodomain:*(objectui is a whole-repo seat, not a domain lane).Cross-repo dedup run: searched open objectui issues and PRs for a shadow of this work (Studio / pillar / preview /
action/dataset) — nothing found, so no cross-link orBlocked-by:is needed and this keeps exactly one dispatch entry.Grade: the ruling approved Part A, and this card is scoped down to the two quick wins with explicit out-of-scope boundaries (other placements, new pillars, all of Part B). That is dispatchable as written.
Stale-premise flag carried forward, not resolved here: the underlying audit is from July. The card already instructs re-checking rail/preview registration against current objectui main before implementing — keep that in the dispatch prompt; it is the difference between two quick wins and a rediscovery.
No
target:v17: surfacing already-registered types is an improvement, not a release blocker — it rides the next train.本评论来自分诊座位 Routine（#5474 试点），不构成认领。
Generated by Claude Code
os-zhuang commentedon Aug 10, 2026
Migrated to objectstack-ai/objectui#4019 under #7167 (file-at-destination ruling, maintainer 2026-08-10). Native GitHub issue transfer is not available to this session's credential, so the card was recreated at the destination; this thread stays as the authoritative history and is linked from the new card. Closing as not planned here — moved, not rejected.
Generated by Claude Code