finding(examples,skills): two in-repo authored nodes put config under the inert `props` envelope on a component-renderer node

[claude]

Found by the corpus census the objectui#6708 ruling required before its diagnostic's level could be chosen. Filed rather than fixed: objectui#6708's PR is the SchemaRenderer-tier diagnostic and changes no authored metadata.

The mechanism (settled, not re-litigated here)

SchemaRenderer hoists properties.* onto the node; props is evaluated and then spread as React props instead. A renderer declared as ({ schema }) — the normal component-renderer shape — never sees it. The element:* family is the exception, because its readProps() merges both bags. Every gate accepts the spelling: BaseSchema is .passthrough().

The two hits, measured on faac0d935

where	node	keys under props	the renderer reads
packages/types/examples/data-display-examples.json (compositeExample)	flex	direction, gap	schema.direction, schema.gap — flex.tsx
skills/objectui/guides/page-builder.md	statistic	label, value	schema.* — StatisticRenderer is declared ({ schema })

Both therefore render as if the bag were empty: the flex node gets the default row direction and the default gap whatever the example says, and the statistic node renders with no label and no value. Both are published teaching material presented as correct.

The skills one is the higher-leverage half: the published skills corpus is what an AI author learns the spelling from, and this is the same failure class as objectui#5473 and objectui#5947.

What is NOT a hit, and should stay as it is

Three other authored occurrences of the same shape are deliberate counter-examples, already marked as wrong where they stand, and must not be "fixed":

• skills/objectui/rules/protocol.md — a card with props: { title }, immediately followed by the measurement table showing it renders no header;
• skills/objectui/guides/schema-expressions.md — a card and a text node, both flagged with a cross mark and the words "evaluated, then dropped".

Census scope

Every JSON document, every json fence in every .md/.mdx, and every TypeScript object literal in the repo, walked for nodes carrying both type and props: 39 nodes, 22 on component-renderer types, 19 of those 22 test fixtures exercising the shape on purpose. These two are the whole authored, non-test remainder that is not a counter-example. No application runtime metadata in the repo carries the shape.

Suggested fix

Mechanical, and the correct target differs per node: both flex and statistic declare their keys at NODE level in their schemas, so the fix is to lift the keys out of the envelope rather than to rename props to properties. Worth confirming against each schema before editing.

Related: objectui#6708 (the diagnostic that now names this at render), objectui#6508 (a different defect in the same guide file), objectui#5473, objectui#5947.

---

Generated by Claude Code

[huangyiirene]

定级：pm:queue · domain:skills · priority:p2。

⛔ 接手前必读的一条，比修复本身重要：卡里点名了三处不得动的同形写法——skills/objectui/rules/protocol.md 的 card（下面紧跟着证明它不渲染 header 的测量表）、skills/objectui/guides/schema-expressions.md 的 card 与 text（都打了叉、写着 "evaluated, then dropped"）。它们是故意的反例，是教材的一部分。把它们"修好"等于删掉教学内容。任何以"统一 props→properties"为名的批量改写都会踩中这三处 ⇒ ⛔ 禁止批量替换，逐节点确认。

车道：本卡两个落点分属两条车道，不拆卡，理由如下——

落点	车道	合并方式
skills/objectui/guides/page-builder.md	domain:skills	治理面 ⇒ 人工合并
packages/types/examples/data-display-examples.json	domain:spec（本仓三流规则：packages/types 属 spec 流）	常规

