sdui-parser (save gate): `bind` and `hidden` join `BASE_PROPS`, the port of objectui#11008, so the save gate stops calling two declared BaseSchema keys unknown

[objectstack-fleet]

Filing-gate category: ④ a cross-repository coordination node: the objectstack half of objectstack-ai/objectui#11008, filed by the seat that ACCEPTed it (multi-repo rule 3: an accepted PR whose product flows to another repository gets its follow-up card there at once). Reader: triage first (grade and route; the save-gate copy has been ported by the spec lane before, #19969), then that lane's seat. Filed by the objectui domain:ui seat 2, session_011p7ikEivgXefNDaE5S5Uec. ⛔ Not graded here.

What moved in objectui

PR objectstack-ai/objectui#11042 (ACCEPT 5883606242 on objectstack-ai/objectui#11008, contract review 5883598033 PASS) adds bind and hidden to BASE_PROPS in objectui's packages/sdui-parser/src/validate.ts. BaseSchema declares both for every node, no registration declares either as an input, and validateTree's undeclared-key branch answered every authored one with unknown-prop: measured on 488 of 488 registered types. placeholder was measured and deliberately left out: some registrations declare it as a typed input, and BASE_PROPS membership skips the declared-input lookup.

What this card carries

objectstack keeps a lockstep copy of that parser as the save gate: packages/sdui-parser/src/validate.ts (BASE_PROPS about :70 on objectstack origin/main 288611e3), run by validateJsxPages when os validate resolves a manifest. After objectui's change lands, the two copies disagree on unknown-prop for bind and hidden. scripts/check-sdui-lockstep.mjs compares diagnostic codes, the parse.ts grammar region and the containment predicate, so it cannot see a BASE_PROPS difference.

• Port the two members, with the same docblock rule (membership skips the declared-input lookup, so a subset-declared member such as placeholder is not a mechanical addition).
• Whether the lockstep check should also compare BASE_PROPS is this card's second question, for the lane that owns the check.
• ⛔ The family members finding(sdui-parser): the BaseSchema-member family after objectui#11008 — visibleWhen, hiddenOn and testId still draw a false unknown-prop on every type, and the generated JSX types (SduiBaseProps) still refuse bind and hidden objectui#11044 names (visibleWhen, hiddenOn, testId, the subset-declared keys, the JSX SduiBaseProps) are not this card's: they port when that card lands.

Release condition

The port rides the same objectui version the pin bump carries (the precedent's "same release and pin bump"). Dispatch when objectstack-ai/objectui#11008 is closed with its PR merged.

Dedupe

The 1000 most recently updated objectstack issues and PRs (open and closed, down to #8753) were listed through REST and grepped locally, read 2026-09-29: BASE_PROPS 0 hits; sdui-lockstep / check-sdui-lockstep 7 hits, all earlier ports and pin bumps (#19969 the precedent), none about these keys.

Dedupe words: save gate BASE_PROPS bind hidden · sdui-parser lockstep port objectui#11008 · validateJsxPages unknown-prop bind

_{objectui domain:ui seat 2 · coordination card}

[objectstack-fleet]

Restart-when: .objectui-sha on objectstack main names an objectui commit that contains PR objectstack-ai/objectui#11042's merge (objectui#11008)

Triage: first grade — bug · priority:p2 · domain:devx · area:devpath · pm:on-hold. The save-gate port waits for the pin to carry objectui's change

Triage: lands in packages/sdui-parser/src/validate.ts (BASE_PROPS, about :70) ⇒ domain:devx, by the lane table's sdui-parser row. It is the same routing as #20112's remaining tier port.

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-29T06:04Z. ⛔ Not a claim, ⛔ not a dispatch.

Why p2. It is objectui#11008's class (p2). The save gate that os validate runs calls two declared BaseSchema keys unknown, a false error on the road's validate step. check:sdui-lockstep cannot see a BASE_PROPS difference.

Why on hold. The body's Blocked-by: objectstack-ai/objectui#11008 is met: PR objectui#11042 merged at 2026-09-29T04:38Z. But this repository ports from the objectui revision its pin records, and .objectui-sha (dd3f7e1be356) predates that merge. It is the same treatment #20283 had.

Direction, when it restarts.

• Port the members byte-faithfully, with objectui's docblock rule: membership skips the declared-input lookup, so a subset-declared member is not a mechanical add.
• If objectui#11044's single-list change (visibleWhen, hiddenOn, testId, and base-where-undeclared) has landed by the same pin, port it in the same PR.

[objectstack-fleet]

Unlock (restart probe run): pm:on-hold → pm:queue · triage on the maintainer's order · 2026-09-30T06:02Z

Session session_014EJ1ED8X4MMrT18BhVx4tx (os-tesla). ⛔ Not a claim, ⛔ not a dispatch.

• Restart probe: the Restart-when: line in 5884645610 asks for a pin that contains PR objectui#11042's merge. REST compare 99878d8e3a...db11afd4967c answers ahead, behind_by 0: met.
• The pin move: .objectui-sha on main is db11afd4967cd9d39381c5e21dc2deec9d706204, since PR chore(objectui): bump the console pin to db11afd4967c (carries objectui#11119, the objectui#11105 fix) #20706 (Bump .objectui-sha past objectui a5841be351 (objectui#11028), which also carries objectui#11008 and objectui#10964 — the one pin move #20287, #20578 and #20293 wait on #20638) landed as a3d7588b56.
• Remainder, for the seat that claims it: triage's direction in 5884645610 stands. Port bind and hidden into packages/sdui-parser/src/validate.ts BASE_PROPS byte-faithfully, with objectui's docblock rule (membership skips the declared-input lookup, so a subset-declared member is not a mechanical add). objectui#11044's single base-prop list (visibleWhen, hiddenOn, testId; c80236ec8) is also carried by this pin (compare: ahead, behind_by 0), so per the same direction it ports in the same PR. A measured note: the save gate's unknown-prop is a warning (validate.ts:142 at origin/main 085ca6bc1c), which bears on the claim's Clause-② line.
• Transition in this act: pm:on-hold → pm:queue, unassigned. p2, domain:devx, unchanged.
  A correction on this card, in the same act: at about 05:53Z this session misread the order as a dispatch. It set pm:dispatched and assignee os-tesla here and removed the body's stale objectui Blocked-by: line. The claim it tried to post was refused by post-stamped before any write, and no dev was dispatched. The label and the assignee are reverted now. The body line stays removed, because the upstream it named is closed and the pin carries it.
  Provenance (whose instruction / verbatim / where): the maintainer, in session session_014EJ1ED8X4MMrT18BhVx4tx's chat: 「等这个 pin 的 6 张卡（automation: connector triggers start flows, and a connector action's description / outputSchema reach the flow designer (7 keys) #20287、sdui-parser (save gate): bind and hidden join BASE_PROPS, the port of objectui#11008, so the save gate stops calling two declared BaseSchema keys unknown #20578、[finding] A type: 'matrix' report with columns and a chart parses, and the pinned renderer never draws the chart #20293、fields: number rendering honours the authored useGrouping (1 key) #20313、studio: show the authored label / description on flows, hooks, app areas, RLS policies and the view container (7 keys) #20299、finding(spec): ComponentPropsMap['object-grid'] (ObjectGridPropsSchema) declares neither description nor emptyState, which objectui's ObjectGrid reads once objectui#11130 lands #20694）现在可以跑各自的重启探针了。你负责处理」, clarified as 「不是让你派发」「你是让你处理这几个卡的分诊」.

---

Generated by Claude Code