- [ ] **Choose your isolation tool(s).**
→ *Decide per stack and document in `README` → “Virtual Environments”:
**Python:** `venv` (project-local `.venv/`), **uv**, **Poetry**, **Conda** (env per project).
**Node:** `nvm`/`fnm` + `corepack` (npm/pnpm/yarn).
**JVM:** **SDKMAN!** (per-project JDK/Gradle/Maven).*
- [ ] **Question:** How will environments be auto-selected?
→ *Use marker files: `.python-version` (pyenv), `pyproject.toml` (Poetry/uv), `.nvmrc` (Node), `sdkmanrc` (SDKMAN!). Add them to the repo and explain in `/docs/install.md`.*
- [ ] **Create and document the env bootstrap.**
→ *Add `/scripts/setup_env.(sh|ps1)` that creates/activates the env and installs deps. Show example commands in the `README`.*
- [ ] **Project-local envs for Python.**
→ *Prefer a **project-root** `.venv/` (not global). Add IDE notes for interpreter selection in `/docs/install.md`.*
- [ ] **Question:** What is your activation workflow?
→ *Define standard commands for Windows/macOS/Linux (e.g. `source .venv/bin/activate` / `.venv\Scripts\activate`). Add to `README` quick start.*
- [ ] **Never commit environments.**
→ *Ensure `.gitignore` excludes `.venv/`, `.conda/`, `node_modules/` (if applicable), `.gradle/`, etc. Link to your ignore policy.*
- [ ] **IDE integration parity.**
→ *Document how to point VS Code / JetBrains to the chosen env or SDK; include one screenshot per IDE in `/docs/install.md`.*
- [ ] **Question:** How do you update or recreate envs safely?
→ *Write a short description in `/docs/env_maintenance.md` (remove old env, re-create, re-install from lockfile, run tests).*
- [ ] **Optional auto-activation.**
→ *If desired, set up `direnv`/IDE auto-env and document install + trust steps. Mention security considerations.*
- [ ] **Verification issue.**
→ *Open “Virtual Env Verified” issue: each member posts OS, tool (e.g. venv/uv/SDKMAN!), exact version, and output of the quick-start commands.*