Does detaspace guarantee automatic rollback after a breaking schema change

Detaspace is described as a framework for managing versioned data spaces with basic schema versioning support.

Public documentation on schema evolution mechanisms is sparse, and there is no clear consensus on whether a breaking schema change can be automatically reverted by the system or whether rollback safety must be provided by the application. Community discussion suggests manual compensation may be required, leaving the built-in safety guarantees unclear.

The design decision about automatic revert versus application-managed rollback remains unresolved in available references.

Does detaspace provide automatic rollback of a schema change when validation fails? Which conditions, if any, trigger an automatic revert versus leaving the data space in a partially migrated state? What is the documented contract for rollback safety across schema versions?