Decision A is now strict. Records saved by builds before the list go out
in main's order and batching, with nothing new merged into, replacing or
riding along with them. A side change of a page whose slot holds one
waits as its own record in the list, which waits until they drain. The
rename that went ahead of them, and the renames-first order inside their
batch, are gone, and successors promote as on main.

An add answered "no change" no longer moves the changes behind it on: an
add sent again after its op record expired gets the strategy's revision
now, which may be a teammate's.

Also: Use cloud and Discard flush the work they held back; a waiting
delete of the page on screen moves to a page that can open; a page drawn
after this device's rename carries the revision it landed at; a page
change goes only after the work made before it (an add copies its source
page with the edit made just before "+"); and record times always move
forward, so that order survives a coarse clock.

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