FA-76337 / Chat ordering and read receipts / Member archive

Compute a member's visible history and initial read marker: deduplicate · case 02

Duplicated deliveries appear twice in the visible history.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

messages are seqs (duplicates possible). A member sees seqs >= join_seq, or all seqs from 1 when the room shares history with new members; after leaving at leave_seq they see nothing after leave_seq (their own leave event included). The initial read marker is join_seq - 1, so only messages from the join onward are unread. Result {visible (sorted, unique), initial_marker}.

Why this case matters

Membership changes decide which history a user may read and where their unread count starts.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
duplicate deliveries	`{"initial_marker": 6, "visible": [7, 7, 8, 9]}`	`{"initial_marker": 6, "visible": [7, 8, 9]}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.