dsh-notify-me 1.10.2 → 1.10.4

package/CHANGELOG.md

@@ -2,6 +2,30 @@
 
 All notable changes to **dsh-notify-me** are documented here.
 
+## [1.10.4] — 2026-10-21
+
+### 新增
+
+- **桌面端审批按钮落到页内卡片**：桌面壳在 `dsh-app:` 协议下拿不到 Service Worker（注册被拒），带按钮的审批通知因此只剩标题、点不出「同意 / 拒绝」。现在这种拿不到 SW 的情形会在窗口角落画一张卡片：审批标题与正文、`同意` / `拒绝` 两个按钮、正文过长时可就地展开「详情」，12 秒自动收起，同一条审批不叠第二张卡。按钮走的是和系统通知完全同一条裁决路径（`allowed-once` / `rejected`），裁完即撤卡。Web 端（SW 可用）行为不变，仍是带按钮的系统通知。
+
+### 修复
+
+- 页面里写的 `api.version` 与 `package.json` 对齐（1.10.3 的发版提交只改了 `package.json`，页内版本号停在 1.10.2，冒烟断言因此一开始就是红的）。
+
+### 测试
+
+- 冒烟新增 12 组断言覆盖桌面降级卡片：出现时机、两个按钮、详情展开/收起、点卡片本体不撤卡、同意、拒绝、审批从状态里消失时撤卡、同一条审批不叠卡、开关关闭时不画卡、12 秒回收、Web 路径不回归。
+
+## [1.10.3] — 2026-10-21
+
+### 修复
+
+- **桌面端同类系统通知只弹第一条**（#15）：普通通知的 `tag` 原本按类别固定（`dsh-notify-me-<kind>`），靠 `renotify: true` 让同 tag 的新通知替换并重新提示；Electron 不认这个标志，同 tag 的第二条被静默替换，横幅不再出现。现改为每条普通通知独立 tag（`dsh-notify-me-<kind>-<seq>-<ts>`，计数器防同毫秒碰撞）。审批通知的 tag 保持稳定，`closeNotificationTag()` 撤回逻辑不变。
+
+### 测试
+
+- 冒烟新增 `uniqueToastTags()` 回归用例：连发三次「回复完成」断言三条 tag 互不相同、审批 tag 前缀不变；`npm test` 两套件通过。
+
 ## [1.10.2] — 2026-10-21
 
 ### 变更

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-%7E173%20KiB-green?style=flat-square)](lib/client.js)
+[![Package size](https://img.shields.io/npm/unpacked-size/dsh-notify-me?style=flat-square&label=package%20size)](https://www.npmjs.com/package/dsh-notify-me)
 [![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)
 
@@ -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.10.2 defaults) rendered in a standalone demo shell. 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, 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.
 </details>
 
 ## Installation
@@ -74,17 +74,17 @@ 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, 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, the alert type on system notifications, 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 page is open" toggle.
 
-Web users can also test approval buttons. On Desktop that test sends a plain notification: **no Approve / Reject buttons is the expected result**.
+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).
 
 **Optional console check** — in environments with DevTools, you can also run:
 
 ```js
 window.__dshNotifyMe.test("done")        // "reply finished" sample
 window.__dshNotifyMe.test("attention")   // "needs your input" sample
-window.__dshNotifyMe.test("approval")    // Approve / Reject with an active Web bridge; buttonless on Desktop
+window.__dshNotifyMe.test("approval")    // Approve / Reject with an active Web bridge; an in-page card on Desktop
 window.__dshNotifyMe.debug()             // the bridge field reports the button channel: "active" = buttons work
 ```
 
@@ -108,7 +108,7 @@ dsh-notify-me decouples **supervision** from **sitting in front of the screen**:
 | 🔔 Input needed | Alerts even in the foreground; the conversation on screen keeps only a title marker |
 | ✅ Reply finished | Alerts while the page is hidden / backgrounded |
 
-**Input needed** covers approval requests, plan review, and questions (`ask_user_question`). Supported Web environments show Approve / Reject buttons; Desktop does not.
+**Input needed** covers approval requests, plan review, and questions (`ask_user_question`). Approvals carry Approve / Reject: on Web as a system notification with buttons, on Desktop (which cannot register a Service Worker) as a card drawn in the window corner.
 
 **Reply finished** also covers background sessions. A finished but unread session keeps the `✅ Reply finished ·` title marker until opened. Title markers are independent of the "while the page is open" toggles.
 
@@ -123,9 +123,9 @@ Open **Settings → Notify me**. The page runs as how you get told, when to aler
 - **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. Click the row open to pick one of four corners when it is the chosen channel. See [Secondary displays and the overlay](#secondary-displays-and-the-overlay);
+  - **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): 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.
+- **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.
 
 ### Secondary displays and the overlay
 
@@ -133,10 +133,10 @@ Windows draws system notification banners on the primary display only. There is
 
 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.
 
-- **Position** — click the In-page overlay row open (▸ turns into ▾), then pick top right / bottom right / top left / bottom left; the row shows the current value. Default bottom right, changes apply immediately;
+- **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" 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;
+- **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.
 
 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.
@@ -189,7 +189,7 @@ The last block inside Advanced. The page protocol is detected automatically to t
 <summary>Alert language, Desktop window raising, reset</summary>
 
 - **Alert language**: follow the UI / Simplified Chinese / English — governs alert copy and the `🔔 …` title marker;
-- **How the Desktop window is raised**: `window.focus()` cannot lift a native Electron window, so since 1.5.2 the page drives the app's own `dsh://open` deep link — it works even when the window is parked in the tray;
+- **How the Desktop window is raised**: `window.focus()` cannot lift a native Electron window, so since 1.5.2 the page drives the app's own `dsh://open` deep link — measured working on DSH Desktop 0.2.0-rc.2, flaky on 0.2.1-rc.2 / Windows (see the next section);
 - **Reset settings**: restores every switch and cue setting to the factory defaults (webhook targets and chosen audio files are kept).
 
 </details>
@@ -200,8 +200,9 @@ 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** — 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)
+- **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)
 - **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
