dsh-notify-me 1.10.5 → 1.11.0

package/CHANGELOG.md

@@ -2,6 +2,33 @@
 
 All notable changes to **dsh-notify-me** are documented here.
 
+## [1.11.0] — 2026-10-21
+
+### 移除
+
+- **「提醒方式」二选一整段删掉**：系统通知成了唯一通道，设置页不再有「通知类型」分段选择器。页面浮层当独立通道的用途是「窗口在哪块屏，卡片就在哪块屏」，可它只在 DSH 窗口处于前台时看得见——需要提醒的时刻恰恰是窗口在后台。选了浮层、切走之后，后台只剩提示音和标题标记，等于没提醒；1.10.6 想在后台补发系统通知，又违背了你选的通道。两个方向都不成立，所以直接去掉这个选项。
+- `channel` / `overlay` / `toast` 三个配置键失效。旧配置里的值在下次读配置时删掉，其余设置不受影响（`overlayCorner` 保留）。
+- `window.__dshNotifyMe.debug()` 里的 `channel`、`toast` 被去掉，`overlay` 改名为 `card`，只报告桌面端审批卡片（`enabled` / `corner` / `cards`）。
+
+### 保留
+
+- **桌面端审批卡片**：`dsh-app://` 注册不了 Service Worker，系统通知带不了「同意 / 拒绝」，所以审批类提醒仍在窗口角落画一张可点击的卡片（12 秒回收，同一条审批不叠第二张）。位置改由「提醒方式 → 审批通知上直接裁决」下面的「审批卡片位置」决定，与已删除的通道无关。
+- 1.10.5 的「窗口失焦也算后台」与 1.10.7 的行为原样保留。
+
+### 测试
+
+- 冒烟删掉浮层通道用例（`overlayChannel`、`settingsOverlayRow`），换成 `cardLayer`（卡片只给审批、四角位置、卡片上的审批按钮能裁决）与 `settingsAlertSetup`（设置页没有通道分段选择器、审批卡片位置子行在、旧配置的 `channel` 被清掉）。
+
+## [1.10.7] — 2026-10-21
+
+### 撤销
+
+- **1.10.6 的「浮层通道在后台补发系统通知」整条撤销**。它把「选浮层」变成了「浮层 + 后台时又弹系统通知」，等于绕过了用户明确选定的通道——用户的反馈是「我选的不是浮层提醒吗，为什么弹系统通知」。现在恢复 1.10.5 的行为：选了浮层就只画页面卡片，窗口被挡住时后台只有提示音和标题标记，系统通知一条都不发。想要后台可见的提醒，请把「通知类型」切到「系统通知」。
+
+### 说明
+
+- 1.10.5 的「窗口失焦也算后台」保留不动：它决定的是「要不要提醒」，与「用哪个通道提醒」无关。
+
 ## [1.10.5] — 2026-10-21
 
 ### 修复

package/README.en.md

@@ -26,9 +26,9 @@ 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:** 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).
+- **When you do not watch the primary display:** system notifications only ever appear on the primary display; the Desktop approval card is drawn in the page and follows the DSH window onto whichever screen it is on (see [Secondary displays and the approval card](#secondary-displays-and-the-approval-card)).
 
-> 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)).
+> Keep the page or desktop app running; backgrounding / minimizing is fine. System notifications require permission. Approval buttons need a Service Worker: Web (`http://127.0.0.1` or `https`) has one, the Desktop `dsh-app://` pages cannot register one, so their notifications carry no buttons and approvals are decided on a card in the window corner instead.
 
 > 🔎 Looking for it? Search `dsh-notify-me`, **message alerts**, **notification**, **desktop notification**, **reminder**, **approval alert**, **external notifications**, **Discord / Bark / Gotify push** or **可操作提醒 / 消息提醒 / 桌面通知 / 需要你操作** (npm keywords include both English and Chinese terms).
 
@@ -38,16 +38,12 @@ A notification plugin for DSH Web / Desktop, so you can keep full access off wit
 
 *Plain notification example · Windows / Edge · no approval buttons.* [View full size](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/notify-toast.png)
 
-![Three overlay cards in the bottom-right corner of the DSH page: question, approval request with Approve / Reject, and reply finished](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/overlay-en.png)
-
-*In-page overlay · the real plugin rendered on a demo page · for when system notifications cannot reach the secondary display; cards appear on whichever display the DSH window is on.* [View full size](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/overlay-en.png)
-
 <details>
 <summary>See the settings interface</summary>
 
 ![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)
 
-Just the plugin panel (the real component, v1.10.2 defaults) without the DSH navigation sidebar. Alert type is a segmented control, 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.
+Just the plugin panel (the real component, captured before 1.11.0) without the DSH navigation sidebar. Row explanations live in a hover tooltip that appears when the pointer rests on a title, which is why only the titles show here. 1.11.0 removed the "alert type" row at the top; the rest is unchanged.
 </details>
 
 ## Installation
@@ -74,7 +70,7 @@ The Electron application manages the `desktop` profile. Do not change the Web co
 ## First-use check
 
 1. Click once in the DSH page and allow notifications when prompted. If you previously declined, allow them in the browser's site settings. The operating system must also allow notifications from the browser / DSH Desktop.
-2. Open **Settings → Notify me**. Confirm that the section and plugin version at its foot appear, and leave the master switch, the alert type on system notifications, and sound enabled.
+2. Open **Settings → Notify me**. Confirm that the section and plugin version at its foot appear, and leave the master switch and sound enabled.
 3. Click **Test "reply finished"** on the settings page. A test notification should appear and sound according to your cue settings. This local test does not forward to external endpoints and ignores the "while the window is in front" toggle.
 
 Web users can also test approval buttons. On Desktop the shell cannot register a Service Worker, so this test draws an in-page card with Approve / Reject in the window corner (since 1.10.4; earlier versions sent a plain notification).
