infra-setup

1# Infra Setup
2 
3Use this when the user wants to change where experiments run: local worktrees, pool slots, or a remote provider such as Modal, E2B, Daytona, AWS, Azure, SSH, manual, or a custom dotted-path provider.
4 
5## Goals
6 
7- Be explicit about the target backend/provider.
8- Check prerequisites before mutating evo config.
9- Never install provider SDKs silently.
10- Give one actionable auth command per provider.
11- Keep provider credentials separate from benchmark runtime env.
12 
13## Flow
14 
151. Identify the target:
16   - `worktree` or `pool` means local backends.
17   - `modal`, `e2b`, `ssh:...`, or another remote spec means `backend=remote`.
182. If the target is remote, parse the provider choice the same way evo CLI does:
19- `modal`
20- `e2b`
21- `daytona`
22- `aws`
23- `azure`
24- `manual`
25- `ssh:user@host[:port]`
26   - another built-in provider name
27   - dotted import path for a custom provider
283. Check whether `evo` is on PATH and whether it is the expected `evo-hq-cli` package (`evo --version`). If the provider SDK is missing, evo's provider loader prints the provider-specific extra or SDK package to install; use that message rather than guessing.
294. For SDK-backed providers, verify the SDK import only when you can run the check in the same environment that owns the `evo` executable. If missing, ask the user before installing it.
30   - If `evo` was installed with `uv tool` or `pip`/`venv`, prefer the matching extra on `evo-hq-cli`:
31…