What happens. When the stream draws an account for the first time, the index puts the stream's record in its history, then rereads the repository and appends the older records in the order the listing returns them, newest first. Nothing sorts the history afterwards. history_of is documented as oldest first, and the badge, share page and agent detail take its last entry as the newest. On both the index and the query mirror the account's history ends up [new, yesterday 10:00, yesterday 09:00].
How to reproduce. worker.rs:520-541 calls see_scrobble with the stream record and then reread. reread (relay.rs:463-470) feeds the listing in order through read_back, which is see_scrobble, and see_scrobble pushes onto the end (view.rs:1650). The mirror applies the same events in the same order (view.rs:2035). Only snapshots are sorted. The readers that assume order are badge.rs:192 (the live count and ?repo= check use .last()), badge.rs:214 and 225 (tall badge lines), share.rs:172-180 (share page lines) and read.rs:389-390 (agent detail, reversed as newest first). A local test calling see_scrobble with a 2026-10-22T12:00 line and then 2026-10-21T10:00 and 09:00 lines left history_of(..).last() at 09:00.
Why it matters. This happens on every first draw: a new agent, one let go for room, or one back after a pause, and to non-didbot accounts as much as didbot's. Until the query reseeds, such an agent counts as not live on its badge, and its tall badge and share page list yesterday's lines without the one it just wrote.
Fixed on main by https://tangled.org/permadeath.com/vibescrobble.com/pulls/340 (8fe13b46): history is kept oldest first however a record arrives.