chore(docs): 合入 main 后整体重跑 gen:schema && gen:docs (#5553, #6136)

纯生成物,由 `pnpm --filter @objectstack/spec build && … gen:docs` 在合并后的
源码树上整体产出(#4675 第四步),而非把两侧各自的生成物文本拼接。

与 #6211(#5340 内联长枚举省略)同树共存已核实:
- 省略标记 `… +N more` 全语料 160 处,与 origin/main 完全一致(160)。
- 两者受影响页面交集 33 张,逐页复核 description 区(本 PR)与 type 单元格
  (#6211)各自的效果同时在位。例如 integration/connector.mdx 第 68 行「另见」
  为单个可点链接(#6136),同页 3 处 `… +N more`(#6211);security/explain.mdx
  开篇跨行行内代码跨度完整(#5553),同页 4 处省略标记。
- 验收复跑:`[../[` 归零;按段落计未配对反引号归零;代码跨度内 `\{` 残留归零。
- 全量 216 张参考页经 @mdx-js/mdx 编译通过。
- 无页面新增或丢失开篇描述。

Author: os-zhuang

content/docs/references/ai/conversation.mdx

@@ -8,7 +8,6 @@ description: Conversation protocol schemas
 AI Conversation Memory Protocol
 
 Multi-turn AI conversations with token budget management.
-
 Enables context preservation, conversation history, and token optimization.
 
 <Callout type="info">

content/docs/references/ai/embedding.mdx

@@ -10,25 +10,17 @@ Embedding & Vector Store Primitives
 Platform contract for configuring embedding models and vector stores.
 
 Scope (intentionally minimal):
-
 - How to reference an embedding model (provider + model name + secret).
-
 - How to reference a vector store (provider + connection).
 
 NOT in scope (these belong to application code, not the platform):
-
 - Chunking strategies (fixed/semantic/recursive/markdown).
-
 - Retrieval pipelines (rerankers, multi-stage retrieval, filters).
-
 - Document loaders / ingestion DSLs.
-
 - End-to-end RAG pipeline orchestration.
 
 These were removed in v1 because they describe one specific way to
-
 build a RAG application; the platform's job is to expose the embed +
-
 vector primitives so any RAG strategy can be built on top.
 
 <Callout type="info">

content/docs/references/ai/knowledge-document.mdx

@@ -6,15 +6,11 @@ description: Knowledge Document protocol schemas
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
 Knowledge Document / Chunk / Hit — canonical shapes shared by every
-
 `IKnowledgeAdapter` implementation.
 
 The framework does **not** prescribe chunk strategy or vector
-
 format. Adapters are free to chunk however they like; the framework
-
 only requires they round-trip these shapes when talking to the
-
 `IKnowledgeService`.
 
 See `content/docs/protocol/knowledge.mdx` for the full design.

content/docs/references/ai/knowledge-source.mdx

@@ -6,17 +6,12 @@ description: Knowledge Source protocol schemas
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
 Knowledge Source — declarative metadata describing what to index and
-
 which adapter to use.
 
 A KnowledgeSource is the metadata-level equivalent of an
-
 `IDataEngine` driver binding: it pairs a logical source description
-
 (object/file/http) with the *id* of an `IKnowledgeAdapter` plugin
-
 that will actually do the work. The adapter resolves the id at
-
 runtime via `IKnowledgeService.registerAdapter`.
 
 See `content/docs/protocol/knowledge.mdx` for the full design.

content/docs/references/ai/mcp.mdx

@@ -8,29 +8,20 @@ description: Mcp protocol schemas
 Model Context Protocol (MCP) — Reference & Binding Primitives
 
 MCP itself is an external protocol defined by Anthropic
-
 (https://modelcontextprotocol.io). The platform does NOT re-define
-
 MCP's wire format, transport, or message shapes — that is the job
-
 of the `@modelcontextprotocol/sdk` consumed by `@objectstack/mcp`.
 
 This file defines only the two things the *platform* needs:
 
 1. **MCPServerRef** — how a project references an external MCP
-
-server (so an agent can mount its tools).
-
+   server (so an agent can mount its tools).
 2. **MCPToolBinding** — how an MCP tool from a referenced server
-
-is exposed as an ObjectStack `AIToolDefinition` (alias,
-
-visibility, approval policy).
+   is exposed as an ObjectStack `AIToolDefinition` (alias,
+   visibility, approval policy).
 
 Everything else (transport details, capability negotiation,
-
 resource/prompt shapes, streaming, sampling) is handled by the SDK
-
 at runtime and does not need a metadata representation.
 
 <Callout type="info">

content/docs/references/ai/model-registry.mdx

@@ -8,7 +8,6 @@ description: Model Registry protocol schemas
 AI Model Registry Protocol
 
 Centralized registry for managing AI models, prompt templates, and model versioning.
-
 Enables AI-powered ObjectStack applications to discover and use LLMs consistently.
 
 <Callout type="info">

content/docs/references/ai/skill.mdx

@@ -8,7 +8,6 @@ description: Skill protocol schemas
 Skill Trigger Condition Schema
 
 Defines programmatic conditions under which a skill becomes active.
-
 Allows context-aware activation based on object type, user role, etc.
 
 <Callout type="info">

content/docs/references/ai/usage.mdx

@@ -10,25 +10,17 @@ AI Usage Primitives
 Platform contract for measuring AI consumption.
 
 Scope (intentionally minimal):
-
 - Token usage per call.
-
 - Per-call cost (computed from a model's unit price).
-
 - Model unit pricing.
 
 NOT in scope (deferred to FinOps / product layer):
-
 - Budget definitions, enforcement, alerts.
-
 - Cost allocation / chargeback / reports.
-
 - Optimization recommendations.
 
 Rationale: the platform must record *what was used*; deciding what
-
 to do about it (block calls, send alerts, allocate to cost centers)
-
 is product policy that varies wildly between tenants.
 
 <Callout type="info">

content/docs/references/api/analytics.mdx

@@ -8,7 +8,6 @@ description: Analytics protocol schemas
 Analytics API Protocol
 
 Defines the HTTP interface for the Semantic Layer.
-
 Provides endpoints for executing analytical queries and discovering metadata.
 
 <Callout type="info">

content/docs/references/api/auth-endpoints.mdx

@@ -8,13 +8,10 @@ description: Auth Endpoints protocol schemas
 Authentication Endpoint Specification
 
 Defines the canonical HTTP endpoints for the authentication service.
-
 Based on better-auth v1.4.18 endpoint conventions.
 
 NOTE: ObjectStack's auth implementation uses better-auth library which has
-
 established endpoint conventions. This spec documents those conventions as
-
 the canonical API contract.
 
 <Callout type="info">