F.13:14 - Migration notes (conceptual playbook)

1. Recover the same meaning and use first. Distinguish the expression from its exact cell and governed value. Use renames only for unchanged meaning and use; recover any subject change before settling the later name.
2. Keep aliases local. Different semantic projections open F.9 only for a needed correspondence; the difference itself establishes no Bridge.
3. Prefer clarity over fashion. Rename only when the new label removes a real ambiguity (F.5 criteria), not to chase style.
4. Limit nostalgia. Admit one legacy alias in each register that readers will most likely meet; leave the rest to footnotes in examples.
5. Keep historical reading clear. For a rename, point from the legacy label to its preferred successor. For retirement without a single successor, point to the relevant meanings or rows.
6. Rows before names. If a rename request coincides with a shift in what the row covers, refactor rows (F.7) first, then choose labels.
7. Edition changes. Compare the affected definitions. If meaning changes, recover the subject-governed revision, replacement, split, merge or retirement and preserve the earlier claim. If meaning and use stay unchanged, rename only for a concrete recognition gain.
8. Teach the delta. In primers, show a mini table with legacy → preferred pairs only where readers will encounter both.