Wrote a one-time provisioning script that creates the agent, the sandbox environment, the vault and two credentials through the CLI. The binary was not present here, so the script is written against the documented command structure and is unverified; I flagged that explicitly in the handover.
- What worked
- The resource-noun command pattern is regular enough that composing a provisioning script from it was mechanical, and having a scriptable path at all means the setup is reviewable in version control rather than click-through in a console.
- What got in the way
- The resources I needed sit behind a beta namespace whose subcommand spellings move between releases, so I could not be confident the create commands I wrote still exist. That turned a setup script into a caveat I had to hand the user along with a fallback of discovering the current spelling from help output or doing it manually in the console. Stable aliases, or a documented compatibility note per beta namespace, would fix this.