主车道判 domain:skills：skills/** 是治理面，只要 PR 碰它就整体走人工合并，所以拆成两张卡省不下人工那一步，只会多一次派发。packages/types 那半作为同一 PR 内的跨车道搭车项登记在此，⛔ 不要因为它不在 domain:skills 就漏掉。

（对照 objectstack#13072：那张我拆了，因为两半是两种不同的工作。这张两半是同一个两行机械编辑，拆卡的成本大于收益。判据是"工作是否同形"，不是"车道是否相同"。）

修法：⛔ 不是把 props 改名成 properties。flex 与 statistic 都在 NODE 层声明自己的键，所以正确动作是把键从信封里提出来放到节点上。卡里已写"Worth confirming against each schema before editing" —— 请照做，两个节点分别对着各自 schema 确认。

⚠️ 这是同一类的第三次（#5473、#5947，现在是本卡），都在已发布的 skills 语料里，都是"AI 作者从教材学到错误拼写"。#6708 的诊断现在能在渲染期指出这个形状，机制已经存在；它是否应该跑在 skills 语料上是一个尚未有人提的问题。⛔ 我不在本卡代裁，也不把它塞进本卡范围——已作为"类卡是否该立"登记给维护者。

⭐ 立卡人的普查值得记一笔：全仓 JSON 文档 + 所有 .md/.mdx 的 json fence + 所有 TypeScript 对象字面量，39 个带 type+props 的节点，22 个落在 component-renderer 类型上，其中 19 个是故意练这个形状的测试夹具。剩下的非测试、非反例的全部就是这两个。这是一个有分母的普查，不是抽样——所以"只有两处"是个结论，不是"只找到两处"。

---

Generated by Claude Code

[huangyiirene]

⚠️ 本轮治理合并审计的发现：本卡的两个相关文件在定级后 20 分钟内各被一次治理合并动过。取卡前必须重新核。

审计窗口 objectstack=1a540e82 → objectui=4a4c6a6（07:02–07:04Z），两笔治理合并都落在 skills/**，且都是本卡点名的文件：

PR	提交	文件	与本卡的关系
objectui#6742	4a4c6a61d @ 07:04:06Z	skills/objectui/guides/page-builder.md	⚠️ 本卡要修的两个站点之一就在这里
objectui#6738	3cef56290 @ 07:02:36Z	skills/objectui/guides/schema-expressions.md	⛔ 本卡列为"不得动"的反例文件

⛔ 两件必须做的重新核验

1. page-builder.md —— 本卡的 statistic 站点是否还在？

#6742 的标题是 "put the GanttConfig keys back under the gantt block" ⇒ 看起来与本卡的 statistic 节点无关（那是 GanttConfig，不是 props 信封）。但它改动了同一个文件 ⇒ ⛔ 行号与上下文已经移动。取卡人请按内容重新定位，⛔ 不要照抄本卡的描述去找位置。

2. ⚠️ schema-expressions.md —— 那两个"故意的反例"是否被 #6738 改掉了？

本卡明确把该文件里的 card 与 text 两个节点列为不得修复的教学反例（打了叉、写着 "evaluated, then dropped"）。而 #6738 的标题是 "stop teaching the table renderer's retired column aliases" —— 一次以"停止教错东西"为名的清理，正是最可能顺手把反例一起"修好"的那类改动。

⇒ ⛔ 取卡前先读 #6738 的 diff，确认那两个反例仍然完整。若它们已被删掉或改写，那是一个独立的新问题（教学反例被当成缺陷清除），⛔ 请回填立卡，不要在本卡里悄悄补回去。

⭐ 我在本卡上写下"这三处是故意的反例、不得修"时，⛔ 并不知道其中一个文件在 22 分钟前刚被动过。这正说明那条围栏是必要的——但也说明围栏写在卡上不等于它生效了。

关于审计本身的两条限制，照实说明

• merged_by 读不到：objectui 两笔的归属在所有通道上都是 403（env token 与匿名 REST 均失败）。⇒ ⛔ 我不能确认这两笔是维护者本人执行或指派的。按 fix(types): retire VectorFieldMetadata.indexed and .distance_metric #4690 的规矩，这不算"已审计通过"，只算"已列出"。
• 两个治理仓完全未审：cloud 与 objectos 本会话无检出。⛔ 未审的仓不是干净的仓——那里什么都没发现，是因为什么都没看。

---

Generated by Claude Code