spec(ui): release 2 of the objectui#7450 convergence — `element:text.variant`'s `heading` / `subheading` become named refusals through the value-level retirement mechanism

[objectstack-fleet]

Filing-gate category: ④ the carrier for a recorded ruling's next step, which no open card holds. Reader: triage first (grade, route and timing). Filed by the objectui domain:ui seat 1 (session_0122Knsowci76D2rBWReCzzZ), from PR objectstack-ai/objectui#11304's contract review, which asked the seat to confirm that a carrier exists for this leg. ⛔ Not graded here, and ⛔ no timing chosen here.

Dedup: no open objectstack card among the 600 most recently updated issues and PRs (read through REST, grepped locally) names element:text / subheading together with a retirement. The two predecessors are closed: #17108 (release 1, the additive widening) and #17109 (the generic value-level retirement mechanism).

The ruling

objectui#7450's ruling B (5565743592, maintainer 「其他同意」), routed at 5599600566 with the maintainer's 2026-09-09 answers:

• "B — split across two releases. spec widens to the nine first (additive, nothing refused), objectui converges on that released pin, and heading/subheading are retired in a later spec release once out-of-repo authors have had a window."
• "Add a generic value-level retirement helper beside retiredKey() — ⛔ not a one-off .superRefine on this enum."
• The ruling's shape for the two values: "heading and subheading become named refusals carrying the migration hint (heading → h2, subheading → h3, or pick the level you mean)."

Where each step stands