@@ -121,25 +117,21 @@ 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;
-- **Alert type (pick one)**: one segmented control — system notifications on the left, in-page overlay on the right; whichever you pick is the only channel used;
-  - **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. With the overlay chosen, a Corner row appears; open it to pick one of four positions. See [Secondary displays and the overlay](#secondary-displays-and-the-overlay);
 - **Sound / Volume**: the switch is direct; the slider folds into that row — click the title (▸ turns into ▾) to reveal it. What it plays comes from Advanced → Alert sound;
-- **Decide approvals from the toast** (on by default): approvals carry Approve / Reject that settle the request in place. On Web that is a system notification with buttons; on Desktop `dsh-app://` cannot register a Service Worker, so the buttons are drawn on a card in the window corner (auto-dismissed after 12 s, one card per approval). You can also switch the channel to the in-page overlay and decide there.
+- **Decide approvals from the toast** (on by default): approvals carry Approve / Reject that settle the request in place. On Web that is a system notification with buttons; on Desktop `dsh-app://` cannot register a Service Worker, so the buttons are drawn on a card in the window corner (auto-dismissed after 12 s, one card per approval). Its corner comes from the Corner sub-row underneath — see [Secondary displays and the approval card](#secondary-displays-and-the-approval-card).
 
-### Secondary displays and the overlay
+### Secondary displays and the approval card
 
-Windows draws system notification banners on the primary display only. There is no setting in Windows and no API in the browser to aim one at another monitor, so with DSH parked on a second screen and the primary display unwatched, a toast is as good as not sent.
+Windows draws system notification banners on the primary display only. There is no setting in Windows and no API in the browser to aim one at another monitor, so with DSH parked on a second screen and the primary display unwatched, a toast is as good as not sent. That part is out of reach — the only thing that can show up on the other screen comes from inside the page.
 
-The **in-page overlay** skips the notification center and draws the card inside the DSH page instead: wherever the window is, the card is there too.
+One thing does: the Desktop approval card. It is drawn in the DSH page, so it appears on whichever display the window sits on, and it carries Approve / Reject (Desktop toasts have no buttons).
 
-- **Position** — with the in-page overlay chosen, a Corner row appears showing the current value (bottom right by default); click it open (▸ turns into ▾), then pick top right / bottom right / top left / bottom left. 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" and "reply finished" cards retire after 5s each, an approval card with buttons after 12s (system toasts use the same two numbers); 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 made it a single choice, and 1.10.2 turns that into one segmented row. An old config with the overlay on migrates to it.
+- **Position** — the Corner sub-row under "Decide approvals from the toast" shows the current value (bottom right by default); click it open (▸ turns into ▾), then pick top right / bottom right / top left / bottom left. Changes apply immediately;
+- **Approvals only** — plain "needs you" and "reply finished" alerts never draw a card; they are system notifications only;
+- **Lifetime** — an approval card retires after 12 s; clicking the card body opens its conversation. At most 4 cards stack at once;
+- **No notification permission needed** — this path touches no Service Worker and needs no permission.
 
-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.
+> 1.11.0 removed the "alert type" choice. The in-page overlay used to work as a standalone channel, but it is only visible while the DSH window is in front — and the moment an alert matters is exactly when the window is in the background. With the overlay chosen, backgrounding left only the sound and the tab marker, which is no alert at all.
 
 ### When to alert
 
@@ -200,9 +192,8 @@ The last block inside Advanced. The page protocol is detected automatically to t
 
 ## How it alerts
 
-- **Alert channel (pick one — the two never run together)**:
-  - **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** — 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)
+- **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)
+- **Desktop approval card** — `dsh-app://` cannot put Approve / Reject on a toast, so approval alerts also drop a clickable card in the window corner; see [Secondary displays and the approval card](#secondary-displays-and-the-approval-card)
 - **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
@@ -252,15 +243,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)
-  channel: "toast",          // alert channel: 'toast' system notification | 'overlay' in-page card, pick one
+  quickActions: true,         // Approve / Reject on approval alerts
   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,             // 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'
+  overlayCorner: "bottom-right", // Desktop approval card 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)
   externalDone: true,         // forward "reply finished"
@@ -322,7 +312,7 @@ There is no page-side fallback either: the shell preload only exposes `dshDeskto
 - 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 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.
+- 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. The one thing that does reach another display is the Desktop approval card, drawn in the page and carried by the window; for plain alerts across screens, forward them to your phone with external notifications.
 - 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.
 - Config lives in browser `localStorage`: switching browsers/devices or clearing site data returns to defaults (one-click restore in the Settings page).

package/README.md

@@ -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-app://` 页面注册不了，通知上没有按钮，审批改在窗口角落的卡片上裁决。
 
 > 🔎 想找这个插件？可以搜：`dsh-notify-me`、**消息提醒**、**可操作提醒**、**桌面通知**、**需要你操作**、**回复完成提醒**、**后台完成提醒**、**外部通知**、**Discord / Bark / Gotify 推送**（npm 关键词已含以上中英文词）。
 
@@ -38,16 +38,12 @@ DSH Web / Desktop 的通知插件，让你敢不开完整访问，也不必一
 
 *普通通知示例 · Windows / Edge · 不含审批按钮。* [查看原图](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/notify-toast.png)
 
