@agent-native/core 0.109.3 → 0.109.4

package/corpus/core/docs/content/locales/zh-CN/agent-native-toolkit.mdx

@@ -1,23 +1,15 @@
 ---
-title: "Toolkits"
-description: "Battle-tested reusable building blocks for high-quality agentic applications: collaboration, sharing, settings, teams, setup, navigation, resources, agent UX, history, comments, and observability."
+title: "Toolkit"
+description: "一个均衡的目录，涵盖可复用基础、编辑器与画布、智能体上下文、治理、工作区框架、运营以及 Toolkit 能力模块。"
 ---
 
 <!-- i18n-docs-ignore -->
 
-# Toolkits
+# Toolkit
 
-Toolkits are reusable, battle-tested building blocks for high-quality agentic
-applications. They turn the hard product work that repeats across apps into
-standard surfaces: realtime collaboration between humans and agents, sharing
-with humans and agents, settings, teams, setup, resources, history, review, and
-observability.
+Toolkit 是面向高质量智能体应用的可复用、久经验证的构建模块。它将跨应用反复出现的棘手产品工作转化为标准界面：人类与智能体之间的实时协作、面向人类和智能体的共享、设置、团队、配置、资源、历史记录、审阅和可观测性。
 
-Each kit packages the UI patterns, action contracts, app-state expectations,
-access boundaries, and agent-visible behavior that users expect to work
-consistently. Apps still own their domain model and visual identity; toolkits
-make the common product systems feel complete from the first version instead of
-being rebuilt in slightly different ways every time.
+每个工具包都封装了用户期望持续一致的 UI 模式、操作契约、应用状态预期、访问边界和智能体可见行为。应用仍拥有自己的领域模型和视觉标识；Toolkit 让通用产品系统从第一个版本起就完整可用，而不是每次以略有不同的方式重新构建。
 
 <WireframeBlock id="doc-block-toolkits-index">
   <Screen
@@ -28,23 +20,23 @@ being rebuilt in slightly different ways every time.
   />
 </WireframeBlock>
 
-<Diagram id="doc-block-toolkits-boundary" title="How kits fit" summary={"The framework runtime supplies durable guarantees. Toolkits turn those guarantees into reusable product systems. Apps add domain-specific data, routes, and visual identity."}>
+<Diagram id="doc-block-toolkits-boundary" title="工具包如何融入" summary={"框架运行时提供持久保证。Toolkit 将这些保证转化为可复用的产品系统。应用再加入领域特定的数据、路由和视觉标识。"}>
 
 ```html
 <div class="diagram-row">
   <div class="diagram-card">
-    <span class="diagram-pill accent">Runtime</span><br />
-    actions, SQL, auth, app state, access checks, realtime transport
+    <span class="diagram-pill accent">运行时</span><br />
+    操作、SQL、认证、应用状态、访问检查、实时传输
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-card">
-    <span class="diagram-pill accent">Toolkits</span><br />
-    collaboration, sharing, setup, review, history, observability
+    <span class="diagram-pill accent">Toolkit</span><br />
+    协作、共享、配置、审阅、历史记录、可观测性
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-card">
-    <span class="diagram-pill accent">Apps</span><br />
-    domain schema, routes, actions, branding, specialized workflows
+    <span class="diagram-pill accent">应用</span><br />
+    领域架构、路由、操作、品牌、专门工作流
   </div>
 </div>
 ```
@@ -68,45 +60,60 @@ being rebuilt in slightly different ways every time.
 
 </Diagram>
 
