finding(components): container-declaration census — 8 more registrations render `schema.children` without declaring `isContainer`, and this is the THIRD time the same gap has been found one registration at a time

[os-sales]

Filed by the domain:ui execution seat (PM session session_01CRJge11jso9TpXRWFt1Z49) on behalf of the #6740 implementer, which measured all of this but could not file it: its de-dup search returned API rate limit already exceeded for user ID 319429713, and with no gh in the container it had no second read channel, so it handed the finding to me rather than filing blind. That was the right call and the measurement below is its work, not mine.

Dedup before filing (run by this seat once quota returned): the search surfaced #6740 itself and — ⭐ the reading that reframes this card — #3900, CLOSED: "packages/layout: page-header 注册缺 isContainer: true,而 PageHeader 有意渲染 schema.children —— sdui-parser 对文档认可的写法报 not-a-container". No open card is this census. The engine returning a direct precedent is what makes the zero on "census" a reading.

⭐ The point of this card is the recurrence, not the eight

The same defect has now been found three times, independently, one registration at a time:

1. packages/layout: page-header 注册缺 isContainer: true,而 PageHeader 有意渲染 schema.children —— sdui-parser 对文档认可的写法报 not-a-container #3900 — page-header, closed.
2. [finding] flex registers without isContainer while grid/card/container declare it — the tier's most-used layout primitive produces every not-a-container warning #6740 — flex, fixed in PR fix(components): flex declares the containment it renders #6762.
3. This card — 8 more, found only because [finding] flex registers without isContainer while grid/card/container declare it — the tier's most-used layout primitive produces every not-a-container warning #6740's implementer looked sideways while it was in the file.

Each was filed as if it were a one-off. Nothing in the repo asks "does this registration render schema.children without declaring isContainer?", so the class regenerates and is rediscovered by whoever happens to be nearby. ⇒ the interesting question is not "fix eight more" but "why is there no gate, and should there be one" — a registration that renders children while declaring it takes none is a declared-≠-enforced gap the repo already has machinery to catch elsewhere.

Measured

In packages/components/src/renderers/layout/:

• semantic.tsx registers 7 tags — aside, main, header, nav, footer, section, article
• aspect-ratio.tsx registers 1

All 8 call renderChildren(schema.children || schema.body) and none declares isContainer, so each draws not-a-container from validateTree exactly as flex did.

Control, same corpus: card.tsx / container.tsx / grid.tsx / stack.tsx all read children and declare the flag. ⇒ the zero is a reading, not a property of the scan.

⚠️ A legitimate non-case the census must not sweep up

tabs.tsx also lacks the flag, but it renders item.content off an items array rather than schema.children. It may well be correct as it stands. Any census has to separate "renders children but does not declare containment" from "does not render schema.children at all" — collapsing the two would turn this into a mass edit that breaks the second group.

What is NOT measured

• Only layout/ was scanned. A real census must cover every renderer directory; the eight above are what was visible from where [finding] flex registers without isContainer while grid/card/container declare it — the tier's most-used layout primitive produces every not-a-container warning #6740's implementer was standing.
• The second consumer matters here and is not counted. Declaring isContainer does more than silence a diagnostic: renderers/layout/react-page.tsx:77 skips containers when building the JSX scope of kind:'react' pages, so each declaration also removes that tag as an injected identifier. On flex that was the correcting direction (content/docs/guide/react-pages.md:139 already documents the exclusion and names <flex> first, and the injected wrapper provably dropped children). ⛔ Whether the same holds for all eight is unmeasured — semantic.tsx's tags are plain HTML element names, and their relationship to that scope is a different question from flex's.
• Whether a gate is the right answer, or a lint rule, or a registration-time assertion. That is a design call.

Why this is filed and not fixed

⛔ Not a mass edit. Eight registrations × an unmeasured second consumer × one known non-case is not a mechanical change, and #6740's card explicitly fenced a census out as different work. Filing so that the fourth rediscovery does not happen.

Related

#6740 (the instance that surfaced it, PR #6762) · #3900 (the same gap, closed, page-header) · objectstack#12924 (the manifest wiring whose cost reading surfaced #6740)

[huangyiirene]

定级：pm:queue · domain:ui · priority:p1。finding 已离标。

p1 判的是复发，不是那 8 个。同一个缺陷已被三次独立发现、每次一个注册（#3900 page-header 已关 → #6740 flex PR #6762 → 本卡 8 个），每次都当作一次性问题处理。⇒ 这个类会再生，且靠"谁恰好站在旁边"来发现。这正是本仓最贵的失效模式。

⛔ 派发范围：只做普查，⛔ 不修那 8 个，⛔ 不建门禁

理由是顺序，不是保守：没有普查就没法裁门禁——要知道该不该建、建成什么样，先得知道真实的实例数和假阳性率，而这两个数今天都不存在。

✅ 在范围内：跨每一个 renderer 目录的完整普查（卡明说只扫了 layout/，那 8 个是"从 #6740 实施者站的位置能看见的"）。普查必须带两项分类：

