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

The releases overview still said the Console UI is built from the objectui
repository and sent readers to its archived CHANGELOG. Since 18.2.0 the
Console is built from this repository's ui/ workspace, and every
@object-ui/* package ships its own changeset-generated CHANGELOG.md in the
same release.

The upgrading guide's 17.x `npx skills remove` roster now names objectui,
matching the objectstack-upgrade skill: a 17.x project installed it from
the objectui repository, so the sync skips it like the objectstack-* ones.

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

Author: claude

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