setup-repolisted

# Configure a repository for the lifecycle skills `create-issue`, `implement-issue`, `merge-pr` and `auto-dev` are generic workflows wrapped around a thin layer of repo-specific facts. `profile-repo` records those facts — and when it finds none, its only outlet is a `TODO:` line. That is the right answer for a fact it cannot read and the wrong one for a **configuration the repo does not have**, which is what four of its TODOs always are: | What the profile reports | What it actually means | What silently degrades | |---|---|---| | no `priority:` axis | the labels were never created | `create-issue` omits the axis | | no `effort:` axis | the labels were never created | `auto-dev`'s "small first, then medium" ordering has nothing to sort on | | no `area:` axis | the labels were never created | `auto-dev` cannot give parallel workers non-overlapping areas | | no `.github/ISSUE_TEMPLATE/` | the directory was never created | `create-issue` has no form to obey | This skill is the missing verb. It does not describe a repo; it makes one. The same manifest also carries the four surfaces a **public** repository is judged by before anyone opens a file (#400): `settings.description`, `settings.homepage`, `topics:` and `pages:`. The description and homepage ride the settings PATCH; topics are one `PUT` that replaces the whole set, so `apply` writes the union of live and declared; the Pages source is one `POST` to create the site or one `PUT` to update it — never a `DELETE`. ## Do thi