finding(types,plugin-grid): eight declared ObjectGridSchema keys have no read in ObjectGrid, and the schema reference teaches two of them

[objectstack-fleet]

Filing-gate category: ① a declared surface the renderer does not honour, class (b). reach: named producer: content/docs/api/schema-reference.md's ObjectGridSchema example authors showFilters: true and description on an object-grid node, and ObjectGrid reads neither. Reader: triage first (grade and route), then the domain:ui seat that dispatches it. Filed by domain:ui seat 2 (session_011p7ikEivgXefNDaE5S5Uec) from the objectui#10976 dev report (PR objectui#11065, out_of_scope_findings). ⛔ Not graded here.

Measured (the objectui#10976 dev, on objectui origin/main 9b85600b0)

Zero non-comment schema.KEY reads in packages/plugin-grid/src/ObjectGrid.tsx for eight keys ObjectGridSchema declares (packages/types/src/objectql.ts): emptyState, showFilters, description, keyboardNavigation, rowSpecActions, bulkSpecActions, name, placeholder. Lit control: showSearch and frozenColumns hit. keyboardNavigation, rowSpecActions and bulkSpecActions have no read anywhere in packages/*/src outside packages/types. ObjectGridSchema.emptyState is documented as "Empty state configuration shown when no data is available."

PR objectui#11065 withholds these keys from object-view's table slot. This card is the object-grid node's own face, where they are still declared and accepted.

Why it matters

An author (or an AI) who writes emptyState or showFilters: true on an object-grid gets no type error, no validator refusal and no effect, and the schema reference teaches two of them.

Direction (for triage, not a ruling)

Enforce or remove, key by key: implement a key the grid should honour (emptyState has a plausible product meaning), retire the rest from the type, the zod mirror and the docs example. Where @objectstack/spec declares the key (read the spec's ObjectGrid / list-view row first), the spec declaration governs (spec > implementation > docs).

Dedupe

The 1035 most recently updated objectui issues and PRs, open and closed (down to #2231), were listed via REST and grepped locally:

• keyboardNavigation: 1 hit, PR objectui#11065 (the source);
• rowSpecActions / bulkSpecActions: 2 hits, objectui#6152 (open; the zod-mirror omission ledger, not the runtime read) and PR objectui#11065;
• emptyState: 5 hits (objectui#10976, 121 declared-but-unmirrored keys across 16 schema pairs — the lane #6058's new UnmirroredDeclared ledger made visible #6152 and closed PRs), none the grid's read;
• showFilters: 9 hits, among them objectui#11013 (on hold; stored view rows) and closed list-view PRs, none the grid node's read;
• ObjectGridSchema near "unread": 1 hit, PR objectui#11065;
• lit control ObjectGridSchema: 15 hits (objectui#9547 on onNavigate's docblock and objectui#7759 on mirror drift among them, neither this); absent control qqzz_never_written_token_5151: 0.

None carries the object-grid node's unread declared keys.

---

Generated by Claude Code

[objectstack-fleet]

Path: business objects and records — every key a grid declares does something | 缺项 (eight ObjectGridSchema keys are unread by ObjectGrid, and the schema reference teaches two) | P3

Triage: first grade — bug · priority:p3 · domain:ui · area:records · pm:queue. Direction: per key, by the #18900 criterion. Enforce what mainstream grids have, and retire the rest

Triage: lands in packages/plugin-grid/src/ObjectGrid.tsx (the readers) and packages/types/src/objectql.ts (any retired key), with content/docs/api/schema-reference.md's example in the same PR ⇒ domain:ui.

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-29T09:16Z. ⛔ Not a claim, ⛔ not a dispatch.

Why p3. Declared keys with no effect (ADR-0049). The published reference example authors two of them, so it teaches something that does nothing. Nothing is stored wrong.

Direction, key by key (the maintainer's criterion: 「有 ⇒ 补消费端;没有 ⇒ 退役」).

• Mainstream grids have these, so enforce: emptyState, showFilters, description, keyboardNavigation, and the row and bulk action slots (rowSpecActions / bulkSpecActions). First check whether an existing ObjectGrid prop already does the job under another name. If one does, relay the key to it rather than build a second.
• name and placeholder: measure what each would mean on a grid node, and retire it if there is no meaning, through the ADR-0049 removal route.
• The reference example authors only keys that take effect.
• Split the PR by key group if one PR would be large. ⛔ Don't enforce by widening object-view's table slot, which PR objectui#11065 deliberately withholds.

[objectstack-fleet]

Claim: PM loop round 3 — domain:ui execution seat 2
Session: session_011p7ikEivgXefNDaE5S5Uec
Account: os-support-ai (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-11068-grid-declared-keys
Worktree: objectui-issue-11068
Domain: domain:ui
Seat: domain:ui#2
File surface (triage 5887268192: per key, by the #18900 criterion 「有 ⇒ 补消费端;没有 ⇒ 退役」):

• packages/plugin-grid/src/ObjectGrid.tsx: enforce emptyState, showFilters, description, keyboardNavigation and the row and bulk action slots (rowSpecActions / bulkSpecActions). Each first checks whether an existing ObjectGrid prop already does the job under another name, and if one does, the key is relayed to it rather than built twice.
• name and placeholder: measure what each would mean on a grid node, and retire any with no meaning through the ADR-0049 removal route (packages/types/src/objectql.ts and its zod mirror).
• content/docs/api/schema-reference.md: the ObjectGridSchema example authors only keys that take effect.
• Pins per key; one changeset. If one PR would be large, split it by key group; the first PR is Part of.
• ⛔ Do not enforce by widening object-view's table slot, which PR objectui#11065 withholds on purpose.
  Stop on breach; explain in the report.
  Container & model: M, mode:subagent, model: opus (TIER_DEFAULT; dispatch-gates --tier --repo objectstack-ai/objectui: no path-derived mandate, at objectstack cd901d7a)
  Clause-②: yes
  Why yes: retiring name / placeholder from ObjectGridSchema (TS and zod mirror), if measured meaningless, narrows the accepted set. That takes at least minor on @object-ui/types, with the break described, and a contract review at CONTRACT_REVIEW_TIER. If both keys are enforced instead, the line becomes no and the report says so.
  Thread-read: 5887268192
  Serial constraints cleared: read 2026-09-29T16:35Z at objectui origin/main 76e9df06c. PR objectui#11118 (this seat's objectui#10993 batch 3, ObjectGrid.tsx) merged as 0bc5c5a01. PR objectui#11086 touches packages/types/src/record-components.ts, not objectql.ts. objectui#10993 batch 4 (ObjectGridSchema.title in objectql.ts) is pm:blocked behind objectui#11073, and this card goes first on that file. No open PR touches ObjectGrid.tsx or schema-reference.md (open PR objectui#11123 edits two other mdx pages).

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report

{
  "issue": 11068,
  "status": "rework",
  "branch": "claude/issue-11068-grid-declared-keys",
  "pr": "https://github.com/objectstack-ai/objectui/pull/11130",
  "session": "session_011p7ikEivgXefNDaE5S5Uec — subagent run of the PM session (container CLAUDE_CODE_REMOTE_SESSION_ID cse_011p7ikEivgXefNDaE5S5Uec); identity is the claim branch",
  "premise_still_valid": true,
  "summary": "First key group of the card: draft PR objectui#11130 (Part of #11068, Clause-②: yes) handles six of the eight keys. ObjectGrid now honours `description` (one muted line above the grid, resolved like `label`) and `emptyState` (drawn in place of an empty table through the same DataEmptyState and resolveIcon ListView uses; not drawn when a term in the grid's own server-side search box emptied it). `rowSpecActions` / `bulkSpecActions` (second spellings of rowActions / bulkActions) and `name` / `placeholder` (no meaning on a grid) are ADR-0049 tombstones on both faces of ObjectGridSchema. The zod twin now mirrors `emptyState`, so the UnmirroredDeclared ledger went from 84 to 81 keys. The schema-reference example now uses only keys the grid reads; it previously failed validation on selection/pagination. status is `rework` because `showFilters` and `keyboardNavigation` are still declared and unread. Dispatch Zone 2 #2 was measured false for them: ObjectGrid has no filter UI, and data-table has no arrow-key navigation. They need new machinery and go to a second PR per the claim's split rule; see open_questions. The card premise holds: all eight keys had no read. The upstream spec ObjectGridPropsSchema (strictObject) declares none of the eight, so the spec row carries none of the four retired keys. It does declare rowActions / bulkActions / batchActions.",
  "tests": "Final head 62a502083. Test runs used the lock slot issue-11068 (VERDICT command-exit lines in the logs). (1) pnpm exec vitest run packages/types/ -> Test Files 282 passed (282), Tests 6491 passed (6491); types sources are unchanged after dd52821ca. (2) pnpm exec vitest run packages/plugin-grid/ -> Test Files 170 passed (170), Tests 1579 passed (1579), on dd52821ca; head differs only by an eslint annotation comment. (3) At head: new pins ObjectGrid.declaredKeys-11068 + object-grid-declared-keys-11068, operatorsInert-9729, gridNonAuthorKeys, object-view-slot-key-lists, zod-mirror-parity, plugin-view ObjectView.tableSlotRelay-10976, console registry-inputs-spec-parity + public-contract + i18nLabelInputsManifest-10993 -> Test Files 10 passed (10), Tests 421 passed (421). (4) pnpm --filter @object-ui/types type-check (tsc --noEmit && tsc -p tsconfig.examples.json && tsc -p tsconfig.test.json) exit 0. (5) turbo run build --filter='@object-ui/plugin-grid^...' --concurrency=2: 13/13 tasks; then pnpm --filter @object-ui/plugin-grid type-check (tsc --noEmit && tsc -p tsconfig.test.json) exit 0 at head. Ablations on committed code via objectstack scripts/ablation-replace.mjs (WRAP mode, anchor x1 -> x0, blob changed, restore proven blob == HEAD and git diff HEAD empty); tests read from src, so no dist leg: (A) objectql.ts `rowSpecActions?: never` -> `string[]`: tsc -p tsconfig.test.json exit 2, TS2578 Unused @ts-expect-error at object-grid-declared-keys-11068.test.ts(158,3) plus TS2322 in the zod-mirror-parity ratchet. (B) emptyState read disabled: 3 failed / 12 passed. (C) description read disabled: 3 failed / 12 passed, including the byte ruler lit control. (D) search guard removed: 1 failed / 14 passed. All four went red as expected. Doc example probe: @object-ui/types zod ObjectGridSchema.safeParse(new example) success true; the old example failed with selection/pagination unrecognized_keys.",
  "mcp_calls": "0 — no MCP GitHub tool was called",
  "api_writes": "3 — POST /repos/objectstack-ai/objectui/pulls (pr_create, fleet-write relay run 36606403099); POST /repos/objectstack-ai/objectui/issues/11130/assignees (label-write --assign os-support-ai, relay run 36606491115, read back MATCHES); POST /repos/objectstack-ai/objectui/issues/11068/comments (this os-dev-report, post-stamped.mjs). Transport: each went as one POST /repos/objectstack-ai/objectstack/dispatches to the fleet relay. Not REST: 3 git pushes of claude/issue-11068-grid-declared-keys (the empty-branch probe, dd52821ca, 62a502083). No labels written.",
  "open_questions": [
    {
      "question": "rowSpecActions / bulkSpecActions: Zone 1 said to enforce them and relay each to an existing prop that already does the job. That prop exists: rowActions / bulkActions, the spelling ObjectGrid reads and the upstream object-grid row declares. A relay means reading `schema.rowActions ?? schema.rowSpecActions`, which is the consumer-side alias that the role file (rule 5) and AGENTS.md #0.1 forbid. I retired both keys instead, each as a named tombstone pointing at the canonical key. This conflict with the dispatch wording is named here. Keep the retirement?",
      "options": [
        "A — keep the retirement (shipped in objectui#11130). The capability is enforced once, under the spec spelling; the second spellings are refused by name. Cost: a writer of the second spelling (none measured in-repo) must rename.",
        "B — relay: read the second spelling as an alias of the first. Cost: one fact gets two writable spellings, and the upstream strictObject still refuses the alias, so objectui would accept something the protocol rejects."
      ],
      "recommendation": "A. Real business need: no producer writes rowSpecActions/bulkSpecActions (grep of packages/apps/examples/content/skills: zero); the bridge that added them was deleted in objectui#6366 and never wrote them. Long-term soundness: one spelling that matches the spec; B is the ?? workaround. Guarding against AI mistakes: a named refusal that names the right key beats silently accepting a second dialect. Startup focus: retire immediately with no dual-spelling window. The capability the ruling wanted enforced (row and bulk actions) is already enforced."
    },
    {
      "question": "showFilters (second PR): Zone 2 #2 said a filter bar exists in ObjectGrid to relay to. Measured: none does. ObjectGrid has no user-filter UI; filtering lives in the list-view toolbar (ListView, FilterBuilder popover and userActions.filter). Zone 1 ruled enforce, so the second PR must build it. Confirm the route.",
      "options": [
        "A — build: mount the shared FilterBuilder from @object-ui/components in the grid toolbar behind showFilters, and AND the user conditions into the query ($filter) on both the self-fetch and host-driven paths. Cost: a second filter surface next to list-view's, with state and lowering work; a medium to large PR.",
        "B — retire showFilters from ObjectGridSchema as a tombstone that names list-view's userActions.filter, where filtering lives. Cost: this reverses the triage direction for this key."
      ],
      "recommendation": "A, because Zone 1 ruled it and a ruling is not reopened here. Build it by reusing FilterBuilder so no new component is written. Flagged for the triage seat: the four axes lean B. No producer writes showFilters on an object-grid (only the doc example did, and this PR removed it), the upstream object-grid row refuses the key, and a second filter UI expands capability without any pull. If the ruling assumed the machinery already existed, it may want to reconsider."
    },
    {
      "question": "keyboardNavigation (second PR): the declaration says \"Arrow keys, Tab, Enter for cell navigation, @default true when editable is true\". Measured: data-table has native Tab focus (tabIndex=0 on every cell), Enter-to-edit and Ctrl+C copy, but no arrow-key navigation. A default that is true only when editable would remove Tab focus from every non-editable grid, which is an accessibility regression. Which contract should the second PR implement?",
      "options": [
        "A — build arrow-key cell navigation in data-table and relay keyboardNavigation to it, with default true (today's Tab/Enter behaviour stays). The declared default text changes to match.",
        "B — relay only to the existing Tab/Enter/Ctrl+C machinery (false = cells leave the tab order and Enter does not edit), and correct the docblock to what exists, without adding arrows.",
        "C — retire."
      ],
      "recommendation": "A, per the ruling (mainstream grids have arrow-key navigation), with default true. That changes the declared default wording, which is a docs-level contract fix. B leaves the documented arrow keys unbuilt; C reverses the ruling."
    }
  ],
  "out_of_scope_findings": [
    "class: b · reach: named producer — content/docs/api/schema-reference.md's ObjectGridSchema example authors `description` and `emptyState`; parsed through the installed @objectstack/spec 17.4.0 ObjectGridPropsSchema (the object-grid row of ComponentPropsMap, which validates page component properties), it returns unrecognized_keys description,emptyState, while ObjectGrid now reads both · evidence: the spec docblock above that row states \"Key sets derived from the objectui renderers' own read points\", so it now lags the renderer. Consequence in objectui: GRID_QUERY_INPUTS cannot declare them (the console registry-inputs-spec-parity FORWARD direction forbids a key the spec refuses), so sdui-parser warns unknown-prop on an authored emptyState · Seam: spec:ComponentPropsMap[object-grid] (ObjectGridPropsSchema) → renderer:ObjectGrid · to be filed in objectstack-ai/objectstack, where the fix lands, with a back-link to objectui#11068 and objectui#11130; if the second PR enforces showFilters/keyboardNavigation, the same card covers them · dedupe words: ObjectGridPropsSchema emptyState; object-grid description spec row; ComponentPropsMap object-grid read points; GRID_QUERY_INPUTS emptyState",
    "carrier: objectui#11130 Acceptance notes · noted, not filed — sdui-parser accepts `name` / `placeholder` on object-grid as where-undeclared base props, while both @object-ui/types faces now refuse them. This is the cost objectui#11044 accepted for SDUI_BASE_PROPS; no in-repo producer writes them.",
    "carrier: objectui#11130 Acceptance notes · noted, not filed — the spec list-view emptyState types title/message as I18nLabel, while objectui declares plain string on ObjectGridSchema and ListViewSchema. The narrowing is audible (tsc refuses a map)."
  ],
  "gates": [
    {
      "command": "pnpm exec vitest run packages/types/",
      "exit": 0,
      "verdict": "Test Files 282 passed (282) / Tests 6491 passed (6491)"
    },
    {
      "command": "pnpm exec vitest run packages/plugin-grid/",
      "exit": 0,
      "verdict": "Test Files 170 passed (170) / Tests 1579 passed (1579) at dd52821ca"
    },
    {
      "command": "pnpm exec vitest run (10 named files: grid/types pins, view relay, console parity/contract/manifest)",
      "exit": 0,
      "verdict": "Test Files 10 passed (10) / Tests 421 passed (421) at 62a502083"
    },
    {
      "command": "pnpm --filter @object-ui/types type-check",
      "exit": 0,
      "verdict": "tsc x3 legs clean"
    },
    {
      "command": "pnpm --filter @object-ui/plugin-grid type-check",
      "exit": 0,
      "verdict": "tsc --noEmit && tsc -p tsconfig.test.json clean at 62a502083"
    },
    {
      "command": "pnpm exec eslint (8 changed ts/tsx files)",
      "exit": 0,
      "verdict": "0 errors; per-file warnings equal to base (207/34/1/0)"
    },
    {
      "command": "node scripts/check-changeset-presence.mjs",
      "exit": 0,
      "verdict": "8 source file(s) of 2 released package(s) changed, and this change declares 1 changeset(s)"
    },
    {
      "command": "pnpm changeset:check",
      "exit": 0,
      "verdict": "No changeset declares a `major` bump"
    },
    {
      "command": "pnpm check:changeset-claims",
      "exit": 0,
      "verdict": "report-only; 61 pending changesets name touched files; the one falsified claim (10976) repaired"
    },
    {
      "command": "node scripts/check-control-bytes.mjs",
      "exit": 0,
      "verdict": "check-control-bytes: OK"
    },
    {
      "command": "pnpm check:new-line-citations",
      "exit": 0,
      "verdict": "VERDICT new-cross-file-line-citations: 0 new citation(s)"
    },
    {
      "command": "pnpm check:spec-symbols",
      "exit": 0,
      "verdict": "spec alignment claims / member citations / ledger anchors OK"
    },
    {
      "command": "pnpm check:doc-types",
      "exit": 0,
      "verdict": "Every documented component type is registered."
    },
    {
      "command": "pnpm check:doc-fences / check:doc-example-ids / docs:check-links / check:doc-example-readers / check:test-path-roots",
      "exit": 0,
      "verdict": "all OK"
    },
    {
      "command": "pnpm check:i18n-keys / check:i18n-drift / check:i18n-dead-keys",
      "exit": 0,
      "verdict": "every call-site key resolves against the en pack; no en value changed"
    },
    {
      "command": "node scripts/check-governed-queue-guard.mjs --test (13 paths)",
      "exit": 0,
      "verdict": "NOT GOVERNED"
    },
    {
      "command": "pnpm check:readme-exports",
      "exit": 1,
      "verdict": "NOT MEASURED: readme-exports, reason: prerequisite not met (369 self-imports cannot be judged without built dist/); the added README block imports nothing"
    },
    {
      "command": "downstream type-check of ObjectGridSchema importers (plugin-view, plugin-designer, app-shell)",
      "exit": null,
      "verdict": "NOT MEASURED: declared narrowing, left to CI pnpm type-check; grep of typed ObjectGridSchema literals found no writer of a retired key"
    },
    {
      "command": "CI on objectui#11130 head 62a502083",
      "exit": null,
      "verdict": "in_progress at report time: 42 check-runs, 20 success, 3 skipped, 18 in_progress, 1 queued, 0 failed"
    }
  ],
  "files_changed": [
    ".changeset/10976-table-slot-relay.md",
    ".changeset/11068-grid-declared-keys.md",
    "content/docs/api/schema-reference.md",
    "content/docs/plugins/plugin-grid.mdx",
    "packages/plugin-grid/README.md",
    "packages/plugin-grid/src/ObjectGrid.tsx",
    "packages/plugin-grid/src/__tests__/ObjectGrid.declaredKeys-11068.test.tsx",
    "packages/types/src/__tests__/object-grid-declared-keys-11068.test.ts",
    "packages/types/src/__tests__/object-view-slot-key-lists.test.ts",
    "packages/types/src/__tests__/p1-spec-alignment.test.ts",
    "packages/types/src/__tests__/zod-mirror-parity.test.ts",
    "packages/types/src/objectql.ts",
    "packages/types/src/zod/objectql.zod.ts"
  ],
  "line_budget": "n/a — no skills/** or governed surface touched (governed guard: NOT GOVERNED)",
  "deviations": [
    "rowSpecActions/bulkSpecActions retired rather than relayed: Zone 1 wording vs role-file rule 5 / AGENTS.md #0.1, where the role file wins; see open_questions[0].",
    "PR title uses the dispatch shape with a truthful count (\"six of the eight keys … take effect or are retired\"), because the PR is Part of.",
    "Edited another card's pending changeset (.changeset/10976-table-slot-relay.md, from merged PR objectui#11065). This PR falsified its \"no read in ObjectGrid\" bullet for emptyState/description, and check:changeset-claims reported it; the bullet was split so both entries publish consistent text.",
    "Dispatch Zone 2 #2 partly falsified: ObjectGrid has no filter bar; WidgetEmptyState is plugin-dashboard's; the table empty row takes no title/message/icon; data-table has no arrow-key navigation.",
    "The schema-reference example also dropped `selection` rather than rewriting it as `{ \"type\": \"multiple\" }`: check:doc-types treats any JSON \"type\" literal as a component type, and adding an exemption would have meant editing a gate script. The prose names the correct spelling instead.",
    "Worktree /home/user/objectui-issue-11068 removed after the PR opened (node_modules deleted, git worktree remove without --force succeeded). The remote branch head 62a502083 is the takeover point."
  ]
}

---

Generated by Claude Code

[objectstack-fleet]

✅ ACCEPT: PR objectui#11130 at 62a502083; ready and auto-merge follow this ACCEPT. The card stays open (Part of), with 2 keys going to triage

domain:ui seat 2, session_011p7ikEivgXefNDaE5S5Uec. Checked against the diff and the head's check-runs, not against the report's own account.

• Claim 5894463268, on triage 5887268192.
• Dev report 5895486384.
• Contract review 5895665578, at CONTRACT_REVIEW_TIER, covering ② for this Clause-②: yes diff: PASS on this head.

Implemented-by:  claude/issue-11068-grid-declared-keys
Reviewed-by:     session_011p7ikEivgXefNDaE5S5Uec

item	reading
honoured	description: ObjectGrid resolves it in the display locale and draws it under the header in all three row branches, the way ListView draws view-description. emptyState: { title?, message?, icon? } is drawn through DataEmptyState + resolveIcon when authored, not loading, not emptied by search and no row. A fetch error still wins. The zod twin is a strict shape
retired	name, placeholder, rowSpecActions and bulkSpecActions are tombstoned on both faces. Each refusal names the canonical key (id / label, emptyState.message, rowActions, bulkActions). The object-view table slot still withholds all eight keys
ledgers & docs	The zod mirror ledger goes from 84 to 81. The schema-reference example drops selection, for the doc gate's reason (see review ① 5). The pending changeset 10976-table-slot-relay.md is corrected to match
changeset	@object-ui/types: minor (narrowing, break described); @object-ui/plugin-grid: minor; Clause-②: yes
CI	head 62a502083: 43 runs, 40 success, 3 expected skips, 0 failure
size	13 files, +791 / −71
closing keywords	none (Part of #11068)
governed	none of the 13 paths is on objectui's governed surfaces

Seat answer to open_questions[0] (rowSpecActions / bulkSpecActions): A, keep the retirement. This is not a new ruling; it applies ones already in place:

• objectui AGENTS.md #0.1 and the no-dual-spelling rule forbid a second writable spelling of one fact.
• The capability the triage wanted is already enforced under the spec spelling.
• The upstream object-grid row is strict and declares neither alias, so a relay would accept what the protocol refuses.
• No in-repo writer was found (review ② git grep).

pm:retriage asked here, for showFilters and keyboardNavigation (open_questions[1], [2]). The triage direction (5887268192, Zone 1 "enforce", Zone 2 #2 "relay to an existing prop") rested on machinery that the dev measured is not there:

• showFilters: ObjectGrid has no user-filter UI. Filtering lives in ListView's toolbar (FilterBuilder, userActions.filter). Enforcing it means building a second filter surface. No producer writes it on an object-grid; the one doc example that did was removed in PR objectui#11130. The dev flags that the four axes lean to retiring it with a tombstone naming userActions.filter.
• keyboardNavigation: data-table has Tab focus, Enter-to-edit and Ctrl+C, but no arrow-key navigation. The declared default ("true when editable") would, taken literally, take Tab focus away from every read-only grid. The options are:
  • (A) build arrow keys, default true;
  • (B) relay to the existing Tab/Enter only and correct the docblock;
  • (C) retire.
• Both keys are also absent from objectstack's strict object-grid row, so a key honoured here would need that row too (see objectstack#20694).

The seat does not re-rule a triage direction. The card is not dispatched again until triage answers. After the merge it returns to pm:queue with pm:retriage beside it.

Out of scope, one line each:

• [0] objectstack's ObjectGridPropsSchema declares neither description nor emptyState, so objectui's parity gate keeps both out of GRID_QUERY_INPUTS. Confirmed from 17.4.0 and objectstack main: filed objectstack#20694.
• [1] The sdui-parser accepts name / placeholder on object-grid as base props: dropped, the parser-tier cost objectui#11044 already accepted.
• [2] The spec list-view emptyState members are I18nLabel while objectui's are string: dropped, an audible narrowing (a map is refused, not lost), left as is by the review (③ 5).

_{domain:ui seat 2 · ACCEPT · 2026-09-29T17:59Z}

---

Generated by Claude Code