-## The Kits {#the-kits}
-
-| Kit                                                      | Use it for                                                                                                  |
-| -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
-| [Sharing](/docs/toolkit-sharing)                         | Ownable resources, share dialogs, visibility badges, share actions, public/private/org access.              |
-| [Collaboration](/docs/toolkit-collaboration)             | Realtime editing, presence, live cursors, recent-edit highlights, collaborative undo.                       |
-| [Settings](/docs/toolkit-settings)                       | Standard settings pages and tabs so app settings and agent/provider settings live in one predictable place. |
-| [Org & Team](/docs/toolkit-org-team)                     | Team pages, org switching, invites, org domains, roles, and app switching.                                  |
-| [Setup & Connections](/docs/toolkit-setup-connections)   | Onboarding, secrets, workspace connections, OAuth/provider readiness, and Builder connect.                  |
-| [Command & Navigation](/docs/toolkit-command-navigation) | Command menu, deep links, standard app routes, sidebar and shell patterns.                                  |
-| [Resources](/docs/toolkit-resources)                     | Resource trees, editors, file picker/search, attachments, and local file mode.                              |
-| [Agent UX](/docs/toolkit-agent-ux)                       | Composer, model picker, context chips, approvals, run recovery, and the runs tray.                          |
-| [History](/docs/toolkit-history)                         | Version history, audit logs, undo/redo, restore, and "what changed" surfaces.                               |
-| [Comments & Review](/docs/toolkit-comments-review)       | Inline comments, annotations, mentions, resolved threads, review status.                                    |
-| [Observability](/docs/toolkit-observability)             | Usage, spend, feedback, replay, errors, and run diagnostics.                                                |
-
-## Implementation Boundary {#implementation-boundary}
-
-Kits are product surfaces first. Some pieces are runtime-backed
-(`@agent-native/core`), some are presentation primitives
-(`@agent-native/toolkit`), and apps usually wrap both through local adapters.
-Use the package path that owns the needed behavior, but design the user-facing
-settings, collaboration, sharing, team, review, and setup experiences as one
-coherent kit instead of exposing package boundaries in the app.
-
-## Foundation Pieces {#foundation-pieces}
-
-- [UI Primitives](/docs/toolkit-ui) cover shared shadcn-style primitives under
-  `@agent-native/toolkit/ui/*`.
-- [App Adapters](/docs/toolkit-ui#app-adapters) show how apps wrap Toolkit pieces
-  through local `@/components/*` adapters.
-- [Shell & Hooks](/docs/toolkit-ui#shell-hooks) cover header actions, mobile hooks,
-  toasts, and small app-shell helpers.
-- [Component API](/docs/components) remains the lower-level reference for the
-  public React exports.
-
-## Design Rule {#design-rule}
-
-Use a toolkit when the behavior repeats across apps and users expect it to feel
-standard: sharing, settings, teams, comments, history, and agent progress should
-not be slightly different in every template. Keep domain-specific data,
-workflows, labels, and visual styling in the app.
+## 目录 {#catalog}
+
+| 领域               | 从这里开始                                      | 覆盖内容                                                     |
+| ------------------ | ----------------------------------------------- | ------------------------------------------------------------ |
+| 基础               | [UI 原语](/docs/toolkit-ui)                     | 共享控件、Hook、应用适配器和 Shell 接缝。                    |
+| 编辑器与画布       | [编辑器与画布](/docs/toolkit-editors-canvases)  | 富文本编辑、结构化区块、可复用画布控件和 Design 模式。       |
+| 智能体体验与上下文 | [上下文与知识](/docs/toolkit-context-knowledge) | Context X-Ray、资源、知识、Composer 上下文和智能体可见状态。 |
+| 协作与治理         | [协作](/docs/toolkit-collaboration)             | 分享、在线状态、审阅、历史、审计和组织边界。                 |
+| 工作区框架         | [应用框架](/docs/toolkit-settings)              | 设置、团队、配置、导航、资源和智能体 UX。                    |
+| 运营               | [可观测性](/docs/toolkit-observability)         | 使用情况、反馈、回放、诊断和运营可见性。                     |
+| Toolkit 能力模块   | [能力包](/docs/toolkit-capability-packages)     | 按需安装的领域包及其生命周期清单。                           |
+
+## 产品套件 {#product-kits}
+
+| 工具包                                         | 用途                                                                    |
+| ---------------------------------------------- | ----------------------------------------------------------------------- |
+| [共享](/docs/toolkit-sharing)                  | 可拥有资源、共享对话框、可见性徽章、共享操作、公开/私有/组织访问。      |
+| [协作](/docs/toolkit-collaboration)            | 实时编辑、在线状态、实时光标、最近编辑高亮、协作撤销。                  |
+| [设置](/docs/toolkit-settings)                 | 标准设置页和标签页，让应用设置与智能体/提供商设置位于一个可预测的位置。 |
+| [组织与团队](/docs/toolkit-org-team)           | 团队页、组织切换、邀请、组织域、角色和应用切换。                        |
+| [配置与连接](/docs/toolkit-setup-connections)  | 引导、密钥、工作区连接、OAuth/提供商就绪状态和 Builder 连接。           |
+| [命令与导航](/docs/toolkit-command-navigation) | 命令菜单、深层链接、标准应用路由、侧栏和外壳模式。                      |
+| [资源](/docs/toolkit-resources)                | 资源树、编辑器、文件选择/搜索、附件和本地文件模式。                     |
+| [智能体 UX](/docs/toolkit-agent-ux)            | 编辑器、模型选择器、上下文标签、批准、运行恢复和运行托盘。              |
+| [历史记录](/docs/toolkit-history)              | 版本历史、审计日志、撤销/重做、恢复和“发生了什么变化”界面。             |
+| [评论与审阅](/docs/toolkit-comments-review)    | 内联评论、注释、提及、已解决线程和审阅状态。                            |
+| [可观测性](/docs/toolkit-observability)        | 用量、支出、反馈、回放、错误和运行诊断。                                |
+
+## 包成熟度与所有权 {#package-maturity-and-ownership}
+
+- 富文本编辑器由 **Toolkit** 所有；迁移期间，现有 Core import 继续作为轻量兼容性 re-export。
+- Design 是带有可复用 `design-tweaks` 的**模板模式**，不是完整的即插即用编辑器或画布。
+- 本阶段 Blocks 和 Context X-Ray 引擎仍由 **Core** 所有；可复用的 Context X-Ray 呈现由 Toolkit 所有。
+- Creative Context、Scheduling 和 Pinpoint 是按需安装的 **Toolkit 能力模块**；它们保留独立的 npm 包和生命周期清单。Dispatch 仍是独立产品。
+
+## 实现边界 {#implementation-boundary}
+
+工具包首先是产品界面。一些部分由运行时支持（`@agent-native/core`），一些是呈现原语（`@agent-native/toolkit`），应用通常通过本地适配器封装两者。请使用拥有所需行为的包路径，但将面向用户的设置、协作、共享、团队、审阅和配置体验设计为一个连贯的工具包，而不是在应用中暴露包边界。
+
+## 基础组成部分 {#foundation-pieces}
+
+- [UI 原语](/docs/toolkit-ui) 涵盖 `@agent-native/toolkit/ui/*` 下共享的 shadcn 风格原语。
+- [应用适配器](/docs/toolkit-ui#app-adapters) 展示应用如何通过本地 `@/components/*` 适配器封装 Toolkit 组件。
+- [外壳与 Hook](/docs/toolkit-ui#shell-hooks) 涵盖页头操作、移动端 Hook、提示消息和小型应用外壳辅助工具。
+- [组件 API](/docs/components) 仍是公共 React 导出的低层参考。
+
+## 设计规则 {#design-rule}
+
+当某种行为在应用之间重复出现，并且用户希望它具有标准体验时，请使用 Toolkit：共享、设置、团队、评论、历史记录和智能体进度不应在每个模板中略有不同。将领域特定的数据、工作流、标签和视觉样式保留在应用中。
+
+## 下一步
+
+- [**Toolkit UI 原语**](/docs/toolkit-ui) — 共享原语、应用适配器和 Shell Hook。
+- [**分享套件**](/docs/toolkit-sharing) — 资源、分享对话框和可见性的良好起点。
+- [**创建模板**](/docs/creating-templates) — 端到端构建模板，并了解套件如何融入其中。
+- [**组件 API**](/docs/components) — 所有公开 React 导出的参考。
+- [**包生命周期**](/docs/package-lifecycle) — 安全地检查、添加和弹出由清单驱动的 Toolkit 能力模块。

package/corpus/core/docs/content/locales/zh-CN/toolkit-capability-packages.mdx

@@ -0,0 +1,21 @@
+---
+title: "能力包"
+description: "管理领域能力及其清单驱动的生命周期，而不将其并入 Toolkit。"
+---
+
+# 能力包
+
+Toolkit 提供跨应用产品基础；能力包提供受限领域、actions、skills 和生命周期元数据。Scheduling 和 Creative Context 是独立能力包，而不是 Toolkit 功能套件。
+
+`@agent-native/scheduling` 参与通用清单试点。请以各包本地文档和生命周期清单作为扩展点与归属的来源。
+
+- [Scheduling 包文档](https://github.com/BuilderIO/agent-native/tree/main/packages/scheduling/docs)
+- [Creative Context 包文档](https://github.com/BuilderIO/agent-native/tree/main/packages/creative-context/docs)
+
+```bash
+agent-native package inspect @agent-native/scheduling
+agent-native package add @agent-native/scheduling --apply
+agent-native package eject @agent-native/scheduling --apply
+```
+
+检查、预演和 eject 规则见[包生命周期](/docs/package-lifecycle)。

package/corpus/core/docs/content/locales/zh-CN/toolkit-context-knowledge.mdx

@@ -0,0 +1,12 @@
+---
+title: "上下文与知识"
+description: "在引擎、数据访问和可复用呈现之间保持正确边界，构建面向智能体的上下文表面。"
+---
+
+# 上下文与知识
+
+Core 负责应用状态、范围受限的访问和 Context X-Ray 引擎。Toolkit 提供可复用呈现；应用负责领域记录、分类法和选择规则。
+
+Context X-Ray 引擎仍归 Core。可用 Toolkit 统一呈现上下文，但状态和访问决策应保留在 Core 与 actions 中。[Context awareness](/docs/context-awareness) 让导航、选择和聚焦对象对智能体可见；[Resources](/docs/toolkit-resources) 处理文件与附件。
+
+上下文不能替代访问控制。检索提供商知识前必须保留资源和凭据检查。

package/corpus/core/docs/content/locales/zh-CN/toolkit-editors-canvases.mdx

@@ -0,0 +1,17 @@
+---
+title: "编辑器与画布"
+description: "在 Core 兼容路径、模板模式与 Toolkit 原语之间作出清晰选择。"
+---
+
+# 编辑器与画布
+
+编辑器和画布是相关的产品表面，不应把其中任何一个作为唯一旗舰功能。
+
+| 表面         | 当前归属                                                    |
+| ------------ | ----------------------------------------------------------- |
+| 富文本编辑器 | 归 Toolkit，Core 保留兼容性重导出。                         |
+| Blocks       | 本阶段仍归 Core。                                           |
+| Design       | 带有 `design-tweaks` 的模板模式，并非完整的即插即用编辑器。 |
+| 画布呈现     | Toolkit 或应用的组合。                                      |
+
+请从 `@agent-native/toolkit/editor` 导入编辑器。旧 Core 路径继续作为兼容性重导出。架构、命令和持久化仍由应用负责。Blocks 仍归 Core，但 Toolkit 栏目是可复用 UI 的统一目录，因此文档集中在这里。

package/corpus/core/docs/content/locales/zh-TW/agent-native-toolkit.mdx

@@ -1,23 +1,15 @@
 ---
-title: "Toolkits"
-description: "Battle-tested reusable building blocks for high-quality agentic applications: collaboration, sharing, settings, teams, setup, navigation, resources, agent UX, history, comments, and observability."
+title: "Toolkit"
+description: "一個均衡的目錄，涵蓋可重用基礎、編輯器與畫布、智慧代理脈絡、治理、工作區框架、營運以及 Toolkit 能力模組。"
 ---
 
 <!-- i18n-docs-ignore -->
 
-# Toolkits
+# Toolkit
 
-Toolkits are reusable, battle-tested building blocks for high-quality agentic
-applications. They turn the hard product work that repeats across apps into
-standard surfaces: realtime collaboration between humans and agents, sharing
-with humans and agents, settings, teams, setup, resources, history, review, and
-observability.
+Toolkit 是面向高品質智慧代理應用程式、可重複使用且經過實戰驗證的建構元件。它將跨應用程式反覆出現的困難產品工作轉化為標準介面：人類與智慧代理之間的即時協作、面向人類和智慧代理的分享、設定、團隊、設定流程、資源、歷程、審閱和可觀測性。
 
-Each kit packages the UI patterns, action contracts, app-state expectations,
-access boundaries, and agent-visible behavior that users expect to work
-consistently. Apps still own their domain model and visual identity; toolkits
-make the common product systems feel complete from the first version instead of
-being rebuilt in slightly different ways every time.
+每個套件都封裝了使用者期待能持續一致運作的 UI 模式、動作契約、應用程式狀態預期、存取邊界和智慧代理可見行為。應用程式仍擁有自己的領域模型和視覺識別；Toolkit 讓通用產品系統從第一個版本起就完整可用，而不是每次以稍有不同的方式重新建立。
 
 <WireframeBlock id="doc-block-toolkits-index">
   <Screen
@@ -28,23 +20,23 @@ being rebuilt in slightly different ways every time.
   />
 </WireframeBlock>
 
-<Diagram id="doc-block-toolkits-boundary" title="How kits fit" summary={"The framework runtime supplies durable guarantees. Toolkits turn those guarantees into reusable product systems. Apps add domain-specific data, routes, and visual identity."}>
+<Diagram id="doc-block-toolkits-boundary" title="套件如何融入" summary={"框架執行階段提供持久保證。Toolkit 將這些保證轉化為可重複使用的產品系統。應用程式再加入領域特定的資料、路由和視覺識別。"}>
 
 ```html
 <div class="diagram-row">
   <div class="diagram-card">
-    <span class="diagram-pill accent">Runtime</span><br />
-    actions, SQL, auth, app state, access checks, realtime transport
+    <span class="diagram-pill accent">執行階段</span><br />
+    動作、SQL、驗證、應用程式狀態、存取檢查、即時傳輸
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-card">
-    <span class="diagram-pill accent">Toolkits</span><br />
-    collaboration, sharing, setup, review, history, observability
+    <span class="diagram-pill accent">Toolkit</span><br />
+    協作、分享、設定流程、審閱、歷程、可觀測性
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-card">
-    <span class="diagram-pill accent">Apps</span><br />
-    domain schema, routes, actions, branding, specialized workflows
+    <span class="diagram-pill accent">應用程式</span><br />
+    領域結構描述、路由、動作、品牌、專門工作流程
   </div>
 </div>
 ```
@@ -68,45 +60,60 @@ being rebuilt in slightly different ways every time.
 
 </Diagram>
 
-## The Kits {#the-kits}
-
-| Kit                                                      | Use it for                                                                                                  |
-| -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
-| [Sharing](/docs/toolkit-sharing)                         | Ownable resources, share dialogs, visibility badges, share actions, public/private/org access.              |
-| [Collaboration](/docs/toolkit-collaboration)             | Realtime editing, presence, live cursors, recent-edit highlights, collaborative undo.                       |
-| [Settings](/docs/toolkit-settings)                       | Standard settings pages and tabs so app settings and agent/provider settings live in one predictable place. |
-| [Org & Team](/docs/toolkit-org-team)                     | Team pages, org switching, invites, org domains, roles, and app switching.                                  |
-| [Setup & Connections](/docs/toolkit-setup-connections)   | Onboarding, secrets, workspace connections, OAuth/provider readiness, and Builder connect.                  |
-| [Command & Navigation](/docs/toolkit-command-navigation) | Command menu, deep links, standard app routes, sidebar and shell patterns.                                  |
-| [Resources](/docs/toolkit-resources)                     | Resource trees, editors, file picker/search, attachments, and local file mode.                              |
-| [Agent UX](/docs/toolkit-agent-ux)                       | Composer, model picker, context chips, approvals, run recovery, and the runs tray.                          |
-| [History](/docs/toolkit-history)                         | Version history, audit logs, undo/redo, restore, and "what changed" surfaces.                               |
-| [Comments & Review](/docs/toolkit-comments-review)       | Inline comments, annotations, mentions, resolved threads, review status.                                    |
-| [Observability](/docs/toolkit-observability)             | Usage, spend, feedback, replay, errors, and run diagnostics.                                                |
-
-## Implementation Boundary {#implementation-boundary}
-
-Kits are product surfaces first. Some pieces are runtime-backed
-(`@agent-native/core`), some are presentation primitives
-(`@agent-native/toolkit`), and apps usually wrap both through local adapters.
-Use the package path that owns the needed behavior, but design the user-facing
-settings, collaboration, sharing, team, review, and setup experiences as one
-coherent kit instead of exposing package boundaries in the app.
-
-## Foundation Pieces {#foundation-pieces}
-
-- [UI Primitives](/docs/toolkit-ui) cover shared shadcn-style primitives under
-  `@agent-native/toolkit/ui/*`.
-- [App Adapters](/docs/toolkit-ui#app-adapters) show how apps wrap Toolkit pieces
-  through local `@/components/*` adapters.
-- [Shell & Hooks](/docs/toolkit-ui#shell-hooks) cover header actions, mobile hooks,
-  toasts, and small app-shell helpers.
-- [Component API](/docs/components) remains the lower-level reference for the
-  public React exports.
-
-## Design Rule {#design-rule}
-
-Use a toolkit when the behavior repeats across apps and users expect it to feel
-standard: sharing, settings, teams, comments, history, and agent progress should
-not be slightly different in every template. Keep domain-specific data,
-workflows, labels, and visual styling in the app.
+## 目錄 {#catalog}
+
+| 領域               | 從這裡開始                                     | 涵蓋內容                                                     |
+| ------------------ | ---------------------------------------------- | ------------------------------------------------------------ |
+| 基礎               | [UI 原語](/docs/toolkit-ui)                    | 共用控制項、Hook、應用程式配接器和 Shell 接點。              |
+| 編輯器與畫布       | [編輯器與畫布](/docs/toolkit-editors-canvases) | 豐富編輯、結構化區塊、可重用畫布控制項和 Design 模式。       |
+| 智慧代理體驗與脈絡 | [脈絡與知識](/docs/toolkit-context-knowledge)  | Context X-Ray、資源、知識、Composer 脈絡和智慧代理可見狀態。 |
+| 協作與治理         | [協作](/docs/toolkit-collaboration)            | 分享、在線狀態、審閱、歷程、稽核和組織邊界。                 |
+| 工作區框架         | [應用程式框架](/docs/toolkit-settings)         | 設定、團隊、設定流程、導覽、資源和智慧代理 UX。              |
+| 營運               | [可觀測性](/docs/toolkit-observability)        | 使用情況、意見回饋、重播、診斷和營運可見性。                 |
+| Toolkit 能力模組   | [能力套件](/docs/toolkit-capability-packages)  | 依需要安裝的領域套件及其生命週期資訊清單。                   |
+
+## 產品套件 {#product-kits}
+
+| 套件                                              | 用途                                                                           |
+| ------------------------------------------------- | ------------------------------------------------------------------------------ |
+| [分享](/docs/toolkit-sharing)                     | 可擁有資源、分享對話方塊、可見性徽章、分享動作、公開／私人／組織存取。         |
+| [協作](/docs/toolkit-collaboration)               | 即時編輯、在線狀態、即時游標、最近編輯醒目提示、協作復原。                     |
+| [設定](/docs/toolkit-settings)                    | 標準設定頁面和分頁，讓應用程式設定與智慧代理／提供者設定位於一個可預期的位置。 |
+| [組織與團隊](/docs/toolkit-org-team)              | 團隊頁面、組織切換、邀請、組織網域、角色和應用程式切換。                       |
+| [設定流程與連線](/docs/toolkit-setup-connections) | 上手引導、密鑰、工作區連線、OAuth／提供者就緒狀態和 Builder 連線。             |
+| [命令與導覽](/docs/toolkit-command-navigation)    | 命令選單、深層連結、標準應用程式路由、側欄和 Shell 模式。                      |
+| [資源](/docs/toolkit-resources)                   | 資源樹、編輯器、檔案選擇／搜尋、附件和本機檔案模式。                           |
+| [智慧代理 UX](/docs/toolkit-agent-ux)             | Composer、模型選擇器、脈絡籤、核准、執行復原和執行托盤。                       |
+| [歷程](/docs/toolkit-history)                     | 版本歷程、稽核日誌、復原／重做、還原和「有何變更」介面。                       |
+| [評論與審閱](/docs/toolkit-comments-review)       | 內嵌評論、註解、提及、已解決討論串和審閱狀態。                                 |
+| [可觀測性](/docs/toolkit-observability)           | 使用量、支出、意見回饋、重播、錯誤和執行診斷。                                 |
+
+## 套件成熟度與所有權 {#package-maturity-and-ownership}
+
+- 豐富編輯器由 **Toolkit** 擁有；移轉期間，現有 Core import 持續作為精簡的相容性 re-export。
+- Design 是使用可重用 `design-tweaks` 的**範本模式**，不是完整的即插即用編輯器或畫布。
+- 此階段 Blocks 和 Context X-Ray 引擎仍由 **Core** 擁有；可重用的 Context X-Ray 呈現由 Toolkit 擁有。
+- Creative Context、Scheduling 和 Pinpoint 是依需要安裝的 **Toolkit 能力模組**；它們保留獨立 npm 套件和生命週期資訊清單。Dispatch 仍是獨立產品。
+
+## 實作邊界 {#implementation-boundary}
+
+套件首先是產品介面。有些部分由執行階段支援（`@agent-native/core`），有些是呈現原語（`@agent-native/toolkit`），應用程式通常會透過本機配接器封裝兩者。請使用擁有所需行為的套件路徑，但將面向使用者的設定、協作、分享、團隊、審閱和設定流程體驗設計為一個連貫的套件，而不要在應用程式中暴露套件邊界。
+
+## 基礎元件 {#foundation-pieces}
+
+- [UI 原語](/docs/toolkit-ui) 涵蓋 `@agent-native/toolkit/ui/*` 下共用的 shadcn 風格原語。
+- [應用程式配接器](/docs/toolkit-ui#app-adapters) 說明應用程式如何透過本機 `@/components/*` 配接器封裝 Toolkit 元件。
+- [Shell 與 Hook](/docs/toolkit-ui#shell-hooks) 涵蓋頁首動作、行動裝置 Hook、Toast 和小型應用程式 Shell 輔助工具。
+- [元件 API](/docs/components) 仍是公開 React 匯出的低階參考。
+
+## 設計規則 {#design-rule}
+
+當行為在各應用程式間重複出現，且使用者期待標準體驗時，請使用 Toolkit：分享、設定、團隊、評論、歷程和智慧代理進度不應在每個範本中略有不同。請將領域特定的資料、工作流程、標籤和視覺樣式保留在應用程式中。
+
+## 下一步
+
+- [**Toolkit UI 原語**](/docs/toolkit-ui) — 共用原語、應用程式配接器和 Shell Hook。
+- [**分享套件**](/docs/toolkit-sharing) — 資源、分享對話框和可見性的良好起點。
+- [**建立範本**](/docs/creating-templates) — 端到端建立範本，並了解套件如何融入其中。
+- [**元件 API**](/docs/components) — 所有公開 React 匯出的參考。
+- [**套件生命週期**](/docs/package-lifecycle) — 安全地檢查、新增和彈出由資訊清單驅動的 Toolkit 能力模組。

package/corpus/core/docs/content/locales/zh-TW/toolkit-capability-packages.mdx

@@ -0,0 +1,21 @@
+---
+title: "能力套件"
+description: "管理領域能力及其清單驅動生命週期，而不將其併入 Toolkit。"
+---
+
+# 能力套件
+
+Toolkit 提供跨應用程式產品基礎；能力套件提供受限領域、actions、skills 和生命週期中繼資料。Scheduling 和 Creative Context 是獨立能力套件，而不是 Toolkit 功能套件。
+
+`@agent-native/scheduling` 參與通用清單試行。請以各套件本機文件與生命週期清單作為擴充點和歸屬的來源。
+
+- [Scheduling 套件文件](https://github.com/BuilderIO/agent-native/tree/main/packages/scheduling/docs)
+- [Creative Context 套件文件](https://github.com/BuilderIO/agent-native/tree/main/packages/creative-context/docs)
+
+```bash
+agent-native package inspect @agent-native/scheduling
+agent-native package add @agent-native/scheduling --apply
+agent-native package eject @agent-native/scheduling --apply
+```
+
+檢查、預演和 eject 規則見[套件生命週期](/docs/package-lifecycle)。

package/corpus/core/docs/content/locales/zh-TW/toolkit-context-knowledge.mdx

@@ -0,0 +1,12 @@
+---
+title: "脈絡與知識"
+description: "在引擎、資料存取和可重用呈現之間維持正確邊界，建立面向智慧代理的脈絡表面。"
+---
+
+# 脈絡與知識
+
+Core 負責應用程式狀態、範圍受限存取與 Context X-Ray 引擎。Toolkit 提供可重用呈現；應用程式負責領域記錄、分類與選擇規則。
+
+Context X-Ray 引擎仍歸 Core。可用 Toolkit 統一呈現脈絡，但狀態和存取決策應保留在 Core 與 actions 中。[Context awareness](/docs/context-awareness) 讓導覽、選取和聚焦物件對智慧代理可見；[Resources](/docs/toolkit-resources) 處理檔案與附件。
+
+脈絡不能取代存取控制。擷取提供者知識前必須保留資源與憑證檢查。

package/corpus/core/docs/content/locales/zh-TW/toolkit-editors-canvases.mdx

@@ -0,0 +1,17 @@
+---
+title: "編輯器與畫布"
+description: "在 Core 相容路徑、範本模式與 Toolkit 原語之間作出清楚選擇。"
+---
+
+# 編輯器與畫布
+
+編輯器和畫布是相關的產品表面，不應將任何一項當成唯一旗艦功能。
+
+| 表面       | 目前歸屬                                                |
+| ---------- | ------------------------------------------------------- |
+| 豐富編輯器 | 歸 Toolkit，Core 保留相容性重新匯出。                   |
+| Blocks     | 此階段仍歸 Core。                                       |
+| Design     | 具 `design-tweaks` 的範本模式，並非完整即插即用編輯器。 |
+| 畫布呈現   | Toolkit 或應用程式的組合。                              |
+
+請從 `@agent-native/toolkit/editor` 匯入編輯器。舊 Core 路徑繼續作為相容性重新匯出。結構、命令與持久化仍由應用程式負責。Blocks 仍歸 Core，但 Toolkit 區段是可重用 UI 的統一目錄，因此文件集中在這裡。

package/corpus/core/docs/content/toolkit-capability-packages.mdx

@@ -0,0 +1,52 @@
+---
+title: "Toolkit Capability Modules"
+description: "Install Toolkit domain capabilities on demand while preserving their package-level dependency and lifecycle boundaries."
+---
+
+# Toolkit capability modules
+
+Toolkit capability modules add reusable domain behavior on demand. They share
+one Toolkit discovery shelf while staying in separate npm packages, so an app
+only installs the bounded domain model, actions, skills, dependencies, and
+lifecycle metadata it needs.
+
+## Current package boundary
+
+| Package                          | Toolkit module                                      | Lifecycle                                                                                               |
+| -------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| `@agent-native/scheduling`       | Scheduling and booking, installed on demand         | Supports the generic manifest lifecycle pilot; package-local docs live under `docs/`.                   |
+| `@agent-native/creative-context` | Governed creative context, installed on demand      | Publishes its own `agent-native.package.json` and package-local `docs/llms.txt` / `docs/llms-full.txt`. |
+| `@agent-native/pinpoint`         | Visual feedback and annotation, installed on demand | Package-local setup and agent integration live in its README and packaged assets.                       |
+
+These modules belong to the Toolkit brand without being folded into the
+`@agent-native/toolkit` npm package. Use each published package's README and,
+where present, `docs/` bundle and `agent-native.package.json` lifecycle manifest
+as the source of truth for setup, contribution points, and ownership.
+
+Dispatch is the workspace control plane and remains a separate product.
+
+- [Scheduling package docs](https://github.com/BuilderIO/agent-native/tree/main/packages/scheduling/docs)
+- [Creative Context package docs](https://github.com/BuilderIO/agent-native/tree/main/packages/creative-context/docs)
+- [Pinpoint package README](https://github.com/BuilderIO/agent-native/tree/main/packages/pinpoint)
+
+## Lifecycle manifests
+
+Each manifest describes static contributions such as actions, schema entry
+points, skills, required secret names, and peer providers. Inspect before
+writing, then use the explicit apply step:
+
+```bash
+agent-native package inspect @agent-native/scheduling
+agent-native package add @agent-native/scheduling --apply
+agent-native package eject @agent-native/scheduling --apply
+```
+
+See [Package Lifecycle](/docs/package-lifecycle) for the safety, dry-run, and
+eject rules. See [Scheduling](/docs/template-calendar) for a product-level
+example; it is not a substitute for the package-local contract.
+
+## Related docs
+
+- [Toolkit overview](/docs/agent-native-toolkit) — the unified discovery shelf.
+- [Package Lifecycle](/docs/package-lifecycle) — manifest inspection, add, and eject.
+- [Recurring jobs](/docs/recurring-jobs) — runtime scheduling is different from the Scheduling package.

package/corpus/core/docs/content/toolkit-context-knowledge.mdx

@@ -0,0 +1,46 @@
+---
+title: "Context & Knowledge"
+description: "Build agent-aware context and knowledge surfaces while keeping engines, data access, and reusable presentation in their proper layers."
+---
+
+# Context & knowledge
+
+Context and knowledge are shared responsibilities: the runtime makes state and
+access durable, Toolkit presents reusable surfaces, and each app owns the
+domain records that make context useful.
+
+## Ownership boundary
+
+| Layer   | Owns                                                                                       |
+| ------- | ------------------------------------------------------------------------------------------ |
+| Core    | Application state, scoped data access, Context X-Ray engine, resource and block contracts. |
+| Toolkit | Reusable Context X-Ray presentation and agent-facing context UI.                           |
+| App     | Domain knowledge, selection rules, resource taxonomy, and product-specific context.        |
+
+The Context X-Ray engine remains Core-owned. Use Toolkit presentation to show
+that context consistently, but keep the actual app-state and access decisions
+on the Core/action surface.
+
+Import the controlled presentation views from `@agent-native/toolkit/context-ui`.
+Core's existing Context X-Ray components remain adapters that connect those
+views to runtime state and mutations. Both are documented in this Toolkit
+section because together they form one reusable product surface.
+
+## Build a useful context surface
+
+Use [context awareness](/docs/context-awareness) to make navigation,
+selection, and focused objects visible to the agent. Use [Resources](/docs/toolkit-resources)
+for browsable files and attachments, and use scoped actions for every read or
+write. Context should describe what the user is working on without bypassing
+the app's access model.
+
+For knowledge that comes from a provider, preserve provider credentials and
+resource access checks before exposing retrieval to the agent. Do not treat a
+presentation component as an authorization boundary.
+
+## Related docs
+
+- [Agent UX](/docs/toolkit-agent-ux) — composer context chips, approvals, and runs.
+- [Resources](/docs/toolkit-resources) — resource trees, search, and attachments.
+- [Context awareness](/docs/context-awareness) — application state shared with the agent.
+- [Security](/docs/security) — scoped access and credential handling.

package/corpus/core/docs/content/toolkit-editors-canvases.mdx

@@ -0,0 +1,55 @@
+---
+title: "Editors & Canvases"
+description: "Choose reusable editor and canvas surfaces without confusing Core compatibility APIs, template patterns, and Toolkit primitives."
+---
+
+# Editors & canvases
+
+Editors and canvases are related product surfaces, not one flagship feature.
+Choose the smallest reusable layer that matches the interaction your app owns.
+
+## Ownership today
+
+| Surface             | Current owner and maturity                     | Use it when                                                                                                      |
+| ------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| Rich editor         | Toolkit, with Core compatibility re-exports    | You need portable rich editing, markdown, slash commands, images, drag handles, or collaboration reconciliation. |
+| Blocks              | Core in this phase                             | You need registered, structured blocks and their runtime contract.                                               |
+| Design              | Template pattern plus reusable `design-tweaks` | You are building a Design-like workflow and can own its domain behavior.                                         |
+| Canvas presentation | Toolkit or app composition                     | You need reusable UI around an app-specific canvas model.                                                        |
+
+## Choose deliberately
+
+Import the portable editor surface from `@agent-native/toolkit/editor`:
+
+```tsx
+import {
+  RichMarkdownEditor,
+  createSharedEditorExtensions,
+  useCollabReconcile,
+} from "@agent-native/toolkit/editor";
+```
+
+Existing imports from `@agent-native/core/client` and
+`@agent-native/core/client/editor` continue to work as compatibility
+re-exports. Keep app-specific schemas, commands, persistence, upload actions,
+and registry adapters in your app or Core as appropriate.
+
+Design is not a drop-in replacement for an editor or general canvas. The
+[Design template](/docs/template-design) demonstrates a complete product
+pattern; `design-tweaks` are reusable presentation adjustments within that
+pattern. Reuse them when they fit, but do not assume they supply a complete
+canvas data model, collaboration model, or workflow.
+
+Blocks remain Core-owned because the browser and server contracts share one
+implementation. They are documented here alongside editors and canvases
+because Toolkit docs are the discovery catalog for reusable UI, regardless of
+which package currently owns the implementation. Register and render blocks
+through the Core contract so the agent and UI share the same structured
+vocabulary.
+
+## Related docs
+
+- [Toolkit overview](/docs/agent-native-toolkit) — the full catalog and ownership boundary.
+- [Component API](/docs/components) — public React exports and rich-editor compatibility details.
+- [Real-time collaboration](/docs/real-time-collaboration) — presence and collaborative editing foundations.
+- [Design template](/docs/template-design) — the Design product pattern.