Project file is corrupted: Unresolved need for automatic schema migration in Premiere Pro

Problem Context

When Premiere Pro attempts to load an XML project file that fails its schema validation, the Project Manager displays the dialog "Project file is corrupted". The error originates during the parsing phase before the project tree is built.

Current Constraints

• There is no documented rollback mechanism for project files after an internal schema change.
• Newer versions of Premiere Pro cannot open older project files that use deprecated XML elements.
• Recovery via File > Open Project > Recover only skips malformed sections and rebuilds a new project file, but does not address schema evolution.

Unresolved Decision

Adobe has not announced whether it will provide an automatic schema migration tool that safely converts legacy project files to the current schema without data loss.

Specific Questions

1. What criteria would determine when an automatic migration should be offered to the user?
2. How would Adobe ensure that all project metadata, including custom XML tags, survive a schema upgrade?
3. Would a migration tool be integrated into the existing Recovery workflow or presented as a separate feature?