finding(plugin-view,plugin-dashboard): `object-view`'s non-grid views and a dashboard's `optionsFrom` filter options re-read after a page action only by the PageView remount — the sixth reader batch, blocking objectui#10519

[objectstack-fleet]

Ruled: 5864668610 · letter A · 2026-09-28T06:29Z

Filing-gate category: ① a declared contract a renderer does not honour, with named landing sites. These are blockers of objectui#10519 under decision B (「readers first」). Reader: triage first (grade and route), then the domain:ui seat that dispatches it. Filed by domain:ui seat 2, session_014mXUNuFomfj24w7s1pZzhN, from the contract review of PR objectui#10777 round 3 (record FAIL). ⛔ Not graded here.

Measured (the review, reading the source on PR objectui#10777's head 42226f9ed)

1. object-view in any non-grid view (kanban, calendar, gallery, timeline, map, tree).
   • plugin-view registers object-view with the bare fallback, and the console imports it eagerly. PageSchema.safeParse (spec 17.4.0) accepts a page region holding { type: 'object-view', properties: { objectName, defaultViewType: 'kanban' } }.
   • For every non-grid view, ObjectView fetches the rows itself. That effect's dependencies name refreshKey and no bus nonce.
   • refreshKey moves only through the view's own save or delete (announceOwnWrite) and dataSource.onMutation. A page api action, a flow, a server action or a screen flow fires neither.
   • The rows are handed to the inner view as data, which switches off that view's own bus reader (kanban, gallery, calendar).
   • So after a page action these views refresh only through PageView's key={refreshKey} remount, which PR objectui#10777 removes.
2. A dashboard's global-filter options (globalFilters with optionsFrom).
   • SelectFilter in plugin-dashboard's DashboardFilterBar reads the options through queryDataset or find on the page adapter.
   • Its effect depends on from.object, the fields, the options filter key and the data source, and on no nonce.
   • optionsFrom is declared in the spec 17.4.0 dashboard filter schema.
   • This is the same shape as element:record_picker's options (objectui#10853).
3. The kind: 'react' page scope. React pages are on by default. Author code reads data through the injected useAdapter, but the scope injects no useDataInvalidation. The remount used to re-run the author's effects after a page action, and nothing will once it is gone.

Direction (the seat's ruling on objectui#10519 records it; for triage to grade)

• Members 1 and 2, the objectui#10623 / finding(plugin-tree,plugin-dashboard): object-tree, object-pivot and object-data-table do not re-read on the data-invalidation bus — once PageView stops remounting (objectui#10519), a page action leaves them stale #10778 / finding(plugin-form,components): object-master-detail-form's edit-mode detail lines and element:record_picker's options have no bus reader — both refresh after a page action only through PageView's remount (the fifth batch; blocks objectui#10519) #10853 shape.
  • Each read takes the useDataInvalidation nonce for the object it queries: ObjectView's non-grid fetch keys on schema.objectName, and SelectFilter's options key on from.object.
  • ⛔ No second channel, and no remount.
  • The filter keeps its selected value across the re-read, the way the picker's re-read keeps the bound value.
• Member 3, by measurement.
  • If any shipped or taught react page (examples, docs, skills) reads data through useAdapter, inject useDataInvalidation into the react-page scope. That is the canonical bus, not a second channel; teach it in the react-page guide; and treat it as Clause-②: yes, since the scope widens.
  • If none does, inject nothing, and the react-page guide states that a react page's own reads are not refreshed by page actions.
• Pins: one bus event re-reads each block once, in place, with no remount (the objectui#10519 census shape), plus a lit control.
• Serial: member 1 edits plugin-view/src/ObjectView.tsx, which PR objectui#10884 (seat 4, objectui#10758) holds. It dispatches after that PR, or edits only outside its hunks.

Dedupe

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

• optionsFrom / DashboardFilterBar / SelectFilter near bus, invalidat, re-read or refresh;
• react page near useDataInvalidation, bus or re-read;
• ObjectView near non-grid, useDataInvalidation or bus reader.

Three hits, all closed and none a carrier: objectui#10688, #5861 and #10533.

Dedupe words: object-view kanban bus reader page action · dashboard optionsFrom filter options stale · react page useDataInvalidation scope · PageView remount sixth batch readers

[objectstack-fleet]

Path: studio · 自定义页面:块组合、页面变量与页面级动作、三档源码 | studio-authoring.page-variables-and-actions (its steps do not reach a non-grid object-view or a dashboard filter's options after a page action) | P1

Triage: first grade — bug · priority:p2 · domain:ui · area:studio · pm:queue (finding removed)

Triage: lands in packages/plugin-view/src/ObjectView.tsx (the non-grid fetch) and packages/plugin-dashboard/src/DashboardFilterBar.tsx (SelectFilter) ⇒ domain:ui.

• On objectui origin/main 4f38f39 at 2026-09-28T03:53Z, both files have 0 useDataInvalidation hits.
• Lit control: plugin-dashboard/src/DatasetWidget.tsx imports it.

Rationale: this is the reader batch objectui#10519 is Blocked-by: (seat ruling 5862691924, decision B 「readers first」). It is a wall in front of a p2 landing, not a tax ⇒ p2, the same grade as its predecessors objectui#10623 and objectui#10853.

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

Duplicate check. The body's open-and-closed query stands. This seat's query over 2,371 objectui items updated since 2026-09-10T00:00Z: optionsFrom|DashboardFilterBar|SelectFilter|non-grid|react page together with useDataInvalidation|bus|invalidat|re-read|remount gives 13 hits, all closed. None is a carrier. objectui#10688 and PR objectui#10837 are the nearest, and both are earlier batches.

Serial constraint. PR objectui#10884 (objectui#10758, in flight) holds ObjectView.tsx. Claim after it lands, or declare its hunks in the claim and edit outside them. Member 2 (plugin-dashboard) is independent of it.

Member 3 (kind: 'react' pages): one boundary. Injecting useDataInvalidation into the react-page author scope widens a public surface.

• Under the charter's mechanical boundary test (扩大接受集或公开面 ⇒ 人工), that is not a seat's or triage's call.
• If the measurement lands in that branch, the claimant reports needs_decision, and the question goes to the decision box.
• The other branch is inside the seat's call: no shipped or taught react page reads through useAdapter, and the guide states that page actions do not refresh a react page's own reads.

[objectstack-fleet]

Claim: PM loop round 10 — domain:ui execution seat 2
Session: session_014mXUNuFomfj24w7s1pZzhN
Branch: claude/issue-10887-bus-readers-sixth-batch
Worktree: objectui-issue-10887
Domain: domain:ui
Seat: domain:ui#2
File surface, per triage 5863050549 and the seat ruling 5862691924 on objectui#10519 (decision B, 「readers first」):

• packages/plugin-view/src/ObjectView.tsx: member 1. The non-grid fetch effect (its dependency list naming schema.objectName, dataSource, currentViewType and refreshKey) takes the useDataInvalidation nonce for schema.objectName. The edit stays OUTSIDE PR objectui#10884's hunks, which all sit in renderContent from its first hunk at base line 2426 onward.
• packages/plugin-dashboard/src/DashboardFilterBar.tsx: member 2. SelectFilter's optionsFrom read keys on the nonce for from.object, and the selected value survives the re-read.
• Member 3, the kind: 'react' page scope: measured first. If no shipped or taught react page reads data through useAdapter, the react-page guide states that a react page's own reads are not refreshed by page actions. If one does, the scope widening is a public surface, so it stops with needs_decision for the decision box, per triage.
• Tests beside these, and one .changeset/10887-…md per touched published package.
• ⛔ Not PageView.tsx (PR objectui#10777), and not ObjectView.tsx's renderContent region (PR objectui#10884).
  Container & model: M, mode:subagent, model: opus (default judgment tier)
  Clause-②: no
  Why no: members 1 and 2 add a re-read on the canonical bus to two existing readers and change no declared contract. Member 3 either documents a limitation or stops at needs_decision before any scope widening.
  Thread-read: 5863050549
  Serial constraints cleared:
• I read the open-PR file lists at 2026-09-28T04:2xZ, at objectui origin/main 4f8b7f86a. PR objectui#10884 (seat 4, objectui#10758) holds ObjectView.tsx in renderContent only; member 1's effect sits far above its hunks, as triage allows. PR objectui#10892 touches plugin-dashboard/src/ObjectPivotTable.tsx, not DashboardFilterBar.tsx. No open PR touches DashboardFilterBar.tsx.
• If another seat claims at the same time, the earliest live claim wins and this seat yields.

[objectstack-fleet]

os-dev-report
{
"issue": 10887,
"status": "needs_decision",
"branch": "claude/issue-10887-bus-readers-sixth-batch",
"pr": "#10898",
"session": "session_014mXUNuFomfj24w7s1pZzhN — mode:subagent, the dispatching seat 2 session (the order names it as this run's id)",
"premise_still_valid": true,
"summary": "Members 1 and 2 are implemented in draft PR objectui#10898 (base 35d68c4, head 56354a1): ObjectView's non-grid fetch effect names the useDataInvalidation nonce for schema.objectName, and SelectFilter's optionsFrom options effect names it for optionsFrom.object; both reproduced on base through the real SchemaRenderer (1 read after '' and after the own object, expected 2) and pinned red on base, green on head, with per-member ablations. Member 3 stops at needs_decision: 2 of the 3 shipped kind:'react' pages (objectstack app-showcase showcase_crm_workbench and showcase_renewals_pipeline) and the objectui react-pages guide read data through the injected useAdapter, so injecting useDataInvalidation widens a public surface; the PR body opens with 'Part of #10887' and nothing in the react-page scope or guide is changed. One premise narrowed: the card lists tree among the fetch-driven views, but ObjectTree runs its own query ahead of the rows handed to it and reads the bus itself, and ObjectChart never reads the rows, so member 1 does not subscribe for the host-only tree and chart (pinned, ablation 3). Card assignee found as os-elon-musk (not written); PR objectui#10884 had already merged as this branch's base 35d68c4 before the dispatch, so the serial constraint was moot (merge-tree against its head 5dc80e3 clean).",
"tests": "H1 base (35d68c4 sources, committed pins): pnpm exec vitest run ObjectView.busReread-10887.test.tsx DashboardFilterBar.busReread-10887.test.tsx — Tests 17 failed | 6 passed (23); failures quoted: "the rows never re-read after the bus reported a change: expected vi.fn() to be called 2 times, but got 1 times" (kanban, calendar, gallery, timeline, map, gantt) and "the options never re-read after the bus reported a change: expected vi.fn() to be called 2 times, but got 1 times" (dataset and find reads); the 6 passing are the controls (no-object view, no-optionsFrom filter, host tree, host chart, grid object-view lit control, object-metric lit control). Base sources restored with git checkout HEAD --, both blobs equal HEAD (b3891b799c28, 010cd9583f21), git diff HEAD empty. || Head 56354a1: same two files — Tests 23 passed (23). || Ablation 1 (ablation-replace, anchor "invalidationNonce," x1 to x0, ObjectView.tsx blob b3891b799c28 to c34f82f03168): Tests 12 failed | 11 passed (23), only member 1 rows (6 view types x 2); restored blob == HEAD, git diff HEAD empty. || Ablation 2 (anchor ", invalidationNonce]);" x1 to x0, DashboardFilterBar.tsx blob 010cd9583f21 to fc5840bb7e96): Tests 5 failed | 18 passed (23), only member 2 rows; restored blob == HEAD. || Ablation 3 (anchor " && currentViewType !== 'tree' && currentViewType !== 'chart'" deleted, blob b3891b799c28 to 5c07b14a7e4e): Tests 2 failed | 21 passed (23), only the host-composed tree and chart controls (find 1 to 2 each); restored blob == HEAD. No dist between mutation and run: the pins import subjects by relative path and @object-ui/react through the root vitest alias. || plugin-view suite under the verify lock at a70c760 (sources identical to head; later commits touch only the two pin files, re-run at head): Test Files 53 passed (53), Tests 527 passed (527). || plugin-dashboard suite under the verify lock at a70c760: Test Files 147 passed (147), Tests 1339 passed | 6 skipped (1345). || Consumer sweep, 9 render-level consumers outside the two packages in one run: Test Files 9 passed (9), Tests 657 passed (657) — timelineAxisRefusalReach-7070, catalog-gallery-render, plugin-dashboard-gallery-render, rowClickModifierPayloadForward-9462, ObjectView.densityModeThroughFold-7924, ViewPreview.optionsFold-7928, StudioDesignSurface.gridRefresh, DashboardWidgetInspector, DashboardDesignPage.presetAlias. objectui#10519 census test on main: none (0 test files under apps/ or packages/app-shell name 10519 at base and at origin/main 6a7f24e; control: 11 reader pins under packages/ at base). || type-check at head: pnpm --filter @object-ui/plugin-view --filter @object-ui/plugin-dashboard run type-check — echoed "tsc --noEmit && tsc -p tsconfig.test.json" for both, "Done" x2, exit 0 (after the turbo build of both ^... closures, 16 tasks successful). The first run went red on the new pin (TS2493, untyped vi.fn call tuple), repaired in a70c760.",
"gates": [
"head 56354a1, each exit 0: check:control-bytes (OK, 9160 files) · check:new-line-citations (VERDICT new-cross-file-line-citations: 0 new citation(s)) · check:phantom-deps (Every in-scope import is declared) · check:unused-deps · check:test-path-roots · check:changeset-claims (5 pending changesets name ObjectView.tsx: the 6726 records-arm table, the gantt route notes, the title retirement, the viewTabBar reading; none is falsified by this change) · check:pending-changeset-literals · check:shell-escape-residue · changeset:check (no major) · check-changeset-presence (4 source files of 2 released packages, 2 changesets declared)",
"check-governed-queue-guard --test over the 6 changed paths: NOT GOVERNED",
"ESLint --no-inline-config --format json over the 4 changed files: 4 files, 0 errors; pins 0 warnings; ObjectView.tsx 60 and DashboardFilterBar.tsx 18 warnings, identical per rule on the base blobs (stdin-filename). Narrowed run: root config has no type-aware linting (no parserOptions.project / projectService), so the diff cannot move an untouched file. pnpm lint is CI's: NOT MEASURED locally.",
"Serial: git merge-tree --write-tree head x PR objectui#10884 head 5dc80e3: clean (exit 0); head x origin/main 6a7f24e: clean. ObjectView hunks: the @object-ui/react import, the hook above the non-grid fetch effect, and that effect's dependency list, all above renderContent.",
"CI: in_progress (not awaited, per the role file)."
],
"files_changed": [
"packages/plugin-view/src/ObjectView.tsx",
"packages/plugin-view/src/tests/ObjectView.busReread-10887.test.tsx",
"packages/plugin-dashboard/src/DashboardFilterBar.tsx",
"packages/plugin-dashboard/src/tests/DashboardFilterBar.busReread-10887.test.tsx",
".changeset/10887-object-view-non-grid-bus-reader.md (@object-ui/plugin-view patch, Clause-② no)",
".changeset/10887-dashboard-filter-options-bus-reader.md (@object-ui/plugin-dashboard patch, Clause-② no)"
],
"deviations": [
"Member 1 does not subscribe for the host-only tree and chart, although the card lists tree among the fetch-driven views: ObjectTree queries for itself ahead of the handed rows and re-queries when that array changes, ObjectChart never reads them, and both read the bus themselves; subscribing would add a read per event (ablation 3 measures find 1 to 2). Gantt is subscribed (it draws non-empty host rows).",
"The inner non-grid views in the member-1 pins are stand-ins registered in the real registry; the object-view itself goes through the real SchemaRenderer and plugin-view's registration. plugin-view does not declare plugin-kanban / plugin-calendar, and check:phantom-deps judges test imports against the package's own declarations.",
"H1 lit control is three-fold: the bare useDataInvalidation reader, a grid object-view (ObjectGrid) and an object-metric block; all green on base and head.",
"The PM write tools and ablation-replace ran from objectstack origin/main 862b6ce869 extracted with git archive into this issue's scratch dir: the shared objectstack checkout (5581d3000f) lags origin/main in scripts/pm (post-stamped, dispatch-gates, check-governed-queue-guard, record-recognisers). The verify lock ran from the shared checkout path, as objectui AGENTS.md names it. The write-pace ledger is in the home dir, so pacing is shared either way.",
"objectui has no dispatch-gates.mjs; the gate list was derived by hand from objectui package.json check: scripts for the touched file kinds.",
"The first ablation attempt exited 1 with ERR_MODULE_NOT_FOUND (invoked-as.mjs not yet copied): not a measurement, re-run after copying.",
"The member 3 census reads the sister repo objectstack (examples/app-showcase, content/docs, skills) at origin/main: that is where every shipped react page lives; objectui ships none under examples/."
],
"mcp_calls": "0 — no MCP GitHub tool called.",
"api_writes": "3 — (1) pr_create through the fleet relay: POST /repos/objectstack-ai/objectstack/dispatches, run https://github.com/objectstack-ai/objectstack/actions/runs/36380905999 success, executed POST /repos/objectstack-ai/objectui/pulls (draft) = objectui#10898, body read back byte-identical (12518 bytes, 0 angle brackets); (2) label-write --issue 10898 --assign os-elon-musk through the relay: POST /repos/objectstack-ai/objectstack/dispatches, run https://github.com/objectstack-ai/objectstack/actions/runs/36381007734 success, executed the assignees write on objectui#10898, read back MATCHES (assignee os-elon-musk, labels plugin, tests unchanged); (3) this os-dev-report comment via post-stamped: POST /repos//issues/10887/comments. git push (not REST) to claude/issue-10887-bus-readers-sixth-batch, 6 pushes including the empty-branch probe.",
"open_questions": [
{
"question": "Member 3: inject useDataInvalidation into the kind:'react' page author scope (beside useAdapter)? Measured: 3 shipped react pages (objectstack examples/app-showcase), 2 read data through useAdapter in effects (showcase_crm_workbench: KPI strip adapter.find('showcase_project', { $top: 200 }) keyed on its own reloadKey, bumped only by its own ObjectForm onSuccess; showcase_renewals_pipeline: two adapter.find reads keyed on the selected account), showcase_task_desk none; taught in the objectui react-pages guide (Live data, keyed on [adapter]; useAdapter().findOne in the record-family table), objectstack content/docs/ui/react-pages.mdx and skills/objectstack-ui/rules/pages.md. Lit control: useAdapter hits the scope injection site 7 times. Once PR objectui#10777 drops the PageView remount, nothing re-runs these reads after a write the page does not observe itself (an action run inside an injected block, a flow).",
"options": [
"A — inject useDataInvalidation into ReactKindPage's scope (the canonical bus, no new mechanism), teach it in the objectui react-pages guide's Live data example (the nonce in the effect's deps), pin it through a real react page (one re-read on '*', lit control), Clause-② yes. Follow-ups outside this repo: the react-tier scope line in objectstack docs/skills (react-pages.mdx, rules/pages.md, references/react-blocks.md) and the two showcase pages opting in. Four axes: business need — serves 2 measured shipped readers and the taught pattern; long-term — writers declare, readers read, the same hook every renderer uses, no workaround; AI errors — the canonical example becomes correct by default, though a page that omits the nonce still goes stale silently (nothing enforces it); startup focus — widens the scope by one identifier plus a cross-repo docs/skills sync, backed by a measured pull, no new gate.",
"B — inject nothing; the objectui guide (and the objectstack docs/skills) state that a react page's own useAdapter reads are not refreshed by page actions, and name what exists instead: read through the injected blocks (ListView, ObjectChart, Block type object-metric), which re-read on the bus themselves, or re-read in the page's own handlers as showcase_crm_workbench does after its own onSuccess. Four axes: business need — leaves the 2 shipped reads stale after unobserved writes once the remount goes; long-term — the trusted tier stays the one reader class outside the bus, held by prose; AI errors — correctness depends on reading a limitation sentence, and the failure is silent staleness; startup focus — zero scope growth, docs only."
],
"recommendation": "A, because the pull is measured (2 of 3 shipped react pages and the taught Live data example read through useAdapter), it reuses the canonical bus rather than adding a channel, and it makes the taught example correct by default. The startup-focus axis leans the other way (B grows nothing): that trade-off is the maintainer's. Triage 5863050549 marks the scope widening as outside the seat's call."
}
],
"out_of_scope_findings": [
"carrier: none · noted, not filed — renderContent's identityKey comment still says the data-fed views re-read "when refreshKey moves"; now incomplete (they also re-read on the bus), not false; in the region this order said not to touch. In PR Acceptance notes.",
"carrier: none · noted, not filed — ObjectView still runs its non-grid fetch on mount and on refreshKey for the host-only tree and chart, whose renderers do not draw those rows: a read nobody uses, pre-existing, not grown by this change. In PR Acceptance notes."
]
}

---

Generated by Claude Code

[objectstack-fleet]

维护者速读 · decision box: member 3 of this card (the kind:'react' page scope) · domain:ui seat 2 · 2026-09-28T05:2xZ

session_014mXUNuFomfj24w7s1pZzhN. Members 1 and 2 are in draft PR objectui#10898 (Part of #10887), which is in contract review. Member 3 stopped at needs_decision, as triage 5863050549 required: injecting a hook into the react-page author scope widens a public surface (扩大公开面 ⇒ 人工), so neither the seat nor triage can decide it.

The question. Should the kind:'react' page author scope inject useDataInvalidation beside useAdapter, so a react page's own reads can re-run after page actions once PR objectui#10777 removes PageView's remount?

Measured (dev report on this card):

• 2 of the 3 shipped react pages (objectstack examples/app-showcase: showcase_crm_workbench, showcase_renewals_pipeline) read data through useAdapter in effects. Neither re-reads after a write it does not make itself.
• The objectui react-pages guide teaches the same pattern ("Live data", keyed on [adapter]), as do objectstack's react-pages.mdx and skills/objectstack-ui/rules/pages.md.

Options:

• A (recommended). Inject useDataInvalidation (the canonical bus, no new mechanism).
  • Teach it in the guide's Live data example (the nonce in the effect's dependencies), and pin it through a real react page. Clause-②: yes.
  • Follow-ups in objectstack: the docs and skill scope lines, and the two showcase pages opting in.
  • For: it serves 2 measured readers and makes the taught example correct by default.
  • Against: +1 identifier in the scope plus a cross-repo docs sync, and a page that omits the nonce still goes stale silently.
• B. Inject nothing. The guide and the objectstack docs state that a react page's own useAdapter reads are not refreshed by page actions, and point to the injected blocks (which re-read on the bus) or to re-reading in the page's own handlers.
  • For: zero scope growth.
  • Against: the 2 shipped reads go stale after unobserved writes once the remount is removed, and correctness depends on a prose sentence.

Consequence for objectui#10519: it stays Blocked-by: #10887 until member 3 is decided and landed (A) or documented (B).

_{domain:ui seat 2 · decision box · 2026-09-28T05:2xZ}

[objectstack-fleet]

✅ ACCEPT: PR objectui#10898 (Part of, members 1 and 2) at 56354a1c3; ready and auto-merge follow this ACCEPT

domain:ui seat #2, session_014mXUNuFomfj24w7s1pZzhN. I checked this against the diff and CI, not against the reports' own account.

• Claim 5863277782. It executes triage 5863050549.
• Dev report: the newest os-dev-report on this card.

Implemented-by:  claude/issue-10887-bus-readers-sixth-batch
Reviewed-by:     session_014mXUNuFomfj24w7s1pZzhN

item	reading
the change	ObjectView's non-grid fetch (kanban, calendar, gallery, timeline, map, gantt) and SelectFilter's optionsFrom options now re-read on the useDataInvalidation bus. tree and chart are excluded because they read the bus themselves
review	contract review PASS at 56354a1c3 (posted with this landing). Its non-blocking notes ride this card: (a) a zero-row gantt keeps its own reader, so the changeset's "switches off" is imprecise for that case; (b) the view-type deny-list; (c) the calendar loading flash on re-read; (d) the identityKey comment
changesets	patch for plugin-view and plugin-dashboard
serial	git merge-tree clean against main
CI	head 56354a1c3: every check final and green before ready (this landing waits on it)
closing keywords	Part of #10887 only. Member 3 (the react-page scope) is needs-user-decision, so the card and objectui#10519's block stay open until it is decided