@@ -214,7 +215,7 @@ Per-release adaptation records live in [package.json](package.json), under `dsh.
 
 Verified to actually activate on `0.1.2-rc.1`, `0.1.5-rc.1`, `0.1.5-rc.2` and `0.2.0-rc.2` (each booted in its own profile: the plugin entry lands in the boot page's `__DSH_BOOT__` with its inject dependencies resolved, `/plugins/??dsh-notify-me/client.js&rev=…` serves a build containing the new code, and the Settings → Notifications section registers, i.e. the plugin's `apply` really runs), and previously on `0.1.1-rc.2`.
 
-`0.2.1-rc.2` (current latest) got its own isolated run: an isolated `DSH_HOME` booting `dsh web` (70 boot entries) placed the plugin entry 59th, in the `application` batch, with all three inject targets present and ordered before it; `/plugins/??dsh-notify-me/client.js&rev=…` served the 1.7.0 source build (140,153 B); loaded in a headless Chromium page, `apply` ran — `window.__dshNotifyMe.debug()` reported `uiSession: bound`, `uiSessionSource: sessionStatus`, `bridge: active`. Host-side shapes match `0.2.0-rc.2`; no plugin code change was needed.
+`0.2.1-rc.2` (current latest) got its own isolated run: an isolated `DSH_HOME` booting `dsh web` (70 boot entries) placed the plugin entry 59th, in the `application` batch, with all three inject targets present and ordered before it; `/plugins/??dsh-notify-me/client.js&rev=…` served the then-installed 1.7.0 source build (140,153 B); loaded in a headless Chromium page, `apply` ran — `window.__dshNotifyMe.debug()` reported `uiSession: bound`, `uiSessionSource: sessionStatus`, `bridge: active`. Host-side shapes match `0.2.0-rc.2`; no plugin code change was needed.
 
 <details>
 <summary>Host generations and adaptation diagnostics</summary>
@@ -298,7 +299,7 @@ The reminder core stays dependency-free and self-contained: notification copy re
 
 Action buttons (`actions`) belong to persistent notifications shown through `ServiceWorkerRegistration.showNotification()`; passing `actions` to the `new Notification()` constructor throws a `TypeError`. That is a browser rule no plugin can route around, so the bundle holds two jobs in the same bytes: the page half registers the reminder factory as it always did, and the very same file is registered as a Service Worker whose only task is relaying which button was clicked back to the page. The decision itself happens in the page, through the same `PendingApproval.answer('allowed-once' | 'rejected')` the approval card uses — which is why "Approve" is exactly "Allow once" and nothing broader. The "raise a window and switch its conversation" part of a body click is scheduled on the worker half too: `client.focus()` raises exactly one window (a visible one first) and routes the conversation switch to that window alone, so several open DSH tabs never fight over focus or all switch at once.
 
-Every button toast is booked against its interaction key, so it can only decide the request it was raised for. Once the page answers that request or a newer one replaces it, clicking the leftover buttons decides nothing and just closes the notification. Button toasts also skip the auto-dismiss timer: an undecided approval stays in the notification center until you settle it.
+Every button toast is booked against its interaction key, so it can only decide the request it was raised for. Once the page answers that request or a newer one replaces it, clicking the leftover buttons decides nothing and just closes the notification. Button toasts stay 12s (plain ones 5s) and retire on their own, so an approval left undecided there still waits for you in the page.
 
 ### How the Desktop window gets raised
 

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-%7E173%20KiB-green?style=flat-square)](lib/client.js)
+[![Package size](https://img.shields.io/npm/unpacked-size/dsh-notify-me?style=flat-square&label=package%20size)](https://www.npmjs.com/package/dsh-notify-me)
 [![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.10.2 默认配置）在独立演示环境里渲染；「通知类型」是分段选择器，每行的说明在鼠标停在标题文字上时才出现，所以这里只看到标题。
+只截插件自己的面板（真实组件、v1.10.2 默认配置），不带 DSH 左侧导航栏；「通知类型」是分段选择器，每行说明在鼠标停在标题文字上时才出现，所以这里只看到标题。
 </details>
 
 ## 安装
@@ -74,17 +74,17 @@ dsh plugin --profile web add dsh-notify-me
 ## 首次验证
 
 1. 在 DSH 页面上点击一次，按提示允许通知；若此前拒绝过，在浏览器站点设置中允许通知。操作系统也需要允许对应浏览器 / DSH Desktop 显示通知。
-2. 打开 **设置 → 通知提醒**，确认出现该分区及底部插件版本号，保持「启用提醒」「提示音」开启，提醒方式先留「系统通知」。
+2. 打开 **设置 → 通知提醒**，确认出现该分区及底部插件版本号，保持「启用提醒」「提示音」开启，通知类型先留「系统通知」。
 3. 点击设置页的「测试『回复完成』」按钮：应出现一条测试通知，并按当前音效设置播放声音。这个本地测试不会转发到外部通知端点，也不受「页面打开时也提醒」开关限制。
 
-Web 用户可再测试审批按钮；桌面端该测试只发普通通知，**没有「同意 / 拒绝」按钮属于预期行为**。
+Web 用户可再测试审批按钮。桌面端拿不到 Service Worker，这条测试会在窗口角落画一张带「同意 / 拒绝」的卡片（1.10.4 起；之前的版本这里只发普通通知）。
 
 **控制台验证（可选）** — 支持 DevTools 的环境也可执行：
 
 ```js
 window.__dshNotifyMe.test("done")        // 「完成」示例
 window.__dshNotifyMe.test("attention")   // 「需要你」示例
