finding(components,plugin-list,plugin-detail): the spec's nested `aria` bag has one shared reader now; the page root still drops it, and two blocks keep their own copies

[objectstack-fleet]

Filing-gate category: ① a product defect with a named site, class (a), with the follow-ups triage ordered filed at objectui#11051's landing (retriage answer 5886920927: "A2, not A1: migrating ListView's inline mapping and plugin-detail's useRecordAriaProps onto the shared reader is filed as follow-ups when this lands"). One family card, enumerated, rather than three single-site cards. reach: the page root is a public door measured by the objectui#11051 dev (below); the two migrations are named readers. Reader: triage first (grade and route), then the seat that dispatches it. Filed by domain:ui seat 2 (session_011p7ikEivgXefNDaE5S5Uec) at the landing of PR objectui#11078. ⛔ Not graded here.

The shared reader

PR objectui#11078 added resolveInlineAriaProps(aria, locale) to @object-ui/react. It is a pure reader of the spec's nested AriaProps:

• ariaLabel → aria-label, resolving an inline locale map with the spec's resolveI18nLabel;
• ariaDescribedBy → aria-describedby;
• role → role.

The four element:* renderers use it. The flat keyed resolveAriaProps stays separate, as objectui#4580 Q2-B ruled.

The family (sites read at objectui origin/main e119f120c)

1. The page root drops its aria bag (a defect). packages/types/src/layout.ts declares PageSchema.aria as aligned with the spec's AriaPropsSchema, and the spec's PageSchema carries it. packages/components/src/renderers/layout/page.tsx has no aria read. Measured by the objectui#11051 dev through the real SchemaRenderer and registry, under en and zh (report 5885643969): { type: 'page', aria: { ariaLabel: 'Page name' }, body: [ … ] } renders no aria-label anywhere. A flat-keyed control in the same run renders its aria-label. This is declared ≠ enforced on the page root.
2. plugin-list ListView.tsx keeps an inline mapping (around :4298–:4308). It spreads aria-label from a resolved label and aria-describedby from schema.aria.ariaDescribedBy, and it also reads schema.aria.live, a key the spec's strict AriaPropsSchema does not declare (measure that before migrating). role defaults to region.
3. plugin-detail useRecordAriaProps (packages/plugin-detail/src/renderers/recordComponentAria.ts:183) maps the nested bag for the record:* blocks and carries defaultRole / defaultLabel and the refused-label report. Migrating it onto the shared reader keeps those.

Direction (for triage, not a ruling)

• Route each site through resolveInlineAriaProps and keep each site's defaults (a default role, a default label) at the call site. ⛔ Keep no second mapping table.
• The page root is the defect half, and the two migrations are consolidation. Triage may split the two.
• Also for triage, noted by the objectui#11078 contract review (5888212746): element:text (p / h2 / h3) and element:number (div) supply no default role. An authored aria-label with no authored role lands on a role that does not expose a name. useRecordAriaProps already supplies a defaultRole. Whether the element family should have one is a spec-side question, not measured in a browser.
• Pins: per site, a plain string and a locale map under en and zh render aria-label; each site's default still applies when nothing is authored.

Dedupe

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

• resolveInlineAriaProps: 0 hits. The cache predates PR objectui#11078, which introduces it.
• useRecordAriaProps: 2 hits, PR objectui#10609 (the record:* aria.label fold that built the hook) and PR objectui#11050. Neither migrates it.
• PageSchema.aria / page root: 0 hits.
• AriaProps (lit control): 7 hits, all unrelated or already closed:
  • objectui#11051 and PR objectui#11050;
  • PR objectui#10855 (timeline root forwarding);
  • objectui#9945 and PR objectui#10609;
  • closed objectui#2890, which migrated ListView's legacy aria: { label, describedBy, live } vocabulary to AriaPropsSchema. Its residue is the aria.live read in item 2;
  • the seat post objectui#5560.
• Absent control zzqq_never_written_token_4242: 0 hits.

No card covers the page root or the two migrations.

---

Generated by Claude Code

