@agent-native/core 0.109.3 → 0.110.0

package/corpus/core/docs/content/locales/zh-TW/real-time-collaboration.mdx

@@ -252,7 +252,7 @@ export default createCollabPlugin({
 ### 4.使用用戶端鉤子
 
 ```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)
@@ -425,8 +425,7 @@ import {
 返回遠端參與者的反應清單和本機線上狀態有效負載的設定器：
 
 ```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)
@@ -488,8 +487,7 @@ import { RemoteSelectionRings } from "@agent-native/toolkit/collab-ui";
 每當跟隨的參與者的視口發生變化時呼叫回調：
 
 ```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
@@ -523,8 +521,7 @@ const { isFollowing, stopFollowing } = useFollowUser({
 ### 標準化坐標助手 {#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/zh-TW/sharing.mdx

@@ -122,8 +122,7 @@ description: "框架內建了熟悉且一致的共享方式。使用者建立的
 共用按鈕是一次匯入：
 
 ```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/zh-TW/template-chat.mdx

@@ -162,8 +162,7 @@ npx @agent-native/core@latest create my-agent --headless
 
 ```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/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/locales/zh-TW/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 @@ track("checkout.completed", { total: 49.99, items: 3 });
 Agent Native 應用程式可以選擇加入第一方瀏覽器工作階段重播，而無需新增第二個分析 SDK。在瀏覽器根目錄中呼叫一次 `configureTracking()`，並傳入 Analytics 公開金鑰以及收集器端點：
 
 ```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/zh-TW/what-is-agent-native.mdx

@@ -283,8 +283,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/observability.mdx

@@ -93,8 +93,7 @@ No code changes needed. The instrumentation hooks into `production-agent.ts` tra
 Add the dashboard to any template with a single route:
 
 ```tsx filename="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/package-lifecycle.mdx

@@ -37,6 +37,35 @@ imports a package's JavaScript manifest and passes `--ignore-scripts` while
 downloading an uninstalled package archive. Reports show credential key names,
 never credential values.
 
+## Migration manifests and tombstones
+
+Published framework packages ship a `migration-manifest.json`. It records moved
+package specifiers and renamed symbols before a breaking release. When a path is
+removed, its tombstone module remains in the package long enough to throw an
+actionable error that names the replacement and the exact migration command.
+
+Preview the manifest-driven rewrite before making any manual import edits:
+
+```bash
+npx @agent-native/core@latest upgrade --codemods
+```
+
+The command is dry-run by default and prints the proposed diff. After review,
+apply the same rewrite explicitly:
+
+```bash
+npx @agent-native/core@latest upgrade --codemods --yes
+```
+
+Run `agent-native doctor --only migration-manifest` in CI or before an upgrade
+to identify imports that are listed in installed manifests. The guard has no
+opt-out: migrate the import with the codemod instead of suppressing a future
+breaking change.
+
+Manifest entries can be `planned` before their destination ships. Doctor reports
+those as non-blocking warnings, and the codemod leaves them unchanged. An active
+move is rewritten only when the installed destination package exports its target.
+
 ## Scheduling pilot
 
 `@agent-native/scheduling` is the first package with the generic manifest. Add

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

@@ -260,7 +260,11 @@ export default createCollabPlugin({
 ### 4. Use the client hook
 
 ```ts
-import { generateTabId, useCollaborativeDoc } from "@agent-native/core/client";
+import {
+  generateTabId,
+} from "@agent-native/core/client/agent-chat"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)
@@ -420,8 +424,7 @@ Awareness state changes propagate at ~150ms instead of waiting for the full poll
 Returns a reactive list of remote participants and a setter for the local presence payload:
 
 ```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)
@@ -483,8 +486,7 @@ import { RemoteSelectionRings } from "@agent-native/toolkit/collab-ui";
 Invoke a callback whenever the followed participant's viewport changes:
 
 ```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
@@ -518,8 +520,7 @@ The `PresenceBar` component accepts optional follow-mode props:
 ### Normalized coordinate helpers {#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/sharing.mdx

@@ -122,8 +122,7 @@ Every shareable resource gets a share button in its header. Clicking it opens a
 The share button is a single import:
 
 ```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/template-chat.mdx

@@ -163,8 +163,7 @@ Use it for scheduled jobs, queues, CLI loops, or external-agent workflows where
 The chat page is intentionally thin:
 
 ```tsx filename="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/toolkit-agent-ux.mdx

@@ -39,9 +39,10 @@ plus a header trigger showing live run progress.
 ```tsx
 import {
   AgentToggleButton,
-  PromptComposer,
   sendToAgentChat,
-} from "@agent-native/core/client";
+} from "@agent-native/core/client/agent-chat"import {
+  PromptComposer,
+} from "@agent-native/core/client/composer"
 import { RunsTray } from "@agent-native/core/client/progress";
 
 export function AgentDock() {

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.

package/corpus/core/docs/content/toolkit-observability.mdx

@@ -40,8 +40,7 @@ usage/spend/feedback data the dashboard reads back:
 import {
   ObservabilityDashboard,
   ThumbsFeedback,
-} from "@agent-native/core/client";
-
+} 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/toolkit-settings.mdx

@@ -44,10 +44,10 @@ tabs; framework tabs should not be hidden in a second settings universe.
 ```tsx
 import {
   LanguagePicker,
+} from "@agent-native/core/client/i18n"import {
   SettingsTabsPage,
   useAgentSettingsTabs,
-} from "@agent-native/core/client";
-
+} from "@agent-native/core/client/settings"
 export default function SettingsRoute() {
   const agentSettingsTabs = useAgentSettingsTabs();
   return (

package/corpus/core/docs/content/toolkit-sharing.mdx

@@ -64,8 +64,11 @@ registerShareableResource({
 Render the standard controls where users decide access:
 
 ```tsx
-import { ShareButton, VisibilityBadge } from "@agent-native/core/client";
-
+import {
+  ShareButton,
+} from "@agent-native/core/client/sharing"import {
+  VisibilityBadge,
+} from "@agent-native/toolkit/sharing"
 <VisibilityBadge visibility={dashboard.visibility} />
 <ShareButton resourceType="dashboard" resourceId={dashboard.id} />
 ```

package/corpus/core/docs/content/tracking.mdx

@@ -175,8 +175,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 });
 ```
@@ -195,8 +194,7 @@ This is distinct from the framework's internal browser telemetry (`trackEvent()`
 Agent Native apps can opt into first-party browser session replay without adding a second analytics SDK. Call `configureTracking()` once in the browser root and pass the Analytics public key plus collector endpoint:
 
 ```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/what-is-agent-native.mdx

@@ -384,8 +384,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 />;
 ```