feat(release): apply 4a's ui/ half on the merged tree (objectstack#25711)

With ui/ on main (#25825), the objectui side of the release lane lands as tree
edits instead of a patch file:

- README step 2: the pin, the dist-injection probes, objectui's release lane,
  its Changesets config, the QUICK_REFERENCE release sync (17c) and the nested
  pull_request_template.md are deleted; objectui's 65 pending changesets stay
  under ui/ for #25831;
- 4a-ui-side.patch applied under ui/ (git apply --check exit 0 on this tree),
  then deleted; scripts/ui-import/README.md now records what was applied;
- the SDUI manifest is regenerated from ui/ for the merged tree (107 -> 106
  components; objectui#13449 retired html), from the patch the 4b PR 2a
  thread measured.

check-changeset-fixed, check:lockstep-package-count, check:sdui-lockstep and
check-sdui-manifest (--self-test and the run) exit 0.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0149BHSXfCdQywGaLdpRAtWe

Author: claude

scripts/sdui-manifest.record.json

@@ -1,22 +1,54 @@
 {
   "//": [
     "Provenance record for the repo-root `sdui.manifest.json` (ADR-0080; #12924 wiring ruling 2026-08-29).",
-    "The artefact is objectui's public-tier component manifest, generated from objectui's BUILT tree at the",
-    "commit `.objectui-sha` pins (`modulesRoot` below, materialised by `pnpm objectui:build`) by",
-    "scripts/gen-sdui-manifest-node.mjs, the one producer (ruling 丙 on #17735). Same enumeration as objectui's",
-    "apps/console/dev/manifest-dump.tsx: eager-import the 16 registry modules, ComponentRegistry.getPublicConfigs(),",
-    "manifestFromConfigs from @objectstack/sdui-parser. `objectuiWorkspaceVersion` is read from that tree's",
-    "@object-ui/core/package.json — the pinned commit's own declaration, never an npm tarball's.",
-    "`scripts/check-sdui-manifest.mjs` holds this record equal to the artefact and to the live pin:",
-    "a pin bump without regeneration goes RED there — that is the anti-rot half of the freshness gate.",
-    "Regenerate + re-record: pnpm objectui:build && node scripts/gen-sdui-manifest-node.mjs"
+    "The artefact is the console's public-tier component manifest, generated from THIS tree's registry by",
+    "scripts/gen-sdui-manifest-node.mjs, the one producer (ruling 丙 on #17735): it builds the registry packages under",
+    "ui/packages/, then enumerates them from `inTree.modulesRoot` exactly as ui/apps/console/dev/manifest-dump.tsx",
+    "does: eager-import the 16 registry modules, ComponentRegistry.getPublicConfigs(), manifestFromConfigs from",
+    "@objectstack/sdui-parser. `inTree.registrySourcesSha256` digests those packages' src/ as the index holds them;",
+    "`scripts/check-sdui-manifest.mjs` recomputes it, so a registry source edit without regeneration goes RED there.",
+    "`inTree.objectuiWorkspaceVersion` is provenance, not a verdict (#25712). Pin-keyed fields, where present, say the",
+    "artefact is byte-identical to the one generated at that pin.",
+    "Regenerate + re-record: node scripts/gen-sdui-manifest-node.mjs"
   ],
-  "objectuiSha": "b41ed7f68956c8cfda21bc790548361af81b09ac",
   "source": "built-tree",
-  "modulesRoot": ".cache/objectui-b41ed7f68956/apps/console",
-  "objectuiWorkspaceVersion": "18.1.0",
   "generator": "scripts/gen-sdui-manifest-node.mjs",
   "generatedAt": "2026-10-25",
-  "sha256": "d1fde278ffd643900aba9e8fcf834d35a9c345246709f1667ae71618eaad109c",
-  "components": 107
+  "sha256": "1f6e1ccb925a678eaa393f9091dfc7d0285e4e3626e0a5c61a5474687debabb7",
+  "components": 106,
+  "inTree": {
+    "modulesRoot": "ui/apps/console",
+    "objectuiWorkspaceVersion": "18.1.0",
+    "registryPackages": [
+      "ui/packages/components",
+      "ui/packages/core",
+      "ui/packages/data-objectstack",
+      "ui/packages/fields",
+      "ui/packages/i18n",
+      "ui/packages/mobile",
+      "ui/packages/permissions",
+      "ui/packages/plugin-calendar",
+      "ui/packages/plugin-charts",
+      "ui/packages/plugin-dashboard",
+      "ui/packages/plugin-detail",
+      "ui/packages/plugin-form",
+      "ui/packages/plugin-gantt",
+      "ui/packages/plugin-grid",
+      "ui/packages/plugin-kanban",
+      "ui/packages/plugin-list",
+      "ui/packages/plugin-map",
+      "ui/packages/plugin-markdown",
+      "ui/packages/plugin-report",
+      "ui/packages/plugin-timeline",
+      "ui/packages/plugin-tree",
+      "ui/packages/plugin-view",
+      "ui/packages/providers",
+      "ui/packages/react",
+      "ui/packages/react-runtime",
+      "ui/packages/sdui-parser",
+      "ui/packages/types"
+    ],
+    "registrySources": 922,
+    "registrySourcesSha256": "35ef1abd88b0011a06bfc895b3091d1f8ecf319c3f78d2bfb0d9feb4e53f3bbe"
+  }
 }

scripts/ui-import/4a-ui-side.patch

@@ -38,17 +38,17 @@ their own changes after the cutover.
 
 # ui-import: the objectui side of the release-lane merge (objectstack#25711)
 
-`4a-ui-side.patch` is the `ui/` half of sub-issue 4a of objectstack#25677: it removes
+This is the record of the `ui/` half of sub-issue 4a of objectstack#25677. It removed
 objectui's pin on objectstack (`.objectstack-sha`, `.objectstack-pin/`, the scripts that
 read them), the dist-injection Vite probes, objectui's own release lane and its own
-Changesets config. It is a patch file and not tree edits because `ui/` does not exist on
-`main` until the subtree PR of sub-issue 5 lands; it is applied in that cutover window,
-right after the subtree PR, together with the root half of 4a.
+Changesets config. While `ui/` did not exist on `main` it was carried as a patch file,
+`4a-ui-side.patch`. In the cutover sitting, right after the subtree PR (objectstack#25825)
+landed on `main` (`fd40831416`), 4a's own PR (objectstack#25745) applied it as tree edits
+together with the root half of 4a, and deleted the patch file in the same commit.
 
-## What it changes
+## What it changed
 
-Deleted (step 2 below; the patch carries only modifications and additions, so the
-deleted files' lines are not repeated here):
+Deleted (step 2 below):
 
 - the pin: `.objectstack-sha`, `.objectstack-pin/` (7 packed manifests),
   `scripts/bump-objectstack.sh`, `scripts/objectstack-pin.mjs`,
@@ -68,7 +68,7 @@ deleted files' lines are not repeated here):
   `quick-reference-current-release-4143` pin. Its only release-path caller was
   `changeset-release.yml`, deleted above.
 
-Changed by the patch:
+Changed (step 3 below):
 
 - `scripts/vite-single-zod.ts` (new): the single-zod build guard, moved out of the deleted
   spec probe because it runs in every console build. `apps/console/vite.config.ts` drops
@@ -96,9 +96,9 @@ Changed by the patch:
   `quick-reference-commands-4149.test.ts`: their pin, release-lane and release-sync
   rows.
 
-## Apply
+## How it was applied
 
-From the monorepo root, on the tree the subtree PR produced:
+From the monorepo root, after `git merge origin/main` brought the subtree in:
 
 ```sh
 # 1. Not here: objectui's 65 pending ui/.changeset/*.md stay under ui/ for the
@@ -132,15 +132,17 @@ git rm -r -q --ignore-unmatch -- \
   ui/scripts/__tests__/vite-objectstack-client-dist.test.ts \
   ui/scripts/__tests__/vite-objectstack-spec-dist.test.ts
 
-# 3. The modifications and the three new files.
-git apply --directory=ui --check scripts/ui-import/4a-ui-side.patch
-git apply --directory=ui scripts/ui-import/4a-ui-side.patch
+# 3. The modifications and the three new files: `git apply --directory=ui` of
+#    4a-ui-side.patch, deleted in the same commit.
+
+# 4. The SDUI manifest regenerated from ui/ for the merged tree (107 -> 106
+#    components; objectui#13449 retired `html`): sdui.manifest.json and
+#    scripts/sdui-manifest.record.json, from the patch the 4b PR 2a thread measured.
 ```
 
-The patch is written against the verification branch head `9e37acd126` (objectstack#25697,
-the run 8 tree: objectui `main` imported under `ui/` plus the adaptations). Before the
-cutover, run step 3's `--check` against the final tree and regenerate the patch if it
-fails (sub-issue 5 owns that re-check).
+The patch was written against the verification branch head `9e37acd126` (objectstack#25697,
+the run 8 tree) and re-checked with `git apply --check` on the cutover heads `1c0d02eda4`
+and `c04b36dcb9` and on `main` at `fd40831416` before it was applied.
 
 ## Verify
 

scripts/ui-import/README.md

@@ -1603,7 +1603,7 @@
           "name": "sections",
           "type": "array",
           "of": "object",
-          "description": "Field groups rendered as the detail body, in order. Every entry is an OBJECT — `{ name?, label?, columns?, fields }` — a bare section-id string is NOT accepted (the spec retired that spelling in objectstack#5611, and the renderer reads name/label/fields off each entry, so a string entry renders no fields at all). `fields` are the field names shown in this section, in order — required unless `group` supplies the members instead (the spec refuses a section carrying neither, and refuses one carrying both). `label` is the section heading; omit it for an untitled, borderless section. `name` is a stable snake_case identifier and the i18n anchor — the heading resolves through objects.<object>._sections.<name>.label, so a section without a name shows its authored label in every locale. `columns` (1-4) is THIS section's field-grid width; omit it and the renderer derives the width. Authoring `sections` at all makes it the only source of the detail body; omit it and the body falls back to the object's highlightFields. @objectstack/spec 17.3.0 declares eight more member keys on an entry, and this renderer honours all eight: `icon` (a Lucide name on the section header), `description` (sub-heading copy under the heading), `collapsible` and `defaultCollapsed` (a foldable section and its initial state), `showBorder` (force the Card wrapper on or off, overriding the heading-derived default) and `headerColor` (a header tint from the shared palette) through DetailSection, plus `group` — the ADR-0085 §5 REFERENCE form, the alternative to enumerating `fields`. `{ group: 'contact_info' }` inherits the object's `fieldGroups` entry with that key: its members (every visible field pointing at it, in declaration order), its presentation (label, icon, description, collapse) and its `visibleWhen` all come from the group, so the section restates none of it — the predicate is evaluated against the bound record exactly as the entry form evaluates it, and a group it hides renders nothing (a `visibleWhen` written on a section itself is refused by the spec and not read: gate the group and reference it) and the spec refuses those keys beside `group`; `columns`, `showBorder` and `headerColor` stay yours because they are how THIS page lays the section out. A `group` naming no declared group renders nothing and is reported to the console (`@objectstack/lint` flags it as `page-section-group-unknown`). `hideEmpty` is the eighth, and it decides whether an ALL-empty section exists: it defaults to on, so a section whose fields are every one of them empty renders nothing at all — no heading, no skeleton — and `hideEmpty: false` is the spelling that keeps that heading and its label skeleton on a brand-new record. It decides ONLY the all-empty case; the empty rows of a section that still has a filled one belong to DetailSection's auto-hide heuristic plus the reader's show-empty toggle, which no authored value overrides in either polarity (objectui#7129 Q2-C), and inline-edit mode renders the section either way so its fields stay reachable. Restored under objectui#8603 (maintainer 2026-09-15) after objectui#7129 retired it on the premise, since falsified upstream, that the spec refused the key. None of the eight has a designer control yet; they are authorable in source mode only, tracked as a deferred feature. @objectstack/spec 18 declares a ninth, `count` (`{ field }`): the renderer fills the heading's `{{ count }}` hole with how many values that multi-value field holds on the current record — `{ name: 'tagging', label: '{{ count }} tags', count: { field: 'tags' }, fields: ['tags'] }` reads `3 tags` when three are selected. An absent or empty value counts 0; `count` changes only the heading, never whether the section renders, so with `hideEmpty` on an all-empty section is still absent. The hole is filled after the heading is translated, so each locale of an inline label map and a translated objects.<object>._sections.<name>.label write the same `{{ count }}`. The spec refuses `count` beside `group`, on a section with no `label`, and on a label with no hole; a heading on a section without `count` prints as written. Like the eight, `count` has no designer control yet."
+          "description": "Field groups rendered as the detail body, in order. Every entry is an OBJECT — `{ name?, label?, columns?, fields }` — a bare section-id string is NOT accepted (the spec retired that spelling in objectstack#5611, and the renderer reads name/label/fields off each entry, so a string entry renders no fields at all). `fields` are the field names shown in this section, in order — required unless `group` supplies the members instead (the spec refuses a section carrying neither, and refuses one carrying both). `label` is the section heading; omit it for an untitled, borderless section. `name` is a stable snake_case identifier and the i18n anchor — the heading resolves through objects.<object>._sections.<name>.label, so a section without a name shows its authored label in every locale. `columns` (1-4) is THIS section's field-grid width; omit it and the renderer derives the width. Authoring `sections` at all makes it the only source of the detail body; omit it and the body falls back to the object's highlightFields. @objectstack/spec 17.3.0 declares eight more member keys on an entry, and this renderer honours all eight: `icon` (a Lucide name on the section header), `description` (sub-heading copy under the heading), `collapsible` and `defaultCollapsed` (a foldable section and its initial state), `showBorder` (force the Card wrapper on or off, overriding the heading-derived default) and `headerColor` (a header tint from the shared palette) through DetailSection, plus `group` — the ADR-0085 §5 REFERENCE form, the alternative to enumerating `fields`. `{ group: 'contact_info' }` inherits the object's `fieldGroups` entry with that key: its members (every visible field pointing at it, in declaration order), its presentation (label, icon, description, collapse) and its `visibleWhen` all come from the group, so the section restates none of it — the predicate is evaluated against the bound record exactly as the entry form evaluates it, and a group it hides renders nothing (a `visibleWhen` written on a section itself is refused by the spec and not read: gate the group and reference it) and the spec refuses those keys beside `group`; `columns`, `showBorder` and `headerColor` stay yours because they are how THIS page lays the section out. A `group` naming no declared group renders nothing and is reported to the console (`@objectstack/lint` flags it as `page-section-group-unknown`). `hideEmpty` is the eighth, and it decides whether an ALL-empty section exists: it defaults to on, so a section whose fields are every one of them empty renders nothing at all — no heading, no skeleton — and `hideEmpty: false` is the spelling that keeps the section on a brand-new record: in read-only mode as its heading plus one fold row that counts the empty fields and reveals them on request (the same fold a partly-filled section uses, objectui#13386), in edit mode as every field an editable row. It decides ONLY the all-empty case; the empty rows of a section that still has a filled one belong to DetailSection's auto-hide heuristic plus the reader's show-empty toggle, which no authored value overrides in either polarity (objectui#7129 Q2-C), and inline-edit mode renders the section either way so its fields stay reachable. Restored under objectui#8603 (maintainer 2026-09-15) after objectui#7129 retired it on the premise, since falsified upstream, that the spec refused the key. None of the eight has a designer control yet; they are authorable in source mode only, tracked as a deferred feature. @objectstack/spec 18 declares a ninth, `count` (`{ field }`): the renderer fills the heading's `{{ count }}` hole with how many values that multi-value field holds on the current record — `{ name: 'tagging', label: '{{ count }} tags', count: { field: 'tags' }, fields: ['tags'] }` reads `3 tags` when three are selected. An absent or empty value counts 0; `count` changes only the heading, never whether the section renders, so with `hideEmpty` on an all-empty section is still absent. The hole is filled after the heading is translated, so each locale of an inline label map and a translated objects.<object>._sections.<name>.label write the same `{{ count }}`. The spec refuses `count` beside `group`, on a section with no `label`, and on a label with no hole; a heading on a section without `count` prints as written. Like the eight, `count` has no designer control yet."
         },
         {
           "name": "fields",
@@ -3738,17 +3738,6 @@
         }
       ]
     },
-    "html": {
-      "type": "html",
-      "namespace": "ui",
-      "inputs": [
-        {
-          "name": "html",
-          "type": "string",
-          "description": "Raw HTML content"
-        }
-      ]
-    },
     "h1": {
       "type": "h1",
       "namespace": "ui",