@agent-native/core 0.207.0 → 0.207.1-nightly-20261012011809

package/docs/content/toolkit-history.mdx

@@ -1,13 +1,11 @@
 ---
 title: "History Kit"
-description: "Version history, audit log, undo/redo, restore flows, and what-changed surfaces."
+description: "Version and audit APIs, undo/redo foundations, and app-owned history UI."
 ---
 
 # History Kit
 
-The History Kit helps users answer the questions that matter after humans and
-agents edit together: what changed, who changed it, can I undo it, and can I
-restore an older version?
+The History Kit provides versioning, access-scoped history actions, and undo/redo foundations. Apps compose their own timelines, previews, diffs, and restore controls around these APIs; Toolkit does not ship a drop-in history panel.
 
 <WireframeBlock id="doc-block-toolkit-history">
   <Screen
@@ -18,19 +16,20 @@ restore an older version?
   />
 </WireframeBlock>
 
+This mock shows one app-owned history interface built from the APIs below. The timeline, diff summary, and restore button are examples, not exported Toolkit components.
+
 ## Pieces {#pieces}
 
 | Piece                         | Purpose                                                                                                                               |
 | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
 | `registerVersionedResource()` | Register a resource type, access resolver, optional `getSnapshot()`, and optional `restoreSnapshot()` handler.                        |
 | Version actions               | `create-resource-version`, `list-resource-versions`, `get-resource-version`, `restore-resource-version`, and `list-resource-history`. |
-| `VersionHistoryPanel`         | Drop-in React panel for listing versions and restoring a selected version.                                                            |
-| `HistoryTimeline`             | Controlled presentational timeline for custom history layouts.                                                                        |
+| App-owned history UI          | Compose a timeline, preview, diff, or restore flow with the history APIs.                                                             |
 | History hooks                 | `useResourceVersions()`, `useResourceHistory()`, `useCreateResourceVersion()`, and `useRestoreResourceVersion()`.                     |
 | Audit log                     | Durable record of human and agent actions, scoped by access, included by `list-resource-history`.                                     |
 | `useCollabUndo()`             | CRDT undo/redo for collaborative document edits.                                                                                      |
 | `useLocalOpUndo()`            | App-local inverse operations for commands outside the Yjs document.                                                                   |
-| What-changed views            | Diff summaries, changed sections, and reviewer-friendly explanations.                                                                 |
+| Diff and compare UI           | App-owned presentation built from version snapshots and domain-specific comparison rules.                                             |
 
 ## Register A Resource {#register-resource}
 
@@ -60,24 +59,13 @@ When a resource is already registered with the Sharing Kit, History can reuse
 that access model. Register a History adapter when the app wants automatic
 snapshot capture or restore behavior.
 
-## UI Usage {#ui-usage}
-
-```tsx
-import { VersionHistoryPanel } from "@agent-native/core/client/history";
-
-export function DocumentHistory({ documentId }: { documentId: string }) {
-  return (
-    <VersionHistoryPanel
-      resourceType="document"
-      resourceId={documentId}
-      onRestored={() => refreshDocument()}
-    />
-  );
-}
-```
+## Compose an app-specific history surface {#ui-usage}
 
-Agents and UI call the same actions. Apps can also use the hooks directly when
-they need a custom timeline, preview, or compare view.
+The Core client exports `useResourceVersions()`, `useResourceHistory()`,
+`useCreateResourceVersion()`, and `useRestoreResourceVersion()` from
+`@agent-native/core/client/history`. Use these hooks or the corresponding
+actions to build the interface your resource needs. The app decides how to
+present diffs, identify authors, and confirm restores.
 
 ## UX Standard {#ux-standard}
 
@@ -96,5 +84,4 @@ they need a custom timeline, preview, or compare view.
   timeline's audit view reads from.
 - [**Realtime Collaboration**](/docs/real-time-collaboration) — the CRDT
   editing surface `useCollabUndo()` wraps.
