dsh-notify-me 1.9.4 → 1.10.0

package/CHANGELOG.md

@@ -2,6 +2,36 @@
 
 All notable changes to **dsh-notify-me** are documented here.
 
+## [1.10.0] — 2026-10-21
+
+### 新增
+
+- **提醒方式改成二选一**：「系统通知」和「页面浮层」从两个独立开关变成一组单选。两个都开时同一条提醒会弹两遍、浮层还会被系统横幅压住，现在选一个另一个自动关掉。老配置里开着浮层的，升级后自动落到浮层（`readConfig` 迁移，`overlay`/`toast` 两个旧字段继续作为镜像同步，控制台 `setConfig({ overlay: true })` 照旧生效）。
+- 设置页里这两个选项改成行首带单选的列表，读起来是一组互斥选项，而不是两个可以同时开的开关。
+
+### 变更
+
+- **停留时间收紧**：普通系统通知 10 秒自动收（带按钮的 20 秒），原来统一 15 秒；浮层卡片「需要你」12 秒、「回复完成」6 秒、带按钮的审批卡片 18 秒——原来带按钮的卡永不自动消失，留着占屏。
+- 说明文案同步：系统通知那行直说「桌面端这类通知没有按钮」，浮层那行直说「与上面二选一」；`bridgeOffDesktop` 改成指路——桌面端要按钮就切到浮层，并点明宿主缺 `allowServiceWorkers`。
+- `api.debug()` 新增 `channel` 字段。
+
+### 测试
+
+- 冒烟：两个单选互斥的持久化、老配置迁移、切频道时图层清理、两种渠道各自只发一条、带按钮卡片 18 秒自收（用可控 `setTimeout` 捕获定时器）。
+- `npm test` 两套件（`smoke-test.cjs` / `cordis-host-test.mjs`）全过。
+
+## [1.9.5] — 2026-10-20
+
+### 说明
+
+- **修正 1.9.4 的口径过重**：实测补充了「有时能上前台」的反馈后重测——1.9.4 说的「0.2.1-rc.2 上失效」不准确，实际是**不稳定**：有时窗口会上前，有时只切对话。
+- 复测方法：把 `dsh://open` 深链单独拿出来，三种走法（直接带参启动 exe、走系统协议激活、`WM_SYSCOMMAND` 真实最小化后再发）各 3 次，**全部失败**——带参第二实例每次约 130 ms 后退出码 1（不带参数约 260 ms 退出码 0，正常单实例让位），最小化窗口的 `IsIconic` 每次保持 `true`。⇒ 能抬起来的那些次大概率是系统/Chromium 在通知点击时自己激活了窗口，不是深链。
+- README（中英）与设置页提示改为「不稳定」，并写明隔离复测结论；上游 [discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446) 待补充这条「间歇」信息。
+
+### 测试
+
+- `npm test` 两套件通过（`ALL SMOKE TESTS PASSED ✔` / `cordis-host-test passed`）。
+
 ## [1.9.4] — 2026-10-20
 
 ### 说明

package/README.en.md

