@agent-native/core 0.96.0 → 0.97.0

package/docs/content/locales/zh-TW/sandbox-adapters.mdx

@@ -101,6 +101,10 @@ Agent-Native 有兩個轉接器接縫，可消除狹窄後面的問題，
       path: "index.ts",
       note: "選取：getSandboxAdapter() / registerSandboxAdapter()",
     },
+    {
+      path: "background.ts",
+      note: "持久佇列標記與背景執行生命週期",
+    },
     {
       path: "local-child-process-adapter.ts",
       note: "預設後端：受限的 Node 子行程",
@@ -181,12 +185,17 @@ registerSandboxAdapter(adapter)  →  AGENT_NATIVE_SANDBOX  →  local default
 
 ### `AGENT_NATIVE_SANDBOX` 環境變數 {#env}
 
-透過 id 選取內建轉接器。目前僅有線`local`（預設）；未知值回退到本機而不是執行失敗。
+透過 id 選取內建轉接器。`local`（預設）與 `background` 均已接入；未知值會回退到 `local`，而不會導致執行失敗。
 
 ```bash
-AGENT_NATIVE_SANDBOX=local   # 預設值——顯式
+AGENT_NATIVE_SANDBOX=local        # 預設值——顯式
+AGENT_NATIVE_SANDBOX=background   # 將每次 run-code 呼叫持久排入佇列
 ```
 
+`background` 將原始程式碼存入 `sandbox_executions`，並立即回傳帶有 `status: "queued"` 的 `executionId`。簽署的自我派送會啟動新的 serverless 呼叫；長時間執行的 Node 會在行程內啟動分離工作；狀態輪詢與定期 sweep 會重新驅動遺失的派送或已過期的 lease。稍後輪詢該執行即可取得持久化結果。
+
+`BackgroundQueueAdapter` 是持久佇列標記，而不是執行器。佇列中的工作會在可用時使用已註冊的非佇列執行轉接器，否則回退到本機子行程。僅選取 `background` 不會提供遠端或容器隔離，也不會讓 edge 執行環境與 `node:child_process` 相容。
+
 ### `registerSandboxAdapter()` {#register}
 
 主機行程透過接縫的 `index.ts` 覆蓋所有後續 `run-code` 呼叫的後端 - 例如，執行遠端容器中的每個呼叫：
@@ -211,13 +220,15 @@ registerSandboxAdapter(new RemoteSandboxAdapter());
 
 ## 耐用跑鞋的接縫 {#durable}
 
-這個介面是特意為未來的遠端/持久沙箱做的接縫。遠端或持久轉接器（Docker、Vercel-Sandbox 式執行程式或排隊背景工作程式）將：
+內建 `background` 轉接器已提供持久排隊與新的執行預算，但實際執行仍使用非佇列轉接器或本機子行程回退。另行註冊的遠端或隔離轉接器（Docker 或 Vercel-Sandbox 式執行器）可以提供不同的執行邊界，也可以執行每次呼叫的背景工作。
+
+此類轉接器將：
 
-1. 針對行程外執行時實現 `SandboxAdapter.run`。
-2. 透過隧道環回網橋（或代理網橋回調至父級）。
-3. 讓大資料作業獨立於請求生命週期執行直至完成 - 超過限制本機子行程轉接器的託管約 40 秒程式碼執行上限。
+1. 針對行程外執行環境實作 `SandboxAdapter.run`。
+2. 為 loopback 橋接建立通道，或將橋接呼叫代理回父行程。
+3. 獨立於已提供的持久佇列生命週期，提供遠端或容器隔離。
 
-將其註冊為新的 `AGENT_NATIVE_SANDBOX` 值（例如 `remote`）和/或透過 `registerSandboxAdapter()`。代理迴圈和 `run-code.ts` 永遠不會改變。
+透過 `registerSandboxAdapter()` 以程式化方式註冊。代理迴圈和 `run-code.ts` 無需變更。
 
 > [!TIP]
 > `agent-native add sandbox docker` 藍圖發出了一個完整的、獨立的配方，用於針對此接縫實現 Docker 轉接器。參見[Blueprint Installer](/docs/blueprint-installer)。

package/docs/content/locales/zh-TW/security.mdx

@@ -415,3 +415,11 @@ AGENT_NATIVE_KEYS_WORKSPACE_FALLBACK=1
 ```
 
 無論此標誌如何，工作空間範圍的秘密寫入仍然需要組織所有者/管理員角色。
+
+## 下一步
+
+- [**Authentication**](/docs/authentication) — 本頁所依賴的驗證模式、cookie realm 和工作階段細節
+- [**Multi-Tenancy**](/docs/multi-tenancy) — `org_id` 範圍界定背後的組織成員模型
+- [**Sharing**](/docs/sharing) — 應用於可共用資源的 `ownableColumns()` 和存取守衛模式
+- [**Messaging**](/docs/messaging#env-vars) — 上方清單中提到的每個整合的 webhook 簽名金鑰
+- [**Deployment**](/docs/deployment) — 此清單假定已設定的正式環境變數

package/docs/content/package-lifecycle.mdx

@@ -0,0 +1,51 @@
+---
+title: Package Lifecycle
+description: Inspect, add, and eject manifest-driven Agent Native packages safely.
+---
+
+# Package lifecycle
+
+Reusable Agent Native packages can publish a versioned static
+`agent-native.package.json`. The CLI reads that JSON without executing package
+code and reports the package's actions, schema entry point, skills, secret key
+names, and peer providers.
+
+```bash
+agent-native package inspect @agent-native/scheduling
+agent-native package inspect @agent-native/scheduling --json
+agent-native package add @agent-native/scheduling
+agent-native package add @agent-native/scheduling --apply
+agent-native package eject @agent-native/scheduling --apply
+```
+
+`add` and `eject` are dry-run by default. `--apply` is required before the CLI
+writes files or runs the detected package manager. Use `--root` for a different
+project root; at a workspace root, pass `--app <name>` to select the target app.
+
+## Safety and idempotency
+
+Before writing, the CLI resolves every contribution and refuses missing or
+ambiguous layouts, existing files with different content, escaping manifest
+paths, and eject targets that already exist. It stages the complete write set,
+uses atomic renames, snapshots package and lock files, and rolls back if the
+package-manager install fails. A provenance record under
+`.agent-native/packages/` makes a repeated add a no-op when generated files are
+unchanged.
+
+Inspection and registry staging use static package metadata only. The CLI never
+imports a package's JavaScript manifest and passes `--ignore-scripts` while
+downloading an uninstalled package archive. Reports show credential key names,
+never credential values.
+
+## Scheduling pilot
+
+`@agent-native/scheduling` is the first package with the generic manifest. Add
+creates action re-export stubs, adds the schema export, copies its agent skills,
+records the dependency, and reports required secret names and providers.
+Eject copies the published Scheduling source to `packages/scheduling`, switches
+the dependency to `workspace:*`, and preserves canonical
+`@agent-native/scheduling` imports so workspace resolution selects the local
+copy.
+
+Ejecting other packages, including Pinpoint, is intentionally refused until the
+Scheduling pilot has proven the contract.

package/docs/content/sandbox-adapters.mdx

@@ -106,6 +106,10 @@ The seam lives in core at `packages/core/src/coding-tools/sandbox/` — `adapter
       path: "index.ts",
       note: "selection: getSandboxAdapter() / registerSandboxAdapter()",
     },
