setuplisted

# setup — first-run profile bootstrap Generate or repair `milestone-driver.json` through a guided, inference-first flow. Every key is presented with a plain-language description and a detected default. Optional keys state their skip-consequence. No blank prompts — if a default cannot be inferred, an example is shown. **After writing the file, return control to the caller** (solve-issue or solve-milestone) so the original task continues immediately. The user does not need to re-run the command. ## When this runs - **Auto-invoked** by `solve-issue`/`solve-milestone` when `milestone-driver.json` is absent or missing a required Core key (`integrationBranch`, `protectedBranch`, or `sourceGlobs`). - **Direct invocation** (`/milestone-driver:setup`) when onboarding a new repo or repairing an existing profile. ## Procedure ### Phase 1 — Silent project-evaluation pass Before asking anything, gather signals from the repo. Run these checks silently (no output to the user yet): | Signal | Command / check | |---|---| | Repo default branch | `git symbolic-ref refs/remotes/origin/HEAD` → strip `refs/remotes/origin/`; fall back to `gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'` | | Integration-branch candidates | `git branch -a` — look for `develop`, `dev`, `development`, `integration` | | Repo layout | List top-level dirs + key files: `package.json`, `*.sln`, `*.csproj`, `Makefile`, `pyproject.toml`, `Cargo.toml` | | Unit test command | `package.json` → `.script