docs(cleanup): mark discord-control-api references as historical after in-plugin migration

docs/PR_SUMMARY.md

@@ -51,5 +51,5 @@ This PR delivers two tracks:
 ## Rollback
 
 - Disable plugin entry or remove plugin path from OpenClaw config
-- Stop `discord-control-api` process
+- (Legacy note) `discord-control-api` sidecar has been removed; Discord control is in-plugin now
 - Keep no-reply API stopped if not needed

docs/TEST_REPORT.md

@@ -8,7 +8,7 @@
 
 1. Dirigent 基础静态与脚本测试
 2. no-reply-api 隔离集成测试
-3. discord-control-api 功能测试（dryRun + 实操）
+3. （历史）discord-control-api 功能测试（dryRun + 实操，当前版本已迁移为 in-plugin）
 
 未覆盖：
 
@@ -53,7 +53,7 @@ make check check-rules test-api
 
 ---
 
-### B. discord-control-api dryRun + 实操测试
+### B. （历史）discord-control-api dryRun + 实操测试（当前版本已迁移）
 
 执行内容与结果：
 
@@ -113,7 +113,7 @@ make check check-rules test-api
 
 ### 2) 回归测试
 
-- discord-control-api 引入后，不影响 Dirigent 原有流程
+- （历史结论）discord-control-api 引入后，不影响 Dirigent 原有流程；现已迁移为 in-plugin 实现
 - 规则校验脚本在最新代码继续稳定通过
 
 ### 3) 运行与安全校验

docs/TURN-WAKEUP-PROBLEM.md

@@ -78,7 +78,7 @@ When current speaker NO_REPLYs, have **that bot** send a brief handoff message i
 **Challenges:**
 - Adds visible noise to the channel (could use a convention like a specific emoji reaction)
 - The no-reply'd bot can't send messages (it was silenced)
-- Could use the discord-control-api to send as a different bot
+- Could use in-plugin Discord REST control to send as a different bot (sidecar removed)
 
 ### 6. Timer-Based Retry (Pragmatic)
 
@@ -93,7 +93,7 @@ After advancing the turn, set a short timer (e.g., 2-3 seconds). If no new messa
 **Solution 5 (Bot-to-Bot Handoff)** is the most pragmatic with current constraints. The implementation would be:
 
 1. In the `message_sent` hook, after detecting NO_REPLY and advancing the turn:
-2. Use the discord-control-api to send a short message (e.g., `[轮转]` or a specific emoji) from the **next speaker's bot account** in the channel
+2. Use in-plugin Discord REST control to send a short message (e.g., `[轮转]` or a specific emoji) from the **next speaker's bot account** in the channel
 3. This real Discord message triggers OpenClaw to route it to all agents
 4. The turn manager allows only the (now-current) next speaker to respond
 5. The next speaker sees the original conversation context in their session history and responds appropriately