For a replica (federated) space, members on the home server and other peers join/leave over time. The home server fans these out so replicas stay current; the client must apply them to the member list live.
What to do
- Handle member join/leave gateway events for federated spaces, inserting/removing remote (qualified) members in the member list controller.
- Reconcile the membership snapshot received at join time with subsequent fanout events (no duplicates, no stale members).
Acceptance
- Joining a federated space shows the current member set; later remote joins/leaves update the list without a reconnect.
Server reference
- Member join/leave fanout: commit
f7366f8 (member join/leave fanout); payloads in src/federation/outbound.rs (member_join_payload/member_leave_payload).
Client touch points
lib/features/member/controllers/accord_members.dart.
Server reference — accordserver branch claude/federated-servers-xlydlj.
For a replica (federated) space, members on the home server and other peers join/leave over time. The home server fans these out so replicas stay current; the client must apply them to the member list live.
What to do
Acceptance
Server reference
f7366f8(member join/leave fanout); payloads insrc/federation/outbound.rs(member_join_payload/member_leave_payload).Client touch points
lib/features/member/controllers/accord_members.dart.Server reference — accordserver branch
claude/federated-servers-xlydlj.