feat(spec): retire page.components[].responsive (ADR-0049 D2) and repair the four redirect texts (#11027)

[os-warren]

Fixes#11027

Maintainer ruling (2026-08-22, 「同意所有」 item 11, recorded in comment 5380752244): B — retire page.components[].responsive (ADR-0049 D2) and repair the four author-facing redirect texts in the same change. Playbook: spec-property-retirement.

What this does

page.components[].responsive was the LAST carrier of the ResponsiveConfig per-breakpoint LAYOUT block — and the destination four shipped texts prescribed, verbatim, as the live alternative after #4876 retired its widget sibling. The card's two-repo census (tsc-probe methodology, positive + negative controls) measured the claim false: objectui's two complete implementations of the contract (useResponsiveConfig, ResponsiveProtocol) have zero callers, nothing reads .responsive off a page component, objectui's own BaseSchema never declared the key, and zero authored instances exist. So:

• Tombstone — retiredKey() at page.zod.ts (the spec: DashboardWidgetSchema.responsive 按断点建模 —— objectui#3173 维护者已裁决；目标 17.0.0 正式版，带回退条款 #4876/enforce-or-remove: DashboardWidgetSchema 的 5 个 dead 键(#4956 下钻首次给出裁决) #5010 family route; PageComponentSchema is strict, and the tombstone is what makes the refusal a prescription instead of "unrecognized key"). Prescription points at responsiveStyles (ADR-0065) with the CSS translations.
• Carrier disposition — ResponsiveConfigSchema, BreakpointColumnMapSchema, BreakpointOrderMapSchema and BreakpointName (+ their types) are removed: no other authorable carrier existed, and an exported value schema with no consumer reads as a capability (refactor(spec)!: remove the plugin sandboxing / integrity / approval config that never existed (#3896 follow-up) #3950; the PerformanceConfigSchema precedent recorded in the same file). Declared as four RETIRED_DEFS_BY_MAJOR[18] entries. StyleMapSchema / ResponsiveStylesSchema (the live ADR-0065 channel) are untouched, with an explicit control pin.
• The four redirect texts repaired (plus the extra sites found in the sweep):
  1. dashboard.zod.tsspec: DashboardWidgetSchema.responsive 按断点建模 —— objectui#3173 维护者已裁决；目标 17.0.0 正式版，带回退条款 #4876 tombstone prescription — now records the correction and points at responsiveStyles; its pin test asserts the corrected text.
  2. Generated reference page (content/docs/references/ui/dashboard.mdx) — regenerated from 1.
  3. docs/protocol-upgrade-guide.md — regenerated from the corrected protocol-17 rationale + conversion summary.
  4. migrations/registry.ts protocol-17 rationale prose (os migrate meta --from 16 output) — dated CORRECTED sentence.
  • Also: the spec: DashboardWidgetSchema.responsive 按断点建模 —— objectui#3173 维护者已裁决；目标 17.0.0 正式版，带回退条款 #4876 conversion summary (copied verbatim into spec-changes.json + the upgrade-guide table), the liveness/dashboard.json widgets.responsive note, content/docs/ui/pages.mdx, content/docs/protocol/objectui/layout-dsl.mdx (the BreakpointColumnMapSchema reference card and the responsive.hiddenOn sentence), and the fifth subtle site — responsive.zod.ts's hidden → hiddenOn alias curation justified by useResponsiveConfig's return shape — leaves with the schema that hosted it. ResponsiveStylesSchema's columns/hiddenOn/order guidance now names the retirement and gives the CSS that IS applied, instead of prescribing the dead sibling key.
• ADR-0087 — retired-key entry ui/PageComponent:responsive (protocol 18), D2 conversion page-component-responsive-removed (mapPageComponents + stripKeys, retiredFromLoadPath: true, disjoint fixture covering the region-level and nested-container positions), wired into the step-18 chain with rationale.
• Pins — negative pin asserting the prescription and positive pin asserting nothing else strips (page.test.ts); the ADR-0122 iso-pin ledger rebalances 837 → 833 with a history entry.
• Changeset — @objectstack/specminor (launch-window convention: breaking rides minor; scripts/check-changeset-no-major.mjs passes), with FROM → TO and the retirement kit.

Note on the skills/** hunk (split attempted and withdrawn)

skills/objectstack-ui/references/_index.md (one regenerated line — the file's headline changes when the retired family leaves responsive.zod.ts) was briefly split out to #11696 under the governed-surface one-hit rule, at the PM's instruction. The PM withdrew that instruction after check:skill-refs went red on the split head — the gate byte-compares the committed index against a fresh render of the tree's own sources, so a generator-owned hunk cannot be green on either side of a split, and main would sit red between the two landings. The line is back in this PR (restored at d9bb37b2, check:skill-refs verified in sync locally); #11696 is closed. For the maintainer at landing time: with this generated skills/** path in the diff, Prime Directive #14 as written still makes this PR human-merge-only unless the generated-artifact exception is extended to cover it (the exact #9866 shape that produced the .claude/workflows/docs-accuracy-audit.js exception).

Ratchet readings (route: whole-def deletion + one tombstoned key — the readings match the route)

• authorable-surface/ui.json: −16 rows (the three defs' keys) + ui/PageComponent:responsive → … [RETIRED]. Deleted deliberately; the authorable-surface 的 tombstone 门禁可被手编基线绕过 —— 删掉基线行就删掉了证据(#4638 / #4643 已两次这样过绿) #4650 deletion gate verified each against RETIRED_DEFS_BY_MAJOR[18].
• json-schema.manifest/ui.json: −4 keys — the gate fired first demanding the deliberate deletion + def registration (the authorable-surface 的 tombstone 门禁可被手编基线绕过 —— 删掉基线行就删掉了证据(#4638 / #4643 已两次这样过绿) #4650 path-3 self-evidence for the def-deletion route).
• api-surface/ui.json / export-origins/ui.json: −7 exports each.
• spec-changes.json / upgrade guide: the corrected spec: DashboardWidgetSchema.responsive 按断点建模 —— objectui#3173 维护者已裁决；目标 17.0.0 正式版，带回退条款 #4876 summary only — step-18 entries project at the major cut (verified: no existing step-18 conversion projects yet either).

Liveness-ledger disposition (recorded, not drilled)

The walk drills ONE level through explicit children; page.components[] sits two levels down (regions[].components[]) and no ledger file anywhere nests children, so no walked coordinate for this key can exist. Drilling page/regions one level would classify only region keys and leave components a NEW invisible blanket (the #4956 shape recursed, and worse than the recorded gap). Disposition: page/regionsstays RECORDED in undrilled-containers.baseline.json (the gap for the other ~12 component keys is real and stays visible); the retirement's machine-checked record is the authorable-surface [RETIRED] row + RETIRED_KEYS_BY_MAJOR[18] (the #5898 aging clock) + the D2 conversion; page.json carries a dated prose record in _note and the regions row so a future driller inherits the verdict.

Verification record

Gate / suite	Result
@objectstack/spec build (tsc sweep = tombstone channel)	PASS
Full workspace build (70 packages)	PASS
@objectstack/spec tests	420 files, 11202 tests PASS
check:liveness · empty-state · authorable-surface · docs · api-surface · spec-changes · upgrade-guide · skill-refs · skill-docs · skill-examples · migration-registry · export-origins · strictness-ledger · variant-docs	all PASS (skill-refs re-verified in sync at d9bb37b2)
check:meta-url-spelling · exported-any · dual-source-exports · browser-reachable-entries · objectui-pin-citations · react-blocks · template-manifests · test-typecheck · scripts-typecheck	all PASS
pnpm check:i18n (root; no form inputs existed for the key, bundles unchanged)	PASS (EXIT=0 captured explicitly)
dispatch-gates named families: adr-0087-registration · changeset-no-major · cross-package-test-inputs · dev-prereqs · doc-frontmatter · empty-changeset · plugin-teardown-shape · section-landing-index · docs-audit affected-docs · release-rehearsal self-test · test-source-alias · type-source-resolution · query-options-erasure · type-check-coverage · type-check-debt · engine-double-contract · where-matcher	all PASS
Consumers: packages/lint (2271 tests) · CLI migrate-meta.e2e (14, replays the new conversion + idempotence) · qa/dogfood expression-conformance (3) · examples/app-showcase tsc + tests (362)	all PASS
check:react-declaration-parity	NOT RUN — requires a sibling objectui checkout/manifest; objectui is ⛔ out of this session's scope. CI's own job carries it.

The third leg (premise check, per the ruling)

#11029 (cloud census, repo:cloud) is still OPEN with no reading posted as of 2026-08-24. The ruling converts the cloud leg into a premise check: if the cloud greps surface a real consumer before landing, this PR stops and the card gets a report instead. Recorded status: pending, zero consumers surfaced so far. Whoever assembles the train: re-read #11029 before merge.

Landing train — PARKS AS DRAFT

Per the #10986 rule and the claim comment (5394270160): this PR ships together with objectui#4773's fix (the two dead consumer implementations + MobileComponentConfig) and the console pin bump, or not at all — and after #11029's cloud reading returns zero. Removing the spec exports before the objectui half lands would break ResponsiveProtocol's SpecResponsiveConfig import at the next pin bump, which is exactly why the train exists. Train assembly is the PM/maintainer's coordination item; this PR stays draft until the train is assembled.

Out of scope (deliberate)

• objectui's two dead consumer implementations — ui#4773 (⛔ cross-repo, its seat's half). No text in this PR points authors at them any more.
• docs/adr/** (constraint) and dated audit/analysis records (docs/audits/2026-07-…ledger.md row, docs/notes/airtable-dashboard-analysis.mdx, ADR-0021's dashboard sketch) — historical measurements, left as records; the generated counts companion regenerated.
• content/docs/releases/** — untouched (repo rule); the changeset is the release-notes input.

🤖 Generated with Claude Code

https://claude.ai/code/session_013Uia4VoGZrEQpskAy1Dq8j

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/spec, touching 26 documentable anchor(s).

26 hand-written doc(s) name something this change touched — list omitted above 15 rows. Re-derive on the tree named below: node scripts/docs-audit/affected-docs.mjs --json ffbb7a100bc02679f8f38029612135e6a0ef7ff1.

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

What this run could not see

• 12 changed file(s) yielded no anchor (packages/spec/api-surface/ui.json, packages/spec/authorable-surface/ui.json, packages/spec/export-origins/ui.json, …) — pages documenting those are invisible to this run
• 10 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 45 of 222 client-bound route-ledger rows — the other 177 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run: node scripts/docs-audit/affected-docs.mjs --bridge-coverage

Coarse fallback — 126 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json ffbb7a100bc02679f8f38029612135e6a0ef7ff1 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 5c2b11c952316dd067f4cac974ab0ac219504160 — the merge of head d9bb37b2828dcbff2f6f62ebdbda514a42667add into base ffbb7a100bc02679f8f38029612135e6a0ef7ff1, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin 5c2b11c952316dd067f4cac974ab0ac219504160 && git checkout 5c2b11c952316dd067f4cac974ab0ac219504160
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin ffbb7a100bc02679f8f38029612135e6a0ef7ff1 d9bb37b2828dcbff2f6f62ebdbda514a42667add && git checkout -B drift-repro ffbb7a100bc02679f8f38029612135e6a0ef7ff1 && git merge --no-ff d9bb37b2828dcbff2f6f62ebdbda514a42667add
node scripts/docs-audit/affected-docs.mjs --json ffbb7a100bc02679f8f38029612135e6a0ef7ff1

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs ffbb7a100bc02679f8f38029612135e6a0ef7ff1 → pass the list as
args.docs, on the commit named under Which tree this was computed on.