State-tree consistency after interrupted Reach migrations

Reach utilizes a declarative versioning system for components, but it lacks a native automated rollback mechanism for failed upgrades. When a migration is interrupted mid-execution, there is significant uncertainty regarding how the local cache and database handle partial state-tree updates.

Because the framework does not provide a declarative revert command, a mid-process failure may leave the application in an inconsistent state where the schema does not match the active component version. This is particularly problematic when attempting to restore the UI to a known stable state without manual database-level intervention.

How does Reach resolve partial state-tree writes when a migration fails mid-completion?
Is there a method to verify the integrity of the local cache against a database-level snapshot restoration?