@object-ui/core 里第二个 mergeViewsIntoObjects:仓内零消费者,且丢掉容器的默认 list、用裸键而非组装器身份

做 #3770 时清扫「规则的消费半径」发现的,观察类(dormant code,今天没有用户会撞上),按 PD #10 立单记录,不在该单范围内。

事实

仓里有两个 mergeViewsIntoObjects:

packages/app-shell/src/providers/MetadataProvider.tsx —— 真正在用的那个。app-shell 用已退休的 || 'list' 方言给默认列表视图命名,与组装器身份 default 不一致 —— 默认列表的译文键在 objectui 永远命不中 #3770 之后它对容器调 expandViewContainer,视图身份一律 {object}.{key}(含默认 list 的隐式 {object}.default),并继承组装器的折叠 / 改名去重。
packages/core/src/utils/merge-views-into-objects.ts —— 由 packages/core/src/index.ts 公开导出,但全仓零消费者(grep mergeViewsIntoObjects:只有 app-shell 自己的实现与测试,data-objectstack 仅在注释里提了一句「mirroring MetadataProvider.mergeViewsIntoObjects」)。

第 2 个的行为与第 1 个已经不是一回事:

只读 view.listViews,完全忽略容器的默认 list —— 经它合并的对象拿不到主列表视图;
键用作者写的裸键(all),不是组装器身份({object}.all),因此下游按 view.name || view.id 去解析 _views 译文键时,行为与 app-shell 那条路径不一致;
对象名从 listView.data.object 反推,而 app-shell 那条还接受 view.name 与 form.data.object。

ROADMAP.md:1428 还挂着一条未完成项:「Move mergeViewsIntoObjects from composeStacks to runtime/provider layer」—— 这个 core 版本正是那次搬迁留下的中间态。

为什么记成观察类而不是缺陷

它没有仓内调用方,所以今天没有任何用户路径会命中上面三条差异;但它是 @object-ui/core 的公开导出,外部消费者拿到的是一个与真实渲染路径已经分叉的实现,而分叉点恰好是 #3770 刚统一掉的那个(视图身份)。留着不管的风险是下一个 agent 把它当成「那个 merge」去读或去改。

方向留给分诊:要么删(公开导出,需按 objectui 的破坏性变更约定走 changeset,注意 AGENTS.md 的「不要声明 major」),要么让它内部委托到同一段组装器逻辑。

相关

app-shell 用已退休的 || 'list' 方言给默认列表视图命名,与组装器身份 default 不一致 —— 默认列表的译文键在 objectui 永远命不中 #3770 / 其 PR(app-shell 侧改为向组装器要身份)
ROADMAP.md:1411 / 1416 / 1428(这个 adapter 的来历)
查重已做:objectui open issues 搜 mergeViewsIntoObjects,只有 Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890(ListView 词汇迁移,另一件事)。

Finding-triage ruling: Hold (why still held): the second mergeViewsIntoObjects in core has zero in-repo consumers and diverges from the live app-shell merge, but removing a public export is a changeset-discipline change, not a drive-by; the record's chief value is stopping the next agent from mistaking it for the live merge. Restart: the next dead-code sweep or the next core public-surface changeset (ROADMAP.md:1428 item still unchecked).

Authorization: maintainer directive (this session) —「对于issue中的findings 执行一次集中分诊，并更新issue 的状态。」Centralized pass under that directive; finding grading is normally the triage seat's single channel. Round: objectstack#4949 finding-triage, 2026-08-10.
Session: 01JaVVMrSxt7Tgi1uwEuDtH7

Generated by Claude Code

Findings triage (re-verify @ origin/main da81093): HOLD — the second copy (packages/core/src/utils/merge-views-into-objects.ts) still exists, is still publicly exported (core/src/index.ts:34), and still has zero in-repo consumers (the only new grep hit since filing, clientValidation.ts:76, is a comment). Divergence from the app-shell path stands. Exit is delete-with-changeset vs delegate — a public-API call, held for a ruling. finding stands.