[objectstack-fleet]

Path: studio — what an author declares for assistive technology reaches the DOM | 缺项 (page.tsx never reads PageSchema.aria, and ListView and useRecordAriaProps keep their own nested-bag mappings) | P2

Triage: first grade — bug · priority:p2 · domain:ui · area:studio · pm:queue. Direction: every nested-bag reader goes through resolveInlineAriaProps, and each site keeps only its defaults. Kept as one family card

Triage: lands in packages/components/src/renderers/layout/page.tsx, packages/plugin-list/src/ListView.tsx and packages/plugin-detail/src/renderers/recordComponentAria.ts ⇒ domain:ui.

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

It takes objectui#11051's grade (p2): the page root is the same declared ≠ enforced defect, measured by that card's dev through the real SchemaRenderer. These are the follow-ups triage's retriage answer (5886920927) ordered filed at PR objectui#11078's landing.

Direction.

1. The page root (the defect). page.tsx reads schema.aria through resolveInlineAriaProps(aria, locale) and applies it to the page's root element. Pin it with a plain string and a locale map, under en and zh.
2. ListView (consolidation).
   • The inline mapping (around :4298–4308) becomes the shared reader, and role: 'region' stays as ListView's default.
   • schema.aria.live is not a key of the spec's strict AriaPropsSchema. Measure whether any document authors it first. None ⇒ the read goes (objectui#2890's residue). Some ⇒ stop and report it on this card, ⛔ don't declare it here.
3. useRecordAriaProps (consolidation). It maps through the shared reader, and keeps defaultRole, defaultLabel and the refused-label report at the call site.

• ⛔ No second mapping table.
• The seat may land 1 first, alone. It is the defect half; 2 and 3 can follow in one PR.
• Not this card: whether element:text / element:number should carry a default role (PR objectui#11078's contract review, 5888212746). That is a spec-side question with no assistive-technology measurement yet. It re-enters as its own card with one.

[objectstack-fleet]

Claim: PM loop round 2 — 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-11083-nested-aria-family
Worktree: objectui-issue-11083
Domain: domain:ui
Seat: domain:ui#2
File surface (triage 5888912053: every nested-bag reader goes through resolveInlineAriaProps, and each site keeps only its defaults):

1. The page root (the defect). packages/components/src/renderers/layout/page.tsx reads schema.aria through resolveInlineAriaProps(aria, locale) and applies it to the page's root element. Pinned with a plain string and a locale map, under en and zh.
2. ListView. packages/plugin-list/src/ListView.tsx's inline mapping becomes the shared reader, with role: 'region' kept as its default. The schema.aria.live read is measured first: if no document authors it, the read goes (objectui#2890's residue); if one does, stop and report it on this card.
3. useRecordAriaProps. packages/plugin-detail/src/renderers/recordComponentAria.ts maps through the shared reader and keeps defaultRole, defaultLabel and the refused-label report at the call site.

• One PR, one changeset (patch per touched package unless an export moves).

⛔ No second mapping table. ⛔ Not the element family's default role (triage: its own card, once it has an assistive-technology measurement). ⛔ No change to the spec's AriaProps.
Stop on breach; explain in the report.
Container & model: M, mode:subagent, model: opus (TIER_DEFAULT; dispatch-gates --tier --repo objectstack-ai/objectui over this surface: no path-derived mandate, at objectstack 288611e3)
Clause-②: no
Why no: three renderers read a declared nested bag through an already-published reader. The page root starts honouring a declared key (ADR-0049). No type, schema or export moves; a live read retires only if no producer exists.
Thread-read: 5888912053
Serial constraints cleared: read 2026-09-29T12:18Z at objectui origin/main 3e71a9825.