-![DSH 页面右下角的三张浮层提醒：提问、审批请求（带「同意 / 拒绝」按钮）、回复完成](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/overlay-zh.png)
-
-*页面浮层提醒 · 真实插件在独立演示页里渲染 · 系统通知画不到副屏时用它，卡片落在 DSH 窗口所在的那块屏。* [查看原图](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/overlay-zh.png)
-
 <details>
 <summary>展开设置界面预览</summary>
 
 ![通知提醒设置页：页眉、提醒方式、什么时候提醒、试一试与折叠的高级设置](https://raw.githubusercontent.com/chromoany/dsh-notify-me/main/docs/screenshots/settings-zh.png)
 
-只截插件自己的面板（真实组件、v1.10.2 默认配置），不带 DSH 左侧导航栏；「通知类型」是分段选择器，每行说明在鼠标停在标题文字上时才出现，所以这里只看到标题。
+只截插件自己的面板（真实组件，1.11.0 之前的截图），不带 DSH 左侧导航栏；每行说明在鼠标停在标题文字上时才出现，所以这里只看到标题。1.11.0 删掉了最上面的「通知类型」一行，其余行没变。
 </details>
 
 ## 安装
@@ -74,7 +70,7 @@ dsh plugin --profile web add dsh-notify-me
 ## 首次验证
 
 1. 在 DSH 页面上点击一次，按提示允许通知；若此前拒绝过，在浏览器站点设置中允许通知。操作系统也需要允许对应浏览器 / DSH Desktop 显示通知。
-2. 打开 **设置 → 通知提醒**，确认出现该分区及底部插件版本号，保持「启用提醒」「提示音」开启，通知类型先留「系统通知」。
+2. 打开 **设置 → 通知提醒**，确认出现该分区及底部插件版本号，保持「启用提醒」「提示音」开启。
 3. 点击设置页的「测试『回复完成』」按钮：应出现一条测试通知，并按当前音效设置播放声音。这个本地测试不会转发到外部通知端点，也不受「窗口在前台时也提醒」开关限制。
 
 Web 用户可再测试审批按钮。桌面端拿不到 Service Worker，这条测试会在窗口角落画一张带「同意 / 拒绝」的卡片（1.10.4 起；之前的版本这里只发普通通知）。
@@ -117,25 +113,21 @@ dsh-notify-me 把「监督」和「守在屏幕前」解耦：只在真的出现
 ### 提醒方式
 
 - **启用提醒** 总开关：关闭后不弹通知、不响提示音，也不改标签页标题；
-- **通知类型（二选一）**：一行分段选择器，左边「系统通知」、右边「浮层提醒」，点哪个就只走哪个；
-  - **系统通知**（默认）：进 Windows / macOS 通知中心，需要通知权限；
-  - **页面浮层**：在 DSH 页面角落画提醒卡片，窗口在哪块屏它就在哪块屏——系统通知只会画在主屏，主屏不看时用它；不需要通知权限，桌面端也能在卡片上直接「同意 / 拒绝」。选中后卡片里会多出「浮层位置」子行，点开可选四个角落，见[副屏与浮层提醒](#副屏与浮层提醒)；
 - **提示音 / 音量**：开关直接切；音量滑块收在该行里，点一下标题（▸ 变成 ▾）展开。具体播什么由「高级设置 → 音效来源」决定；
-- **审批通知上直接裁决**（默认开）：审批带「同意 / 拒绝」，点一下即完成裁决，不用切回页面。Web 走带按钮的系统通知；桌面端 `dsh-app://` 注册不了 Service Worker，于是把按钮画在窗口角落的卡片上（12 秒自动收起，同一条审批不叠第二张卡）。也可以把「通知类型」换成「页面浮层」，改在浮层卡片上裁决。
+- **审批通知上直接裁决**（默认开）：审批带「同意 / 拒绝」，点一下即完成裁决，不用切回页面。Web 走带按钮的系统通知；桌面端 `dsh-app://` 注册不了 Service Worker，于是把按钮画在窗口角落的卡片上（12 秒自动收起，同一条审批不叠第二张卡）。卡片位置由它下面的子行「审批卡片位置」控制，见[副屏与审批卡片](#副屏与审批卡片)。
 
-### 副屏与浮层提醒
+### 副屏与审批卡片
 
-Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏览器也没有 API 能把它挪到别的显示器。主屏不看、DSH 停在副屏时，通知就等于没发。
+Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏览器也没有 API 能把它挪到别的显示器。主屏不看、DSH 停在副屏时，通知就等于没发。这一条改不掉——真要在副屏看见，只能靠页面里的东西。
 
-「页面浮层提醒」绕开系统通知中心，直接在 DSH 页面里画一张卡片：窗口在哪块屏，卡片就出现在哪块屏。
+页面里还剩一种：桌面端的审批卡片。它画在 DSH 页面里，窗口在哪块屏就出现在哪块屏，卡片上能直接「同意 / 拒绝」（桌面端通知带不了按钮）。
 
-- **位置**：选中「浮层提醒」后，「浮层位置」子行出现，行上直接显示当前值（默认右下）；点它（▸ 变 ▾）再选右上 / 右下 / 左上 / 左下，改完立刻生效；
-- **不需要通知权限**：通知权限没给、或桌面端弹不出带按钮的通知时，浮层照常工作；
-- **审批卡片带「同意 / 拒绝」**：与审批卡片的「允许一次 / 拒绝」等价，桌面端也能用（不依赖 Service Worker）；点卡片正文则切回对应对话；
-- **停留时间**：普通提醒 5 秒自动收起，带「同意 / 拒绝」的审批卡片 12 秒（系统通知用同一套数字）；也可以点卡片或右上角叉提前关掉。最多同时叠 4 张；
-- **与系统通知的关系**：二选一。以前两个开关可以同开，结果同一条提醒弹两遍、还互相挡住；1.10.0 起改成单选，1.10.2 起做成一行分段选择器。老配置里开着浮层的，升级后自动落到浮层。
+- **位置**：「审批通知上直接裁决」下面的「审批卡片位置」子行，行上直接显示当前值（默认右下）；点它（▸ 变 ▾）再选右上 / 右下 / 左上 / 左下，改完立刻生效；
+- **只给审批**：普通提醒与「回复完成」不画卡片，它们只有系统通知；
+- **停留时间**：审批卡片 12 秒自动收起；点卡片正文切回对应对话。最多同时叠 4 张；
+- **不用通知权限**：这条路径不碰 Service Worker，也不依赖通知权限。
 
-浮层只知道窗口在哪块屏，不知道你人在看哪块屏。窗口留在主屏、人却盯着副屏时，它同样看不见。
+> 1.11.0 删掉了「通知类型」二选一。页面浮层曾经能当独立通道用，但它只在 DSH 窗口处于前台时看得见——需要提醒的时刻恰恰是窗口在后台。选浮层、切走之后后台只剩提示音和标题标记，等于没提醒。
 
 ### 什么时候提醒
 
@@ -196,9 +188,8 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 
 ## 提醒渠道
 
-- **提醒渠道（二选一，不同时出现）**：
-  - **系统通知**：经浏览器弹出的系统通知，进 Windows 通知中心或 macOS 通知中心（点击回到提醒所属的对话；支持快捷裁决的 Web 环境可点审批按钮直接裁决，桌面端无按钮）
-  - **页面浮层**：画在 DSH 页面角落的提醒卡片，落在窗口所在的那块屏，可带「同意 / 拒绝」按钮；见[副屏与浮层提醒](#副屏与浮层提醒)
+- **系统通知**：经浏览器弹出的系统通知，进 Windows 通知中心或 macOS 通知中心（点击回到提醒所属的对话；支持快捷裁决的 Web 环境可点审批按钮直接裁决，桌面端没有按钮）
+- **桌面端审批卡片**：`dsh-app://` 下系统通知带不了「同意 / 拒绝」，审批类提醒额外在窗口角落画一张可点卡片；见[副屏与审批卡片](#副屏与审批卡片)
 - **提示音**：默认是 WebAudio 合成音（「需要你」与「完成」使用不同音型）；可在设置里为两类提醒分别换成自定义音频文件，或改成让操作系统播放它自己的通知音
 - **标签页标题标记**：有待处理事项时，标题前出现 `🔔 需要你 · …` / `🔔 Action needed · …`；后台会话**完成但还没看**时出现 `✅ 回复完成 · …` / `✅ Reply finished · …`，打开对应会话（或它再次开跑）即消失。两种标记可同时出现，「需要你」在前；宿主改写标题后标记基于新标题重建
 - **外部通知**（可选，默认关）：按设置里配的推送目标，把同一条提醒转发到 Discord Webhook / Bark / Gotify / 自定义 Webhook——临时离开电脑时，手机上的推送渠道照样收到
@@ -248,15 +239,13 @@ window.__dshNotifyMe.setConfig({
   currentHiddenOnly: true,    // true = 当前对话的等待只留标题标记（转后台补发）
   doneHiddenOnly: true,       // false = 页面可见时「完成」也提醒
   ignoreSubagent: true,       // true = 后台子代理（subagent）会话不提醒（当前打开的照常）
-  channel: "toast",          // 通知类型：'toast' 系统通知 | 'overlay' 页面浮层，二选一
   sound: true,                // 提示音开关（含「系统通知音」模式）
   soundDone: "synth",         // 「完成」音效来源：'synth' 内置 | 'custom' 自定义文件 | 'system' 系统通知音
   soundAttention: "synth",    // 「需要你」音效来源，取值同上
   volume: 0.5,                // 音量 0~1
   autoFocus: true,            // 点通知回到提醒所属的对话
   quickActions: true,         // 审批通知上的「同意 / 拒绝」按钮
-  overlay: false,             // 兼容字段，跟随 channel 同步（老配置靠它迁移）
-  overlayCorner: "bottom-right", // 浮层位置：'top-right' | 'bottom-right' | 'top-left' | 'bottom-left'
+  overlayCorner: "bottom-right", // 桌面端审批卡片位置：'top-right' | 'bottom-right' | 'top-left' | 'bottom-left'
   externalEnabled: false,     // 外部通知转发主开关（默认关：不填端点就什么都不发）
   externalAttention: true,    // 转发「需要你」（触发规则跟本地提醒完全一致）
   externalDone: true,         // 转发「回复完成」
@@ -316,7 +305,7 @@ DSH Desktop 是一层 Electron 壳，页面跑在 `dsh-app://app` 下：DOM 的
 - 页面必须开着才会提醒（后台标签/最小化可以；关标签页即失效——浏览器层方案固有限制）。
 - 通知经由浏览器弹出，需允许浏览器通知权限，且勿扰模式不能屏蔽它。
 - 桌面端（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 窗口走。
+- 系统通知横幅只画在主屏：Windows 没有设置项、Chromium 没有 API 能把它指到别的显示器（多屏时副屏收不到系统通知）。页面里唯一还会出现在副屏的是桌面端的审批卡片，它跟着 DSH 窗口走；普通提醒要跨屏，只能靠外部推送转到手机。
 - 每次页面加载后第一次出声/弹通知前，需在页面上点击过一次（浏览器自动播放与权限策略）。
 - 未授权通知权限时只有提示音与标题标记。
 - 快捷裁决按钮要 Service Worker：`http://127.0.0.1`、`https` 可用，`http://192.168.x.x` 这类局域网地址不行；**桌面端（`dsh-app://`）已实测无法注册 Service Worker**，按钮渲染不了，审批通知退回无按钮样式。浏览器或桌面宿主不渲染通知按钮时，`window.__dshNotifyMe.debug()` 的 `bridge` 字段会说明原因，其余功能不受影响。
@@ -324,7 +313,7 @@ DSH Desktop 是一层 Electron 壳，页面跑在 `dsh-app://app` 下：DOM 的
 - 配置存在浏览器 `localStorage`：换浏览器/设备或清除站点数据后会回到默认值（设置页可一键恢复默认）。
 - `≥ 0.1.6`（含 `0.2.0-rc.2`、`0.2.1-rc.2`）的「回复完成」提醒正文只有会话名，不再附带回复摘要——宿主快照已不再提供 `nodes`；提醒本身照常触发。
 - 标题标记由宿主与插件共同写 `document.title`：宿主重算标题时标记可能被覆盖，直到下一次提醒事件重新写成。
-- 「当前对话不弹通知」按 `document.hidden` 判定：窗口被别的应用完全盖住时仍算「页面可见」，此时当前对话的等待照样静默。
+- 「当前对话不弹通知」按「窗口是否在前台」判定：窗口被别的应用盖住、切到别的应用、最小化都算后台，此时当前对话的等待照常提醒；窗口回到前台再静默。
 - 外部通知转发受浏览器跨域（CORS）限制：端点不放行时自动降级为「送出但不可确认」（no-cors），如实标为「已送出不可确认」；Discord Webhook 官方放行跨域，可直接确认送达。HTTP 错误如实记失败、不重试。转发在本地提醒决定要发之后才触发，所以被「当前对话不弹通知」等规则静音的提醒也不会外发。
 
 - **设置左侧导航行图标靠 DOM 补丁**：外壳按分区 id 硬编码图标且 `settings.section` 没有图标字段，插件只能在面板渲染后把那一行的 `<svg>` 换成铃铛。命中依赖宿主当前的面板结构（`data-shortcut-modal="settings"` + 导航按钮里的标签 `<span>`）；如果 DSH 改了这套结构，补丁会静默失效、显示回默认齿轮，其他功能不受影响。
@@ -334,7 +323,7 @@ DSH Desktop 是一层 Electron 壳，页面跑在 `dsh-app://app` 下：DOM 的
 ```powershell
 node --check lib\client.js
 node --check lib\index.js
-node smoke\smoke-test.cjs        # 离线状态机冒烟测试：三代宿主 + 主开关 + 中英语言用例 + 快捷裁决桥（Service Worker 半侧一并跑）+ 页面浮层
+node smoke\smoke-test.cjs        # 离线状态机冒烟测试：三代宿主 + 主开关 + 中英语言用例 + 快捷裁决桥（Service Worker 半侧一并跑）+ 桌面审批卡片
 node smoke\cordis-host-test.mjs  # 真 cordis 端到端（找不到本机 DSH 时自动跳过）
 npm pack --dry-run               # 预览发布包
 ```

package/lib/client.js

@@ -59,7 +59,7 @@
 //     (client.focus()) and routes the conversation switch to that window alone. Where a worker cannot run (insecure context, no
 //     bundle URL) the plugin degrades to today's plain toast;
 //   - registers a "通知提醒 / Notify me" page into DSH Settings
-//     (settings.section slot) exposing an on/off master switch, per-channel
+//     (settings.section slot) exposing an on/off master switch, per-event
 //     toggles, volume and the notification language (follow-interface /
 //     Simplified Chinese / English);
 //   - preferences persist in localStorage (origin-scoped, like other
@@ -237,7 +237,6 @@
       // keys on, plus "not the session on screen" — an open subagent session is
       // just another conversation to alert for.
       ignoreSubagent: true,
-      toast: true,
       sound: true,
       // Where each alert's cue comes from (per kind, so "needs you" and "reply
       // finished" stay independent):
@@ -256,21 +255,15 @@
       // through the Service Worker half of this same file; where that cannot
       // run, the toast simply falls back to its plain form.
       quickActions: true,
-      // 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
+      // Alerts reach the user through the OS notification center; there is no
+      // second channel. An in-page card would follow the DSH window to whatever
+      // display it sits on, but it is invisible the moment the window is not in
+      // front — which is exactly when a reminder is worth anything — so 1.11.0
+      // removed it as a channel. The card layer survives for the one case that
+      // needs it: the desktop shell cannot put Approve / Reject on a system
+      // notification, so an approval also drops a clickable card in the corner
+      // (see showFallbackApprovalCard).
+      // Which corner of this window that approval card stacks in. The screen
       // follows the window — the page cannot aim it anywhere else either.
       overlayCorner: "bottom-right", // bottom-right | bottom-left | top-right | top-left
       // External forwarding: mirror every alert the plugin actually delivers to
@@ -289,31 +282,18 @@
         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";
-      }
+      // The alert channel is gone: 1.11.0 removed the in-page overlay as a
+      // delivery option, so an old config's `channel` / `overlay` / `toast` keys
+      // mean nothing now. Dropped here so the next write stores a clean config.
+      delete cfg.channel;
+      delete cfg.overlay;
+      delete cfg.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;
     }
@@ -321,18 +301,13 @@
     // Persist a patch, swap the live module config and re-apply any active
     // title marker (its prefix follows the notification language).
     function setConfigLocal(patch) {
-      var wasOverlay = config.channel === "overlay";
       config = writeConfig(patch);
       applyTitle();
-      // Overlay re-apply: leaving the overlay channel takes its cards down at
-      // once, and a new corner moves the layer without waiting for the next
-      // alert. Cards can also exist on the toast channel (the desktop fallback),
-      // so an unrelated patch must not sweep them away.
+      // A new corner moves the approval-card layer without waiting for the next
+      // alert. Cards themselves are left alone: an unrelated patch must not
+      // sweep a pending approval off the screen.
       try {
-        if (config.channel !== "overlay") {
-          if (wasOverlay) clearOverlays();
-          else if (overlayLayer) overlayLayer.className = "dnm-ov-layer dnm-ov-" + overlayCorner();
-        } else if (overlayLayer) overlayLayer.className = "dnm-ov-layer dnm-ov-" + overlayCorner();
+        if (overlayLayer) overlayLayer.className = "dnm-ov-layer dnm-ov-" + overlayCorner();
       } catch (e) {}
       return config;
     }
@@ -468,10 +443,12 @@
       } catch (e) {}
     }
     function canToast() {
-      if (config.channel !== "toast") return false;
+      // System notifications are the only channel left (1.11.0); permission is
+      // the single gate. A denied or policy-disabled Notification must not break
+      // delivery: the sound and the title marker still fire.
       try {
         return "Notification" in window && Notification.permission === "granted";
-      } catch (e) { return false; } // a policy-disabled Notification must not break delivery
+      } catch (e) { return false; }
     }
     // True on the packaged desktop shell, where the app page lives under
     // dsh-app://app inside Electron. The desktop needs its own raise path
@@ -922,11 +899,9 @@
       }
     }
     function overlayCount() { return Object.keys(overlayCards).length; }
