fix(release): keep the now-private @object-ui/runner out of the fixed group (objectstack#25711, WIP)

objectui#13506 made @object-ui/runner private and moved it into objectui's
changeset ignore list before the freeze at 9e1fe03. Measured on the cutover
head 1c0d02e with this branch merged and the ui-side patch applied, root
check-changeset-fixed reported it as stale. The root fixed group drops it and
the root ignore list takes it, mirroring objectui. The lockstep count moves
112 -> 111 in the two places that state it.

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

Author: claude

.changeset/config.json

@@ -117,7 +117,6 @@
       "@object-ui/providers",
       "@object-ui/react",
       "@object-ui/react-runtime",
-      "@object-ui/runner",
       "@object-ui/sdui-parser",
       "@object-ui/types",
       "object-ui"
@@ -127,6 +126,6 @@
   "access": "public",
   "baseBranch": "main",
   "updateInternalDependencies": "patch",
-  "ignore": ["@object-ui/example-*", "@object-ui/site", "@object-ui/test-support"],
+  "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 112 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 **112** 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,7 +33,7 @@
  * 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 112 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), and it also holds the private members

scripts/ui-import/README.md

@@ -117,8 +117,14 @@ Measured on 2026-10-25:
 - on `9e37acd126` with steps 1–3 and the root half of 4a, after `pnpm install
   --frozen-lockfile` and `pnpm run build`: `type-check:scripts`,
   `type-check:vitest-config`, `lint:root` exit 0, and root and objectui
-  `check-changeset-fixed` both pass (112 public packages plus `object-ui`).
-  `changeset version` moves all 113 to 18.2.0 together, `object-ui` included;
+  `check-changeset-fixed` both pass (112 public packages plus `object-ui` at that base).
+  `changeset version` moved all 113 to 18.2.0 together, `object-ui` included;
+- on the cutover head `1c0d02eda4` (objectui frozen at `9e1fe03286`), with steps 1–3 and
+  the root half of 4a: `@object-ui/runner` is private there and in objectui's `ignore`
+  (objectui#13506), so the root `fixed` group drops it and the root `ignore` takes it.
+  Root and objectui `check-changeset-fixed` exit 0 (111 public packages plus `object-ui`),
+  `check:lockstep-package-count` reads 111, and `changeset version` moves all 112 members
+  to 18.2.0 together while `@object-ui/runner` stays at 18.1.0;
 - `vitest run scripts/__tests__`: 17 failed / 5,573 passed. Two of them are 15 s
   timeouts under load (`check-vi-mock-inherit`, `dollar-dialect-alias-census`), which
   pass alone (125/125). Two failed the same way on the earlier merged tree without the