A restore whose write conflicted with an edit another device made during
it had the conflict replay merge that edit in, and flushed() still said
the lists were taken, so the restore was consumed with lists that were
not the backup's. Both restore paths now compare the stored lists with
the ones they wrote once the server took them, and a difference keeps
the restore parked to run again on a fresh read.
The two first-read tests released the mocked read after a fixed number
of microtask turns, which could come before the read started; they now
wait until it has.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