-    // One card builder for both channels: the overlay channel draws with it,
-    // and so does the desktop fallback below. `opts` keeps the two behaviours
-    // apart: the overlay card is a shortcut (a click opens the conversation and
-    // takes the card down), while the fallback card carries a decision the OS
-    // notification cannot — so a click must not dismiss it unanswered, and a
+    // The card builder behind the desktop approval fallback below (the overlay
+    // channel that also used it is gone since 1.11.0). `opts` keeps behaviours
+    // apart: a click must not dismiss an unanswered approval, and a
     // "详情 / Details" toggle exposes the body that the CSS clamps to 3 lines.
     function drawOverlayCard(kind, title, body, sessionId, quick, opts) {
       opts = opts || {};
@@ -1030,25 +1005,18 @@
         return true;
       } catch (e) { return false; }
     }
-    // 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.channel !== "overlay") return false;
-      return drawOverlayCard(kind, title, body, sessionId, quick, { dismissOnClick: true });
-    }
     // The desktop shell cannot register the Service Worker that OS action
     // buttons require, so an approval toast on a dsh-app:// page has no button
-    // to click. While the alert channel is system notifications, an approval
-    // therefore also drops a card into the same in-page layer, in the same
-    // corner and with the same styling: its buttons call decidePending(), the
-    // exact path a Web toast button takes. Only states that prove the bridge is
-    // unusable qualify — 'idle'/'registering' are transitional, 'disabled' means
-    // the quick-decision switch is off (quickFor() then returns null, so no card
-    // is drawn at all), and the Web path stays untouched once the worker is up.
+    // to click. An approval therefore also drops a card into the in-page layer,
+    // in the configured corner and with the same styling: its buttons call
+    // decidePending(), the exact path a Web toast button takes. Only states that
+    // prove the bridge is unusable qualify — 'idle'/'registering' are
+    // transitional, 'disabled' means the quick-decision switch is off (quickFor()
+    // then returns null, so no card is drawn at all), and the Web path stays
+    // untouched once the worker is up.
     function showFallbackApprovalCard(kind, title, body, sessionId, quick) {
       if (kind !== "attention") return false;
       if (!quick || typeof quick.key !== "string") return false;
-      if (config.channel !== "toast") return false;
       if (bridgeActive()) return false;
       if (swState.indexOf("unsupported:") !== 0 && swState.indexOf("failed:") !== 0) return false;
       return drawOverlayCard(kind, title, body, sessionId, quick, { dismissOnClick: false, expand: true });
@@ -1425,7 +1393,6 @@
     function deliver(kind, title, body, sessionId, quick) {
       if (!config.enabled) return;
       showToast(kind, title, body, sessionId, quick);
-      showOverlay(kind, title, body, sessionId, quick);
       showFallbackApprovalCard(kind, title, body, sessionId, quick);
       if (kind === "attention") {
         playAttentionSound();
@@ -2066,7 +2033,7 @@
       });
     } catch (e) {}
     // keep in sync with package.json "version" on every release