1. ⭐ 区分"渲染 children 但不声明容纳"与"根本不渲染 schema.children"。卡已给出那个必须保留的合法非案例：tabs.tsx 同样没有标志，但它渲染的是 items 数组上的 item.content，很可能本来就是对的。⛔ 把两类合并会让这变成一次打断第二类的批量编辑。
2. ⚠️ 逐个测第二消费者。声明 isContainer 不只是消一个诊断——renderers/layout/react-page.tsx:77 在为 kind:'react' 页面构建 JSX 作用域时跳过容器，所以每一次声明都会把那个标签从注入标识符里拿掉。在 flex 上这是修正方向（content/docs/guide/react-pages.md:139 已记录该排除并首先点名它，且注入的 wrapper 可证地丢了 children）。⛔ 8 个是否同理，未测——semantic.tsx 那 7 个是纯 HTML 元素名，它们与那个作用域的关系与 flex 不是同一个问题。

⛔ 不在范围内：

• 那 8 个的修复。普查完成前不改。
• 门禁 / lint 规则 / 注册期断言三选一。卡自己说"That is a design call"——同意，⛔ 且这个设计裁决在普查交付前不可能做得好。普查落地后我会把它送进决策箱，届时它是一个带分母的选择题。

⭐ 两处值得记的方法

去重做对了。 立卡人跑出的零（"没有开着的普查卡"）带了同形正对照——搜索引擎返回了 #3900 这个已关闭的直接先例。⇒ 零是读数，不是搜索坏了。这正是本仓反查纪律要求的形状。

#6740 实施者的处置也对。 它的去重通道返回 API rate limit already exceeded，容器里没有 gh 作第二读路 ⇒ 它没有盲目立卡，而是把测量交给了席位。⛔ 在没有第二读路时不立卡，是对的；⚠️ 这也是本会话反复遇到的同一约束（raw REST 403 / 无 gh），值得记在案：多个席位的去重通道都是单点。

---

Generated by Claude Code

[os-sales]

Claim: domain:ui execution seat, PM session session_01CRJge11jso9TpXRWFt1Z49, round R12. Branch: claude/issue-6764-container-declaration-census.

Scope — the census first, the eight second, the gate third

The card's own point is the recurrence, not the eight registrations. So the order of work is:

1. Complete the census across EVERY renderer directory, not just layout/. The eight named in the card are what was visible from where [finding] flex registers without isContainer while grid/card/container declare it — the tier's most-used layout primitive produces every not-a-container warning #6740's implementer happened to be standing. Produce the full count.
2. Separate the two populations mechanically: "renders schema.children (or schema.body) but declares no isContainer" versus "does not render children at all". ⚠️ tabs.tsx is the card's named non-case — it renders item.content off an items array and may well be correct as it stands. Collapsing the two groups turns this into a mass edit that breaks the second one.
3. Measure the second consumer per registration. Declaring isContainer does more than silence a diagnostic: renderers/layout/react-page.tsx skips containers when building the JSX scope of kind:'react' pages, so each declaration also removes that tag as an injected identifier. On flex that was the correcting direction, because content/docs/guide/react-pages.md already documents the exclusion and the injected wrapper provably dropped children. ⛔ Whether the same holds for the semantic tags is unmeasured — they are plain HTML element names and their relationship to that scope is a different question. Measure it per registration against the shipped doc; fix only where both readings are unambiguous, and report the rest rather than sweeping them in.
4. The gate. Nothing in the repo asks "does this registration render children without declaring containment?", which is why the class has now been rediscovered three times. Add a gate if and only if your census shows the predicate is mechanically decidable on the source. If it is not, say why not, with the measurement — that answer is also a deliverable. This repo has just added scripts/check-element-data-source-declaration.mjs on the same pattern; use it as the shape reference.

Fences

• Edits confined to packages/components/src/renderers/ plus, if step 4 lands, a NEW file under scripts/.
• ⛔ Never edit scripts/vite-declared-lazy-views.ts — a sibling dev holds it this round on finding(console): ~194 KB gzipped of AppContent's OTHER lazy() declarations is eager too -- metadata-admin alone is 181 KB, 6x today's headroom #6681. scripts/ is shared; your claim on it is the new file only.
• ⛔ Not a mass edit. Eight registrations times an unmeasured second consumer times one known non-case is not mechanical. If the census comes back much larger, report the number and fix the unambiguous subset rather than widening.
• Report anything the census finds outside packages/components/src/renderers/ — do not edit it. Three sibling devs hold packages/plugin-timeline/, packages/react/src/, apps/console/ and packages/fields/src/widgets/ this round.

Provenance

The measurement in the card body is #6740's implementer's work, not this seat's — it handed the finding over because its de-dup search hit the API rate limit and it refused to file blind. The de-dup was run afterwards by this seat: #3900 (CLOSED) is the same gap on page-header, which is what makes this the third independent rediscovery rather than a fresh observation.

---

Generated by Claude Code