-window.__dshNotifyMe.test("approval")    // Web 桥可用时带「同意 / 拒绝」按钮；桌面端为无按钮通知
+window.__dshNotifyMe.test("approval")    // 桥可用时带「同意 / 拒绝」按钮；桌面端画在窗口角落的卡片上
 window.__dshNotifyMe.debug()             // 桥接状态看 bridge 字段，active = 按钮可用
 ```
 
@@ -104,7 +104,7 @@ dsh-notify-me 把「监督」和「守在屏幕前」解耦：只在真的出现
 | 🔔 需要你操作 | 页面可见也提醒；当前对话只留标题标记 |
 | ✅ 回复完成 | 页面隐藏 / 后台时提醒 |
 
-**需要你操作**包括审批请求、方案待确认（plan review）和提问（`ask_user_question`）。支持快捷裁决的 Web 环境会显示「同意 / 拒绝」按钮，桌面端无按钮。
+**需要你操作**包括审批请求、方案待确认（plan review）和提问（`ask_user_question`）。审批带「同意 / 拒绝」：Web 走带按钮的系统通知，桌面端（注册不了 Service Worker）改画在窗口角落的卡片上。
 
 **回复完成**也覆盖后台会话；完成但还没看时，标题带 `✅ 回复完成 ·` 标记，打开对应会话即撤。标题标记不受「页面打开时也提醒」开关限制。
 
@@ -119,9 +119,9 @@ dsh-notify-me 把「监督」和「守在屏幕前」解耦：只在真的出现
 - **启用提醒** 总开关：关闭后不弹通知、不响提示音，也不改标签页标题；
 - **通知类型（二选一）**：一行分段选择器，左边「系统通知」、右边「浮层提醒」，点哪个就只走哪个；
   - **系统通知**（默认）：进 Windows / macOS 通知中心，需要通知权限；
-  - **页面浮层**：在 DSH 页面角落画提醒卡片，窗口在哪块屏它就在哪块屏——系统通知只会画在主屏，主屏不看时用它；不需要通知权限，桌面端也能在卡片上直接「同意 / 拒绝」。选中后可在该行点开选四个角落的位置，见[副屏与浮层提醒](#副屏与浮层提醒)；
+  - **页面浮层**：在 DSH 页面角落画提醒卡片，窗口在哪块屏它就在哪块屏——系统通知只会画在主屏，主屏不看时用它；不需要通知权限，桌面端也能在卡片上直接「同意 / 拒绝」。选中后卡片里会多出「浮层位置」子行，点开可选四个角落，见[副屏与浮层提醒](#副屏与浮层提醒)；
 - **提示音 / 音量**：开关直接切；音量滑块收在该行里，点一下标题（▸ 变成 ▾）展开。具体播什么由「高级设置 → 音效来源」决定；
-- **审批通知上直接裁决**（默认开）：审批通知带「同意 / 拒绝」，点一下即完成裁决，不用切回页面。**桌面端的通知没有按钮**（`dsh-app://` 页面无法注册 Service Worker），需要按钮就打开「页面浮层提醒」，改在浮层上裁决；设置页会如实说明当前哪种渠道能给按钮。
+- **审批通知上直接裁决**（默认开）：审批带「同意 / 拒绝」，点一下即完成裁决，不用切回页面。Web 走带按钮的系统通知；桌面端 `dsh-app://` 注册不了 Service Worker，于是把按钮画在窗口角落的卡片上（12 秒自动收起，同一条审批不叠第二张卡）。也可以把「通知类型」换成「页面浮层」，改在浮层卡片上裁决。
 
 ### 副屏与浮层提醒
 
