What?

Fixes collaborative editing notes (block comments) not syncing between editors. When User A adds a note to a block, User B never sees it until they refresh the page.

Why?

PR #76704 introduced the isPrimaryRoom concept to the HTTP polling manager to optimise collaborator detection — only the primary room (the post entity) is checked for awareness to avoid false positives from shared collection rooms like taxonomy/category.

However, the change accidentally restricted updateQueue.resume() to only the primary room's queue. Non-primary rooms — such as the root/comment collection room used for notes — had their update queues permanently paused. Since a paused queue's get() returns [], CRDT save events from markEntityAsSaved() were never sent to the server, and notes never synced between editors.

How?

When collaborators are detected on the primary room, resume all room queues instead of just the primary room's queue. This preserves the optimisation of only checking the primary room for collaborator awareness while ensuring collection rooms can also send their updates.

The fix (packages/sync/src/providers/http-polling/polling-manager.ts):

 if (
     roomState.isPrimaryRoom &&
     Object.keys( room.awareness ).length > 1
 ) {
     hasCollaborators = true;
-    roomState.updateQueue.resume();
+    roomStates.forEach( ( state ) => {
+        state.updateQueue.resume();
+    } );
 }

Testing Instructions

1. Enable real-time collaboration in Settings → Writing.
2. Create or open a draft post in two different browser sessions (two different users).
3. Wait for both users to see each other's presence avatars.
4. In User A's editor, insert a paragraph block.
5. Select the paragraph block, open the block options menu (⋮), and click Add note.
6. Type a note and click Add note.
7. In User B's editor, click the All notes button in the top bar.
8. Expected: User B sees the note from User A within a few seconds.
9. Repeat in the other direction — User B adds a note, verify User A sees it.