From 36a80c41b336a671ee9fe7611010cd365d00e782 Mon Sep 17 00:00:00 2001
From: Tianyi Cui <53024+tianyicui@users.noreply.github.com>
Date: Mon, 19 Oct 2026 03:35:05 +0800
Subject: [PATCH] test(web): explain the adjacent fork clock pins

---
 apps/web/tests/message-actions.e2e.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/apps/web/tests/message-actions.e2e.ts b/apps/web/tests/message-actions.e2e.ts
index 466393228c..2f96305714 100644
--- a/apps/web/tests/message-actions.e2e.ts
+++ b/apps/web/tests/message-actions.e2e.ts
@@ -212,7 +212,9 @@ describe('web e2e: message IconActions and clocks on settled history', () => {
     await seedSession(scaffold, raw, SEED_ID, undefined, { createdAt: WEB_FIXTURE_TIME - 90_000 })
     browser = await chromium.launch()
     page = await newEnglishPage(browser)
-    // Fork summaries and browser placeholders must rank against the same clock.
+    // Fork summaries use Host time; placeholders use browser time. Each pin
+    // starts at the fixture date, so keep these calls adjacent: setup between
+    // them can create enough clock skew to reverse the fork order.
     hostClock = pinHostClock()
     await pinBrowserClock(page)
     tripwire = watchConsole(page)