@@ -129,10 +129,10 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 
 「页面浮层提醒」绕开系统通知中心，直接在 DSH 页面里画一张卡片：窗口在哪块屏，卡片就出现在哪块屏。
 
-- **位置**：点开「页面浮层提醒」那一行（▸ 变 ▾）再选右上 / 右下 / 左上 / 左下，默认右下，行上直接显示当前值；改完立刻生效；
+- **位置**：选中「浮层提醒」后，「浮层位置」子行出现，行上直接显示当前值（默认右下）；点它（▸ 变 ▾）再选右上 / 右下 / 左上 / 左下，改完立刻生效；
 - **不需要通知权限**：通知权限没给、或桌面端弹不出带按钮的通知时，浮层照常工作；
 - **审批卡片带「同意 / 拒绝」**：与审批卡片的「允许一次 / 拒绝」等价，桌面端也能用（不依赖 Service Worker）；点卡片正文则切回对应对话；
-- **停留时间**：普通提醒 5 秒自动收起，带「同意 / 拒绝」的审批卡片 12 秒，系统通知同档（普通 5 秒、带按钮 12 秒）；也可以点卡片或右上角叉提前关掉。最多同时叠 4 张；
+- **停留时间**：普通提醒 5 秒自动收起，带「同意 / 拒绝」的审批卡片 12 秒（系统通知用同一套数字）；也可以点卡片或右上角叉提前关掉。最多同时叠 4 张；
 - **与系统通知的关系**：二选一。以前两个开关可以同开，结果同一条提醒弹两遍、还互相挡住；1.10.0 起改成单选，1.10.2 起做成一行分段选择器。老配置里开着浮层的，升级后自动落到浮层。
 
 浮层只知道窗口在哪块屏，不知道你人在看哪块屏。窗口留在主屏、人却盯着副屏时，它同样看不见。
@@ -194,12 +194,11 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 
 > 需要浏览器通知权限：页面上点一下 → 允许；或地址栏锁 → 站点设置 → 通知 → 允许 → 刷新。macOS 还要在 系统设置 → 通知 里允许该浏览器。
 
-## 五种提醒渠道
+## 提醒渠道
 
