docs: migrate protocol/objectos → protocol/kernel (URL-level layer-name retirement) (#2960)

* docs: migrate protocol/objectos → protocol/kernel (URL-level layer-name retirement)

Completes the ObjectOS layer-name retirement (#2955) at the URL level:

- content/docs/protocol/objectos/ → content/docs/protocol/kernel/
  (11 pages, git mv — history preserved)
- permanent redirect /docs/protocol/objectos/:path* → /docs/protocol/kernel/:path*
  added to the redirects table (folder-moves section)
- all in-content links rewritten (protocol index/cards, objectui index,
  automation, api, kernel, concepts/architecture, plugins, package READMEs);
  historical audit docs left as-is — the redirect covers them
- protocol/meta.json: objectos → kernel

Verified: turbo build --filter=@objectstack/docs green (4m08s); zero
remaining protocol/objectos references outside the redirects table.

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

* chore: rebase role-word baseline for protocol/objectos → protocol/kernel move

The guard keys its baseline by path; git mv made the 3 baselined
occurrences show up as 'new' under kernel/ and 'gone' under objectos/.
Occurrence counts are unchanged (6 total).

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

---------

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

Author: os-zhuang

apps/docs/redirects.mjs

@@ -109,6 +109,9 @@ export const docsRedirects = [
   // folder moves (wildcards — keep after exact entries)
   ['/docs/guides/runtime-services/:path*', '/docs/kernel/runtime-services/:path*'],
   ['/docs/guides/contracts/:path*', '/docs/kernel/contracts/:path*'],
+  // ObjectOS layer-name retirement: the System Protocol section is now "kernel"
+  // (:path* matches zero or more segments, so this also covers the bare URL)
+  ['/docs/protocol/objectos/:path*', '/docs/protocol/kernel/:path*'],
   // safety net for anything else under retired sections — keep last
   ['/docs/guides/:path*', '/docs'],
 ];

content/docs/api/data-flow.mdx

@@ -212,7 +212,7 @@ flowchart LR
 How data changes propagate to connected clients in real time.
 
 <Callout type="warn">
-**Implementation status:** This diagram (and the `emit(...)` → `EB->>WS` broadcast step in the Write Flow diagram above) shows the target design. The realtime service that ships today is an **in-memory pub/sub adapter** (`InMemoryRealtimeAdapter` in `@objectstack/service-realtime`), delivered to JS clients via **long-polling** (`RealtimeAPI` in `@objectstack/client`) — no WebSocket transport is wired up yet. The adapter also only matches subscriptions by `object` and `eventTypes`; per-field `filter` conditions (e.g. `{ project: 'prj_1' }`) are accepted in the request shape but are not yet enforced server-side. See [Real-Time Protocols](/docs/protocol/objectos/realtime-protocol) for the full implementation-status breakdown.
+**Implementation status:** This diagram (and the `emit(...)` → `EB->>WS` broadcast step in the Write Flow diagram above) shows the target design. The realtime service that ships today is an **in-memory pub/sub adapter** (`InMemoryRealtimeAdapter` in `@objectstack/service-realtime`), delivered to JS clients via **long-polling** (`RealtimeAPI` in `@objectstack/client`) — no WebSocket transport is wired up yet. The adapter also only matches subscriptions by `object` and `eventTypes`; per-field `filter` conditions (e.g. `{ project: 'prj_1' }`) are accepted in the request shape but are not yet enforced server-side. See [Real-Time Protocols](/docs/protocol/kernel/realtime-protocol) for the full implementation-status breakdown.
 </Callout>
 
 ```mermaid

content/docs/api/index.mdx

@@ -71,7 +71,7 @@ See [Actions as Tools](/docs/ai/actions-as-tools) for the `run_action` bridge an
 - [Error Catalog](/docs/api/error-catalog) — the full list of error codes
 - [Wire Format](/docs/api/wire-format) — request/response envelopes on the wire
 
-Spec: [HTTP API](/docs/protocol/objectos/http-protocol), [Real-Time Protocols](/docs/protocol/objectos/realtime-protocol)
+Spec: [HTTP API](/docs/protocol/kernel/http-protocol), [Real-Time Protocols](/docs/protocol/kernel/realtime-protocol)
 
 Schema reference: [API](/docs/references/api)
 

content/docs/automation/index.mdx

@@ -49,6 +49,6 @@ Rule of thumb: model *state* with workflows, model *steps* with flows, use hooks
 
 ## Related
 
-- **Spec:** [State Machine (Lifecycle)](/docs/protocol/objectql/state-machine), [Runtime Capabilities](/docs/protocol/objectos/runtime-capabilities)
+- **Spec:** [State Machine (Lifecycle)](/docs/protocol/objectql/state-machine), [Runtime Capabilities](/docs/protocol/kernel/runtime-capabilities)
 - **Schema reference:** [Automation](/docs/references/automation)
 - **Neighbors:** validation rules that block bad data live in [Data Modeling](/docs/data-modeling/validation); who may trigger an automation is governed by [Permissions & Identity](/docs/permissions); the services hooks call (email, queue, storage…) are documented in [Kernel & Services](/docs/kernel/runtime-services).

content/docs/concepts/architecture.mdx

@@ -561,7 +561,7 @@ The three protocols are **loosely coupled** but **tightly integrated**:
 
 - [ObjectQL: Data Protocol](/docs/protocol/objectql) - Full data protocol specification
 - [ObjectUI: UI Protocol](/docs/protocol/objectui) - Full view protocol specification
-- [Kernel: System Protocol](/docs/protocol/objectos) - Full control protocol specification
+- [Kernel: System Protocol](/docs/protocol/kernel) - Full control protocol specification
 - [Developer Guide](/docs/getting-started/quick-start) - Build your first ObjectStack application
 
 ---

content/docs/kernel/index.mdx

@@ -5,7 +5,7 @@ description: The ObjectKernel runtime — plugin host, event bus, service regist
 
 # Kernel & Services
 
-The kernel is ObjectStack's runtime: it loads your metadata artifact, hosts plugins, wires up services, and enforces the lifecycle that keeps the system stable. This module documents the **ObjectOS layer** in practice — the [System Protocol](/docs/protocol/objectos) is its normative spec. If you write hooks or plugins, this is where the capability surface you call — `ctx.api`, `ctx.getService(...)`, and the `services.*` contract they implement — is documented.
+The kernel is ObjectStack's runtime: it loads your metadata artifact, hosts plugins, wires up services, and enforces the lifecycle that keeps the system stable. This module documents the **ObjectOS layer** in practice — the [System Protocol](/docs/protocol/kernel) is its normative spec. If you write hooks or plugins, this is where the capability surface you call — `ctx.api`, `ctx.getService(...)`, and the `services.*` contract they implement — is documented.
 
 ## How it fits together
 
@@ -40,6 +40,6 @@ The kernel is ObjectStack's runtime: it loads your metadata artifact, hosts plug
 
 ## Related
 
-- **Spec:** [System Lifecycle](/docs/protocol/objectos/lifecycle), [Runtime Capabilities](/docs/protocol/objectos/runtime-capabilities), [Metadata Service](/docs/protocol/objectos/metadata-service)
+- **Spec:** [System Lifecycle](/docs/protocol/kernel/lifecycle), [Runtime Capabilities](/docs/protocol/kernel/runtime-capabilities), [Metadata Service](/docs/protocol/kernel/metadata-service)
 - **Schema reference:** [Kernel](/docs/references/kernel), [System](/docs/references/system), [Contracts](/docs/references/contracts)
 - **Neighbors:** building and packaging plugins is covered in [Plugins & Packages](/docs/plugins); running the kernel in production is covered in [Deployment & Operations](/docs/deployment).

content/docs/plugins/index.mdx

@@ -18,7 +18,7 @@ ObjectStack is built on a **microkernel architecture** where nearly everything b
 - **[Package Overview](/docs/plugins/packages)** — All ObjectStack packages, services, drivers, plugins, and adapters
 - **[Adding a Metadata Type](/docs/plugins/adding-a-metadata-type)** — Register a new metadata type in the Studio Metadata Admin
 - Schema reference: [Kernel](/docs/references/kernel)
-- Spec: [Plugin Package Specification](/docs/protocol/objectos/plugin-spec)
+- Spec: [Plugin Package Specification](/docs/protocol/kernel/plugin-spec)
 
 ---
 

content/docs/protocol/index.mdx

@@ -12,7 +12,7 @@ The ObjectStack Protocol defines three interconnected layers that together descr
 <Cards>
   <Card icon={<Database />} title="ObjectQL: Data Protocol" href="/docs/protocol/objectql" description="Schema definitions, field types, state machines, query syntax, and data security." />
   <Card icon={<Layout />} title="ObjectUI: UI Protocol" href="/docs/protocol/objectui" description="Server-driven UI contracts for layouts, widgets, forms, and actions." />
-  <Card icon={<Cpu />} title="Kernel: System Protocol" href="/docs/protocol/objectos" description="Runtime lifecycle, HTTP/realtime protocols, plugins, configuration, and i18n." />
+  <Card icon={<Cpu />} title="Kernel: System Protocol" href="/docs/protocol/kernel" description="Runtime lifecycle, HTTP/realtime protocols, plugins, configuration, and i18n." />
 </Cards>
 
 ## Design Principles

…/protocol/objectos/config-resolution.mdx …cs/protocol/kernel/config-resolution.mdxcontent/docs/protocol/objectos/config-resolution.mdx renamed to content/docs/protocol/kernel/config-resolution.mdx content/docs/protocol/objectos/config-resolution.mdx renamed to content/docs/protocol/kernel/config-resolution.mdx

@@ -898,4 +898,4 @@ ObjectStack configuration resolution:
 - **Boot-time validation** using Zod schemas
 - **Inspection tools** for debugging config issues
 
-**Next:** Learn about internationalization in [i18n Standard](/docs/protocol/objectos/i18n-standard).
+**Next:** Learn about internationalization in [i18n Standard](/docs/protocol/kernel/i18n-standard).

…ocs/protocol/objectos/error-handling.mdx …/docs/protocol/kernel/error-handling.mdxcontent/docs/protocol/objectos/error-handling.mdx renamed to content/docs/protocol/kernel/error-handling.mdx content/docs/protocol/objectos/error-handling.mdx renamed to content/docs/protocol/kernel/error-handling.mdx

@@ -1047,12 +1047,12 @@ for (let i = 0; i < 1000000; i++) {
     icon={<Radio />}
     title="HTTP API"
     description="Learn REST endpoint conventions and CRUD operations"
-    href="/docs/protocol/objectos/http-protocol"
+    href="/docs/protocol/kernel/http-protocol"
   />
   <Card
     icon={<Zap />}
     title="Real-Time Protocols"
     description="Implement WebSocket subscriptions and event streaming"
-    href="/docs/protocol/objectos/realtime-protocol"
+    href="/docs/protocol/kernel/realtime-protocol"
   />
 </Cards>