[markmnl]

Problem

GET /fmsg ordered the inbox by message id. When someone adds an identity to an older message, it stays at its original position, far below newer messages. A client reading the latest page, whether a person or an agent checking for new mail, never sees it.

Change

The inbox is now ordered by when each message arrived for that identity:

• the message's time_sent, where the identity is in msg_to;
• the time_added of any add-to batch that added the identity;
• whichever of these is latest.

Ties fall back to id descending.

• Adding someone else doesn't move the message for its other recipients.
• Visibility, the trash filter and the response shape are unchanged. Only the order changes.
• The query collects arrivals from msg_to and msg_add_to/msg_add_to_batch for the identity first (both use the existing lower(addr) indexes), then joins msg.
• The README's GET /fmsg section describes the new order.

Tests

TestListOrdersByArrival covers:

• a message aged an hour, plus newer ones;
• after the add-to, the added recipient sees that message first, including across limit/offset pages;
• the original recipient's order doesn't change.

It fails on main and passes with the change. The full go test ./... passes against Postgres 17 with fmsgd's dd.sql.

🤖 Generated with Claude Code