@agent-native/core 0.157.3 → 0.157.4

package/dist/server/identity-sso-store.d.ts

@@ -15,17 +15,22 @@
  * development may initialize these tables lazily; production release
  * migrations own their creation before serverless requests are served.
  */
+export declare const CANONICAL_IDENTITY_SSO_HUB_URL = "https://dispatch.agent-native.com";
 export declare const SSO_STATE_TTL_MS: number;
 export declare const SSO_LOGIN_MAX = 60;
 export declare const SSO_LOGIN_WINDOW_MS = 60000;
 export declare function getIdentityHubUrl(): string | undefined;
+export declare function isIdentitySsoExplicitlyEnabled(): boolean;
 export declare function isIdentitySsoEnabled(): boolean;
 export declare function isDesktopSsoCanaryUserAgent(userAgent: string | undefined): boolean;
 export declare function isCanonicalAgentNativeAppOrigin(origin: string | undefined): boolean;
+export declare function isCanonicalIdentitySsoClientOrigin(origin: string | undefined): boolean;
 export declare function isCanonicalAgentNativeAppRequest(host: string | undefined, forwardedProtocol: string | undefined): boolean;
+export declare function isCanonicalIdentitySsoClientRequest(host: string | undefined, forwardedProtocol: string | undefined): boolean;
 /**
  * The conditional login entry is the only browser UI this feature adds. It
- * stays byte-for-byte absent when the direct web federation env is unset.
+ * stays byte-for-byte absent on self-hosted apps; canonical hosted clients
+ * use their exact registered origin as the implicit opt-in.
  */
 export declare function identitySsoLoginButtonHtml(): string;
 export interface CreateSsoStateInput {

package/dist/server/identity-sso-store.js

@@ -20,6 +20,7 @@ import { getDbExec, intType, isConnectionError, isPostgres, isProductionServerle
 import { ensureTableExists } from "../db/ddl-guard.js";
 let _initPromise;
 const DESKTOP_SSO_CANARY_USER_AGENT = /AgentNativeDesktopSsoCanary\//i;
+export const CANONICAL_IDENTITY_SSO_HUB_URL = "https://dispatch.agent-native.com";
 const CANONICAL_IDENTITY_SSO_APP_ORIGINS = new Set([
     "https://analytics.agent-native.com",
     "https://assets.agent-native.com",
@@ -47,28 +48,61 @@ const CLIENT_ID_PATTERN = /^[A-Za-z0-9][A-Za-z0-9._:-]{0,127}$/;
 const CODE_CHALLENGE_PATTERN = /^[A-Za-z0-9_-]{43}$/;
 const CONTROL_CHARS = /[\u0000-\u001f\u007f]/;
 const LOCALHOST_HOSTS = new Set(["localhost", "127.0.0.1", "[::1]", "::1"]);
+const CANONICAL_IDENTITY_SSO_CLIENT_ORIGINS = new Set([...CANONICAL_IDENTITY_SSO_APP_ORIGINS].filter((origin) => origin !== CANONICAL_IDENTITY_SSO_HUB_URL));
 // ---------------------------------------------------------------------------
 // Feature switch — this module is intentionally dependency-light because the
 // auth guard and the route handler both import the same pure switch.
 // ---------------------------------------------------------------------------
+function configuredAppOrigin() {
+    for (const raw of [
+        process.env.APP_URL,
+        process.env.BETTER_AUTH_URL,
+        process.env.VITE_APP_URL,
+        process.env.VITE_BETTER_AUTH_URL,
+        process.env.URL,
+        process.env.DEPLOY_PRIME_URL,
+        process.env.DEPLOY_URL,
+    ]) {
+        const value = raw?.trim();
+        if (!value)
+            continue;
+        try {
+            const url = new URL(value);
+            return `${url.protocol}//${url.host}${url.pathname}`.replace(/\/+$/, "");
+        }
+        catch (error) {
+            void error;
+        }
+    }
+    return undefined;
+}
 export function getIdentityHubUrl() {
     const raw = process.env.AGENT_NATIVE_IDENTITY_HUB_URL?.trim();
-    if (!raw)
-        return undefined;
-    try {
-        const u = new URL(raw);
-        if (u.protocol !== "https:" &&
-            !(u.protocol === "http:" && LOCALHOST_HOSTS.has(u.hostname))) {
-            return undefined;
+    if (raw) {
+        try {
+            const u = new URL(raw);
+            if (u.protocol !== "https:" &&
+                !(u.protocol === "http:" && LOCALHOST_HOSTS.has(u.hostname))) {
+                return undefined;
+            }
+            if (u.username || u.password || u.search || u.hash)
+                return undefined;
+            return `${u.protocol}//${u.host}${u.pathname}`.replace(/\/+$/, "");
         }
-        if (u.username || u.password || u.search || u.hash)
+        catch (error) {
+            void error;
             return undefined;
-        return `${u.protocol}//${u.host}${u.pathname}`.replace(/\/+$/, "");
-    }
-    catch (error) {
-        void error;
-        return undefined;
+        }
     }
+    // Canonical hosted apps are all registered with Dispatch already. Keep
+    // self-hosted deployments opt-in, and never make Dispatch federate to itself.
+    const appOrigin = configuredAppOrigin();
+    return isCanonicalIdentitySsoClientOrigin(appOrigin)
+        ? CANONICAL_IDENTITY_SSO_HUB_URL
+        : undefined;
+}
+export function isIdentitySsoExplicitlyEnabled() {
+    return Boolean(process.env.AGENT_NATIVE_IDENTITY_HUB_URL?.trim() && getIdentityHubUrl());
 }
 export function isIdentitySsoEnabled() {
     return !!getIdentityHubUrl();
@@ -94,14 +128,23 @@ export function isCanonicalAgentNativeAppOrigin(origin) {
         return false;
     }
 }
+export function isCanonicalIdentitySsoClientOrigin(origin) {
+    return Boolean(origin && CANONICAL_IDENTITY_SSO_CLIENT_ORIGINS.has(origin));
+}
 export function isCanonicalAgentNativeAppRequest(host, forwardedProtocol) {
     if (!host || forwardedProtocol !== "https")
         return false;
     return isCanonicalAgentNativeAppOrigin(`https://${host}`);
 }
+export function isCanonicalIdentitySsoClientRequest(host, forwardedProtocol) {
+    if (!host || forwardedProtocol !== "https")
+        return false;
+    return isCanonicalIdentitySsoClientOrigin(`https://${host}`);
+}
 /**
  * The conditional login entry is the only browser UI this feature adds. It
- * stays byte-for-byte absent when the direct web federation env is unset.
+ * stays byte-for-byte absent on self-hosted apps; canonical hosted clients
+ * use their exact registered origin as the implicit opt-in.
  */
 export function identitySsoLoginButtonHtml() {
     if (!isIdentitySsoEnabled())

package/dist/server/identity-sso.d.ts

@@ -7,11 +7,10 @@
  * callback-scoped cookie and redeems the code server-to-server. Only that
  * server-to-server response may contain the signed identity assertion.
  *
- * Direct browser federation remains opt-in through
- * `AGENT_NATIVE_IDENTITY_HUB_URL`. The packaged Desktop Canary may use the
- * canonical Dispatch authority on canonical app origins, as established by
- * the merged feature-flagged Desktop work. This module does not change the
- * Desktop implementation or any ordinary auth surface.
+ * Direct browser federation uses the canonical Dispatch authority for exact
+ * first-party hosted app origins and remains opt-in through
+ * `AGENT_NATIVE_IDENTITY_HUB_URL` for self-hosted deployments. The packaged
+ * Desktop Canary follows the same canonical-origin boundary.
  */
 import type { H3Event } from "h3";
 import { getIdentityHubUrl, identitySsoLoginButtonHtml, isIdentitySsoEnabled } from "./identity-sso-store.js";
@@ -22,9 +21,9 @@ export declare const IDENTITY_SSO_DESKTOP_COMPLETE_PATH = "/_agent-native/identi
 export declare const IDENTITY_SSO_CALLBACK_PATH = "/_agent-native/identity/callback";
 export declare const IDENTITY_SSO_TOKEN_PATH = "/_agent-native/identity/token";
 /**
- * The packaged Desktop SSO Canary may use Dispatch without each canonical app
- * deploying the direct-web hub env. Ordinary browsers and self-hosted apps
- * remain strictly env-gated.
+ * Canonical hosted apps may use Dispatch without per-app hub configuration.
+ * Self-hosted apps remain strictly env-gated. The exact-origin check is kept
+ * request-scoped so a missing deployment URL cannot broaden the trust set.
  */
 export declare function resolveIdentityHubUrl(event: H3Event): string | undefined;
 export declare function handleIdentitySso(event: H3Event, subpath: string): Promise<Response>;

package/dist/server/identity-sso.js

@@ -7,11 +7,10 @@
  * callback-scoped cookie and redeems the code server-to-server. Only that
  * server-to-server response may contain the signed identity assertion.
  *
- * Direct browser federation remains opt-in through
- * `AGENT_NATIVE_IDENTITY_HUB_URL`. The packaged Desktop Canary may use the
- * canonical Dispatch authority on canonical app origins, as established by
- * the merged feature-flagged Desktop work. This module does not change the
- * Desktop implementation or any ordinary auth surface.
+ * Direct browser federation uses the canonical Dispatch authority for exact
+ * first-party hosted app origins and remains opt-in through
+ * `AGENT_NATIVE_IDENTITY_HUB_URL` for self-hosted deployments. The packaged
+ * Desktop Canary follows the same canonical-origin boundary.
  */
 import { createHash, randomBytes } from "node:crypto";
 import { deleteCookie, getCookie, getHeader, getMethod, setCookie } from "h3";
@@ -22,7 +21,7 @@ import { getAppName } from "./app-name.js";
 import { getSession, isExpectedAuthFailure, safeReturnPath } from "./auth.js";
 import { getBetterAuth, getBetterAuthInternalAdapter, } from "./better-auth-instance.js";
 import { createOAuthSession, getOrigin } from "./google-oauth.js";
-import { consumeSsoState, createSsoState, getIdentityHubUrl, identitySsoLoginButtonHtml, isCanonicalAgentNativeAppRequest, isDesktopSsoCanaryUserAgent, isIdentitySsoEnabled, isJtiReplayed, SSO_STATE_TTL_MS, } from "./identity-sso-store.js";
+import { consumeSsoState, createSsoState, CANONICAL_IDENTITY_SSO_HUB_URL, getIdentityHubUrl, identitySsoLoginButtonHtml, isCanonicalAgentNativeAppRequest, isCanonicalIdentitySsoClientRequest, isDesktopSsoCanaryUserAgent, isIdentitySsoExplicitlyEnabled, isIdentitySsoEnabled, isJtiReplayed, SSO_STATE_TTL_MS, } from "./identity-sso-store.js";
 export { getIdentityHubUrl, identitySsoLoginButtonHtml, isIdentitySsoEnabled };
 export const IDENTITY_SSO_PROVIDER_ID = "agent-native";
 export const IDENTITY_SSO_SCOPE = "identity";
@@ -33,7 +32,6 @@ const DESKTOP_COMPLETION_NONCE = /^[A-Za-z0-9_-]{32,128}$/;
 const STATE_PATTERN = /^[A-Za-z0-9_-]{43}$/;
 const CODE = /^[A-Za-z0-9_-]{43}$/;
 const CODE_VERIFIER = /^[A-Za-z0-9._~-]{43,128}$/;
-const DESKTOP_IDENTITY_HUB_URL = "https://dispatch.agent-native.com";
 const SSO_VERIFIER_COOKIE_PREFIX = "agent_native_sso_verifier_";
 const MAX_ASSERTION_AGE_SECONDS = 5 * 60;
 const LOCALHOST_HOSTS = new Set(["localhost", "127.0.0.1", "[::1]", "::1"]);
@@ -153,14 +151,19 @@ function resolveClientBinding(event, hub) {
     return { appId, clientId, redirectUri, authority };
 }
 /**
- * The packaged Desktop SSO Canary may use Dispatch without each canonical app
- * deploying the direct-web hub env. Ordinary browsers and self-hosted apps
- * remain strictly env-gated.
+ * Canonical hosted apps may use Dispatch without per-app hub configuration.
+ * Self-hosted apps remain strictly env-gated. The exact-origin check is kept
+ * request-scoped so a missing deployment URL cannot broaden the trust set.
  */
 export function resolveIdentityHubUrl(event) {
-    const configured = getIdentityHubUrl();
+    const configured = isIdentitySsoExplicitlyEnabled()
+        ? getIdentityHubUrl()
+        : undefined;
     if (configured)
         return configured;
+    if (isCanonicalIdentitySsoClientRequest(getHeader(event, "host"), getHeader(event, "x-forwarded-proto"))) {
+        return CANONICAL_IDENTITY_SSO_HUB_URL;
+    }
     if (!isDesktopSsoCanaryUserAgent(getHeader(event, "user-agent"))) {
         return undefined;
     }
@@ -168,7 +171,7 @@ export function resolveIdentityHubUrl(event) {
         if (!isCanonicalAgentNativeAppRequest(getHeader(event, "host"), getHeader(event, "x-forwarded-proto"))) {
             return undefined;
         }
-        return DESKTOP_IDENTITY_HUB_URL;
+        return CANONICAL_IDENTITY_SSO_HUB_URL;
     }
     catch (error) {
         void error;

package/dist/sharing/actions/list-resource-shares.d.ts

@@ -11,11 +11,13 @@ declare const _default: import("../../action.js").ActionDefinition<{
     };
     orgId?: undefined;
     role?: undefined;
+    agentReadable?: undefined;
 } | {
     ownerEmail: string;
     orgId: string;
     visibility: import("../schema.js").Visibility;
     role: "owner" | import("../schema.js").ShareRole;
+    agentReadable: boolean;
     shares: any;
     policy: {
         allowPublic: boolean;

package/dist/sharing/actions/list-resource-shares.js

@@ -60,6 +60,7 @@ export default defineAction({
             orgId: access.resource.orgId ?? null,
             visibility: access.resource.visibility ?? "private",
             role: access.role,
+            agentReadable: Boolean(reg.agentReadable),
             shares: shares.map((s) => ({
                 id: s.id,
                 principalType: s.principalType,

package/dist/sharing/schema.d.ts

@@ -160,7 +160,7 @@ export declare function createSharesTable(tableName: string): import("drizzle-or
             data: string;
             driverParam: string;
             notNull: true;
-            hasDefault: false;
+            hasDefault: true;
             isPrimaryKey: false;
             isAutoincrement: false;
             hasRuntimeDefault: false;

package/dist/sharing/schema.js

@@ -73,7 +73,10 @@ export function createSharesTable(tableName) {
         })
             .notNull()
             .default("viewer"),
-        createdBy: text("created_by").notNull(),
+        // Older app databases may already contain share rows from before this
+        // audit field existed. A literal default lets additive schema repair add
+        // the column without inventing an actor for those historical rows.
+        createdBy: text("created_by").notNull().default(""),
         createdAt: text("created_at").notNull().default(now()),
     });
 }

package/dist/templates/chat/.agents/skills/agent-native-toolkit/SKILL.md

@@ -182,6 +182,11 @@ in the moment of agent use.
   five-item sidebar preview and a footer row with New chat followed by an
   ellipsis disclosure up to fifteen. Apps inject routing, labels, and domain
   actions.
+- **Data grid kit**: provider-agnostic spreadsheet mechanics belong in
+  `@agent-native/toolkit/data-grid`. Apps provide rows, typed columns, editor
+  slots, selection and width state, persistence callbacks, and product-level
+  row/body slots. Keep database models, access checks, grouping, drag/drop,
+  and domain actions in the app adapter.
 - **Agent page kit**: the full-page `/agent` surface (`AgentTabsPage` from
   `@agent-native/core/client`) with Context, Files, Connections, Jobs, and
   Access tabs plus a Personal/Organization scope toggle. The canonical home

package/dist/templates/chat/.agents/skills/sharing/SKILL.md

@@ -184,6 +184,27 @@ import { ShareButton } from "@agent-native/core/client/sharing";
 
 For list views, show `<VisibilityBadge visibility={row.visibility} />` next to each resource.
 
+## Standard share surface
+
+All app share popovers should use the same compact surface contract:
+
+- Use the text-only `ShareTrigger` from `@agent-native/toolkit/sharing`.
+- Render ordinary links with `ShareCopyRow`, which exposes a Copy action without
+  printing the raw URL.
+- Keep general access and individual people access in the standard Core sharing
+  flow. The people flow supports email invites, roles, notifications, and
+  removal through the shared share actions.
+- Add `ShareAgentsSection` only when the resource has a real agent-readable
+  link or prompt. Keep it collapsed by default and supply domain-specific
+  content through the shared section shell.
+- App-specific tabs or controls may remain when they represent a real domain
+  action (for example, an embed-code editor), but they should retain the same
+  trigger, copy-row, access, and spacing language.
+
+`ShareDisclosureSection` is the toolkit-owned shell for optional expandable
+share details; use its `ShareAgentsSection` or `SharePeopleSection` wrappers
+instead of creating another collapsible share panel in a template.
+
 ## Actions available everywhere
 
 The framework auto-mounts these actions in every template — no per-template boilerplate:

package/dist/templates/default/.agents/skills/agent-native-toolkit/SKILL.md

@@ -182,6 +182,11 @@ in the moment of agent use.
   five-item sidebar preview and a footer row with New chat followed by an
   ellipsis disclosure up to fifteen. Apps inject routing, labels, and domain
   actions.
+- **Data grid kit**: provider-agnostic spreadsheet mechanics belong in
+  `@agent-native/toolkit/data-grid`. Apps provide rows, typed columns, editor
+  slots, selection and width state, persistence callbacks, and product-level
+  row/body slots. Keep database models, access checks, grouping, drag/drop,
+  and domain actions in the app adapter.
 - **Agent page kit**: the full-page `/agent` surface (`AgentTabsPage` from
   `@agent-native/core/client`) with Context, Files, Connections, Jobs, and
   Access tabs plus a Personal/Organization scope toggle. The canonical home

package/dist/templates/default/.agents/skills/sharing/SKILL.md

@@ -184,6 +184,27 @@ import { ShareButton } from "@agent-native/core/client/sharing";
 
 For list views, show `<VisibilityBadge visibility={row.visibility} />` next to each resource.
 
+## Standard share surface
+
+All app share popovers should use the same compact surface contract:
+
+- Use the text-only `ShareTrigger` from `@agent-native/toolkit/sharing`.
+- Render ordinary links with `ShareCopyRow`, which exposes a Copy action without
+  printing the raw URL.
+- Keep general access and individual people access in the standard Core sharing
+  flow. The people flow supports email invites, roles, notifications, and
+  removal through the shared share actions.
+- Add `ShareAgentsSection` only when the resource has a real agent-readable
+  link or prompt. Keep it collapsed by default and supply domain-specific
+  content through the shared section shell.
+- App-specific tabs or controls may remain when they represent a real domain
+  action (for example, an embed-code editor), but they should retain the same
+  trigger, copy-row, access, and spacing language.
+
+`ShareDisclosureSection` is the toolkit-owned shell for optional expandable
+share details; use its `ShareAgentsSection` or `SharePeopleSection` wrappers
+instead of creating another collapsible share panel in a template.
+
 ## Actions available everywhere
 
 The framework auto-mounts these actions in every template — no per-template boilerplate:

package/dist/templates/headless/.agents/skills/agent-native-toolkit/SKILL.md

@@ -182,6 +182,11 @@ in the moment of agent use.
   five-item sidebar preview and a footer row with New chat followed by an
   ellipsis disclosure up to fifteen. Apps inject routing, labels, and domain
   actions.
+- **Data grid kit**: provider-agnostic spreadsheet mechanics belong in
+  `@agent-native/toolkit/data-grid`. Apps provide rows, typed columns, editor
+  slots, selection and width state, persistence callbacks, and product-level
+  row/body slots. Keep database models, access checks, grouping, drag/drop,
+  and domain actions in the app adapter.
 - **Agent page kit**: the full-page `/agent` surface (`AgentTabsPage` from
   `@agent-native/core/client`) with Context, Files, Connections, Jobs, and
   Access tabs plus a Personal/Organization scope toggle. The canonical home

package/dist/templates/workspace-core/.agents/skills/agent-native-toolkit/SKILL.md

@@ -182,6 +182,11 @@ in the moment of agent use.
   five-item sidebar preview and a footer row with New chat followed by an
   ellipsis disclosure up to fifteen. Apps inject routing, labels, and domain
   actions.
+- **Data grid kit**: provider-agnostic spreadsheet mechanics belong in
+  `@agent-native/toolkit/data-grid`. Apps provide rows, typed columns, editor
+  slots, selection and width state, persistence callbacks, and product-level
+  row/body slots. Keep database models, access checks, grouping, drag/drop,
+  and domain actions in the app adapter.
 - **Agent page kit**: the full-page `/agent` surface (`AgentTabsPage` from
   `@agent-native/core/client`) with Context, Files, Connections, Jobs, and
   Access tabs plus a Personal/Organization scope toggle. The canonical home

package/dist/templates/workspace-core/.agents/skills/sharing/SKILL.md

@@ -184,6 +184,27 @@ import { ShareButton } from "@agent-native/core/client/sharing";
 
 For list views, show `<VisibilityBadge visibility={row.visibility} />` next to each resource.
 
+## Standard share surface
+
+All app share popovers should use the same compact surface contract:
+
+- Use the text-only `ShareTrigger` from `@agent-native/toolkit/sharing`.
+- Render ordinary links with `ShareCopyRow`, which exposes a Copy action without
+  printing the raw URL.
+- Keep general access and individual people access in the standard Core sharing
+  flow. The people flow supports email invites, roles, notifications, and
+  removal through the shared share actions.
+- Add `ShareAgentsSection` only when the resource has a real agent-readable
+  link or prompt. Keep it collapsed by default and supply domain-specific
+  content through the shared section shell.
+- App-specific tabs or controls may remain when they represent a real domain
+  action (for example, an embed-code editor), but they should retain the same
+  trigger, copy-row, access, and spacing language.
+
+`ShareDisclosureSection` is the toolkit-owned shell for optional expandable
+share details; use its `ShareAgentsSection` or `SharePeopleSection` wrappers
+instead of creating another collapsible share panel in a template.
+
 ## Actions available everywhere
 
 The framework auto-mounts these actions in every template — no per-template boilerplate:

package/docs/content/cross-app-sso.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Cross-App SSO"
-description: "Sign in once across every hosted agent-native app via identity federation with Dispatch as the identity authority — opt-in per app, reversible with a single env var."
+description: "Sign in once across every hosted agent-native app via identity federation with Dispatch as the identity authority. Canonical hosted clients are enabled by exact origin; self-hosted apps opt in with one env var."
 ---
 
 # Cross-App SSO
@@ -233,16 +233,20 @@ trust boundary.
 
 5. **App mints a normal local session.** From here on the user has an ordinary local session in that app's own store — every existing access check, org scoping, and action guard works exactly as before. The federation only happened at the front door.
 
-### Opting in {#opt-in}
+### Hosted and self-hosted behavior {#opt-in}
 
-An app's ordinary web sign-in participates **only** when this environment variable is set on its deployment:
+Canonical hosted client apps use Dispatch automatically when their deployment has
+one of the exact registered `*.agent-native.com` origins. Dispatch is the
+identity authority, not a client, so it never federates to itself. Self-hosted
+apps remain opt-in and must set this environment variable on their deployment:
 
 ```bash
 AGENT_NATIVE_IDENTITY_HUB_URL=https://dispatch.agent-native.com
 ```
 
-- **Set** → the app shows a **"Sign in with Agent-Native"** option that runs the flow above. Direct local login (email/password, Google) still works alongside it.
-- **Unset (default)** → **zero behavior change.** The app authenticates exactly as it did before; the federation code path is dormant. There is no schema change and nothing to migrate, so flipping the variable on or off is fully reversible at any time.
+- **Canonical hosted client** → the app shows a **"Sign in with Agent-Native"** option that runs the flow above. Direct local login (email/password, Google) still works alongside it.
+- **Self-hosted with the variable set** → the app shows the same option, using the configured Dispatch instance.
+- **Self-hosted with the variable unset** → **zero behavior change.** The app authenticates exactly as it did before; the federation code path is dormant. There is no schema change and nothing to migrate.
 
 ## Security {#security}
 
@@ -262,7 +266,7 @@ The whole model rests on a few deliberately small guarantees:
   accept a user id, role, org membership, or any privileged state from the
   wire — it derives everything locally from the matched account.
 - **Additive-only identity writes.** Linking either reuses an existing same-email account untouched or inserts a new one. No update, rename, repoint, or delete of identity rows ever happens on this path.
-- **Off by default.** With `AGENT_NATIVE_IDENTITY_HUB_URL` unset, ordinary browser federation is inert. The separately gated packaged Desktop path is described below.
+- **Exact-origin trust.** Only the registered canonical hosted client origins get the implicit hosted default. Self-hosted and custom origins remain opt-in through `AGENT_NATIVE_IDENTITY_HUB_URL`; the separately gated packaged Desktop path is described below.
 
 <Callout id="doc-block-18qhl3m" tone="success">
 
@@ -345,8 +349,8 @@ flag controls whether Desktop may begin the ceremony; it does not authorize a
 user or weaken nonce, signature, origin, callback, app-binding, cookie,
 revocation, or credential-custody checks. With the flag Off or unavailable,
 Desktop leaves ordinary per-app sign-in, sign-out, and Settings unchanged.
-Canonical hosted apps recognize the packaged Desktop request without requiring
-`AGENT_NATIVE_IDENTITY_HUB_URL` on every deployment; ordinary web browsers and
+Canonical hosted apps recognize the packaged Desktop request and ordinary web
+browsers without requiring `AGENT_NATIVE_IDENTITY_HUB_URL` on every deployment;
 self-hosted apps still require that explicit configuration.
 Stable Desktop builds do not initialize the broker until a later release is
 separately approved.
@@ -379,19 +383,22 @@ Without an exact custom registry entry, a self-hosted Dispatch can only issue co
 
 ## Canary rollout runbook {#canary-rollout}
 
-Cutover and rollback are **a single environment variable per app deployment**. Roll out one app at a time, verify, then expand. Do not set the variable on every app at once.
+Canonical hosted clients take the default after the release ships. Self-hosted
+and custom deployments still use **a single environment variable per app**.
+Roll out one deployment at a time, verify, then expand.
 
-**1. Deploy the code — no behavior change.**
-Ship the release to every app with `AGENT_NATIVE_IDENTITY_HUB_URL` **unset everywhere**. Confirm normal logins still work on a couple of apps.
+**1. Deploy the code and verify a canonical hosted client.**
+Ship the release to the canonical apps. Confirm normal logins still work on a
+couple of apps and that the new sign-in option appears on a client app.
 
-**2. Enable the canary on ONE app at a time.**
+**2. Enable self-hosted/custom apps one at a time.**
 Set, on one deployment only:
 
 ```bash
 AGENT_NATIVE_IDENTITY_HUB_URL=https://dispatch.agent-native.com
 ```
 
-Leave every other app's environment unset. Redeploy/restart so it picks up the variable.
+Leave every other self-hosted app's environment unset. Redeploy/restart so it picks up the variable.
 
 **3. Verify the canary (checklist).**
 
@@ -402,13 +409,13 @@ Leave every other app's environment unset. Redeploy/restart so it picks up the v
 - **App data is intact** — your existing records, settings, and org scoping are exactly as they were.
 - **Existing direct logins still work** — email/password and Google sign-in continue to function alongside SSO.
 
-If any check fails, go straight to step 4 (rollback) — it is instant and data-safe.
+If any check fails, go straight to step 5 (rollback) — it is instant and data-safe.
 
 **4. Expand app-by-app.**
-Once one app is verified, repeat steps 2–3 for the next app — setting `AGENT_NATIVE_IDENTITY_HUB_URL` on one deployment at a time. Never batch-enable.
+Once one deployment is verified, repeat steps 2–3 for the next one. Never batch-enable custom origins.
 
-**5. Rollback = unset the env var on that app's deploy.**
-To revert any app, **remove `AGENT_NATIVE_IDENTITY_HUB_URL` from that app's environment and redeploy/restart it.** The app immediately returns to its prior auth behavior. There is **no data change to undo** — identity rows were only ever added, and unsetting the variable simply makes the federation path dormant again. Each app's cutover and rollback are independent and reversible.
+**5. Rollback.**
+For a self-hosted app, **remove `AGENT_NATIVE_IDENTITY_HUB_URL` from its environment and redeploy/restart it.** A canonical hosted client can be rolled back by reverting the release or disabling the hosted client path. There is **no data change to undo** — identity rows were only ever added. Each deployment's cutover and rollback are independent and reversible.
 
 <Callout tone="info">
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.157.3",
+  "version": "0.157.4",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -424,7 +424,7 @@
     "yjs": "^13.6.31",
     "zod": "^4.3.6",
     "@agent-native/recap-cli": "0.5.4",
-    "@agent-native/toolkit": "^0.15.1"
+    "@agent-native/toolkit": "^0.16.0"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",

package/src/templates/chat/.agents/skills/agent-native-toolkit/SKILL.md

@@ -182,6 +182,11 @@ in the moment of agent use.
   five-item sidebar preview and a footer row with New chat followed by an
   ellipsis disclosure up to fifteen. Apps inject routing, labels, and domain
   actions.
+- **Data grid kit**: provider-agnostic spreadsheet mechanics belong in
+  `@agent-native/toolkit/data-grid`. Apps provide rows, typed columns, editor
+  slots, selection and width state, persistence callbacks, and product-level
+  row/body slots. Keep database models, access checks, grouping, drag/drop,
+  and domain actions in the app adapter.
 - **Agent page kit**: the full-page `/agent` surface (`AgentTabsPage` from
   `@agent-native/core/client`) with Context, Files, Connections, Jobs, and
   Access tabs plus a Personal/Organization scope toggle. The canonical home

package/src/templates/chat/.agents/skills/sharing/SKILL.md

@@ -184,6 +184,27 @@ import { ShareButton } from "@agent-native/core/client/sharing";
 
 For list views, show `<VisibilityBadge visibility={row.visibility} />` next to each resource.
 
+## Standard share surface
+
+All app share popovers should use the same compact surface contract:
+
+- Use the text-only `ShareTrigger` from `@agent-native/toolkit/sharing`.
+- Render ordinary links with `ShareCopyRow`, which exposes a Copy action without
+  printing the raw URL.
+- Keep general access and individual people access in the standard Core sharing
+  flow. The people flow supports email invites, roles, notifications, and
+  removal through the shared share actions.
+- Add `ShareAgentsSection` only when the resource has a real agent-readable
+  link or prompt. Keep it collapsed by default and supply domain-specific
+  content through the shared section shell.
+- App-specific tabs or controls may remain when they represent a real domain
+  action (for example, an embed-code editor), but they should retain the same
+  trigger, copy-row, access, and spacing language.
+
+`ShareDisclosureSection` is the toolkit-owned shell for optional expandable
+share details; use its `ShareAgentsSection` or `SharePeopleSection` wrappers
+instead of creating another collapsible share panel in a template.
+
 ## Actions available everywhere
 
 The framework auto-mounts these actions in every template — no per-template boilerplate:

package/src/templates/default/.agents/skills/agent-native-toolkit/SKILL.md

@@ -182,6 +182,11 @@ in the moment of agent use.
   five-item sidebar preview and a footer row with New chat followed by an
   ellipsis disclosure up to fifteen. Apps inject routing, labels, and domain
   actions.
+- **Data grid kit**: provider-agnostic spreadsheet mechanics belong in
+  `@agent-native/toolkit/data-grid`. Apps provide rows, typed columns, editor
+  slots, selection and width state, persistence callbacks, and product-level
+  row/body slots. Keep database models, access checks, grouping, drag/drop,
+  and domain actions in the app adapter.
 - **Agent page kit**: the full-page `/agent` surface (`AgentTabsPage` from
   `@agent-native/core/client`) with Context, Files, Connections, Jobs, and
   Access tabs plus a Personal/Organization scope toggle. The canonical home

package/src/templates/default/.agents/skills/sharing/SKILL.md

@@ -184,6 +184,27 @@ import { ShareButton } from "@agent-native/core/client/sharing";
 
 For list views, show `<VisibilityBadge visibility={row.visibility} />` next to each resource.
 
+## Standard share surface
+
+All app share popovers should use the same compact surface contract:
+
+- Use the text-only `ShareTrigger` from `@agent-native/toolkit/sharing`.
+- Render ordinary links with `ShareCopyRow`, which exposes a Copy action without
+  printing the raw URL.
+- Keep general access and individual people access in the standard Core sharing
+  flow. The people flow supports email invites, roles, notifications, and
+  removal through the shared share actions.
+- Add `ShareAgentsSection` only when the resource has a real agent-readable
+  link or prompt. Keep it collapsed by default and supply domain-specific
+  content through the shared section shell.
+- App-specific tabs or controls may remain when they represent a real domain
+  action (for example, an embed-code editor), but they should retain the same
+  trigger, copy-row, access, and spacing language.
+
+`ShareDisclosureSection` is the toolkit-owned shell for optional expandable
+share details; use its `ShareAgentsSection` or `SharePeopleSection` wrappers
+instead of creating another collapsible share panel in a template.
+
 ## Actions available everywhere
 
 The framework auto-mounts these actions in every template — no per-template boilerplate:

package/src/templates/headless/.agents/skills/agent-native-toolkit/SKILL.md

@@ -182,6 +182,11 @@ in the moment of agent use.
   five-item sidebar preview and a footer row with New chat followed by an
   ellipsis disclosure up to fifteen. Apps inject routing, labels, and domain
   actions.
+- **Data grid kit**: provider-agnostic spreadsheet mechanics belong in
+  `@agent-native/toolkit/data-grid`. Apps provide rows, typed columns, editor
+  slots, selection and width state, persistence callbacks, and product-level
+  row/body slots. Keep database models, access checks, grouping, drag/drop,
+  and domain actions in the app adapter.
 - **Agent page kit**: the full-page `/agent` surface (`AgentTabsPage` from
   `@agent-native/core/client`) with Context, Files, Connections, Jobs, and
   Access tabs plus a Personal/Organization scope toggle. The canonical home