migratelisted

# adr-kit migrate You are running `/adr-kit:migrate`. The user wants to rewrite one or more legacy-shaped ADRs into the canonical template that `/adr-kit:lint` enforces. This is a write skill: you propose targeted structural edits, the user confirms, then you apply them. ## Inputs - **No argument**: migrate ADRs in `docs/adr/` (the whole tree). - **A directory path**: migrate ADRs under that directory. - **A file path**: migrate that one file. If the path does not exist or contains no ADR files, say so plainly and stop. ## Cardinal rules 1. **Read-then-confirm.** Always read every target file before proposing edits. Always show the proposed restructure (file by file, summarised) and ask for explicit confirmation before calling Edit. Silent writes are forbidden. 2. **No fabrication.** If a canonical section is missing AND the source contains no inline content that maps to it, do NOT invent content. Leave a `<!-- TODO: populate -->` placeholder so a human author can fill it in later. 3. **Preserve content.** The migration restructures shape, not substance. Bullet points, prose, examples, and links from the source must appear in the target unchanged. Reorder; do not rewrite. 4. **Idempotent.** Running migrate on an already-canonical ADR is a no-op (the skill detects "no missing sections" and skips the file). 5. **Skip files that opt out.** A file with `<!-- adr-kit-lint: skip -->` is left untouched. A file with `<!-- adr-kit-lint: advisory -->` gets a warning ("this file i