bailian-managed-agent

Bailian managed agent IaC (bl managed-agent)

CRITICAL — Before executing, MUST read the shared protocol in ../bailian-protocol/SKILL.md: Version & updates (pre-flight checklist) and CLI errors: report an issue. Command details are authoritative in reference/managed-agent.md and bl managed-agent --help — do not guess flags. If that protocol file is missing, stop and run bl skill init; do not guess auth/consent.

Safety guardrail (the most important rule)

apply / destroy mutate remote resources and only execute when --yes is passed:

1. Always run bl managed-agent plan first and show the diff to the user.
2. Only after explicit user confirmation, retry apply / destroy with --yes.
3. Never add --yes on your own initiative before the user has confirmed.

IaC lifecycle

1. Init      bl managed-agent init          # scaffold agents.yaml
2. Validate  bl managed-agent validate      # offline, no network calls
3. Preview   bl managed-agent plan          # show the pending change diff
4. Apply     bl managed-agent apply --yes   # only after user confirmation
5. Destroy   bl managed-agent destroy --yes # only after user confirmation

Deployment as IaC

Deployment 与 Agent 一样声明在 agents.yaml 中，并复用同一条 validate → plan → apply → destroy IaC 链路； CLI 不提供绕过 state 的命令式 Deployment CRUD。最小配置：

deployments:
  daily-report:
    agent: assistant
    initial_events:
      - type: user.message
        content: "Generate today's report."

• apply 会在百炼创建原生 Deployment；destroy 会归档已跟踪的远端 Deployment。
• schedule 会在 apply 后由百炼服务端执行。若旧流程已有外部 cron / CI，先检查 plan，避免重复触发。
• initial_events 至少包含一个 user.message 或 system.message；user.define_outcome 在百炼会被丢弃并产生诊断。
• 本地文件资源在 apply 时上传，mount_path 必须位于 /mnt，且归一化后不能重复。
• 旧版模拟 Deployment 的 state 可能记录空 remote_id；升级后 plan 会显示 materialize 更新，确认后再 apply。

Session interaction (chat with a deployed managed agent)