同步bailian deployment能力 (#86)

* feat(bailian): implement native Deployment support

Bailian's Agent Studio now exposes a first-class Deployment resource, so
replace the emulated implementation that expanded a deployment into a
one-shot Session at run time. The adapter now uses the real endpoints for
create, get, list, update, archive, run, and pause/unpause; the deployment
API takes `agent` as an object ({id, version?}) rather than the bare id
the sessions API accepts.

Notable behavior: file resources upload at apply time instead of run time,
and updateDeployment falls back to create when a state row carries a null
remote_id so deployments recorded under the emulated implementation
materialize on the next apply. Removing an existing schedule is rejected —
update replaces only the fields it is given and the API documents no null
form for `schedule`.

`user.define_outcome` events and `github_repository` resources are dropped
from the payload and now warn in validate-config; the emulated schedule
warning no longer fires since cron runs server-side. Docs, capability
tables, examples, and the live smoke script move to native.

Verified: typecheck, bun test (653 pass), biome. Not run against the live
API — no workspace credentials.

* fix(bailian): harden native deployment lifecycle

* fix(deps): upgrade nanoid to 3.3.18

Author: chenanran555

.changeset/bailian-native-deployments.md

@@ -0,0 +1,5 @@
+---
+"@openagentpack/sdk": minor
+---
+
+Bailian: implement native Deployment support against the Agent Studio `/deployments` API (create, get, list, update, archive, run, pause/unpause), replacing the previous emulated session expansion. Deployment schedules now run server-side; `user.define_outcome` events and `github_repository` resources are dropped from the deployment payload and surface a warning on plan.

README.md

@@ -147,7 +147,7 @@ Beta testers can install `@openagentpack/cli@beta`; see the [release guide](./do
 | MCP Server | native | native | native | native |
 | Memory Store | unsupported | native | native | native |
 | Multi-Agent | unsupported | unsupported | native | native |
-| Deployment | emulated | native | native | emulated |
+| Deployment | native | native | native | emulated |
 | Session | native | native | native | native |
 
 The full capability matrix and per-provider differences live in the [Provider reference](./docs/reference/providers.md).

README.zh-CN.md

@@ -147,7 +147,7 @@ Beta 用户可以安装 `@openagentpack/cli@beta`；固定版本及切回稳定
 | MCP Server | native | native | native | native |
 | Memory Store | unsupported | native | native | native |
 | Multi-Agent | unsupported | unsupported | native | native |
-| Deployment | emulated | native | native | emulated |
+| Deployment | native | native | native | emulated |
 | Session | native | native | native | native |
 
 完整能力矩阵与各 Provider 差异见 [Provider 参考](./docs/reference/providers.zh-CN.md)。

bun.lock

@@ -63,4 +63,4 @@ agents state import <address> <remote-id>
 
 Resources (agents, environments, skills…) are **infrastructure** — long-lived, managed by `plan`/`apply`. A **session** is a **runtime** conversation started from an agent. Sessions are managed separately with `agents session` and are not part of the plan/apply lifecycle.
 
-Deployments sit between the two: they are declared as resources but produce runs. On Qoder and Claude they schedule server-side; on Bailian and Volcengine Ark a `deployment run` expands into a session.
+Deployments sit between the two: they are declared as resources but produce runs. On Bailian, Qoder, and Claude they schedule server-side; on Volcengine Ark a `deployment run` expands into a session.

docs/architecture/how-it-works.md

@@ -19,7 +19,7 @@ Because the declaration is a file, it gets everything a file gets: code review,
 - The **agent harness** is the provider-managed layer that wraps a model into an agent: knowledge base, skills, MCP wiring, prompt/instructions, vault, deployment, multi-agent orchestration. These are the customer's portable assets.
 - The **agent infra** is the interchangeable execution substrate beneath the harness — the specific provider (Bailian, Qoder, Claude, Volcengine Ark) that runs the agent.
 
-OpenAgentPack's portability claim is that the same harness declaration can target different agent infra. Portability means the *core declaration* is portable and the per-provider **capability contract** is explicit — unsupported facets degrade gracefully (for example, an emulated `Deployment` on Bailian/Volcengine Ark) — not that every feature is identical on every provider.
+OpenAgentPack's portability claim is that the same harness declaration can target different agent infra. Portability means the _core declaration_ is portable and the per-provider **capability contract** is explicit — unsupported facets degrade gracefully (for example, an emulated `Deployment` on Volcengine Ark) — not that every feature is identical on every provider.
 
 ## What this enables
 

docs/concepts/agents-as-code.md

@@ -24,17 +24,18 @@ How a deployment *runs* depends on the provider's capability tier:
 |----------|:--------------:|------------------------------------|
 | Claude | native | schedules server-side through the deployments API |
 | Qoder | native | creates a deployment run and associated session |
-| Bailian, Ark | emulated | expands into a one-shot session at run time |
+| Bailian | native | triggers a server-side run through the deployments API |
+| Ark | emulated | expands into a one-shot session at run time |
 
-On the emulated providers, scheduling and outcome rubrics are **not** enforced server-side — use external cron/CI for always-on or scheduled runs.
+On Ark (the emulated provider), scheduling and outcome rubrics are **not** enforced server-side — use external cron/CI for always-on or scheduled runs.
 
 ## The lifecycle in one picture
 
 ```text
 agents.yaml ──plan/apply──▶ managed resources (agent, environment, …)
                                │
                                └─session create/run──▶ runtime session
-                               └─deployment run──────▶ runtime session (emulated) or scheduled run (native)
+                               └─deployment run──────▶ scheduled run (native) or runtime session (emulated on Ark)
 ```
 
 Next: [Run sessions](../guides/run-sessions.md) and [Manage deployments](../guides/manage-deployments.md).

docs/concepts/sessions-and-deployments.md

@@ -53,7 +53,7 @@ agents destroy
 | MCP Server | native | native | native | native |
 | Memory Store | unsupported | native | native | native |
 | Multi-Agent | unsupported | unsupported | native | native |
-| Deployment | emulated | native | native | emulated |
+| Deployment | native | native | native | emulated |
 | Session | native | native | native | native |
 
 See [Provider reference](./reference/providers.md) for per-provider configuration and notes.

docs/examples.md

@@ -484,7 +484,7 @@ Deployment 是介于「定义」与「运行」之间的声明式中间层。它
 - **部署层**（Deployment）：声明「用哪个 Agent、带哪些绑定、以什么初始事件和调度运行」。
 - **运行层**（Session）：一次具体的执行实例。
 
-> Provider 差异：Qoder 和 Claude 原生支持 Deployment（对应平台的 deployments API，可服务端调度）；百炼、火山方舟为**模拟**实现——`apply` 只写本地状态（`remote_id` 为 `null`），`agents deployment run` 时展开为一个 Session。详见 [Provider 参考](../reference/providers.zh-CN.md#模拟emulated资源的能力降级)。
+> Provider 差异：百炼、Qoder 和 Claude 原生支持 Deployment（对应平台的 deployments API，可服务端调度）；火山方舟为**模拟**实现——`apply` 只写本地状态（`remote_id` 为 `null`），`agents deployment run` 时展开为一个 Session。百炼上 `user.define_outcome` 事件和 `github_repository` 资源不在部署 payload 内，plan 时会输出警告。详见 [Provider 参考](../reference/providers.zh-CN.md#原生-deployment-的-payload-裁剪)。
 
 ### 定义 Deployment
 

docs/guides/configure-an-agent.zh-CN.md

@@ -26,11 +26,11 @@ providers:
 | Environment, Vault, Skill, Agent, MCP Server, Session | native |
 | Memory Store | unsupported |
 | Multi-Agent | unsupported |
-| Deployment | emulated |
+| Deployment | native |
 
 - Skills upload as a zip via the Files API (two-step).
 - MCP servers are **official managed servers** referenced by `name` (no vault needed for them).
-- `deployment run` expands into a one-shot session; scheduling/outcome rubrics are not enforced server-side.
+- Deployments are native: `apply` creates the remote deployment, `schedule` runs server-side (cron + timezone), and `deployment run` triggers a server-side run. `user.define_outcome` events and `github_repository` resources are not part of the deployment payload and surface a warning on plan.
 
 ## Minimal agent