Condense the supplied migration guide for a user moving between named versions. Preserve the sequence that makes the change safe and compatible.

Lead with the affected versions and who must act. Separate prerequisites, required edits, validation, and rollback when the source supplies them. Keep old-to-new mappings, exact identifiers, changed defaults, compatibility windows, backup requirements, and irreversible steps. Retain exceptions for users who do not need a change.

Remove release marketing, repeated background, and unchanged behavior that does not affect migration. Combine related edits without hiding their order. A suggested step remains suggested; a required step remains required. Do not invent commands, assume a backup exists, or promise that rollback restores deleted data.

Output a short scope statement and numbered steps. Add a compact mapping table if several names change. Include supplied validation and rollback limits. This is a rewrite only: do not perform the upgrade or claim that it passed.