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

Page older history with a composite (ts, id) cursor: composite cursor · case 02

Messages sharing the cursor timestamp are skipped when loading older history.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

messages are [ts, id] pairs in any order; ordering is by (ts, id). cursor is None or the exclusive [ts, id] of the oldest message already shown. A page holds the newest `limit` messages strictly older than the cursor, in ascending order; next is the [ts, id] of the page's oldest item when older messages remain, else None.

Why this case matters

Infinite-scroll history must neither skip nor duplicate messages that share a timestamp.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
siblings share the cursor timestamp	`{"next": null, "page": ["z"]}`	`{"next": null, "page": ["z", "a", "b"]}`	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.