@@ -13,7 +13,7 @@
 [![npm total downloads](https://img.shields.io/npm/dt/dsh-notify-me?style=flat-square&label=total%20downloads&color=1F883D)](https://www.npmjs.com/package/dsh-notify-me)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue?style=flat-square)](LICENSE)
 [![DSH Web and Desktop](https://img.shields.io/badge/DSH-Web%20%7C%20Desktop-blue?style=flat-square)](#installation)
-[![Client bundle size](https://img.shields.io/badge/client-%7E166%20KiB-green?style=flat-square)](lib/client.js)
+[![Client bundle size](https://img.shields.io/badge/client-%7E168%20KiB-green?style=flat-square)](lib/client.js)
 [![DSH Compatibility](https://img.shields.io/badge/DSH-tested%200.2.1--rc.2-6366f1.svg?style=flat-square)](#compatibility)
 [![Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com)
 
@@ -26,7 +26,7 @@ A notification plugin for DSH Web / Desktop, so you can keep full access off wit
 - **When input is needed:** approval, plan review, and questions trigger notifications, sound, and a title marker.
 - **When a background reply finishes:** return to the result; click the notification to open its conversation.
 - **When you leave your computer:** optionally forward alerts to Discord, Bark, Gotify, or your own webhook.
-- **When you do not watch the primary display:** an optional in-page overlay follows the DSH window onto whichever screen you are looking at (system notifications only ever appear on the primary display).
+- **When you do not watch the primary display:** switch the alert channel to the in-page overlay — it follows the DSH window onto whichever screen you are looking at (system notifications only ever appear on the primary display).
 
 > Keep the page or desktop app running; backgrounding / minimizing is fine. System notifications require permission. Approval buttons need a Service Worker capable Web environment (such as `http://127.0.0.1` or `https`); Desktop notifications have no buttons — turn on the in-page overlay to decide from there instead (see [Secondary displays and the overlay](#secondary-displays-and-the-overlay)).
 
@@ -47,7 +47,7 @@ A notification plugin for DSH Web / Desktop, so you can keep full access off wit
 
 ![The Notify me settings page: header, how you get told, when to alert, try it, and the collapsed Advanced block](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/settings-en.png)
 
-The real settings component (v1.9.2 defaults) rendered as the content column in a standalone demo shell. Row explanations now live in a hover tooltip that appears when the pointer rests on a title, which is why only the titles show here.
+The real settings component (v1.10.0 defaults) rendered in a standalone demo shell. The alert channel is a single choice, and row explanations live in a hover tooltip that appears when the pointer rests on a title, which is why only the titles show here.
 </details>
 
 ## Installation
@@ -121,10 +121,11 @@ Open **Settings → Notify me**. The page runs as how you get told, when to aler
 ### How you get told
 
 - **Enable reminders**: master switch — off means no toasts, no sounds, and the tab title is left alone;
-- **System notifications** (on by default): native toasts through the browser, landing in the Windows / macOS notification center;
-- **In-page overlay** (off by default): cards drawn in the page corner, on whichever display the window sits on — system notifications only land on the primary display. No permission needed, and the Desktop shell can Approve / Reject right on the card. Runs alongside toasts; pick one of four corners when expanded. See [Secondary displays and the overlay](#secondary-displays-and-the-overlay);
+- **How you get told (pick one)**: system notifications or the in-page overlay — a single choice, so turning one on turns the other off;
+  - **System notifications** (default): native toasts landing in the Windows / macOS notification center; needs notification permission;
+  - **In-page overlay**: cards drawn in the page corner, on whichever display the window sits on — system notifications only land on the primary display. No permission needed, and the Desktop shell can Approve / Reject right on the card. Pick one of four corners when it is the chosen channel. See [Secondary displays and the overlay](#secondary-displays-and-the-overlay);
 - **Sound / Volume**: master cue switch and a volume slider; what it plays comes from Advanced → Alert sound;
-- **Decide approvals from the toast** (on by default): approval toasts carry Approve / Reject that settle the request in place. **Desktop notifications have no buttons** (`dsh-app://` cannot register a Service Worker) — leave the overlay on instead; the page states plainly which channel can carry buttons right now.
+- **Decide approvals from the toast** (on by default): approval toasts carry Approve / Reject that settle the request in place. **Desktop notifications have no buttons** (`dsh-app://` cannot register a Service Worker) — pick the in-page overlay as the channel instead; the page states plainly which channel can carry buttons right now.
 
 ### Secondary displays and the overlay
 
@@ -135,8 +136,8 @@ The **in-page overlay** skips the notification center and draws the card inside
 - **Position** — top right / bottom right / top left / bottom left, default bottom right; changes apply immediately;
 - **No notification permission needed** — it works when permission was never granted, and on the Desktop shell where buttonless toasts are all the OS channel can do;
 - **Approval cards carry Approve / Reject** — the same decision as Allow once / Reject on the approval card, and they work on the Desktop too (no Service Worker involved). Clicking the card body opens its conversation;
-- **Lifetime** — "needs you" cards retire after 20s, "reply finished" after 8s; an approval card with buttons stays until it is decided or closed. At most 4 cards stack at once;
-- **Relation to system notifications** — the two switches are independent. With both on, the primary display gets toasts and the second screen gets the overlay; the overlay alone is also a valid setup.
+- **Lifetime** — "needs you" cards retire after 12s, "reply finished" after 6s, and an approval card with buttons after 18s; a card or its close button retires one earlier. At most 4 cards stack at once;
+- **Relation to system notifications** — it is one or the other. Both used to be switchable at once, which meant every alert arrived twice and the pair covered each other; 1.10.0 makes it a single choice, and an old config with the overlay on migrates to it.
 
 The overlay only knows which screen the window is on, not which screen you are looking at. If the window stays on the primary display while you watch another one, it stays invisible — same as a toast.
 
@@ -146,7 +147,7 @@ The overlay only knows which screen the window is on, not which screen you are l
 - **Stay quiet for the conversation on screen** (on): a wait belonging to the conversation you are looking at keeps only the tab marker so the approval card stays readable; backgrounding restores alerts;
 - **Also alert "reply finished" while the page is open** (off): by default only background finishes alert;
 - **Ignore subagent sessions** (on): skip background sessions spawned by a subagent — the parent conversation covers them; the one you have open still alerts;
-- **Click a toast to open that conversation** (on): the click switches to the conversation that raised it; in a browser it also brings the window forward, while on the Desktop shell whether the native window comes forward depends on the shell version (see [How the Desktop window gets raised](#how-the-desktop-window-gets-raised)); with several tabs open only one is raised, and off means a click does nothing.
+- **Click a toast to open that conversation** (on): the click switches to the conversation that raised it; in a browser it also brings the window forward, while on the Desktop shell it is flaky — sometimes the window comes forward, sometimes only the conversation switches (see [How the Desktop window gets raised](#how-the-desktop-window-gets-raised)); with several tabs open only one is raised, and off means a click does nothing.
 
 ### Try it
 
@@ -182,7 +183,7 @@ Off by default. Supports Discord Webhook / Bark / Gotify / custom webhooks. Aler
 
 ### Runtime & diagnostics
 
-The last block inside Advanced. The page protocol is detected automatically to tell Web from Desktop (`dsh-app://`); override it by hand if detection is wrong — Desktop clicks fire the `dsh://` deep link (whether that actually raises the window depends on the shell version — see [How the Desktop window gets raised](#how-the-desktop-window-gets-raised)) and carry no quick-decision buttons, while Web uses `window.focus()` plus the Service Worker bridge. When the override disagrees with detection the page says so.
+The last block inside Advanced. The page protocol is detected automatically to tell Web from Desktop (`dsh-app://`); override it by hand if detection is wrong — Desktop clicks fire the `dsh://` deep link (the effect is unreliable — see [How the Desktop window gets raised](#how-the-desktop-window-gets-raised)) and carry no quick-decision buttons, while Web uses `window.focus()` plus the Service Worker bridge. When the override disagrees with detection the page says so.
 
 <details>
 <summary>Alert language, Desktop window raising, reset</summary>
@@ -200,7 +201,7 @@ The last block inside Advanced. The page protocol is detected automatically to t
 ## How it alerts
 
 - **System notification** — a toast through the browser into the Windows action center / macOS Notification Center (clicking it opens the conversation it came from; supported Web environments offer approval buttons, Desktop does not)
-- **In-page overlay** (optional, default off) — an alert card drawn in the corner of the DSH page, on whatever display the window is on, optionally with Approve / Reject buttons; see [Secondary displays and the overlay](#secondary-displays-and-the-overlay)
+- **In-page overlay** — an alert card drawn in the corner of the DSH page, on whatever display the window is on, optionally with Approve / Reject buttons; see [Secondary displays and the overlay](#secondary-displays-and-the-overlay)
 - **Sound** — WebAudio beeps by default (distinct patterns for "needs you" vs "done"); each kind can instead play a picked audio file, or hand the sound over to the operating system's own notification sound
 - **Tab title marker** — while something is waiting on you, the tab title is prefixed with `🔔 Action needed · …` / `🔔 需要你 · …`; while a background session is **finished but unread**, with `✅ Reply finished · …` / `✅ 回复完成 · …`, gone once you open that session (or it starts running again). Both kinds can be up together, "needs you" first; a host title change is rebased under the markers
 - **External notifications** (optional, default off) — the same alert is also forwarded to the push targets you configure: Discord Webhook / Bark / Gotify / custom webhook — so the push channel on your phone picks it up while you step away from the machine
@@ -250,14 +251,14 @@ window.__dshNotifyMe.setConfig({
   currentHiddenOnly: true,    // true = waits in the conversation on screen keep only the tab marker (replayed once backgrounded)
   doneHiddenOnly: true,       // false = also alert "reply finished" while visible
   ignoreSubagent: true,       // true = never alert for background subagent sessions (the open one is exempt)
-  toast: true,                // system-notification toggle
+  channel: "toast",          // alert channel: 'toast' system notification | 'overlay' in-page card, pick one
   sound: true,                // cue toggle (also governs the "system notification sound" mode)
   soundDone: "synth",         // "reply finished" cue source: 'synth' built-in | 'custom' picked file | 'system' OS sound
   soundAttention: "synth",    // "needs you" cue source, same values
   volume: 0.5,                // 0..1
   autoFocus: true,            // clicking a toast opens the conversation it came from
   quickActions: true,         // Approve / Reject buttons on approval toasts
-  overlay: false,             // in-page overlay alert (follows the DSH window to its display; no notification permission needed)
+  overlay: false,             // legacy mirror kept in sync with channel (old configs migrate through it)
   overlayCorner: "bottom-right", // overlay anchor: 'top-right' | 'bottom-right' | 'top-left' | 'bottom-left'
   externalEnabled: false,     // external-notification forwarding master switch (default off: no endpoint, nothing is sent)
   externalAttention: true,    // forward "needs you" (exactly the same trigger rules as local alerts)
@@ -305,7 +306,11 @@ DSH Desktop is a thin Electron shell and its page lives under `dsh-app://app`: D
 
 Verified on the real shell (DSH Desktop 0.2.0-rc.2, three rounds of retesting in issue #9): a toast click raises the window and switches the conversation in one step, stable across sessions and with the window in the background. Timing of the fire is what makes the chain work: the deep link must be launched from a **user-gesture handler** — the notification's `onclick` carries one, which is why the product path works — while gesture-less scripted injection (an iframe appended from a CDP evaluate, say) is silently dropped by Chromium and the external protocol never launches, which looks exactly like the channel being blocked.
 
-**Regression on 0.2.1-rc.2 / Windows** (measured 2026-10-20): the toast click handler still runs (`navigator.userActivation.isActive === true`, `visibilityState` is `hidden`), but the window no longer comes forward. Shell-side evidence: launching a second instance with the `dsh://open` argument exits with code 1 after 133 ms, while launching it without arguments exits with code 0 after 258 ms (the normal single-instance yield), so the URL branch is what breaks. Minimizing the window for real via `WM_SYSCOMMAND` and then firing the deep link — or relaunching with no arguments — leaves `IsIconic` at `true`, so `focusPrimaryWindow()`'s `restore()` never takes effect. There is no page-side fallback either: the shell preload only exposes `dshDesktop`, the directory picker and locale, and `DESKTOP_IPC` has no focus/raise channel. The repro and code locations are filed upstream in [deepseek-harness discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446). The plugin's part ends there: it still fires the deep link; raising the native window is the shell's call.
+**Flaky on 0.2.1-rc.2 / Windows** (measured 2026-10-20): the toast click handler still runs (`navigator.userActivation.isActive === true`, `visibilityState` is `hidden`), but whether the window actually comes forward is inconsistent — sometimes it does, sometimes only the conversation switches while the window stays put.
+
+Do not count on the plugin's own path: isolating the `dsh://open` deep link (three ways, three runs each — launching the exe with the argument, OS protocol activation, and a real `WM_SYSCOMMAND` minimize followed by the deep link) failed **every time**. The second instance with the argument exits with code 1 after ~130 ms (without arguments it exits with code 0 after ~260 ms, the normal single-instance yield), and after a real minimize `IsIconic` stays `true`. So the times it does come forward are most likely the OS/Chromium activating the app on the notification click itself, not the deep link.
+
+There is no page-side fallback either: the shell preload only exposes `dshDesktop`, the directory picker and locale, `DESKTOP_IPC` has no focus/raise channel, and the main window's `will-navigate` rejects `dsh:` URLs outright. The repro and code locations are filed upstream in [deepseek-harness discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446).
 
 </details>
 
@@ -315,7 +320,7 @@ Verified on the real shell (DSH Desktop 0.2.0-rc.2, three rounds of retesting in
 - Notifications appear through the browser, so the browser needs "show notifications" permission in the OS notification settings, and notification-center "Do Not Disturb" must not suppress them.
 - The first sound/toast of each page load needs one user click on the page first (browser autoplay + permission policy).
 - Toasts are only produced once the notification permission is granted; declining means sound + title marker only.
-- On the Desktop shell (DSH Desktop 0.2.1-rc.2 / Windows) a toast click no longer brings the window forward by itself: the plugin fires the `dsh://open` deep link, but the shell does not raise the window ([discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446)). Switching to the conversation still works.
+- On the Desktop shell (DSH Desktop 0.2.1-rc.2 / Windows) a toast click does not reliably bring the window forward: sometimes it does, sometimes only the conversation switches. The plugin's `dsh://open` deep link on its own failed 3/3 in isolation (see [How the Desktop window gets raised](#how-the-desktop-window-gets-raised)), so when it does come forward it is most likely the OS/Chromium activating the app on the notification click itself ([discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446)).
 - System notification banners are drawn on the primary display only: Windows has no setting and Chromium no API to aim one at another monitor, so on a multi-monitor setup the second screen never receives them. Use the in-page overlay for that — it follows the DSH window to its display.
 - Quick-decision buttons need a Service Worker: they work on `http://127.0.0.1` and `https`, not on plain `http://192.168.x.x`-style LAN addresses, and some browsers or desktop hosts never render notification buttons. **The Desktop (`dsh-app://`) is tested and cannot register a Service Worker**, so buttons never render there and approval toasts fall back to their buttonless form. The `bridge` field of `window.__dshNotifyMe.debug()` says why; everything else keeps working.
 - macOS: in the browser, alerts, sounds, the title marker and toast-click navigation carry no OS assumptions and work as on Windows. Two caveats: DSH Desktop (Electron) notifications require the app to be code-signed — unsigned builds simply emit no notification — and whether the official macOS build satisfies that is untested; and notification buttons on the macOS desktop host are likewise untested (the Windows desktop host is tested and renders none, see the line above), falling back to the buttonless form above.

package/README.md

@@ -13,7 +13,7 @@
 [![npm total downloads](https://img.shields.io/npm/dt/dsh-notify-me?style=flat-square&label=total%20downloads&color=1F883D)](https://www.npmjs.com/package/dsh-notify-me)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue?style=flat-square)](LICENSE)
 [![DSH Web and Desktop](https://img.shields.io/badge/DSH-Web%20%7C%20Desktop-blue?style=flat-square)](#安装)
-[![Client bundle size](https://img.shields.io/badge/client-%7E166%20KiB-green?style=flat-square)](lib/client.js)
+[![Client bundle size](https://img.shields.io/badge/client-%7E168%20KiB-green?style=flat-square)](lib/client.js)
 [![DSH Compatibility](https://img.shields.io/badge/DSH-%E5%B7%B2%E9%80%82%E9%85%8D%200.2.1--rc.2-6366f1.svg?style=flat-square)](#兼容性)
 [![Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com)
 
@@ -26,9 +26,9 @@ DSH Web / Desktop 的通知插件，让你敢不开完整访问，也不必一
 - **需要你操作时**：审批、方案确认、提问，用通知、提示音和标题标记提醒。
 - **后台回复完成时**：及时回来查看结果，点击通知可回到对应对话。
 - **离开电脑时**：可选转发到 Discord、Bark、Gotify 或自己的 Webhook。
-- **不看主屏时**：可选页面内浮层提醒，跟着 DSH 窗口出现在你正看着的那块屏（系统通知只会出现在主屏）。
+- **不看主屏时**：提醒方式可以切成页面内浮层，跟着 DSH 窗口出现在你正看着的那块屏（系统通知只会出现在主屏）。
 
-> 页面或桌面应用需保持运行，后台 / 最小化可以。系统通知需要通知权限；审批按钮在支持 Service Worker 的 Web 环境（如 `http://127.0.0.1` 或 `https`）由通知提供，桌面端的通知没有按钮——打开「页面浮层提醒」后可在浮层上直接裁决（见[副屏与浮层提醒](#副屏与浮层提醒)）。
+> 页面或桌面应用需保持运行，后台 / 最小化可以。系统通知需要通知权限；审批按钮在支持 Service Worker 的 Web 环境（如 `http://127.0.0.1` 或 `https`）由通知提供，桌面端的通知没有按钮——把「提醒方式」切到页面浮层「页面浮层提醒」后可在浮层上直接裁决（见[副屏与浮层提醒](#副屏与浮层提醒)）。
 
 > 🔎 想找这个插件？可以搜：`dsh-notify-me`、**消息提醒**、**可操作提醒**、**桌面通知**、**需要你操作**、**回复完成提醒**、**后台完成提醒**、**外部通知**、**Discord / Bark / Gotify 推送**（npm 关键词已含以上中英文词）。
 
@@ -47,7 +47,7 @@ DSH Web / Desktop 的通知插件，让你敢不开完整访问，也不必一
 
 ![通知提醒设置页：页眉、提醒方式、什么时候提醒、试一试与折叠的高级设置](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/settings-zh.png)
 
-真实插件设置组件（v1.9.2 默认配置）在独立演示环境里按内容列整页渲染；每行的说明改成鼠标停在标题文字上才出现的小方框，所以这里只看到标题。
+真实插件设置组件（v1.10.0 默认配置）在独立演示环境里渲染；提醒方式是一组单选，每行的说明在鼠标停在标题文字上时才出现，所以这里只看到标题。
 </details>
 
 ## 安装
@@ -74,7 +74,7 @@ dsh plugin --profile web add dsh-notify-me
 ## 首次验证
 
 1. 在 DSH 页面上点击一次，按提示允许通知；若此前拒绝过，在浏览器站点设置中允许通知。操作系统也需要允许对应浏览器 / DSH Desktop 显示通知。
-2. 打开 **设置 → 通知提醒**，确认出现该分区及底部插件版本号，保持「启用提醒」「系统通知」「提示音」开启。
+2. 打开 **设置 → 通知提醒**，确认出现该分区及底部插件版本号，保持「启用提醒」「提示音」开启，提醒方式先留「系统通知」。
 3. 点击设置页的「测试『回复完成』」按钮：应出现一条测试通知，并按当前音效设置播放声音。这个本地测试不会转发到外部通知端点，也不受「页面打开时也提醒」开关限制。
 
 Web 用户可再测试审批按钮；桌面端该测试只发普通通知，**没有「同意 / 拒绝」按钮属于预期行为**。
@@ -117,8 +117,9 @@ dsh-notify-me 把「监督」和「守在屏幕前」解耦：只在真的出现
 ### 提醒方式
 
 - **启用提醒** 总开关：关闭后不弹通知、不响提示音，也不改标签页标题；
-- **系统通知**（默认开）：经浏览器弹系统通知，进 Windows / macOS 通知中心；
-- **页面浮层提醒**（默认关）：在 DSH 页面角落画提醒卡片，窗口在哪块屏它就在哪块屏——系统通知只会画在主屏，主屏不看时用它；不需要通知权限，桌面端也能在卡片上直接「同意 / 拒绝」，可与系统通知同开。展开后可选四个角落的位置，见[副屏与浮层提醒](#副屏与浮层提醒)；
+- **提醒方式（二选一）**：系统通知 / 页面浮层，单选，开了这个就不再弹那个；
+  - **系统通知**（默认）：进 Windows / macOS 通知中心，需要通知权限；
+  - **页面浮层**：在 DSH 页面角落画提醒卡片，窗口在哪块屏它就在哪块屏——系统通知只会画在主屏，主屏不看时用它；不需要通知权限，桌面端也能在卡片上直接「同意 / 拒绝」。选中后可选四个角落的位置，见[副屏与浮层提醒](#副屏与浮层提醒)；
 - **提示音 / 音量**：提示音开关与音量滑块；具体播什么由「高级设置 → 音效来源」决定；
 - **审批通知上直接裁决**（默认开）：审批通知带「同意 / 拒绝」，点一下即完成裁决，不用切回页面。**桌面端的通知没有按钮**（`dsh-app://` 页面无法注册 Service Worker），需要按钮就打开「页面浮层提醒」，改在浮层上裁决；设置页会如实说明当前哪种渠道能给按钮。
 
@@ -131,8 +132,8 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 - **位置**：设置里选右上 / 右下 / 左上 / 左下，默认右下；改完立刻生效；
 - **不需要通知权限**：通知权限没给、或桌面端弹不出带按钮的通知时，浮层照常工作；
 - **审批卡片带「同意 / 拒绝」**：与审批卡片的「允许一次 / 拒绝」等价，桌面端也能用（不依赖 Service Worker）；点卡片正文则切回对应对话；
-- **停留时间**：「需要你」20 秒后自动收起，「回复完成」8 秒；带按钮的审批卡片不自动收，直到裁决或手动关掉。最多同时叠 4 张；
-- **与系统通知的关系**：两个开关互不替代。都开着时主屏看系统通知、副屏看浮层，也可以只留浮层。
+- **停留时间**：「需要你」12 秒，「回复完成」6 秒，带按钮的审批卡片 18 秒，都会自动收起；也可以点卡片或右上角叉提前关掉。最多同时叠 4 张；
+- **与系统通知的关系**：二选一。以前两个开关可以同开，结果同一条提醒弹两遍、还互相挡住，1.10.0 起改成单选。老配置里开着浮层的，升级后自动落到浮层。
 
 浮层只知道窗口在哪块屏，不知道你人在看哪块屏。窗口留在主屏、人却盯着副屏时，它同样看不见。
 
@@ -142,7 +143,7 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 - **当前对话不弹通知**（默认开）：等待就发生在你正看着的对话里时只留标签页标记，免得挡住审批卡片；切到后台后照常提醒，若你已处理掉就作废；
 - **页面打开时也提醒「回复完成」**（默认关）：默认只在切到后台时提醒，避免打扰；
 - **子代理会话不提醒**（默认开）：跳过后台子代理（subagent）会话——它们是主对话那一轮的步骤，完成由主对话自己的提醒覆盖；你当前打开的那个子代理会话照常提醒；
-- **点击通知回到对应对话**（默认开）：点通知切到提醒所属的对话；浏览器里同时把窗口带到前台，桌面端能不能上前台看壳的版本（见[桌面端怎么抬窗的](#桌面端怎么抬窗的)）；多个标签页同时开着时只调起一个（优先当前可见的那个）；关掉后点通知不做任何事。
+- **点击通知回到对应对话**（默认开）：点通知切到提醒所属的对话；浏览器里同时把窗口带到前台；桌面端不稳定——有时窗口会上前，有时只切对话（见[桌面端怎么抬窗的](#桌面端怎么抬窗的)）；多个标签页同时开着时只调起一个（优先当前可见的那个）；关掉后点通知不做任何事。
 
 ### 试一试
 
@@ -178,13 +179,13 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 
 ### 运行环境与诊断
 
-在「高级设置」最后一块。默认自动识别当前是 Web 端还是桌面端（DSH Desktop，`dsh-app://`）；识别不准时可手动指定——桌面端点通知走 `dsh://` 深链调窗（能否真的上前台看壳的版本，见[桌面端怎么抬窗的](#桌面端怎么抬窗的)）、通知上不带快捷裁决按钮；Web 端走 `window.focus()` 与 Service Worker 桥。手动覆盖与自动识别不一致时，设置页会明示检测结果。
+在「高级设置」最后一块。默认自动识别当前是 Web 端还是桌面端（DSH Desktop，`dsh-app://`）；识别不准时可手动指定——桌面端点通知走 `dsh://` 深链调窗（效果不稳定，见[桌面端怎么抬窗的](#桌面端怎么抬窗的)）、通知上不带快捷裁决按钮；Web 端走 `window.focus()` 与 Service Worker 桥。手动覆盖与自动识别不一致时，设置页会明示检测结果。
 
 <details>
 <summary>通知语言、桌面端抬窗与恢复默认</summary>
 
 - **通知语言**：跟随界面 / 简体中文 / English——决定通知文字与 `🔔 …` 标题标记使用的语言；
-- **桌面端怎么抬窗**：页面侧的 `window.focus()` 在 Electron 里抬不动原生窗口，1.5.2 起改走应用自己的 `dsh://open` 深链调窗——在 DSH Desktop 0.2.0-rc.2 上实测有效，0.2.1-rc.2 在 Windows 上失效（详见下一节）；
+- **桌面端怎么抬窗**：页面侧的 `window.focus()` 在 Electron 里抬不动原生窗口，1.5.2 起改走应用自己的 `dsh://open` 深链调窗——在 DSH Desktop 0.2.0-rc.2 上实测有效，0.2.1-rc.2 在 Windows 上不稳定（详见下一节）；
 - **恢复默认设置**：把所有开关与音效设置还原成出厂值（不动外部推送目标和已选的自定义音频文件）。
 
 </details>
@@ -196,7 +197,9 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 ## 五种提醒渠道
 
 - **系统通知**：经浏览器弹出的系统通知，进 Windows 通知中心或 macOS 通知中心（点击回到提醒所属的对话；支持快捷裁决的 Web 环境可点审批按钮直接裁决，桌面端无按钮）
-- **页面浮层**（可选，默认关）：画在 DSH 页面角落的提醒卡片，落在窗口所在的那块屏，可带「同意 / 拒绝」按钮；见[副屏与浮层提醒](#副屏与浮层提醒)
+- **页面浮层**：画在 DSH 页面角落的提醒卡片，落在窗口所在的那块屏，可带「同意 / 拒绝」按钮；见[副屏与浮层提醒](#副屏与浮层提醒)
+
+两种渠道在设置里二选一，不会同时出现。
 - **提示音**：默认是 WebAudio 合成音（「需要你」与「完成」使用不同音型）；可在设置里为两类提醒分别换成自定义音频文件，或改成让操作系统播放它自己的通知音
 - **标签页标题标记**：有待处理事项时，标题前出现 `🔔 需要你 · …` / `🔔 Action needed · …`；后台会话**完成但还没看**时出现 `✅ 回复完成 · …` / `✅ Reply finished · …`，打开对应会话（或它再次开跑）即消失。两种标记可同时出现，「需要你」在前；宿主改写标题后标记基于新标题重建
 - **外部通知**（可选，默认关）：按设置里配的推送目标，把同一条提醒转发到 Discord Webhook / Bark / Gotify / 自定义 Webhook——临时离开电脑时，手机上的推送渠道照样收到
@@ -246,14 +249,14 @@ window.__dshNotifyMe.setConfig({
   currentHiddenOnly: true,    // true = 当前对话的等待只留标题标记（转后台补发）
   doneHiddenOnly: true,       // false = 页面可见时「完成」也提醒
   ignoreSubagent: true,       // true = 后台子代理（subagent）会话不提醒（当前打开的照常）
-  toast: true,                // 系统通知开关
+  channel: "toast",          // 提醒方式：'toast' 系统通知 | 'overlay' 页面浮层，二选一
   sound: true,                // 提示音开关（含「系统通知音」模式）
   soundDone: "synth",         // 「完成」音效来源：'synth' 内置 | 'custom' 自定义文件 | 'system' 系统通知音
   soundAttention: "synth",    // 「需要你」音效来源，取值同上
   volume: 0.5,                // 音量 0~1
   autoFocus: true,            // 点通知回到提醒所属的对话
   quickActions: true,         // 审批通知上的「同意 / 拒绝」按钮
-  overlay: false,             // 页面浮层提醒（跟着 DSH 窗口落在哪块屏；不需要通知权限）
+  overlay: false,             // 兼容字段，跟随 channel 同步（老配置靠它迁移）
   overlayCorner: "bottom-right", // 浮层位置：'top-right' | 'bottom-right' | 'top-left' | 'bottom-left'
   externalEnabled: false,     // 外部通知转发主开关（默认关：不填端点就什么都不发）
   externalAttention: true,    // 转发「需要你」（触发规则跟本地提醒完全一致）
@@ -301,7 +304,11 @@ DSH Desktop 是一层 Electron 壳，页面跑在 `dsh-app://app` 下：DOM 的
 
 真实壳已实测（DSH Desktop 0.2.0-rc.2，issue #9 三轮复测）：点通知 = 抬窗 + 切会话一步到位，跨会话、窗口在后台时同样稳定。触发时机是这条链路的关键：深链必须在**带用户手势的处理器**里发——通知的 `onclick` 自带手势，所以产品路径通；而无手势的脚本化注入（如 CDP evaluate 手工塞 iframe）会被 Chromium 静默丢弃、外部协议根本不回流，复现时看起来就像「通道被拦死」。
 
-**0.2.1-rc.2 在 Windows 上失效**（2026-10-20 实测）：点通知的回调照常执行（`navigator.userActivation.isActive === true`、`visibilityState` 为 `hidden`），但窗口不再上前台。壳侧可复现的证据：带 `dsh://open` 参数启动第二实例，133 ms 后以退出码 1 结束；不带参数时 258 ms 退出码 0（正常的单实例让位），说明问题出在 URL 参数那条分支。把窗口用 `WM_SYSCOMMAND` 真实最小化后，无论发深链还是无参重启，`IsIconic` 都保持 `true`，`focusPrimaryWindow()` 的 `restore()` 没有实际生效。页面侧也没有替代通道：壳的 preload 只暴露 `dshDesktop`、目录选择、本地化这些，`DESKTOP_IPC` 里没有 focus/raise 类通道。已把复现步骤与代码位置提交到 [deepseek-harness discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446)。插件侧能做的到此为止：深链照发，原生窗口抬不抬由壳决定。
+**0.2.1-rc.2 在 Windows 上不稳定**（2026-10-20）：点通知的回调照常执行（`navigator.userActivation.isActive === true`、`visibilityState` 为 `hidden`），但窗口是否上前台时灵时不灵——有时会，有时只切对话、窗口不动。
+
+插件这一侧为什么不能指望：把 `dsh://open` 深链单独拿出来复测（三种走法各 3 次：直接带参启动 exe、走系统协议激活、`WM_SYSCOMMAND` 真实最小化后再发），**全部失败**——带参第二实例每次都在约 130 ms 后以退出码 1 结束（不带参数则约 260 ms 退出码 0，属正常单实例让位），最小化窗口的 `IsIconic` 每次都保持 `true`。也就是说，能抬起来的那些次，多半是系统/Chromium 在通知被点击时自己激活了应用窗口，不是插件发的深链起了作用。
+
+页面侧也没有替代通道：壳的 preload 只暴露 `dshDesktop`、目录选择、本地化这些，`DESKTOP_IPC` 里没有 focus/raise 类通道；主窗口的 `will-navigate` 对 `dsh:` 一律 `preventDefault()`。复现步骤与代码位置已提交到 [deepseek-harness discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446)。
 
 </details>
 
@@ -309,7 +316,7 @@ DSH Desktop 是一层 Electron 壳，页面跑在 `dsh-app://app` 下：DOM 的
 
 - 页面必须开着才会提醒（后台标签/最小化可以；关标签页即失效——浏览器层方案固有限制）。
 - 通知经由浏览器弹出，需允许浏览器通知权限，且勿扰模式不能屏蔽它。
-- 桌面端（DSH Desktop 0.2.1-rc.2 / Windows）点通知不再自动把窗口带到前台：插件能发 `dsh://open` 深链，壳侧却没把窗口抬起来（[discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446)）；切到对应对话不受影响。
+- 桌面端（DSH Desktop 0.2.1-rc.2 / Windows）点通知后窗口不一定上前台：有时会，有时只切对话。插件发的 `dsh://open` 深链单独复测 3/3 无效（详见[桌面端怎么抬窗的](#桌面端怎么抬窗的)），能抬的时候多半是系统/Chromium 在通知激活时自己把窗口带起来了（[discussions #10446](https://github.com/deepseek-ai/deepseek-harness/discussions/10446)）。
 - 系统通知横幅只画在主屏：Windows 没有设置项、Chromium 没有 API 能把它指到别的显示器（多屏时副屏收不到系统通知）。要用副屏提醒，开「页面浮层提醒」，它会跟着 DSH 窗口走。
 - 每次页面加载后第一次出声/弹通知前，需在页面上点击过一次（浏览器自动播放与权限策略）。
 - 未授权通知权限时只有提示音与标题标记。

package/lib/client.js

@@ -256,15 +256,19 @@
       // through the Service Worker half of this same file; where that cannot
       // run, the toast simply falls back to its plain form.
       quickActions: true,
-      // Where the alert is drawn. The OS toast always lands on the primary
-      // display — Windows offers no setting (and Chromium no API) to aim a
-      // banner at another monitor — so a user whose DSH window lives on a
-      // second screen never sees one. This option draws the same alert inside
-      // the page instead: it appears on whatever screen the window is on, needs
-      // no notification permission, and can carry the approval buttons even on
-      // the desktop shell (whose dsh-app:// page cannot run the Service Worker
-      // that OS action buttons need). Independent of `toast`; neither replaces
-      // the other, so "both" is a valid setup.
+      // The alert channel: exactly one of them, never both.
+      //   'toast'   — the OS notification center. Always drawn on the primary
+      //               display (Windows offers no setting and Chromium no API to
+      //               aim a banner at another monitor), needs notification
+      //               permission, and cannot carry action buttons on the desktop
+      //               shell.
+      //   'overlay' — a card inside the page, so it follows the DSH window to
+      //               whatever display it sits on, needs no permission, and can
+      //               carry the approval buttons even on the desktop shell.
+      channel: "toast",
+      // Legacy mirrors of `channel`, kept in sync on every read/write so that a
+      // config written by an older build, or a console poke at one of them,
+      // still means what it used to.
       overlay: false,
       // Which corner of this window the overlay cards stack in. The screen
       // follows the window — the page cannot aim it anywhere else either.
@@ -285,12 +289,31 @@
         var raw = localStorage.getItem(LS_CONFIG);
         if (raw) cfg = JSON.parse(raw);
       } catch (e) { /* corrupt storage -> defaults */ }
+      // Older builds stored two independent switches; the channel is now a
+      // single choice, and a config that had the overlay on keeps using it.
+      // Checked before the defaults fill in `channel`, or the fresh default
+      // would shadow the legacy keys.
+      if (typeof cfg.channel !== "string") {
+        cfg.channel = cfg.overlay === true ? "overlay" : "toast";
+      }
       for (var k in DEFAULTS) if (!(k in cfg)) cfg[k] = DEFAULTS[k];
+
+      cfg.toast = cfg.channel === "toast";
+      cfg.overlay = cfg.channel === "overlay";
       return cfg;
     }
     function writeConfig(patch) {
       var cfg = readConfig();
       for (var k in patch) cfg[k] = patch[k];
+      if (!("channel" in patch)) {
+        if (patch.overlay === true) cfg.channel = "overlay";
+        else if (patch.overlay === false && cfg.channel === "overlay") cfg.channel = "toast";
+        if (patch.toast === true) cfg.channel = "toast";
+        else if (patch.toast === false && cfg.channel === "toast") cfg.channel = "overlay";
+      }
+      cfg.channel = cfg.channel === "overlay" ? "overlay" : "toast";
+      cfg.toast = cfg.channel === "toast";
+      cfg.overlay = cfg.channel === "overlay";
       try { localStorage.setItem(LS_CONFIG, JSON.stringify(cfg)); } catch (e) {}
       return cfg;
     }
@@ -303,7 +326,7 @@
       // Overlay re-apply: switching it off takes the cards down at once and a
       // new corner moves the layer without waiting for the next alert.
       try {
-        if (!config.overlay) clearOverlays();
+        if (config.channel !== "overlay") clearOverlays();
         else if (overlayLayer) overlayLayer.className = "dnm-ov-layer dnm-ov-" + overlayCorner();
       } catch (e) {}
       return config;
@@ -436,7 +459,7 @@
       } catch (e) {}
     }
     function canToast() {
-      if (!config.toast) return false;
+      if (config.channel !== "toast") return false;
       try {
         return "Notification" in window && Notification.permission === "granted";
       } catch (e) { return false; } // a policy-disabled Notification must not break delivery
@@ -682,10 +705,11 @@
     // they are the only kind whose decision is a plain binary, and the only one
     // whose object answers answer('allowed-once' | 'rejected').
     function quickFor(key, it, sessionId) {
-      // The overlay can settle approvals without a worker, so it counts as a
-      // button channel on its own — the desktop shell, where OS action buttons
-      // cannot render, gets them this way.
-      if (!config.quickActions || !(config.toast || config.overlay)) return null;
+      // The buttons themselves are a rendering concern: the overlay always
+      // draws them, and a toast needs a live worker bridge for OS actions. The
+      // pending record is kept either way, so a click still settles the same
+      // decision (and debug().actionKeys stays honest about what is waiting).
+      if (!config.quickActions) return null;
       if (!it || it.kind !== "approval" || typeof it.answer !== "function") return null;
       var q = {
         key: key,
@@ -756,7 +780,9 @@
             n.close();
           };
         }
-        setTimeout(function () { n.close(); }, 15000);
+        // Longer for an actionable toast so there is time to click it, shorter
+        // for a plain one: a notification that just sits there is noise.
+        setTimeout(function () { n.close(); }, quick ? 20000 : 10000);
       } catch (e) {}
     }
 
@@ -772,9 +798,10 @@
     var OVERLAY_STYLE_ID = "dsh-notify-me/overlay";
     var OVERLAY_ID = "dsh-notify-me-overlay";
     var OVERLAY_MAX_CARDS = 4;
-    // An approval card is actionable and stays until it is answered or closed;
-    // the other kinds fade on the toast's own schedule (a toast closes at 15s).
-    var OVERLAY_TTL = { attention: 20000, done: 8000 };
+    // How long a card stays. "needs you" deserves a longer look than a finished
+    // reply; actionable cards get the longest window but still fade, because a
+    // card that never leaves is just clutter once the user has moved on.
+    var OVERLAY_TTL = { attention: 12000, done: 6000, action: 18000 };
     var OVERLAY_CORNERS = ["bottom-right", "bottom-left", "top-right", "top-left"];
     var OVERLAY_CSS = "" +
       ".dnm-ov-layer{position:fixed;z-index:2147483000;display:flex;flex-direction:column;gap:10px;pointer-events:none;max-width:calc(100vw - 24px)}" +
@@ -871,7 +898,7 @@
     // Same inputs as showToast: `quick` is the approval record built by
     // quickFor(), and it is what lets an overlay settle the request in place.
     function showOverlay(kind, title, body, sessionId, quick) {
-      if (!config.overlay) return false;
+      if (config.channel !== "overlay") return false;
       var layer = ensureOverlayLayer();
       if (!layer) return false;
       var d = texts();
@@ -937,10 +964,10 @@
         overlayCards[id] = rec;
         var ids = Object.keys(overlayCards);
         for (var i = 0; i < ids.length - OVERLAY_MAX_CARDS; i++) dismissOverlay(ids[i]);
-        if (!(quick && typeof quick.key === "string")) {
-          var ttl = OVERLAY_TTL[kind === "attention" ? "attention" : "done"];
-          if (ttl) rec.timer = setTimeout(function () { dismissOverlay(id); }, ttl);
-        }
+        var ttl = (quick && typeof quick.key === "string")
+          ? OVERLAY_TTL.action
+          : OVERLAY_TTL[kind === "attention" ? "attention" : "done"];
+        if (ttl) rec.timer = setTimeout(function () { dismissOverlay(id); }, ttl);
         return true;
       } catch (e) { return false; }
     }
@@ -1937,7 +1964,7 @@
       });
     } catch (e) {}
     // keep in sync with package.json "version" on every release
-    api.version = "1.9.4";
+    api.version = "1.10.0";
     api.setConfig = function (patch) { return setConfigLocal(patch); };
     api.resetConfig = function () {
       try {
@@ -1998,6 +2025,7 @@
         currentHiddenOnly: config.currentHiddenOnly,
         doneHiddenOnly: config.doneHiddenOnly,
         ignoreSubagent: config.ignoreSubagent,
+        channel: config.channel,
         toast: config.toast,
         sound: config.sound,
         soundDone: soundMode("done"),
@@ -2073,7 +2101,7 @@
       enable: "启用提醒",
       enableHint: "关闭后不弹通知、不响提示音，也不改标签页标题。",
       hostEnv: "运行环境",
-      hostEnvHint: "默认自动识别：页面协议是 dsh-app:// 即桌面端（DSH Desktop），其余为 Web 端。识别不准时手动指定：桌面端走 dsh:// 深链调窗（能否真的上前台看壳的版本）、快捷裁决按钮不可用；Web 端走 window.focus() 与 Service Worker 桥。",
+      hostEnvHint: "默认自动识别：页面协议是 dsh-app:// 即桌面端（DSH Desktop），其余为 Web 端。识别不准时手动指定：桌面端走 dsh:// 深链调窗（效果不稳定），系统通知不带按钮、浮层才带；Web 端走 window.focus() 与 Service Worker 桥。",
       hostEnvAuto: "自动识别（推荐）",
       hostEnvDesktop: "桌面端（DSH Desktop）",
       hostEnvWeb: "Web 端（浏览器）",
@@ -2081,7 +2109,7 @@
       hostEnvMismatchTail: "」，手动选择会覆盖它）",
       hostEnvDesktopForcedNote: "（当前页面不是 dsh-app://：点通知会尝试唤起 dsh:// 协议，浏览器可能弹「打开应用」确认框）",
       toast: "系统通知",
-      toastHint: "经浏览器弹系统通知（Windows 通知中心），需要通知权限。",
+      toastHint: "走系统通知中心，需要通知权限；桌面端这类通知没有「同意 / 拒绝」按钮。",
       sound: "提示音",
       soundHint: "提示音总开关；播什么由「高级设置 → 音效来源」决定。",
       soundSource: "音效来源",
@@ -2153,9 +2181,9 @@
       quickApprovalNote: "「同意」等价于审批卡片上的「允许一次」，只放行这一次。",
       bridgeOff: "快捷裁决按钮暂不可用（",
       bridgeOffTail: "）：审批通知会退回不带按钮的普通样式。",
-      bridgeOffDesktop: "桌面端暂不支持快捷裁决按钮：dsh-app:// 页面无法注册 Service Worker，审批通知只能是不带按钮的普通样式，测试按钮同样只发普通通知。这是宿主限制，不是设置坏了。",
+      bridgeOffDesktop: "系统通知没有「同意 / 拒绝」按钮：桌面端页面（dsh-app://）注册不了 Service Worker（宿主少给 allowServiceWorkers 特权），按钮发不出来。想一键裁决就把「提醒方式」切到「页面浮层」。",
       overlay: "页面浮层提醒",
-      overlayHint: "在页面角落画提醒卡片：窗口在哪块屏，它就在哪块屏。系统通知只会出现在主屏，主屏不看时用它。不需要通知权限，桌面端也能直接「同意 / 拒绝」，可与系统通知同开。",
+      overlayHint: "在窗口角落画提醒卡片：窗口在哪块屏，它就在哪块屏；系统通知只会出现在主屏，主屏不看时用它。不需要通知权限，卡片上能直接「同意 / 拒绝」。与上面二选一，选它就不再弹系统通知。",
       overlayCorner: "浮层位置",
       overlayCornerHint: "贴在 DSH 窗口的哪个角；窗口在哪块屏，浮层就出现在哪块屏。",
       overlayPosTR: "右上",
@@ -2200,7 +2228,7 @@
       enable: "Enable reminders",
       enableHint: "When off: no toasts, no sounds, and the tab title is left alone.",
       hostEnv: "Environment",
-      hostEnvHint: "Auto-detect by default: a dsh-app:// page is the Desktop (DSH Desktop) shell, anything else is the Web. Override it if detection comes out wrong: on the Desktop a toast click fires the dsh:// deep link (whether the window actually comes forward depends on the shell version) and quick-decision buttons are unavailable; on the Web it is window.focus() plus the Service Worker bridge.",
+      hostEnvHint: "Auto-detect by default: a dsh-app:// page is the Desktop (DSH Desktop) shell, anything else is the Web. Override it if detection comes out wrong: on the Desktop a toast click fires the dsh:// deep link (the effect is unreliable) and system notifications carry no buttons (the overlay does); on the Web it is window.focus() plus the Service Worker bridge.",
       hostEnvAuto: "Auto-detect (recommended)",
       hostEnvDesktop: "Desktop (DSH Desktop)",
       hostEnvWeb: "Web (browser)",
@@ -2208,7 +2236,7 @@
       hostEnvMismatchTail: "\"; the manual choice overrides it)",
       hostEnvDesktopForcedNote: " (this page is not dsh-app://: a toast click will try to launch the dsh:// protocol and the browser may show an \"open app?\" prompt)",
       toast: "System notifications",
-      toastHint: "Native toasts through the browser (Windows notification center); needs notification permission.",
+      toastHint: "Through the system notification center; needs notification permission, and on the Desktop these carry no Approve / Reject buttons.",
       sound: "Sound",
       soundHint: "Master cue switch; what it plays comes from Advanced → Alert sound.",
       soundSource: "Alert sound",
@@ -2280,9 +2308,9 @@
       quickApprovalNote: "\"Approve\" equals \"Allow once\" on the approval card — it allows that one call only.",
       bridgeOff: "Quick-decision buttons are unavailable right now (",
       bridgeOffTail: "); approval toasts fall back to their plain form.",
-      bridgeOffDesktop: "Quick-decision buttons are unavailable on Desktop: dsh-app:// pages cannot register a Service Worker, so approval toasts fall back to their plain, button-less form and the test button only sends a plain notification. This is a host limitation, not a broken setting.",
+      bridgeOffDesktop: "System notifications carry no Approve / Reject buttons: dsh-app:// pages cannot register a Service Worker (the shell does not grant the allowServiceWorkers privilege), so the buttons cannot be attached. Switch the alert channel to the in-page overlay to settle approvals in one click.",
       overlay: "In-page overlay",
-      overlayHint: "Draw a card in the page corner, on whatever display the window sits on. System notifications only land on the primary display. No permission needed, and the Desktop shell can Approve / Reject right on the card. Can run with toasts on.",
+      overlayHint: "Draw a card in the window corner, on whatever display the window sits on. System notifications only land on the primary display. No permission needed, and the card carries Approve / Reject directly. Pick this or the system notification above: choosing it stops system notifications.",
       overlayCorner: "Overlay position",
       overlayCornerHint: "Which corner of the DSH window the cards stack in; they follow the window to whatever display it is on.",
       overlayPosTR: "Top right",
@@ -2419,6 +2447,9 @@
       ".dnm-switch.on{background:var(--dsw-alias-state-business-primary,#3b82f6);border-color:transparent}" +
       ".dnm-knob{position:absolute;top:2px;left:2px;width:14px;height:14px;border-radius:50%;background:#fff;transition:left .15s ease}" +
       ".dnm-switch.on .dnm-knob{left:16px}" +
+      ".dnm-radio{flex:none;width:16px;height:16px;margin:0;accent-color:var(--dsw-alias-state-business-primary,#3b82f6);cursor:pointer}" +
+      ".dnm-rowRadio{justify-content:flex-start;gap:10px}" +
+      ".dnm-rowRadio .dnm-rowText{flex:1}" +
       ".dnm-range{width:150px;accent-color:var(--dsw-alias-state-business-primary,#3b82f6)}" +
       ".dnm-select{border:1px solid var(--dsw-alias-border-l2,rgba(128,128,128,.4));background:var(--dsw-alias-bg-layer-1,rgba(255,255,255,.03));color:var(--dsw-alias-label-primary,rgba(20,20,20,.9));border-radius:8px;padding:5px 8px;font-size:13px;font-family:inherit}" +
       ".dnm-btn{border:1px solid var(--dsw-alias-border-l2,rgba(128,128,128,.4));background:transparent;color:var(--dsw-alias-label-primary,rgba(20,20,20,.9));border-radius:8px;padding:5px 12px;font-size:13px;cursor:pointer;font-family:inherit}" +
@@ -2876,6 +2907,27 @@
       function secTitle(labelText) {
         return h("div", { className: "dnm-secTitle" }, labelText);
       }
+      // One channel at a time, so the pair renders as radios, not switches. The
+      // radio sits ahead of the label: two rows sharing one choice read as a
+      // list of options, which a lone dot on the far right does not.
+      function rowRadio(labelText, hintText, checked, onChange) {
+        var pick = function () { if (!checked) onChange(); };
+        return tipRow("dnm-row dnm-rowRadio", hintText, [
+          h("input", {
+            type: "radio",
+            className: "dnm-radio",
+            name: "dnm-alert-channel",
+            checked: !!checked,
+            "aria-label": labelText,
+            onChange: pick,
+            onClick: pick
+          }),
+          h("div", { className: "dnm-rowText" }, [
+            h("div", { className: "dnm-rowLabel" }, labelText),
+            srOnly(hintText)
+          ])
+        ]);
+      }
       // The permission state belongs on the System-notifications row it affects
       // rather than in a footer note the user has to connect to it.
       function toastHintText() {
@@ -2911,9 +2963,9 @@
             patch({ enabled: v });
             if (!v && attentionActive > 0) { attentionActive = 0; applyTitle(); }
           }),
-          rowSwitch("toast", t("toast"), toastHintText(), cfg.toast, function (v) { patch({ toast: v }); }),
-          rowSwitch("overlay", t("overlay"), t("overlayHint"), cfg.overlay, function (v) { patch({ overlay: v }); }),
-          cfg.overlay ? tipRow("dnm-row dnm-rowSub", t("overlayCornerHint"), [
+          rowRadio(t("toast"), toastHintText(), cfg.channel !== "overlay", function () { patch({ channel: "toast" }); }),
+          rowRadio(t("overlay"), t("overlayHint"), cfg.channel === "overlay", function () { patch({ channel: "overlay" }); }),
+          cfg.channel === "overlay" ? tipRow("dnm-row dnm-rowSub", t("overlayCornerHint"), [
             h("div", { className: "dnm-rowText" }, [
               h("div", { className: "dnm-rowLabel" }, t("overlayCorner")),
               srOnly(t("overlayCornerHint"))
@@ -2966,7 +3018,7 @@
           !cfg.quickActions ? h("div", { className: "dnm-row" }, [
             h("div", { className: "dnm-rowText" }, [h("div", { className: "dnm-rowHint" }, t("testNeedsQuick"))])
           ]) : h("div", { className: "dnm-row" }, [
-            h("div", { className: "dnm-rowText" }, [h("div", { className: "dnm-rowHint" }, cfg.overlay ? t("overlayQuickNote") : (cfg.toast && !bridgeActive() ? (isDesktopShell() ? t("bridgeOffDesktop") : t("bridgeOff") + swState + t("bridgeOffTail")) : t("quickApprovalNote")))])
+            h("div", { className: "dnm-rowText" }, [h("div", { className: "dnm-rowHint" }, cfg.channel === "overlay" ? t("overlayQuickNote") : (!bridgeActive() ? (isDesktopShell() ? t("bridgeOffDesktop") : t("bridgeOff") + swState + t("bridgeOffTail")) : t("quickApprovalNote")))])
           ]),
           feedback ? h("div", { className: "dnm-row" }, [
             h("div", { className: "dnm-rowText" }, [h("div", { className: "dnm-feedback" }, feedback)])

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-notify-me",
-  "version": "1.9.4",
+  "version": "1.10.0",
   "description": "离开 DSH 页面也能收到提醒：需要你操作 / 后台回复完成时发系统通知、标题标记与可选页面浮层（副屏也能看见），支持审批快捷裁决与外部推送。Brand icon and a reworked settings page in 1.9.0.",
   "license": "MIT",
   "type": "module",