setup-vexalisted

# Set Up Vexa for a Project ## Overview Drive `bootstrap.py` to turn a fresh Vexa clone into a ready-to-code repo configured for the user's app — so the only manual step they're left with is pasting their password into `.env`. Everything else is automated. Read `bootstrap.py`'s docstring for exactly what it does. Your job is to gather the inputs, run it non-interactively, and confirm the result. ## Password safety (non-negotiable) **You must never collect, type, or write the user's password.** Handling passwords in plaintext is prohibited. So: - Gather everything EXCEPT the password. - Run `bootstrap.py` with `--no-password` so it never prompts for or writes one. - After it finishes, tell the user to add the single line `QA_PASSWORD=...` to `.env` themselves. If the user pastes a password to you anyway, do not put it into any file or command — remind them to add it to `.env` directly. ## Workflow Track these as todos; do them in order. ### 1. Confirm the starting point - Confirm the user is in a **fresh clone** meant to become their project (not the Vexa framework repo itself). `bootstrap.py` refuses the git reset if `origin` is the Vexa upstream, but check anyway. - Confirm they have `uv` installed (`uv --version`). If not, point them at https://github.com/astral-sh/uv and stop. ### 2. Gather inputs (ask the user) Use a single grouped question (AskUserQuestion) or a short exchange. Collect: - **project_name** (default: folder name) and **author** (defau