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

Decide which messages start a new visual group: previous pointer · case 05

System notices are skipped when tracking the previous message, so the next user message is grouped across the notice.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

messages are ascending {author, ts, kind}. A message shows a header (starts a group) when it is the first message, when it or the previous message is a system message, when the author changes, when more than 300 seconds passed since the previous message, or when the UTC day changes. Result: one boolean per message.

Why this case matters

Compact chat layouts hide repeated avatars; wrong grouping attributes messages to the wrong person or time.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
after a system message	`[true, true, false]`	`[true, true, true]`	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.