diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index f0d59cc58..1209ceecb 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "b34ece705f41d2f00a3d55e6a3abc1e2b9035c7c",
-  "syncedAt": "2026-04-25T06:50:08.332Z"
+  "sha": "bb5e278f63bd6d5fcf99e8c4b79190feed43ae46",
+  "syncedAt": "2026-04-25T06:54:09.141Z"
 }
diff --git a/docs/channels/feishu.md b/docs/channels/feishu.md
index ce87a8056..50571935a 100644
--- a/docs/channels/feishu.md
+++ b/docs/channels/feishu.md
@@ -430,6 +430,12 @@ Full configuration: [Gateway configuration](/gateway/configuration)
 - ✅ Thread replies
 - ✅ Media replies stay thread-aware when replying to a thread message
 
+For `groupSessionScope: "group_topic"` and `"group_topic_sender"`, native
+Feishu/Lark topic groups use the event `thread_id` (`omt_*`) as the canonical
+topic session key. Normal group replies that OpenClaw turns into threads keep
+using the reply root message ID (`om_*`) so the first turn and follow-up turn
+stay in the same session.
+
 ---
 
 ## Related