-- **系统通知**：经浏览器弹出的系统通知，进 Windows 通知中心或 macOS 通知中心（点击回到提醒所属的对话；支持快捷裁决的 Web 环境可点审批按钮直接裁决，桌面端无按钮）
-- **页面浮层**：画在 DSH 页面角落的提醒卡片，落在窗口所在的那块屏，可带「同意 / 拒绝」按钮；见[副屏与浮层提醒](#副屏与浮层提醒)
-
-两种渠道在设置里二选一，不会同时出现。
+- **提醒渠道（二选一，不同时出现）**：
+  - **系统通知**：经浏览器弹出的系统通知，进 Windows 通知中心或 macOS 通知中心（点击回到提醒所属的对话；支持快捷裁决的 Web 环境可点审批按钮直接裁决，桌面端无按钮）
+  - **页面浮层**：画在 DSH 页面角落的提醒卡片，落在窗口所在的那块屏，可带「同意 / 拒绝」按钮；见[副屏与浮层提醒](#副屏与浮层提醒)
 - **提示音**：默认是 WebAudio 合成音（「需要你」与「完成」使用不同音型）；可在设置里为两类提醒分别换成自定义音频文件，或改成让操作系统播放它自己的通知音
 - **标签页标题标记**：有待处理事项时，标题前出现 `🔔 需要你 · …` / `🔔 Action needed · …`；后台会话**完成但还没看**时出现 `✅ 回复完成 · …` / `✅ Reply finished · …`，打开对应会话（或它再次开跑）即消失。两种标记可同时出现，「需要你」在前；宿主改写标题后标记基于新标题重建
 - **外部通知**（可选，默认关）：按设置里配的推送目标，把同一条提醒转发到 Discord Webhook / Bark / Gotify / 自定义 Webhook——临时离开电脑时，手机上的推送渠道照样收到
@@ -212,7 +211,7 @@ Windows 的系统通知横幅固定画在主屏上，系统没有设置项、浏
 
 实测**真正激活**（各自独立 profile 启动：插件条目进启动页 `__DSH_BOOT__` 且注入依赖解析通过、`/plugins/??dsh-notify-me/client.js&rev=…` 返回含新代码的构建，设置里出现「通知提醒」分区，即插件的 `apply` 确实执行）于 `0.1.2-rc.1`、`0.1.5-rc.1`、`0.1.5-rc.2` 与 `0.2.0-rc.2`；更早的 `0.1.1-rc.2` 亦验证过。
 
-`0.2.1-rc.2`（当前 latest）另跑了一轮隔离验证：隔离 `DSH_HOME` 起 `dsh web`（70 个启动条目），插件条目排在第 59、`application` 批，三个注入目标都在且都排在它前面；`/plugins/??dsh-notify-me/client.js&rev=…` 返回 1.7.0 源码构建（140,153 B）；无头 Chromium 载入页面后 `apply` 正常执行，`window.__dshNotifyMe.debug()` 报 `uiSession: bound`、`uiSessionSource: sessionStatus`、`bridge: active`。宿主侧的形状与 `0.2.0-rc.2` 一致，没有需要改代码的地方。
+`0.2.1-rc.2`（当前 latest）另跑了一轮隔离验证：隔离 `DSH_HOME` 起 `dsh web`（70 个启动条目），插件条目排在第 59、`application` 批，三个注入目标都在且都排在它前面；`/plugins/??dsh-notify-me/client.js&rev=…` 返回当时装的 1.7.0 源码构建（140,153 B）；无头 Chromium 载入页面后 `apply` 正常执行，`window.__dshNotifyMe.debug()` 报 `uiSession: bound`、`uiSessionSource: sessionStatus`、`bridge: active`。宿主侧的形状与 `0.2.0-rc.2` 一致，没有需要改代码的地方。
 
 <details>
 <summary>宿主代际与适配排查细节</summary>
@@ -249,7 +248,7 @@ window.__dshNotifyMe.setConfig({
   currentHiddenOnly: true,    // true = 当前对话的等待只留标题标记（转后台补发）
   doneHiddenOnly: true,       // false = 页面可见时「完成」也提醒
   ignoreSubagent: true,       // true = 后台子代理（subagent）会话不提醒（当前打开的照常）
-  channel: "toast",          // 提醒方式：'toast' 系统通知 | 'overlay' 页面浮层，二选一
+  channel: "toast",          // 通知类型：'toast' 系统通知 | 'overlay' 页面浮层，二选一
   sound: true,                // 提示音开关（含「系统通知音」模式）
   soundDone: "synth",         // 「完成」音效来源：'synth' 内置 | 'custom' 自定义文件 | 'system' 系统通知音
   soundAttention: "synth",    // 「需要你」音效来源，取值同上
@@ -296,7 +295,7 @@ window.__dshNotifyMe.testExternal()               // 显式外发测试：向有
 
 通知按钮（`actions`）只属于 Service Worker 弹的持久通知，往 `new Notification()` 里传 `actions` 会直接抛 `TypeError`——这是绕不开的浏览器限制。所以 bundle 一份文件干两件事：页面里照常注册提醒工厂，同一份字节再注册成一个只干转信的 Service Worker，把「点了哪个按钮」（同意 / 拒绝 / 点正文）带回页面。真正的裁决发生在页面里，调的是审批卡片自己用的 `PendingApproval.answer('allowed-once' | 'rejected')`，所以「同意」就是「允许一次」，不多放行任何东西。点正文的「调窗口 + 切对话」同样归 worker 这半侧调度：它用 `client.focus()` 只调起一个窗口（优先当前可见的），并只让那个窗口切对话——多个 DSH 标签页不会互相抢焦点或一起乱切。
 
-每条按钮通知按交互 key 记账，一次只认领一条等待；请求被页面里答掉、或被新请求顶替之后，残留通知上的按钮再点也不会误裁，只是安静地关掉。带按钮的通知不设自动消失——审批没裁决就一直留在通知中心里等你。
+每条按钮通知按交互 key 记账，一次只认领一条等待；请求被页面里答掉、或被新请求顶替之后，残留通知上的按钮再点也不会误裁，只是安静地关掉。带按钮的通知停留 12 秒（普通通知 5 秒），到点自动撤；没来得及点就回页面里裁决，卡片一直等着你。
 
 ### 桌面端怎么抬窗的
 

package/lib/client.js

@@ -321,13 +321,18 @@
     // 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: switching it off takes the cards down at once and a
-      // new corner moves the layer without waiting for the next alert.
+      // 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.
       try {
-        if (config.channel !== "overlay") clearOverlays();
-        else if (overlayLayer) overlayLayer.className = "dnm-ov-layer dnm-ov-" + overlayCorner();
+        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();
       } catch (e) {}
       return config;
     }
@@ -384,6 +389,8 @@
         approve: "同意",
         reject: "拒绝",
         dismiss: "关闭这条提醒",
+        details: "详情",
+        collapse: "收起",
         testAttention: "这是一条测试提醒：DSH 需要你的操作",
         testDone: "测试提醒 · 回复完成示例",
         testApproval: "这是一条测试审批：点「同意 / 拒绝」试试快捷裁决",
@@ -411,6 +418,8 @@
         approve: "Approve",
         reject: "Reject",
         dismiss: "Dismiss this alert",
+        details: "Details",
+        collapse: "Collapse",
         testAttention: "This is a test alert: DSH is waiting for your input",
         testDone: "Test alert · reply-finished sample",
         testApproval: "This is a test approval: try the Approve / Reject buttons to settle it",
@@ -733,10 +742,26 @@
       return q;
     }
 
+    // A plain toast needs a tag unique to that one notification. It used to be
+    // "dsh-notify-me-" + kind, which leans on renotify:true to replace the
+    // previous banner of the same kind; Electron ignores that flag, so the
+    // second toast of a kind silently overwrote the first and never re-alerted
+    // (issue #15). A unique tag makes every toast a fresh alert everywhere,
+    // while renotify stays meaningful on the web. Date.now() alone collides
+    // when two alerts land in the same millisecond, hence the counter; the
+    // >>> 0 wrap keeps it from ever going negative. Approval toasts keep their
+    // stable "dsh-notify-me-attention-<key>" tag: closeNotificationTag() looks
+    // them up by it when the request is settled.
+    var toastSeq = 0;
+    function uniqueToastTag(kind) {
+      toastSeq = (toastSeq + 1) >>> 0;
+      return "dsh-notify-me-" + kind + "-" + toastSeq + "-" + Date.now();
+    }
+
     function showToast(kind, title, body, sessionId, quick) {
       if (!canToast()) return;
       try {
-        var tag = quick ? quick.tag : "dsh-notify-me-" + kind;
+        var tag = quick ? quick.tag : uniqueToastTag(kind);
         if (quick && bridgeActive()) {
           var d = texts();
           try {
@@ -817,9 +842,11 @@
       ".dnm-ov-attention .dnm-ov-dot{color:var(--dsw-alias-state-warning-primary,#f59e0b);opacity:1}" +
       ".dnm-ov-done .dnm-ov-dot{color:var(--dsw-alias-state-success-primary,#22c55e);opacity:1}" +
       ".dnm-ov-title{flex:1;min-width:0;font-weight:600;font-size:13px;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}" +
-      ".dnm-ov-x{flex:none;border:0;background:transparent;color:inherit;opacity:.6;font-size:15px;line-height:15px;padding:0 2px;cursor:pointer;font-family:inherit}" +
-      ".dnm-ov-x:hover{opacity:1}" +
+      ".dnm-ov-x,.dnm-ov-more{flex:none;border:0;background:transparent;color:inherit;opacity:.6;font-size:15px;line-height:15px;padding:0 2px;cursor:pointer;font-family:inherit}" +
+      ".dnm-ov-x:hover,.dnm-ov-more:hover{opacity:1}" +
+      ".dnm-ov-more{font-size:11px;opacity:.8;white-space:nowrap}" +
       ".dnm-ov-body{color:var(--dsw-alias-label-secondary,rgba(220,222,226,.86));font-size:12px;line-height:18px;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden;word-break:break-word}" +
+      ".dnm-ov.dnm-ov-open .dnm-ov-body{display:block;-webkit-line-clamp:unset;max-height:40vh;overflow:auto}" +
       ".dnm-ov-actions{display:flex;gap:8px;margin-top:2px}" +
       ".dnm-ov-btn{flex:1;border:1px solid var(--dsw-alias-border-l2,rgba(128,128,128,.4));background:var(--dsw-alias-bg-layer-1,rgba(255,255,255,.06));color:inherit;border-radius:8px;padding:5px 10px;font-size:12px;font-family:inherit;cursor:pointer}" +
       ".dnm-ov-btn:hover{background:var(--dsw-alias-bg-layer-2,rgba(255,255,255,.12))}" +
@@ -895,17 +922,30 @@
       }
     }
     function overlayCount() { return Object.keys(overlayCards).length; }
-    // 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;
+    // 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
+    // "详情 / Details" toggle exposes the body that the CSS clamps to 3 lines.
+    function drawOverlayCard(kind, title, body, sessionId, quick, opts) {
+      opts = opts || {};
       var layer = ensureOverlayLayer();
       if (!layer) return false;
+      // One card per approval key: a re-delivery (the quieted copy that fires
+      // when the page is backgrounded) must not stack a second card.
+      if (quick && typeof quick.key === "string") {
+        var known = Object.keys(overlayCards);
+        for (var k = 0; k < known.length; k++) {
+          if (overlayCards[known[k]].key === quick.key) return false;
+        }
+      }
       var d = texts();
       try {
         var id = "ov" + (++overlaySeq);
+        var baseClass = "dnm-ov dnm-ov-" + (kind === "attention" ? "attention" : "done");
         var card = document.createElement("div");
-        card.className = "dnm-ov dnm-ov-" + (kind === "attention" ? "attention" : "done");
+        card.className = baseClass;
         card.setAttribute("role", kind === "attention" ? "alert" : "status");
         var head = document.createElement("div");
         head.className = "dnm-ov-head";
@@ -914,6 +954,22 @@
         var label = document.createElement("span");
         label.className = "dnm-ov-title";
         label.textContent = String(title == null ? "" : title);
+        var more = null;
+        if (opts.expand && body) {
+          more = document.createElement("button");
+          more.type = "button";
+          more.className = "dnm-ov-more";
+          more.setAttribute("aria-label", d.details);
+          more.setAttribute("aria-expanded", "false");
+          more.textContent = d.details;
+          more.onclick = function (ev) {
+            if (ev && ev.stopPropagation) ev.stopPropagation();
+            var open = card.className.indexOf("dnm-ov-open") !== -1;
+            card.className = baseClass + (open ? "" : " dnm-ov-open");
+            more.textContent = open ? d.details : d.collapse;
+            more.setAttribute("aria-expanded", open ? "false" : "true");
+          };
+        }
         var close = document.createElement("button");
         close.type = "button";
         close.className = "dnm-ov-x";
@@ -925,6 +981,7 @@
         };
         head.appendChild(dot);
         head.appendChild(label);
+        if (more) head.appendChild(more);
         head.appendChild(close);
         card.appendChild(head);
         if (body) {
@@ -954,10 +1011,12 @@
         }
         // A click on the card body opens the conversation, exactly like a toast
         // body click — and here it is an ordinary page gesture, so it reaches the
-        // desktop's dsh:// raise path even though a worker click would not.
+        // desktop's dsh:// raise path even though a worker click would not. The
+        // overlay channel also takes the card down; the fallback card stays, so
+        // the decision is still one click away after a look at the conversation.
         card.onclick = function () {
           if (config.autoFocus) focusSession(sessionId || null);
-          dismissOverlay(id);
+          if (opts.dismissOnClick !== false) dismissOverlay(id);
         };
         layer.appendChild(card);
         var rec = { card: card, key: (quick && quick.key) ? quick.key : null, kind: kind, timer: null };
@@ -971,6 +1030,29 @@
         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.
+    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 });
+    }
     // Sound: WebAudio beeps (no asset needed). The context only runs after a
     // user gesture; we unlock it on the first pointer/key event.
     var audioCtx = null;
@@ -1325,6 +1407,7 @@
       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();
       } else {
@@ -1964,7 +2047,7 @@
       });
     } catch (e) {}
     // keep in sync with package.json "version" on every release
