docs(releases): say the Console UI builds from this repo's ui/, and add objectui to the 17.x skills remove roster (#31304)

<!-- claude-projects-attribution: {"github_login":"os-project-manager"}
-->
_Requested by **Leehom** · [project
thread](https://claude.ai/code/project/chan_01TenzsRopZj4jMbvjX8uz1X?thread=cmsg_01TenzsRopZj4jMbvjX8uz1XLFhFvLJPa3PqrCb5j7uuBC)_

domain:devx#3 · os-project-manager · session_01FEkQ5pqSJEepcpxnxx9aZy

Fixes #31158

Clause-②: no
Metadata-protocol: none

## 维护者速读

- 改了什么:两处文档文字。发布说明总览页(`content/docs/releases/index.mdx`)改说 Console UI
由本仓 `ui/` 构建,「细粒度变更日志」一节不再指向已归档的 objectui CHANGELOG,改指各 `@object-ui/*`
包自带的 `CHANGELOG.md`;升级指南(`content/docs/upgrading.mdx`)17.x 的 `npx skills
remove` 名单补上 `objectui`。
- 为什么改:18.2.0 起 Console 在本仓 `ui/` 构建,`@object-ui/*` 与 `@objectstack/*`
同一固定版本组;objectui 仓已归档,它的 CHANGELOG
不再更新。升级技能(`skills/objectstack-upgrade/SKILL.md`)的名单已含
`objectui`,文档页与之不一致。
- 风险与回滚:只改文档文字,不发布(skip-changeset);带日期的各版本发布页(v12/v13/v14 仍链到 objectui
CHANGELOG)按裁决保持原样。回滚即 revert。
- 先看:`content/docs/releases/index.mdx` 第 6–11 行与第 41–45 行两个 hunk。
- 两分钟验证:`git grep -n 'objectstack-upgrade objectui -y' --
content/docs/upgrading.mdx
skills/objectstack-upgrade/SKILL.md`,预期两个文件各命中一行(两份 `skills remove`
名单一致)。
- 需要你做的:无,席位落地。

## What changes

`content/docs/releases/index.mdx` (the releases overview, not a dated
release page):

- The opening paragraph says the Console UI is built from this
repository's `ui/` workspace, whose `@object-ui/*` packages version in
the same lockstep group, and is frozen into `@objectstack/console` at
release time. It no longer says "built from the objectui repository".
- "Where the fine-grained changelogs live", the Console UI bullet: every
`@object-ui/*` package under `ui/` ships its own changeset-generated
`CHANGELOG.md` in the same release, as does `@objectstack/console`.
Console changes from before 18.2.0 (built from the separate objectui
repository) are summarized on the release pages for their versions. The
link to the archived objectui `CHANGELOG.md` is dropped.

`content/docs/upgrading.mdx`, the "From 17.x to 18" skills step:

- The `npx skills remove` roster gains `objectui`, so it is again the
same list as `skills/objectstack-upgrade/SKILL.md`.
- The sentence under the block says why `objectui` is there: a 17.x
project installed it from the objectui repository, so the sync skips it
like the `objectstack-*` skills.

## Why

- Since 18.2.0 the Console is built in this workspace from
`ui/apps/console` (`packages/console/CHANGELOG.md`, 18.2.0 entry), and
`.changeset/config.json` puts the `@object-ui/*` packages in the
`@objectstack/*` fixed group. The objectui repository is archived, and
its CHANGELOG gets no entries. `ui/CHANGELOG.md` in this repo is marked
frozen history too, so the overview points at the per-package changelogs
instead.
- PR #31152 added `objectui` to the upgrade skill's roster. The docs
page kept the old list, and no gate holds the two equal.

## Tests

None owed: docs text only, no behaviour changed, so no test and no
ablation.

## Acceptance notes

- **Dated release pages untouched.** v12 (L204), v13 (L188) and v14
(L298) still link the objectui CHANGELOG. They describe their own time;
the order rules them out of scope.
- **Readers of these lines.** `git grep` for
`objectui/blob/main/CHANGELOG` and `built from the [objectui]` outside
`node_modules` hits only `content/docs/releases/index.mdx` and the three
dated pages; no script, census or link checker reads those lines.
`scripts/role-word-baseline.json` counts
`content/docs/releases/index.mdx`; the new text adds no counted word
(`pnpm check:role-word` below).
- `ui/.github/**` untouched.

## Verification

Gate union derived by `node scripts/pm/dispatch-gates.mjs --commands
--repo objectstack-ai/objectstack` (51 families for this diff), run on
head `1ea1840d`, each exit code captured before any pipe:

- **51 run, exit 0 each.** `--ran`: "51 derived famil(ies) accounted for
— 51 run, 0 NOT-MEASURED (a DERIVED zero — all 51 recorded an exit code
and none of them is 3)".
- First pass: five families answered a missing build prerequisite, not a
finding (`check:doc-formula-expressions` and
`check:doc-security-posture` exit 3, `check:skill-examples` exit 3,
`check:docs-transcript-drift` exit 3, `check:docs` exit 1 "json-schema
is missing"). After `pnpm --filter '@objectstack/lint...' --filter
'@objectstack/client-react...' --filter '@objectstack/spec' build` under
the verify lock (VERDICT command-exit 0), all five re-ran exit 0.
- `pnpm check:role-word` exit 0 (reads `content/docs/releases/index.mdx`
against its baseline); `node scripts/check-nul-bytes.mjs` exit 0.
- `node scripts/pm/dispatch-gates.mjs --tier`: no path-derived model
mandate for this surface.
- `pnpm lint`: the diff touches no package, so there is no scoped
package lint.
- CI families are read from this PR's check-runs, not re-run here.

`skip-changeset`: content under `content/docs/` ships in no package.

## Human Minimum

- [x] 1. Schemas start as Zod; `packages/spec` holds no runtime logic.
(not touched)
- [x] 2. Every name I added uses the casing for its kind. (none added)
- [x] 3. No formatter ran; `pnpm lint` passes. (no package touched; docs
only)
- [x] 4. One issue, one branch off an up-to-date `main`, one pull
request.
- [x] 5. A change that publishes carries a changeset, and both
declaration lines are filled in here and in the changeset. (publishes
nothing: `skip-changeset`)
- [x] 6. `packages/spec` touched: its generated artifacts are
regenerated and committed. (not touched)
- [ ] 7. No hand edits to `content/docs/references/`,
`packages/*/CHANGELOG.md` or `content/docs/releases/`. Deliberate: this
is the dedicated docs-only PR AGENTS.md's Documentation Guardrails name
for a factual error on a releases page; only the maintained overview
`index.mdx` moves, no dated page.
- [x] 8. Title, body and comments are in English.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01FEkQ5pqSJEepcpxnxx9aZy

Co-authored-by: Claude <noreply@anthropic.com>

Author: objectstack-fleet[bot]

content/docs/releases/index.mdx

@@ -5,9 +5,10 @@ description: Release notes for the ObjectStack platform — framework packages a
 
 ObjectStack ships as a single release train: all `@objectstack/*` packages are
 version-locked, so one version number describes the whole platform. The
-Console UI (built from the [objectui](https://github.com/objectstack-ai/objectui)
-repository) is frozen into `@objectstack/console` at release time, so each
-release note here also covers what changed in Studio/Console. ObjectStack
+Console UI is built from this repository's [`ui/`](https://github.com/objectstack-ai/objectstack/tree/main/ui)
+workspace, whose `@object-ui/*` packages version in the same lockstep group,
+and is frozen into `@objectstack/console` at release time, so each release
+note here also covers what changed in Studio/Console. ObjectStack
 Cloud (the hosted service) versions independently and deploys continuously —
 developer-facing Cloud changes are summarized in the release note for the
 framework version they accompany.
@@ -37,8 +38,11 @@ These pages are curated summaries. For exhaustive, per-package detail:
 - **Framework packages** — every package ships a `CHANGELOG.md` generated from
   [changesets](https://github.com/changesets/changesets), visible on npm and in
   the [framework repository](https://github.com/objectstack-ai/objectstack).
-- **Console UI** — the [objectui CHANGELOG](https://github.com/objectstack-ai/objectui/blob/main/CHANGELOG.md)
-  follows Keep a Changelog.
+- **Console UI** — every `@object-ui/*` package under `ui/` ships its own
+  `CHANGELOG.md`, generated from the same changesets in the same release, as
+  does `@objectstack/console`. Console changes released before 18.2.0, when
+  the Console was still built from the separate objectui repository, are
+  summarized on the release pages for their versions.
 - **Design decisions** — breaking changes reference their
   [ADRs](https://github.com/objectstack-ai/objectstack/tree/main/docs/adr), which
   record the rationale.

content/docs/upgrading.mdx

@@ -109,7 +109,7 @@ command for this move; it is four steps you run yourself.
    ```bash
    npx skills remove objectstack-ai objectstack-api objectstack-automation \
      objectstack-data objectstack-formula objectstack-i18n objectstack-platform \
-     objectstack-pm-dispatch objectstack-query objectstack-ui objectstack-upgrade -y
+     objectstack-pm-dispatch objectstack-query objectstack-ui objectstack-upgrade objectui -y
    pnpm add -D "@objectstack/skills@$(node -p "require('@objectstack/spec/package.json').version")"
    #   npm: npm install --save-dev "@objectstack/skills@…"   ·   yarn: yarn add -D "@objectstack/skills@…"
    npx skills@1.7.2 experimental_sync --agent claude-code --copy -y
@@ -118,7 +118,8 @@ command for this move; it is four steps you run yourself.
    Add the package with the manager that installed the project: in a pnpm
    project, `npm install --save-dev` exits `1` with
    `npm error Cannot read properties of null (reading 'edgesOut')`.
-   The list names every skill the catalog carried during 17.x, and a name that
+   The list names every skill the catalog carried during 17.x, plus `objectui`,
+   which a 17.x project installed from the objectui repository, and a name that
    is not installed is skipped; `npx skills remove --all` does the same when
    these are the only skills the project has. Run `npx skills list` first:
    `--all` removes every installed skill without asking, so use it only when