-    api.version = "1.10.5";
+    api.version = "1.11.0";
     api.setConfig = function (patch) { return setConfigLocal(patch); };
     api.resetConfig = function () {
       try {
@@ -2127,19 +2094,17 @@
         currentHiddenOnly: config.currentHiddenOnly,
         doneHiddenOnly: config.doneHiddenOnly,
         ignoreSubagent: config.ignoreSubagent,
-        channel: config.channel,
-        toast: config.toast,
         sound: config.sound,
         soundDone: soundMode("done"),
         soundAttention: soundMode("attention"),
         customSoundDone: !!readSound("done"),
         customSoundAttention: !!readSound("attention"),
         quickActions: config.quickActions,
-        // in-page overlay: the alert channel that follows the DSH window to
-        // whatever display it sits on, instead of the OS toast's fixed primary
-        // display. cards is the live stack, corner the configured anchor.
-        overlay: {
-          enabled: !!config.overlay,
+        // The in-page card layer still exists for the desktop approval fallback
+        // (the shell's toasts carry no buttons); `cards` is the live stack and
+        // `corner` the configured anchor.
+        card: {
+          enabled: config.quickActions,
           corner: overlayCorner(),
           cards: overlayCount()
         },
@@ -2212,7 +2177,6 @@
       hostEnvMismatch: "（自动识别结果是「",
       hostEnvMismatchTail: "」，手动选择会覆盖它）",
       hostEnvDesktopForcedNote: "（当前页面不是 dsh-app://：点通知会尝试唤起 dsh:// 协议，浏览器可能弹「打开应用」确认框）",
-      toast: "系统通知",
       toastHint: "走系统通知中心，需要通知权限；桌面端这类通知没有「同意 / 拒绝」按钮。",
       sound: "提示音",
       soundHint: "提示音总开关；播什么由「高级设置 → 音效来源」决定。",
@@ -2285,19 +2249,13 @@
       quickApprovalNote: "「同意」等价于审批卡片上的「允许一次」，只放行这一次。",
       bridgeOff: "快捷裁决按钮暂不可用（",
       bridgeOffTail: "）：系统通知没有按钮，按钮改画在窗口角落的卡片上。",
-      bridgeOffDesktop: "系统通知本身没有「同意 / 拒绝」按钮：桌面端页面（dsh-app://）注册不了 Service Worker（宿主少给 allowServiceWorkers 特权）。审批类提醒会同时在窗口角落弹一张卡片，按钮就在卡片上；想只留卡片、不弹系统通知，把「提醒方式」切到「页面浮层」。",
-      overlay: "页面浮层提醒",
-      overlayHint: "在窗口角落画提醒卡片：窗口在哪块屏，它就在哪块屏；系统通知只会出现在主屏，主屏不看时用它。不需要通知权限，卡片上能直接「同意 / 拒绝」。与系统通知二选一。",
-    channelLabel: "通知类型",
-    overlaySeg: "浮层提醒",
-    channelHint: "系统通知只会出现在主屏，进通知中心要权限，桌面端的通知本身没有「同意 / 拒绝」按钮（审批会额外在窗口角落弹一张可点击的卡片）；页面浮层画在 DSH 窗口所在的那块屏，不需要权限，卡片上能直接裁决。两个只能选一个。",
-      overlayCorner: "浮层位置",
-      overlayCornerHint: "贴在 DSH 窗口的哪个角；窗口在哪块屏，浮层就出现在哪块屏。",
+      bridgeOffDesktop: "系统通知本身没有「同意 / 拒绝」按钮：桌面端页面（dsh-app://）注册不了 Service Worker（宿主少给 allowServiceWorkers 特权）。审批类提醒会同时在窗口角落弹一张卡片，按钮就在卡片上。",
+      overlayCorner: "审批卡片位置",
+      overlayCornerHint: "桌面端审批卡片贴在 DSH 窗口的哪个角；窗口在哪块屏，卡片就出现在哪块屏。",
       overlayPosTR: "右上",
       overlayPosBR: "右下",
       overlayPosTL: "左上",
       overlayPosBL: "左下",
-      overlayQuickNote: "浮层上的「同意」同样等价于审批卡片上的「允许一次」，与通知按钮一致。",
       testApprovalNoBridge: "已发测试提醒：系统通知没有按钮，快捷裁决按钮画在窗口角落的卡片上。",
       testNeedsQuick: "先打开上面的「审批通知上直接裁决」才能测按钮。",
       volume: "音量",
@@ -2342,7 +2300,6 @@
       hostEnvMismatch: " (auto-detection sees \"",
       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: "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.",
@@ -2415,19 +2372,13 @@
       quickApprovalNote: "\"Approve\" equals \"Allow once\" on the approval card — it allows that one call only.",
       bridgeOff: "Quick-decision buttons are unavailable right now (",
       bridgeOffTail: "); system notifications carry no buttons, so they are drawn on a card in the window corner instead.",
-      bridgeOffDesktop: "System notifications carry no Approve / Reject buttons: dsh-app:// pages cannot register a Service Worker (the shell does not grant the allowServiceWorkers privilege). An approval therefore also drops a clickable card in the window corner, buttons and all; switch the alert channel to the in-page overlay to keep only the card and skip the system notification.",
-      overlay: "In-page overlay",
-      overlayHint: "Draw a card in the window corner, on whatever display the window sits on. System notifications only ever show on the primary display. No permission needed, and the card carries Approve / Reject directly. It replaces system notifications rather than adding to them.",
-    channelLabel: "Alert type",
-    overlaySeg: "Overlay",
-    channelHint: "System notifications land in the Windows notification center: permission needed, primary display only, and the Desktop shell's notifications carry no Approve / Reject buttons (an approval also drops a clickable card in the window corner). The in-page overlay draws on whichever display the DSH window sits on, needs no permission, and lets the Desktop shell decide right on the card. Pick one.",
-      overlayCorner: "Overlay position",
-      overlayCornerHint: "Which corner of the DSH window the cards stack in; they follow the window to whatever display it is on.",
+      bridgeOffDesktop: "System notifications carry no Approve / Reject buttons: dsh-app:// pages cannot register a Service Worker (the shell does not grant the allowServiceWorkers privilege). An approval therefore also drops a clickable card in the window corner, buttons and all.",
+      overlayCorner: "Approval card position",
+      overlayCornerHint: "Which corner of the DSH window the Desktop approval card sits in; it follows the window to whatever display it is on.",
       overlayPosTR: "Top right",
       overlayPosBR: "Bottom right",
       overlayPosTL: "Top left",
       overlayPosBL: "Bottom left",
-      overlayQuickNote: "\"Approve\" here equals \"Allow once\" on the approval card — the same decision the toast buttons send.",
       testApprovalNoBridge: "Test alert sent: system notifications carry no buttons, so the quick-decision buttons are drawn on a card in the window corner.",
       testNeedsQuick: "Turn on \"Decide approvals from the toast\" above to test the buttons.",
       volume: "Volume",
@@ -2558,11 +2509,6 @@
       ".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-seg{display:inline-flex;flex:none;border:1px solid var(--dsw-alias-border-l2,rgba(128,128,128,.35));border-radius:8px;overflow:hidden}" +
-      ".dnm-segBtn{height:28px;padding:0 12px;border:0;background:transparent;color:var(--dsw-alias-label-secondary,rgba(90,90,90,.95));font:inherit;font-size:12px;line-height:28px;cursor:pointer;white-space:nowrap}" +
-      ".dnm-segBtn+.dnm-segBtn{border-left:1px solid var(--dsw-alias-border-l2,rgba(128,128,128,.35))}" +
-      ".dnm-segBtn:hover{color:var(--dsw-alias-label-primary,rgba(20,20,20,.9))}" +
-      ".dnm-segBtn.on{background:var(--dsw-alias-state-business-primary,#3b82f6);color:#fff}" +
       ".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}" +
@@ -3025,30 +2971,6 @@
       function secTitle(labelText) {
         return h("div", { className: "dnm-secTitle" }, labelText);
       }
-      // One channel at a time. A pair of radios read as two unrelated dots, so
-      // the choice is a segmented control: the filled half is the active option.
-      function segButton(labelText, checked, onPick) {
-        return h("button", {
-          type: "button",
-          role: "radio",
-          "aria-checked": checked ? "true" : "false",
-          "aria-label": labelText,
-          className: "dnm-segBtn" + (checked ? " on" : ""),
-          onClick: function () { if (!checked) onPick(); }
-        }, labelText);
-      }
-      function rowChannel(labelText, hintText, current, onPick) {
-        return tipRow("dnm-row", hintText, [
-          h("div", { className: "dnm-rowText" }, [
-            h("div", { className: "dnm-rowLabel" }, labelText),
-            srOnly(hintText)
-          ]),
-          h("div", { className: "dnm-seg", role: "radiogroup", "aria-label": labelText }, [
-            segButton(t("toast"), current !== "overlay", function () { onPick("toast"); }),
-            segButton(t("overlaySeg"), current === "overlay", function () { onPick("overlay"); })
-          ])
-        ]);
-      }
       // 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() {
@@ -3057,8 +2979,8 @@
       var advState = React.useState(false);
       var advancedOpen = advState[0];
       var setAdvancedOpen = advState[1];
-      // Dependent controls (overlay corner, volume) stay folded away until the
-      // row they belong to is clicked open.
+      // Dependent controls (volume) stay folded away until the row they belong
+      // to is clicked open.
       var subStateHook = React.useState({});
       var subState = subStateHook[0];
       var setSubState = subStateHook[1];
@@ -3111,39 +3033,15 @@
             h("p", { className: "dnm-headSub" }, t("blurb"))
           ])
         ]),
