@agent-native/core 0.74.0 → 0.75.1

package/dist/deploy/build.d.ts

@@ -42,8 +42,19 @@ export declare function findInstalledResvgPackages(nodeModulesRoots: string[]):
 /**
  * Deploy-time gate for emitting the second `-background` Netlify function.
  * Reads the same env flag the runtime gate uses
- * (`AGENT_CHAT_DURABLE_BACKGROUND`). Off by default — when off, the deploy
- * emits exactly one function (today's behavior, byte-for-byte).
+ * (`AGENT_CHAT_DURABLE_BACKGROUND`).
+ *
+ * DEFAULT-ON, matching the runtime gate (`isFlagEnabled` in
+ * durable-background.ts): unset/empty/unknown means enabled; an app opts OUT
+ * only with an explicit falsy value (`false`/`0`/`no`/`off`). This is what
+ * actually emits the 15-min `-background` function so the `_process-run`
+ * dispatch lands on it (async 202 → the worker runs with the real 15-min budget
+ * → its ~13-min soft-timeout fits). The deploy gate and runtime gate MUST agree:
+ * if the deploy emitted no `-background` function but the runtime still routed
+ * the worker into the ~13-min timeout regime, the worker would overshoot the
+ * ~60s synchronous wall and re-dispatch in a loop. (The runtime now also guards
+ * the ~13-min budget on the real function name via `isInBackgroundFunctionRuntime`,
+ * so a missing emit degrades to clean 40s-chunked runs rather than the loop.)
  */
 export declare function isDurableBackgroundDeployEnabled(): boolean;
 /**
@@ -57,15 +68,20 @@ export declare function isDurableBackgroundDeployEnabled(): boolean;
  * that directory to a sibling `<...>-background` function and write an entry
  * with a `config.path` of the process-run route.
  *
- * ⚠️ REAL-DEPLOY VERIFICATION REQUIRED. Whether Netlify routes
- * `/_agent-native/agent-chat/_process-run` to this `-background` function (and
- * invokes it asynchronously with the 15-min budget) vs the synchronous Nitro
- * function cannot be verified in this environment — Nitro owns the primary
- * function's routing manifest, and the precedence between the two functions for
- * that path is a Netlify runtime behavior. If routing resolves to the
- * synchronous function, the run still completes via the existing 40s
- * soft-timeout path (no durable win, no regression). See
- * docs/design/durable-agent-runs.md (Open risks #1).
+ * The function declares `background: true` so Netlify invokes it ASYNC (HTTP
+ * 202 ack) with the 15-min budget, and a `config.path` of the process-run route
+ * so the `_process-run` self-dispatch lands on it. The earlier version set the
+ * path but omitted `background: true` and relied on the legacy `-background`
+ * filename — which the `config` object overrides — so Netlify served it
+ * SYNCHRONOUSLY (~60s) and the durable worker never got the 15-min budget
+ * (confirmed live: a POST to the process-run path returned a synchronous 401
+ * from the handler instead of a 202 async ack).
+ *
+ * ⚠️ One Netlify runtime behavior still resolves only on a real deploy: the
+ * routing precedence between this function's `config.path` and Nitro's catch-all
+ * for that exact path. If the catch-all wins, the run still completes via the
+ * 40s soft-timeout path on the sync function (no durable win, no regression).
+ * See docs/design/durable-agent-runs.md (Open risks #1).
  */
 export declare function emitSingleTemplateNetlifyBackgroundFunction(projectCwd: string): void;
 /**

package/dist/deploy/build.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"build.d.ts","sourceRoot":"","sources":["../../src/deploy/build.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;GAYG;AAOH,OAAO,EAML,KAAK,eAAe,EACpB,KAAK,gBAAgB,EACtB,MAAM,sBAAsB,CAAC;AAC9B,OAAO,EAEL,KAAK,oBAAoB,EAC1B,MAAM,qBAAqB,CAAC;AA4B7B,eAAO,MAAM,6BAA6B,UAiBzC,CAAC;AAuBF,wBAAgB,wCAAwC,CACtD,WAAW,EAAE,MAAM,EAAE,GACpB,MAAM,CAaR;AAgBD,KAAK,UAAU,GAAG,MAAM,CAAC,MAAM,EAAE;IAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,CAAC,CAAC;AAgBvE,wBAAgB,yCAAyC,CACvD,UAAU,EAAE,UAAU,EACtB,SAAS,EAAE,MAAM,EACjB,WAAW,SAAK,GACf,IAAI,CAQN;AAED;;;;;;;;GAQG;AACH,wBAAgB,mBAAmB,CACjC,MAAM,EAAE,eAAe,EAAE,EACzB,WAAW,EAAE,MAAM,EAAE,EACrB,kBAAkB,GAAE,MAAM,EAAO,EACjC,OAAO,GAAE,gBAAgB,EAAO,EAChC,aAAa,GAAE,oBAAoB,GAAG,IAAW,EACjD,mBAAmB,GAAE,MAAM,EAAO,EAClC,gBAAgB,SAAmC,GAClD,MAAM,CAskBR;AAyXD,wBAAgB,mBAAmB,IAAI,MAAM,EAAE,CAE9C;AAkHD,wBAAgB,OAAO,CACrB,GAAG,EAAE,MAAM,EACX,IAAI,EAAE,MAAM,EACZ,iBAAiB,cAAoB,QAoCtC;AAuBD,KAAK,0BAA0B,GAAG,OAAO,GAAG,KAAK,CAAC;AAQlD,wBAAgB,qCAAqC,CACnD,YAAY,GAAE,MAAM,CAAC,QAA2B,EAChD,QAAQ,GAAE,MAAM,CAAC,YAA2B,EAC5C,UAAU,GAAE,0BAA0B,GAAG,IAAgD,GACxF,OAAO,CAOT;AAqED,wBAAgB,gCAAgC,CAC9C,gBAAgB,EAAE,MAAM,EAAE,GACzB,MAAM,GAAG,IAAI,CA8Bf;AAED,wBAAgB,0BAA0B,CACxC,gBAAgB,EAAE,MAAM,EAAE,GACzB,KAAK,CAAC;IAAE,WAAW,EAAE,MAAM,CAAC;IAAC,UAAU,EAAE,MAAM,CAAA;CAAE,CAAC,CAqCpD;AAED;;;;;GAKG;AACH,wBAAgB,gCAAgC,IAAI,OAAO,CAK1D;AAED;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAgB,2CAA2C,CACzD,UAAU,EAAE,MAAM,GACjB,IAAI,CAyCN;AAkND;;;GAGG;AACH,MAAM,WAAW,eAAe;IAC9B,OAAO,EAAE,CAAC,KAAK,EAAE,GAAG,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IACvC,gBAAgB,EAAE,CAAC,KAAK,EAAE,GAAG,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAChD,UAAU,EAAE,CAAC,KAAK,EAAE,GAAG,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;CAC3C;AAED,MAAM,WAAW,yBAAyB;IACxC,KAAK,EAAE,GAAG,CAAC;IACX,KAAK,EAAE,eAAe,CAAC;IACvB,SAAS,EAAE,MAAM,CAAC;IAClB,eAAe,EAAE,MAAM,GAAG,SAAS,CAAC;IACpC,WAAW,EAAE,MAAM,CAAC;IACpB,GAAG,EAAE,MAAM,CAAC;CACb;AAED;;;;;;;;;;;GAWG;AACH,wBAAsB,qBAAqB,CACzC,IAAI,EAAE,yBAAyB,GAC9B,OAAO,CAAC,IAAI,CAAC,CA+Bf"}
+{"version":3,"file":"build.d.ts","sourceRoot":"","sources":["../../src/deploy/build.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;GAYG;AAOH,OAAO,EAML,KAAK,eAAe,EACpB,KAAK,gBAAgB,EACtB,MAAM,sBAAsB,CAAC;AAC9B,OAAO,EAEL,KAAK,oBAAoB,EAC1B,MAAM,qBAAqB,CAAC;AA4B7B,eAAO,MAAM,6BAA6B,UAiBzC,CAAC;AAuBF,wBAAgB,wCAAwC,CACtD,WAAW,EAAE,MAAM,EAAE,GACpB,MAAM,CAaR;AAgBD,KAAK,UAAU,GAAG,MAAM,CAAC,MAAM,EAAE;IAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,CAAC,CAAC;AAgBvE,wBAAgB,yCAAyC,CACvD,UAAU,EAAE,UAAU,EACtB,SAAS,EAAE,MAAM,EACjB,WAAW,SAAK,GACf,IAAI,CAQN;AAED;;;;;;;;GAQG;AACH,wBAAgB,mBAAmB,CACjC,MAAM,EAAE,eAAe,EAAE,EACzB,WAAW,EAAE,MAAM,EAAE,EACrB,kBAAkB,GAAE,MAAM,EAAO,EACjC,OAAO,GAAE,gBAAgB,EAAO,EAChC,aAAa,GAAE,oBAAoB,GAAG,IAAW,EACjD,mBAAmB,GAAE,MAAM,EAAO,EAClC,gBAAgB,SAAmC,GAClD,MAAM,CAskBR;AAyXD,wBAAgB,mBAAmB,IAAI,MAAM,EAAE,CAE9C;AAkHD,wBAAgB,OAAO,CACrB,GAAG,EAAE,MAAM,EACX,IAAI,EAAE,MAAM,EACZ,iBAAiB,cAAoB,QAoCtC;AAuBD,KAAK,0BAA0B,GAAG,OAAO,GAAG,KAAK,CAAC;AAQlD,wBAAgB,qCAAqC,CACnD,YAAY,GAAE,MAAM,CAAC,QAA2B,EAChD,QAAQ,GAAE,MAAM,CAAC,YAA2B,EAC5C,UAAU,GAAE,0BAA0B,GAAG,IAAgD,GACxF,OAAO,CAOT;AAqED,wBAAgB,gCAAgC,CAC9C,gBAAgB,EAAE,MAAM,EAAE,GACzB,MAAM,GAAG,IAAI,CA8Bf;AAED,wBAAgB,0BAA0B,CACxC,gBAAgB,EAAE,MAAM,EAAE,GACzB,KAAK,CAAC;IAAE,WAAW,EAAE,MAAM,CAAC;IAAC,UAAU,EAAE,MAAM,CAAA;CAAE,CAAC,CAqCpD;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,gCAAgC,IAAI,OAAO,CAK1D;AAED;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,2CAA2C,CACzD,UAAU,EAAE,MAAM,GACjB,IAAI,CA2DN;AAkND;;;GAGG;AACH,MAAM,WAAW,eAAe;IAC9B,OAAO,EAAE,CAAC,KAAK,EAAE,GAAG,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IACvC,gBAAgB,EAAE,CAAC,KAAK,EAAE,GAAG,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAChD,UAAU,EAAE,CAAC,KAAK,EAAE,GAAG,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;CAC3C;AAED,MAAM,WAAW,yBAAyB;IACxC,KAAK,EAAE,GAAG,CAAC;IACX,KAAK,EAAE,eAAe,CAAC;IACvB,SAAS,EAAE,MAAM,CAAC;IAClB,eAAe,EAAE,MAAM,GAAG,SAAS,CAAC;IACpC,WAAW,EAAE,MAAM,CAAC;IACpB,GAAG,EAAE,MAAM,CAAC;CACb;AAED;;;;;;;;;;;GAWG;AACH,wBAAsB,qBAAqB,CACzC,IAAI,EAAE,yBAAyB,GAC9B,OAAO,CAAC,IAAI,CAAC,CA+Bf"}

package/dist/deploy/build.js

@@ -1230,15 +1230,26 @@ export function findInstalledResvgPackages(nodeModulesRoots) {
 /**
  * Deploy-time gate for emitting the second `-background` Netlify function.
  * Reads the same env flag the runtime gate uses
- * (`AGENT_CHAT_DURABLE_BACKGROUND`). Off by default — when off, the deploy
- * emits exactly one function (today's behavior, byte-for-byte).
+ * (`AGENT_CHAT_DURABLE_BACKGROUND`).
+ *
+ * DEFAULT-ON, matching the runtime gate (`isFlagEnabled` in
+ * durable-background.ts): unset/empty/unknown means enabled; an app opts OUT
+ * only with an explicit falsy value (`false`/`0`/`no`/`off`). This is what
+ * actually emits the 15-min `-background` function so the `_process-run`
+ * dispatch lands on it (async 202 → the worker runs with the real 15-min budget
+ * → its ~13-min soft-timeout fits). The deploy gate and runtime gate MUST agree:
+ * if the deploy emitted no `-background` function but the runtime still routed
+ * the worker into the ~13-min timeout regime, the worker would overshoot the
+ * ~60s synchronous wall and re-dispatch in a loop. (The runtime now also guards
+ * the ~13-min budget on the real function name via `isInBackgroundFunctionRuntime`,
+ * so a missing emit degrades to clean 40s-chunked runs rather than the loop.)
  */
 export function isDurableBackgroundDeployEnabled() {
     const raw = process.env.AGENT_CHAT_DURABLE_BACKGROUND;
     if (raw == null)
-        return false;
+        return true;
     const v = raw.trim().toLowerCase();
-    return v === "1" || v === "true" || v === "yes" || v === "on";
+    return !(v === "0" || v === "false" || v === "no" || v === "off");
 }
 /**
  * Single-template Netlify build: emit a SECOND function whose name ends in
@@ -1251,15 +1262,20 @@ export function isDurableBackgroundDeployEnabled() {
  * that directory to a sibling `<...>-background` function and write an entry
  * with a `config.path` of the process-run route.
  *
- * ⚠️ REAL-DEPLOY VERIFICATION REQUIRED. Whether Netlify routes
- * `/_agent-native/agent-chat/_process-run` to this `-background` function (and
- * invokes it asynchronously with the 15-min budget) vs the synchronous Nitro
- * function cannot be verified in this environment — Nitro owns the primary
- * function's routing manifest, and the precedence between the two functions for
- * that path is a Netlify runtime behavior. If routing resolves to the
- * synchronous function, the run still completes via the existing 40s
- * soft-timeout path (no durable win, no regression). See
- * docs/design/durable-agent-runs.md (Open risks #1).
+ * The function declares `background: true` so Netlify invokes it ASYNC (HTTP
+ * 202 ack) with the 15-min budget, and a `config.path` of the process-run route
+ * so the `_process-run` self-dispatch lands on it. The earlier version set the
+ * path but omitted `background: true` and relied on the legacy `-background`
+ * filename — which the `config` object overrides — so Netlify served it
+ * SYNCHRONOUSLY (~60s) and the durable worker never got the 15-min budget
+ * (confirmed live: a POST to the process-run path returned a synchronous 401
+ * from the handler instead of a 202 async ack).
+ *
+ * ⚠️ One Netlify runtime behavior still resolves only on a real deploy: the
+ * routing precedence between this function's `config.path` and Nitro's catch-all
+ * for that exact path. If the catch-all wins, the run still completes via the
+ * 40s soft-timeout path on the sync function (no durable win, no regression).
+ * See docs/design/durable-agent-runs.md (Open risks #1).
  */
 export function emitSingleTemplateNetlifyBackgroundFunction(projectCwd) {
     const functionsDir = path.join(projectCwd, ".netlify", "functions-internal");
@@ -1277,7 +1293,16 @@ export function emitSingleTemplateNetlifyBackgroundFunction(projectCwd) {
     copyDir(serverDir, dest);
     // Drop the original Nitro entry so our background entry is the entrypoint.
     fs.rmSync(path.join(dest, "server.mjs"), { force: true });
-    const entry = `let cachedHandler;
+    const entry = `// Mark this isolate as the durable background runtime BEFORE the handler
+// bundle is imported, so isInBackgroundFunctionRuntime() reliably returns true
+// in this function. The deployed Lambda name is NOT guaranteed to end in
+// "-background" (Netlify may mangle/prefix it), so we cannot depend on
+// AWS_LAMBDA_FUNCTION_NAME alone. A globalThis flag (NOT process.env) avoids the
+// no-env-mutation guard and carries no cross-request state — it is a static,
+// set-once isolate marker read back by isInBackgroundFunctionRuntime().
+globalThis.__AGENT_NATIVE_BACKGROUND_RUNTIME__ = true;
+
+let cachedHandler;
 
 export default async function handler(...args) {
   cachedHandler ??= (await import("./main.mjs")).default;
@@ -1287,6 +1312,15 @@ export default async function handler(...args) {
 export const config = {
   name: "agent background handler",
   generator: "agent-native build",
+  // background: true is what actually makes Netlify invoke this ASYNCHRONOUSLY
+  // (immediate HTTP 202 ack) with the 15-minute budget. Without it, a function
+  // that declares a custom \`path\` is served SYNCHRONOUSLY (~60s) even when its
+  // file name ends in "-background" — the \`config\` object overrides the legacy
+  // filename convention. That omission is why the durable worker was capped at
+  // ~60s in prod (verified live: POST to the process-run path returned a
+  // synchronous 401 from the handler, not a 202 async ack). See Netlify docs:
+  // build/functions/background-functions + build/functions/configuration.
+  background: true,
   path: ${JSON.stringify([AGENT_CHAT_PROCESS_RUN_PATH])},
   nodeBundler: "none",
   includedFiles: ["**"],
@@ -1686,11 +1720,12 @@ export default bundle;
         copyInstalledResvgPackages(nitro.options.output.serverDir);
         copyInstalledFfmpegStaticPackage(nitro.options.output.serverDir);
     }
-    // Durable background agent runs (off by default). Additive ONLY: emits a
-    // SECOND Netlify function whose name ends in `-background` re-exporting the
-    // same handler bundle, so the chat `_process-run` POST lands on Netlify's
-    // async (15-min) function. When the flag is off this is a no-op and the
-    // single-function deploy is byte-for-byte unchanged.
+    // Durable background agent runs (default-ON; opt out with a falsy
+    // AGENT_CHAT_DURABLE_BACKGROUND). Additive ONLY: emits a SECOND Netlify
+    // function whose name ends in `-background` re-exporting the same handler
+    // bundle, so the chat `_process-run` POST lands on Netlify's async (15-min)
+    // function. When explicitly opted out this is a no-op and the single-function
+    // deploy is byte-for-byte unchanged.
     if (preset === "netlify" && isDurableBackgroundDeployEnabled()) {
         try {
             emitSingleTemplateNetlifyBackgroundFunction(cwd);