@agent-native/core 0.92.7 → 0.92.9

package/corpus/core/docs/content/locales/zh-CN/pr-visual-recap.mdx

@@ -138,11 +138,11 @@ npx @agent-native/core@latest recap doctor
 
 除了后端之外，两个存储库变量还可以调整代理的运行方式：
 
-- **`VISUAL_RECAP_MODEL`** 固定传递给 CLI (`--model`) 的模型 — 例如 `gpt-5.5` 用于 Codex，或 Claude 模型 ID。保留其未设置以使用 CLI 自己的默认模型。
+- **`VISUAL_RECAP_MODEL`** 固定传递给 CLI (`--model`) 的模型 — 例如 `gpt-5.6-sol` 用于 Codex，或 Claude 模型 ID。保留其未设置以使用 CLI 自己的默认模型。
 - **`VISUAL_RECAP_REASONING`** 设置推理深度：`none`、`minimal`、`low`、`medium`、`high` 或 `xhigh`。适用于Codex后端； Claude 的推理是模型驱动的，因此该变量被忽略。
 - **`VISUAL_RECAP_SKILL_SOURCE`** 控制提示新鲜度：`auto`/unset 使用最新的捆绑技能指南，而 `repo` 固定到已提交的存储库本地 `visual-recap` 技能文件夹。
 
-例如，要在 Codex 和 GPT-5.5 上以高推理运行回顾，请设置存储库变量 `VISUAL_RECAP_AGENT=codex`、`VISUAL_RECAP_MODEL=gpt-5.5` 和 `VISUAL_RECAP_REASONING=high`。
+例如，要在 Codex 和 GPT-5.6 Sol 上以高推理运行回顾，请设置存储库变量 `VISUAL_RECAP_AGENT=codex`、`VISUAL_RECAP_MODEL=gpt-5.6-sol` 和 `VISUAL_RECAP_REASONING=high`。
 
 ## 秘密和变量
 
@@ -191,7 +191,7 @@ npx @agent-native/core@latest recap setup
 | ------------------------ | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | `OPENAI_API_KEY`         | —                               | 秘密。与 `VISUAL_RECAP_AGENT=codex` 一起设置以使用 Codex 运行回顾。                                                          |
 | `VISUAL_RECAP_AGENT`     | `claude`                        | 变量。选择编码代理后端（`claude` 或 `codex`）。                                                                              |