+    {
+      path: "background.ts",
+      note: "durable queue marker and background execution lifecycle",
+    },
     {
       path: "local-child-process-adapter.ts",
       note: "the default backend — locked-down Node child process",
@@ -189,12 +193,17 @@ registerSandboxAdapter(adapter)  →  AGENT_NATIVE_SANDBOX  →  local default
 
 #### `AGENT_NATIVE_SANDBOX` env var {#env}
 
-Selects a built-in adapter by id. Currently only `local` (the default) is wired; unknown values fall back to local rather than failing the run.
+Selects a built-in adapter by id. Both `local` (the default) and `background` are wired; unknown values fall back to local rather than failing the run.
 
 ```bash
-AGENT_NATIVE_SANDBOX=local   # the default — explicit
+AGENT_NATIVE_SANDBOX=local        # the default — explicit
+AGENT_NATIVE_SANDBOX=background   # enqueue every run-code call durably
 ```
 
+`background` stores the raw code in `sandbox_executions` and returns an `executionId` with `status: "queued"` immediately. A signed self-dispatch starts a fresh serverless invocation; long-lived Node starts detached in-process work; status polling and the periodic sweep redrive lost dispatches or expired leases. Poll the execution later for its persisted result.
+
+`BackgroundQueueAdapter` is a durable queue marker, not the executor. Queued work uses a registered non-queued execution adapter when one is available; otherwise it falls back to the local child process. Selecting `background` alone does not provide remote or container isolation, and it does not make an edge runtime compatible with `node:child_process`.
+
 #### `registerSandboxAdapter()` {#register}
 
 A host process overrides the backend for all subsequent `run-code` invocations through the seam's `index.ts` — for example, to run every call in a remote container:
@@ -219,13 +228,15 @@ registerSandboxAdapter(new RemoteSandboxAdapter());
 
 ### The seam for a durable runner {#durable}
 
-This interface is deliberately the seam for a future remote/durable sandbox. A remote or durable adapter (Docker, a Vercel-Sandbox-style runner, or a queued background worker) would:
+The built-in `background` adapter already provides durable queuing and a fresh execution budget, while actual execution still uses a non-queued adapter or the local child-process fallback. A separately registered remote or isolated adapter (Docker or a Vercel-Sandbox-style runner) can provide a different execution boundary and can also execute per-call background work.
+
+Such an adapter would:
 
 1. Implement `SandboxAdapter.run` against an out-of-process runtime.
 2. Tunnel the loopback bridge (or proxy bridge calls back to the parent).
-3. Let large data jobs run to completion independently of the request lifecycle — exceeding the hosted ~40s code-exec ceiling that bounds the local child-process adapter.
+3. Supply remote or container isolation independently of the shipped durable queue lifecycle.
 
-Register it under a new `AGENT_NATIVE_SANDBOX` value (e.g. `remote`) and/or via `registerSandboxAdapter()`. The agent loop and `run-code.ts` never change.
+Register it programmatically via `registerSandboxAdapter()`. The agent loop and `run-code.ts` do not need to change.
 
 <Callout id="doc-block-adap1tip" tone="info">
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.96.0",
+  "version": "0.97.0",
   "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": {
@@ -101,6 +101,10 @@
     "./shared": "./dist/shared/index.js",
     "./voice": "./dist/voice/index.js",
     "./scripts": "./dist/scripts/index.js",
+    "./guards": {
+      "types": "./dist/guards/index.d.ts",
+      "default": "./dist/guards/index.js"
+    },
     "./application-state": "./dist/application-state/index.js",
     "./settings": "./dist/settings/index.js",
     "./localization": "./dist/localization/index.js",
@@ -207,6 +211,10 @@
       "default": "./dist/local-artifacts/index.js"
     },
     "./workspace-files": "./dist/workspace-files/index.js",
+    "./package-lifecycle": {
+      "types": "./dist/package-lifecycle/index.d.ts",
+      "default": "./dist/package-lifecycle/index.js"
+    },
     "./code-agents": "./dist/code-agents/index.js",
     "./code-agents/transcript-normalizer": "./dist/code-agents/transcript-normalizer.js",
     "./workspace-connections": "./dist/workspace-connections/index.js",
@@ -321,7 +329,7 @@
     "y-protocols": "^1.0.7",
     "yjs": "^13.6.31",
     "zod": "^4.3.6",
-    "@agent-native/toolkit": "^0.4.5"
+    "@agent-native/toolkit": "^0.4.6"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",
@@ -365,7 +373,6 @@
     "react-dom": "^19.2.7",
     "react-router": "^8.1.0",
     "tailwindcss": "^4.2.4",
-    "typescript": "npm:@typescript/typescript6@^6.0.2",
     "typescript-7": "npm:typescript@^7.0.2",
     "vite": "8.1.0",
     "vitest": "^4.1.5",

package/src/templates/default/package.json

@@ -7,6 +7,7 @@
     "build": "agent-native build",
     "start": "agent-native start",
     "typecheck": "agent-native typecheck",
+    "doctor": "agent-native doctor",
     "action": "agent-native action",
     "script": "agent-native script",
     "skills:update": "agent-native skills update scaffold --project",
@@ -43,8 +44,7 @@
     "tailwind-merge": "^3.5.0",
     "tailwindcss": "^4.1.18",
     "tsx": "^4.20.3",
-    "typescript": "catalog:",
     "typescript-7": "catalog:",
-    "vite": "^8.0.0"
+    "vite": "8.1.0"
   }
 }

