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

Order the conversation list by pins and activity: silent events · case 05

A conversation jumps to the top because someone changed its avatar or topic.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

convs {id, pinned (rank or None), last_msg, last_silent, draft_ts (or None)}. Pinned conversations come first by pin rank (rank 0 is a valid pin). The rest are ordered by activity descending, then id ascending, where activity is the later of the last real message and the local draft; silent events (avatar or topic changes) never count.

Why this case matters

The conversation list is the entry point of a chat app; wrong ordering buries active conversations.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
silent topic change	`["a", "b"]`	`["b", "a"]`	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.