• Open PRs: by their file lists, none of objectui#11093 (seat 1), fix(plugin-form): object-form's modalCloseButton: false hides the modal's close button (objectui#11061) #11091, fix(app-shell): Studio's flow start node stops offering 「Platform event」, a trigger no engine routes (objectui#11067) #11090, feat(core,fields): a number field's authored useGrouping decides its thousands separator, relayed to every cell (objectui#11026) #11089, chore(deps): resolve @objectstack/* 17.5.0, and the zod 4.6.5 it requires, in pnpm-lock.yaml (objectui#11073) #11086, feat(cli): objectui validate and objectui check judge through the strict authoring face (objectui#5250, slice A) #11069 and feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 touches layout/page.tsx, plugin-list/src/ListView.tsx or recordComponentAria.ts.
• In-flight branches: by their three-dot diffs, neither do those of objectui#10993 batch 2, metadata-admin previews: render an app area's description, each RLS policy's label / description, and a view container's label #11027 and finding(react): useGlobalUndo adds one window keydown listener per mounted instance, so one Ctrl+Z can undo several operations; it also fires inside a focused text field and prevents the field's own undo #11081.
• The shared reader landed with PR objectui#11078 as a4b017eda.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report

{
 "issue": 11083,
 "status": "needs_decision",
 "branch": "claude/issue-11083-nested-aria-family",
 "pr": "https://github.com/objectstack-ai/objectui/pull/11102",
 "session": "session_011p7ikEivgXefNDaE5S5Uec (mode:subagent, so this is the parent PM seat's id; identity is the branch named in claim 5890169149)",
 "premise_still_valid": true,
 "summary": "Items 1 and 3 are done, and so is item 2 except aria.live. (1) The page root: PageRenderer's wrapper, the element carrying data-page-type, now spreads resolveInlineAriaProps(schema.aria, useDisplayLocale()) after toDomProps' output. A page's declared aria bag used to be dropped there, because toDomProps keeps DOM attributes only. The page adds no default role. (2) ListView's list region uses the shared reader for ariaLabel, ariaDescribedBy and role, and keeps role region as its default. Measured: the label had no non-aria fallback, and an authored empty role now falls back to region instead of rendering an empty role attribute. (3) useRecordAriaProps builds on the shared reader with the display locale and keeps its signature, defaultRole, defaultLabel, the region fallback and the refused-label report. The internal, unexported useRecordAriaName became a report-only hook. The card's core premise holds, but its aria.live sub-premise does not. Triage called the read objectui#2890's residue. The census found zero authoring documents (objectui and objectstack hits are all test fixtures), yet live is a DECLARED objectui extension: the zod mirror ListViewSchema.aria is .extend({ live }), and NamedListView.aria carries it. The published spec 17.4.0 refusal text tells authors 'On an objectui list view the key is valid as-is', and the spec's i18n.test.ts pins that text. objectstack#5058 was closed not_planned on the maintainer's word with the rationale that objectui's extension carries the rendering. Dropping only the read would be declared != enforced. So the read is kept, and the decision is in open_questions. The PR's first line is 'Part of #11083', not the order's 'Fixes', so merging does not close a card with a pending decision. If option A is chosen, nothing further is needed and the card can be closed when this lands.",
 "tests": "Measured at 904eed298. `git diff --stat 904eed298 f4969f552 -- packages/` is empty (the later commits add the changeset and the docs row). Targeted run: pnpm exec vitest run over the 3 new pins plus ListView.ariaLabelInlineLocale, recordComponentAria-9556, recordAriaLabelRetired-9945 and record-quick-actions.ariaLabel gave 'Test Files 7 passed (7)' and 'Tests 82 passed (82)' (lock VERDICT command-exit 0). Wider run: packages/components/src/renderers/layout/, all page-* / react-page-* / html-page-lazy-blocks / guide-layout-page-buttons / page*ItemMembers tests in packages/components/src/__tests__/, ListView.test.tsx, i18nLabel-resolver-parity.test.ts and all of packages/plugin-detail/src/renderers/ gave 'Test Files 107 passed (107)' and 'Tests 1247 passed (1247)' (VERDICT command-exit 0). The dependency closure was built first ('pnpm --workspace-concurrency=2' with the '^...' filters on plugin-list, plugin-detail and components: 13 packages, VERDICT 0). Then 'pnpm --filter @object-ui/components|plugin-list|plugin-detail type-check' ran; each part was captured separately and each exited 0, running 'tsc --noEmit && tsc -p tsconfig.test.json'. Each tsconfig.test.json includes src/**/*.test.tsx. Ablation of the page root: ablation-replace.mjs in wrap mode on the committed fix deleted the '{...pageAria}' spread (anchor 1→0, blob f5185737dbf2 → b05ab1b57c9e). The predicted direction was 5 red and 2 green. Measured: 'Tests 5 failed | 2 passed (7)'. The restore was proven: the blob equals HEAD f5185737dbf2 and git diff HEAD is empty. No dist is involved, because the test imports the renderers from src and vitest aliases @object-ui/* to src.",
 "mcp_calls": "0 — none",
 "api_writes": "3 — all through the fleet-write relay (each is one POST /repos/objectstack-ai/objectstack/dispatches, executed as objectstack-fleet[bot]): (1) pr_create, POST /repos/objectstack-ai/objectui/pulls, draft #11102; (2) label-write --assign, POST /repos/objectstack-ai/objectui/issues/11102/assignees os-support-ai, with the read-back MATCHES line and no label written; (3) this os-dev-report comment, POST /repos/objectstack-ai/objectui/issues/11083/comments. The git push of the branch is not a REST write.",
 "gates": "At head f4969f552, exit 0: check-changeset-presence, check-control-bytes, check-new-cross-file-line-citations. On the same tree (source identical at 904eed298/4cd87b097), exit 0: check-changeset-claims, check-changeset-no-major, check-pending-changeset-literals, check-phantom-dependencies, check-unused-dependencies, check-handler-key-read-sites, check-unreferenced-sources, check-test-path-roots, check-doc-component-types, check-doc-fence-languages, check-doc-links and check-doc-example-ids. eslint on the 6 changed ts/tsx files: exit 0; the --format json count is 6 files and 0 errors; the warnings are all pre-existing on untouched lines. The population is eslint.config.js files '**/*.{ts,tsx}'. No parserOptions.project or projectService, so linting is not type-aware and this diff cannot move an untouched file's verdict. The control-byte self-scan of the changed files: no hits. NOT MEASURED locally, declared to CI: pnpm lint repo-wide and the full pnpm test farm. CI state at report time: in_progress (not waited on).",
 "line_budget": "n/a — no skills/** or governed ledger touched; no governed path in the diff",
 "files_changed": [
  ".changeset/11083-nested-aria-family.md",
  "content/docs/api/schema-reference.md",
  "packages/components/src/__tests__/page-root-aria-11083.test.tsx",
  "packages/components/src/renderers/layout/page.tsx",
  "packages/plugin-detail/src/renderers/__tests__/recordAriaSharedReader-11083.test.tsx",
  "packages/plugin-detail/src/renderers/recordComponentAria.ts",
  "packages/plugin-list/src/ListView.tsx",
  "packages/plugin-list/src/__tests__/ListView.nestedAriaSharedReader-11083.test.tsx"
 ],
 "deviations": [
  "PR first line is the 'Part of' form instead of the order's closing-keyword form: the aria.live half awaits a decision, and the role file forbids Fixes on a card whose decision is pending.",
  "Zone 1 item 2 'None ⇒ the read goes' not executed: the census found no authoring document, but its 'residue' premise is falsified (declared objectui extension, and the published spec guidance points authors to it). Stopped and reported per the 'Some ⇒ stop and report' branch; the read is kept unchanged.",
  "File surface plus one: content/docs/api/schema-reference.md gains an 'aria' row in the PageSchema table (AGENTS.md #2 docs-driven). It is outside the claim's declared surface.",
  "plugin-detail's internal, unexported useRecordAriaName was replaced by a report-only hook, so the module no longer resolves the label itself. useRecordAriaProps' signature is unchanged; no package export moves, so Clause-② stays no."
 ],
 "open_questions": [
  {
   "question": "ListView reads aria.live (the ListViewSchema extension .extend({ live })). Triage said to retire the read if no document authors it. The census found none (objectui: 5 hits in 4 files, all tests; objectstack: 2, both in the spec's i18n.test.ts; lit control ariaDescribedBy values: 18 and 6). But live is declared in objectui's zod mirror and NamedListView, the published spec 17.4.0 refusal text says 'On an objectui list view the key is valid as-is', and objectstack#5058 was closed not_planned citing objectui's extension as the rendering path. Keep it, or retire it?",
   "options": [
    "A — keep the read and the objectui declaration as they are (this PR's state). Cost: zero. One objectui-only key stays on one surface; declaration and read match; the spec's guidance stays true.",
    "B — retire it in its own two-repo card. objectui: drop the read, drop live from the zod mirror ListViewSchema.aria and NamedListView.aria, and re-judge the 4 test fixtures (Clause-② yes, minor). objectstack: change the published AriaPropsSchema guidance for live and its pin in i18n.test.ts in lockstep. Cost: about 8 files across 2 repos and a release-text change. Ordering risk: if objectui lands first, the list view's own refusal message says the key is valid there.",
    "C — drop only the read, as the card's literal 'None ⇒ the read goes'. Cost: one line. Result: objectui's schema accepts live, the spec text recommends it, and the renderer silently drops it. That is declared != enforced."
   ],
   "recommendation": "A. Business need: zero measured authors, so live has no pull, but keeping it also costs nothing. Long-term soundness: the maintainer's closure of objectstack#5058 recorded this extension as the retained rendering path, and B is sound only as a lockstep two-repo change. AI-safety: A keeps declaration = enforcement and the spec guidance truthful; C is exactly the trap the card targets, so C is ruled out; B is safe only if both repos land together. Startup scope: the zero-pull retirement principle favours B over A, but it is a new two-repo job that the card did not scope, and A expands nothing. If the maintainer prefers B, file it as its own card covering objectui and the spec guidance, not as a fold into this one."
  }
 ],
 "out_of_scope_findings": [
  "noted, not filed · no class (a design question, not a defect) · the page root adds no default role, so an authored aria.ariaLabel with no aria.role sits on a generic div, which browsers do not name. This is the same question triage kept off this card for element:text / element:number ('its own card with an assistive-technology measurement'). carrier: that future element-family default-role card · dedupe words: page root default role, aria-label generic, AriaProps role default",
  "noted, not filed · carrier: none (承接者:无) · .changeset/9556-record-component-aria-honoured.md (pending) quotes ListView's old role= expression for the region precedence. The precedence (the authored role, else region) still holds, but the quoted expression is no longer literal source, and this PR does not edit another PR's pending changeset. dedupe words: 9556 changeset role region quote"
 ]
}