package/src/templates/headless/package.json

@@ -19,7 +19,6 @@
     "@types/node": "^24.2.1",
     "oxfmt": "catalog:",
     "tsx": "^4.20.3",
-    "typescript": "catalog:",
     "typescript-7": "catalog:"
   }
 }

package/src/templates/workspace-core/.agents/skills/audit-log/SKILL.md

@@ -77,6 +77,9 @@ SQL to the caller — they never leak another tenant's rows:
   (`agent` | `human` | `system`), `status`, `threadId`/`turnId`, `action`,
   `sinceMs`, `limit`.
 - `get-audit-event` — one event by id, with its redacted input payload.
+- `export-audit-events` — bulk CSV/NDJSON export (same filters minus `limit`,
+  plus `format` and `maxRows`) for offline/compliance pulls; itself audited
+  via `onRead`.
 
 Call them from the UI with `useActionQuery` to build an activity feed or a
 "who changed this" line — never hand-write a fetch to the audit table.

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

@@ -61,7 +61,7 @@ Use the web-request tool with ${keys.SLACK_WEBHOOK}.
 | `triggerType` | `"schedule" \| "event"`        | How the automation fires                               |
 | `event`       | `string?`                      | Event name to subscribe to (event triggers)            |
 | `condition`   | `string?`                      | Natural-language condition evaluated before dispatch   |
