docs: document autonomy notification target derivation from channel allow_from

README.md

@@ -66,6 +66,7 @@
 - 示例：`[keys: repo:clawgo, file:pkg/agent/loop.go, branch:main] 修复对话流程`
 - 未显式声明时，系统会从任务文本自动推断资源键。
 - 冲突任务进入 `resource_lock` 等待，默认 30 秒后重试抢锁，并带公平加权（等待越久优先级越高）。
+- 自治完成/阻塞通知不再使用 `autonomy.notify_channel` / `autonomy.notify_chat_id`；默认自动从已启用通道的 `allow_from` 推导目标（优先 Telegram）。
 
 ## 🏁 快速开始
 

README_EN.md

@@ -66,6 +66,7 @@ Autonomy now supports lock scheduling via `resource_keys`. You can explicitly de
 - Example: `[keys: repo:clawgo, file:pkg/agent/loop.go, branch:main] fix dialog flow`
 - Without explicit keys, the engine derives keys from task text heuristically.
 - Conflicting tasks enter `resource_lock` waiting, retry lock acquisition after 30s, and use fairness weighting (longer wait => higher scheduling priority).
+- Autonomy completion/blocked notifications no longer use `autonomy.notify_channel` / `autonomy.notify_chat_id`; target is derived from enabled channel `allow_from` (Telegram first).
 
 ## 🏁 Quick Start