-- [**Component API**](/docs/components#collab-presence) — the full prop
-  reference for history and presence components.
+- [**Component API**](/docs/components) — the generated reference for public React exports.

package/docs/content/toolkit-org-team.mdx

@@ -74,8 +74,8 @@ import {
   OrgSwitcher,
   RequireActiveOrg,
   TeamPage,
-  useOrgRole,
-} from "@agent-native/core/client/org-team";
+} from "@agent-native/toolkit/app/org";
+import { useOrgRole } from "@agent-native/core/client/org-team";
 
 export function AppShell() {
   return <OrgSwitcher />;
@@ -95,8 +95,8 @@ export function AdminOnlyControl() {
 }
 ```
 
-The Settings shell renders the Organization pages from
-`@agent-native/core/client/org`: `OrgGeneralPage`,
+The Settings shell uses the Toolkit organization UI from
+`@agent-native/toolkit/app/org`: `OrgGeneralPage`,
 `OrgMembersPage({ appRoles? })`, `OrgAuthenticationPage`, and `OrgAppsPage`.
 
 Server code imports the same role helpers from `@agent-native/core/org-team`.

package/docs/content/toolkit-resources.mdx

@@ -37,7 +37,7 @@ Mount the complete panel when you want the whole browser/editor surface with
 no assembly required:
 
 ```tsx
-import { ResourcesPanel } from "@agent-native/core/client/resources";
+import { ResourcesPanel } from "@agent-native/toolkit/app/resources";
 
 <ResourcesPanel scope="personal" resourceFilter="files" />;
 ```
@@ -53,6 +53,8 @@ Compose the tree and editor primitives yourself for custom chrome:
 import {
   ResourceEditor,
   ResourceTree,
+} from "@agent-native/toolkit/app/resources";
+import {
   useResource,
   useResourceTree,
 } from "@agent-native/core/client/resources";

package/docs/content/toolkit-settings.mdx

@@ -112,7 +112,7 @@ core page for its own variant. Dispatch keeps its app-role column on Members
 this way:
 
 ```tsx
-import { OrgMembersPage } from "@agent-native/core/client/org";
+import { OrgMembersPage } from "@agent-native/toolkit/app/org";
 import {
   CORE_SETTINGS_PAGES,
   registerSettingsPages,

package/docs/content/toolkit-setup-connections.mdx

@@ -39,7 +39,7 @@ page/components for the standard settings surface.
 import {
   ProviderReadinessBadge,
   SetupConnectionsPage,
-} from "@agent-native/core/client/setup-connections";
+} from "@agent-native/toolkit/app/setup-connections";
 
 export function SettingsConnectionsTab() {
   return (

package/docs/content/toolkit-sharing.mdx

@@ -64,7 +64,7 @@ registerShareableResource({
 Render the standard controls where users decide access:
 
 ```tsx
-import { ShareButton } from "@agent-native/core/client/sharing";
+import { ShareButton } from "@agent-native/toolkit/app/sharing";
 import { VisibilityBadge } from "@agent-native/toolkit/sharing";
 
 <VisibilityBadge visibility={dashboard.visibility} />;
@@ -99,11 +99,11 @@ The most common low-level import is:
 import { VisibilityBadge } from "@agent-native/toolkit/sharing";
 ```
 
-`<ShareButton>` and `<ShareDialog>` are core-owned rather than Toolkit-owned —
-they call sharing actions directly, so keep importing them from
-`@agent-native/core/client` as shown above. Those imports stay compatible:
-core wrappers keep doing the runtime work and pass data and callbacks into
-Toolkit-owned UI.
+`<ShareButton>` and `<ShareDialog>` are Toolkit UI exported from
+`@agent-native/toolkit/app/sharing`. They use Core client hooks and the shared
+sharing actions. When building custom sharing UI, import
+`useShareButtonController` and `useShareDialogController` from
+`@agent-native/core/client/sharing`.
 
 ### Toolkit vs Core {#toolkit-vs-core}
 

package/docs/content/toolkit-ui.mdx

@@ -127,6 +127,17 @@ surface. The app supplies rows, typed columns, editor slots, selection state,
 and persistence callbacks. The kit provides keyboard navigation, active-cell
 behavior, optional selection, column sizing, and the scroll surface.
 
+<WireframeBlock id="doc-block-toolkit-data-grid">
+  <Screen
+    surface="desktop"
+    html={
+      "<div style='min-height:420px;box-sizing:border-box;padding:22px;display:flex;flex-direction:column;gap:12px'><div style='display:flex;align-items:center;gap:8px'><h2 style='margin:0'>Projects</h2><span class='wf-pill'>3 rows</span><div style='flex:1'></div><button><span data-icon='search'></span> Filter</button></div><div class='wf-card' style='padding:0;overflow:hidden'><div style='display:grid;grid-template-columns:1.5fr 1fr 1fr 1fr;border-bottom:1px solid var(--wf-line);font-weight:600'><div style='padding:10px 12px'>Name</div><div style='padding:10px 12px'>Owner</div><div style='padding:10px 12px'>Status</div><div style='padding:10px 12px'>Updated</div></div><div style='display:grid;grid-template-columns:1.5fr 1fr 1fr 1fr;border-bottom:1px solid var(--wf-line)'><div style='padding:10px 12px'>Website refresh</div><div style='padding:10px 12px'>Maya</div><div style='padding:10px 12px'><span class='wf-pill accent'>In progress</span></div><div style='padding:10px 12px'>Today</div></div><div style='display:grid;grid-template-columns:1.5fr 1fr 1fr 1fr;border-bottom:1px solid var(--wf-line)'><div style='padding:10px 12px'>Q3 launch</div><div style='padding:10px 12px'>Kai</div><div style='padding:10px 12px'><span class='wf-pill'>Planning</span></div><div style='padding:10px 12px'>Yesterday</div></div><div style='display:grid;grid-template-columns:1.5fr 1fr 1fr 1fr'><div style='padding:10px 12px;border:2px solid var(--wf-accent);border-radius:4px'>Onboarding</div><div style='padding:10px 12px'>Steve</div><div style='padding:10px 12px'><span class='wf-pill'>Review</span></div><div style='padding:10px 12px'>Aug 8</div></div></div><small class='wf-muted'>Toolkit handles grid interaction. The app provides rows, columns, cell editors, and saved preferences.</small></div>"
+    }
+  />
+</WireframeBlock>
+
+The mock highlights an active cell. The app still owns the row data, property editors, actions, and saved view preferences.
+
 The grid does not fetch data, call actions, resolve credentials, or persist
 edits. Use `renderHeader`, `renderBody`, `renderRow`, and `renderFooter` when an
 app needs to keep its own headers, grouping, row actions, or summary rows.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.207.0",
+  "version": "0.207.1-nightly-20261012011809",
   "description": "The agentic application framework for building autonomous agents with intuitive UIs",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -694,8 +694,8 @@
     "yaml": "^2.9.0",
     "yjs": "^13.6.33",
     "zod": "^4.3.6",
-    "@agent-native/recap-cli": "^0.5.69",
-    "@agent-native/agentkit": "^0.207.0"
+    "@agent-native/agentkit": "^0.207.1-nightly-20261012011809",
+    "@agent-native/recap-cli": "^0.5.69"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",
@@ -765,7 +765,7 @@
     "xlsx": "^0.18.5"
   },
   "peerDependencies": {
-    "@agent-native/core-corpus": ">=0.196.0",
+    "@agent-native/core-corpus": "0.207.1-nightly-20261012011809",
     "@ai-sdk/anthropic": ">=3",
     "@ai-sdk/cohere": ">=3",
     "@ai-sdk/google": ">=3",