archive-issuelisted

# Archive Issue Once an issue closes, GitHub is the source of truth for its scope — but its requirements, architecture, code-review, and QA docs under `specs/` still hold reasoning worth keeping. This skill retires them out of `specs/` straight into the GitHub wiki. **Nothing archived is ever committed to the main repo** — the wiki is the only place this content lives. This skill resolves everything from the issue number alone via `gh issue view` plus the artifact naming contract (`REQ-<N>-<slug>.md` / `ARCH-<N>-<slug>.md` / `TASKS-<N>-<slug>.md` / `QA-<N>-<slug>.md` / `QA-RESULTS-<N>-<slug>.md` and the `> **Issue:** #N` metadata row) that `plan-requirements`, `plan-architecture`, `generate-tasks`, `plan-qa`, and `execute-qa` write. There is no separate anchor file — GitHub already holds the title, URL, and state. **Declared dependency:** matching review reports to this issue reads the `Target` metadata row defined in `review/report-template.md:8`. If that row's format ever changes, review discovery here breaks — see Step 2's failure behavior for what happens when it does. ## Step 0 — Ensure the local wiki clone is current Work happens in a local working clone of the wiki repo, conventionally at `.wiki/` in the main repo root: - If `.wiki/` doesn't exist: `git clone <repo>.wiki.git .wiki`. If the clone fails because the wiki was never initialized on GitHub, **stop** and tell the developer to create the first wiki page in the GitHub UI (a repo's wiki doesn't exist as