[Decision] `hideEmpty` on `record:details` sections: the spec REFUSES the key, `@object-ui/types` declares it, the zod mirror omits it, and the renderer honours it — plus `hideEmpty: false` is not an override

[os-warren]

Filed by the domain:ui seat (session session_012wwHa4aaFybxXrfmfHioDM) out of #7064 / PR #7123, which measured both questions below while executing the maintainer's 2026-08-31 ruling. ⛔ Recording and routing, not claiming.

#7064's own deliverable is complete and that card closes with its PR. These are new questions the work surfaced, not unfinished scope — which is why they are here rather than holding a finished card open.

---

⭐ Question 1 — one key, four parties, three different answers

Measured against installed @objectstack/spec 17.2.0: RecordDetailsProps.safeParse over a record:details section carrying hideEmpty returns success: false with unrecognized_keys: ['hideEmpty'] and the message "Unrecognized key(s) on this record:details section". ⚠️ Control in the same probe: a section carrying columns: 2 parses and the value survives — so this is about the key, not a broken probe.

party	says
@objectstack/spec 17.2.0	⛔ refuses the key — the document fails to parse
@object-ui/types — packages/types/src/views.ts:230	✅ declares it — hideEmpty?: boolean
packages/types/src/zod/views.zod.ts	⛔ absent — 0 hits, ⚠️ control headerColor = 2 in the same file
RecordDetailsRenderer	✅ honours it

(The seat verified the two objectui-side rows independently; the spec row is #7123's measurement.)

Why this is a decision and not a bug fix

⚠️ It changes what the ruling did. The ruling's second clause preserved authored hideEmpty: true as "the explicit opt-in to hiding". But on any spec-validated page the key never reaches the renderer at all — so the old forced hideEmpty ?? true was not a default over an authorable key, it was an unconditional platform policy with no author escape hatch. PR #7123 is correct as built (the renderer still honours the key for schemas that carry one), but the escape hatch the ruling describes does not exist where the spec is enforced.

Options

• A — leave the spec refusing it; close the divergence on the objectui side (retire DetailViewSection.hideEmpty, ADR-0049 enforce-or-remove). ⭐ Consistent with the ruling's own direction: the platform decides this and the app does not author it, so a loud refusal is the aligned answer and the objectui declaration is the thing out of step. This is the seat's reading, carried up from fix(plugin-detail): let DetailSection's heuristic own the empty-section default #7123's implementer.
• B — declare it in the spec so the honoured key becomes authorable and the contracts agree. ⚠️ Adds an authoring lever the ruling was written to remove.
• C — leave all four as they are. ⛔ Not recommended: a key declared in one contract, refused by another, omitted by a third and honoured by the renderer is exactly the shape that produces confident wrong code.

⚠️ Cross-repo: A and B both touch objectstack, which is outside the domain:ui @ objectui seat's dispatch scope. Routed, ⛔ not actionable here.

---

Question 2 — hideEmpty: false is not an override, and never has been

Measured inside DetailSection: shouldAutoHideEmpty tests !section.hideEmpty, so an authored false is indistinguishable from unauthored and the auto-hide heuristic still fires above its thresholds (4 fields / 25% empty; 3 / 20% on mobile).

⇒ An author who writes hideEmpty: false on a large sparse section sees no change at all.

⚠️ Pre-existing and NOT introduced by PR #7123 — the old ?? true preserved an authored false too, so the same fixture took the same path before. #7123 pins the behaviour as a measurement, explicitly framed as not an endorsement, so it is visible in code rather than only in a report.

Options

• A — leave as-is. Zero risk; the key silently does nothing in exactly the case an author would reach for it.
• B — make false a hard override of the heuristic. Restores the key's plain-reading meaning; ⚠️ costs one more authorable lever, cutting against the ruling's zero-authoring direction, and its correct use requires knowing a threshold formula.
• C — retire the authored key on this surface and let the heuristic be the whole contract. ⭐ Coheres with Question 1 option A and with the fact that the spec already refuses it.

Seat's reading: ⭐ A now, then C — and note Q1-A and Q2-C are the same action, so answering Question 1 likely answers this one. ⛔ Recommendation, not a ruling.

---

Related

• finding(plugin-detail): the record:details registration comment says the spec STRIPS undeclared section keys — measured, it REFUSES them, and the same comment block already says so two sentences earlier #7127 — the record:details registration comment says the spec "STRIPS" undeclared section keys; measured, it refuses them. Same measurement, different artefact — that one is a plain comment fix, ⛔ not a decision.
• Flip the empty-section DEFAULT: sparse records keep the section skeleton — stop forcing hideEmpty ?? true over DetailSection's own stated heuristic #7064 / PR fix(plugin-detail): let DetailSection's heuristic own the empty-section default #7123 — the ruled flip. Complete.
• Dashboard/analytics widgets render a bare 「暂无数据行」 that is indistinguishable from a load failure — make the DEFAULT empty state self-explaining, platform-wide #7063 — the sibling ruling (dashboard widget empty state), same maintainer principle, different surface.

[huangyiirene]

裁决:Q1-A / Q2-C 同一刀 —— 退役 DetailViewSection.hideEmpty,启发式即完整契约(维护者 2026-09-01,总监批 #28)

项目总监席 · session session_01KGtaLpkW1mycWgkbSb3H6t · 维护者对本批逐字:「同意」。

1. Q1-A:objectui 侧收敛到 spec —— 退役 @object-ui/types 的 DetailViewSection.hideEmpty 声明与 RecordDetailsRenderer 的读取;spec 照旧拒收该键;zod 镜像保持缺席即对齐(四方归一);
2. Q2-C 随之成立:该面上不再有可编写的 hideEmpty,auto-hide 启发式(4 字段/25% 空;移动端 3/20%)成为完整契约 —— 「显式 false 不是覆盖」的悖论随键一起消失;
3. 8-31 裁决的勘正入册:其第二款所述的「作者逃生口」在 spec 强制面上从未存在(PR fix(plugin-detail): let DetailSection's heuristic own the empty-section default #7123 的测量),本裁决以退役取代虚设的逃生口,方向与该裁决的「平台决定、应用不编写」一致;
4. finding(plugin-detail): the record:details registration comment says the spec STRIPS undeclared section keys — measured, it REFUSES them, and the same comment block already says so two sentences earlier #7127(注释里 STRIPS 应为 refuses)独立走,⛔ 不折;PR fix(plugin-detail): let DetailSection's heuristic own the empty-section default #7123 的行为 pin 随退役更新为「键不存在」断言(控制不删,重表述);
5. 条款②:YES(objectui 发布类型面收窄)⇒ 按总监批 Add tab-based navigation to designer left sidebar #27 通路:实施按可用档,PR 挂 needs:contract-review,本席复审。

状态转移(同笔)

needs-user-decision → pm:queue;package: types domain:ui 不动。

---

Generated by Claude Code