-| `mode`        | `"agentic" \| "deterministic"` | Full agent loop vs. fixed action set                   |
+| `mode`        | `"agentic"`                    | Full agent loop (only supported mode; `"deterministic"` was removed — never implemented, rejected at define time) |
 | `model`       | `string?`                      | Override the model for this trigger's agent loop       |
 | `domain`      | `string?`                      | Grouping tag (mail, calendar, clips, etc.)             |
 | `createdBy`   | `string?`                      | Owner email                                            |

package/src/templates/workspace-core/package.json

@@ -32,7 +32,6 @@
     "prepare": "tsc"
   },
   "devDependencies": {
-    "typescript": "catalog:",
     "typescript-7": "catalog:"
   }
 }

package/src/templates/workspace-root/package.json

@@ -20,7 +20,6 @@
     "@types/node": "^24.2.1",
     "oxfmt": "catalog:",
     "tsx": "catalog:",
-    "typescript": "catalog:",
     "typescript-7": "catalog:"
   },
   "packageManager": "pnpm@10.14.0",

package/corpus/templates/slides/app/components/ui/toast.tsx

@@ -1 +0,0 @@
-export * from "@agent-native/toolkit/ui/toast";

package/corpus/templates/slides/app/components/ui/toaster.tsx

@@ -1 +0,0 @@
-export * from "@agent-native/toolkit/ui/toaster";

package/corpus/templates/slides/app/hooks/use-toast.ts

@@ -1 +0,0 @@
-export * from "@agent-native/toolkit/hooks/use-toast";