orca-per-workspace-env

# Per-Workspace Environments This file is a discovery stub, not the usage guide. The full, version-matched per-workspace environment reference is served by the `orca` binary itself — kept out of this file on purpose so it can never drift from the binary that will actually run your commands. Engage Orca whenever you set up, review, debug, or validate a per-workspace environment recipe — the on-demand, disposable runtimes (cloud sandboxes, VMs, or local) created fresh for each workspace. This covers first-time setup (provider prerequisites, the reusable base snapshot, the coding-agent auth snapshot, credentials, and state), not just the per-workspace lifecycle scripts. Use it to stand up per-workspace environments, fix an `environmentRecipes` entry in `orca.yaml`, scaffold provider lifecycle scripts, or resolve an `orca vm recipe doctor` failure. Orca is a thin wrapper: you guide, detect, and scaffold; you never own the user's cloud account, billing, images, or credentials, and never spend money without an explicit user OK. ## Resolve the CLI for this session Choose the executable once and reuse it for every later command: - If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`. - Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare `orca` there — outside Orca's terminals it normally resolv...