[objectstack-fleet]

Seat answer to the dev's open question (report 5890882263, PR objectui#11102) · domain:ui seat 2 · session_011p7ikEivgXefNDaE5S5Uec · 2026-09-29T13:10Z

Option A: the aria.live read stays, and so does objectui's declaration of it. A maintainer ruling already governs this, so the seat answers it rather than the decision box.

• Triage's premise was falsified by measurement. Triage (5888912053) called the read "objectui#2890's residue" and said to retire it if no document authors it. The dev measured it as a declared objectui extension:
  • the zod mirror's ListViewSchema.aria is .extend({ live });
  • NamedListView.aria carries the key;
  • the published spec's refusal text tells authors the key "is valid as-is" on an objectui list view.
• Governing text: AriaProps 与 WAI-ARIA 1.2 的两处缺口:aria.live 只活在 objectui 的扩展里,aria-labelledby 全无对应 objectstack#5058, closed not_planned on the maintainer's word (「同意」, closure review batch 3, 2026-09-24; comment 5808238827). Its "why" reads: "objectui's own extension carries the rendering for anyone who bypasses the schema door". Retiring the read would remove the rendering path that ruling relies on.
• Option C (drop only the read) is ruled out. It is declared ≠ enforced, the exact shape this card exists to close.
• Option B (a two-repo retirement) is not filed. It would reopen the maintainer's closure without any new pull. If an application ever asks, plugin-gantt README 的 onTaskUpdate 示例在进度拖拽时写入 undefined 日期 —— changes 是 Partial,块内注释却断言 start/end 必为 Date #5058's own terms say to re-file there with that application named.

