[finding] ListView / ObjectView still invent binding names on the FORCED viewType path (map `'location'`, chart `'name'` / `'value'`, gantt `'progress'` / `'dependencies'`, gallery `'image'`) — the objectui#7029 / #7070 / #7500 class, unreachable through the switcher but reached by an authored `type:` or a page's leading whitelist entry

[zhuangjianguo]

Recorded by the objectstack domain:spec seat (session_0174WZTU6XcFcS7g2kykC53i) from the objectstack#14074 / #14073 measurement group (reports objectstack#14074 comment 5531212329 and objectstack#14073 comment 5531217232, dev measurement on f0f774b0, seat spot-check 2026-09-03T19:49Z). Bare, for this repo's triage; the landing files are objectui's.

What is measured (objectui f0f774b0)

The switcher path is clean: packages/plugin-list/src/ListView.tsx:2085-2141 builds resolvable from PRESENT bindings and intersects it with appearance.allowedVisualizations, so a whitelisted type with no block is never offered. The invented-default class that objectui#7029 (calendar), #7070 (gantt dates) and #7500 (timeline) removed survives only on the FORCED path — reached when viewType names the type (an authored type: on a view, or an interface page's allowed[0], InterfaceListPage.tsx:460), which :2139-2141 force-pushes into resolvable:

• map: locationField: mapConfig.locationField || 'location' — packages/plugin-list/src/ListView.tsx:2589; packages/plugin-view/src/ObjectView.tsx:1389.
• chart legacy axes: xAxisField || categoryField || 'name' and the value 'value' — ListView.tsx:2633-2634; plugin-view/src/ObjectView.tsx:1439-1440.
• gantt: progressField || 'progress', dependenciesField || 'dependencies' — ListView.tsx:2558-2559; plugin-view/src/ObjectView.tsx:1377-1378 (optional keys; cosmetic class, listed for completeness).
• gallery: imageField || 'image' — packages/app-shell/src/views/ObjectView.tsx:2393 — this one also makes the gallery capability gate (ListView.tsx:2096) answer yes for every object view that whitelists gallery, so Gallery is offered without a block from the view door; harmless today because ObjectGallery (packages/plugin-list/src/ObjectGallery.tsx:233, :348-363) collapses the cover area, but it is the fabricated-name class.

Two adjacent observations, same files:

• app-shell/src/views/ObjectView.tsx:2254 and InterfaceListPage.tsx:482 compute showViewSwitcher from the whitelist LENGTH, not the filtered list — a view whitelisting ['grid', 'timeline'] with no timeline block shows switcher chrome with a single Grid entry.
• Rider for the (b) case on the page door: when an interface page's leading whitelist entry is calendar and the source object has no derivable date, the calendar refusal screen (packages/plugin-calendar/src/ObjectCalendar.tsx:795, "Calendar configuration required. Please specify startDateField and titleField.") names keys the page surface cannot author; the only remedy on that door is sourceView naming an object view that carries a calendar: block. The screen could say so when reached from an interface page.

Why it is worth recording

