fix: show accurate request status in message footers

Requests could appear to keep working while OpenCode waited to retry, and retry backoff was described as an active attempt. Report native OpenCode retry timing, distinguish direct-model backoff from dispatch, and show preparation, tool activity, pending input, and terminal states accurately. Keep only the message-footer indicator static. Conversation-list activity indicators, send/stop controls, retry limits, and command replay behavior remain unchanged. Align the feature documentation with verified behavior. Validation: 3618 tests passed, 61 skipped; typecheck and lint passed. Isolated desktop validation used five real text-model calls across three profiles, with controlled local fault injection for retry transitions. Release note: 消息底部现在准确区分请求准备、等待重试、开始重试和需要回答的状态，不再用闪烁暗示仍有进展；会话列表闪点及发送、停止行为保持不变。
2026-09-08 22:47:06 +08:00
parent 9b7cf730d0
commit c82d0161a9
18 changed files with 289 additions and 37 deletions
@@ -117,8 +117,12 @@ GoodBuddy 服务崩溃。
 - Runtime 初始化、Shell 探测或全局服务失败可通过应用通知提示，并在设置状态卡提供重试。
 - 同一错误不同时显示活动块副本和通知副本。
 - 失败后保留用户 Prompt、命令摘要、工作目录和已有输出。
- 直连模型自动重试通过现有聊天状态显示“模型网络请求失败，正在重试（n/3）”，不增加
-  独立按钮、弹窗或通知副本；用户仍可使用当前停止操作取消请求。
+- 直连模型自动重试在消息底部区分“模型网络请求失败，等待重试（n/3，s 秒后）”与
+  “〈模型名〉正在重试请求（n/3），等待响应”；只有退避结束且未取消才显示后者。
+  初始请求显示“〈模型名〉请求处理中”，不把尚无输出的等待描述成思考。
+- 不增加独立按钮、弹窗或通知副本；用户仍可使用当前停止操作取消请求。
+  底部静态状态点、工具进展、待回答及终态优先规则由
+  [消息底部请求状态](../assistant-workbar/runtime-interactions.md#消息底部请求状态)统一定义。

 ## 7. 键盘与无障碍