Does the reach feature support transactionally safe rollback after a schema change?

Goal: Verify whether the reach feature can safely roll back a schema change after it has been applied, ensuring that the database returns to its prior state without data loss or inconsistency.

Uncertainty: The available research does not contain specific documentation for reach regarding transactional DDL support, savepoints, or versioned snapshots that would guarantee reversible schema modifications. General patterns suggest that safe rollback depends on such mechanisms, but it is unclear if reach implements them, requires explicit configuration, or lacks this capability altogether.

Specific questions: Does reach execute schema‑altering statements within a transaction that can be rolled back? Does it provide versioned snapshots or generate reversible migration scripts? Are there any configuration options or known limitations that affect the safety of rollback after a schema change?