fix(mobile): load earlier edits to thread replies when a thread opens - #8870

Summary

In the mobile thread view, if a reply was edited before you opened the thread, the reply showed its original text and no "(edited)" marker. An edit that arrived while the thread was open worked.

The thread /query asked only for message kinds. The channel window carries edits, reactions and deletions (aux events) only for top-level messages, so an earlier edit to a reply was in neither result. The thread query now sends include_aux: true, as desktop does (buzz-app src/features/relay/threads.ts). The relay already supports this on the depth_limit thread route: it returns the aux events for the root and every reply, plus deletions of those (crates/buzz-relay/src/api/bridge.rs, bridge_thread_aux). A relay that ignores the flag gives the same result as before.

The relay sends a page's rows (at most 200 reply-marked events, of any kind) before that page's aux events. It also repeats the root's aux on every page. So fetchCompleteThread treats the leading run of events reply-marked into this thread, other than reactions and NIP-09 deletions, as the page's rows. Only rows count toward a page, move the cursor and feed the reply cache. A reply-marked huddle event still fills a page, and a reply-marked reaction never becomes a reply. A reply-marked edit of the root in the repeated aux can follow a short final page's rows and look like a full page, so the scan also stops when the next cursor does not advance. The thread-summary scan (fetchCompleteThreadReplies) still asks for replies only and pages exactly as on main.

Related issue

Found during the emulator testing of #8863.

Testing

• just mobile-check, just file-size-check and just mobile-test pass.
• thread_replies_provider_test.dart adds two tests. The first checks that the query sends include_aux and that an edit made before the thread opens folds into its reply. The second covers pagination: a reply-marked huddle row filling a page, a reply-marked edit that is a row on one page and aux on the others, a reply-marked reaction that stays aux, 200 reply-marked reactions after 199 replies (one query), 200 reply-marked root edits after a short final page (the progress guard ends the scan), an edit reply-marked into another thread that stays aux, and that the summary scan doesn't send include_aux. It fails if any of these is removed: the reaction/deletion exclusion, the root check, the 200 cap, the progress guard, or the separate row and aux id sets.
• channel_detail_page_test.dart adds a journey: it opens ThreadDetailPage with the real thread query and a fake relay session that sends the reply's earlier edit only when include_aux is set. It checks the edited text, that the original text is gone, and the marker. It fails when the flag is removed or when the provider drops aux.
• Android emulator (AVD, debug build) against a local relay. Morty posts "Who can review the release notes?", Demo User replies "I can, after lunhc" and then edits the reply to "I can, after lunch", all before the thread is opened. These shots come from the first revision of this branch. The pagination changes after it give the same result for a one-page thread like this one.

Before (unfixed: the #8863 build)	After (this branch)	Live edit while the thread is open

Before, the thread shows the original reply text with no marker. After, it shows the edited text and "(edited)". A live edit still lands.

🤖 Generated with Claude Code