-        // 1) How the alert reaches you. Each channel owns its own row, and the
-        // row's dependent control (overlay corner, volume) hangs beneath it.
+        // 1) How the alert reaches you. System notifications only — no channel
+        // choice since 1.11.0 — with the volume slider hanging beneath the
+        // sound switch.
         secTitle(t("secWays")),
         card([
           rowSwitch("enabled", t("enable"), t("enableHint"), cfg.enabled, function (v) {
             patch({ enabled: v });
             if (!v && attentionActive > 0) { attentionActive = 0; applyTitle(); }
           }),
-          rowChannel(t("channelLabel"), t("channelHint"), cfg.channel, function (next) { patch({ channel: next }); }),
-          cfg.channel === "overlay" ? discloseRow({
-            key: "overlayCorner",
-            rowClass: "dnm-row dnm-rowSub",
-            labelText: t("overlayCorner"),
-            hintText: t("overlayCornerHint"),
-            valueText: t("overlayPos" + ({ "top-right": "TR", "bottom-right": "BR", "top-left": "TL", "bottom-left": "BL" })[overlayCorner()] || "BR"),
-            sub: tipRow("dnm-row dnm-rowSub", t("overlayCornerHint"), [
-              h("div", { className: "dnm-rowText" }, [
-                h("div", { className: "dnm-rowLabel" }, t("overlayCorner")),
-                srOnly(t("overlayCornerHint"))
-              ]),
-              h("select", {
-                className: "dnm-select",
-                value: overlayCorner(),
-                "aria-label": t("overlayCorner"),
-                onChange: function (e) { patch({ overlayCorner: e.currentTarget.value }); }
-              }, [
-                h("option", { value: "top-right" }, t("overlayPosTR")),
-                h("option", { value: "bottom-right" }, t("overlayPosBR")),
-                h("option", { value: "top-left" }, t("overlayPosTL")),
-                h("option", { value: "bottom-left" }, t("overlayPosBL"))
-              ])
-            ])
-          }) : null,
           cfg.sound ? discloseRow({
             key: "volume",
             labelText: t("sound"),
@@ -3175,7 +3073,27 @@
           rowSwitch("quickActions", t("quickActions"), t("quickActionsHint"), cfg.quickActions, function (v) {
             patch({ quickActions: v });
             if (v) ensureActionBridge();
-          })
+          }),
+          // The in-page card only exists to carry Approve / Reject where the OS
+          // toast cannot (the desktop shell), so its corner hangs under the
+          // quick-decision switch rather than a channel picker.
+          cfg.quickActions ? tipRow("dnm-row dnm-rowSub", t("overlayCornerHint"), [
+            h("div", { className: "dnm-rowText" }, [
+              h("div", { className: "dnm-rowLabel" }, t("overlayCorner")),
+              srOnly(t("overlayCornerHint"))
+            ]),
+            h("select", {
+              className: "dnm-select",
+              value: overlayCorner(),
+              "aria-label": t("overlayCorner"),
+              onChange: function (e) { patch({ overlayCorner: e.currentTarget.value }); }
+            }, [
+              h("option", { value: "top-right" }, t("overlayPosTR")),
+              h("option", { value: "bottom-right" }, t("overlayPosBR")),
+              h("option", { value: "top-left" }, t("overlayPosTL")),
+              h("option", { value: "bottom-left" }, t("overlayPosBL"))
+            ])
+          ]) : null
         ]),
         // 2) Which events are worth interrupting for.
         secTitle(t("secWhen")),
