Replication unable to continue after termination between rev and ack

Discussion on the linked CBSE but the gist is that if CBL sends a rev to the remote, and then the replication gets terminate (possibly by killing the app) then it will not receive the rev ACK and therefore not update its remote ancestor.  However, SG will have updated its current revision and therefore CBL and SG are now technically in conflict.  A pull should fix this, but in push only it is impossible.