List view `navigation.view` is declared in spec but resolves no form view — its only read lands it in the `onNavigate` navigation-MODE argument

[huangyiirene]

Measured on @objectstack/spec 17.3.0 and the pinned @objectstack/console 17.3.0 bundle, from a real app (objectstack-ai/hotcrm, issue #1716).

The key

ListViewSchema.navigation declares view alongside the keys that describe navigation behaviour:

node_modules/@objectstack/spec/dist/environment-artifact.zod-Bx9Mh1T2.d.ts

  mode: z.ZodOptional<z.ZodEnum<{ page, split, none, modal, drawer, popover, new_window }>>;
  view: z.ZodOptional<z.ZodString>;
  preventNavigation: z.ZodDefault<z.ZodBoolean>;
  openNewTab: z.ZodDefault<z.ZodBoolean>;
  size: z.ZodDefault<z.ZodEnum<{ full, md, auto, sm, lg, xl }>>;

mode and size carry closed vocabularies. view is an unconstrained string with no vocabulary and no resolution step, so any value authors clean and validates clean.

What it actually does

Its only read in the shipped console is the record-navigation hook, which puts it in the second argument of onNavigate — the slot that otherwise carries the literal navigation-mode string:

framework-BfSv4Kb0.js

  function wc(e){ let {navigation:t, objectName:n, onNavigate:r, onRowClick:i}=e,
    l = t?.mode ?? `page`,
    d = t?.view,
    …
    if (l === `page`) { let t = e.id||e._id; r && t != null && r(t, d ?? `view`); return }

So an authored view does not select a view — it substitutes for the mode token. And at least one consumer in the same bundle reads that argument against a closed two-value vocabulary:

index-BU-FzlQ6.js

  onNavigate: (e,t) => { if (t === `edit`) … else if (t === `view`) { navigate to the record page } }

Any authored value other than edit or view matches neither branch there. Other consumers in the bundle take one argument and ignore the second, which is why the effect is invisible on some grids and would be a dead row click on others.

The original finding enumerated the bundle rather than sampling it: every .view property read (exactly three — this one, one on a dataSource, one in mermaid) and every formViews read (formViews?.default in RecordFormPage, useActionModal and RecordDetailView subforms, plus one write in the stored-view normalizer). No read anywhere is keyed by an authored view name. So there is no path by which navigation.view could resolve a named form view, and none by which any other key could either.

Why this is worth a card rather than a doc fix

The name is the trap. view, sitting in a bag next to mode / size / width, reads as "which view to open" — that is exactly how the downstream app authored it, with the comment // Use named form view beside it. It validated, it built, and it selected nothing. This is the ADR-0049 declared-but-unenforced shape, with the extra sharpness that the key is not merely ignored: it is consumed, in a slot that means something else.

Same class as #14108 (app navigation viewName never resolved against the target object's listViews), which shipped a fix in #14286 by extending lintViewRefs. That precedent is why this is filed rather than absorbed: navigation is the well-travelled reference into a view namespace, and this is a second door into it that nothing checks.

What the downstream app did, and did not do

objectstack-ai/hotcrm deleted its one occurrence — a browser reading confirmed the row click was unaffected there, so the key was inert on that grid rather than breaking it. The app has not compensated for the platform behaviour in any other way, and should not: this is a platform surface.

Suggested disposition — enforce or remove

Either honest treatment closes it:

• Enforce — resolve navigation.view against the target object's formViews at lint/build time (the fix(lint): resolve app navigation viewName against the target object's list views #14286 shape), and give the runtime a real read for it, so the key means what its name says.
• Remove — retire navigation.view from ListViewSchema.navigation under ADR-0049. If the mode slot genuinely wants an author-supplied override, it wants a key named for what it does and a closed vocabulary, not a free string named view.

Whichever is chosen, the current state — an unconstrained string whose name promises view selection and whose only read feeds the mode argument — is the one state that teaches authors something false.

---

Generated by Claude Code

[os-litant]

Triage: lands in ListViewSchema.navigation (packages/spec) and its reader; domain:spec; priority:p2; class (c).

ListViewSchema.navigation declares view alongside the keys that describe navigation behaviour (mode: page | split | none | modal | drawer | popover, …) — and its only read lands it in the onNavigate navigation-MODE argument, so it resolves no form view.

⇒ an author writes navigation.view expecting to name a view, and the value is consumed as if it were a mode. ⭐ The key's name promises one thing and its only read does another — which is worse than an ignored key, because the value goes somewhere and does something unintended.

⇒ ⚠️ Two exits, and the measurement decides: either view is meant to name a form view and the read is wrong, or the key is residue and should be retired under ADR-0049. ⛔ Do not assume the second because it is easier; the name is strong evidence of intent.

⚠️ If the exit is retirement, that narrows a published schema ⇒ declare Clause-② and follow the property-retirement playbook. If the exit is to honour it, that is closer to new capability ⇒ stop and report before building.

⭐ Measured on @objectstack/spec 17.3.0 and the pinned @objectstack/console 17.3.0 bundle from a real app (hotcrm#1716) ⇒ shipped behaviour, not a main-only reading.

Size/model suggestion: M.

_{分诊席位 · session_017VGfRocA8VjczSe84fgjY3 · R+166 · 2026-09-10T14:54Z · 本评论来自分诊座位}

---

Generated by Claude Code

[os-bill]

Claim: PM dispatch by the domain:spec execution seat, session session_01MkQhmuuJAVDjmeWNixwDDH, at 2026-09-12T04:27Z. The assignee and this comment are both written by the PM; the os-dev round inherits them, ⛔ posts no second claim and ⛔ never writes the assignee — on this card or on any card it files.

Branch: claude/issue-16885-list-navigation-view-resolves-nothing

• Clause-②: no — the dispatched branch is measure-and-report plus at most a prose/doc correction. ⛔ If your measurement points at retiring the key or at honouring it, STOP — both move a published accept set and the declaration would have to change, which is the SEAT’s act, not yours.

Declared file face (region level) — packages/spec/src/ui/view.zod.ts — ListViewSchema.navigation only. ⛔ packages/spec/src/ui/component.zod.ts is another round’s face this batch; ⛔ the pinned objectui checkout is READ-ONLY evidence.

Concurrency at dispatch (2026-09-12T04:27Z) — sibling dispatches this batch: #17424 (packages/spec/scripts/liveness/**), #17260 (ui/component.zod.ts). Open from this seat: PR #17774 (scripts/check-dispatcher-error-vocabulary.mjs), PR #17776 (scripts/check-adr-0087-registration.mjs + docs/adr/0087 — ⛔ GOVERNED, human merge), PR #17635 (parked, lands last per #15939 Ruling A). ⇒ disjoint from all. ⭐ The round still owes its own check.

Changeset — ⛔ do NOT assume owed or not-owed. Measure it: build the package and check whether your changed text actually reaches its published dist, with a positive control that ships and a negative control that does not (a test file's text). Two rounds tonight reached opposite, correct answers this way. If owed: .changeset/16885-<slug>.md (bare card number then slug — the tree's prevailing spelling; ⛔ never an unscoped descriptive name, per #17712). If not owed: skip-changeset and say why.

Worktree — ../objectstack-issue-16885; ⛔ never edit the shared primary checkout. The branch name above is fixed (the Claim names it).

_{domain:spec execution seat · session_01MkQhmuuJAVDjmeWNixwDDH · claim posted 2026-09-12T04:27Z}

---

Generated by Claude Code

[os-bill]

os-dev-report

{
  "card": 16885,
  "pr": "https://github.com/objectstack-ai/objectstack/pull/17796",
  "branch": "claude/issue-16885-list-navigation-view-resolves-nothing",
  "head_sha": "bec4767cc78de82366224351b85042bf546b27f2",
  "files_changed": [
    "packages/spec/src/ui/view.zod.ts",
    "content/docs/references/ui/view.mdx",
    ".changeset/16885-navigation-view-declared-not-resolved.md"
  ],
  "premise_still_valid": {
    "verdict": true,
    "detail": "The card's finding reproduces at SOURCE, not only in the bundled .d.ts and minified JS it quoted. Declaration: packages/spec/src/ui/view.zod.ts, NavigationConfigSchema — `view: z.string().optional().describe('Name of the form view to use for details ...')`, sitting under a `/** Target View Config */` comment, beside closed-vocabulary `mode` and `size`. Anchor is unique: `preventNavigation` occurs exactly once in non-built tracked source, at that block.",
    "controls": [
      "Repo-local reads of navigation.view: 0 over tracked files excluding **/dist/** — LIT CONTROL: `navigation.mode` occurs 5x in the same space, so the probe can come back non-zero.",
      "Authored instances: 0 — LIT CONTROL: the scanner was proven on a synthetic `navigation: { mode, view }` fixture where it found both keys; the in-tree zero is because ListViewSchema.navigation is authored NOWHERE in-tree (all 21 object-form `navigation: {` sites are i18n translation maps).",
      "No lint rule guards it — checked the named precedent: lint-view-refs resolves app-navigation `viewName` against `listViews`, a DIFFERENT key on a DIFFERENT surface (its own docblock says so).",
      "spec CHANGELOG never mentions the key — LIT CONTROL: the sibling `size` work (#2578) is mentioned 3x."
    ]
  },
  "exit_verdict": {
    "verdict": "undetermined — the measurement does not discharge either exit, and both keep live evidence. Choosing is the seat's act: honouring `view` is new capability; retiring it narrows a published schema (Clause-2 would flip to yes).",
    "evidence_for_meant_to_name_a_form_view": [
      "The declaration does not merely hint through the key's NAME — it states the intent in a full sentence: 'Name of the form view to use for details (e.g. \"summary_view\", \"edit_form\")', under `/** Target View Config */`. That is materially stronger than triage's 'the name is strong evidence of intent'.",
      "objectui at the pinned sha promotes `view` to a first-class member of the hook's returned `NavigationOverlayState` (useNavigationOverlay.ts return block) — a slot shaped for overlay renderers to consume. It is UNREAD, which reads as unfinished rather than as residue from something removed.",
      "A maintainer comment at packages/app-shell/src/views/ObjectView.tsx:1968 describes the forwarding path explicitly: `action` may be 'view'/'page'/undefined OR a custom view name forwarded from `navigation.view` (e.g. 'detail_form')."
    ],
    "evidence_for_residue_retire_under_adr_0049": [
      "No resolution step exists at any layer, in either repo. Every `formViews` read in the pinned objectui tree is `formViews?.default` (23 sites); none is keyed by an authored view name.",
      "No lint rule, no spec-side resolver, no CHANGELOG entry — the key was declared and never announced or finished.",
      "Zero authored instances in-tree.",
      "Its one read puts it in a slot whose other producers are mode tokens, and one shipped consumer types that slot 'view' | 'edit' with no fallback arm."
    ],
    "what_is_missing_to_decide": "Origin history. Both checkouts are SHALLOW (objectstack 93 commits; objectui shallow too and fenced READ-ONLY), so `git log -S` cannot say whether a resolution step ever existed and was removed (residue) versus was never built (unfinished). That discriminator was NOT MEASURED; the CHANGELOG silence is a weaker proxy, reported as such."
  },
  "objectui_readings": {
    "pinned_sha": "53ded82bf7a494f54e344e19099dbf00854b8694 (from .objectui-sha; NOT that checkout's HEAD 3fbdd4a2). Read with `git show SHA:PATH` / `git grep SHA`; dist/ is untracked at that sha (0 tracked dist paths), so the reading is source-only and reproducible.",
    "reads_of_navigation_view": {
      "count": 1,
      "site": "packages/react/src/hooks/useNavigationOverlay.ts:245 — `const view = navigation?.view;`",
      "control": "LIT — `navigation?.mode` / `preventNavigation` / `openNewTab` light 13 sites in the same probe space."
    },
    "where_the_value_goes": "Two branches call `onNavigate(recordId, view ?? 'view')` — :287 (no navigation config) and :320 (mode === 'page'). Two other branches in the SAME function call `onNavigate(recordId, 'new_window')` (:278 modifier-click, :301 new_window/openNewTab). So the second argument is a mode/action token slot and the authored string substitutes for it. Confirmed at source, matching the card's bundle reading.",
    "hook_reexport_unread": {
      "count": 0,
      "detail": "The hook also returns `view` on NavigationOverlayState. No consumer anywhere reads that member.",
      "control": "LIT — siblings on the SAME returned object (`width`, `isOverlay`, `mode`, `selectedRecord`) are read at roughly 20 sites. This is the reading that makes the zero meaningful."
    },
    "closed_vocabulary_on_onNavigate_second_arg": {
      "answer": "YES, on one shipped consumer.",
      "site": "packages/app-shell/src/views/ObjectView.tsx:2540 — `onNavigate: (recordId: string | number, mode: 'view' | 'edit') => { if (mode === 'edit') ... else if (mode === 'view') ... }` — no else arm. An authored name matches neither branch, so the row click does nothing.",
      "bridge": "This is `objectViewSchema.onNavigate`, and every plugin wires `onNavigate: schema.onNavigate` together with `navigation: schema.navigation` into useNavigationOverlay (plugin-list/ListView.tsx:2207, plugin-grid/ObjectGrid.tsx:2020, plus kanban/gallery/gantt/map/tree/timeline/calendar — 13 call sites). So the authored string reaches the closed slot.",
      "tolerant_sibling": "packages/app-shell/src/views/ObjectView.tsx:1957 `handleNavOverlayNavigate` takes `action?: string` and treats anything non-'new_window' as 'go to the record page' — which is why the effect is invisible on some surfaces and a dead click on others, exactly as the card said."
    },
    "formViews_reads": "23 sites, all `formViews?.default` or `Object.keys(...)` in the view-item normalizer. NONE keyed by an authored view name.",
    "apparent_counter_evidence_read_at_the_site": "packages/types/src/__tests__/view-navigation-config-spec-parity.test.ts:139 asserts `site.navigation?.view === 'summary_view'`. Read at the site rather than counted: it uses `{ view: 'summary_view' }` only as a convenient MODE-LESS config to pin type parity after objectui#4588. It asserts the key is ACCEPTED, never that it RESOLVES. Not evidence of a resolution step.",
    "not_counted": "None — every objectui probe reported here had a lit control in the same tree at the same sha."
  },
  "authored_instances": {
    "count": 0,
    "detail": "ListViewSchema.navigation is authored NOWHERE in this repo — not in examples/app-crm, examples/app-showcase, fixtures, docs or platform-objects. All 21 tracked object-form `navigation: {` sites are i18n translation maps (apps.APP.navigation.ID.label), a different shape on a different schema; the rest are app-navigation ARRAYS (`navigation: [`).",
    "control": "LIT on a synthetic fixture: the same scanner found both `view:` and `mode:` inside a `navigation: { ... }` block in a scratch file (view=1 mode=1), so the in-tree zero is a reading and not a broken probe. The first run of this scan returned zero for BOTH probe and control and was correctly rejected as NOT MEASURED before the control was built.",
    "downstream": "The card records that objectstack-ai/hotcrm had exactly one occurrence and deleted it; that app is outside this checkout and was not re-measured here."
  },
  "changeset_decision": {
    "decision": "OWED — .changeset/16885-navigation-view-declared-not-resolved.md, '@objectstack/spec': patch.",
    "measurement": "@objectstack/spec files[] ships both `dist` and `src/**/*.zod.ts`. After rebuild: the corrected sentence is present in 22 built bundles and in the published source file; the ORIGINAL sentence is absent from all of them (0).",
    "positive_control": "A sibling shipped describe() — 'Disable standard navigation entirely' — lit the same dist probe at 22 files.",
    "negative_control": "A test-only `it()` title from packages/spec/src/ui — 1 hit in src/, 0 hits in dist/.",
    "trap_caught": "The first dist probe returned 0 because the search string carried a typographic apostrophe and an em dash through shell quoting. The ASCII fragment re-probe returned 22. A zero was nearly reported as a reading."
  },
  "verification": {
    "build": "pnpm --filter @objectstack/spec build under scripts/pm/os-verify-lock.sh -> VERDICT command-exit 0 (held 190s, waited 496s). Then packages/spec/scripts/build-docs.ts -> exit 0, 'Generated 222 files'. A dependency-closure build of @objectstack/client-react^... was also run (VERDICT command-exit 0) because check:skill-examples refused with PREREQUISITE NOT MET on an unbuilt client-react dist — that refusal was read as NOT MEASURED, not as a red gate, and re-run green afterwards.",
    "gates_green": "56 gate families, each read from the gate's own verdict line, exit captured before any pipe. spec-local: authorable-surface, docs, generated, liveness, api-surface, skill-refs, skill-examples, llms-txt, variant-docs, empty-state, strictness-ledger, objectui-pin-citations, export-origins, duration-unit-keys, exported-any, dual-source-exports, entry-nameability, yaml-examples, browser-reachable-entries. repo: doc-authoring, doc-anchors, docs-single-h1, docs-spec-enumerations, docs-audit-scope, docs-redirects, docs-transcript-drift, nul-bytes, quick-reference-counts, corpus-claim-drift, published-files, org-identifier, role-word, slot-lookup, watch-hint-literal, spec-parsed-alias, page-declaration-shape, pm-widening-tells, skill-identifier-liveness, published-readme-links, type-source-resolution, test-source-alias, cross-package-test-inputs, adr-0087-registration --base origin/main, changeset-no-major --base origin/main, changeset-gate-self-tests, closing-keyword-parity (+ --self-test), comment-mask-adoption, comment-mask-corpus, registry-log-declared, section-landing-index, plugin-teardown-shape, platform-object-tenancy-census, reference-carrier-shape, ci-filter-parity, doc-route-spelling --advisory, affected-docs, undeclared-dep-imports, system-context-census.",
    "tests": "pnpm --filter @objectstack/spec typecheck -> exit 0 (includes check:test-typecheck, which compiles the test layer). Targeted: pnpm --filter @objectstack/spec exec vitest run --maxWorkers=2 src/ui/view.test.ts src/ui/interaction-config-retirement.test.ts -> 2 files, 373 tests passed, exit 0.",
    "lint": "eslint . --no-inline-config over the WHOLE repo at head bec4767c -> exit 0, no output. This is NOT a declared narrowing: the repo-level scan actually ran, so no ratchet reading is deferred to CI.",
    "gate_that_caught_a_real_defect": "check:doc-authoring went RED on the first draft: it forbids an issue id inside .describe() prose, because that prose projects into content/docs/references/** and the generated skill artifacts where '#NNNN' resolves to nothing for a customer. The id was moved into the adjacent TSDoc block (which the gate does not police) and the gate went green. Maintainer ruling quoted by the gate, unmodified: 处理 issue 时犯的错应该总结成经验,保留 issue id没有意义",
    "reconciliation": "node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran RANFILE reported 70 of 100 derived families unrun BEFORE the extra batches; the batches above closed the ones this diff plausibly touches. The remainder are wide-population families CI owns (declared narrowing). The derivation's own stderr confirmed repo objectstack-ai/objectstack at 65481183b8 before it was trusted.",
    "ablation": "NOT APPLICABLE and deliberately not faked — this round adds no guard and changes no behaviour, so there is nothing whose failure could be demonstrated by mutation. A rebuild+mutation proof here would be theatre.",
    "no_card_relation_in_commits": "Scanned the one commit on this branch for the eight closing stems separately: fix/fixes/fixed/close/closes/closed/resolve/resolved all 0; 'resolves' occurs once in the prose 'no reader resolves an authored view name' and there is NO '#NNN' token anywhere in the commit messages (0 matches), so no relation can parse. The push-time hook agreed: 'check:commit-card-trailers: 1 commit message(s) on this push carry no card relation.'",
    "pr_body_readback": "Read back from the API after creation: byte-identical to the local file except the trailing newline GitHub trims. The Clause-2 line and 'Part of #16885' both survived. One short angle-bracket fragment was spelled out as SHA:PATH before sending, per the sanitizer discipline; zero angle-bracket characters remain in the body."
  },
  "mcp_calls": "0 — every GitHub read and write went through repo-scoped REST (probed first: GET /repos/objectstack-ai/objectstack/issues/16885 -> HTTP 200) plus git. No MCP GitHub tool was called.",
  "out_of_scope_findings": [
    "noted, not filed (class b) — the liveness ledger classifies `view/list/navigation` as ONE `live` row with no `children`, so its six sub-keys (mode, view, preventNavigation, openNewTab, size, width) are classified nowhere and `navigation.view` inherits `live` from its container. It is also absent from packages/spec/scripts/liveness/undrilled-containers.baseline.json, whose own `_containers` note declares it records every coordinate whose child keys are 'classified NOWHERE — not in this ledger, not in another file, nowhere' and whose `_excluded` note names only two exclusions, neither covering this one. NOT filed as a new card because it is already filed: 承接者 #17424 ('check-liveness drills exactly ONE level, so a children map at depth 2 is silently ignored'), whose stated fix explicitly includes migrating that baseline. Read #17424's body to confirm the overlap rather than assuming it. `navigation.view` is a concrete measured casualty that round can cite.",
    "noted, not filed (class b, sibling repo) — objectui at the pinned sha, packages/app-shell/src/views/ObjectView.tsx:1968, tells the next reader that a forwarded `navigation.view` name is 'resolved by RecordDetailView from its own config'. RecordDetailView does resolve from its own config, but the forwarded name never reaches it: handleNavOverlayNavigate navigates to `record/:id` carrying only `originState.from` and drops `action` entirely. True about RecordDetailView, misleading about the name. 承接者: 无 — it is a comment in the READ-ONLY pinned checkout and it belongs to whichever exit #16885 takes; filing it now would pre-commit that choice.",
    "noted, not filed (observation, not a class) — NavigationConfigSchema.width is marked '[DEPRECATED → size]' and is still read first by resolveOverlayWidth in objectui (an explicit width wins over the size bucket, because app-shell pre-resolves size into it). That is documented at both ends and behaving as documented; recorded only so the next reader of this block does not re-derive it. 承接者: 无."
  ],
  "open_questions": [],
  "status_note": "Measure-and-report delivered. The card stays OPEN: the PR says 'Part of #16885', never a closing keyword. What landed is the description correction only — no accept set, no vocabulary, no resolution step, no retirement."
}

---

Generated by Claude Code

[os-bill]

维护者速读

列表视图可以配一个 navigation.view,声明里写得很清楚:「Name of the form view to use for details(例如 summary_view、edit_form)」。作者照着写了 —— 然后什么也没发生,而且有的界面上是点一下没反应。

原因是这个值最后被塞进了另一个参数位:那个位置本来放的是导航方式(view / edit / new_window 这类词)。有一个已发布的消费方把那个参数按只有两个值的封闭表来读、而且没有兜底分支 —— 所以作者写的视图名两边都不匹配,那一行就白点了。

⚠️ 两条路都要你拍板,因为两条都在人工地板上:

• A —— 让它兑现(真的按名字去找那个表单视图)。这是新增能力:今天从 spec 到前端,没有任何一层有解析步骤。
• B —— 退役它(按 ADR-0049 立墓碑)。这是收窄已发布的 schema,要走属性退役全套。

⛔ 本席不推荐哪一条,因为证据两边都有,而且分不出来的那一半我测不了:这个键到底是「曾经能用、后来被删剩下的残渣」(⇒ 退役),还是「当初就没做完」(⇒ 兑现),要看历史才知道 —— 而两个检出都是浅克隆,git log -S 给不出答案。

请裁:A 还是 B?

---

os-decision-facets

• ① 项目长远合理性:B 让「声明即契约」重新成立 —— 一个不解析的名字不该留在已发布 schema 里;代价是删掉一个被明确写出意图的能力位。A 让声明兑现它自己写的那句话,但那是从零建一条解析链(spec 要有词表、前端要有按名取视图的一步),属于新增能力而不是修缺陷。⛔ 两者都不新增特例;区别是**「已声明但没做完」该往前做完、还是往回抹掉**。
• ② 实际业务拉动:有过真实用户。卡片是从 hotcrm 的一个真实应用测出来的,那边写了一个 navigation.view、后来把它删掉了。⚠️ 但本仓内作者化实例是 0(控制项:同类 navigation: { 的 21 处全是 i18n 翻译表,是另一种形状)。⇒ 今天没有已知的在用方,不必今晚裁;但它伤过人一次。
• ③ 防 AI 犯错:这条最偏 B,而且偏得很硬。AI 写元数据时读的就是 .describe(),而这句 describe 明确承诺了它做不到的事,还给了两个例子(summary_view、edit_form)—— 等于照着抄就一定错。⭐ 更糟的是失败不响:值被当成导航方式吞掉,不报错、不警告,有的界面还「看起来像没事」。⇒ A 也能解决(兑现了就不骗人了),但 A 要写代码才能兑现;B 一句墓碑立刻让它变响。
• ④ 创业阶段不扩散:B 是收窄(把声明拉回运行时兑现的范围),方向对、面小、可回滚;⚠️ 但它是破坏性动作,要 ADR-0087 条目 + 墓碑 + pin,且已有一个外部应用写过它。A 扩散:新增一条解析链要在两个仓里各落一半,还要定「视图名找不到时怎么办」,是更长的承诺。

推荐:⛔ 无。 分不出「残渣」还是「未完成」的那一半证据,恰恰是决定 A/B 的那一半,而它需要的是意图,不是测量。

本分析看不见什么(强制置信缺口):

1. ⛔ 历史:两个检出都浅,git log -S 说不出解析步骤是否曾经存在过。CHANGELOG 全程没提过这个键(控制项:同一区块的 size 工作被提了 3 次),这是弱代理,不是答案。
2. ⛔ 外部作者:仓外有多少应用写了 navigation.view,从这里不可知。已知一例(hotcrm)已自行删除。
3. ⛔ 我没有测 A 需要多大:按名解析一个表单视图要动哪些层、formViews 今天全是 ?.default(23 处,无一按名取)意味着要新增什么。

---

已经落地的那一半(与裁决无关)

PR #17796 只做了一件事:把那句 describe 从承诺改成如实描述(标 [EXPERIMENTAL — not enforced]),让照抄的人不再被骗。⛔ 没动接受集、没动词表、没加解析步骤、没退役。卡片保持 Part of,不关。

⚠️ 该 PR 目前落不下去 —— 撞上 #17618 的 T1 误报(第三次):diff 只改了已存在键同一行的 .describe() 文本,门禁却报「accept set 获得新拼法」。实测该键在 main 与分支上都是 2 处,不是新增。⛔ 唯一被认可的解法是把 Clause-②: no 翻成 yes,那会在永久载体上记录一次没发生的收窄 —— 拒绝。

⭐ 顺带一条被这轮测出来、已有承接者的:liveness 台账把 view/list/navigation 当一整行 live,它的六个子键(含 view)哪里都没被分类,于是 navigation.view 从容器继承了 live。这不是新缺陷,是 #17424 正在修的「只钻一层」的一个具体受害者 —— 那张卡可以直接引用。

_{domain:spec 执行席 · session_01MkQhmuuJAVDjmeWNixwDDH · 测量时间 2026-09-12T05:35Z}

---

Generated by Claude Code

[os-tesla]

Ruling recorded — B: ListViewSchema.navigation.view retires (director seat, decision batch #126 item 4, 2026-09-13)

Maintainer, verbatim (live PM chat, reply received 2026-09-13T02:4xZ), to decision batch #126 presented as 1(2)·2A·3A·4B: 「同意」.

Derived first from the long-term axis: declared equals delivered. A key whose describe promises "the form view to use for details" while no layer from spec to console resolves a view by name is a declared-not-delivered surface; zero authored instances in the repo, the one external author removed it; zero pull ⇒ remove. Should "open the detail in a chosen view" ever be pulled, it belongs to the page-assignment machinery (record pages, isDefault), not to a string on a list view.

Execution

1. packages/spec (ListViewSchema.navigation): view becomes an ADR-0049 tombstone refusing any value and naming page assignment as the route; ADR-0087 semantic migration entry (remove the key; structured TODO naming the list view).
2. PR docs(spec): navigation.view stops promising a view selection nothing performs #17796 (describe → [EXPERIMENTAL — not enforced]) is superseded by the tombstone; close it without merging or fold it into the retirement PR — the seat's call.
3. objectui at the pinned .objectui-sha: the onNavigate mode-argument read that swallowed the value is unchanged by the spec retirement (nothing reaches it any more); the contract twins gain the tombstone pin.
4. Liveness: view/list/navigation's six children are unclassified because check-liveness drills one level — check-liveness drills exactly ONE level, so a children map at depth 2 is silently ignored — no evidence resolved, no unclassified report, no warning that any of it is missing #17424's subject; this row is cited there, ⛔ not fixed here.
5. major under the window convention; Clause-②: no.

State

needs-user-decision → pm:queue; domain:spec / priority:p2 kept.

---

Generated by Claude Code