@agent-native/core 0.209.2-nightly-20261016153022 → 0.209.2

package/dist/collab/struct-routes.d.ts

@@ -1,6 +1,6 @@
 export declare const postCollabJson: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    error: string;
     ok?: undefined;
+    error: string;
 } | {
     error?: undefined;
     ok: boolean;

package/dist/mcp/screen-memory-stdio.d.ts

@@ -140,13 +140,13 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
             includeMicrophone?: undefined;
             includeSystemAudio?: undefined;
             requestId?: undefined;
+            count?: undefined;
         };
         required?: undefined;
     };
@@ -171,13 +171,13 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
             includeMicrophone?: undefined;
             includeSystemAudio?: undefined;
             requestId?: undefined;
+            count?: undefined;
         };
         required?: undefined;
     };
@@ -196,13 +196,13 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
             includeMicrophone?: undefined;
             includeSystemAudio?: undefined;
             requestId?: undefined;
+            count?: undefined;
         };
         required?: undefined;
     };
@@ -231,13 +231,13 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             };
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
             includeMicrophone?: undefined;
             includeSystemAudio?: undefined;
             requestId?: undefined;
+            count?: undefined;
         };
     };
 } | {
@@ -260,12 +260,12 @@ export declare function screenMemoryMcpToolDefinitions(): ({
                 description: string;
             };
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             includeMicrophone?: undefined;
             includeSystemAudio?: undefined;
             requestId?: undefined;
+            count?: undefined;
         };
     };
 } | {
@@ -317,7 +317,6 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt: {
                 type: string;
                 description: string;
@@ -337,6 +336,7 @@ export declare function screenMemoryMcpToolDefinitions(): ({
                 type: string;
             };
             requestId?: undefined;
+            count?: undefined;
         };
     };
 } | {
@@ -352,7 +352,6 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
@@ -361,6 +360,7 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             requestId: {
                 type: string;
             };
+            count?: undefined;
         };
     };
 })[];

package/dist/notifications/routes.d.ts

@@ -16,6 +16,6 @@ export declare function createNotificationsHandler(): import("h3").EventHandlerW
 } | {
     count?: undefined;
     updated?: undefined;
-    ok: boolean;
     error?: undefined;
+    ok: boolean;
 }>>;

package/dist/org/index.d.ts

@@ -161,9 +161,9 @@ export declare const getMyOrgHandler: import("h3").EventHandlerWithFetch<import(
     soloDeploymentAdmin: boolean;
 }>>;
 export declare const createOrgHandler: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    name?: undefined;
     success: boolean;
     id?: undefined;
+    name?: undefined;
     role?: undefined;
 } | {
     success?: undefined;

package/dist/provider-api/actions/custom-provider-registration.d.ts

@@ -75,7 +75,6 @@ export declare function createCustomProviderRegistrationAction<TSchema extends Z
         user: "user";
     }>>;
 }, z.core.$strip>>, {
-    provider?: undefined;
     id?: undefined;
     deleted?: undefined;
     message?: undefined;
@@ -89,6 +88,7 @@ export declare function createCustomProviderRegistrationAction<TSchema extends Z
         updatedAt: number;
     }[];
     count: number;
+    provider?: undefined;
     found?: undefined;
     registered?: undefined;
     label?: undefined;
