setuplisted

# kagura-engineer: setup Thin wrapper around the `kagura-engineer setup` CLI verb. It repairs the environment that `kagura-engineer:doctor` diagnoses. It reimplements nothing — it shells out to the installed CLI and surfaces the result. **Announce:** "Using the kagura-engineer:setup skill to prepare the harness environment." Usage: `kagura-engineer:setup` — no arguments. Add `--fix <step>` to repair one step, `--dry-run` to preview. > Note: `setup` installs/authenticates **tooling**. It does **not** create `repo.yaml` > for you — author that file first (backend choice, workspace/context ids). Setup may > prompt for credentials unless run with `--no-input`. ## Steps 1. **Discover config.** Pass `--config <path>` if `repo.yaml` is not in CWD. 2. **(Optional) Preview.** For a dry run that changes nothing: ```bash kagura-engineer setup --dry-run --json ``` 3. **Run setup:** ```bash kagura-engineer setup --json ``` To repair a single step only, use `--fix <step>` where `<step>` is one of `git`, `claude-code`, `gh`, `ollama`, `ollama-models`, `memory-cloud`. Exit-code contract: `0` = all steps ok/skipped · `1` = any step failed (**takes priority over 2**) · `2` = a step needs user input with no failure (or a config / unknown `--fix` error). 4. **Surface the result.** Print the `ran` / `skipped` / `needs_user` / `failed` groups from the JSON, leading with `failed` and `needs_user`. 5. **Re-check and hand off.** Re-run the diagnosis t