diff --git a/DOC/bugs.json b/DOC/bugs.json
index c92f66783..94508f15c 100644
--- a/DOC/bugs.json
+++ b/DOC/bugs.json
@@ -1,5 +1,5 @@
 {
-  "nextId": 400,
+  "nextId": 401,
   "bugs": [
     {
       "id": 2,
@@ -4102,6 +4102,17 @@
       "longTerm": false,
       "createdAt": 1782653812569,
       "updatedAt": 1782653812569
+    },
+    {
+      "id": 400,
+      "title": "有帝国陨落的时候，单位死亡后周围的单位的高亮状态没有刷新",
+      "description": "",
+      "status": "open",
+      "priority": "medium",
+      "module": "",
+      "longTerm": false,
+      "createdAt": 1782725473077,
+      "updatedAt": 1782725473077
     }
   ]
 }
\ No newline at end of file
diff --git a/Tools/Dashboard/data/community_monitor/tohotopia_monitor.sqlite3 b/Tools/Dashboard/data/community_monitor/tohotopia_monitor.sqlite3
index 9cf061e0b..de93a13c2 100644
Binary files a/Tools/Dashboard/data/community_monitor/tohotopia_monitor.sqlite3 and b/Tools/Dashboard/data/community_monitor/tohotopia_monitor.sqlite3 differ
diff --git a/tmp/QQ_NapCat_QCE_HANDOFF_20260629.md b/tmp/QQ_NapCat_QCE_HANDOFF_20260629.md
new file mode 100644
index 000000000..ee0e2b6ed
--- /dev/null
+++ b/tmp/QQ_NapCat_QCE_HANDOFF_20260629.md
@@ -0,0 +1,93 @@
+# QQ / NapCat / QQ Chat Exporter Handoff
+
+Date: 2026-06-29
+
+## Goal
+
+Run the user's normal QQ account and a separate bot QQ account without mixing sessions. Use the bot QQ account to export all accessible QQ group chat records, and optionally connect AI-assisted group replies with strict manual approval or safeguards.
+
+## Local Findings On Source PC
+
+- Main tool directory:
+  `D:\TH1_本地目录\Q群每日\聊天记录\Tools\NapCat-QCE-Windows-x64-v5.5.64\NapCat-QCE-Windows-x64`
+- Full mode launcher:
+  `launcher-user.bat`
+- Standalone browser-only mode:
+  `start-standalone.bat`
+- Saved QQNT executable path:
+  `D:\Program Files\Tencent\QQNT\QQ.exe`
+- QQ Chat Exporter Web UI:
+  `http://localhost:40653/qce-v4-tool`
+- NapCat Web UI config file:
+  `config\webui.json`
+- QCE plugin is enabled in:
+  `config\plugins.json`
+- Current OneBot config files have no HTTP/WebSocket endpoints enabled:
+  `config\onebot11.json`
+  `config\onebot11_3885485626.json`
+- Previously exported records:
+  `D:\TH1_本地目录\Q群每日\聊天记录\072`
+- Backup found:
+  `D:\TH1_本地目录\Q群每日\聊天记录\消息记录备份\3885485626的1个聊天记录.bak`
+- User-level QCE data directory:
+  `C:\Users\daixiawu\.qq-chat-exporter`
+
+## Recommended Execution On New PC
+
+Do not run the user's main QQ and bot QQ in the same QQNT user data context if stability matters. Prefer one of:
+
+1. Run main QQ normally on the desktop, and run bot QQ + NapCat under a second Windows user.
+2. Run bot QQ + NapCat inside a virtual machine.
+3. Only use same-session multi-open if the user accepts login-state conflicts and possible forced switching.
+
+## Bot Login And Export Steps
+
+1. Install QQNT on the new PC.
+2. Copy or re-download the NapCat-QCE package.
+3. If the QQ path differs, run `reset-qq-path.bat` or pass the QQ.exe path to `launcher-user.bat`.
+4. Start full mode:
+
+   ```powershell
+   cd /d "D:\TH1_本地目录\Q群每日\聊天记录\Tools\NapCat-QCE-Windows-x64-v5.5.64\NapCat-QCE-Windows-x64"
+   .\launcher-user.bat
+   ```
+
+5. Log in with the bot QQ account by QR/client login.
+6. Open:
+   `http://localhost:40653/qce-v4-tool`
+7. Enter the access token printed in the console.
+8. Select target groups, time range, and export format. JSON is best for later AI analysis; HTML is best for manual browsing.
+
+## AI Auto-Speaking Feasibility
+
+Technically possible via NapCat OneBot, but currently not enabled in the found config. To implement later:
+
+- Enable OneBot HTTP or WebSocket endpoint in `onebot11.json` for the bot account.
+- Run a separate AI relay process that:
+  - receives group messages;
+  - filters by group whitelist and trigger rules;
+  - calls the AI model;
+  - either writes a draft for manual confirmation or sends with strict rate limits.
+- Prefer manual-confirm mode first. Full automatic group speaking can misfire, spam, violate group expectations, and risk account restrictions.
+
+## Prompt To Paste Into Codex On The New PC
+
+I am continuing a handoff for QQ / NapCat / QQ Chat Exporter setup.
+
+Context:
+- Need to run my normal QQ account separately from a bot QQ account.
+- Prefer bot QQ in another Windows user or VM to avoid QQNT session conflicts.
+- The source PC found a NapCat + QQ Chat Exporter package at:
+  `D:\TH1_本地目录\Q群每日\聊天记录\Tools\NapCat-QCE-Windows-x64-v5.5.64\NapCat-QCE-Windows-x64`
+- Main launcher: `launcher-user.bat`
+- Web UI after startup: `http://localhost:40653/qce-v4-tool`
+- The launcher's first argument is a path to `QQ.exe`, not a QQ number.
+- Existing source PC saved QQ path was `D:\Program Files\Tencent\QQNT\QQ.exe`.
+- QCE plugin is enabled, but OneBot HTTP/WebSocket endpoints were empty, so AI auto-speaking is not active yet.
+
+Please help me on this new PC:
+1. Locate QQNT and the NapCat-QCE package.
+2. Verify the launcher/config paths.
+3. Start or tell me exactly how to start bot QQ login safely.
+4. Help export all accessible group chat records.
+5. If I ask for AI group replies, set up a conservative manual-confirm workflow first, not unrestricted auto-send.