fix: prevent duplicate queue replay and use cached Agents

An interrupted dispatch could leave the same user input both in conversation history and in the pending queue, causing it to be sent again after restart. Persisted user messages now retain their queue identity, startup recovery drops only matching materialized inputs, and conversation branches discard that ownership marker. Explicit GoodBuddy transfer now leases a verified local Agent package when the catalog is unavailable or the local version is at least as new, while a known newer online package still wins. Prepare both the desktop and Agent locks for 0.11.7; the experimental LoongArch preview remains excluded. Release note: 修复对话中断后同一条排队输入可能重复发送的问题；GoodBuddy 传输现在可复用已验证的本地 Agent 包，同时不会阻止已知的线上新版。
2026-08-29 13:31:56 +08:00
parent 459cc21e3d
commit f327341b00
17 changed files with 334 additions and 42 deletions
@@ -363,7 +363,8 @@ Task Center 显示 Scheduled Task 的范围、关联 Conversation、状态、模
 - [x] 手动运行不改变下次计划时间。
 - [x] Scheduled Task 与普通消息共用 Conversation 级队列，不并发写入同一时间线。
 - [x] 当前回复期间可以继续发送普通消息，并在 Composer 上沿查看、删除或提升待发送项。
- [x] 应用重启恢复尚未执行的队列项和有界附件上下文。
+- [x] 应用重启恢复尚未执行的队列项和有界附件上下文；已写入 Conversation 的用户输入
+  通过队列项身份完成恢复对账，不会再次进入待发送队列。
 - [x] 文本结果只写入 Conversation，独立交付物才进入成果。
 - [ ] Task Center 和桌面通知可以打开正确 Conversation 并定位 Task。
 - [ ] 应用重启不自动重放结果未知的副作用。