feat(spec): retire inert targetVariable on element:text_input / element:record_picker (ADR-0049)

[os-zhuang]

Fixes#9198

Ledger verdict: dead (re-established, not inherited from the card)

Measured at retirement time, against sources:

• objectui (origin/main 372d9f9b4): zero production readers. The only repo-wide hits are the reverse-parity gate's exemption block (apps/console/src/__tests__/registry-inputs-spec-parity.test.ts:545-556, citing objectui#3834) and CHANGELOG lines. The live binding runs the other direction — usePageVariableBinding(schema?.id) reverse-looks-up the page variable whose source names the component id — exactly as the key's own describe text admitted ("Declarative hint; the live binding resolves via the variable whose source equals this component id").
• framework (this repo): only spec's own accept tests authored the key (component.test.ts, page.test.ts); no runtime, metadata-protocol, lint, dogfood, example, skill or hand-written-docs reader.
• cloud (origin/main d8c3c44): zero hits.
• Liveness ledger: no row exists and none is owed — element props schemas are outside the walked metadata-type shapes (the SDUI props 声明与 renderer 不一致:6 处「renderer 兑现但 ComponentPropsMap 未声明」+ 2 处「声明了没人读」(#5068 error 升级的 spec 侧前置) #5775 record-picker retirements likewise carry no rows; check:liveness is green in both directions on this change). The verdict is recorded in the retired-key entry files instead.

Disposition inherited from the settled sibling (objectui#3829 → objectui PR #4794, retirement route), per the card.

What this does

• Tombstones both keys with retiredKey() in packages/spec/src/ui/component.zod.ts (the SDUI props 声明与 renderer 不一致:6 处「renderer 兑现但 ComponentPropsMap 未声明」+ 2 处「声明了没人读」(#5068 error 升级的 spec 侧前置) #5775 pattern on the same schemas): authoring is a tsc error and a parse error whose message carries the prescription — delete the key; declare the binding on the page variable (variables: [{ name, type, source: '<component id>' }]); os migrate meta --from 17 rewrites sources.
• ADR-0087 registration (protocol 18 — v17.0.0 was cut 2026-08-14, so the tombstone ships on the 17.x line and the prescription lives at the major boundary, the additionalTypes on MetadataPluginConfig is authorable, documented as THE way a plugin declares a metadata type, and has no reader — a plugin cannot declare a kind at all #8586 precedent**)**:
  • retired-key entries ui/ElementTextInputProps:targetVariable + ui/ElementRecordPickerProps:targetVariable (one file each under src/migrations/entries/retired-keys/, registry regenerated by gen:migration-registry);
  • D2 conversion element-input-target-variable-removed (toMajor: 18, retiredFromLoadPath: true, stripKeys — pure lossless delete, the key never had an effect to lose), wired into step 18's conversionIds + rationale. Fixture covers nested containers, slots, and keeps two untouched controls: the live variables[].source binding and element:filter's targetVariable (a different surface, ADR-0049 candidate: element:filter declares targetVariable (and possibly the whole element) with no renderer or reader in any repo #9220 — which remains open and is not addressed here);
  • no D3 semantic entry: page components are stack collection members, so the D2 conversion is the channel (unlike the kernel/Manifest:loading family).
• Pin tests (component.test.ts): refusal pins asserting the prescription text (/targetVariable.*removed.*Delete the key/s, house s-flag style) on both elements; accept-side controls assert a clean parse materializes nothing. Stale fixture cleanup in page.test.ts: the page-variables fixture authored displayField (retired by SDUI props 声明与 renderer 不一致:6 处「renderer 兑现但 ComponentPropsMap 未声明」+ 2 处「声明了没人读」(#5068 error 升级的 spec 侧前置) #5775 — pre-existing drift, page block properties are not parsed against element schemas) and targetVariable; both replaced with the working spelling (labelField, binding via variables[].source).
• Generated artifacts regenerated the scripted way (check:generated --fix after build): authorable-surface/ui.json gains the two [RETIRED] marks; content/docs/references/ui/component.mdx follows the schema. spec-changes.json / upgrade guide are green unchanged — they carry published majors only, and no major-18 entry (e.g. additionalTypes on MetadataPluginConfig is authorable, documented as THE way a plugin declares a metadata type, and has no reader — a plugin cannot declare a kind at all #8586's) appears there yet. Four-ratchet expectation matches the tombstone route: api-surface/, json-schema.manifest/, signatures unchanged (no def added/removed; no export changed).
• Changeset: @objectstack/spec: minor (post-GA launch-window convention, the additionalTypes on MetadataPluginConfig is authorable, documented as THE way a plugin declares a metadata type, and has no reader — a plugin cannot declare a kind at all #8586 precedent), FROM → TO mapping, marker adr-0087: registered element-input-target-variable-removed.

Verification (all at head e4204118b, after the final commit)

• pnpm --filter @objectstack/spec test — 407 files, 10832 passed.
• pnpm --filter @objectstack/spec typecheck — green (incl. check:test-typecheck self-test).
• check:generated — all 13 artifact gates ✓; source audits check:liveness / check:empty-state / check:skill-examples / check:variant-docs PASS.
• check:adr-0087-registration, check:nul-bytes — green.
• Consumer sweep, downstream direction: @objectstack/lint (the SDUI 组件 props 没有解析闸门:PageComponent.properties 是开放 record,ComponentPropsMap 的 29 个站点从不被 parse(#4001 批 17 的 no gate 判定) #5068 authoring gate that dispatches these schemas) — 2061 tests passed against the rebuilt spec; @objectstack/dogfoodexpression-conformance — 3 passed (after building the dependency closure; no expression surface touched).
• Derived gate union (scripts/pm/dispatch-gates.mjs on the real changed paths): all named local gates PASS, including check:changeset-gate-self-tests, check:cross-package-test-inputs, check:merge-driver, check:spec-parsed-alias, check:type-check-coverage, check:type-check-debt (after full workspace build), check:engine-double-contract, check:where-matcher, check:dev-prereqs.
• Reverse verification (direction decided beforehand: red): fix committed first, then component.zod.ts restored to origin/main tree-only — exactly the 2 refusal pins went red (183 others green); restored from the branch commit, 185/185 green, git status clean.

Not in this PR

• objectui follow-through is owed and rides this card's landing: dropping the parity-gate exemption block for these two keys (objectui#3834 is pm:blocked on this card). Dispatched separately per the claim.
• element:filter's targetVariable — equally reader-less, but outside this card's two-key disposition and possibly the wrong grain (the whole element appears to have no renderer). Filed as ADR-0049 candidate: element:filter declares targetVariable (and possibly the whole element) with no renderer or reader in any repo #9220; ADR-0049 candidate: element:filter declares targetVariable (and possibly the whole element) with no renderer or reader in any repo #9220 remains open.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/spec.

106 hand-written doc(s) reference the affected code — list omitted above 15 rows. Re-derive: node scripts/docs-audit/affected-docs.mjs --json origin/main.

⛔ 7 release-owned page(s) also affected — read-only, see AGENTS.md Documentation Guardrails.

Advisory only. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs origin/main → pass the list as args.docs.