career-migratelisted

# career-migrate **Run this instead of `/career-init` when the user already has a wiki, an export, or a folder of career material.** `/career-init` interviews from zero and scaffolds templates — on a populated vault it writes over pages that already exist and asks an hour of questions already answered. **`tools/migrate.py` does the mechanical half. This skill is the judgement it deliberately refuses to make**, and every step below comes from a real migration of 166 files, not from imagining one. ## 0. Before anything: what should not come at all **Ask what else lives in that folder.** A vault directory usually accumulates things that are not the vault — a side project, a client folder, a downloads dump. **The first real migration carried 118 files of an unrelated software project** into the drop zone, where they sat looking like unclassified career material. 🔴 **Have them copy it out first, not after.** Sorting around it wastes the report. ## 1. Report first. Do not apply. ```bash python3 tools/migrate.py ``` **Read the verdicts to the user before anything moves.** They know what their files are and you do not; this is the one moment where a wrong guess is cheap to correct. **Then apply, then repair links — in that order, every time:** ```bash python3 tools/migrate.py --apply python3 tools/wikilinks.py --fix ``` ## 2. The four kinds of leftover, and what each one means **Everything the sorter would not file is still in `migration/`, on purpose.** 🔴 **Name every