github-setuplisted

# GitHub setup Scaffold a fresh or under-scaffolded repository with declarative labels, a main-branch ruleset pinned to one aggregate check, issue forms, a PR template, a work-item runbook and a Project board. The target project's runbook owns mechanics after setup. ## User gate first Before any GitHub write or enforcement, the user approves a plan naming the target, exact scaffold diff and Project board. Name destructive steps: ruleset enforcement and label pruning via `skip-delete: false`. Ask for an unnamed target; never infer it from the working directory. ## Steps 1. **Labels**: copy [`templates/labels.yml`](templates/labels.yml) to `.github/labels.yml` and [`templates/workflows-labels.yml`](templates/workflows-labels.yml) to `.github/workflows/labels.yml`; sync runs on the next push to `main`. Warn: pruning is on, so labels missing from the file are deleted. 2. **Ruleset**: add a `ci-status` aggregate job (template: [`templates/ci-status-aggregate.yml`](templates/ci-status-aggregate.yml)) to the project's CI, then create the branch ruleset pinning that one check. Commands and the `integration_id` rationale: [references/ruleset-and-ci.md](references/ruleset-and-ci.md). 3. **Issue forms and security route**: before adding the issue-form contact link, copy [`templates/SECURITY.md`](templates/SECURITY.md) to the repository root, or verify that an existing `SECURITY.md` provides a valid private route. Then copy `templates/ISSUE_TEMPLATE/