qol-dev-environmentslisted

# qol-dev-environments ## Establish current truth Do not use this skill as a command database. 1. Locate the relevant repo with `git rev-parse --show-toplevel`. 2. Start from `qol dev` and inspect the Sandbox panel; this is the normal user surface. 3. Read current command grammar from `qol --help`, `qol env --help`, and `qol flow --help` before using lower-level diagnostic surfaces. 4. Run `qol env list` and `qol env doctor` before choosing an environment. 5. Inspect the selected definition under `flows/envs/*.toml` and any local override path printed by `qol env doctor`. 6. Run `qol env runs` and `qol flow runs` before diagnosing leaked or interrupted work. Treat the CLI output, environment definitions, implementation source, and run reports as authoritative. Treat prose examples as shapes only. ## Choose the correct surface | Need | Surface | | --- | --- | | Run the selected environment's declared real workflow | `qol dev` Sandbox panel, then `r` | | Set the next flow's bounded parallelism | `qol dev` Sandbox panel, then `-` or `+` | | Verify and import a matching prepared qcow2 image | `qol dev` Sandbox panel, then `a` | | Run or stop isolated `qol dev` using the active worktree's built artifacts | `qol dev` Sandbox panel, then Enter | | Run one or more artifact-backed development guests directly | `qol env up <environment> --dev-worktree <absolute-worktree>` | | Keep a generic clean guest running without a development payload | `qol env up` without `--dev-worktree`