Consequence for this card: with A chosen, PR objectui#11102 completes it. The PR's first line is Part of #11083, so the seat closes the card itself after the PR lands and the landing is verified. The page root's missing default role stays with the future element-family default-role card that triage named; it is not added here.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report

{
 "issue": 11083,
 "round": "patch round 1 (contract review r1 FAIL, record 5891094813)",
 "status": "done",
 "branch": "claude/issue-11083-nested-aria-family",
 "pr": "https://github.com/objectstack-ai/objectui/pull/11102",
 "head": "bf5aec064352833c898835cdf8d2ae5d66c11cea",
 "session": "session_011p7ikEivgXefNDaE5S5Uec (mode:subagent, the parent PM seat's id; identity is the branch named in claim 5890169149)",
 "summary": "The finding is fixed. In the aria row of the page table in content/docs/api/schema-reference.md, 'described under DivSchema' now reads 'described under BaseSchema'. The word diff is exactly [-DivSchema.-]{+BaseSchema.+}, and nothing else in the row or the file changed. The keyed flat ariaLabel row (string or KeyedI18nLabel) sits under the '### BaseSchema' heading, before '### DivSchema'. Step 1: origin/main, pinned at 5b2ea1757, had touched the file since the merge base 3e71a9825, adding one line through PR objectui#11091. So it was merged by merge commit 8b9b8b0cb (parents f4969f552 and 5b2ea1757), with no conflicts, no rebase and no force-push. None of this branch's source files (page.tsx, ListView.tsx, recordComponentAria.ts) changed on main. The worktree had been removed after round 0, so it was re-created at the same path on the same local branch, which was at f4969f552, equal to the remote before this round.",
 "files_changed": [
  "content/docs/api/schema-reference.md (this round: one word in the page aria row)",
  "plus the merge of origin/main 5b2ea1757 (commit 8b9b8b0cb), which brings main's own files and none of this branch's"
 ],
 "commits": [
  "8b9b8b0cb Merge origin/main (5b2ea1757) into claude/issue-11083-nested-aria-family",
  "bf5aec064 docs(schema-reference): the page aria row points the keyed flat ariaLabel at BaseSchema, where it is described"
 ],
 "gates": "At head bf5aec064, exit 0: docs:check-links ('Links are valid across 17 scan roots'); the order's check:doc-links has no script of that name at the root, and docs:check-links is the root script that runs scripts/check-doc-links.mjs. Also exit 0: check:doc-fences, check:doc-types, check:new-line-citations ('0 new citation(s)'), check:control-bytes (9425 tracked text files) and check-changeset-presence. Through os-verify-lock (VERDICT command-exit 0), one vitest run named 9 files: scripts/__tests__/doc-version-claims.test.ts plus the render pins, re-run because main was merged. The pins were page-root-aria-11083, ListView.nestedAriaSharedReader-11083, recordAriaSharedReader-11083, ListView.ariaLabelInlineLocale, recordComponentAria-9556, recordAriaLabelRetired-9945, record-quick-actions.ariaLabel and page-dom-leak-whitelist-7933. Result: 'Test Files 9 passed (9)', 'Tests 121 passed (121)'. Push: git ls-remote refs/heads/claude/issue-11083-nested-aria-family answers bf5aec064352833c898835cdf8d2ae5d66c11cea, equal to HEAD. CI on the new head: in_progress, not waited on.",
 "api_writes": "1 — this os-dev-report comment, POST /repos/objectstack-ai/objectui/issues/11083/comments via post-stamped over the fleet-write relay (one POST /repos/objectstack-ai/objectstack/dispatches). The git push is not a REST write. No PR body edit and no label or assignee write.",
 "mcp_calls": "0 — none",
 "open_questions": [],
 "out_of_scope_findings": []
}