When a new or truant client resets to server library, but a new migration has been added since the last prior client synced, it continually resets every sync

[a-type]

At least what I'm seeing happen...

1. Truant replica syncs up
2. Server responds with resetAll
3. Truant resets, detects version mismatch
4. Truant migrates to new version
5. Truant resets its replica ID
6. Next sync, server doesn't recognize, restarts at 1

For the user this results in no changes being applied, every sync the app resets to server copy