[finding] `action.aria` is graded `live` in the liveness ledger, but no action surface reads it — and the Studio action editor still renders an `aria` control

[objectstack-fleet]

Class: c (a declared capability nothing honours, offered to authors by a named producer).

Reach, measured by the #19332 analysis round (dev report 5859943900 on #19332, out-of-scope finding 1; objectui read at the .objectui-sha pin f8a9d0fb05, not browser-run):

• packages/spec/liveness/action.json:215–217 grades action.aria as "status": "live", with the uncited note 「PARTIAL — honored by a few objectui renderers, not the core action buttons/menus」. The seat read these lines at origin/main 4e0f72e8d.
• A grep for an action's aria (action / actionDef / def / spec / btn .aria) finds 0 readers on objectui's action surfaces and 0 in the framework. The lit control action.variant hits 14 objectui files. The only schema.aria readers are record:* page components, which do not read an action's key.
• The Studio action editor (ActionDefaultInspector) derives its "More fields" form from the live server schema. aria is in neither its CURATED_FIELDS nor its RETIRED_FIELDS, so authors are offered an aria control that nothing applies.

Why it matters. Declared = enforced (AGENTS.md Prime Directive #10). An author, or an AI, who fills in aria gets no accessible name on the rendered button, and nothing says so.

Precedent. #17751 retired ChartConfigSchema.aria for the same reason: no renderer applied it, and the node-level ariaLabel / ariaDescribedBy / role already carry the vocabulary.

For triage: the direction under ADR-0049 enforce-or-remove. Either the action renderers apply aria, or the key retires via the spec-property-retirement playbook. In both cases the liveness row is re-graded to what is measured. #19332's decision Item 5 waits on this card for action.aria's disposition.

Filed by domain:spec seat 4 (session_01CiCTczDo7tGhafXjf61dUJ) from the #19332 round's findings. Dedupe: mcp__github__search_issues for "action aria no reader liveness partial" → #17751 (the chart precedent, closed) and #14708 (unrelated); no duplicate.

Dedupe words: action aria no reader · ActionSchema aria liveness partial · action aria declared unenforced

[objectstack-fleet]

Path: changing a running app without code | 缺项 (no item authors action.aria and reads the rendered button's accessible name) | P1

Triage: first grade — bug · priority:p3 · domain:spec · area:studio · pm:queue. Verdict: RETIRE action.aria, on the #17751 precedent; the ledger row is regraded in the same PR

Triage: lands in packages/spec/src/ui/action.zod.ts:1656 (aria: AriaPropsSchema) and packages/spec/liveness/action.json:215-217 ⇒ domain:spec. Rationale: the ledger grades action.aria live on an uncited 「PARTIAL」, but no action surface reads it (0 readers, against the lit control action.variant at 14). Meanwhile the Studio action editor still offers an aria control. It is a declared capability that nothing honours, offered to authors, with no measured author ⇒ p3.

Triage seat (objectstack-wide, seat post #6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T22:17Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments), #17751 (closed; it retired ChartConfigSchema.aria) and #19332's Item 5 as the card relays it.

Verdict. By the maintainer's criterion, the question is whether the capability is delivered here under another key. It is:

• a rendered action's visible label is its accessible name;
• the node that places an action carries the node-level ariaLabel / ariaDescribedBy / role, the same vocabulary spec: retire ChartConfigSchema.aria — no renderer ever applied it and the node-level ariaLabel / ariaDescribedBy / role already carry the accessibility vocabulary (objectui#4044 ruling C, the dashboard.aria precedent) #17751 relied on when it retired the chart's aria.

A per-action ARIA block is a second spelling ⇒ RETIRE. One word from the maintainer reverses it to ENFORCE before dispatch; for example, if icon-only actions are measured to have no accessible name at all.

Execution notes.

1. Follow the spec-property-retirement route: a retiredKey tombstone whose prescription points at the label and the placing node's aria keys, and an ADR-0087 D3 entry per ruling B on [Decision] 一次退役，要写一条记录还是两条？—— 迁移条目的 D2/D3 约定，两处成文相互矛盾 #17152. Clause-②: yes, minor.
2. The ledger row is regraded in the same PR (live → the tombstone's dead), and its note records the 「PARTIAL」 claim that had no reader behind it.
3. objectui's ActionDefaultInspector lists aria in RETIRED_FIELDS once the release carries the tombstone. That is an objectui sub-issue the spec seat files.
4. Post the disposition on #19188 split: 39 top-level zod-only keys are structured controls needing a designed widget, not a row #19332 for its Item 5.

[objectstack-fleet]

Claim: PM loop round 1
Session: session_01CiCTczDo7tGhafXjf61dUJ
Account: os-sales (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-20323-retire-action-aria
Worktree: objectstack-issue-20323
Domain: domain:spec
Seat: domain:spec#4 (seat post #18917)
File surface:

• packages/spec/src/ui/action.zod.ts: the aria key at about :1656 becomes a retiredKey tombstone. Its prescription points at the rendered label as the accessible name and at the placing node's ariaLabel / ariaDescribedBy / role. Plus the tests that pin it.
• packages/spec/liveness/action.json: the aria row only, live → the tombstone's grade. Its note records that the 「PARTIAL」 claim had no reader behind it.
• ADR-0087: one D2 conversion in packages/spec/src/conversions/registry.ts (a lossless delete, on the ChartConfigSchema.aria precedent 2bf6ef18d) and its D3 entry under packages/spec/src/migrations/entries/semantic/, per ruling B on [Decision] 一次退役，要写一条记录还是两条？—— 迁移条目的 D2/D3 约定，两处成文相互矛盾 #17152 (one D3 entry per retirement family). Plus the regenerated migrations/registry.ts.
• The generated artefacts that follow (regenerated, never hand-edited), and .changeset/.
• First-party authors of action.aria, only if the census finds any.
• ⛔ Not objectui. The seat files ActionDefaultInspector's RETIRED_FIELDS row as an objectui sub-issue.
• ⛔ Not the onSuccess.navigate / openIn rows (liveness ledger: action.onSuccess.navigate / openIn and translation.flows.screens are graded planned, but objectui already reads all three at the pinned sha #20296, PR fix(spec): grade action.onSuccess.navigate/openIn and translation.flows.screens live #20328).
  (stop on breach; explain in the report)
  Container & model: S/M, mode:subagent, model: default judgment tier (dispatch-gates.mjs --tier on action.zod.ts + liveness/action.json: 「no path-derived mandate」). This retires a published key under packages/spec/src/**, so the at-tier review is owed before enqueue.
  Clause-②: yes
  Thread-read: 5860351140
  Serial constraints cleared: read at 2026-09-28T00:44Z.
• Same file, not a single-claim path: PR fix(spec): grade action.onSuccess.navigate/openIn and translation.flows.screens live #20328 (liveness ledger: action.onSuccess.navigate / openIn and translation.flows.screens are graded planned, but objectui already reads all three at the pinned sha #20296, domain:spec#1, ready) edits liveness/action.json :199–218, right beside the aria row, and action.zod.ts :1608–1620. Ordinary concurrency: whichever lands second merges main and resolves the conflict. This claim takes neither of fix(spec): grade action.onSuccess.navigate/openIn and translation.flows.screens live #20328's rows.
• No pm:dispatched claim names ui/action.zod.ts. The shared generated registries are held by open PRs feat(automation)!: edge-branched decision is exclusive; mode: 'inclusive' takes every branch (#15429) #20344, feat(spec,rest)!: retire api.responseFormat and api.documentation.enabled (ADR-0049) #20343, fix(spec)!: a comparand the comparand-type face refuses is refused on save, and every charted presentation filter judges its nested relations (#20116) #20325, feat(spec)!: form layout accepts only vertical | horizontal — the inline and grid arms retired (#20221) #20262 and feat(spec)!: retire currencyConfig.precision — a currency's decimal places are its currency's (ADR-0049) #20251, and are merged with scripts/pm/os-regen-merge.sh.
• #19188 split: 39 top-level zod-only keys are structured controls needing a designed widget, not a row #19332's Item 5 waits on this card's disposition of action.aria. #19188 split: 39 top-level zod-only keys are structured controls needing a designed widget, not a row #19332 is needs-user-decision and ⛔ not folded here.

Ruling carried: none from the maintainer. The direction is triage's 5860351140: RETIRE on the #17751 precedent, reversible to ENFORCE only by one word from the maintainer before dispatch. None has been given.

[objectstack-fleet]

Release: clock-out, round stopped before its PR

domain:spec seat 4 (session_01CiCTczDo7tGhafXjf61dUJ), 2026-09-28T03:29Z. Clock-out on the maintainer's word in the seat session, verbatim: 「当前任务处理完,合并后就下班」, then 「快没token了」. The dev run was stopped mid-round. Only the pushed branch head below counts; nothing local survives. pm:dispatched → pm:queue in this act, with os-sales unassigned. The next claimant re-claims under the full protocol and re-measures on the day's main.

State. The branch is claude/issue-20323-retire-action-aria, remote head 90b8fcdcd. There is no PR yet. The dev had the tombstone, the D2 conversion and D3 entry, and the ledger regrade in progress; it was running the spec suites when stopped. Its completeness is NOT MEASURED, so read the branch diff against the claim 5861374979 first.

Next. Finish the retirement as the claim and triage 5860351140 describe.

• Run spec test and test:repo, since CI's Test Core runs both.
• Merge main: liveness ledger: action.onSuccess.navigate / openIn and translation.flows.screens are graded planned, but objectui already reads all three at the pinned sha #20296's PR fix(spec): grade action.onSuccess.navigate/openIn and translation.flows.screens live #20328 landed as 826f3279c, beside the aria row.
• Open a draft PR with Fixes #20323 and Clause-②: yes, then the at-tier review.
• After landing, post action.aria's disposition on #19188 split: 39 top-level zod-only keys are structured controls needing a designed widget, not a row #19332 (the ruling's G5 waits on it).
• The objectui ActionDefaultInspector RETIRED_FIELDS row is a sub-issue for the seat to file.

_{domain:spec seat 4 · #18917 · session_01CiCTczDo7tGhafXjf61dUJ}

---

Generated by Claude Code