chore(cutover): the @object-ui packages join the Changesets fixed group, 4a's text byte for byte (bill item 39, objectstack#25803)

The fixed group gains the public @object-ui packages and the VS Code extension `object-ui`
(111 public packages in all, plus `object-ui`); `ignore` becomes the example, site, runner and
test-support packages. The lockstep-count prose moves 73 -> 111 in its three places
(backward-compatibility.mdx twice, publish-smoke-pack.mjs's header). All three files are
taken byte for byte from 4a (objectstack#25745 head 9a776c6), so the two PRs carry
identical hunks and 4a's collapse once the cutover lands. 4a's rewrites of
scripts/check-changeset-fixed.mjs and scripts/check-lockstep-package-count.mjs are not
carried.

Measured on the merged tree with main's scripts:
- check-changeset-fixed: before exit 1 (38 public @object-ui packages missing); after exit 1,
  `object-ui` "no longer exists in the workspace": its manifest is private, and main's script
  counts public packages only. 4a's script accepts it through PRIVATE_FIXED_MEMBERS.
- check:lockstep-package-count: after exit 1, truth 112 (fixed[0].length) vs 111 in the
  three occurrences. 4a's script subtracts PRIVATE_FIXED_MEMBERS from the length.
- Probe, not committed: the same config without `object-ui` exits 0 on both, at 111.

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

Author: claude

.changeset/config.json

@@ -80,13 +80,52 @@
       "@objectstack/account",
       "create-objectstack",
       "@objectstack/connector-openapi",
-      "@objectstack/verify"
+      "@objectstack/verify",
+      "@object-ui/app-shell",
+      "@object-ui/auth",
+      "@object-ui/cli",
+      "@object-ui/collaboration",
+      "@object-ui/components",
+      "@object-ui/console",
+      "@object-ui/core",
+      "@object-ui/create-plugin",
+      "@object-ui/data-objectstack",
+      "@object-ui/fields",
+      "@object-ui/i18n",
+      "@object-ui/layout",
+      "@object-ui/mobile",
+      "@object-ui/permissions",
+      "@object-ui/plugin-ai",
+      "@object-ui/plugin-calendar",
+      "@object-ui/plugin-charts",
+      "@object-ui/plugin-chatbot",
+      "@object-ui/plugin-dashboard",
+      "@object-ui/plugin-designer",
+      "@object-ui/plugin-detail",
+      "@object-ui/plugin-editor",
+      "@object-ui/plugin-form",
+      "@object-ui/plugin-gantt",
+      "@object-ui/plugin-grid",
+      "@object-ui/plugin-kanban",
+      "@object-ui/plugin-list",
+      "@object-ui/plugin-map",
+      "@object-ui/plugin-markdown",
+      "@object-ui/plugin-report",
+      "@object-ui/plugin-timeline",
+      "@object-ui/plugin-tree",
+      "@object-ui/plugin-view",
+      "@object-ui/providers",
+      "@object-ui/react",
+      "@object-ui/react-runtime",
+      "@object-ui/sdui-parser",
+      "@object-ui/types",
+      "object-ui"
     ]
   ],
   "linked": [],
   "access": "public",
   "baseBranch": "main",
   "updateInternalDependencies": "patch",
-  "ignore": [],
+  "ignore": ["@object-ui/example-*", "@object-ui/site", "@object-ui/runner", "@object-ui/test-support"],
   "privatePackages": { "version": true, "tag": false }
 }

content/docs/protocol/backward-compatibility.mdx

@@ -116,7 +116,7 @@ Read the **Breaking?** column, not the version number: in the 17.x minors every
 1. **RFC (Request for Comments)** — Breaking changes are proposed as GitHub issues with the `protocol:breaking` label.
 2. **Deprecation** — The old behavior is deprecated in a MINOR release (see timeline above).
 3. **Migration Guide** — A detailed migration guide is published before the removal lands, in the release notes for the version that carries it.
-4. **Release** — In the 17.x minors the breaking change shipped in the next **MINOR** version, carrying a changeset entry marked `**BREAKING**`, and `scripts/check-changeset-no-major.mjs` failed a pull request that declared a `major` bump, because under lockstep one `major` would promote all 73 published packages. During the v18 prerelease it shipped in the next `18.0.0-next.N`, because the guard stood aside in pre mode and a pull request could declare a major bump. Changesets has exited pre mode, so the guard fails a `major` bump again. See [how a breaking stage lands on the v18 line](/docs/releases/v18#how-a-breaking-stage-lands-on-this-line).
+4. **Release** — In the 17.x minors the breaking change shipped in the next **MINOR** version, carrying a changeset entry marked `**BREAKING**`, and `scripts/check-changeset-no-major.mjs` failed a pull request that declared a `major` bump, because under lockstep one `major` would promote all 111 published packages. During the v18 prerelease it shipped in the next `18.0.0-next.N`, because the guard stood aside in pre mode and a pull request could declare a major bump. Changesets has exited pre mode, so the guard fails a `major` bump again. See [how a breaking stage lands on the v18 line](/docs/releases/v18#how-a-breaking-stage-lands-on-this-line).
 
 ---
 
@@ -196,7 +196,7 @@ The `@objectstack/spec` package provides additional stability guarantees:
 
 ### Which surfaces this covers
 
-**All of them.** It was not scoped to an experimental corner or a pre-release channel: all **73** packages published from this repository belong to a single Changesets `fixed` group, so they share one version number and one policy. No published surface was exempt.
+**All of them.** It was not scoped to an experimental corner or a pre-release channel: all **111** packages published from this repository belong to a single Changesets `fixed` group, so they share one version number and one policy. No published surface was exempt.
 
 The convention was enforced rather than informal — `scripts/check-changeset-no-major.mjs` failed a pull request that introduced a `major` bump, because under lockstep a single `major` on one package would promote the entire stack. During the v18 prerelease Changesets was in pre mode with the tag `next` and the guard stood aside, so a pull request on the v18 line could declare a major bump. Changesets has exited pre mode, and the guard fails a `major` bump again.
 

scripts/publish-smoke-pack.mjs

@@ -33,10 +33,11 @@
  * a future exclusion cannot re-open the hole silently.
  *
  * Source of truth: the workspace itself. The Changesets `fixed` group in
- * .changeset/config.json enumerates the same 73 names, but it is a DERIVED
+ * .changeset/config.json enumerates the same 111 names, but it is a DERIVED
  * declaration validated against the workspace by scripts/check-changeset-fixed.mjs
  * (which reddens both when a public package is missing from the group and
- * when a group name no longer exists) — deriving from the group would mean
+ * when a group name no longer exists), and it also holds the private members
+ * that gate declares, which are never packed here — deriving from the group would mean
  * reading a copy that a gate keeps honest, rather than the thing itself.
  */