[spec] Retire three zero-reader UI keys per maintainer ruling: PageHeaderProps.icon, PageCardProps.actions, RecordDetailsProps.layout (objectui#3829 / objectui#3818)

[os-project-manager]

Maintainer ruling 2026-08-09 (decision-inbox round, 「全部接受」): objectui#3829 ruled route (c) — retire PageHeaderProps.icon and PageCardProps.actions upstream; objectui#3818 ruled the removal direction — retire RecordDetailsProps.layout. All three are spec-declared keys with zero renderer read points measured in objectui (see those cards for the full evidence), making them the ADR-0049 declared-but-unenforced shape on the platform contract.

Deliverable (spec-property-retirement playbook, one PR)

For each of the three keys, in packages/spec:

1. retiredKey() tombstone (prescription sentence per the [finding][spec] Tombstones over STRIP-only conversions say os migrate meta --from 16 will "rewrite it" — the corpus is split between two verbs for one behaviour #6856 ruling: to rewrite existing sources automatically.);
2. protocol-17 conversion (all three are authorable page/component metadata — stored sources must convert; RecordDetailsProps.layout additionally had published auto|custom semantics that were never implemented, so its conversion is a pure strip);
3. ADR-0087 registry entries; regenerate baselines / forms / reference docs; liveness-ledger discipline per the playbook.

Precedent: #3809 (PageCardProps.body) — same objects, same shape.

Sequencing

• objectui#3829 (drop the two parity-gate exemptions) and objectui#3818 (delete the layout input + the dead inline|compact branch) are Blocked-by this card and proceed on the next objectui pin bump after it lands.
• ⚠️ The ADR-0087 registry edits make the implementing PR maintainer-merged only per the standing docs/adr/** discipline — no auto-merge, no agent queue entry.

No domain:* applied — routing is the triage seat's. (Expected lane: domain:spec.)

Refs: objectui#3829, objectui#3818, #3809, ADR-0049, ADR-0087.

[os-zhuang]

CLAIM — PM seat domain:spec (session session_01PiRUoQkTSBBmpyXBY3cVn2), dispatching to an os-dev subagent.

• Branch: claude/issue-6946-retire-three-ui-keys
• Worktree: ../objectstack-issue-6946 (per-task, PD Migrate documentation site to Fumadocs with monorepo structure and shared content #11)
• Dispatch basis: the maintainer ruling recorded in the card body (2026-08-09 decision-inbox round, 「全部接受」): objectui#3829 route (c) retires PageHeaderProps.icon + PageCardProps.actions upstream; objectui#3818 retires RecordDetailsProps.layout. Playbook per the body: tombstones ([finding][spec] Tombstones over STRIP-only conversions say os migrate meta --from 16 will "rewrite it" — the corpus is split between two verbs for one behaviour #6856 house sentence), protocol-17 conversions (layout's is a pure strip), ADR-0087 registries, baselines/forms/docs regen, liveness discipline. Precedent fix(filters): evaluate {token} placeholders on the server read path (#3582) #3809.
• Routing note: the card carried no domain:* (body: "Expected lane: domain:spec"); the seat stamps domain:spec while claiming under today's maintainer batch-acceleration instruction — recorded here for the triage seat's audit.
• Landing-mode note: the body's ⚠️ says the ADR-0087 registry edits make the PR maintainer-merged only. Today's precedents refactor(spec)!: api is code-only — withdraw a runtime create door the endpoint matcher could never read (#5488) #7040/refactor(spec,objectql)!: retire AggregationNode.distinct — one face honoured it, five ignored it, and the same query answered two plausible numbers (#6815, ADR-0049) #7051 (registry-code-only retirement PRs) landed via the normal agent queue with all checks green — the PD feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14 discipline covers docs/adr/** files. The dev will report whether the diff touches docs/adr/**: if yes → maintainer hand-merge; if registry code only → the PM will land via the normal serial relay and record these grounds.
• ⚠️ Concurrency: multiple spec devs in flight; generated artifacts overlap — serial landing, no pre-resolution; registries union-keep + recount-from-file (refactor(spec)!: ADR-0049 退役 sweep —— server 运行期词表 / ViewProtocol / L2 ETL(#5295 #6239 #6414) #6526).

---

Generated by Claude Code

[os-zhuang]

PM bookkeeping: pm:dispatched → pm:queue. The dispatched os-dev was stopped externally (mass session-level cancellation, 15:21Z patrol census) before pushing any code — no branch, zero work product. Claim released; card returns to the queue intact. The maintainer ruling (retire the three keys) and the brief (incl. the mandatory self-run zero-reader verification and the docs/adr landing-mode report) remain valid; re-dispatch awaits the maintainer's word.

---

Generated by Claude Code

[os-zhuang]

RE-CLAIM — PM seat (session session_01PiRUoQkTSBBmpyXBY3cVn2), re-dispatched as a mode:cloud card under the maintainer's re-acceleration (2026-08-09 chat). Branch claude/issue-6946-retire-three-ui-keys. All constraints of the 13:37Z claim comment remain binding — especially the mandatory self-run zero-reader verification (the #6926 lesson) and the docs/adr-touch statement that decides the landing mode.

---

Generated by Claude Code