@agent-native/core 0.75.0 → 0.75.1

package/corpus/core/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @agent-native/core
 
+## 0.75.1
+
+### Patch Changes
+
+- 98b89e2: Durable background agent-chat runs now actually receive Netlify's 15-min async
+  budget. The emitted `-background` function declared a custom `config.path` but
+  omitted `background: true`, so Netlify served it SYNCHRONOUSLY (~60s) — the
+  `config` object overrides the legacy `-background` filename convention — and the
+  durable worker was capped at the 60s wall (it degraded to 40s-chunked runs and
+  never used the 15-min budget). The emit now sets `background: true` (immediate
+  202 ack + 15-min execution) and force-marks the background runtime in the
+  function entry so the worker reliably takes the ~13-min soft-timeout regardless
+  of the deployed Lambda name. Root cause confirmed with a live prod routing probe
+  (POST to the process-run path returned a synchronous 401 from the handler
+  instead of a 202 async ack).
+
 ## 0.75.0
 
 ### Minor Changes

package/corpus/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.75.0",
+  "version": "0.75.1",
   "type": "module",
   "engines": {
     "node": ">=22"

package/corpus/core/src/agent/durable-background.ts

@@ -112,11 +112,23 @@ export function isHostedRuntimeForDurableBackground(): boolean {
  * hard wall and get killed at 60s, then re-dispatch/resume in a wasteful loop.
  * So the 13-min budget is taken ONLY when this returns true.
  *
- * Falls back to the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy)
- * for hosts that don't expose a `-background`-suffixed function name but where
- * the operator has confirmed a long async budget. Off by default.
+ * The PRIMARY signal is a `globalThis` marker the emitted background function's
+ * entry sets at cold start — the deployed Lambda name is not guaranteed to end
+ * in `-background` on Netlify, so the entry marks its own runtime. A `globalThis`
+ * flag (not `process.env`) keeps the no-env-mutation guard satisfied and carries
+ * no cross-request state (set once per isolate). The `AWS_LAMBDA_FUNCTION_NAME`
+ * suffix and the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy) are
+ * additional signals — the latter an operator escape hatch. Off by default.
  */
 export function isInBackgroundFunctionRuntime(): boolean {
+  // Set by the emitted `-background` function entry at cold start (the primary,
+  // most reliable signal — see the emit in deploy/build.ts).
+  if (
+    (globalThis as Record<string, unknown>)
+      .__AGENT_NATIVE_BACKGROUND_RUNTIME__ === true
+  ) {
+    return true;
+  }
   const lambdaName = process.env.AWS_LAMBDA_FUNCTION_NAME;
   if (
     typeof lambdaName === "string" &&

package/corpus/core/src/cli/skills.ts

@@ -394,14 +394,16 @@ sign-in at setup — this is intended), so the first tool call in that client do
 not hit an OAuth wall:
 
 \`\`\`bash
-npx @agent-native/core@latest skills add visual-plan
+npx @agent-native/core@latest skills add visual-plans
 \`\`\`
 
 After that, \`/visual-plan\` and \`/visual-recap\` are the two installed slash
-commands. The other planning modes (\`create-ui-plan\`, \`create-prototype-plan\`,
-\`create-plan-design\`, \`create-visual-questions\`) are MCP tools reachable from
-\`/visual-plan\`, not separate slash commands. Pass \`--no-connect\` to register
-the connector without authenticating, then run
+commands. If you only need one command, use \`skills add visual-plan\` or
+\`skills add visual-recap\` instead. The other planning modes
+(\`create-ui-plan\`, \`create-prototype-plan\`, \`create-plan-design\`,
+\`create-visual-questions\`) are MCP tools reachable from \`/visual-plan\`, not
+separate slash commands. Pass \`--no-connect\` to register the connector without
+authenticating, then run
 \`npx @agent-native/core@latest connect https://plan.agent-native.com --client all\`
 whenever you are ready, or choose a narrower \`--client\`. Auth and MCP tool
 loading are per client config/session.
@@ -410,7 +412,7 @@ loading are per client config/session.
 install with \`--mode local-files\`:
 
 \`\`\`bash
-npx @agent-native/core@latest skills add visual-plan --mode local-files
+npx @agent-native/core@latest skills add visual-plans --mode local-files
 \`\`\`
 
 This mode does not register the Plan MCP connector. Before authoring structured
@@ -1648,14 +1650,16 @@ sign-in at setup — this is intended), so the first tool call in that client do
 not hit an OAuth wall:
 
 \`\`\`bash
-npx @agent-native/core@latest skills add visual-plan
+npx @agent-native/core@latest skills add visual-plans
 \`\`\`
 
 After that, \`/visual-plan\` and \`/visual-recap\` are the two installed slash
-commands. The other planning modes (\`create-ui-plan\`, \`create-prototype-plan\`,
-\`create-plan-design\`, \`create-visual-questions\`) are MCP tools reachable from
-\`/visual-plan\`, not separate slash commands. Pass \`--no-connect\` to register
-the connector without authenticating, then run
+commands. If you only need one command, use \`skills add visual-plan\` or
+\`skills add visual-recap\` instead. The other planning modes
+(\`create-ui-plan\`, \`create-prototype-plan\`, \`create-plan-design\`,
+\`create-visual-questions\`) are MCP tools reachable from \`/visual-plan\`, not
+separate slash commands. Pass \`--no-connect\` to register the connector without
+authenticating, then run
 \`npx @agent-native/core@latest connect https://plan.agent-native.com --client all\`
 whenever you are ready, or choose a narrower \`--client\`. Auth and MCP tool
 loading are per client config/session.

package/corpus/core/src/deploy/build.ts

@@ -1512,15 +1512,20 @@ export 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 function emitSingleTemplateNetlifyBackgroundFunction(
   projectCwd: string,
@@ -1543,7 +1548,16 @@ export function emitSingleTemplateNetlifyBackgroundFunction(
   // 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;
@@ -1553,6 +1567,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: ["**"],

package/corpus/core/src/templates/default/_gitignore

@@ -10,6 +10,7 @@ npm-debug.log*
 pnpm-debug.log*
 
 node_modules
+node-compile-cache/
 dist
 dist-ssr
 *.local

package/corpus/core/src/templates/headless/_gitignore

@@ -7,6 +7,7 @@ npm-debug.log*
 pnpm-debug.log*
 
 node_modules
+node-compile-cache/
 dist
 *.local
 

package/corpus/core/src/templates/workspace-root/_gitignore

@@ -28,6 +28,7 @@ packages/*/.env
 # pnpm
 .pnpm-store/
 pnpm-debug.log*
+node-compile-cache/
 
 # Local workspace data
 data/

package/corpus/templates/clips/actions/list-recordings.ts

@@ -55,6 +55,15 @@ export default defineAction({
       .describe("Sort order"),
     limit: z.coerce.number().int().min(1).max(500).default(100),
     offset: z.coerce.number().int().min(0).default(0),
+    countOnly: z
+      // Robust coercion: a GET query param arrives as the string "true"/"false",
+      // and z.coerce.boolean would treat "false" as true. Map strings explicitly.
+      .preprocess(
+        (v) => (typeof v === "string" ? v === "true" : v),
+        z.boolean(),
+      )
+      .default(false)
+      .describe("Return only the total count, skipping the row payload"),
   }),
   http: { method: "GET" },
   run: async (args) => {
@@ -135,6 +144,18 @@ export default defineAction({
       );
     }
 
+    // Count-only callers (e.g. the sidebar badge) need just the total for the
+    // same filters, ignoring limit/offset. Run the COUNT and short-circuit
+    // before the row select, joins, and tag/view subqueries. Keeping it inside
+    // this branch means the normal list path doesn't pay for an extra query.
+    if (args.countOnly) {
+      const totalRows = await db
+        .select({ count: sql<number>`COUNT(1)` })
+        .from(schema.recordings)
+        .where(and(...whereClauses));
+      return { recordings: [], total: Number(totalRows[0]?.count ?? 0) };
+    }
+
     // Sort
     const viewCountOrder = sql<number>`(
       SELECT COUNT(1)

package/corpus/templates/clips/app/components/library/library-layout.tsx

@@ -46,6 +46,7 @@ import {
   useSpaces,
   useOrganizations,
   useCreateFolder,
+  useRecordingsCount,
 } from "@/hooks/use-library";
 import { useIsMobile } from "@/hooks/use-mobile";
 import { useDesktopPromo } from "@/hooks/use-desktop-promo";
@@ -124,6 +125,10 @@ export function LibraryLayout({ children }: LibraryLayoutProps) {
     { enabled: hasActiveOrg && Boolean(currentOrganizationId) },
   );
 
+  // Clip count for the "Library" nav item — count-only, no row payload or
+  // title polling across the app shell.
+  const { data: libraryCount } = useRecordingsCount({ view: "library" });
+
   const libFolderList: FolderNode[] = useMemo(
     () =>
       (libFolders?.folders ?? [])
@@ -176,12 +181,14 @@ export function LibraryLayout({ children }: LibraryLayoutProps) {
     label: string;
     icon: React.ComponentType<{ className?: string }>;
     match: (path: string) => boolean;
+    count?: number;
   }[] = [
     {
       to: "/library",
       label: "Library",
       icon: IconInbox,
       match: (p) => p.startsWith("/library"),
+      count: libraryCount,
     },
     {
       to: "/spaces",
@@ -374,7 +381,7 @@ export function LibraryLayout({ children }: LibraryLayoutProps) {
                   </div>
 
                   <nav className="mt-3 space-y-0.5 px-2">
-                    {navItems.map(({ to, label, icon: Icon, match }) => {
+                    {navItems.map(({ to, label, icon: Icon, match, count }) => {
                       const active = match(location.pathname);
                       return (
                         <NavLink
@@ -388,7 +395,19 @@ export function LibraryLayout({ children }: LibraryLayoutProps) {
                           )}
                         >
                           <Icon className="h-4 w-4" />
-                          {label}
+                          <span className="flex-1 truncate">{label}</span>
+                          {count !== undefined && count > 0 && (
+                            <span
+                              className={cn(
+                                "shrink-0 tabular-nums text-[11px]",
+                                active
+                                  ? "text-primary/80"
+                                  : "text-muted-foreground",
+                              )}
+                            >
+                              {count}
+                            </span>
+                          )}
                         </NavLink>
                       );
                     })}

package/corpus/templates/clips/app/hooks/use-library.ts

@@ -87,6 +87,24 @@ export function useRecordings(args: ListRecordingsArgs = {}) {
   );
 }
 
+/**
+ * Count-only variant for surfaces like the sidebar badge that need a total but
+ * not the rows. Hits `list-recordings` with `countOnly`, so it skips the row
+ * payload server-side and doesn't share (or pay for) the full-list query or its
+ * title polling.
+ */
+export function useRecordingsCount(
+  args: Omit<ListRecordingsArgs, "limit" | "offset"> = {},
+) {
+  return useActionQuery<number>(
+    "list-recordings",
+    { ...args, countOnly: true } as any,
+    {
+      select: (data: any) => (typeof data?.total === "number" ? data.total : 0),
+    },
+  );
+}
+
 export interface SearchHit {
   id: string;
   title: string;

package/corpus/templates/plan/.agents/skills/visual-plan/SKILL.md

@@ -489,14 +489,16 @@ sign-in at setup — this is intended), so the first tool call in that client do
 not hit an OAuth wall:
 
 ```bash
-npx @agent-native/core@latest skills add visual-plan
+npx @agent-native/core@latest skills add visual-plans
 ```
 
 After that, `/visual-plan` and `/visual-recap` are the two installed slash
-commands. The other planning modes (`create-ui-plan`, `create-prototype-plan`,
-`create-plan-design`, `create-visual-questions`) are MCP tools reachable from
-`/visual-plan`, not separate slash commands. Pass `--no-connect` to register
-the connector without authenticating, then run
+commands. If you only need one command, use `skills add visual-plan` or
+`skills add visual-recap` instead. The other planning modes
+(`create-ui-plan`, `create-prototype-plan`, `create-plan-design`,
+`create-visual-questions`) are MCP tools reachable from `/visual-plan`, not
+separate slash commands. Pass `--no-connect` to register the connector without
+authenticating, then run
 `npx @agent-native/core@latest connect https://plan.agent-native.com --client all`
 whenever you are ready, or choose a narrower `--client`. Auth and MCP tool
 loading are per client config/session.

package/dist/agent/durable-background.d.ts

@@ -39,9 +39,13 @@ export declare function isHostedRuntimeForDurableBackground(): boolean;
  * hard wall and get killed at 60s, then re-dispatch/resume in a wasteful loop.
  * So the 13-min budget is taken ONLY when this returns true.
  *
- * Falls back to the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy)
- * for hosts that don't expose a `-background`-suffixed function name but where
- * the operator has confirmed a long async budget. Off by default.
+ * The PRIMARY signal is a `globalThis` marker the emitted background function's
+ * entry sets at cold start — the deployed Lambda name is not guaranteed to end
+ * in `-background` on Netlify, so the entry marks its own runtime. A `globalThis`
+ * flag (not `process.env`) keeps the no-env-mutation guard satisfied and carries
+ * no cross-request state (set once per isolate). The `AWS_LAMBDA_FUNCTION_NAME`
+ * suffix and the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy) are
+ * additional signals — the latter an operator escape hatch. Off by default.
  */
 export declare function isInBackgroundFunctionRuntime(): boolean;
 /**

package/dist/agent/durable-background.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"durable-background.d.ts","sourceRoot":"","sources":["../../src/agent/durable-background.ts"],"names":[],"mappings":"AA6CA;;;;GAIG;AACH,eAAO,MAAM,2BAA2B,2CACE,CAAC;AAE3C;;;GAGG;AACH,eAAO,MAAM,iCAAiC,kCACb,CAAC;AAElC;;;;;;GAMG;AACH,eAAO,MAAM,+BAA+B,oBAAoB,CAAC;AAEjE;;;;GAIG;AACH,wBAAgB,mCAAmC,IAAI,OAAO,CAsB7D;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,6BAA6B,IAAI,OAAO,CAcvD;AAyBD;;;;;;GAMG;AACH,wBAAgB,mCAAmC,IAAI,OAAO,CAM7D;AAED,uDAAuD;AACvD,MAAM,MAAM,qBAAqB,GAC7B;IACE,EAAE,EAAE,IAAI,CAAC;IACT,+DAA+D;IAC/D,KAAK,EAAE,MAAM,CAAC;IACd,4EAA4E;IAC5E,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAC/B,GACD;IACE,EAAE,EAAE,KAAK,CAAC;IACV,2CAA2C;IAC3C,MAAM,EAAE,MAAM,CAAC;IACf,qBAAqB;IACrB,KAAK,EAAE,MAAM,CAAC;CACf,CAAC;AAEN;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,wBAAwB,CACtC,IAAI,EAAE,OAAO,EACb,UAAU,EAAE,MAAM,GAAG,SAAS,GAC7B,qBAAqB,CA0CvB"}
+{"version":3,"file":"durable-background.d.ts","sourceRoot":"","sources":["../../src/agent/durable-background.ts"],"names":[],"mappings":"AA6CA;;;;GAIG;AACH,eAAO,MAAM,2BAA2B,2CACE,CAAC;AAE3C;;;GAGG;AACH,eAAO,MAAM,iCAAiC,kCACb,CAAC;AAElC;;;;;;GAMG;AACH,eAAO,MAAM,+BAA+B,oBAAoB,CAAC;AAEjE;;;;GAIG;AACH,wBAAgB,mCAAmC,IAAI,OAAO,CAsB7D;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,6BAA6B,IAAI,OAAO,CAsBvD;AAyBD;;;;;;GAMG;AACH,wBAAgB,mCAAmC,IAAI,OAAO,CAM7D;AAED,uDAAuD;AACvD,MAAM,MAAM,qBAAqB,GAC7B;IACE,EAAE,EAAE,IAAI,CAAC;IACT,+DAA+D;IAC/D,KAAK,EAAE,MAAM,CAAC;IACd,4EAA4E;IAC5E,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAC/B,GACD;IACE,EAAE,EAAE,KAAK,CAAC;IACV,2CAA2C;IAC3C,MAAM,EAAE,MAAM,CAAC;IACf,qBAAqB;IACrB,KAAK,EAAE,MAAM,CAAC;CACf,CAAC;AAEN;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,wBAAwB,CACtC,IAAI,EAAE,OAAO,EACb,UAAU,EAAE,MAAM,GAAG,SAAS,GAC7B,qBAAqB,CA0CvB"}

package/dist/agent/durable-background.js

@@ -93,11 +93,21 @@ export function isHostedRuntimeForDurableBackground() {
  * hard wall and get killed at 60s, then re-dispatch/resume in a wasteful loop.
  * So the 13-min budget is taken ONLY when this returns true.
  *
- * Falls back to the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy)
- * for hosts that don't expose a `-background`-suffixed function name but where
- * the operator has confirmed a long async budget. Off by default.
+ * The PRIMARY signal is a `globalThis` marker the emitted background function's
+ * entry sets at cold start — the deployed Lambda name is not guaranteed to end
+ * in `-background` on Netlify, so the entry marks its own runtime. A `globalThis`
+ * flag (not `process.env`) keeps the no-env-mutation guard satisfied and carries
+ * no cross-request state (set once per isolate). The `AWS_LAMBDA_FUNCTION_NAME`
+ * suffix and the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy) are
+ * additional signals — the latter an operator escape hatch. Off by default.
  */
 export function isInBackgroundFunctionRuntime() {
+    // Set by the emitted `-background` function entry at cold start (the primary,
+    // most reliable signal — see the emit in deploy/build.ts).
+    if (globalThis
+        .__AGENT_NATIVE_BACKGROUND_RUNTIME__ === true) {
+        return true;
+    }
     const lambdaName = process.env.AWS_LAMBDA_FUNCTION_NAME;
     if (typeof lambdaName === "string" &&
         lambdaName.toLowerCase().endsWith("-background")) {

package/dist/agent/durable-background.js.map

@@ -1 +1 @@
-{"version":3,"file":"durable-background.js","sourceRoot":"","sources":["../../src/agent/durable-background.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmCG;AACH,OAAO,EACL,sBAAsB,EACtB,sBAAsB,GACvB,MAAM,uBAAuB,CAAC;AAC/B,OAAO,EACL,kBAAkB,EAClB,mBAAmB,GACpB,MAAM,mCAAmC,CAAC;AAE3C;;;;GAIG;AACH,MAAM,CAAC,MAAM,2BAA2B,GACtC,wCAAwC,CAAC;AAE3C;;;GAGG;AACH,MAAM,CAAC,MAAM,iCAAiC,GAC5C,+BAA+B,CAAC;AAElC;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,+BAA+B,GAAG,iBAAiB,CAAC;AAEjE;;;;GAIG;AACH,MAAM,UAAU,mCAAmC;IACjD,IACE,OAAO,CAAC,GAAG,CAAC,OAAO;QACnB,OAAO,CAAC,GAAG,CAAC,OAAO,KAAK,OAAO;QAC/B,OAAO,CAAC,GAAG,CAAC,aAAa,KAAK,MAAM,EACpC,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IACD,IACE,OAAO,CAAC,GAAG,CAAC,wBAAwB;QACpC,OAAO,CAAC,GAAG,CAAC,aAAa,KAAK,MAAM,EACpC,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IACD,OAAO,OAAO,CACZ,OAAO,CAAC,GAAG,CAAC,QAAQ;QACpB,OAAO,CAAC,GAAG,CAAC,MAAM;QAClB,OAAO,CAAC,GAAG,CAAC,UAAU;QACtB,OAAO,CAAC,GAAG,CAAC,MAAM;QAClB,OAAO,CAAC,GAAG,CAAC,YAAY;QACxB,OAAO,CAAC,GAAG,CAAC,SAAS,CACtB,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,UAAU,6BAA6B;IAC3C,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,wBAAwB,CAAC;IACxD,IACE,OAAO,UAAU,KAAK,QAAQ;QAC9B,UAAU,CAAC,WAAW,EAAE,CAAC,QAAQ,CAAC,aAAa,CAAC,EAChD,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IACD,MAAM,MAAM,GAAG,OAAO,CAAC,GAAG,CAAC,mCAAmC,CAAC;IAC/D,IAAI,MAAM,IAAI,IAAI,EAAE,CAAC;QACnB,MAAM,CAAC,GAAG,MAAM,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;QACtC,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC,KAAK,MAAM,IAAI,CAAC,KAAK,KAAK,IAAI,CAAC,KAAK,IAAI,CAAC;IAChE,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED,SAAS,aAAa;IACpB,8EAA8E;IAC9E,+EAA+E;IAC/E,kDAAkD;IAClD,EAAE;IACF,yEAAyE;IACzE,4EAA4E;IAC5E,sEAAsE;IACtE,8EAA8E;IAC9E,0EAA0E;IAC1E,oEAAoE;IACpE,mDAAmD;IACnD,MAAM,GAAG,GAAG,OAAO,CAAC,GAAG,CAAC,6BAA6B,CAAC;IACtD,IAAI,GAAG,IAAI,IAAI;QAAE,OAAO,IAAI,CAAC;IAC7B,MAAM,UAAU,GAAG,GAAG,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;IAC5C,OAAO,CAAC,CACN,UAAU,KAAK,GAAG;QAClB,UAAU,KAAK,OAAO;QACtB,UAAU,KAAK,IAAI;QACnB,UAAU,KAAK,KAAK,CACrB,CAAC;AACJ,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,mCAAmC;IACjD,OAAO,CACL,aAAa,EAAE;QACf,mCAAmC,EAAE;QACrC,sBAAsB,EAAE,CACzB,CAAC;AACJ,CAAC;AAmBD;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,wBAAwB,CACtC,IAAa,EACb,UAA8B;IAE9B,IAAI,CAAC,IAAI,IAAI,OAAO,IAAI,KAAK,QAAQ,EAAE,CAAC;QACtC,OAAO,EAAE,EAAE,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,EAAE,KAAK,EAAE,sBAAsB,EAAE,CAAC;IACnE,CAAC;IACD,MAAM,MAAM,GAAG,IAA+B,CAAC;IAC/C,MAAM,MAAM,GAAG,MAAM,CAAC,+BAA+B,CAExC,CAAC;IACd,MAAM,KAAK,GACT,MAAM,IAAI,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ;QACxC,CAAC,CAAC,MAAM,CAAC,KAAK;QACd,CAAC,CAAC,OAAO,MAAM,CAAC,MAAM,KAAK,QAAQ;YACjC,CAAC,CAAE,MAAM,CAAC,MAAiB;YAC3B,CAAC,CAAC,EAAE,CAAC;IACX,IAAI,CAAC,KAAK,EAAE,CAAC;QACX,OAAO,EAAE,EAAE,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,EAAE,KAAK,EAAE,gBAAgB,EAAE,CAAC;IAC7D,CAAC;IAED,IAAI,sBAAsB,EAAE,EAAE,CAAC;QAC7B,MAAM,KAAK,GAAG,kBAAkB,CAAC,UAAU,CAAC,CAAC;QAC7C,IAAI,CAAC,mBAAmB,CAAC,KAAK,EAAE,KAAK,IAAI,EAAE,CAAC,EAAE,CAAC;YAC7C,OAAO;gBACL,EAAE,EAAE,KAAK;gBACT,MAAM,EAAE,GAAG;gBACX,KAAK,EAAE,oCAAoC;aAC5C,CAAC;QACJ,CAAC;IACH,CAAC;SAAM,IAAI,sBAAsB,EAAE,EAAE,CAAC;QACpC,OAAO;YACL,EAAE,EAAE,KAAK;YACT,MAAM,EAAE,GAAG;YACX,KAAK,EACH,qFAAqF;SACxF,CAAC;IACJ,CAAC;IAED,qEAAqE;IACrE,wEAAwE;IACxE,IAAI,CAAC,MAAM,IAAI,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ,EAAE,CAAC;QAChD,MAAM,CAAC,+BAA+B,CAAC,GAAG,EAAE,KAAK,EAAE,CAAC;IACtD,CAAC;IACD,OAAO,EAAE,EAAE,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE,CAAC;AAC3C,CAAC","sourcesContent":["/**\n * Durable background agent-chat runs (Netlify background functions).\n *\n * Off by default. When enabled, a long in-app agent-chat turn is dispatched\n * into a Netlify *background* function (15-min budget) instead of completing\n * synchronously under the ~40s soft-timeout. The foreground POST claims the\n * run slot, inserts the run row, fires an HMAC-signed self-dispatch to\n * `AGENT_CHAT_PROCESS_RUN_PATH`, and returns the existing SSE subscription so\n * the client streams the same events (via the cross-isolate SQL-poll path)\n * with no client change.\n *\n * This module owns ONLY the gating decision + shared constants so both the\n * HTTP handler (`production-agent.ts`) and the processor route\n * (`agent-chat-plugin.ts`) agree on when the path is active without a circular\n * import. The actual run machinery is reused verbatim from run-manager /\n * run-store / self-dispatch / internal-token.\n *\n * GUARDRAIL: when `isAgentChatDurableBackgroundEnabled()` returns false, the\n * agent-chat handler must behave byte-for-byte like the current synchronous\n * path. The gate is true only when ALL of these hold:\n *   1. `AGENT_CHAT_DURABLE_BACKGROUND` env is not explicitly disabled. It is\n *      DEFAULT-ON: unset/empty/unknown counts as enabled; set it to a falsy\n *      value (`false`/`0`/`no`/`off`) to opt a specific app back out.\n *   2. The runtime is hosted/serverless (local dev keeps the inline path so SSE\n *      stays a single live stream and no second function is needed).\n *   3. `A2A_SECRET` is configured (the HMAC handoff is required to authenticate\n *      the background dispatch; without it the dispatch can't be trusted).\n *\n * Default-on is safe because a *dispatch failure degrades to an inline run*: if\n * the self-dispatch self-POST can't be delivered (fast connection error or\n * fast non-2xx), the foreground handler runs the turn synchronously instead of\n * erroring (see `production-agent.ts` — the inline fallback claims the run row\n * atomically so a delayed delivery can never double-execute). So an app where\n * durable dispatch happens to fail still gets a working chat, just without the\n * 15-min budget.\n */\nimport {\n  hasConfiguredA2ASecret,\n  isA2AProductionRuntime,\n} from \"../a2a/auth-policy.js\";\nimport {\n  extractBearerToken,\n  verifyInternalToken,\n} from \"../integrations/internal-token.js\";\n\n/**\n * Framework route the background function actually runs — sibling to\n * `AGENT_TEAM_PROCESS_RUN_PATH`. Reached *through* the Netlify background\n * function, so it inherits the 15-min budget.\n */\nexport const AGENT_CHAT_PROCESS_RUN_PATH =\n  \"/_agent-native/agent-chat/_process-run\";\n\n/**\n * Env flag for durable background runs. DEFAULT-ON: unset means enabled; an app\n * opts OUT with an explicit falsy value (`false`/`0`/`no`/`off`).\n */\nexport const AGENT_CHAT_DURABLE_BACKGROUND_ENV =\n  \"AGENT_CHAT_DURABLE_BACKGROUND\";\n\n/**\n * Body field the foreground handler injects when self-dispatching to the\n * background processor. Its presence is how the re-entered handler knows it is\n * the background worker (run inline with the background soft-timeout; do NOT\n * re-claim the slot or re-dispatch). Untrusted on its own — the route also\n * verifies the HMAC token before invoking the handler.\n */\nexport const AGENT_CHAT_BACKGROUND_RUN_FIELD = \"__backgroundRun\";\n\n/**\n * Mirror of run-manager's private `isHostedRuntime`. Kept in sync deliberately:\n * the durable-background gate must agree with the soft-timeout regime about\n * what \"hosted\" means.\n */\nexport function isHostedRuntimeForDurableBackground(): boolean {\n  if (\n    process.env.NETLIFY &&\n    process.env.NETLIFY !== \"false\" &&\n    process.env.NETLIFY_LOCAL !== \"true\"\n  ) {\n    return true;\n  }\n  if (\n    process.env.AWS_LAMBDA_FUNCTION_NAME &&\n    process.env.NETLIFY_LOCAL !== \"true\"\n  ) {\n    return true;\n  }\n  return Boolean(\n    process.env.CF_PAGES ||\n    process.env.VERCEL ||\n    process.env.VERCEL_ENV ||\n    process.env.RENDER ||\n    process.env.FLY_APP_NAME ||\n    process.env.K_SERVICE,\n  );\n}\n\n/**\n * True when THIS process is actually executing inside a Netlify *background*\n * function (the long, 15-min-budget async function whose deployed name ends in\n * `-background`). Netlify runs functions on AWS Lambda and sets\n * `AWS_LAMBDA_FUNCTION_NAME` to the function's name, so a `-background` suffix is\n * the runtime proof that the ~60s synchronous wall does NOT apply here.\n *\n * This is the SAFETY GUARD for the soft-timeout regime. The `_process-run`\n * self-dispatch worker (`isBackgroundWorker`) is NOT enough on its own: if the\n * `-background` function was never emitted (deploy gate off, or Netlify routed\n * the path to the synchronous function), the self-POST lands on the regular\n * ~60s `server` function. A worker there MUST use the 40s soft-timeout and\n * checkpoint before the 60s wall — using the ~13min budget would overshoot the\n * hard wall and get killed at 60s, then re-dispatch/resume in a wasteful loop.\n * So the 13-min budget is taken ONLY when this returns true.\n *\n * Falls back to the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy)\n * for hosts that don't expose a `-background`-suffixed function name but where\n * the operator has confirmed a long async budget. Off by default.\n */\nexport function isInBackgroundFunctionRuntime(): boolean {\n  const lambdaName = process.env.AWS_LAMBDA_FUNCTION_NAME;\n  if (\n    typeof lambdaName === \"string\" &&\n    lambdaName.toLowerCase().endsWith(\"-background\")\n  ) {\n    return true;\n  }\n  const forced = process.env.AGENT_CHAT_FORCE_BACKGROUND_RUNTIME;\n  if (forced != null) {\n    const v = forced.trim().toLowerCase();\n    return v === \"1\" || v === \"true\" || v === \"yes\" || v === \"on\";\n  }\n  return false;\n}\n\nfunction isFlagEnabled(): boolean {\n  // Read the literal key (not `process.env[CONST]`) so guard:no-env-credentials\n  // can statically verify it against the allowlisted `AGENT_*` prefix. Keep this\n  // in sync with AGENT_CHAT_DURABLE_BACKGROUND_ENV.\n  //\n  // DEFAULT-ON: durable background runs are the desired behavior for every\n  // hosted app. So an unset/empty/unknown flag means ON; an app opts OUT only\n  // with an explicit falsy value. This still composes with the hosted +\n  // A2A_SECRET gates below, so non-hosted / unconfigured apps stay synchronous.\n  // Safety net: a failed dispatch degrades to a synchronous inline run (see\n  // production-agent.ts), so default-on cannot break chat even if the\n  // self-dispatch can't be delivered on a given app.\n  const raw = process.env.AGENT_CHAT_DURABLE_BACKGROUND;\n  if (raw == null) return true;\n  const normalized = raw.trim().toLowerCase();\n  return !(\n    normalized === \"0\" ||\n    normalized === \"false\" ||\n    normalized === \"no\" ||\n    normalized === \"off\"\n  );\n}\n\n/**\n * The single gate. True when the flag is not explicitly disabled (default-on)\n * AND the runtime is hosted AND A2A_SECRET is configured. False otherwise — and\n * false means the current synchronous behavior is used, unchanged. So a local /\n * non-hosted / unconfigured app stays synchronous even with the flag defaulting\n * on; durable only engages where the runtime actually supports it.\n */\nexport function isAgentChatDurableBackgroundEnabled(): boolean {\n  return (\n    isFlagEnabled() &&\n    isHostedRuntimeForDurableBackground() &&\n    hasConfiguredA2ASecret()\n  );\n}\n\n/** Decision returned by `prepareProcessRunRequest`. */\nexport type ProcessRunPreparation =\n  | {\n      ok: true;\n      /** The pre-claimed run id the background worker must reuse. */\n      runId: string;\n      /** Body to stash for the re-entered handler (marker guaranteed present). */\n      body: Record<string, unknown>;\n    }\n  | {\n      ok: false;\n      /** HTTP status the route should return. */\n      status: number;\n      /** Error payload. */\n      error: string;\n    };\n\n/**\n * Pure, transport-agnostic core of the `_process-run` route: validate the body,\n * authenticate the HMAC self-dispatch, and produce the body the re-entered\n * agent-chat handler should run as the background worker.\n *\n * Auth policy mirrors the agent-teams processor exactly:\n *   - `A2A_SECRET` set → require a valid `verifyInternalToken(runId, token)`.\n *   - no secret but a production runtime → refuse (503) — never run unsigned in\n *     prod.\n *   - no secret + non-prod (local dev) → allow unsigned; the SQL atomic claim\n *     in the worker still prevents double-processing.\n *\n * Extracted from the route handler so the auth + marker-prep decision is unit\n * testable without booting the whole Nitro plugin. The route only adds body\n * reading and the final handler invocation around this.\n */\nexport function prepareProcessRunRequest(\n  body: unknown,\n  authHeader: string | undefined,\n): ProcessRunPreparation {\n  if (!body || typeof body !== \"object\") {\n    return { ok: false, status: 400, error: \"Invalid request body\" };\n  }\n  const record = body as Record<string, unknown>;\n  const marker = record[AGENT_CHAT_BACKGROUND_RUN_FIELD] as\n    | { runId?: unknown }\n    | undefined;\n  const runId =\n    marker && typeof marker.runId === \"string\"\n      ? marker.runId\n      : typeof record.taskId === \"string\"\n        ? (record.taskId as string)\n        : \"\";\n  if (!runId) {\n    return { ok: false, status: 400, error: \"runId required\" };\n  }\n\n  if (hasConfiguredA2ASecret()) {\n    const token = extractBearerToken(authHeader);\n    if (!verifyInternalToken(runId, token ?? \"\")) {\n      return {\n        ok: false,\n        status: 401,\n        error: \"Invalid or expired processor token\",\n      };\n    }\n  } else if (isA2AProductionRuntime()) {\n    return {\n      ok: false,\n      status: 503,\n      error:\n        \"Agent chat background processor not configured — set A2A_SECRET on this deployment.\",\n    };\n  }\n\n  // Ensure the marker is present so the re-entered handler runs as the\n  // background worker (reuses runId/turnId, no re-claim, no re-dispatch).\n  if (!marker || typeof marker.runId !== \"string\") {\n    record[AGENT_CHAT_BACKGROUND_RUN_FIELD] = { runId };\n  }\n  return { ok: true, runId, body: record };\n}\n"]}
+{"version":3,"file":"durable-background.js","sourceRoot":"","sources":["../../src/agent/durable-background.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmCG;AACH,OAAO,EACL,sBAAsB,EACtB,sBAAsB,GACvB,MAAM,uBAAuB,CAAC;AAC/B,OAAO,EACL,kBAAkB,EAClB,mBAAmB,GACpB,MAAM,mCAAmC,CAAC;AAE3C;;;;GAIG;AACH,MAAM,CAAC,MAAM,2BAA2B,GACtC,wCAAwC,CAAC;AAE3C;;;GAGG;AACH,MAAM,CAAC,MAAM,iCAAiC,GAC5C,+BAA+B,CAAC;AAElC;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,+BAA+B,GAAG,iBAAiB,CAAC;AAEjE;;;;GAIG;AACH,MAAM,UAAU,mCAAmC;IACjD,IACE,OAAO,CAAC,GAAG,CAAC,OAAO;QACnB,OAAO,CAAC,GAAG,CAAC,OAAO,KAAK,OAAO;QAC/B,OAAO,CAAC,GAAG,CAAC,aAAa,KAAK,MAAM,EACpC,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IACD,IACE,OAAO,CAAC,GAAG,CAAC,wBAAwB;QACpC,OAAO,CAAC,GAAG,CAAC,aAAa,KAAK,MAAM,EACpC,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IACD,OAAO,OAAO,CACZ,OAAO,CAAC,GAAG,CAAC,QAAQ;QACpB,OAAO,CAAC,GAAG,CAAC,MAAM;QAClB,OAAO,CAAC,GAAG,CAAC,UAAU;QACtB,OAAO,CAAC,GAAG,CAAC,MAAM;QAClB,OAAO,CAAC,GAAG,CAAC,YAAY;QACxB,OAAO,CAAC,GAAG,CAAC,SAAS,CACtB,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,UAAU,6BAA6B;IAC3C,8EAA8E;IAC9E,2DAA2D;IAC3D,IACG,UAAsC;SACpC,mCAAmC,KAAK,IAAI,EAC/C,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IACD,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,wBAAwB,CAAC;IACxD,IACE,OAAO,UAAU,KAAK,QAAQ;QAC9B,UAAU,CAAC,WAAW,EAAE,CAAC,QAAQ,CAAC,aAAa,CAAC,EAChD,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IACD,MAAM,MAAM,GAAG,OAAO,CAAC,GAAG,CAAC,mCAAmC,CAAC;IAC/D,IAAI,MAAM,IAAI,IAAI,EAAE,CAAC;QACnB,MAAM,CAAC,GAAG,MAAM,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;QACtC,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC,KAAK,MAAM,IAAI,CAAC,KAAK,KAAK,IAAI,CAAC,KAAK,IAAI,CAAC;IAChE,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED,SAAS,aAAa;IACpB,8EAA8E;IAC9E,+EAA+E;IAC/E,kDAAkD;IAClD,EAAE;IACF,yEAAyE;IACzE,4EAA4E;IAC5E,sEAAsE;IACtE,8EAA8E;IAC9E,0EAA0E;IAC1E,oEAAoE;IACpE,mDAAmD;IACnD,MAAM,GAAG,GAAG,OAAO,CAAC,GAAG,CAAC,6BAA6B,CAAC;IACtD,IAAI,GAAG,IAAI,IAAI;QAAE,OAAO,IAAI,CAAC;IAC7B,MAAM,UAAU,GAAG,GAAG,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;IAC5C,OAAO,CAAC,CACN,UAAU,KAAK,GAAG;QAClB,UAAU,KAAK,OAAO;QACtB,UAAU,KAAK,IAAI;QACnB,UAAU,KAAK,KAAK,CACrB,CAAC;AACJ,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,mCAAmC;IACjD,OAAO,CACL,aAAa,EAAE;QACf,mCAAmC,EAAE;QACrC,sBAAsB,EAAE,CACzB,CAAC;AACJ,CAAC;AAmBD;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,wBAAwB,CACtC,IAAa,EACb,UAA8B;IAE9B,IAAI,CAAC,IAAI,IAAI,OAAO,IAAI,KAAK,QAAQ,EAAE,CAAC;QACtC,OAAO,EAAE,EAAE,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,EAAE,KAAK,EAAE,sBAAsB,EAAE,CAAC;IACnE,CAAC;IACD,MAAM,MAAM,GAAG,IAA+B,CAAC;IAC/C,MAAM,MAAM,GAAG,MAAM,CAAC,+BAA+B,CAExC,CAAC;IACd,MAAM,KAAK,GACT,MAAM,IAAI,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ;QACxC,CAAC,CAAC,MAAM,CAAC,KAAK;QACd,CAAC,CAAC,OAAO,MAAM,CAAC,MAAM,KAAK,QAAQ;YACjC,CAAC,CAAE,MAAM,CAAC,MAAiB;YAC3B,CAAC,CAAC,EAAE,CAAC;IACX,IAAI,CAAC,KAAK,EAAE,CAAC;QACX,OAAO,EAAE,EAAE,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,EAAE,KAAK,EAAE,gBAAgB,EAAE,CAAC;IAC7D,CAAC;IAED,IAAI,sBAAsB,EAAE,EAAE,CAAC;QAC7B,MAAM,KAAK,GAAG,kBAAkB,CAAC,UAAU,CAAC,CAAC;QAC7C,IAAI,CAAC,mBAAmB,CAAC,KAAK,EAAE,KAAK,IAAI,EAAE,CAAC,EAAE,CAAC;YAC7C,OAAO;gBACL,EAAE,EAAE,KAAK;gBACT,MAAM,EAAE,GAAG;gBACX,KAAK,EAAE,oCAAoC;aAC5C,CAAC;QACJ,CAAC;IACH,CAAC;SAAM,IAAI,sBAAsB,EAAE,EAAE,CAAC;QACpC,OAAO;YACL,EAAE,EAAE,KAAK;YACT,MAAM,EAAE,GAAG;YACX,KAAK,EACH,qFAAqF;SACxF,CAAC;IACJ,CAAC;IAED,qEAAqE;IACrE,wEAAwE;IACxE,IAAI,CAAC,MAAM,IAAI,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ,EAAE,CAAC;QAChD,MAAM,CAAC,+BAA+B,CAAC,GAAG,EAAE,KAAK,EAAE,CAAC;IACtD,CAAC;IACD,OAAO,EAAE,EAAE,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE,CAAC;AAC3C,CAAC","sourcesContent":["/**\n * Durable background agent-chat runs (Netlify background functions).\n *\n * Off by default. When enabled, a long in-app agent-chat turn is dispatched\n * into a Netlify *background* function (15-min budget) instead of completing\n * synchronously under the ~40s soft-timeout. The foreground POST claims the\n * run slot, inserts the run row, fires an HMAC-signed self-dispatch to\n * `AGENT_CHAT_PROCESS_RUN_PATH`, and returns the existing SSE subscription so\n * the client streams the same events (via the cross-isolate SQL-poll path)\n * with no client change.\n *\n * This module owns ONLY the gating decision + shared constants so both the\n * HTTP handler (`production-agent.ts`) and the processor route\n * (`agent-chat-plugin.ts`) agree on when the path is active without a circular\n * import. The actual run machinery is reused verbatim from run-manager /\n * run-store / self-dispatch / internal-token.\n *\n * GUARDRAIL: when `isAgentChatDurableBackgroundEnabled()` returns false, the\n * agent-chat handler must behave byte-for-byte like the current synchronous\n * path. The gate is true only when ALL of these hold:\n *   1. `AGENT_CHAT_DURABLE_BACKGROUND` env is not explicitly disabled. It is\n *      DEFAULT-ON: unset/empty/unknown counts as enabled; set it to a falsy\n *      value (`false`/`0`/`no`/`off`) to opt a specific app back out.\n *   2. The runtime is hosted/serverless (local dev keeps the inline path so SSE\n *      stays a single live stream and no second function is needed).\n *   3. `A2A_SECRET` is configured (the HMAC handoff is required to authenticate\n *      the background dispatch; without it the dispatch can't be trusted).\n *\n * Default-on is safe because a *dispatch failure degrades to an inline run*: if\n * the self-dispatch self-POST can't be delivered (fast connection error or\n * fast non-2xx), the foreground handler runs the turn synchronously instead of\n * erroring (see `production-agent.ts` — the inline fallback claims the run row\n * atomically so a delayed delivery can never double-execute). So an app where\n * durable dispatch happens to fail still gets a working chat, just without the\n * 15-min budget.\n */\nimport {\n  hasConfiguredA2ASecret,\n  isA2AProductionRuntime,\n} from \"../a2a/auth-policy.js\";\nimport {\n  extractBearerToken,\n  verifyInternalToken,\n} from \"../integrations/internal-token.js\";\n\n/**\n * Framework route the background function actually runs — sibling to\n * `AGENT_TEAM_PROCESS_RUN_PATH`. Reached *through* the Netlify background\n * function, so it inherits the 15-min budget.\n */\nexport const AGENT_CHAT_PROCESS_RUN_PATH =\n  \"/_agent-native/agent-chat/_process-run\";\n\n/**\n * Env flag for durable background runs. DEFAULT-ON: unset means enabled; an app\n * opts OUT with an explicit falsy value (`false`/`0`/`no`/`off`).\n */\nexport const AGENT_CHAT_DURABLE_BACKGROUND_ENV =\n  \"AGENT_CHAT_DURABLE_BACKGROUND\";\n\n/**\n * Body field the foreground handler injects when self-dispatching to the\n * background processor. Its presence is how the re-entered handler knows it is\n * the background worker (run inline with the background soft-timeout; do NOT\n * re-claim the slot or re-dispatch). Untrusted on its own — the route also\n * verifies the HMAC token before invoking the handler.\n */\nexport const AGENT_CHAT_BACKGROUND_RUN_FIELD = \"__backgroundRun\";\n\n/**\n * Mirror of run-manager's private `isHostedRuntime`. Kept in sync deliberately:\n * the durable-background gate must agree with the soft-timeout regime about\n * what \"hosted\" means.\n */\nexport function isHostedRuntimeForDurableBackground(): boolean {\n  if (\n    process.env.NETLIFY &&\n    process.env.NETLIFY !== \"false\" &&\n    process.env.NETLIFY_LOCAL !== \"true\"\n  ) {\n    return true;\n  }\n  if (\n    process.env.AWS_LAMBDA_FUNCTION_NAME &&\n    process.env.NETLIFY_LOCAL !== \"true\"\n  ) {\n    return true;\n  }\n  return Boolean(\n    process.env.CF_PAGES ||\n    process.env.VERCEL ||\n    process.env.VERCEL_ENV ||\n    process.env.RENDER ||\n    process.env.FLY_APP_NAME ||\n    process.env.K_SERVICE,\n  );\n}\n\n/**\n * True when THIS process is actually executing inside a Netlify *background*\n * function (the long, 15-min-budget async function whose deployed name ends in\n * `-background`). Netlify runs functions on AWS Lambda and sets\n * `AWS_LAMBDA_FUNCTION_NAME` to the function's name, so a `-background` suffix is\n * the runtime proof that the ~60s synchronous wall does NOT apply here.\n *\n * This is the SAFETY GUARD for the soft-timeout regime. The `_process-run`\n * self-dispatch worker (`isBackgroundWorker`) is NOT enough on its own: if the\n * `-background` function was never emitted (deploy gate off, or Netlify routed\n * the path to the synchronous function), the self-POST lands on the regular\n * ~60s `server` function. A worker there MUST use the 40s soft-timeout and\n * checkpoint before the 60s wall — using the ~13min budget would overshoot the\n * hard wall and get killed at 60s, then re-dispatch/resume in a wasteful loop.\n * So the 13-min budget is taken ONLY when this returns true.\n *\n * The PRIMARY signal is a `globalThis` marker the emitted background function's\n * entry sets at cold start — the deployed Lambda name is not guaranteed to end\n * in `-background` on Netlify, so the entry marks its own runtime. A `globalThis`\n * flag (not `process.env`) keeps the no-env-mutation guard satisfied and carries\n * no cross-request state (set once per isolate). The `AWS_LAMBDA_FUNCTION_NAME`\n * suffix and the explicit `AGENT_CHAT_FORCE_BACKGROUND_RUNTIME` env (truthy) are\n * additional signals — the latter an operator escape hatch. Off by default.\n */\nexport function isInBackgroundFunctionRuntime(): boolean {\n  // Set by the emitted `-background` function entry at cold start (the primary,\n  // most reliable signal — see the emit in deploy/build.ts).\n  if (\n    (globalThis as Record<string, unknown>)\n      .__AGENT_NATIVE_BACKGROUND_RUNTIME__ === true\n  ) {\n    return true;\n  }\n  const lambdaName = process.env.AWS_LAMBDA_FUNCTION_NAME;\n  if (\n    typeof lambdaName === \"string\" &&\n    lambdaName.toLowerCase().endsWith(\"-background\")\n  ) {\n    return true;\n  }\n  const forced = process.env.AGENT_CHAT_FORCE_BACKGROUND_RUNTIME;\n  if (forced != null) {\n    const v = forced.trim().toLowerCase();\n    return v === \"1\" || v === \"true\" || v === \"yes\" || v === \"on\";\n  }\n  return false;\n}\n\nfunction isFlagEnabled(): boolean {\n  // Read the literal key (not `process.env[CONST]`) so guard:no-env-credentials\n  // can statically verify it against the allowlisted `AGENT_*` prefix. Keep this\n  // in sync with AGENT_CHAT_DURABLE_BACKGROUND_ENV.\n  //\n  // DEFAULT-ON: durable background runs are the desired behavior for every\n  // hosted app. So an unset/empty/unknown flag means ON; an app opts OUT only\n  // with an explicit falsy value. This still composes with the hosted +\n  // A2A_SECRET gates below, so non-hosted / unconfigured apps stay synchronous.\n  // Safety net: a failed dispatch degrades to a synchronous inline run (see\n  // production-agent.ts), so default-on cannot break chat even if the\n  // self-dispatch can't be delivered on a given app.\n  const raw = process.env.AGENT_CHAT_DURABLE_BACKGROUND;\n  if (raw == null) return true;\n  const normalized = raw.trim().toLowerCase();\n  return !(\n    normalized === \"0\" ||\n    normalized === \"false\" ||\n    normalized === \"no\" ||\n    normalized === \"off\"\n  );\n}\n\n/**\n * The single gate. True when the flag is not explicitly disabled (default-on)\n * AND the runtime is hosted AND A2A_SECRET is configured. False otherwise — and\n * false means the current synchronous behavior is used, unchanged. So a local /\n * non-hosted / unconfigured app stays synchronous even with the flag defaulting\n * on; durable only engages where the runtime actually supports it.\n */\nexport function isAgentChatDurableBackgroundEnabled(): boolean {\n  return (\n    isFlagEnabled() &&\n    isHostedRuntimeForDurableBackground() &&\n    hasConfiguredA2ASecret()\n  );\n}\n\n/** Decision returned by `prepareProcessRunRequest`. */\nexport type ProcessRunPreparation =\n  | {\n      ok: true;\n      /** The pre-claimed run id the background worker must reuse. */\n      runId: string;\n      /** Body to stash for the re-entered handler (marker guaranteed present). */\n      body: Record<string, unknown>;\n    }\n  | {\n      ok: false;\n      /** HTTP status the route should return. */\n      status: number;\n      /** Error payload. */\n      error: string;\n    };\n\n/**\n * Pure, transport-agnostic core of the `_process-run` route: validate the body,\n * authenticate the HMAC self-dispatch, and produce the body the re-entered\n * agent-chat handler should run as the background worker.\n *\n * Auth policy mirrors the agent-teams processor exactly:\n *   - `A2A_SECRET` set → require a valid `verifyInternalToken(runId, token)`.\n *   - no secret but a production runtime → refuse (503) — never run unsigned in\n *     prod.\n *   - no secret + non-prod (local dev) → allow unsigned; the SQL atomic claim\n *     in the worker still prevents double-processing.\n *\n * Extracted from the route handler so the auth + marker-prep decision is unit\n * testable without booting the whole Nitro plugin. The route only adds body\n * reading and the final handler invocation around this.\n */\nexport function prepareProcessRunRequest(\n  body: unknown,\n  authHeader: string | undefined,\n): ProcessRunPreparation {\n  if (!body || typeof body !== \"object\") {\n    return { ok: false, status: 400, error: \"Invalid request body\" };\n  }\n  const record = body as Record<string, unknown>;\n  const marker = record[AGENT_CHAT_BACKGROUND_RUN_FIELD] as\n    | { runId?: unknown }\n    | undefined;\n  const runId =\n    marker && typeof marker.runId === \"string\"\n      ? marker.runId\n      : typeof record.taskId === \"string\"\n        ? (record.taskId as string)\n        : \"\";\n  if (!runId) {\n    return { ok: false, status: 400, error: \"runId required\" };\n  }\n\n  if (hasConfiguredA2ASecret()) {\n    const token = extractBearerToken(authHeader);\n    if (!verifyInternalToken(runId, token ?? \"\")) {\n      return {\n        ok: false,\n        status: 401,\n        error: \"Invalid or expired processor token\",\n      };\n    }\n  } else if (isA2AProductionRuntime()) {\n    return {\n      ok: false,\n      status: 503,\n      error:\n        \"Agent chat background processor not configured — set A2A_SECRET on this deployment.\",\n    };\n  }\n\n  // Ensure the marker is present so the re-entered handler runs as the\n  // background worker (reuses runId/turnId, no re-claim, no re-dispatch).\n  if (!marker || typeof marker.runId !== \"string\") {\n    record[AGENT_CHAT_BACKGROUND_RUN_FIELD] = { runId };\n  }\n  return { ok: true, runId, body: record };\n}\n"]}