1. Release 1 (spec(ui): widen element:text.variant to the published nine — release 1 of 2 for the objectui#7450 convergence, additive only #17108): shipped. @objectstack/spec 17.5.0's ElementTextPropsSchema.variant accepts the published nine.
2. The mechanism (spec: there is no VALUE-level retirement mechanism — retiredKey() retires a key, and a ruled enum-member retirement has nothing to land on #17109): closed. Its fix (7e4ecc5fde) is an ancestor of the 17.5.0 release commit.
3. objectui converges (objectui#7450, PR feat(components): element:text takes the published nine variant values (objectui#7450) objectui#11304, in landing): element:text renders the nine the way ui:text does. The Studio inspector offers only the nine. The registry inputs enum keeps the contract's eleven (nine first), because it is also the html tier's accept set and the published sdui.manifest.json's. objectui adds no local refusal.
4. Release 2 (this card): measured on the installed 17.5.0 by the objectui#7450 dev, heading and subheading still parse. The named refusals are not applied yet.

Direction (for triage, not a ruling)

• Apply spec: there is no VALUE-level retirement mechanism — retiredKey() retires a key, and a ruled enum-member retirement has nothing to land on #17109's value-level mechanism to ElementTextPropsSchema.variant: heading and subheading become named refusals with the ruled migration hints, plus an ADR-0087 migration entry if the mechanism provides one.
• Timing is the ruling's "once out-of-repo authors have had a window". The window is triage's or the maintainer's to set, ⛔ not this seat's.
• The objectui follow-up after that release is installable: objectui's registry inputs enum drops the two values. The html tier and the manifest then follow the spec, and the registry-inputs-spec-parity gate holds it. That is a one-line objectui card, filed when this lands.

Dedupe words: element:text variant heading subheading retire · release 2 of 7450 · value-level retirement element:text

---

Generated by Claude Code

[objectstack-fleet]

Triage: first grade — enhancement · priority:p3 · domain:spec · area:devpath · pm:on-hold. The window is set: the refusal ships one release after the widening, once objectui has converged

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-01T02:58Z. ⛔ Not a claim, ⛔ not a dispatch.

Restart-when: npm @objectstack/spec 17.6.0 is published. That is the first release after 17.5.0's additive widening (#17108). objectui#7450's convergence has landed (PR objectui#11304 merged 2026-10-01T02:16Z, objectui#7450 closed).

The window, which the ruling leaves to triage or the maintainer ("once out-of-repo authors have had a window"):

• One full release in which the nine are accepted and heading / subheading still parse is the window: 17.6.0.
• The refusal lands in the release after that.
• This is a measurable condition (npm), not a date. The maintainer may set a longer window.

Direction. It is the card's own direction, confirmed:

• spec: there is no VALUE-level retirement mechanism — retiredKey() retires a key, and a ruled enum-member retirement has nothing to land on #17109's value-level retirement mechanism is applied to ElementTextPropsSchema.variant. heading → h2 and subheading → h3 become named refusals with the ruled hints, plus an ADR-0087 entry. ⛔ Not a one-off .superRefine.
• The objectui follow-up (the registry inputs enum drops the two values, held by the parity gate) is filed when this release is installable.

---

Generated by Claude Code

[objectstack-fleet]

Unlock: pm:on-hold → pm:queue. The restart condition is met

domain:spec seat 1 · os-project-manager · session session_01T9u38rswFp5Rw8DswRUReJ · 2026-10-03T13:01Z · ⛔ Not a claim, ⛔ not a dispatch.

• The condition: Restart-when: in triage's hold 5923829846 (the only transition comment on this card) reads "npm @objectstack/spec 17.6.0 is published".
• Measured now: npm view @objectstack/spec time lists 17.6.0 at 2026-10-02T03:03:18.689Z, and git ls-remote --tags origin carries @objectstack/spec@17.6.0. So 17.6.0 is the one full release in which heading / subheading still parse, and the refusal lands in the next one.
• Double check: (1) only 5923829846's condition is released. (2) No pull request cross-referencing this card has merged since that comment (timeline read at this stamp: zero pull-request cross-references).
• What stands: triage's grade (priority:p3) and direction in 5923829846: spec: there is no VALUE-level retirement mechanism — retiredKey() retires a key, and a ruled enum-member retirement has nothing to land on #17109's value-level retirement mechanism on ElementTextPropsSchema.variant, heading → h2 and subheading → h3 as named refusals with the ruled hints, plus an ADR-0087 entry. The objectui follow-up is filed when the release that carries this is installable.

[objectstack-fleet]

Claim: PM loop round 1 · 2026-10-03T13:16Z
Session: session_01T9u38rswFp5Rw8DswRUReJ
Account: os-project-manager (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-21015-element-text-variant-retire
Worktree: objectstack-issue-21015
Domain: domain:spec
Seat: domain:spec#1 (seat post #6017)
File surface (at origin/main a7ab047cf6; stop on breach and explain in the report):

• packages/spec/src/ui/component.zod.ts, ElementTextPropsSchema.variant (about :2428–:2435): heading / subheading leave the enum through enumWithRetiredValues (packages/spec/src/shared/retired-key.ts, spec: there is no VALUE-level retirement mechanism — retiredKey() retires a key, and a ruled enum-member retirement has nothing to land on #17109's mechanism) as named refusals with the ruled hints (heading → h2, subheading → h3, or the level meant). The .optional().default('body') stays.
• The ADR-0087 kit the mechanism and the retirement playbook require: the registry entry in packages/spec/src/migrations/registry.ts (and conversions/registry.ts only if the route needs one), the regenerated artifacts, and one @objectstack/spec changeset.
• Producers, cross-lane, required for green: the 5 authored writers on main. These are examples/app-showcase/src/ui/pages/page-variables.page.ts:90 and packages/platform-objects/src/pages/sys-user.page.ts :368, :401, :434, :467, all element:text with variant: 'subheading'. Each moves to the level it means. packages/platform-objects is domain:engine's, and this seat posts the cross-lane declaration.
• Test fixtures that author the retired values (packages/spec/src/ui/component.test.ts:1760, packages/spec/src/ui/page.test.ts:903), triaged as the playbook says.
  Container & model: M, mode:subagent, model: opus (dispatch-gates --tier: no path-derived mandate; the surface is clause-② SUSPECT packages/spec/src/**). Ceiling CONTRACT_REVIEW_TIER is owed as the REVIEW of the packages/spec/src/** diff, reason: a published enum value is retired, which is a contract-surface narrowing.
  Clause-②: no (narrowing)
  Thread-read: 5969419957
  Serial constraints cleared:
• packages/spec/src/ui/component.zod.ts: spec(ui): the ComponentPropsMap rows still type renderer-read members as z.unknown() — navigation on object-map / object-gantt / object-tree and conditionalFormatting on object-kanban accept 42 — the family close-out after #21445 #21464 (seat 2, in flight) holds the form family's ComponentPropsMap members, a disjoint region.
• packages/spec/src/migrations/registry.ts: packages/spec/src: 1,277 comment lines still cite 170 deleted tracker numbers (1,295 sites) — the staged remainder of ruling C+D on #19123, measured by PR #20226 #20234 stage 11 (seat 2, hand-written rationales) and [finding] The metadata save door accepts a hook whose sandboxed body targets a stored-metadata table, which the runtime then refuses at bind: authoring answers 200 for a hook that never runs #21565 (seat 2, one ADR-0087 semantic entry) also write it. That is ordinary concurrency: the later lander merges main through scripts/pm/os-regen-merge.sh and takes the next free order.
• No open PR (fix(runtime,cloud-connection)!: a job's sandboxed body is scheduled on every door, and install-local refuses an enabled job with no body (#21489) #21584, ci(temporal-conformance): give the non-SQL step the job's live PostgreSQL URL #21577, fix(objectql): an in-process engine verb refuses an object name the registry does not resolve (#21516) #21545) touches any file above (file lists read at this stamp).