A strategy change this device sent is drawn from the outbox until its
answer arrives, but nothing kept it drawn after that. A read of the
strategy older than the answer (a page reloaded while the read after the
last batch was still on its way) then drew the map and theme from before
it, and the next save wrote them back: change the map twice and add a
page, and the first map came back on the server.

The queue now remembers this device's newest strategy change that landed,
and the revision it landed at. A read older than that revision is drawn,
compared and written against that change, as #324 does for items. A read
at or past it shows the server as it is, a teammate's later change
included.

Also checks a lineup set back offline behind an edit being sent on a
server that merges by field: it keeps the first edit's value as its base.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>