@@ -103,30 +103,30 @@ export declare function createCustomProviderRegistrationAction<TSchema extends Z
     registered?: undefined;
     label?: undefined;
 } | {
-    provider?: undefined;
     deleted?: undefined;
     count?: undefined;
     message?: undefined;
     providers?: undefined;
+    provider?: undefined;
     found: boolean;
     id: string;
     registered?: undefined;
     label?: undefined;
 } | {
-    provider?: undefined;
     count?: undefined;
     message?: undefined;
     providers?: undefined;
+    provider?: undefined;
     found?: undefined;
     deleted: boolean;
     id: string;
     registered?: undefined;
     label?: undefined;
 } | {
-    provider?: undefined;
     deleted?: undefined;
     count?: undefined;
     providers?: undefined;
+    provider?: undefined;
     found?: undefined;
     registered: boolean;
     id: string;

package/dist/provider-api/actions/provider-api.d.ts

@@ -316,7 +316,6 @@ export declare function createProviderApiActions(runtime: Pick<ProviderApiRuntim
         notes?: string | undefined;
         scope?: "org" | "user" | undefined;
     }, {
-        id?: undefined;
         message?: undefined;
         providers: {
             id: string;
@@ -332,20 +331,21 @@ export declare function createProviderApiActions(runtime: Pick<ProviderApiRuntim
         found?: undefined;
         deleted?: undefined;
         registered?: undefined;
+        id?: undefined;
         label?: undefined;
     } | {
-        id?: undefined;
-        count?: undefined;
         message?: undefined;
+        count?: undefined;
         providers?: undefined;
         found: boolean;
         provider: import("../custom-registry.js").CustomProviderConfig;
         deleted?: undefined;
         registered?: undefined;
+        id?: undefined;
         label?: undefined;
     } | {
-        count?: undefined;
         message?: undefined;
+        count?: undefined;
         providers?: undefined;
         provider?: undefined;
         found: boolean;
@@ -354,8 +354,8 @@ export declare function createProviderApiActions(runtime: Pick<ProviderApiRuntim
         registered?: undefined;
         label?: undefined;
     } | {
-        count?: undefined;
         message?: undefined;
+        count?: undefined;
         providers?: undefined;
         provider?: undefined;
         found?: undefined;

package/dist/server/agent-engine-api-key-route.d.ts

@@ -67,12 +67,12 @@ export declare function createAgentEngineApiKeyHandler(): import("h3").EventHand
     code: any;
 } | {
     errorCode?: undefined;
+    error?: undefined;
     code?: undefined;
     ok: boolean;
     key: string;
     baseUrlKey?: string;
     scope: AgentEngineApiKeyScope;
     defaultModel?: import("./agent-engine-default-model-route.js").SavedKeyDefaultModelOutcome;
-    error?: undefined;
 }>>;
 export {};

package/dist/server/agent-engine-default-model-route.d.ts

@@ -8,17 +8,17 @@ export declare const AGENT_ENGINE_API_KEY_ACTION_NAME = "agent-engine-api-key";
  * resolveEngine's credential detection.
  */
 export declare function createAgentEngineDisconnectHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
+    ok?: undefined;
     error: string;
     scope?: undefined;
-    ok?: undefined;
 } | {
     ok: boolean;
     error: any;
     scope?: undefined;
 } | {
+    error?: undefined;
     ok: boolean;
     scope: "org" | "user";
-    error?: undefined;
 }>>;
 export interface DefaultModelSelectionRequest {
     engine: string;

package/dist/server/app-release-migrations.d.ts

@@ -0,0 +1,21 @@
+/** Where the starters' storing-data skill tells an app to declare its tables. */
+export declare const APP_DB_PLUGIN = "server/plugins/db.ts";
+export type AppReleaseMigrationResult = {
+    status: "applied";
+    plugin: string;
+} | {
+    status: "no-app-tables";
+} | {
+    status: "managed-drizzle";
+    config: string;
+};
+/**
+ * Applies the app's own `runMigrations` list at release. A release-owned
+ * hosted function skips that list at boot (that is what release-owned means),
+ * so without this step a starter app's tables are never created in
+ * production. A managed Drizzle project is the exception: `db:migrate` owns
+ * its tables, and running the plugin too would give them two owners.
+ *
+ * Call inside `withMigrationRuntime`, after `runFrameworkReleaseMigrations`.
+ */
+export declare function runAppReleaseMigrations(cwd?: string): Promise<AppReleaseMigrationResult>;

package/dist/server/app-release-migrations.js

@@ -0,0 +1,33 @@
+import { existsSync } from "node:fs";
+import path from "node:path";
+import { pathToFileURL } from "node:url";
+/** Where the starters' storing-data skill tells an app to declare its tables. */
+export const APP_DB_PLUGIN = "server/plugins/db.ts";
+const MANAGED_DRIZZLE_CONFIGS = [
+    "drizzle.config.ts",
+    "drizzle.config.js",
+    "drizzle.config.json",
+];
+/**
+ * Applies the app's own `runMigrations` list at release. A release-owned
+ * hosted function skips that list at boot (that is what release-owned means),
+ * so without this step a starter app's tables are never created in
+ * production. A managed Drizzle project is the exception: `db:migrate` owns
+ * its tables, and running the plugin too would give them two owners.
+ *
+ * Call inside `withMigrationRuntime`, after `runFrameworkReleaseMigrations`.
+ */
+export async function runAppReleaseMigrations(cwd = process.cwd()) {
+    const managed = MANAGED_DRIZZLE_CONFIGS.find((file) => existsSync(path.join(cwd, file)));
+    if (managed)
+        return { status: "managed-drizzle", config: managed };
+    const pluginPath = path.join(cwd, APP_DB_PLUGIN);
+    if (!existsSync(pluginPath))
+        return { status: "no-app-tables" };
+    const plugin = (await import(pathToFileURL(pluginPath).href)).default;
+    if (typeof plugin !== "function") {
+        throw new Error(`${APP_DB_PLUGIN} must default-export its migration plugin (export default runMigrations([...], { table })).`);
+    }
+    await plugin(null);
+    return { status: "applied", plugin: APP_DB_PLUGIN };
+}

package/dist/server/core-routes-plugin.d.ts

@@ -585,8 +585,8 @@ export declare function createPublicRemoteAgentsHandler(discover?: PublicAgentDi
     error: string;
     agents?: undefined;
 } | {
-    agents: Omit<import("./agent-discovery.js").DiscoveredAgent, "auth" | "kind">[];
     error?: undefined;
+    agents: Omit<import("./agent-discovery.js").DiscoveredAgent, "auth" | "kind">[];
 }>>;
 export declare function getBuilderConnectErrorDisposition(error: unknown, connectAttemptId: string | null): "correlated" | "legacy" | null;
 export declare function getBuilderConnectErrorKey(ownerEmail: string, connectAttemptId?: string | null): string;

package/dist/server/index.d.ts

@@ -38,6 +38,7 @@ export { createPollEventsHandler } from "./poll-events.js";
 export { createAuthPlugin, defaultAuthPlugin } from "./auth-plugin.js";
 export { BETTER_AUTH_MIGRATIONS, runBetterAuthMigrations, } from "./better-auth-migrations.js";
 export { runFrameworkReleaseMigrations } from "./release-migrations.js";
+export { runAppReleaseMigrations, type AppReleaseMigrationResult, } from "./app-release-migrations.js";
 export { initServerSentry, isServerSentryEnabled, setSentryUserForRequest, captureRouteError, type RouteErrorContext, } from "./sentry.js";
 export { captureError, captureServerError, registerErrorCaptureProvider, type CaptureErrorContext, type CaptureErrorProvider, } from "./capture-error.js";
 export { createSentryPlugin, defaultSentryPlugin } from "./sentry-plugin.js";

package/dist/server/index.js

@@ -37,6 +37,7 @@ export { createPollEventsHandler } from "./poll-events.js";
 export { createAuthPlugin, defaultAuthPlugin } from "./auth-plugin.js";
 export { BETTER_AUTH_MIGRATIONS, runBetterAuthMigrations, } from "./better-auth-migrations.js";
 export { runFrameworkReleaseMigrations } from "./release-migrations.js";
+export { runAppReleaseMigrations, } from "./app-release-migrations.js";
 export { initServerSentry, isServerSentryEnabled, setSentryUserForRequest, captureRouteError, } from "./sentry.js";
 export { captureError, captureServerError, registerErrorCaptureProvider, } from "./capture-error.js";
 export { createSentryPlugin, defaultSentryPlugin } from "./sentry-plugin.js";

package/dist/templates/builder-code-starter/.agents/skills/storing-data/SKILL.md.patch

@@ -1,7 +1,7 @@
 ===================================================================
 --- a/.agents/skills/storing-data/SKILL.md
 +++ b/.agents/skills/storing-data/SKILL.md
-@@ -36,21 +36,12 @@
+@@ -36,23 +36,12 @@
  such as `ownableColumns()` and `createSharesTable()`, from
  `@agent-native/core/db/schema`. Do not import table builders through the core
  helper module.
@@ -13,12 +13,14 @@
 -Drizzle Kit setup; follow their local instructions and the Database docs for
 -the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 -with `createGetDb(schema)`, and `server/plugins/db.ts` with
--`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
--do not create a parallel `runMigrations([...])` list beside a generated Drizzle
--migration owner. Give each handwritten migration a unique, stable `name`
+-`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+-framework tables and then that plugin (`runAppReleaseMigrations`), because a
+-release-owned deploy skips it at boot; a project with a Drizzle config is left to
+-`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+-generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 -alongside its `version`; append changes instead of renumbering, reusing, or
 -editing an applied entry.
-+When the project contains `drizzle.config.ts` and `drizzle/START_HERE.md`, that managed Drizzle scaffold is the only app migration path. Define app tables in `drizzle/schema.ts`, run `pnpm db:generate`, and apply them with `pnpm db:migrate`. `scripts/migrate-production.ts` is framework-only: do not create a parallel `runMigrations([...])` list in `server/plugins/db.ts` or import an app migration runner into the release script.
++When the project contains `drizzle.config.ts` and `drizzle/START_HERE.md`, that managed Drizzle scaffold is the only app migration path. Define app tables in `drizzle/schema.ts`, run `pnpm db:generate`, and apply them with `pnpm db:migrate`. `scripts/migrate-production.ts` applies the framework tables and leaves app tables to `db:migrate` (it skips `server/plugins/db.ts` when `drizzle.config.ts` exists): do not create a parallel `runMigrations([...])` list in `server/plugins/db.ts` or import an app migration runner into the release script.
  
 +In projects without that managed scaffold, every entry added to a framework `runMigrations([...])` list (`@agent-native/core/db`) needs a unique, stable `name` alongside its `version`; append changes instead of renumbering, reusing, or editing an applied entry.
 +
@@ -26,7 +28,7 @@
  
  Existing unnamed migrations don't need to be renamed retroactively (the two gating strategies coexist), but any new entry should always carry a name.
  
-@@ -70,12 +61,12 @@
+@@ -72,12 +61,12 @@
  | `sessions`          | Auth sessions                                        | `@agent-native/core/server`               |
  
  ### Domain Data (per-template)

package/dist/templates/builder-code-starter/scripts/migrate-production.ts.patch

@@ -7,10 +7,10 @@
 +
  import { closeDbExec, withMigrationRuntime } from "@agent-native/core/db";
  import { loadEnv } from "@agent-native/core/scripts";
- import { runFrameworkReleaseMigrations } from "@agent-native/core/server";
- 
-@@ -9,8 +12,37 @@
-     await runFrameworkReleaseMigrations(null);
+ import {
+   runAppReleaseMigrations,
+@@ -13,8 +16,37 @@
+     await runAppReleaseMigrations();
    });
  }
  

package/dist/templates/chat/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/dist/templates/chat/scripts/migrate-production.ts

@@ -1,12 +1,16 @@
 import { closeDbExec, withMigrationRuntime } from "@agent-native/core/db";
 import { loadEnv } from "@agent-native/core/scripts";
-import { runFrameworkReleaseMigrations } from "@agent-native/core/server";
+import {
+  runAppReleaseMigrations,
+  runFrameworkReleaseMigrations,
+} from "@agent-native/core/server";
 
 loadEnv();
 
 async function main(): Promise<void> {
   await withMigrationRuntime(async () => {
     await runFrameworkReleaseMigrations(null);
+    await runAppReleaseMigrations();
   });
 }
 

package/dist/templates/default/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/dist/templates/default/scripts/migrate-production.ts

@@ -1,12 +1,16 @@
 import { closeDbExec, withMigrationRuntime } from "@agent-native/core/db";
 import { loadEnv } from "@agent-native/core/scripts";
-import { runFrameworkReleaseMigrations } from "@agent-native/core/server";
+import {
+  runAppReleaseMigrations,
+  runFrameworkReleaseMigrations,
+} from "@agent-native/core/server";
 
 loadEnv();
 
 async function main(): Promise<void> {
   await withMigrationRuntime(async () => {
     await runFrameworkReleaseMigrations(null);
+    await runAppReleaseMigrations();
   });
 }
 

package/dist/templates/headless/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

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

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/dist/triggers/actions/manage-automation.d.ts

@@ -14,7 +14,6 @@ declare const _default: import("../../action.js").ActionDefinition<{
     executionCwd?: string;
 }, {
     deleted?: undefined;
-    enabled?: undefined;
     created: boolean;
     name: string;
     scope: "organization" | "personal";
@@ -25,24 +24,25 @@ declare const _default: import("../../action.js").ActionDefinition<{
     reasoningEffort: "auto" | "high" | "low" | "max" | "medium" | "minimal" | "none" | "xhigh";
     webhookPath: string;
     nextRun: string;
+    enabled?: undefined;
     executionHostId?: undefined;
     executionEngine?: undefined;
     executionCwd?: undefined;
 } | {
-    enabled?: undefined;
-    nextRun?: undefined;
     created?: undefined;
     scope?: undefined;
     triggerType?: undefined;
     event?: undefined;
     deleted: boolean;
     name: string;
+    enabled?: undefined;
     schedule?: undefined;
     timezone?: undefined;
     reasoningEffort?: undefined;
     executionHostId?: undefined;
     executionEngine?: undefined;
     executionCwd?: undefined;
+    nextRun?: undefined;
     webhookPath?: undefined;
 } | {
     deleted?: undefined;

package/package.json

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

package/src/templates/builder-code-starter/.agents/skills/storing-data/SKILL.md.patch

@@ -1,7 +1,7 @@
 ===================================================================
 --- a/.agents/skills/storing-data/SKILL.md
 +++ b/.agents/skills/storing-data/SKILL.md
-@@ -36,21 +36,12 @@
+@@ -36,23 +36,12 @@
  such as `ownableColumns()` and `createSharesTable()`, from
  `@agent-native/core/db/schema`. Do not import table builders through the core
  helper module.
@@ -13,12 +13,14 @@
 -Drizzle Kit setup; follow their local instructions and the Database docs for
 -the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 -with `createGetDb(schema)`, and `server/plugins/db.ts` with
--`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
--do not create a parallel `runMigrations([...])` list beside a generated Drizzle
--migration owner. Give each handwritten migration a unique, stable `name`
+-`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+-framework tables and then that plugin (`runAppReleaseMigrations`), because a
+-release-owned deploy skips it at boot; a project with a Drizzle config is left to
+-`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+-generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 -alongside its `version`; append changes instead of renumbering, reusing, or
 -editing an applied entry.
-+When the project contains `drizzle.config.ts` and `drizzle/START_HERE.md`, that managed Drizzle scaffold is the only app migration path. Define app tables in `drizzle/schema.ts`, run `pnpm db:generate`, and apply them with `pnpm db:migrate`. `scripts/migrate-production.ts` is framework-only: do not create a parallel `runMigrations([...])` list in `server/plugins/db.ts` or import an app migration runner into the release script.
++When the project contains `drizzle.config.ts` and `drizzle/START_HERE.md`, that managed Drizzle scaffold is the only app migration path. Define app tables in `drizzle/schema.ts`, run `pnpm db:generate`, and apply them with `pnpm db:migrate`. `scripts/migrate-production.ts` applies the framework tables and leaves app tables to `db:migrate` (it skips `server/plugins/db.ts` when `drizzle.config.ts` exists): do not create a parallel `runMigrations([...])` list in `server/plugins/db.ts` or import an app migration runner into the release script.
  
 +In projects without that managed scaffold, every entry added to a framework `runMigrations([...])` list (`@agent-native/core/db`) needs a unique, stable `name` alongside its `version`; append changes instead of renumbering, reusing, or editing an applied entry.
 +
@@ -26,7 +28,7 @@
  
  Existing unnamed migrations don't need to be renamed retroactively (the two gating strategies coexist), but any new entry should always carry a name.
  
-@@ -70,12 +61,12 @@
+@@ -72,12 +61,12 @@
  | `sessions`          | Auth sessions                                        | `@agent-native/core/server`               |
  
  ### Domain Data (per-template)

package/src/templates/builder-code-starter/scripts/migrate-production.ts.patch

@@ -7,10 +7,10 @@
 +
  import { closeDbExec, withMigrationRuntime } from "@agent-native/core/db";
  import { loadEnv } from "@agent-native/core/scripts";
- import { runFrameworkReleaseMigrations } from "@agent-native/core/server";
- 
-@@ -9,8 +12,37 @@
-     await runFrameworkReleaseMigrations(null);
+ import {
+   runAppReleaseMigrations,
+@@ -13,8 +16,37 @@
+     await runAppReleaseMigrations();
    });
  }
  

package/src/templates/chat/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/src/templates/chat/scripts/migrate-production.ts

@@ -1,12 +1,16 @@
 import { closeDbExec, withMigrationRuntime } from "@agent-native/core/db";
 import { loadEnv } from "@agent-native/core/scripts";
-import { runFrameworkReleaseMigrations } from "@agent-native/core/server";
+import {
+  runAppReleaseMigrations,
+  runFrameworkReleaseMigrations,
+} from "@agent-native/core/server";
 
 loadEnv();
 
 async function main(): Promise<void> {
   await withMigrationRuntime(async () => {
     await runFrameworkReleaseMigrations(null);
+    await runAppReleaseMigrations();
   });
 }
 

package/src/templates/default/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/src/templates/default/scripts/migrate-production.ts

@@ -1,12 +1,16 @@
 import { closeDbExec, withMigrationRuntime } from "@agent-native/core/db";
 import { loadEnv } from "@agent-native/core/scripts";
-import { runFrameworkReleaseMigrations } from "@agent-native/core/server";
+import {
+  runAppReleaseMigrations,
+  runFrameworkReleaseMigrations,
+} from "@agent-native/core/server";
 
 loadEnv();
 
 async function main(): Promise<void> {
   await withMigrationRuntime(async () => {
     await runFrameworkReleaseMigrations(null);
+    await runAppReleaseMigrations();
   });
 }
 

package/src/templates/headless/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/src/templates/workspace-core/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.