@@ -267,6 +267,14 @@ vitest 调用被拒绝:从包目录跑 vitest 会静默跑错测试集 (objectui
 
 Its "repository root" is `ui/`. The guard is `ui/scripts/vitest-invocation-guard.mjs`.
 
+### UI CI
+
+GitHub runs only the workflows in the repository root's
+[workflow directory](./.github/workflows/), so a `ui/` change is checked by the same
+`ci.yml` as the rest of the repository: its `Lint UI`, `Type Check UI`, `Test UI` and
+`Build & E2E UI` jobs run when a pull request changes `ui/`. Read those jobs for what each one
+runs; `ui/` keeps no CI guide of its own.
+
 ### UI examples
 
 No directory under `ui/examples/` is a dev server: `hello-world` is a snippet to paste into
 
@@ -289,7 +289,7 @@ For platforms that expect an HTTP 200 on `/`, the SPA `index.html` fallback alre
 
 ## Next Steps
 
-- [CI/CD Pipeline](/docs/guide/ci-cd-pipeline) — Understand the automated build and release workflows
+- [CI workflows](https://github.com/objectstack-ai/objectstack/tree/main/.github/workflows) — The repository-root workflows that build, test and release ObjectUI
 - [Architecture Overview](/docs/guide/architecture) — How ObjectUI packages fit together
 - [Quick Start](/docs/guide/quick-start) — Set up a new ObjectUI project from scratch
 - [Theming](/docs/guide/theming) — Customize the look-and-feel before deploying
@@ -33,7 +33,6 @@
     "user-state-persistence",
     "objectos-integration",
     "troubleshooting",
-    "ci-cd-pipeline",
     "deployment",
     "release-notes"
   ]
 
@@ -4,7 +4,8 @@
 # OBJECTSTACK_VERSION — the published @objectstack/* npm version the backend
 #   runs on. Until objectui moved into the objectstack repository it had to
 #   match the @objectstack/spec version this repo's pnpm-lock.yaml resolved,
-#   and ci-cd-pipeline-doc.test.ts required the two equal (objectui#7689).
+#   and objectui's CI-guide pin test (deleted by objectstack#26058) required the two equal
+#   (objectui#7689).
 #   Since the import (objectstack#25803) the console builds against the
 #   workspace's own @objectstack/spec, a lockfile link with no version, so
 #   that comparison is retired and this value is the published backend the
 
@@ -8,8 +8,8 @@ import { test, expect } from '@playwright/test';
  * only the server can answer the question the issue asked: does it accept a
  * rule array in `$filter`? It does not. Measured against the published backend
  * backend this lane pins — `OBJECTSTACK_VERSION` in `e2e/live/ci/backend.env`,
- * held to the lockfile by `scripts/__tests__/ci-cd-pipeline-doc.test.ts`
- * (objectui#7689), with the showcase-app commit derived from it at boot from
+ * once held to the lockfile by objectui's CI-guide pin test (objectui#7689; deleted by
+ * objectstack#26058), with the showcase-app commit derived from it at boot from
  * the matching `@objectstack/cli` release tag (objectui#7964). That pin has
  * moved since this measurement was first taken, which is why it is named by
  * FILE and not by value: a version literal written here goes stale behind the
 
@@ -45,7 +45,7 @@
  *
  * ## Why the consumer sweep is a blunt string match
  *
- * It follows the `scripts/__tests__/ci-cd-pipeline-doc.test.ts` pattern (#4170):
+ * It follows the pattern objectui's CI-guide pin test set (#4170; deleted by objectstack#26058):
  * read the real files, compare them, pin the inverse direction too. A type-aware
  * "is this identifier read anywhere" analysis would be more precise and much more
  * fragile, and it would still miss the reachable path that has no static reference
 
@@ -505,7 +505,7 @@ describe('wiring — the gate is actually reachable and actually runs', () => {
     // a markdown-only change anywhere under `ui/`.
     expect(withoutComments(triggerBlock(ci))).not.toMatch(/^\s+paths(-ignore)?:/m);
     const globs = uiFilterGlobs(ci);
-    const missed = ['README.md', 'content/docs/guide/ci-cd-pipeline.md', 'packages/core/README.md']
+    const missed = ['README.md', 'content/docs/guide/deployment.md', 'packages/core/README.md']
       .map(repoPath)
       .filter((file) => !globs.some((glob) => globMatches(glob, file)));
     expect(missed, 'a markdown-only change under ui/ would skip Lint UI').toEqual([]);
 
@@ -490,12 +490,6 @@ describe('check-doc-example-shared-reader — this repository', () => {
       jobBlock(rootCi(), UI_JOBS.typeCheck),
       'the gate must run in CI, next to the other source-parsing gates',
     ).toContain(`run: ${uiRun('check:doc-example-readers')}`);
-
-    // The page that inventories the gates is pinned by command (objectui#3653), so
-    // this would fail there too — asserted here as well because a reader looking
-    // for this gate looks at this file first.
-    const page = fs.readFileSync(path.join(repoRoot, 'content/docs/guide/ci-cd-pipeline.md'), 'utf8');
-    expect(page).toContain('check:doc-example-readers');
   });
 });
 
 
@@ -546,31 +546,9 @@ describe('wiring — the gate is reachable by name, and documented by command',
   // case at the bottom keeps its `package.json` half and drops the workflow
   // half for the same reason.
 
-  /**
-   * objectui#3653's discipline, applied by hand here: the page that inventories
-   * this repository's gates must name the command a contributor can be stopped
-   * by. `doc-snippet-types.yml` carries no `commandParity` unit in
-   * `ci-cd-pipeline-doc.test.ts` — verified when this landed — so this stands in
-   * for one rather than relying on a pin that does not cover the section.
-   */
-  it('is documented on the page that inventories the gates, by command', () => {
-    const page = fs.readFileSync(
-      path.join(repoRoot, 'content/docs/guide/ci-cd-pipeline.md'),
-      'utf8',
-    );
-    expect(page, 'a contributor stopped by this gate must be able to find it').toContain(
-      'pnpm check:doc-examples',
-    );
-    expect(page).toContain(GATE);
-    // The by-command row, asserted as the whole row rather than by a regex that
-    // could drift onto the prose mentions elsewhere in the same section.
-    const row = page
-      .split('\n')
-      .filter((line) => line.startsWith('|') && line.includes('`pnpm check:doc-examples`'));
-    expect(row, 'exactly one by-command table row must name this gate').toHaveLength(1);
-    expect(row[0], 'the page must say the gate BLOCKS, not merely that it exists').toContain('**Yes**');
-    expect(row[0]).toContain(GATE);
-  });
+  // `is documented on the page that inventories the gates, by command` retired
+  // with objectstack#26944, which deleted that page (objectui's CI guide, which
+  // described workflows that run nowhere under the monorepo).
 
   it('the root package.json alias invokes the gate', () => {
     const pkg = JSON.parse(fs.readFileSync(path.join(repoRoot, 'package.json'), 'utf8')) as {
Original file line number	Diff line number	Diff line change
`@@ -33,7 +33,6 @@`
`33`	`33`	`"user-state-persistence",`
`34`	`34`	`"objectos-integration",`
`35`	`35`	`"troubleshooting",`
`36`		`- "ci-cd-pipeline",`
`37`	`36`	`"deployment",`
`38`	`37`	`"release-notes"`
`39`	`38`	`]`
Original file line number	Diff line number	Diff line change
`@@ -45,7 +45,7 @@`
`45`	`45`	`*`
`46`	`46`	`* ## Why the consumer sweep is a blunt string match`
`47`	`47`	`*`
`48`		- * It follows the `scripts/__tests__/ci-cd-pipeline-doc.test.ts` pattern (#4170):
	`48`	`+ * It follows the pattern objectui's CI-guide pin test set (#4170; deleted by objectstack#26058):`
`49`	`49`	`* read the real files, compare them, pin the inverse direction too. A type-aware`
`50`	`50`	`* "is this identifier read anywhere" analysis would be more precise and much more`
`51`	`51`	`* fragile, and it would still miss the reachable path that has no static reference`