setup-repolisted

# Setup ## User gate first Before any write, user approves a plan naming the target, exact keep/create/adapt/conflict diff and, for GitHub, the Project board. Confirm permission; if the target is unnamed, ask instead of inferring it from cwd. ## Inspect and classify Read the target's `Repository process` declaration first, then inventory `MAINTAINING.md`, docs layout, `.github/**`, the work-item runbook and board. Classify each action as **keep (exact match)**, **create (absent)**, **adapt (compatible; propose the merge)** or **conflict (semantic mismatch; STOP and ask)**. Never overwrite; amend the declarations block per heading. A re-run against an already-set-up repository must produce no diff. ## Choose tracker Ask: **Use GitHub issues?** If yes, use the GitHub branch, confirming the remote host before any `gh` command. If no, record the chosen tracker or `none`; skip labels, ruleset, issue forms and board. Tracker-specific setup remains out of scope; document the skip. ## Declare repository process Amend or create the **Repository process** block in `MAINTAINING.md` from [`templates/repo-declarations.md`](templates/repo-declarations.md). Record the tracker choice, canonical **scope and stories** home (`issue-tracker` or `project-docs`), workflow-state owner (`tracker` or `project-docs`) and pointer, docs-layout homes, merge policy/authority and work-item runbook pointer. Use pointers only; never duplicate runbook or policy content. With `issue-tracker`, the paren