Bailian managed agent IaC (bl managed-agent)

CRITICAL — Before executing, MUST read the shared protocol in ../bailian-protocol/SKILL.md: High-risk operation confirmation, Version & updates (pre-flight checklist), Call attribution (every Agent bl command), and CLI errors: report an issue. Command details are authoritative in reference/managed-agent.md and bl managed-agent --help — do not guess flags. Examples in reference/ stay bare; wrap with Call attribution when running. If that protocol file is missing, stop and run bl skill init; do not guess auth/consent.

Call attribution: Examples below and in reference/ stay bare bl …. When running a command, wrap it with bailian-protocol → Call attribution (bash or PowerShell). One sample for this skill (BAILIAN_SKILL_NAME=bailian-managed-agent; replace codex with this host). When copying commands into a reusable script / template / task definition (including project scripts), switch to the protocol script template (never keep agent); the sample below is for this-turn inline execution only. Strip attribution when handing a command to the user to paste.

BAILIAN_CALLER_TYPE=agent BAILIAN_CALLER_NAME=codex BAILIAN_SKILL_NAME=bailian-managed-agent BAILIAN_SKILL_VERSION=<metadata.version> bl managed-agent plan

Safety guardrail (the most important rule)

apply / destroy and single-resource create --yes mutate persistent remote resources:

1. For agents.yaml resource changes, always run bl managed-agent plan first and show the diff to the user.
2. A single-resource create command previews its scoped plan when --yes is absent; show that preview before retrying it with --yes.
3. Only after explicit user confirmation, retry apply / destroy / single-resource create with --yes.
4. Never add --yes on your own initiative before the user has confirmed.