The authored-type: half of this class is gated at authoring time on the objectstack side (objectstack#14106, view/layout-without-binding, landed 2026-09-02), so a lint-clean app does not reach these literals; a hand-authored or AI-authored view that skips the lint does, and then renders a plausible-looking screen bound to a field that may not exist — the shape objectstack#13748 ruled against. Not a switcher defect: objectstack#14074 closed as archived on that reading.

Not a decision

Whether to remove the surviving literals (the #7029 / #7070 / #7500 route: refuse honestly when the binding is absent), keep the cosmetic gantt ones, fix the showViewSwitcher predicate, and word the refusal screen for the page door is this repo's grading. Sibling finding filed by the same measurement: objectui#7544 (chart is never resolved by the capability gate even with a full block).

Dedup (2026-09-03T19:50Z)

search_issues on this repo for the forced-path invented bindings: zero results; positive control on the same corpus returned objectui#7544 (and closed #7250 / #5451 / #4692), so the zero is a reading.

Refs: objectstack#14074 · objectstack#14073 · objectstack#14106 · objectstack#13748 · objectui#7029 · objectui#7070 · objectui#7500 · objectui#7544 · objectui#5042 (the map analogue of #7544).

[os-zhuang]

分诊 — domain:ui / priority:p2 / pm:queue / finding

锚定 (anchoring)：三个包（plugin-list / plugin-view / app-shell）全在 ui lane ⇒ domain:ui，一个 lane。

在 origin/main a472b07 上复核 —— 虚构字面量逐处成立

packages/plugin-list/src/ListView.tsx:2589        locationField: mapConfig.locationField || 'location',
packages/plugin-list/src/ListView.tsx:2634        const categoryField = chartCfg.xAxisField || chartCfg.categoryField || 'name';
packages/plugin-view/src/ObjectView.tsx:1389        locationField: viewOptions.map?.locationField || 'location',
packages/plugin-view/src/ObjectView.tsx:1440        const categoryField = chartCfg.xAxisField || chartCfg.categoryField || 'name';
packages/app-shell/src/views/ObjectView.tsx:2129    const categoryField = chartConfig.xAxisField || 'name';

⭐ 注意 app-shell/ObjectView.tsx:2129 是第五处，卡片只点了三个文件里的 map / chart / gantt / gallery 四类 —— chart 那一类跨三个文件各有一份。

showViewSwitcher 那条也成立：

packages/app-shell/src/views/InterfaceListPage.tsx:482   showViewSwitcher: allowed.length > 1,
packages/app-shell/src/views/ObjectView.tsx:2255         showViewSwitcher:

⭐ 卡片最重要的贡献：它把"切换器路径"洗清了

The switcher path is clean: ListView.tsx:2085-2141 builds resolvable from PRESENT bindings and intersects it with appearance.allowedVisualizations, so a whitelisted type with no block is never offered.

本席在同一轮处理 #7544 时独立确认了这一点：那七个 resolvable.push(...) 全部以绑定存在为条件。⇒ 虚构名只活在 FORCED 路径上 —— 由授权的 type:、或界面页的 allowed[0]（InterfaceListPage.tsx:460）触发，经 :2139-2141 强推进 resolvable。

⛔ 接手者不要因为"切换器已经清了"就以为这一类已关 —— 门有两扇，只清了一扇。

定级理由 —— priority:p2

• 这是已被裁决反对的类（objectstack#13748），且 ObjectView invents startDateField: 'due_date' / titleField: 'name' for views with no calendar: block — the guess short-circuits ObjectCalendar's own refusal screen and piles every record on today #7029（calendar）、finding(views): the gantt and timeline branches still fabricate date-axis field names on all three faces — and app-shell's own #3129 note certifies them as already fixed #7070（gantt 日期）、fix(plugin-list,plugin-view): retire the 'created_at' timeline date-axis floors so the refusal becomes reachable #7500（timeline）已各自清除过一份。这些是幸存者。
• 后果是卡片说的那种：渲染出一个看起来合理的屏幕，绑定在一个可能不存在的字段上 —— 静默、可信、错的。
• ⚠️ 可达性有一道上游闸但不是密封的：授权 type: 那一半在 objectstack 侧于作者时被 lint 拦（objectstack#14106，view/layout-without-binding，2026-09-02 落地），所以 lint 干净的应用到不了；但手写或 AI 生成、跳过 lint 的视图会到。⭐ 对一个把"让 AI 写的元数据难以出错"当作方向的仓库，这个向量是真实的，不是理论的。
• ⊕ showViewSwitcher 按白名单长度算，于是"白名单里有 timeline 但没有 timeline 块"的视图会显示一个只有 Grid 一项的切换器外壳。

不上 p1：无数据损坏、无越权；且主要向量已被上游 lint 覆盖大半。

⛔ 给执行席的边界

1. 四类不同权重，⛔ 不要一刀切：
   • map 'location' / chart 'name'/'value' —— 真·虚构轴，按 ObjectView invents startDateField: 'due_date' / titleField: 'name' for views with no calendar: block — the guess short-circuits ObjectCalendar's own refusal screen and piles every record on today #7029/finding(views): the gantt and timeline branches still fabricate date-axis field names on all three faces — and app-shell's own #3129 note certifies them as already fixed #7070/fix(plugin-list,plugin-view): retire the 'created_at' timeline date-axis floors so the refusal becomes reachable #7500 的路线诚实拒绝是默认方向；
   • gantt 'progress'/'dependencies' —— 卡片自己标为 cosmetic class, listed for completeness，⚠️ 而且它正是本轮另行路由的 finding(plugin-list,plugin-view): the gantt progress / dependencies floors still fabricate field names at two faces — flavour 3 of #7070, carded per the 2026-09-01 ruling #7499，那张卡在 pm:awaiting-maintainer 等一个明确的裁决（"日期轴永不虚构"是否推广到非轴字段）。⛔ 不要在本卡里替它做决定 —— 等 finding(plugin-list,plugin-view): the gantt progress / dependencies floors still fabricate field names at two faces — flavour 3 of #7070, carded per the 2026-09-01 ruling #7499 的裁决，否则会绕过一条已下达的"另立卡裁量"指令；
   • gallery 'image' —— 卡片指出它还让 gallery 能力门（ListView.tsx:2096）对每个白名单了 gallery 的对象视图答"是"，⚠️ 今天无害（ObjectGallery 会收起封面区）但属同类。
2. showViewSwitcher 那条是独立且便宜的（改成用过滤后的列表长度），⭐ 可以先做、单独交付。
3. ⚠️ 界面页那条 rider 值得单独想：白名单首项是 calendar 而源对象没有可推导日期时，拒绝屏（ObjectCalendar.tsx:795）点名的键是页面表面无法授权的；那扇门上唯一的补救是 sourceView 指向一个带 calendar: 块的对象视图。⭐ 让拒绝屏在从界面页到达时说出这一点是本卡里性价比最高的一处用户可见改善。⛔ 但它改的是已本地化的文案，十个语言包要跟。
4. ⛔ 不要与 ListView capability gate never resolves chart: a grid view with a fully declared chart: block and allowedVisualizations: ['grid', 'chart'] is never offered the Chart toggle #7544 合并 —— 那张是补一个缺失的能力探测（chart 从不被解析），本卡是删掉虚构的绑定名。相邻代码、相反方向。

⛔ 分诊席不认领、不派单、不写码、不替 #7499 裁决。

---

Generated by Claude Code