@@ -3193,7 +3111,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.channel === "overlay" ? t("overlayQuickNote") : (!bridgeActive() ? (isDesktopShell() ? t("bridgeOffDesktop") : t("bridgeOff") + swState + t("bridgeOffTail")) : t("quickApprovalNote")))])
+            h("div", { className: "dnm-rowText" }, [h("div", { className: "dnm-rowHint" }, !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)])
@@ -3424,7 +3342,7 @@
             try { bindCurrentFace(); } catch (e) {}
             try { bindUiSession(); } catch (e) {}
           }, 1500);
-          try { console.log("[dsh-notify-me] active — window.__dshNotifyMe 可配置提醒 (enabled=" + config.enabled + ", lang=" + effectiveLang() + ", toast=" + config.toast + ", sound=" + config.sound + ")"); } catch (e) {}
+          try { console.log("[dsh-notify-me] active — window.__dshNotifyMe 可配置提醒 (enabled=" + config.enabled + ", lang=" + effectiveLang() + ", sound=" + config.sound + ")"); } catch (e) {}
         } catch (e) {
           try { console.error("[dsh-notify-me] init failed", e); } catch (e2) {}
         }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-notify-me",
-  "version": "1.10.5",
-  "description": "离开 DSH 页面也能收到提醒：需要你操作 / 后台回复完成时发系统通知、标题标记与可选页面浮层（副屏也能看见），支持审批快捷裁决与外部推送，Web 版与桌面版均可用。",
+  "version": "1.11.0",
+  "description": "离开 DSH 页面也能收到提醒：需要你操作 / 后台回复完成时发系统通知、标题标记与提示音，支持审批快捷裁决与外部推送，Web 版与桌面版均可用。",
   "license": "MIT",
   "type": "module",
   "main": "lib/index.js",