[Design] Should a DB rollback also delete/restore the remote files?

During the creation/update/deletion of a local file, the remote file is also changed.

However, when an error happens during such an operation, a database rollback happens, which restores the previous state of the local file. Yet, the remote file is not restored to its previous state.

Because of the absence of remote rollback, the remote file will be seen as new (because of its modification time, newer than both local mtime and last sync dt), and will overwrite the local file on the next sync.