Rollback is not a note added after configuration. Before launch, record the current versions, files that will change, generated artifacts, tool permissions, and the smoke test for the previous state. Prefer additive configuration and versioned output over in-place edits. A failed upgrade should have one clear stop condition and a tested route back. This discipline also makes support cheaper: the customer and operator can compare states without guessing which hidden change caused the problem.