-| `VISUAL_RECAP_MODEL`     | 每个CLI的默认值                 | 变量。固定模型 - 例如`gpt-5.5` 表示 Codex，或 Claude 型号 ID。取消设置使用 CLI 自己的默认值。                                |
+| `VISUAL_RECAP_MODEL`     | 每个CLI的默认值                 | 变量。固定模型 - 例如`gpt-5.6-sol` 表示 Codex，或 Claude 型号 ID。取消设置使用 CLI 自己的默认值。                            |
 | `VISUAL_RECAP_REASONING` | 每个模型的默认值                | 变量。推理深度：`none`、`minimal`、`low`、`medium`、`high` 或 `xhigh`。适用于Codex后端。                                     |
 | `RECAP_CLI_VERSION`      | `latest`                        | 变量。固定工作流程安装的 `@agent-native/core` CLI 版本 - 例如`1.5.0`。参见[Version pinning](#version-pinning-copy-variant)。 |
 | `PLAN_RECAP_APP_URL`     | `https://plan.agent-native.com` | 秘密。仅当在不同来源自行托管计划应用时。                                                                                     |

package/corpus/core/docs/content/locales/zh-CN/pure-agent-apps.mdx

@@ -66,6 +66,10 @@ Automation-first app 是无浏览器的 Agent-Native app，用于 scheduled jobs
 
 → [**Agent Surfaces — Headless agent**](/docs/agent-surfaces#headless)
 
+## 稍后添加聊天 {#add-chat-later}
+
+`--headless` 只选择初始 scaffold；没有可将现有仅 actions 项目原地转换为聊天应用的 `agent-native` 命令。当用户需要浏览器对话时，请将 [Chat 模板](/docs/template-chat) 用作迁移参考：保留 actions、SQL 数据、instructions 和 skills，并添加浏览器 shell、server plugins、`<AgentChatSurface>` 以及加载现有 actions 的 chat plugin。验证 `pnpm typecheck`，并完成一次调用现有 action 的聊天。`agent-native add` 用于 integration blueprints，不用于此转换。
+
 ## 下一步是什么
 
 - [**Agent Surfaces — Headless**](/docs/agent-surfaces#headless) — 完整的无头决策指南和 API

package/corpus/core/docs/content/locales/zh-TW/a2a-protocol.mdx

@@ -436,6 +436,18 @@ const client = new A2AClient(url, process.env.A2A_API_KEY);
 
 JWT 驗證（`server.ts` 中的 `verifyA2AToken`）接受使用全域 `A2A_SECRET` 或透過權杖的 `org_domain` 聲明從 SQL 尋找的組織範圍秘密簽名的權杖，並在存在時強制執行權杖自己的 `aud`/`iss` 聲明。
 
+### 組織密鑰同步 {#organization-secret-sync}
+
+**組織 → 跨應用程式驗證**設定會管理組織範圍的密鑰，用來驗證同一組織中個別部署的應用程式之間的委派。它不是使用者登入或 Cross-App SSO 設定。此密鑰補充部署的 `A2A_SECRET`：具有 `org_domain` 宣告的 A2A JWT 可使用相符組織的密鑰驗證。
+
+組織擁有者應為每個參與的應用程式提供相同的允許電子郵件網域與相同的組織範圍密鑰：
+
+1. 在第一個應用程式中，從**組織 → 跨應用程式驗證**產生或顯示密鑰。
+2. 在每個其他應用程式中，選擇**從另一個應用程式貼上密鑰**並貼上該值。首次連線必須進行這個手動步驟：尚未擁有該密鑰的應用程式無法驗證遠端同步要求。
+3. 應用程式共用此密鑰後，使用**同步到應用程式**將後續更新推送至已連線且已探索到的應用程式。結果會回報無法更新的應用程式。
+
+當您**重新產生**密鑰時，設定 UI 會立即同步它，並使用先前的密鑰簽署更新，讓已連線的應用程式可以驗證變更。如果某個應用程式錯過該同步，請在其中手動貼上新密鑰，然後再次同步。請像對待其他憑證一樣對待此密鑰：不要將它放入用戶端程式碼、日誌或第三方用戶端設定中。
+
 ## 繼續 {#continuations}
 
 當代理呼叫未立即返回的遠端 A2A 對等點時，框架會輪詢 `tasks/get` 直到工作解決。這是透過 `A2AClient.sendAndWait` 連線的，這是 `callAgent()` 幫助程式使用的預設模式。

package/corpus/core/docs/content/locales/zh-TW/pr-visual-recap.mdx

@@ -138,11 +138,11 @@ npx @agent-native/core@latest recap doctor
 
 除了後端之外，兩個儲存庫變數還可以調整代理的執行方式：
 
-- **`VISUAL_RECAP_MODEL`** 固定傳遞給 CLI (`--model`) 的模型 — 例如 `gpt-5.5` 用於 Codex，或 Claude 模型 ID。保留其未設定以使用 CLI 自己的預設模型。
+- **`VISUAL_RECAP_MODEL`** 固定傳遞給 CLI (`--model`) 的模型 — 例如 `gpt-5.6-sol` 用於 Codex，或 Claude 模型 ID。保留其未設定以使用 CLI 自己的預設模型。
 - **`VISUAL_RECAP_REASONING`** 設定推理深度：`none`、`minimal`、`low`、`medium`、`high` 或 `xhigh`。適用於Codex後端； Claude 的推理是模型驅動的，因此該變數被忽略。
 - **`VISUAL_RECAP_SKILL_SOURCE`** 控制提示新鮮度：`auto`/unset 使用最新的捆綁技能指南，而 `repo` 固定到已提交的儲存庫本機 `visual-recap` 技能資料夾。
 
-例如，要在 Codex 和 GPT-5.5 上以高推理執行回顧，請設定儲存庫變數 `VISUAL_RECAP_AGENT=codex`、`VISUAL_RECAP_MODEL=gpt-5.5` 和 `VISUAL_RECAP_REASONING=high`。
+例如，要在 Codex 和 GPT-5.6 Sol 上以高推理執行回顧，請設定儲存庫變數 `VISUAL_RECAP_AGENT=codex`、`VISUAL_RECAP_MODEL=gpt-5.6-sol` 和 `VISUAL_RECAP_REASONING=high`。
 
 ## 秘密和變數
 
@@ -191,7 +191,7 @@ npx @agent-native/core@latest recap setup
 | ------------------------ | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | `OPENAI_API_KEY`         | —                               | 秘密。與 `VISUAL_RECAP_AGENT=codex` 一起設定以使用 Codex 執行回顧。                                                          |
 | `VISUAL_RECAP_AGENT`     | `claude`                        | 變數。選取編碼代理後端（`claude` 或 `codex`）。                                                                              |
-| `VISUAL_RECAP_MODEL`     | 每個 CLI 的預設值               | 變數。固定模型 - 例如`gpt-5.5` 表示 Codex，或 Claude 型號 ID。取消設定使用 CLI 自己的預設值。                                |
+| `VISUAL_RECAP_MODEL`     | 每個 CLI 的預設值               | 變數。固定模型 - 例如`gpt-5.6-sol` 表示 Codex，或 Claude 型號 ID。取消設定使用 CLI 自己的預設值。                            |
 | `VISUAL_RECAP_REASONING` | 每個模型的預設值                | 變數。推理深度：`none`、`minimal`、`low`、`medium`、`high` 或 `xhigh`。適用於Codex後端。                                     |
 | `RECAP_CLI_VERSION`      | `latest`                        | 變數。固定工作流程安裝的 `@agent-native/core` CLI 版本 - 例如`1.5.0`。參見[Version pinning](#version-pinning-copy-variant)。 |
 | `PLAN_RECAP_APP_URL`     | `https://plan.agent-native.com` | 秘密。僅當在不同來源自行託管計畫應用時。                                                                                     |

package/corpus/core/docs/content/locales/zh-TW/pure-agent-apps.mdx

@@ -66,6 +66,10 @@ Automation-first app 是無瀏覽器的 Agent-Native app，用於 scheduled jobs
 
 → [**Agent Surfaces — Headless agent**](/docs/agent-surfaces#headless)
 
+## 稍後新增聊天 {#add-chat-later}
+
+`--headless` 只會選擇初始 scaffold；沒有可將現有僅 actions 專案原地轉換為聊天應用程式的 `agent-native` 命令。當使用者需要瀏覽器對話時，請將 [Chat 範本](/docs/template-chat) 作為遷移參考：保留 actions、SQL 資料、instructions 和 skills，並新增瀏覽器 shell、server plugins、`<AgentChatSurface>` 與載入現有 actions 的 chat plugin。請驗證 `pnpm typecheck`，並完成一次呼叫現有 action 的聊天。`agent-native add` 用於 integration blueprints，不用於此轉換。
+
 ## 下一步是什麼
 
 - [**Agent Surfaces — Headless**](/docs/agent-surfaces#headless) — 完整的無頭決策指南和 API

package/corpus/core/docs/content/pr-visual-recap.mdx

@@ -138,11 +138,11 @@ If the variable is unset, the action uses `claude`.
 
 Beyond the backend, two repository variables tune _how_ the agent runs:
 
-- **`VISUAL_RECAP_MODEL`** pins the model passed to the CLI (`--model`) — for example `gpt-5.5` for Codex, or a Claude model id. Leave it unset to use the CLI's own default model.
+- **`VISUAL_RECAP_MODEL`** pins the model passed to the CLI (`--model`) — for example `gpt-5.6-sol` for Codex, or a Claude model id. Leave it unset to use the CLI's own default model.
 - **`VISUAL_RECAP_REASONING`** sets the reasoning depth: `none`, `minimal`, `low`, `medium`, `high`, or `xhigh`. It applies to the Codex backend; Claude's reasoning is model-driven, so this variable is ignored there.
 - **`VISUAL_RECAP_SKILL_SOURCE`** controls prompt freshness: `auto`/unset uses the latest bundled skill guidance, while `repo` pins to the committed repo-local `visual-recap` skill folder.
 
-For example, to run the recap on Codex with GPT-5.5 at high reasoning, set the repository variables `VISUAL_RECAP_AGENT=codex`, `VISUAL_RECAP_MODEL=gpt-5.5`, and `VISUAL_RECAP_REASONING=high`.
+For example, to run the recap on Codex with GPT-5.6 Sol at high reasoning, set the repository variables `VISUAL_RECAP_AGENT=codex`, `VISUAL_RECAP_MODEL=gpt-5.6-sol`, and `VISUAL_RECAP_REASONING=high`.
 
 ## Secrets and variables
 
@@ -191,7 +191,7 @@ real token.
 | ------------------------ | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
 | `OPENAI_API_KEY`         | —                               | Secret. Set together with `VISUAL_RECAP_AGENT=codex` to run the recap with Codex instead.                                                       |
 | `VISUAL_RECAP_AGENT`     | `claude`                        | Variable. Selects the coding-agent backend (`claude` or `codex`).                                                                               |
-| `VISUAL_RECAP_MODEL`     | each CLI's default              | Variable. Pins the model — e.g. `gpt-5.5` for Codex, or a Claude model id. Unset uses the CLI's own default.                                    |
+| `VISUAL_RECAP_MODEL`     | each CLI's default              | Variable. Pins the model — e.g. `gpt-5.6-sol` for Codex, or a Claude model id. Unset uses the CLI's own default.                                |
 | `VISUAL_RECAP_REASONING` | each model's default            | Variable. Reasoning depth: `none`, `minimal`, `low`, `medium`, `high`, or `xhigh`. Applies to the Codex backend.                                |
 | `RECAP_CLI_VERSION`      | `latest`                        | Variable. Pins the `@agent-native/core` CLI version the workflow installs — e.g. `1.5.0`. See [Version pinning](#version-pinning-copy-variant). |
 | `PLAN_RECAP_APP_URL`     | `https://plan.agent-native.com` | Secret. Only when self-hosting the Plans app at a different origin.                                                                             |

package/corpus/core/docs/content/pure-agent-apps.mdx

@@ -91,6 +91,28 @@ The `--headless` flag only chooses the initial scaffold. It does not choose a
 different architecture. You can later move the same `actions/`, instructions,
 skills, and SQL state into a chat app or full application surface.
 
+## Add chat later {#add-chat-later}
+
+`--headless` is not a permanent runtime mode, and there is no `agent-native`
+command that converts an existing action-only project into a chat app in place.
+When people need a browser conversation surface, use the [Chat template](/docs/template-chat)
+as the migration reference and keep the durable action and database contract:
+
+1. Scaffold a temporary Chat app with the framework version you are migrating
+   to: `npx @agent-native/core@latest create my-chat-reference --template chat`.
+2. Bring its browser shell, server plugins, and UI dependencies into the
+   existing project. In particular, add the full-page `<AgentChatSurface>` and
+   an `agent-chat` plugin that loads the existing action registry.
+3. Keep your action names, Zod schemas, SQL data, instructions, and skills.
+   Chat calls those same actions; it does not replace them.
+4. Verify both surfaces: run `pnpm typecheck`, start the browser app with
+   `pnpm dev`, then complete one chat turn that calls an existing action.
+
+Use `agent-native add` for integration blueprints, not for this conversion.
+Choose chat when people need conversational steering, approvals, or durable
+thread history; add app pages when they need to browse, compare, edit, or share
+persistent objects.
+
 ## What to add next {#whats-next}
 
 - [**Getting Started**](/docs/getting-started) — the chat-first tutorial from action to inline result to durable page

package/corpus/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.92.7",
+  "version": "0.92.9",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {

package/corpus/core/src/agent/engine/builtin.ts

@@ -96,7 +96,7 @@ export function registerBuiltinEngines(): void {
       "Claude models through the Vercel AI SDK. Supports thinking and caching via AI SDK providerOptions.",
     openai: "OpenAI GPT models via the Vercel AI SDK. Requires OPENAI_API_KEY.",
     openrouter:
-      "300+ models from Anthropic, OpenAI, Google, Z.ai, and more routed through a single endpoint. Use model IDs like 'anthropic/claude-sonnet-5', 'openai/gpt-5.5', or 'z-ai/glm-5.2'. Requires OPENROUTER_API_KEY.",
+      "300+ models from Anthropic, OpenAI, Google, Z.ai, and more routed through a single endpoint. Use model IDs like 'anthropic/claude-sonnet-5', 'openai/gpt-5.6-sol', or 'z-ai/glm-5.2'. Requires OPENROUTER_API_KEY.",
     google:
       "Google Gemini models via the Vercel AI SDK. Requires GOOGLE_GENERATIVE_AI_API_KEY.",
     groq: "Groq LPU inference via the Vercel AI SDK. Requires GROQ_API_KEY.",

package/corpus/core/src/agent/model-config.ts

@@ -11,14 +11,13 @@
 //
 // Sources (June 2026):
 //  Anthropic  https://platform.claude.com/docs/en/about-claude/models/overview
-//  OpenAI     https://developers.openai.com/api/docs/models/gpt-5.5
-//             https://developers.openai.com/api/docs/models/gpt-5.4
+//  OpenAI     https://developers.openai.com/api/docs/models/gpt-5.6
 //  Google     https://ai.google.dev/gemini-api/docs/models
 //  OpenRouter https://openrouter.ai/api/v1/models
 //
 // Family defaults (used when a model id isn't listed explicitly):
 //  claude-*        → 200_000  (Haiku 4.5 and earlier models)
-//  gpt-5*          → 1_050_000 (GPT-5.4/5.5 flagship context)
+//  gpt-5*          → 1_050_000 (GPT-5.6 Sol/Terra flagship context)
 //  gemini-2* / gemini-3* → 1_048_576
 //  everything else → 128_000  (safe conservative floor)
 //
@@ -37,9 +36,9 @@ const MODEL_CONTEXT_WINDOWS: Record<string, number> = {
   "claude-haiku-4-5-20251001": 200_000,
 
   // ── Builder gateway OpenAI IDs (dot→dash) ────────────────────────────────
-  "gpt-5-5": 1_050_000,
-  "gpt-5-4": 1_050_000,
-  "gpt-5-4-mini": 400_000,
+  "gpt-5-6-sol": 1_050_000,
+  "gpt-5-6-terra": 1_050_000,
+  "gpt-5-6-luna": 400_000,
 
   // ── Gemini (Builder gateway IDs) ─────────────────────────────────────────
   "gemini-3-1-pro": 1_048_576,
@@ -52,15 +51,16 @@ const MODEL_CONTEXT_WINDOWS: Record<string, number> = {
   "anthropic/claude-opus-4.7": 1_000_000,
   "anthropic/claude-sonnet-5": 1_000_000,
   "anthropic/claude-sonnet-4.6": 1_000_000,
-  "openai/gpt-5.5": 1_050_000,
-  "openai/gpt-5.4": 1_050_000,
+  "openai/gpt-5.6-sol": 1_050_000,
+  "openai/gpt-5.6-terra": 1_050_000,
+  "openai/gpt-5.6-luna": 1_050_000,
   "google/gemini-2.5-flash": 1_048_576,
   "z-ai/glm-5.2": 1_048_576,
 
   // ── AI-SDK native OpenAI IDs ──────────────────────────────────────────────
-  "gpt-5.5": 1_050_000,
-  "gpt-5.4": 1_050_000,
-  "gpt-5.4-mini": 400_000,
+  "gpt-5.6-sol": 1_050_000,
+  "gpt-5.6-terra": 1_050_000,
+  "gpt-5.6-luna": 400_000,
 
   // ── AI-SDK native Google IDs ──────────────────────────────────────────────
   "gemini-3.5-flash": 1_048_576,
@@ -127,15 +127,13 @@ export function getContextWindowForModel(modelId: string): number {
 //  Anthropic  https://platform.claude.com/docs/en/docs/about-claude/models/overview
 //             (Fable 5 / Opus 4.8 / Opus 4.7 / Sonnet 5 / Sonnet 4.6 = 128K;
 //              Haiku 4.5 / Sonnet 4.5 / Opus 4.5 = 64K)
-//  OpenAI     https://developers.openai.com/api/docs/models/gpt-5.5
-//             https://developers.openai.com/api/docs/models/gpt-5.4
-//             https://developers.openai.com/api/docs/models/gpt-5.4-mini
-//             (GPT-5.5 / GPT-5.4 / GPT-5.4-mini = 128K)
+//  OpenAI     https://developers.openai.com/api/docs/models/gpt-5.6
+//             (GPT-5.6 Sol / Terra / Luna = 40K)
 //
 // Family defaults (used when a model id isn't listed explicitly):
 //  claude flagship (fable-5 / opus-4.6+ / sonnet-5 / sonnet-4.6) → 128_000
 //  claude-* (Haiku 4.5, older/unknown Claude ids)                → 64_000
-//  gpt-5*                                                        → 128_000
+//  gpt-5*                                                        → 128_000 (safe fallback)
 //  everything else                                               → 64_000
 //    (safe conservative ceiling that matches the previous global clamp)
 // ---------------------------------------------------------------------------
@@ -151,9 +149,9 @@ const MODEL_MAX_OUTPUT_TOKENS: Record<string, number> = {
   "claude-haiku-4-5-20251001": 64_000,
 
   // ── Builder gateway OpenAI IDs (dot→dash) ────────────────────────────────
-  "gpt-5-5": 128_000,
-  "gpt-5-4": 128_000,
-  "gpt-5-4-mini": 128_000,
+  "gpt-5-6-sol": 40_000,
+  "gpt-5-6-terra": 40_000,
+  "gpt-5-6-luna": 40_000,
 
   // ── OpenRouter model IDs ──────────────────────────────────────────────────
   "anthropic/claude-fable-5": 128_000,
@@ -161,13 +159,14 @@ const MODEL_MAX_OUTPUT_TOKENS: Record<string, number> = {
   "anthropic/claude-opus-4.7": 128_000,
   "anthropic/claude-sonnet-5": 128_000,
   "anthropic/claude-sonnet-4.6": 128_000,
-  "openai/gpt-5.5": 128_000,
-  "openai/gpt-5.4": 128_000,
+  "openai/gpt-5.6-sol": 40_000,
+  "openai/gpt-5.6-terra": 40_000,
+  "openai/gpt-5.6-luna": 128_000,
 
   // ── AI-SDK native OpenAI IDs ──────────────────────────────────────────────
-  "gpt-5.5": 128_000,
-  "gpt-5.4": 128_000,
-  "gpt-5.4-mini": 128_000,
+  "gpt-5.6-sol": 40_000,
+  "gpt-5.6-terra": 40_000,
+  "gpt-5.6-luna": 40_000,
 };
 
 /**
@@ -243,7 +242,7 @@ function openRouterModelId(provider: string, model: string): string {
   return `${provider}/${model}`;
 }
 
-const FRAMEWORK_DEFAULT_OPENAI_MODEL = "gpt-5.5";
+const FRAMEWORK_DEFAULT_OPENAI_MODEL = "gpt-5.6-sol";
 const FRAMEWORK_DEFAULT_BUILDER_MODEL = ANTHROPIC_DEFAULT_MODEL_ID;
 const FRAMEWORK_DEFAULT_BUILDER_OPENAI_MODEL = builderGatewayModelId(
   FRAMEWORK_DEFAULT_OPENAI_MODEL,
@@ -262,8 +261,8 @@ export const AGENT_MODEL_CONFIG = {
       CLAUDE_SONNET_MODEL_ID,
       "claude-haiku-4-5",
       FRAMEWORK_DEFAULT_BUILDER_OPENAI_MODEL,
-      "gpt-5-4",
-      "gpt-5-4-mini",
+      "gpt-5-6-terra",
+      "gpt-5-6-luna",
       "gemini-3-1-pro",
       "gemini-3-5-flash",
       "gemini-3-1-flash-lite",
@@ -292,8 +291,8 @@ export const AGENT_MODEL_CONFIG = {
       defaultModel: FRAMEWORK_DEFAULT_OPENAI_MODEL,
       supportedModels: [
         FRAMEWORK_DEFAULT_OPENAI_MODEL,
-        "gpt-5.4",
-        "gpt-5.4-mini",
+        "gpt-5.6-terra",
+        "gpt-5.6-luna",
       ],
     },
     openrouter: {
@@ -303,7 +302,8 @@ export const AGENT_MODEL_CONFIG = {
         "anthropic/claude-opus-4.8",
         OPENROUTER_CLAUDE_SONNET_MODEL_ID,
         FRAMEWORK_DEFAULT_OPENROUTER_MODEL,
-        "openai/gpt-5.4",
+        "openai/gpt-5.6-terra",
+        "openai/gpt-5.6-luna",
         // Current stable Gemini on OpenRouter (2.5 Flash is GA)
         "google/gemini-2.5-flash",
         "z-ai/glm-5.2",

package/corpus/core/src/agent/production-agent.ts

@@ -2840,6 +2840,25 @@ export async function runAgentLoop(opts: {
     try {
       const priorEvents = await getCurrentTurnEventsForThread(opts.threadId);
       if (priorEvents.length > 0) {
+        // A logical turn can span multiple background continuation runs. Final
+        // response guards must see successful reads from earlier chunks, not
+        // only tools executed after the latest handoff. Otherwise a guard can
+        // reject a grounded answer (or a successfully-created artifact) after
+        // the evidence-producing query completed in a predecessor run.
+        for (const event of priorEvents) {
+          if (event.type === "tool_start") {
+            toolCallHistory.push({
+              name: event.tool,
+              input: event.input,
+            });
+          } else if (event.type === "tool_done") {
+            toolResultHistory.push({
+              name: event.tool,
+              content: event.result,
+              isError: event.isError === true,
+            });
+          }
+        }
         toolCallJournal = classifyToolCallJournal(priorEvents);
       }
     } catch {
@@ -3790,7 +3809,7 @@ export async function runAgentLoop(opts: {
             tool: toolCall.name,
             input: toolCall.input as Record<string, unknown>,
             result,
-            completedSideEffect: false,
+            completedSideEffect: true,
           });
           recordToolResult(result, false);
           return {
@@ -3844,6 +3863,7 @@ export async function runAgentLoop(opts: {
               tool: toolCall.name,
               input: toolCall.input as Record<string, unknown>,
               result,
+              completedSideEffect: true,
               ...(actionEntry.chatUI ? { chatUI: actionEntry.chatUI } : {}),
             });
             recordToolResult(result, false);
@@ -4951,6 +4971,73 @@ export interface ChainServerDrivenContinuationDeps {
   sleep?: (ms: number) => Promise<void>;
 }
 
+/** Retry-budget sizing for one `chainServerDrivenContinuation` dispatch. */
+export interface ContinuationDispatchBudget {
+  maxDispatchAttempts: number;
+  dispatchResponseTimeoutMs: number;
+  /** Cap (ms) on the per-gap exponential backoff. `Infinity` preserves the
+   *  original uncapped `500 * 2 ** attempt` schedule for the two budgets
+   *  that predate this cap (their attempt counts are low enough it never
+   *  mattered); only the larger proven-in-background-function budget uses a
+   *  real cap so its extra attempts don't add unbounded backoff. */
+  backoffCapMs: number;
+}
+
+/**
+ * Sizes the dispatch retry budget by *remaining wall-clock capacity*, not by
+ * dispatch TARGET — the two are independent concerns. `chainViaDurableBackground`
+ * only picks where the dispatch goes (see `continuationDispatchPath` above);
+ * this picks how hard to retry getting it there.
+ *
+ * Three cases:
+ *   - `chainViaDurableBackground === true`: the durable worker chain dispatching
+ *     to the Netlify background function url. Unchanged: 3 attempts / 15s.
+ *   - `chainViaDurableBackground === false` and
+ *     `workerProvenInBackgroundFunction === true`: a worker PROVEN (by runtime
+ *     function name, see `shouldUseBackgroundFunctionTimeoutForWorker`) to
+ *     already be executing inside a real `-background` function — it was
+ *     forced onto the regular-function dispatch target only because a
+ *     background function cannot invoke its own URL from within a live
+ *     invocation (see the caller's `&& !runsInBackgroundFunction` comment),
+ *     NOT because it lacks time or a connected-client fallback. This worker
+ *     has up to `BACKGROUND_SOFT_TIMEOUT_CEILING_MS` (13min) of soft-timeout
+ *     budget behind it and up to Netlify's ~15min hard function limit ahead —
+ *     roughly 2 minutes of remaining wall clock — and, being a background
+ *     worker, NO connected client to fall back on if the handoff is dropped.
+ *     Demoting it to the foreground's 2-attempt/10s budget is exactly the bug
+ *     this type documents: 5 attempts / 15s response timeout, with backoff
+ *     capped at 4s/gap (500ms, 1s, 2s, 4s across the 4 gaps ≈ 7.5s total).
+ *     Worst case: 5 × 15s dispatch + ~7.5s backoff ≈ 82.5s, safely inside the
+ *     ~2min of remaining budget before the function's hard kill.
+ *   - Otherwise: a true foreground caller not proven in a background
+ *     function. Unchanged: 2 attempts / 10s — it has a live connected client
+ *     as a fallback (the terminal `auto_continue` event still reaches it).
+ */
+export function resolveContinuationDispatchBudget(opts: {
+  chainViaDurableBackground: boolean;
+  workerProvenInBackgroundFunction: boolean;
+}): ContinuationDispatchBudget {
+  if (opts.chainViaDurableBackground) {
+    return {
+      maxDispatchAttempts: 3,
+      dispatchResponseTimeoutMs: 15_000,
+      backoffCapMs: Infinity,
+    };
+  }
+  if (opts.workerProvenInBackgroundFunction) {
+    return {
+      maxDispatchAttempts: 5,
+      dispatchResponseTimeoutMs: 15_000,
+      backoffCapMs: 4_000,
+    };
+  }
+  return {
+    maxDispatchAttempts: 2,
+    dispatchResponseTimeoutMs: 10_000,
+    backoffCapMs: Infinity,
+  };
+}
+
 /**
  * Server-driven continuation handoff for a chunk that hit its soft-timeout
  * boundary still unfinished: mint the next chunk's runId, PRE-INSERT its run
@@ -4980,7 +5067,14 @@ export interface ChainServerDrivenContinuationDeps {
  *     a dead handoff — after a failed/timed-out attempt the successor's
  *     ATOMIC CLAIM is consulted (`readBackgroundRunClaim`): a row that
  *     flipped to `background-processing` (or already went terminal) proves
- *     the handoff landed, so no retry is fired. 2 attempts, ~10s settle.
+ *     the handoff landed, so no retry is fired.
+ *
+ * `chainViaDurableBackground` does NOT alone determine the retry BUDGET —
+ * see `resolveContinuationDispatchBudget` and `workerProvenInBackgroundFunction`
+ * below: a worker forced onto this same `false` target because it is proven
+ * to already be inside a real background function gets a materially larger
+ * budget than a true foreground caller, since it has no connected-client
+ * fallback and minutes of remaining wall clock instead of seconds.
  *
  * Never throws — all failure paths are handled (recorded + marked) inside.
  */
@@ -4994,6 +5088,13 @@ export async function chainServerDrivenContinuation(opts: {
   requestBody: Record<string, unknown>;
   backgroundContinuationCount: number;
   chainViaDurableBackground: boolean;
+  /** True only when this worker is PROVEN (by runtime function name) to
+   *  already be executing inside a real Netlify `-background` function —
+   *  distinct from `chainViaDurableBackground`, which is forced `false` for
+   *  this exact worker (it cannot dispatch to its own function URL from a
+   *  live invocation). Widens the retry budget; does NOT change the dispatch
+   *  target. See `resolveContinuationDispatchBudget`. Defaults to `false`. */
+  workerProvenInBackgroundFunction?: boolean;
   deps?: ChainServerDrivenContinuationDeps;
 }): Promise<void> {
   const d = {
@@ -5060,10 +5161,13 @@ export async function chainServerDrivenContinuation(opts: {
     : AGENT_CHAT_PROCESS_RUN_PATH;
   const continuationExpectsNetlifyBackgroundFunction =
     dispatchPathTargetsNetlifyBackgroundFunction(continuationDispatchPath);
-  const maxDispatchAttempts = opts.chainViaDurableBackground ? 3 : 2;
-  const dispatchResponseTimeoutMs = opts.chainViaDurableBackground
-    ? 15_000
-    : 10_000;
+  const dispatchBudget = resolveContinuationDispatchBudget({
+    chainViaDurableBackground: opts.chainViaDurableBackground,
+    workerProvenInBackgroundFunction:
+      opts.workerProvenInBackgroundFunction === true,
+  });
+  const maxDispatchAttempts = dispatchBudget.maxDispatchAttempts;
+  const dispatchResponseTimeoutMs = dispatchBudget.dispatchResponseTimeoutMs;
   const continuationMarker = {
     runId: nextRunId,
     turnId: effectiveTurnId,
@@ -5147,7 +5251,17 @@ export async function chainServerDrivenContinuation(opts: {
     ) {
       try {
         if (attempt > 0) {
-          await d.sleep(500 * 2 ** attempt);
+          // Uncapped budgets (durable-background and true-foreground) keep
+          // the original `500 * 2 ** attempt` schedule unchanged. The capped
+          // budget (proven-in-background-function) instead uses a schedule
+          // starting at 500ms and doubling per gap, capped at
+          // `backoffCapMs` — see `resolveContinuationDispatchBudget` for why
+          // this stays well inside the worker's remaining wall clock even
+          // with 5 attempts.
+          const backoffMs = Number.isFinite(dispatchBudget.backoffCapMs)
+            ? Math.min(500 * 2 ** (attempt - 1), dispatchBudget.backoffCapMs)
+            : 500 * 2 ** attempt;
+          await d.sleep(backoffMs);
           // Keep the pre-inserted successor row visibly alive while we
           // retry: the awaited attempts + backoff can outlast
           // UNCLAIMED_BACKGROUND_RUN_GRACE_MS (25s), and without a fresh
@@ -6599,6 +6713,14 @@ export function createProductionAgentHandler(
                     isAgentChatDurableBackgroundEnabled({
                       appOptIn: options.durableBackgroundRuns === true,
                     }) && !runsInBackgroundFunction,
+                  // Only changes the retry BUDGET, never the dispatch target
+                  // above: a worker proven in a real background function has
+                  // minutes of remaining wall clock and no connected-client
+                  // fallback, so it must not be demoted to the foreground's
+                  // 2-attempt budget just because it was forced onto the
+                  // regular-function dispatch target. See
+                  // `resolveContinuationDispatchBudget`.
+                  workerProvenInBackgroundFunction: runsInBackgroundFunction,
                 });
               }
             } finally {