@agent-native/core 0.109.3 → 0.110.0

package/corpus/core/docs/content/locales/pt-BR/drop-in-agent.mdx

@@ -105,7 +105,7 @@ as crianças ficam na área principal do aplicativo. O chat do agente é o paine
   filename="app/root.tsx"
   language="tsx"
   code={
-    'import { Outlet } from "react-router";\nimport { AgentSidebar, AgentToggleButton } from "@agent-native/core/client";\n\nexport default function Root() {\n  return (\n    <AgentSidebar\n      emptyStateText="Como posso ajudar?"\n      suggestions={[\n        "Summarize my inbox",\n        "Draft a reply to the latest email",\n        "Show me yesterday\'s signup numbers",\n      ]}\n      dynamicSuggestions\n      defaultSidebarWidth={420}\n      position="right"\n    >\n      <header>\n        <AgentToggleButton />\n      </header>\n\n      <main>\n        <Outlet />\n      </main>\n    </AgentSidebar>\n  );\n}'
+    'import { Outlet } from "react-router";\nimport { AgentSidebar, AgentToggleButton } from "@agent-native/core/client/agent-chat";\n\nexport default function Root() {\n  return (\n    <AgentSidebar\n      emptyStateText="Como posso ajudar?"\n      suggestions={[\n        "Summarize my inbox",\n        "Draft a reply to the latest email",\n        "Show me yesterday\'s signup numbers",\n      ]}\n      dynamicSuggestions\n      defaultSidebarWidth={420}\n      position="right"\n    >\n      <header>\n        <AgentToggleButton />\n      </header>\n\n      <main>\n        <Outlet />\n      </main>\n    </AgentSidebar>\n  );\n}'
   }
   annotations={[
     {
@@ -154,8 +154,7 @@ Quando você precisar de controle total sobre o layout — uma rota `/chat` dedi
 
 ```tsx
 // app/routes/agent.tsx
-import { AgentPanel } from "@agent-native/core/client";
-
+import { AgentPanel } from "@agent-native/core/client/agent-chat";
 export default function AgentRoute() {
   return (
     <div className="h-screen">
@@ -182,8 +181,7 @@ Acessórios completos: `AgentPanelProps` em `@agent-native/core/client`.
 Um botão que transfere o trabalho para o agente (em vez de executar uma chamada `llm()` em linha — o antipadrão do [ladder](/docs/what-is-agent-native#the-ladder)):
 
 ```tsx
-import { sendToAgentChat } from "@agent-native/core/client";
-
+import { sendToAgentChat } from "@agent-native/core/client/agent-chat";
 <Button
   onClick={() =>
     sendToAgentChat({
@@ -232,8 +230,7 @@ As chamadas `sendToAgentChat()` são encaminhadas para o chat do host quando hou
 Se você deseja um estado de carregamento, use o gancho `useSendToAgentChat()` — ele retorna `send` e `isGenerating`:
 
 ```ts
-import { useSendToAgentChat } from "@agent-native/core/client";
-
+import { useSendToAgentChat } from "@agent-native/core/client/agent-chat";
 const { send, isGenerating } = useSendToAgentChat();
 ```
 
@@ -267,8 +264,7 @@ o código do cliente não aprende um segundo transporte ad hoc.
 Quando o UI precisar executar a mesma operação que uma ferramenta de agente executaria — linha 3 do [ladder](/docs/what-is-agent-native#rung-three) — use `useActionMutation`:
 
 ```tsx
-import { useActionMutation } from "@agent-native/core/client";
-
+import { useActionMutation } from "@agent-native/core/client/hooks";
 const { mutate, isPending } = useActionMutation("reply-to-email");
 
 <Button onClick={() => mutate({ emailId, body: "Thanks!" })}>
@@ -298,8 +294,7 @@ import {
   AgentSidebar,
   AgentToggleButton,
   sendToAgentChat,
-} from "@agent-native/core/client";
-
+} from "@agent-native/core/client/agent-chat";
 export default function Root() {
   return (
     <AgentSidebar suggestions={["Draft a reply", "Summarize selection"]}>

package/corpus/core/docs/content/locales/pt-BR/embedding-sdk.mdx

@@ -118,8 +118,7 @@ No cliente:
 import {
   AgentNativeEmbedded,
   defineClientAction,
-} from "@agent-native/core/client";
-
+} from "@agent-native/core/client/host";
 export function BuilderAppShell({ children, content, editor }) {
   return (
     <AgentNativeEmbedded
@@ -297,8 +296,10 @@ for await (const chunk of sendMessage(
 Para aplicativos secundários independentes ou iframes de origem cruzada, use o `<AgentNative />` de nível inferior. Ele renderiza o sidecar iframe e o contexto da página de fios, o cliente ativo actions e os comandos de atualização/navegação do host em um só lugar:
 
 ```tsx
-import { AgentNative, defineClientAction } from "@agent-native/core/client";
-
+import {
+  AgentNative,
+  defineClientAction,
+} from "@agent-native/core/client/host";
 export function AssistantDock({ customer, sessionToken }) {
   return (
     <AgentNative
@@ -385,8 +386,7 @@ import {
   requestAgentNativeHostContext,
   runAgentNativeHostAction,
   sendAgentNativeHostCommand,
-} from "@agent-native/core/client";
-
+} from "@agent-native/core/client/host";
 announceAgentNativeFrameReady({ hostOrigin: "https://app.example.com" });
 
 const context = await requestAgentNativeHostContext({
@@ -463,8 +463,7 @@ No aplicativo sidecar, inicie a ponte de sessão do navegador uma vez quando o i
 
 ```tsx
 import { useEffect } from "react";
-import { startAgentNativeBrowserSessionBridge } from "@agent-native/core/client";
-
+import { startAgentNativeBrowserSessionBridge } from "@agent-native/core/client/host";
 export function SidecarRuntime() {
   useEffect(() => {
     const bridge = startAgentNativeBrowserSessionBridge({
@@ -516,8 +515,7 @@ import {
   AgentNativeExtensionSlot,
   createHttpAgentNativeExtensionStorage,
   defineClientAction,
-} from "@agent-native/core/client";
-
+} from "@agent-native/core/client/host";
 const storage = createHttpAgentNativeExtensionStorage({
   endpoint: "/api/agent-native/extensions/storage",
   headers: () => ({ Authorization: `Bearer ${sessionToken()}` }),

package/corpus/core/docs/content/locales/pt-BR/internationalization.mdx

@@ -15,7 +15,11 @@ Inglês quando um aplicativo ainda não traduziu uma string.
 Use o provedor por meio de `AppProviders`:
 
 ```tsx
-import { AppProviders, getLocaleInitScript } from "@agent-native/core/client";
+import {
+  AppProviders,
+} from "@agent-native/core/client/hooks"import {
+  getLocaleInitScript,
+} from "@agent-native/core/client/i18n"
 import { i18nCatalog } from "./i18n";
 
 const LOCALE_INIT_SCRIPT = getLocaleInitScript();
@@ -42,8 +46,7 @@ Cada modelo localizado mantém catálogos em `app/i18n/`:
 ```ts
 // app/i18n/index.ts
 import enUS from "./en-US";
-import type { AgentNativeI18nCatalog } from "@agent-native/core/client";
-
+import type { AgentNativeI18nCatalog } from "@agent-native/core/client/i18n";
 export const i18nCatalog = {
   sourceLocale: "en-US",
   messages: enUS,
@@ -71,10 +74,10 @@ o ícone do idioma do cabeçalho é apenas um atalho.
 ```tsx
 import {
   LanguagePicker,
-  openAgentSettings,
   useT,
-} from "@agent-native/core/client";
-
+} from "@agent-native/core/client/i18n"import {
+  openAgentSettings,
+} from "@agent-native/core/client/navigation"
 function SettingsPage() {
   const t = useT();
   return (

package/corpus/core/docs/content/locales/pt-BR/key-concepts.mdx

@@ -255,8 +255,7 @@ O UI nunca chama um LLM diretamente. Quando um usuário clica em “Gerar gráfi
 
 ```ts
 // In a React component — delegate AI work to the agent
-import { sendToAgentChat } from "@agent-native/core/client";
-
+import { sendToAgentChat } from "@agent-native/core/client/agent-chat";
 sendToAgentChat({
   message: "Generate a chart showing signups by source",
   context: "Dashboard ID: main, date range: last 30 days",
@@ -307,8 +306,7 @@ As alterações do banco de dados são sincronizadas com UI por meio de `useDbSy
 
 ```ts
 // Client: subscribe to agent/UI data changes once near the app shell
-import { useDbSync } from "@agent-native/core/client";
-
+import { useDbSync } from "@agent-native/core/client/hooks";
 useDbSync({ queryClient });
 ```
 

package/corpus/core/docs/content/locales/pt-BR/observability.mdx

@@ -96,8 +96,7 @@ Adicione o painel a qualquer modelo com uma única rota:
 
 ```tsx
 // app/routes/observability.tsx
-import { ObservabilityDashboard } from "@agent-native/core/client";
-
+import { ObservabilityDashboard } from "@agent-native/core/client/observability";
 export default function ObservabilityPage() {
   return (
     <div className="min-h-screen bg-background p-6">

package/corpus/core/docs/content/locales/pt-BR/package-lifecycle.mdx

@@ -19,3 +19,9 @@ Adicionar e ejetar são simulações por padrão. `--apply` permite gravações
 executa o gerenciador de pacotes. A CLI recusa colisões e layouts desconhecidos
 e restaura arquivos e lockfiles se a instalação falhar. Apenas Scheduling pode
 ser ejetado neste piloto; Pinpoint fica adiado.
+
+## Migrações
+
+Pacotes publicados incluem `migration-manifest.json` para caminhos e símbolos movidos. `npx @agent-native/core@latest upgrade --codemods` mostra o diff; após revisar, use `--yes`. Em CI execute `agent-native doctor --only migration-manifest`; não há opt-out.
+
+Entradas `planned` podem ser publicadas antes do destino; aparecem como avisos não bloqueantes e o codemod não as reescreve. Um movimento ativo só é reescrito quando o export de destino está instalado.

package/corpus/core/docs/content/locales/pt-BR/real-time-collaboration.mdx

@@ -261,7 +261,7 @@ export default createCollabPlugin({
 ### 4. Use o gancho do cliente
 
 ```ts
-import { useCollaborativeDoc } from "@agent-native/core/client";
+import { useCollaborativeDoc } from "@agent-native/core/client/collab";
 import { emailToColor, emailToName } from "@agent-native/toolkit/collab-ui";
 
 const TAB_ID = generateTabId(); // or Math.random().toString(36)
@@ -434,8 +434,7 @@ As mudanças no estado de reconhecimento agora se propagam em aproximadamente 15
 Retorna uma lista reativa de participantes remotos e um configurador para a carga de presença local:
 
 ```ts
-import { usePresence } from "@agent-native/core/client";
-
+import { usePresence } from "@agent-native/core/client/collab";
 const { others, setPresence } = usePresence(awareness, ydoc?.clientID);
 
 // Publish cursor position (normalized 0–1)
@@ -497,8 +496,7 @@ import { RemoteSelectionRings } from "@agent-native/toolkit/collab-ui";
 Invoque um retorno de chamada sempre que a janela de visualização do participante seguido for alterada:
 
 ```ts
-import { useFollowUser } from "@agent-native/core/client";
-
+import { useFollowUser } from "@agent-native/core/client/collab";
 const { isFollowing, stopFollowing } = useFollowUser({
   others,
   followingId, // null to stop following
@@ -532,8 +530,7 @@ O componente `PresenceBar` agora aceita adereços opcionais de modo de acompanha
 ### Ajudantes de coordenadas normalizadas {#norm-coords}
 
 ```ts
-import { toNormalized, fromNormalized } from "@agent-native/core/client";
-
+import { toNormalized, fromNormalized } from "@agent-native/core/client/collab";
 // In a pointer event handler:
 const norm = toNormalized(
   e.clientX,

package/corpus/core/docs/content/locales/pt-BR/sharing.mdx

@@ -122,8 +122,7 @@ Todo recurso compartilhável recebe um botão de compartilhamento em seu cabeça
 O botão de compartilhamento é uma importação única:
 
 ```tsx
-import { ShareButton } from "@agent-native/core/client";
-
+import { ShareButton } from "@agent-native/core/client/sharing";
 <ShareButton
   resourceType="deck"
   resourceId={deck.id}

package/corpus/core/docs/content/locales/pt-BR/template-chat.mdx

@@ -164,8 +164,7 @@ A página de bate-papo é intencionalmente estreita:
 
 ```tsx
 // app/routes/_index.tsx
-import { AgentChatSurface } from "@agent-native/core/client";
-
+import { AgentChatSurface } from "@agent-native/core/client/agent-chat";
 export default function ChatRoute() {
   return (
     <AgentChatSurface

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

@@ -0,0 +1,21 @@
+---
+title: "Pacotes de capacidade"
+description: "Gerencie capacidades de domínio e seu ciclo de vida por manifesto sem incorporá-las ao Toolkit."
+---
+
+# Pacotes de capacidade
+
+O Toolkit fornece fundações de produto transversais; pacotes de capacidade trazem domínio delimitado, actions, skills e metadados de ciclo de vida. Scheduling e Creative Context permanecem pacotes de capacidade separados, não kits do Toolkit.
+
+`@agent-native/scheduling` participa do piloto do manifesto genérico. Consulte a documentação e o manifesto locais de cada pacote para pontos de extensão e responsabilidade.
+
+- [Documentação do pacote Scheduling](https://github.com/BuilderIO/agent-native/tree/main/packages/scheduling/docs)
+- [Documentação do pacote 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
+```
+
+Veja [Ciclo de vida de pacotes](/docs/package-lifecycle) para inspeção, simulação e eject.

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

@@ -0,0 +1,12 @@
+---
+title: "Contexto e conhecimento"
+description: "Crie superfícies de contexto para agentes respeitando as camadas de mecanismo, acesso a dados e apresentação reutilizável."
+---
+
+# Contexto e conhecimento
+
+O Core mantém estado da aplicação, acesso com escopo e o mecanismo Context X-Ray. O Toolkit fornece a apresentação reutilizável; o app mantém registros de domínio, taxonomia e regras de seleção.
+
+O mecanismo Context X-Ray continua no Core. Use a apresentação do Toolkit para contexto consistente, mas mantenha decisões de estado e acesso no Core e nas actions. [Context awareness](/docs/context-awareness) expõe navegação, seleção e objeto em foco ao agente; [Resources](/docs/toolkit-resources) cobre arquivos e anexos.
+
+Contexto não substitui controles de acesso. Preserve verificações de recurso e credencial antes de recuperar conhecimento de provedores.

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

@@ -0,0 +1,17 @@
+---
+title: "Editores e canvases"
+description: "Escolha superfícies reutilizáveis sem confundir compatibilidade do Core, padrões de template e primitivas do Toolkit."
+---
+
+# Editores e canvases
+
+Editores e canvases são superfícies relacionadas, não um único recurso principal.
+
+| Superfície             | Responsabilidade atual                                                          |
+| ---------------------- | ------------------------------------------------------------------------------- |
+| Editor rico            | Toolkit, com reexportações de compatibilidade pelo Core.                        |
+| Blocos                 | Core nesta fase.                                                                |
+| Design                 | Padrão de template com `design-tweaks`, não um editor completo pronto para uso. |
+| Apresentação de canvas | Composição do Toolkit ou do app.                                                |
+
+Importe o editor de `@agent-native/toolkit/editor`. Os caminhos antigos do Core continuam como reexportações de compatibilidade. Mantenha esquemas, comandos e persistência no app. Os blocos ficam no Core, mas são documentados aqui porque a seção Toolkit é o catálogo de UI reutilizável.

package/corpus/core/docs/content/locales/pt-BR/tracking.mdx

@@ -176,8 +176,7 @@ Identity is resolved **server-side** from the session — browser code never pas
 </Endpoint>
 
 ```ts
-import { track } from "@agent-native/core/client";
-
+import { track } from "@agent-native/core/client/analytics";
 // e.g. inside a click handler or effect
 track("checkout.completed", { total: 49.99, items: 3 });
 ```
@@ -196,8 +195,7 @@ Isso é diferente da telemetria interna do navegador da estrutura (`trackEvent()
 Aplicativos Agent Native podem optar por um replay de sessão do navegador nativo sem adicionar um segundo SDK de análise. Chame `configureTracking()` uma vez na raiz do navegador e passe a chave pública do Analytics mais o endpoint do coletor:
 
 ```ts
-import { configureTracking } from "@agent-native/core/client";
-
+import { configureTracking } from "@agent-native/core/client/analytics";
 configureTracking({
   key: "anpk_...",
   endpoint: "https://analytics.example.com/api/analytics/track",

package/corpus/core/docs/content/locales/pt-BR/what-is-agent-native.mdx

@@ -290,8 +290,7 @@ const { mutate } = useActionMutation("reply-to-email");
 
 ```tsx
 // And the agent panel mounted anywhere in your app
-import { AgentSidebar } from "@agent-native/core/client";
-
+import { AgentSidebar } from "@agent-native/core/client/agent-chat";
 <AgentSidebar />;
 ```
 

package/corpus/core/docs/content/locales/zh-CN/actions.mdx

@@ -441,8 +441,7 @@ export default defineAction({
 对于改变状态的actions：
 
 ```tsx
-import { useActionMutation } from "@agent-native/core/client";
-
+import { useActionMutation } from "@agent-native/core/client/hooks";
 const { mutate, isPending } = useActionMutation("reply-to-email");
 
 <Button
@@ -460,8 +459,7 @@ const { mutate, isPending } = useActionMutation("reply-to-email");
 对于只读 GET actions：
 
 ```ts
-import { useActionQuery } from "@agent-native/core/client";
-
+import { useActionQuery } from "@agent-native/core/client/hooks";
 const { data, isLoading } = useActionQuery("get-lead", { leadId });
 ```
 

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/agent-surfaces.mdx

@@ -14,8 +14,7 @@ search: "无头代理丰富聊天完整应用程序 BYO 代理运行时 AgentCha
 页面，而不必重复这些流程。
 
 ```tsx filename="app/routes/agent.tsx"
-import { AgentTabsPage } from "@agent-native/core/client";
-
+import { AgentTabsPage } from "@agent-native/core/client/agent-chat";
 export default function AgentRoute() {
   return <AgentTabsPage />;
 }
@@ -406,8 +405,7 @@ export default createAgentNativeEmbeddedPlugin({
 React sidecar 传递页面上下文和主机命令：
 
 ```tsx
-import { AgentNativeEmbedded } from "@agent-native/core/client";
-
+import { AgentNativeEmbedded } from "@agent-native/core/client/host";
 export function AppShell({ children }) {
   return (
     <AgentNativeEmbedded

package/corpus/core/docs/content/locales/zh-CN/audit-log.mdx

@@ -82,8 +82,7 @@ export default defineAction({
 通过使用 `useActionQuery` 从 UI 调用 `list-audit-events` 来构建活动源或“谁更改了此”行 - 切勿手写对审核表的提取：
 
 ```tsx
-import { useActionQuery } from "@agent-native/core/client";
-
+import { useActionQuery } from "@agent-native/core/client/hooks";
 const { data } = useActionQuery("list-audit-events", {
   targetType: "recording",
   targetId: recordingId,

package/corpus/core/docs/content/locales/zh-CN/authentication.mdx

@@ -363,8 +363,9 @@ interface AuthSession {
 在客户端上，使用 `useSession()` 挂钩：
 
 ```ts
-import { useSession } from "@agent-native/core/client";
-
+import {
+  useSession,
+} from "@agent-native/core/client/hooks"
 function MyComponent() {
   const { session, isLoading } = useSession();
   if (isLoading) return <p>Loading...</p>;