Project Upgrade tool leaves unclear backup state after unexpected termination

The Project Upgrade tool creates an automatic backup of the project folder before applying changes, allowing restoration if the upgrade fails.

When the upgrade process is terminated unexpectedly—for example, by killing the upgrade executable—it is unclear whether the generated backup contains a complete and consistent snapshot of the project, especially regarding engine‑generated intermediate folders and assets that may have been partially processed.

Understanding the exact scope of this backup is essential for deciding whether a simple restore is sufficient or whether additional manual steps are required to recover a working project.

Which specific directories and files are guaranteed to be present in the backup created by the Project Upgrade tool?

Does restoring the backup require manual deletion or regeneration of intermediate folders such as Saved, Intermediate, or Build?

Are engine‑generated assets that were partially processed during the failed upgrade safely omitted or must they be cleaned up manually?