Decision: `ObjectViewSchema`'s ten unmirrored declared keys are LOCAL (objectui#7279 re-derivation) — mirror them, retire them, or defer to #2231?

[os-justin]

Filed by the domain:spec @ objectui execution seat (session session_01BAZFhALsQsGqxui8sNqM8s) as the follow-up triage 5548347502 on #7279 reserved for the manual floor: "若重推导后发现 ObjectViewSchema 的 key 该走 LOCAL 且数量可观、构成加宽 mirror 的可授权面，那是 manual floor 的事，届时另起". The re-derivation landed with PR #7776 (test-file routing record; no mirror moved). This card asks for the remedy decision; ⛔ nothing is dispatched until it is answered. domain:* and grading are triage's.

What was measured (PR #7776, on origin/main 16a725f9)

objectql.zod.ts:196 ObjectViewSchema = BaseSchema.extend({…}) is a hand-written mirror of local literals and z.lazy siblings; it references no spec schema and is not in SPEC_DERIVED_PAIRS. Ten keys the TypeScript interface declares are absent from the mirror (UnmirroredDeclared ledger entry), so a document authoring any of them passes the validator unexamined through BaseSchema's passthrough while the published type invites the author to write it — the declared ≠ enforced shape. Read through the installed @objectstack/spec@17.2.0 (ui entry, all 122 exported object schemas walked, control keys hit):

keys	spec models it	shape
navigation	yes — ListViewSchema.navigation / ObjectListViewSchema.navigation	optional NavigationConfigSchema; the declaration already imports that very type
searchableFields, filterableFields	yes — ListViewSchema / ObjectListViewSchema	optional array of string (the spec calls filterableFields a legacy shorthand for userFilters.fields)
listViews	by name — ViewSchema.listViews	record of spec list views; ⚠️ the declaration's value is the local NamedListView, so the value type is a unification question
allowCreateView, defaultListView, defaultViewType, showViewSwitcher, viewActions, viewTabBar	no	plain hand-written omissions — no spec slot anywhere

Read sites for the six were NOT measured by #7279 (out of its scope); that measurement is the first step of option B below.

Options

• A — mirror all ten now: four by reference to the spec slot that models them, six as local literals matching the declaration. One PR, @object-ui/types: minor (accept set narrows for wrong-typed values, widens nothing the type does not already promise). Cost: any of the six that nothing reads becomes an enforced-but-dead key — the [Decision] hideEmpty on record:details sections: the spec REFUSES the key, @object-ui/types declares it, the zod mirror omits it, and the renderer honours it — plus hideEmpty: false is not an override #7129 / finding(types): DashboardComponentSchema.title is declared-but-unread once the #7509 retirement lands #7623 precedent says such a key is retired, not mirrored.
• B — liveness first, then mirror-or-retire per key (recommended): mirror the four by spec reference (with the listViews value type decided, not papered over with z.any()); for each of the six, measure the renderer / app-shell reads — mirror where a read exists, retire (?: never + retirementTombstone(), the [Decision] hideEmpty on record:details sections: the spec REFUSES the key, @object-ui/types declares it, the zod mirror omits it, and the renderer honours it — plus hideEmpty: false is not an override #7129 route) where nothing reads it. One or two PRs, minor, "Breaking for authored metadata" where a key is retired.
• C — defer all ten to Unify hand-written @object-ui/types zod with @objectstack/spec/ui (ListViewSchema drift) #2231 (spec unification): wrong on the evidence — the pair is not spec-derived, so Unify hand-written @object-ui/types zod with @objectstack/spec/ui (ListViewSchema drift) #2231 has nothing to unify here; the keys would stay declared-unenforced indefinitely.

决策四维分析

• 实际业务需求：这十个键是 ObjectView 节点上已发布的 TS 声明面；四个键规范已建模（navigation / searchableFields / filterableFields / listViews），是真实存在的视图配置；另外六个是 objectui 本地的 UI 旋钮，谁在读尚未实测——B 把实测放在动手之前，A 假设它们都活着，C 假设它们都不归本仓管。
• 项目长远合理性：contract-first。四个键按规范引用镜像不会漂移；六个本地键若无读者就按 [Decision] hideEmpty on record:details sections: the spec REFUSES the key, @object-ui/types declares it, the zod mirror omits it, and the renderer honours it — plus hideEmpty: false is not an override #7129 路线退役，避免把死键固化成契约（A 的长期代价）。C 把不属于 Unify hand-written @object-ui/types zod with @objectstack/spec/ui (ListViewSchema drift) #2231 的问题挂到 Unify hand-written @object-ui/types zod with @objectstack/spec/ui (ListViewSchema drift) #2231 上，永远等不到解锁。
• 防 AI 写元数据犯错：今天这十个键"声明即邀请、校验器却不认"，AI 写了就静默通过——正是 declared ≠ enforced 的温床。任何选项都比现状好；B 让每个幸存键都被校验、每个死键被响亮拒绝，A 让死键"通过校验但无效果"。
• 创业阶段不扩散需求：不新增能力；implementation-first，读者为零的声明面退役而不是补镜像；B 的实测成本是每键一次 grep，远小于固化死键的维护成本。

Seat recommendation: B. The dev of PR #7776 reached the same recommendation independently (report 5553436702, open_questions).

Refs: #7279 (the re-derivation, PR #7776) · #6152 (the 121-key worklist this entry belongs to; pm:blocked, domain:devx) · #6058 / PR #6149 (the ledger) · #6705 / PR #7277 (the scanner fix) · #7129 / #7623 (the retire-by-deleting-the-declaration route) · #2231 (spec unification — not this entry's route).

[os-justin]

Maintainer ruling recorded — option B: liveness first, then mirror-or-retire per key. needs-user-decision → pm:dispatched (one stroke), dispatched this round.

Recorded by the domain:spec @ objectui execution seat, session session_01BAZFhALsQsGqxui8sNqM8s, 2026-09-06T02:32Z. Provenance (who / verbatim / where): the maintainer (os-justin), live PM chat with this session, replying to decision batch 2 of 2026-09-05T23:1xZ, in which this card was item 7 — tabled with the seat's recommendation B and the four-facet analysis in Chinese (the dev of PR #7776 reached B independently, report 5553436702). Verbatim reply: 「第二批(4 项,契约形状族) 帮我处理，全部同意」.

Ruled shape. The ten keys ObjectViewSchema's TypeScript face declares and its hand-written mirror does not are closed in two halves, not one:

• The four the spec models — navigation, searchableFields, filterableFields, listViews — are mirrored by reference to the spec slot that models them, not restated as local literals. ⚠️ listViews's value type is the open question inside this half: the declaration's value is the local NamedListView while the spec's ViewSchema.listViews is a record of spec list views. It is decided and stated, ⛔ never papered over with z.any().
• The six with no spec slot — allowCreateView, defaultListView, defaultViewType, showViewSwitcher, viewActions, viewTabBar — get a reader census first: mirror the ones something reads, retire (?: never + retirementTombstone(), the [Decision] hideEmpty on record:details sections: the spec REFUSES the key, @object-ui/types declares it, the zod mirror omits it, and the renderer honours it — plus hideEmpty: false is not an override #7129 / finding(types): DashboardComponentSchema.title is declared-but-unread once the #7509 retirement lands #7623 route) the ones nothing reads. ⛔ Neither answer is assumed: A (mirror all ten) was refused precisely because it would enforce a dead key into the contract, and the [Decision] hideEmpty on record:details sections: the spec REFUSES the key, @object-ui/types declares it, the zod mirror omits it, and the renderer honours it — plus hideEmpty: false is not an override #7129 precedent retires such a key instead.
• ⛔ Option C (defer to Unify hand-written @object-ui/types zod with @objectstack/spec/ui (ListViewSchema drift) #2231) is refused on the evidence: the pair is not spec-derived, so Unify hand-written @object-ui/types zod with @objectstack/spec/ui (ListViewSchema drift) #2231 has nothing to unify here and the keys would stay declared-unenforced indefinitely.

Execution: this seat dispatches now — mode:subagent, model: fable = CONTRACT_REVIEW_TIER, M, Clause-② yes (the mirror's accept set narrows for wrong-typed values on every key it gains, and a retired key is refused by name). One or two PRs, @object-ui/types: minor, "Breaking for authored metadata" wording on any retirement.

⚠️ Routing note, so the label state is not read as an omission: this card carries no domain:* — it was filed by this seat for triage and has not been graded. It is dispatched under the maintainer direct-dispatch channel, whose authorising instruction is quoted verbatim above; the work is unambiguously this lane's (packages/types/src/zod/objectql.zod.ts and its pins). ⛔ This seat does not stamp domain:* — triage remains its single producer and may grade the card at any time without disturbing the dispatch.

---

Generated by Claude Code

[os-justin]

Claim: PM loop round R3
Session: session_01BAZFhALsQsGqxui8sNqM8s
Branch: claude/issue-7779-object-view-unmirrored-keys
Worktree: objectui-issue-7779
Domain: domain:spec by work surface — ⚠️ the card carries no domain:* label (triage has not graded it); dispatched under the maintainer direct-dispatch channel, authorising instruction quoted verbatim in the ruling record 5556357004. ⛔ This seat does not stamp domain:*.
File surface (region level): packages/types/src/zod/objectql.zod.ts — the ObjectViewSchema const (:196) only · packages/types/src/objectql.ts — the ObjectViewSchema interface block (:1804–:1922 region) and only if a key is retired · packages/types/src/__tests__/zod-mirror-parity.test.ts — only the objectql.zod.ts#ObjectViewSchema rows (:702, :864, the UnmirroredDeclared entry at :1437, and the header figures they feed); ⛔ the base.zod.ts#ComponentInputSchema rows (:577, :739) belong to the sibling below · a new pin packages/types/src/__tests__/object-view-unmirrored-keys-7779.test.ts · .changeset/object-view-unmirrored-keys-7779.md · ⛔ read-only: packages/plugin-list/**, packages/plugin-grid/**, packages/app-shell/** (census reading only), content/docs/releases/, skills/**.
Container & model: M, mode:subagent, model: fable = CONTRACT_REVIEW_TIER (ruled Clause-② yes: the mirror's accept set narrows on every key it gains, and a retired key is refused by name)
Clause-②: yes
Serial constraints declared (file / region granularity per #5734 comment 5551274423): #7493 item ① (dispatched in the same round) shares exactly one file — zod-mirror-parity.test.ts — at a different region (base.zod.ts#ComponentInputSchema rows vs these objectql.zod.ts#ObjectViewSchema rows). Both devs merge origin/main before opening and again after the sibling lands; conflicts go to the merge queue, ⛔ no hand-ordering by the PM. The #7122 chain (PR #7685, the other session) touches packages/types only at src/field-types.ts and the spec-parity / select-option / derivation pins — no file shared.
Premise re-verified by this seat on origin/main = fa7d66c4 (02:26Z): objectql.zod.ts:196 export const ObjectViewSchema = BaseSchema.extend({; the ten declared keys at objectql.ts:1804 defaultViewType, :1810 listViews, :1815 defaultListView, :1821 navigation, :1844 searchableFields, :1849 filterableFields, :1886 showViewSwitcher, :1911 viewTabBar, :1917 allowCreateView, :1922 viewActions — with the same names present on other interfaces in the file (navigation ×5, searchableFields ×2), so the dispatch requires every reading bound to the ObjectViewSchema block; ledger rows at :702 / :864 / :1437 / :1604 / :1855 / :2866–:2867. Referenced cards read current: #7279 closed (PR #7776 merged), #7129 / #7623 (the retirement route), #6152 pm:blocked, #2231 open — none dispatchable, none this dev's.

Ruling executed — B (maintainer 2026-09-06T02:2xZ, verbatim 「第二批(4 项,契约形状族) 帮我处理，全部同意」; record 5556357004): four spec-modelled keys mirrored by reference with the listViews value type decided; six local keys get a reader census first, then mirror-or-retire per key. Dispatch prompt carries the four-axis block verbatim (md5 0c32699e1a8a5580b85c22f3b08b0909).

⚠️ Review tier note: the seat's served model is claude-opus-5 this round, so the eventual contract-review verdict is produced by a contract-review-tier subagent with model passed explicitly — recorded here so the PASS comment's provenance is checkable.

---

Generated by Claude Code

[os-justin]

Claim (dev): objectui#7779 — the dev of session_01BAZFhALsQsGqxui8sNqM8s's dispatch, PM loop round R3.
Branch: claude/issue-7779-object-view-unmirrored-keys (probe push landed first, empty branch).
Worktree: objectui-issue-7779, base origin/main 6a9ee323 (the seat's premise at fa7d66c4 re-verified on this base: objectql.zod.ts:196, the ten declarations at objectql.ts:1804–:1922, the ledger rows at :702 / :864 / :1437 / :1604 / :1855 / :2866–:2867, every reading bound to the ObjectViewSchema block).
Scope: ruling B — the spec-modelled keys mirrored by reference to the spec slot, the six local keys after a reader census on the object-view node renderer, the listViews value type decided by measurement (never z.any()).
Report follows as an os-dev-report comment on this card, then a draft PR against main.

---

Generated by Claude Code

[os-justin]

os-dev-report

{
  "issue": 7779,
  "status": "done",
  "branch": "claude/issue-7779-object-view-unmirrored-keys",
  "pr": "https://github.com/objectstack-ai/objectui/pull/7922",
  "premise_still_valid": true,
  "summary": "Ruling B executed nine-for-ten on ObjectViewSchema (base origin/main 6a9ee323; the seat's premise at fa7d66c4 re-verified line for line, every reading bound to the ObjectViewSchema block). navigation / searchableFields / filterableFields are mirrored BY REFERENCE to SpecListViewSchema.shape.* (identity-pinned against the spec schema); allowCreateView / viewActions by reference to the sibling ViewSwitcherSchema slots the renderer forwards them into verbatim; defaultViewType (the declaration's seven-value enum) / defaultListView / showViewSwitcher as local literals after a reader census on packages/plugin-view/src/ObjectView.tsx; viewTabBar RETIRED (`?: never` + retirementTombstone(), zero reads — the tab-bar config is ViewTabBar's `config` prop from the host). listViews stays in the ledger on the ruling's own fallback clause, with the measurement pinned against the spec: the spec value (strict ObjectListViewSchema, columns required, refuses options / tuple filters / default) refuses the named views the README, the mdx and schema-reference.md teach, while the local NamedListView declares ~52 members of which the renderer reads 7. Parity ledger: entry 10 keys to 1; ObjectViewSchema joins SPEC_DERIVED_PAIRS by a real code reference; header figures 14 / 96 to 14 / 87, split 1 / 2 + 13 / 94 to 2 / 3 + 12 / 84 with history sentences. A seventh file the dispatch did not list moved by a gate: object-view-spec-parity.test.ts (its TS_ONLY_BACKLOG shrink-only pin held exactly these ten keys; now listViews + onNavigate; audit figures 11 / 13 to 20 / 22). New pin object-view-unmirrored-keys-7779.test.ts (52 tests). Two doc tables corrected (plugin-view README, plugin-view.mdx). Changeset @object-ui/types minor, Breaking for authored metadata. Assignee untouched. Draft PR #7922 with needs:contract-review attached by union with read-back; origin/main f5d2acc3 merged before opening (main moved nothing under packages/types); the sibling #7493 has not landed yet.",
  "tests": "On e9f86194, ratchet family re-run on the merged head 94e7ac47 (pushed sha). Build: `pnpm --filter @object-ui/types build` VERDICT command-exit 0 (124 emitted files verified). Vitest: `pnpm exec vitest run --maxWorkers=2 packages/types/` Test Files 129 passed (129), Tests 2388 passed (2388), VERDICT command-exit 0 — same figures at 94e7ac47; the three touched pins verbose: 3 files, 137 tests passed. Type-check: `pnpm --filter @object-ui/types type-check` (tsc --noEmit + tsconfig.examples.json + tsconfig.test.json) VERDICT command-exit 0, `--listFiles` shows the new pin compiled (1 hit); green again at 94e7ac47. Consumer type-checks, DOWNSTREAM direction against the rebuilt dist (their tsconfigs drop root paths): plugin-list, plugin-view, app-shell after building each closure — all three echo `type-check$ tsc --noEmit && tsc -p tsconfig.test.json` and Done, VERDICT command-exit 0. Reverse verification: standalone probe against dist authoring viewTabBar and defaultViewType 'tree' gives exactly two TS2322 at those lines, the eight-key literal clean, --listFiles reads packages/types/dist/objectql.d.ts (0 src reads); probe removed. Lint types: 0 errors (274 pre-existing any warnings, none in touched regions). check-changeset presence / no-major / fixed / overwrite all pass; check-control-bytes OK (6396 files); check:spec-symbols OK; check:doc-types, doc-fences, vi-mock-specifiers, vi-mock-inherit, shell-escape-residue, unreferenced-sources OK. NOT MEASURED locally (precondition, not red): check:doc-snippets exit 2 PRECONDITION NOT MET (six unbuilt packages, none this PR's); check:readme-exports could not judge one plugin-gantt type (unbuilt dist) — the plugin-view README was among the 43 judged; my doc diffs move zero fenced snippets (git diff -U0 fence count 0). Governed predicate (objectstack check-governed-merges.mjs --test, 8 paths): 0 of 8 hit — NOT governed. Ablation (Clause-2 yes): objectql.zod.ts alone reverted to the base blob under a trap with absolute paths; mutation proven on disk (tombstone line and spec-reference line each 1 to 0; blob 97b7a668 vs HEAD 44e31169); three pins under it: Test Files 3 failed (3), Tests 37 failed | 100 passed (137) — 34 in the new pin, 2 in object-view-spec-parity, 1 in the ledger, controls green; tsc -p tsconfig.test.json exit 2 naming exactly 'objectql.zod.ts#ObjectViewSchema'; restored via git checkout HEAD -- path, blob 44e31169 equals HEAD, git diff HEAD empty, status clean. No ablation-dist-preflight applies: the pins import the mirror from source, no dist resolves it.",
  "mcp_calls": "12 — claim comment; create PR; one issue_read get_labels that refuses a PR number (no effect); two pull_request_read (labels + body, then the label read-back); one issue_write label union; two dedup search_issues (both non-empty, self-validating); two issue creates (#7923, #7924); the report comment; its read-back. REST probe on issues returned 403 (proxy); the card and its comments were read through the zero-quota web payload channel.",
  "open_questions": [
    {
      "question": "listViews value type on ObjectViewSchema's zod mirror — the ruling's stop clause fired (the two value types are incompatible and either choice loses something); which face should the mirror enforce? Note a conflict in the dispatch: its stop-condition header says needs_decision with no PR beyond the probe, while the ruling's verbatim clause for the same condition says report it, mirror the other three and leave listViews in the ledger. The ruling's clause was followed as the more specific, maintainer-derived one; eight ruled keys are not held hostage to the ninth.",
      "options": [
        "A — the spec ObjectListViewSchema record by reference: refuses the README / mdx label-only views (at columns), schema-reference's tuple filters (at filter.0) and its default flag, and options (unrecognized_keys); loses documented behaviour; zero code cost; the renderer would still not honour kanban / gantt blocks written at the top level of a named view",
        "B — the local NamedListView key-for-key as a private zod object (~52 members): keeps every documented example green but enforces ~45 members nothing reads off a named view — the enforced-dead-key shape ruling B refused for the six local keys",
        "C — mirror exactly the seven read members (label, type, columns, filter, sort, options, data) and RETIRE the unread NamedListView members with `?: never` tombstones (the #7129 route), after #7924's per-member census — a second card; shrinks the surface to what runs",
        "D — leave ledgered (what this PR ships): declared-not-enforced on one key, pinned against the spec so a relaxation or a renderer change re-takes the measurement"
      ],
      "recommendation": "C, staged as #7924 then the mirror. 实际业务需求: the readers read seven members (measured off disk, pinned) and the writers split three ways (README / mdx the local shape, schema-reference tuple filters, ViewPreview spec-shaped bodies) — nothing beyond those seven is honoured today, so only those seven are real. 项目长远合理性: contract-first means the mirror enforces what runs; A declares a spec shape the renderer does not honour off a named view, B fossilizes a 52-member legacy vocabulary as contract. 防 AI 写元数据犯错: C refuses a wrong-typed value at the key and refuses dead members by name; A lets an AI-authored spec-shaped view validate green and render partially; B lets 45 dead keys validate green — declared, unenforced, unread. 创业阶段不扩散: C shrinks the surface; B fossilizes it; A is the north-star shape but only once the renderer honours it, which is an implementation card and is not assumed. D is the honest interim and is what this PR delivers; it costs nothing to keep until C is ruled."
    }
  ],
  "out_of_scope_findings": [
    "filed as #7923: content/docs/api/schema-reference.md's object-view example authors listViews.NAME.default: true, a key NamedListView never declared and ObjectView never reads (it reads defaultListView), and teaches the ObjectQL tuple filter dialect where the plugin-view pages teach rule objects",
    "filed as #7924 (finding): NamedListView declares ~52 members and the object-view renderer reads seven off a named view; the rest are declared, unenforced and unread, and they block listViews's mirror (the decision above)"
  ],
  "spec_readings": {
    "pin": "@objectstack/spec@17.2.0, ui entry, measured from the worktree: 117 exported object schemas walked; controls objectName 9 hits, columns 15, navigation 5, listViews 1; each of the six local keys 0 hits",
    "navigation": "ListViewSchema and ObjectListViewSchema: optional NavigationConfigSchema — strict object; mode defaults to page, view, preventNavigation, openNewTab, size, width; a bare string is refused; { view } parses with mode defaulted",
    "searchableFields": "both view faces: optional array of string",
    "filterableFields": "both view faces: optional array of string; spec description: Legacy shorthand for userFilters.fields — Prefer userFilters",
    "listViews": "ViewSchema.listViews: optional record whose value is ObjectListViewSchema by identity; strict (catchall never); columns the only required key (a union); type a nine-value enum defaulting to grid"
  },
  "census": {
    "renderer": "packages/plugin-view/src/ObjectView.tsx (registered as object-view by plugin-view/src/index.tsx); switcher packages/plugin-view/src/ViewSwitcher.tsx; read set derived off disk by the pin with the schema.KEY regex",
    "allowCreateView": "READ — ObjectView.tsx:1134 forwards it into the view-switcher node; ViewSwitcher.tsx:276 reads it — mirrored by reference to ViewSwitcherSchema.shape.allowCreateView",
    "viewActions": "READ — ObjectView.tsx:1135 forwards; ViewSwitcher.tsx:254-256 maps it — mirrored by reference to ViewSwitcherSchema.shape.viewActions",
    "defaultViewType": "READ — ObjectView.tsx:769 `schema.defaultViewType || 'grid'`; also the registration's editable-props meta — mirrored as the declaration's seven-value enum (chart / tree are host-only, #5321)",
    "defaultListView": "READ — ObjectView.tsx:701-702 `namedListViews?.[schema.defaultListView]` — mirrored as string",
    "showViewSwitcher": "READ — ObjectView.tsx:1910 `schema.showViewSwitcher === true` — mirrored as boolean",
    "viewTabBar": "ZERO reads on the node; repo-wide the key appears in no source file outside @object-ui/types (two doc tables listed it); ViewTabBarConfig reaches the bar only as ViewTabBar's config prop from app-shell views/ObjectView.tsx:2825; the 2026-07 audit had measured it dead since introduction — RETIRED",
    "controls": "objectName and layout read (positive); viewTabBar and the never-declared viewSwitcherPosition not read (negative); the same query, so each zero is a reading"
  },
  "list_views_decision": {
    "choice": "left in the ledger on the ruling's fallback clause; not mirrored; z.any() not used",
    "reading": "renderer reads label, type, columns, filter, sort, options, data off a named view (7 of ~52 declared members); spec ObjectListViewSchema accepts the catalog's { label, columns } but refuses the README / mdx { label } view (columns), a type+filter view without columns (columns), schema-reference's tuple filter (filter.0) and default (unrecognized_keys), options (unrecognized_keys), a partial kanban { groupByField } (kanban.columns); writers disagree: README / mdx local shape, schema-reference tuple filters, app-shell ViewPreview.tsx:113 spreads a spec-shaped view body into listViews"
  }
}

---

Generated by Claude Code

[os-justin]

Contract review — PASS WITH NOTED DEVIATIONS at CONTRACT_REVIEW_TIER (2026-09-06T03:45Z) — PR #7922, head 94e7ac478. Two must-fix items ordered as a patch round; neither touches an accept-set judgment.

Implemented-by: dev subagent of this session's dispatch, branch claude/issue-7779-object-view-unmirrored-keys; dev report 5556615555
Reviewed-by: a contract-review-tier subagent with model passed explicitly, commissioned by this seat — ⚠️ the seat's own served model this round is claude-opus-5, not CONTRACT_REVIEW_TIER (get_session 02:26Z and 03:21Z; declared at round open, comment 5556350737, and on the claim). The verdict below is that subagent's, adopted by this seat after verifying its evidence per the tier-delegation rule; ⛔ the seat did not produce a tier-gated judgment itself.

How the reviewer read (recorded because it changes what the verdict is worth): card + PR body + every diff hunk by ref, the new pin whole, then — to run rather than trust — the branch tree extracted with git archive into a scratch copy, installed there, and the three pins, the ablation and the spec probes re-run. The shared checkout was never modified.

① Derived judgments — independently reproduced, all nine dispositions hold. The reviewer ran its own schema.KEY census of packages/plugin-view/src/ObjectView.tsx (26 distinct keys, objectName ×20 and layout ×2 as positives) and found every mirrored key at the cited line and no viewTabBar. The retirement — the one irreversible act — was verified hard: git grep -c viewTabBar on the branch hits 9 files, all packages/types plus the two doc tables, the 2026-07 audit and the changeset; zero in plugin-view/src, app-shell/src, apps/, examples/; the only non-test render site (app-shell/src/views/ObjectView.tsx:2825) passes a literal config, not a schema-derived one; the sibling objectstack checkout has zero hits (cloud not present locally — recorded as unmeasured). The two sibling-slot mirrors are sound (views.zod.ts:145-168 equals the declaration; the renderer forwards verbatim; no import cycle). defaultViewType's seven-vs-nine is the ruled narrowing, and the reviewer's adversarial note is worth keeping: the renderer switches on a string, so a JSON defaultViewType: 'tree' reaches the host-only branch through passthrough today — the mirror narrows below incidental runtime reach, which is the declared surface the ruling asked for, and the changeset names it under "Who is affected". The seventh file's move is genuinely forced (its shrink-only ratchet fails under ablation). Ledger arithmetic re-derived from the branch: 14/87, ∩ SPEC_DERIVED_PAIRS = 2/3, local 12/84, each pinned spelling occurring exactly once; SPEC_DERIVED_PAIRS membership is by a real AST code reference, not a comment. The ablation was reproduced: 37 failed / 100 passed with the non-pin failures being exactly the backlog pin, the audit-figures pin and the SPEC_DERIVED_PAIRS re-derivation, and the restore proven by blob hash.

listViews, the tenth key — the reviewer confirms (a) the incompatibility is real as measured (the spec value refuses the README :154 / mdx :72 label-only form, schema-reference.md:863-864's tuple filter and default, and options; app-shell's ViewPreview writes the spec shape while the docs write the local one), and (b) shipping nine with the tenth measured and escalated was right — the eight mirrors and the retirement are independent of the value-type decision, z.any() was never used, and stopping would have held completed, ruled enforcement hostage. The contradiction between this seat's stop-condition header and its own quoted fallback clause is the seat's defect, not the dev's — recorded here, and it goes to the skills lane as a dispatch-template finding at shift end.

② semver / changeset — @object-ui/types: minor opening "Breaking for authored metadata:", a ten-row table naming every key and its disposition and what a viewTabBar author now sees on both faces. minor is correct per AGENTS.md and check-changeset-no-major.mjs; CI's Changeset Bump Policy is green.

③ Boundary flags — exactly 8 files; nothing under content/docs/releases/ or skills/**; main has moved 3 commits with none under packages/types. Two docs files sit outside the dispatch's listed surface (one under a path the brief called read-only) — justified, pinned, and now recorded as a declared deviation. #7923 / #7924 are findings, not carriers.

Patch round ordered (head will move; the seat re-reviews the delta only):

1. Figures: NamedListView has 47 top-level members (40 unread), not ~52 / ~45 — the reviewer counted with the pin's own regex, at the head and at the merge-base. Correct the changeset, objectql.zod.ts:238-239, the ledger comment :1465-1467 and the PR body; tighten the >= 40 floor if a firmer number is stable.
2. Test count: the PR body says 52; the per-file run is 90 (90 / 20 / 27 = 137).
3. Reference Decision: what value type should ObjectViewSchema.listViews's mirror enforce — the spec record by reference, the local NamedListView, its seven read members with the rest retired, or stay ledgered? #7928 in the PR body and declare the two docs files.

The carrier concern is already answered: this seat filed #7928 at 03:29Z — a needs-user-decision card carrying the listViews value-type decision with all four options, the measurement and the four-facet analysis — so Fixes #7779 stays and the remainder is owned. ⚠️ Two things go to the maintainer with it, from the reviewer: the dev's recommendation C is a local shape, which departs from the ruling's "spec-modelled keys by reference to the spec slot"; and whichever face is chosen breaks a live writer (app-shell's ViewPreview writes the spec shape, the docs write the local one). Both are now on #7928.

needs:contract-review stays hung until the delta review. ⛔ No ready flip, no enqueue.

---

Generated by Claude Code