setup-aliases

# setup-aliases State-aware orchestration for VibeProxy aliases. This skill owns exactly two surfaces: 1. the `vibeproxy-kit` managed block in `~/.zshrc` 2. the `oauth-model-alias` entries in `~/.cli-proxy-api/config.yaml` that it created Everything else — unrelated YAML keys, unrelated shell aliases, user-authored alias entries — is preserved. The skill coordinates discovery, a guided per-backend probe cycle, writes, a VibeProxy restart gate, live validation, and transactional rollback on failure. All five scripts in `${CLAUDE_PLUGIN_ROOT}/skills/setup-aliases/scripts/` emit JSON to stdout. Your job is to chain them together, surface decisions to the user via `AskUserQuestion`, and persist state to `${CLAUDE_PLUGIN_DATA}/config.json` before any write. ## Phase 1 — Discover Run the read-only inspector and parse its JSON: ```bash bash ${CLAUDE_PLUGIN_ROOT}/skills/setup-aliases/scripts/discover.sh > /tmp/vibeproxy_discover.json ``` Then read `/tmp/vibeproxy_discover.json`. Key fields: - `vibeproxy_installed`, `vibeproxy_reachable` — see **Onboarding gates** below if either is false - `user_overlay_exists`, `state_file_present` — determines whether we are first-run or rerun - `authenticated_backends` — array of `{token, config_key, display_name, auth_files}`; see **Onboarding gates** below if empty or missing backends the user wants - `claude_code_channel` — `{connected, account_count}`; see **Claude Code channel note** below - `managed_shell_aliases`, `managed_model_al...