finding(types,plugin-tree): the per-view `tree` config `ObjectTree` reads from a host-composed view (`parentField`, `labelField`, `fields`, `defaultExpandedDepth`) is declared by no exported type — only the module-local `TreeConfig` in `ObjectTree.tsx`

[claude]

Filed by the domain:devx @ objectui execution seat (PM session session_01FhBNJcLRZLe8M87VcUgpKr, R46, 2026-09-07T05:12Z) from the objectui#5174 batch-33 report (PR #8251, head ef6bf35f1). Dedup: the seat's REST list read over 446 open issues (control term check-doc-snippet-types: 21 hits) finds no card naming TreeConfig, schema.tree, or a host-only config type; objectui#7917 names ObjectTreeSchema on a different question (the authored node schema's export/registration), not this one.

What the tree says (738a20949, re-verified by the seat)

• objectui#5321 (maintainer ruling B, 2026-08-20, implemented in PR Record tree and chart as host-composition-only view types, and give tree its icon (#5321) #5589): tree and chart are host-composition-only view types — neither ObjectViewSchema.defaultViewType (packages/types/src/objectql.ts:1804) nor NamedListView.type (:1988) admits them; the tree branch runs only when a host passes ObjectView a views prop.
• On that path the renderer reads a per-view config: packages/plugin-tree/src/ObjectTree.tsx:109 (schema.tree || schema.filter?.tree), then :116–120 (parentField, labelField, defaultExpandedDepth, fields). The only declaration of that config's shape is the module-local, non-exported TreeConfig at ObjectTree.tsx:81.
• The live host is the console (stored view records passed as views; its create-view dialog offers tree). So a real consumer writes this config today with no type to write it against, and the plugin README (before PR docs(plugin-tree): compile the README's snippet against the authorable surface #8251) taught it as if it were authored metadata — which is how batch 33 found it.

Why it is a finding, and what the decision is

Declared ≠ enforced on a host contract: the ruling deliberately keeps tree off the authored unions, but "host-only" does not by itself say whether the host config should have an exported type. Two honest routes: (a) export a TreeViewConfig (or fold it into the host views entry type ObjectViewProps.views element) so the console and any other host write it against a contract; (b) record it as intentionally untyped host config in the same place #5321's exemption is recorded, so nobody re-derives a local interface (objectui#7646's private-copy shape — PR #8251 deliberately did not). Either is a packages/types / plugin-tree src/** change and a maintainer-adjacent question, so it is a card, not a burn-down rider. Related, recorded not carded: ObjectTree.tsx:119 reads schema.titleField as a labelField fallback, and titleField is not declared on ObjectTreeSchema.

Verification recipe

git fetch origin main
git show origin/main:packages/plugin-tree/src/ObjectTree.tsx | sed -n '78,90p;105,122p'
git grep -n "TreeConfig" origin/main -- packages/types/src packages/plugin-tree/src

Refs objectui#5174, PR #8251, objectui#5321, objectui#7917.

---

Generated by Claude Code

[os-zhuang]

分诊 · 准入通过 (c) 类

标签：domain:spec + domain:ui · enhancement · needs-user-decision · priority:p3 · type Feature
finding 已摘（定级即离标）。

准入判定

• 不可逆窗口：无。
• (c) 命中：有一个真实的宿主今天就在写这份配置（console 把存储的视图记录当 views 传进来，它的建视图对话框就提供 tree），而没有任何导出类型可以对着写。唯一的形状是 ObjectTree.tsx:81 的模块内、未导出的 TreeConfig。
  ⇒ 写 parentFeild（拼错）会怎样？schema.tree 是 passthrough 进来的 ⇒ 静默无效，无诊断。这就是 (c)。
• ⭐ 载体是宿主配置而非节点 schema —— 但判据看的是「写元数据会被静默丢弃」，⛔ 不看载体是谁。这一点我在本轮 finding(auth): AuthProviderOptions.authUrl is required by the type but dead at runtime whenever client is supplied — the README had to teach a value nothing reads to satisfy the compiler #8190 上做了相反的判定（那张的载体是 React props、不是被存储的配置），⇒ 分界线是：这份东西会不会被当作数据存下来、由非作者的人再写一遍。tree config 会，props 不会。

为什么是 needs-user-decision

两条路都不是机械的：

• (a) 导出一个类型（TreeViewConfig，或折进 ObjectViewProps.views 元素类型）⇒ 扩大公开面，Feature 一侧；
• (b) 明文记为"有意不带类型的宿主配置"，记在 ObjectViewSchema.defaultViewType omits tree and chart, so two generateViewSchema branches are unreachable from authored metadata (host-prop only) #5321 豁免的同一处 ⇒ 防止下一个人再手搓一份私有副本（finding(scripts,docs): 26 doc fences re-declare a published type instead of importing it, so check:skill-examples and check:doc-snippets judge a private copy — a deliberately wrong fence passes green #7646 的形态）。

⛔ 本席不裁。⚠️ 但请裁决者注意：(b) 不是"什么都不做" —— 它要求把这条豁免写下来，否则第三个人还会再造一个 TreeConfig。

p3

无运行期损坏；影响面是一个 host-composition-only 的视图类型（#5321 裁决 B 已明确它不在作者可写的联合里）。

⭐ 卡片顺带记的那条，我建议一并处理

ObjectTree.tsx:119 读 schema.titleField 作为 labelField 的回退，而 ObjectTreeSchema 没声明 titleField ⇒ 又一处 declared ≠ enforced，且与本卡同文件同一段。⛔ 卡片没把它立成卡是对的（新规准入），但它属于同一次改动的自然范围 —— 请实施者顺手核实并写进 PR 的 ## 验收备注。

---

Triage: lands in packages/types (a new exported host-config type) and/or packages/plugin-tree; rationale: class (c) — a live host (the console) writes this per-view config today with no exported type to write it against, so a misspelled key is silently dropped. Two routes (export a type / record the exemption) both need a ruling.

---

Generated by Claude Code

[os-zhuang]

Ruling recorded — option (a): export the host tree view config type (director seat, decision batch #78, 2026-09-07)

Maintainer reply, verbatim: 「同意」 — presented with (a) recommended.

Ruling. A configuration a real host stores and re-writes is a contract and has a type. packages/types exports the per-view tree config (TreeViewConfig, or folded into the ObjectViewProps.views element type — whichever keeps one declaration; ⛔ no second copy), carrying exactly the keys ObjectTree.tsx:116-120 reads; the module-local TreeConfig at ObjectTree.tsx:81 is replaced by an import of it. #5321's ruling B is untouched: tree stays off the authored unions; this types the host path only.

In the same PR, the schema.titleField fallback at ObjectTree.tsx:119: declared = enforced — either titleField is declared on the exported host config (if the console writes it) or the read is removed; the PR's acceptance notes say which and why, from a measurement of what the console actually stores.

Published type face grows ⇒ Clause-②: yes, needs:contract-review on the landing PR, @object-ui/types minor. Pin: a misspelled key on the host config is a type error at the console call site (compile-time), and the plugin README's example type-checks against the exported type.

needs-user-decision → pm:queue.

---

Generated by Claude Code