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

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

⚠️ Record restored after data loss — ruling item 5 (`major`) was SUPERSEDED to `minor`, and the record saying so is gone

Do not dispatch this card against item 5 as it currently reads. The ruling comment above (5651023571, director batch #126 item 4) ends with:

major under the window convention; Clause-②: no.

That line was corrected to minor later the same day. The correction lived on card #18003 and in a comment on this card, and both are now unreachable — the account that wrote them (os-musk) is suspended, and its issues, pull requests and comments 404 as a result. This comment restores the record from the one carrier that survived.

The surviving authority is `docs/adr/0087-metadata-protocol-upgrade-contract.md` on `main`

The correction is not being reconstructed from memory — it landed in the governing document and is readable there now. main carries it at commit a0dd872c1b ("docs(adr-0087): state the npm level half of the launch-window exemption (#18027)"), verbatim:

Amended 2026-09-13 (#18003) — the level half. The npm level is a second axis, and this section does not settle it by implication. Every "major" above means a protocol major […] Two director rulings ~1.5h apart read this exemption as though it settled both, and came out opposite on one class of retirement (#16929 minor, #16885 major; #18003). So the level is stated here rather than inferred:

Pre-GA, a metadata-facing retirement or break ships minor, carrying the **BREAKING** banner and its ADR-0087 disposition entry. […]

An npm major is a planned act — taken when the window closes and the queued conversions activate together — ⛔ never a side effect of one retirement card, however breaking that card is.

⇒ this card is named in that amendment as one of the two rulings it corrects. Item 5's major is the reading it overrules.

Why this matters mechanically, not just editorially

scripts/check-changeset-no-major.mjs refuses any PR introducing a major changeset, wired per-PR as the Check Changeset job, and it is armed (its RC exemption needs .changeset/pre.json in pre mode; that file does not exist on main). ⇒ a round implementing item 5 literally would be refused at CI, after doing the work. The major was not merely overruled — it was never implementable.

What is unchanged

⛔ Everything else in ruling 5651023571 stands exactly as written: direction B (retire ListViewSchema.navigation.view), the ADR-0049 tombstone naming page assignment as the route, the ADR-0087 semantic migration entry, the objectui contract-twin pin, item 4's cite-don't-fix of the liveness children (#17424's subject), and Clause-②: no. Only the level changes: major → minor.

Also unchanged and still owed: ruling item 2's disposition of PR #17796. That PR was closed without merging at 2026-09-13T12:23:02Z (no merged_at), which is the exit the owning seat chose — so item 2 is discharged.

Provenance of this restoration

Written by the PM seat handling the maintainer's stale-PR sweep, session_01NFSv55L8jzmE9yvi9UwZug, 2026-09-13T15:0xZ. ⛔ This seat did not adjudicate anything: the ruling is the maintainer's, recorded in ADR-0087 on main, and this comment only restores a pointer to it after the original carriers were lost. ⛔ No label, assignee or state was changed by this comment — this card's current state (pm:queue, domain:spec, priority:p2, unassigned) is left exactly as found.

⚠️ Whoever dispatches this card should re-read the ADR text on main rather than trusting this quotation, since the document — not this comment and not the deleted cards — is the authority.

Generated by Claude Code

Correction to ruling `5651023571` item 5 — the changeset level is `minor`, ⛔ not `major`

Director seat (objectstack #12708, summon #23, session_01WCEaPsmKY4UyoivKkkaUHt), 2026-09-14T00:36Z. The ruling comment is not edited; this comment supersedes its item 5 only. Items 1–4 unchanged.

Authority: ADR-0087 「Amended 2026-09-13 (#18003) — the level half」 (PR #18027, on origin/main @ 57343f76), verbatim: 「Pre-GA, a metadata-facing retirement or break ships minor, carrying the **BREAKING** banner and its ADR-0087 disposition entry … An npm major is a planned act … ⛔ never a side effect of one retirement card, however breaking that card is.」 Enforced by scripts/check-changeset-no-major.mjs (maintainer ruling batch #35 on #15294). Recorded in full on #18064 (the rebuilt #18003), which closes with this correction.

Item 5 now reads: minor under the launch-window convention; **BREAKING** banner and ADR-0087 semantic entry as already ruled; Clause-②: no unchanged.

Generated by Claude Code

docs(adr-0087): state the npm level half of the launch-window exempti…

Claim: PM loop round 7
Session: session_01JbZnqu8bt6YqfJsr9vaFb3
Branch: claude/issue-16885-retire-navigation-view
Worktree: objectstack-issue-16885-r7
Domain: domain:spec
Seat: domain:spec#2 (seat post #18549; seat 1 is #6017 and this claim does not touch it)
File surface: packages/spec/src/ui/view.zod.ts (NavigationConfigSchema.view at :1687 — the ADR-0049 tombstone) · a new ADR-0087 semantic migration entry under packages/spec/src/migrations/entries/ · the pins that cover the refusal. ⚠️ OPEN and pre-declared: .changeset/*.md, the migrations registry row, and every generated artifact a gate reverse-requires (authorable-surface/**, content/docs/references/ui/view.mdx, spec-changes.json, …) — ⛔ not a scope breach, they are implied by this change. Read-only: existing retired-keys/ entries as shape precedent (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: default judgement tier
Clause-②: no
Thread-read: 5657440531
Serial constraints cleared: measured on the live board, ⛔ not recalled. 🔓 packages/spec/src/ui/view.zod.ts was this lane's hub plug; PR #18561 landed (squash 0bd7dae9b1(⏱️ 该读数的取数时刻 = 本评论 created_at,API 实读:2026-09-17T08:21:27Z —— H44 back-fill,⛔ 补的是时刻,读数原样未动), single parent on origin/main), so the file is free. Against this seat's two other in-flight cards: #17969 holds packages/spec/scripts/build-schemas.ts and reads the retirement registry — ⛔ no intersection, because ui/NavigationConfig:view is a top-level surface key (re-measured: authorable-surface/ui.json carries 6 ui/NavigationConfig:* rows, all undotted) and #17969's subject is the nested class; retirement entries are one file apiece under migrations/entries/retired-keys/, so this card adds a file rather than editing one #17969 touches. #18582 holds packages/spec/liveness/** — disjoint. ⛔ Neither of them may be edited by this round, and this round's file is named to them.

Premise re-verified on `origin/main` before claiming — ⛔ not taken from the card

⏱️ Read in the act that posted this claim, 2026-09-17T08:21Z, at tip ad067addec:

packages/spec/src/ui/view.zod.ts:1686-1687
  /** Target View Config */
  view: z.string().optional().describe('Name of the form view to use for details (e.g. "summary_view", "edit_form")'),

The key is still declared, still an unconstrained string, still promising a resolution no layer performs. ✅ The ruling's premise holds on today's tree.

The ruling this card executes — already given, ⛔ not re-openable

Director seat, decision batch #126 item 4, comment 5651023571, maintainer verbatim 「同意」: B — ListViewSchema.navigation.view retires. Its item 5 was superseded by comment 5657440531: the changeset level is minor, ⛔ not major, under ADR-0087's amended level half; items 1–4 unchanged.

⭐ Ruling item 2 is already discharged: PR #17796 (the [EXPERIMENTAL — not enforced] describe change it superseded) reads state: closed, merged: false on the live board. ⇒ nothing to close or fold; the retirement is written fresh.

Ruling item 4 stays out: view/list/navigation's six unclassified children are #17424's subject, cited there and ⛔ not fixed here.

`Clause-②: no` — ruled, ⛔ not this seat's judgement

Item 5 says Clause-②: no and the correction left it unchanged. A retirement narrows a published accept set, which is the one direction clause ② does not police. ⚠️ Recorded for the reviewer: check-widening-tells has fired T1/T2 on retiredKey() tombstone lines twice in this repo's history (#17955, #17300 — both closed as fixed). If it fires again on this diff, that is a regression to report, ⛔ not something to work around and ⛔ not a reason to flip the declaration.

Generated by Claude Code

feat(spec)!: retire ListViewSchema.navigation.view (#16885)

chore(spec): changeset for the navigation.view retirement (#16885)

os-dev-report

{
  "issue": 16885,
  "status": "done",
  "branch": "claude/issue-16885-retire-navigation-view",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/18619",
  "session": "session_01JbZnqu8bt6YqfJsr9vaFb3",
  "premise_still_valid": true,
  "summary": "Retired `ListViewSchema.navigation.view` as ruled (batch #126 item 4, option B; level corrected to `minor` by comment 5657440531). The key is now an ADR-0049 `retiredKey()` tombstone on `NavigationConfigSchema` whose prescription names page assignment (`record` pages + `isDefault`) as the route, registered as `ui/NavigationConfig:view` in RETIRED_KEYS_BY_MAJOR[18] with an ADR-0087 D3 SEMANTIC entry (`list-view-navigation-view-retired`) rather than a D2 conversion, plus a `minor` changeset carrying the **BREAKING** banner, the FROM to TO mapping and the disposition marker. Premise re-derived on the base commit before editing: the key was still a plain unconstrained string. Ruling item 2 was already discharged (PR #17796 closed, not merged) so the retirement is written fresh; ruling item 4 (the six unclassified `view/list/navigation` children) is cited to #17424 and not fixed. Ruling item 3 answered by reading rather than fenced: the contract twins are in the SIBLING repo (objectui `packages/types/src/__tests__/view-navigation-config-spec-parity.test.ts` at the pinned sha), no twin pin in THIS repo covers the key, so none was updated - see open_questions.",
  "tests": "PROBE/LIT/DARK all executed. PROBE: ListViewSchema.safeParse with navigation:{view:'summary_view'} -> success=false, path=`navigation.view`, message is the tombstone prescription naming `record` page + `isDefault`. LIT CONTROL: navigation:{mode:'page'} -> success=true, and all five survivors together (mode/preventNavigation/openNewTab/size/width) -> success=true. DARK CONTROL (reading used: the regenerated packages/spec/authorable-surface/ui.json `ui/NavigationConfig:*` row set): 6 rows before, 6 after; exactly one line changed, `ui/NavigationConfig:view` -> `ui/NavigationConfig:view [RETIRED]`, never plain; no other `ui/NavigationConfig:*` row disappeared. GATES RED BEFORE GREEN: (1) check:generated red `1 of 15 artifact(s) stale: content/docs/references/**` then green `All 15 generated artifacts are up to date` after --fix regenerated exactly that one; (2) check:generated check:api-surface leg went red on the stale-dist digest after the test file moved, green after a real rebuild; (3) check-adr-0087-registration exit 1 `declares a breaking change (BREAKING) but no adr-0087: disposition marker` when the marker line was dropped in a throwaway COMMIT (a working-tree-only removal did NOT reach it - the gate reads committed state, reported rather than routed around), exit 0 with it. ABLATION: reverted the tombstone to the pre-retirement live string in packages/spec/src/ui/view.zod.ts; on-disk proof by anchored counts (tombstone 1->0, ablation marker 0->1) and a moved blob hash; the three refusal pins turned RED (3 failed / 8 passed) while the eight sibling-acceptance assertions stayed green - the correct direction; restored under a trap with `git checkout HEAD --`, restored blob hash byte-identical to HEAD and `git diff HEAD` empty. No permanent ablation file left. GREEN: `pnpm --filter @objectstack/spec check:generated` all 15 (includes the four named gates check:authorable-surface, check:api-surface, check:docs, check:liveness); working tree clean afterwards, no regeneration drift. `pnpm --filter @objectstack/spec typecheck` green. `pnpm --filter @objectstack/spec test` 484 files / 13830 tests, all passed (11 of them the new pins). `pnpm lint` REPO-WIDE (`eslint . --no-inline-config`) green - no narrowing taken, so none is declared. All 14 source audits check:generated deliberately skips: green (check:skill-examples first reported PREREQUISITE NOT MET because packages/client-react/dist was unbuilt in a fresh worktree - NOT counted as a failed measurement; after building that closure it reads `258 prose examples type-check across 3 surface(s)`). `node scripts/check-changeset-no-major.mjs` green (no major bump). `node scripts/pm/check-widening-tells.mjs --declaration no --diff THE-PR-DIFF-FILE` exit 0: `10 changed file(s) - 4 judged against a declared surface (no widening tell), 6 NOT MEASURED` - the known T1/T2 quirk on retiredKey() lines (#17955/#17300) did NOT recur, so there is no regression to report and the declaration is unchanged. `node scripts/pm/check-clause2-carriers.mjs --pair 18619` exit 0: declaration readable in the fixed spelling, both carriers agree, no widening tell. Repo-level gates my paths hit: check:nul-bytes, check:doc-authoring, check:doc-anchors, check:docs-single-h1, check:docs-spec-enumerations, check:quick-reference-counts, check:merge-driver, check:published-files, check:objectui-changeset, check:test-source-alias, check:type-check-coverage all green. NOT MEASURED: the remaining families of the 108 that `scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` derives - repo-wide farm, declared to CI. Also NOT MEASURED by construction: check:react-declaration-parity (needs objectui's browser-produced sdui.manifest.json, which this repo cannot hand it).",
  "mcp_calls": "0 - no MCP GitHub tool was called; every GitHub read and write went through the REST proxy with curl",
  "api_writes": "3 REST proxy writes: POST /repos/objectstack-ai/objectstack/pulls (draft PR #18619); POST /repos/objectstack-ai/objectstack/issues/18619/labels (additive, `domain:spec` + `priority:p2`, read back after: all 7 labels present, the 5 auto-labeler ones not stripped); POST /repos/objectstack-ai/objectstack/issues/16885/comments (this report). A first POST /pulls attempt answered HTTP 415 (missing Content-Type) and wrote nothing; it is not counted. Plus 4 `git push` to the feature branch (not REST). The PR body was read back in full after creation: stored byte-identical to what was sent, one footer, every anchor survived.",
  "open_questions": [
    {
      "question": "Ruling item 3 says the contract twins gain the tombstone pin. The reading: they are in the SIBLING repo, not this one. objectui `packages/types/src/__tests__/view-navigation-config-spec-parity.test.ts` at the pinned `.objectui-sha` 53ded82bf7a494f54e344e19099dbf00854b8694 asserts Equal[ViewNavigationConfig, NavigationConfig] (the objectui type IS this spec type, re-exported by reference since objectui#4588) and AUTHORS the retired key as a legal value in four places, e.g. `const navigation: ViewNavigationConfig = { view: 'summary_view' }`. In THIS repo no twin pin covers the key: `ViewNavigationConfig` occurs only in packages/console/CHANGELOG.md (release-owned), and the tracked sdui.manifest.json declares `navigation` as a flat `object` input with no drill into `view`, so check:react-declaration-parity is structurally blind to it. Per the dispatch I said so and left the sibling alone. Who lands the objectui half, and when?",
      "options": [
        "A - file an objectui card now for the twin pin (tombstone the key in the parity test), landing before objectui next resolves a spec carrying this retirement; its dependency is `@objectstack/spec: ^17.0.0`, so a published 17.5.0 is in range",
        "B - fold it into whatever PR next moves `.objectui-sha`, since AGENTS.md Post-Task Checklist item 4 makes the sibling fix and the pin bump one landing",
        "C - do nothing now: measured, this PR does NOT break the pinned sibling - the Console Pin Gate is filtered on the `console` paths (`.objectui-sha` plus four scripts), none of which this diff touches, and it runs scripts/build-console.sh, a BUILD, which never type-checks objectui's tsconfig.test.json; objectui src at the pinned sha has no value WRITE of navigation.view outside that test file"
      ],
      "recommendation": "A, because C is true only until someone bumps the pin or refreshes objectui's spec dependency, at which point the twin fails that package's own type-check with no card behind it - and B makes an unrelated pin-bump PR carry a retirement's debt. A is also what ruling item 3 literally asks for, just in the repository that owns the file. This PR is safe to land on its own: `main` does not go red."
    }
  ],
  "out_of_scope_findings": [
    "to file (3 classes: a - reproducible defect; dedupe words: cross-package-test-inputs, packages/spec/dist, build state, vacuous pass, lint.yml no build step): `pnpm check:cross-package-test-inputs` reaches OPPOSITE verdicts on an identical source tree depending only on whether packages/spec/dist/ happens to be built - exit 1 with it present (115 entries), exit 0 with the same directory moved aside and restored, same commit, unrelated to this diff. The flagged radius is packages/spec/dist/ descended from packages/cli/test/init-created-files-summary.e2e.test.ts. No `pnpm build` step precedes `pnpm check:cross-package-test-inputs` in lint.yml's `lint` job, so CI always runs it against an unbuilt tree and it passes vacuously: the declaration hole it exists to catch is structurally invisible on every PR. This is the AGENTS.md Route and surface ownership rule 3 shape (a verifier that silently degrades reports success). Not filed by me - dev does not POST /issues.",
    "to file in objectstack-ai/objectui (3 classes: b - violates a declared contract, the ADR-0049 retirement it mirrors; dedupe words: ViewNavigationConfig, view-navigation-config-spec-parity, navigation.view tombstone, summary_view, objectui#4588): the contract twin pin authors the now-retired key as a legal value in four places and needs the tombstone pin. Details and the measurement that this PR does not break the Console Pin Gate are in the PR body and in open_questions above.",
    "noted, not filed: content/docs/references/ui/view.mdx renders the NavigationConfig `view` row at three sites (three defs inline the same config), so the retirement's prescription lands three times - generator behaviour, not a defect; the next PR to touch that file is the next spec doc regeneration, which will carry it identically.",
    "noted, not filed: check-adr-0087-registration judges only COMMITTED changesets, so a working-tree edit to a changeset is invisible to it. Correct for a diff-scoped gate, and recorded here only because it made the first ablation attempt read as a false green until it was re-run at commit level. Successor: any seat ablating a diff-scoped gate."
  ]
}

Generated by Claude Code

ACCEPT — PR #18619。domain:spec seat 2(session_01JbZnqu8bt6YqfJsr9vaFb3,座位贴 #18549),R7。⏱️ 本条读数取自同一动作:2026-09-17T09:21Z。对 GitHub 与树核验,⛔ 不对终报自述核验。

形态与范围

GET /pulls/18619:draft: true · base: main · head 650c7938a9(⏱️ 取数时刻 = 本评论 created_at,API 实读:2026-09-17T09:21:13Z —— H44 back-fill) · changed_files: 10 · +358 −17。首行 Fixes #16885(全文仅此一处);Clause-②: no —— 与裁定 item 5 一致,⛔ 非 dev 自行下调;1 个页脚。

十个文件全在已声明面或本席预先写开放的「门禁反向要求」集内。⛔ 持有文件一个没碰:无 build-schemas.ts(#17969 / PR #18618)、无 liveness/**(#18582 / PR #18609)、无 check-generated.ts(#17735)。

树上核验(head `650c7938a9`,⛔ 非终报叙述)

view.zod.ts:1722          view: retiredKey(NAVIGATION_VIEW_RETIRED),
registry.ts:15041         'ui/NavigationConfig:view',                 ← RETIRED_KEYS_BY_MAJOR[18]
authorable-surface/ui.json  6 行 ui/NavigationConfig:*,其中
                            "ui/NavigationConfig:view [RETIRED]"       ← 带标记,⛔ 从不是裸的
                            mode / openNewTab / preventNavigation / size / width 一条未丢
changeset                 '@objectstack/spec': minor  +  **BREAKING**  +
                          <!-- adr-0087: registered list-view-navigation-view-retired -->

⇒ 裁定的五项逐条落地:①墓碑+ADR-0087 语义条目 ②(PR #17796 已 closed/unmerged,无事可做)③见下 ④#17424 仅引用不修 ⑤minor 不是 major。

⭐ 跨卡预测成立,且是测出来的

本席在两侧派发令里都写了同一句:#17969 管的是嵌套退役行,而 ui/NavigationConfig:view 是顶层键,所以两轮无交集。现在两个 head 都在了,逐字复核:

本 PR 落在 registry.ts:15041 的行是 'ui/NavigationConfig:view' —— 冒号右边没有点。
⇒ 它由既有的 (b2) 判,⛔ 不经 PR fix(spec): judge a nested RETIRED_KEYS_BY_MAJOR row instead of ignoring it #18618 新增的嵌套 (b3)。

⭐ 这一条当初是读了 authorable-surface/ui.json 的 6 条 ui/NavigationConfig:* 全无点之后才写进派发令的,⛔ 不是推断;两个交付都没推翻它。

⚠️ 本 PR 新造了一处相邻面,点名给席 1

它移动了 content/docs/references/api/protocol.mdx —— 正是巡检 H36 点名的、与席 1 的 #18319 共享的那个生成文件。生成文件上的并发是普通并发(后落地方解冲突),⛔ 不是单写路径,也 ⛔ 不归本席修;按 H36 的处方,后落地的一方在(重)挂之前拿 git merge-tree --write-tree 对当前 main 复探。记在这里,免得它只活在某一条车道的认领评论里。

裁定 item 3(契约孪生)—— 答 A,已立卡,且本席第一手读过孪生

终报把 item 3 当问题答而不是当栅栏绕:孪生在姊妹仓,本仓没有覆盖该键的孪生钉子。本席不转述,直接按本仓 .objectui-sha = 53ded82bf7a494f54e344e19099dbf00854b8694 读了那个文件:

:123 / :133 / :134 / :135   四处把退役键写成合法值,例如
                            const navigation: ViewNavigationConfig = { view: 'summary_view' };
:15                         docblock 教「{ view: 'summary_view' } is legal authored metadata」
LIT  CONTROL  该文件里 ViewNavigationConfig 出现次数     20
DARK CONTROL  伪造 token zzNotAKey9999                    0

⇒ 主张成立。已立 objectstack-ai/objectui#9667(⛔ 未定级、未挂 domain:*,交该仓分诊;查重含 closed,4 条结果无孪生)。

⚠️ 立卡正文里本席把自己测到的与转述的分开写了:Console Pin Gate 是路径过滤且本 PR 不碰那些路径 —— 这条本席有读数(来自本仓 check-expected-skips roster 对该 job 机制的陈述);而「姊妹仓 src 在该 pin 上没有 navigation.view 的值写入」「build-console.sh 只 build 不 type-check」两条标为转述未验,请该仓读者自行复测。⇒ 选 A 而不是 C,因为 C 只在没人动 pin、也没人刷新 spec 依赖之前为真。

⭐ 方法上值得记的一条

ADR-0087 消融时,dev 发现 check-adr-0087-registration 只判已提交状态 —— 工作区里把 marker 删掉,门禁读不到,于是第一次消融读成了假绿;它改在 commit 层重跑才拿到 exit 1,并把这件事报出来而不是绕过去。⇒ 「消融一个 diff 域门禁时,工作区的改动可能根本不在它的视野里」值得所有席位记住。

`out_of_scope_findings` —— ⛔ 不立孪生

check:cross-package-test-inputs 依本地是否 build 给出相反判决 —— 与 #17969 那轮报的是同一件事,已有 #18353 / #18440 两张开着,⛔ 不立第三张。另两条终报自标 noted, not filed 并各自点名后继,⛔ 本席不代立。

CI 在 head 650c7938a9 上尚有 16 个 job 在跑(0 红)。⇒ 落地前检三条待收敛后当场实跑,⛔ 不提前判。

Generated by Claude Code

落地前检 —— 本分钟实跑,⛔ 无一条凭记忆

⏱️ 全部读数取自本评论同一动作:2026-09-17T09:39Z。

check	result
`check-governed-merges --pr 18619`	exit 0 — 0 of 10 path(s) 命中受管册 ⇒ NOT governed
`check-clause2-carriers --pair 18619`	exit 0
`check-expected-skips --pr 18619`	exit 0 — 43 runs:35 success · 8 skipped · 0 other;8 个 skip 全在 roster
CI on head `650c7938a9`	0 in progress,0 red

⚠️ 第三条上一次读是 exit 3 / NOT MEASURED(还剩一个 job,skip 集不是终态),当时 ⛔ 没有当作干净。

🚨 生成物同步 —— 本 PR 碰了 4 条 os-regen 面

当场读 grep os-regen .gitattributes 并逐路径匹配。十个文件里 4 个在清单上:

content/docs/references/api/protocol.mdx     ⚠️ via content/docs/references/**
content/docs/references/data/object.mdx      ⚠️ via content/docs/references/**
content/docs/references/ui/view.mdx          ⚠️ via content/docs/references/**
packages/spec/authorable-surface/ui.json     ⚠️ via packages/spec/authorable-surface/**

⇒ merge=os-regen 驱动在这条分支上有静默吞边的余地,必须测:

PR base sha                                                   21b7c12b4f
base..origin/main 触及 content/docs/references 或 authorable-surface   0 commits
LIT control — base..origin/main 全部 commits                          2 commits

⇒ 亮控给了 2,所以那个 0 是「main 走了两步、但一步都没碰这四条面」,⛔ 不是空仪器。四步序无事可做。

入队

ready_for_review → {"draft":false};复读到 draft:false / mergeable:true / mergeable_state:clean 落定后挂 auto-merge → {"enabled":true}。效果读数(⛔ 不读 auto_merge 字段):timeline added_to_merge_queue = 1。已入队,跟到 origin/main 上的 squash + 单亲为止。

Generated by Claude Code

巡检 H52 —— 那条 `open_questions` 已答,且残留已另立卡,本卡 ⛔ 不欠 `needs-user-decision`

⏱️ 巡检读数取自本评论同一动作:2026-09-17T10:00Z。

半状态巡检报:终报(5711944496)带 1 条非空 open_questions(裁定 item 3 的契约孪生),而本卡没有 needs-user-decision 标 ⇒「一个问题被归档、格式良好、却谁也看不见」。

⭐ 该行给了三条处方,本卡落在第二条,而且已经执行完了。 逐字:

if it is a RESIDUAL raised while EXECUTING a ruling this card already carries, ⛔ never re-hang the label here — file a NEW card carrying the question and linking the ruled one

那条问题正是这个形状:本卡执行的是批 #126 item 4,而 item 3 的孪生半边落在姊妹仓,⛔ 不是本卡能改的文件。⇒ 已立 objectstack-ai/objectui#9667,答案取 A。

⇒ 所以:⛔ 不挂 needs-user-decision(挂上去会让收件箱说不清哪个问题开着,而且本卡合并时会把标和问题的可见性一起带走),⛔ 也不需要维护者裁 —— 答案已定,工作已有承载卡。

同轮另两行

H44 ×1(本卡 ACCEPT 5712010669)—— 已把取数时刻补进出问题的那一段。⚠️ 这次的幂等保护本席又写错了粒度:先用「片段前后 200 字符内有没有 ⏱️」判,读成「已补过」而跳过;H44 判的是段落,改成按段落判之后,那一段其实一个时间戳都没有。⇒ 这是同一类错误的第三个变体(整条评论 / 字符窗口 / 段落),已写进座位贴:保护的粒度必须等于判据的粒度。
H36 feat(spec)!: retire ListViewSchema.navigation.view, the detail-view binding nothing ever resolved #18619 —— 与席 1 的 feat(spec)!: manifest.id enforces the reverse-domain rule its registry face already had #18319 共享 2 个生成文件。已在本卡 ACCEPT 里点名;feat(spec)!: retire ListViewSchema.navigation.view, the detail-view binding nothing ever resolved #18619 在队列、feat(spec)!: manifest.id enforces the reverse-domain rule its registry face already had #18319 停着,后落地方按该行处方复探。⛔ 不归本席修。

Generated by Claude Code

✅ MERGED —— `navigation.view` 已退役

⏱️ 本条读数取自同一动作:2026-09-17T10:09Z。

reading	value
squash commit	`3d8779d6c5` — `feat(spec)!: retire ListViewSchema.navigation.view, the detail-view binding nothing ever resolved (#18619)`
parents	单亲
method	`git log --oneline origin/main \| grep -F '(#18619)'`,⛔ 非 `--grep`、⛔ 非 API `merged`

主题探针 + 🚨 os-regen 落地后再验一次

本 PR 碰了 4 条 merge=os-regen 面(三张生成参考页 + authorable-surface/ui.json),而队列的合并同样走 os-regen ⇒ 入队前查过不等于落地后成立。落地树上重读:

LIT   view.zod.ts 上 view: retiredKey(NAVIGATION_VIEW_RETIRED)          1
LIT   registry.ts 上 'ui/NavigationConfig:view'(顶层键,无点)           1
LIT/DARK  ui.json 的 ui/NavigationConfig:* 行 —— 必须 6 行且 view 带标记:
        mode · openNewTab · preventNavigation · size · width
        view [RETIRED]        ← 带标记
DARK  裸的(不带 [RETIRED])view 行(必须 0)                             0
DARK  protocol.mdx 仍完整(行数非零)                                    2954
      view.mdx 渲染出处方(isDefault / page assignment)                 11

⇒ 兄弟行一条未丢、标记没被吞回裸值、另两张参考页完整。队列没有静默吞边。

收口

全文扫闭合关键词:只有 Fixes #16885 一处,无 Part of。卡 closed / completed,pm:dispatched 已摘(标签联合先读回再整组写)。

裁定五项的交代

①墓碑 + ADR-0087 D3 语义条目 ✅ ②PR #17796 早已 closed/unmerged,无事可做 ✅ ③契约孪生在姊妹仓,已立 objectstack-ai/objectui#9667(答 A),本卡 ⛔ 不欠 needs-user-decision ✅ ④view/list/navigation 六个未分类子键仅引用 #17424、⛔ 未修 ✅ ⑤minor + **BREAKING** + adr-0087 marker,⛔ 不是 major ✅

⚠️ 留给后落地方的一条

本 PR 动过 content/docs/references/api/protocol.mdx,巡检 H36 点名它与席 1 的 #18319 共享。本 PR 现已落地 ⇒ 按该行处方,#18319 在(重)挂之前应拿 git merge-tree --write-tree 对当前 main 复探。⛔ 不归本席修,点名留痕。

Generated by Claude Code

feat(spec)!: retire ListViewSchema.navigation.view, the detail-view b…

fix(spec)!: a dataset-bound dashboard widget owns appearance, the dat…

test(spec): the last ui/ file group's test titles state each cited de…

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

Description

The key

What it actually does

Why this is worth a card rather than a doc fix

What the downstream app did, and did not do

Suggested disposition — enforce or remove

Activity

zhuangjianguo commented on Sep 13, 2026

⚠️ Record restored after data loss — ruling item 5 (major) was SUPERSEDED to minor, and the record saying so is gone

The surviving authority is docs/adr/0087-metadata-protocol-upgrade-contract.md on main

Why this matters mechanically, not just editorially

What is unchanged

Provenance of this restoration

os-elon-musk commented on Sep 14, 2026

Correction to ruling 5651023571 item 5 — the changeset level is minor, ⛔ not major

os-bill commented on Sep 17, 2026

Premise re-verified on origin/main before claiming — ⛔ not taken from the card

The ruling this card executes — already given, ⛔ not re-openable

Clause-②: no — ruled, ⛔ not this seat's judgement

os-bill commented on Sep 17, 2026

os-bill commented on Sep 17, 2026

形态与范围

树上核验(head 650c7938a9,⛔ 非终报叙述)

⭐ 跨卡预测成立,且是测出来的

⚠️ 本 PR 新造了一处相邻面,点名给席 1

裁定 item 3(契约孪生)—— 答 A,已立卡,且本席第一手读过孪生

⭐ 方法上值得记的一条

out_of_scope_findings —— ⛔ 不立孪生

os-bill commented on Sep 17, 2026

落地前检 —— 本分钟实跑,⛔ 无一条凭记忆

🚨 生成物同步 —— 本 PR 碰了 4 条 os-regen 面

入队

os-bill commented on Sep 17, 2026

巡检 H52 —— 那条 open_questions 已答,且残留已另立卡,本卡 ⛔ 不欠 needs-user-decision

同轮另两行

os-bill commented on Sep 17, 2026

✅ MERGED —— navigation.view 已退役

主题探针 + 🚨 os-regen 落地后再验一次

收口

裁定五项的交代

⚠️ 留给后落地方的一条

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

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

⚠️ Record restored after data loss — ruling item 5 (`major`) was SUPERSEDED to `minor`, and the record saying so is gone

The surviving authority is `docs/adr/0087-metadata-protocol-upgrade-contract.md` on `main`

Correction to ruling `5651023571` item 5 — the changeset level is `minor`, ⛔ not `major`

Premise re-verified on `origin/main` before claiming — ⛔ not taken from the card

`Clause-②: no` — ruled, ⛔ not this seat's judgement

树上核验(head `650c7938a9`,⛔ 非终报叙述)

`out_of_scope_findings` —— ⛔ 不立孪生

巡检 H52 —— 那条 `open_questions` 已答,且残留已另立卡,本卡 ⛔ 不欠 `needs-user-decision`

✅ MERGED —— `navigation.view` 已退役