vac-deploylisted

# VAC Deploy Deploy the agent directly to ElevenLabs. Store artifacts in GitHub. Output: `deployment-log.md`. **HARD RULE: Deployment goes straight against the ElevenLabs API (EU Residency). The VAC Service is NOT used.** ## Prerequisites (input check) Before starting, check that these files are present in the agent directory (`../voice-agents/<agent>/`): | File | Comes from | Missing? | |---|---|---| | `prompt.md` (approved) | `vac-prompt` (step 4) | Run `vac-prompt` first | | `config.json` (approved) | `vac-prompt` (step 4) | Run `vac-prompt` first | | `example-variables.md` | `vac-prompt` (step 4) | Run `vac-prompt` first | | `review-log.md` (PASS) | `vac-review` (step 5) | Run `vac-review` through to PASS; do not deploy without a PASS | | `knowledge-base.md` | `vac-knowledge-base` (step 3b) | KB agents only; run `vac-knowledge-base` first | If an input is missing, do NOT improvise and do NOT carry on with placeholders: name the missing predecessor step and ask the requester whether it should be done now. ## Process 1. Read approved `prompt.md`, `config.json`, `example-variables.md` 2. Select voice (if not already selected) 3. **Determine the use case** (`outbound` | `inbound`) — this drives the settings overlay. **Transfer target agents** (handed over via `transfer_to_agent`, no dialer of their own) fit neither overlay cleanly: no voicemail (never hits an answering machine), first_message is set (not empty), no custom variables. Workaround: pick `outbound`; the bu