From d063223ad3a342ad436b07a847033a451c5b74b5 Mon Sep 17 00:00:00 2001
From: Larry
 <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
Date: Mon, 28 Sep 2026 16:07:11 -0400
Subject: [PATCH] test(desktop): wait for channel head refresh before paging
 thread summary test

The thread summary prepend test scrolled back before the live
subscription's head refresh. That refresh replaces the channel window,
so on slower CI runners it could drop the older page just fetched and
leave the reader stuck at the top. Use waitForMockChannelHeadReady like
the sibling pagination tests.

Signed-off-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz>
---
 desktop/tests/e2e/scroll-history.spec.ts | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/desktop/tests/e2e/scroll-history.spec.ts b/desktop/tests/e2e/scroll-history.spec.ts
index 27bf08b731f..5313bdaf727 100644
--- a/desktop/tests/e2e/scroll-history.spec.ts
+++ b/desktop/tests/e2e/scroll-history.spec.ts
@@ -2172,6 +2172,13 @@ test("thread summary badge survives a retained older-history prepend", async ({
 
   await page.getByTestId("channel-deep-history").click();
   await expect(page.getByTestId("chat-title")).toHaveText("deep-history");
+  // Page only after live admission and its head refresh. That refresh
+  // replaces the window, so an earlier prepend can be discarded.
+  await waitForMockChannelHeadReady(
+    page,
+    "deep-history",
+    "feedf00d-0000-4000-8000-000000000007",
+  );
   const timeline = page.getByTestId("message-timeline");
   const badgeSelector =
     '[data-testid="message-thread-summary"][data-thread-head-id="mock-deep-history-599"]';