-    api.version = "1.10.2";
+    api.version = "1.10.4";
     api.setConfig = function (patch) { return setConfigLocal(patch); };
     api.resetConfig = function () {
       try {
@@ -2177,16 +2260,16 @@
       autoFocus: "点击通知回到对应对话",
       autoFocusHint: "点通知会切到这条提醒所属的对话；关掉后点击不做任何事。",
       quickActions: "审批通知上直接裁决",
-      quickActionsHint: "审批通知上带「同意 / 拒绝」，点一下即完成裁决，不用切回页面。需要 Service Worker（http://127.0.0.1 或 https），用不了时退回普通通知。",
+      quickActionsHint: "审批通知上带「同意 / 拒绝」，点一下即完成裁决，不用切回页面。需要 Service Worker（http://127.0.0.1 或 https）；用不了时按钮改画在窗口角落的卡片上（桌面端就是这条路）。",
       quickApprovalNote: "「同意」等价于审批卡片上的「允许一次」，只放行这一次。",
       bridgeOff: "快捷裁决按钮暂不可用（",
-      bridgeOffTail: "）：审批通知会退回不带按钮的普通样式。",
-      bridgeOffDesktop: "系统通知没有「同意 / 拒绝」按钮：桌面端页面（dsh-app://）注册不了 Service Worker（宿主少给 allowServiceWorkers 特权），按钮发不出来。想一键裁决就把「提醒方式」切到「页面浮层」。",
+      bridgeOffTail: "）：系统通知没有按钮，按钮改画在窗口角落的卡片上。",
+      bridgeOffDesktop: "系统通知本身没有「同意 / 拒绝」按钮：桌面端页面（dsh-app://）注册不了 Service Worker（宿主少给 allowServiceWorkers 特权）。审批类提醒会同时在窗口角落弹一张卡片，按钮就在卡片上；想只留卡片、不弹系统通知，把「提醒方式」切到「页面浮层」。",
       overlay: "页面浮层提醒",
       overlayHint: "在窗口角落画提醒卡片：窗口在哪块屏，它就在哪块屏；系统通知只会出现在主屏，主屏不看时用它。不需要通知权限，卡片上能直接「同意 / 拒绝」。与系统通知二选一。",
     channelLabel: "通知类型",
     overlaySeg: "浮层提醒",
-    channelHint: "系统通知只会出现在主屏，进通知中心要权限，桌面端也没有「同意 / 拒绝」按钮；页面浮层画在 DSH 窗口所在的那块屏，不需要权限，卡片上能直接裁决。两个只能选一个。",
+    channelHint: "系统通知只会出现在主屏，进通知中心要权限，桌面端的通知本身没有「同意 / 拒绝」按钮（审批会额外在窗口角落弹一张可点击的卡片）；页面浮层画在 DSH 窗口所在的那块屏，不需要权限，卡片上能直接裁决。两个只能选一个。",
       overlayCorner: "浮层位置",
       overlayCornerHint: "贴在 DSH 窗口的哪个角；窗口在哪块屏，浮层就出现在哪块屏。",
       overlayPosTR: "右上",
@@ -2194,7 +2277,7 @@
       overlayPosTL: "左上",
       overlayPosBL: "左下",
       overlayQuickNote: "浮层上的「同意」同样等价于审批卡片上的「允许一次」，与通知按钮一致。",
-      testApprovalNoBridge: "已发普通测试通知（快捷裁决按钮需要 Service Worker，当前环境没有，按钮渲染不了）。",
+      testApprovalNoBridge: "已发测试提醒：系统通知没有按钮，快捷裁决按钮画在窗口角落的卡片上。",
       testNeedsQuick: "先打开上面的「审批通知上直接裁决」才能测按钮。",
       volume: "音量",
       language: "通知语言",
@@ -2307,16 +2390,16 @@
       autoFocus: "Click a toast to open that conversation",
       autoFocusHint: "A click switches to the conversation the alert came from; off means a click does nothing.",
       quickActions: "Decide approvals from the toast",
-      quickActionsHint: "Approval notifications carry Approve / Reject; one click settles the request without switching back. Needs a Service Worker browser (http://127.0.0.1 or https), else plain toasts.",
+      quickActionsHint: "Approval notifications carry Approve / Reject; one click settles the request without switching back. Needs a Service Worker browser (http://127.0.0.1 or https); when it is unavailable the buttons land on a card in the window corner (the Desktop shell's route).",
       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: "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.",
+      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 no Approve / Reject buttons on the Desktop shell. 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.",
+    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.",
       overlayPosTR: "Top right",
@@ -2324,7 +2407,7 @@
       overlayPosTL: "Top left",
       overlayPosBL: "Bottom left",
       overlayQuickNote: "\"Approve\" here equals \"Allow once\" on the approval card — the same decision the toast buttons send.",
-      testApprovalNoBridge: "Plain test notification sent (quick-decision buttons need a Service Worker, which this environment lacks, so they cannot render).",
+      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",
       language: "Notification language",

package/package.json

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