dsh-notify-me 1.14.2 → 1.14.3

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to **dsh-notify-me** are documented here.
 
+## [1.14.3] — 2026-10-26
+
+### 修复
+
+- **当前会话的通知正文改用真实会话标题**：以前关于「已经在屏幕上的那个会话」的通知，「回复完成」的正文、以及「需要你」的会话行，对当前会话第一行写死占位符「当前对话 / Current conversation」，而其他会话都带侧栏标题。现在当前会话也从同一条列表行取标题（新增 `sessionTitleOf()`，与侧栏同一个 `displayTitle`/`title`，宿主改名后下一条通知即生效）；只有列表还没给出标题的新会话（或列表里暂时没有这一行）才回落到占位符。宿主 0.1.x 与 0.2.x 共用这条 adapter，两代都修复（issue #20）。
+
+### 测试
+
+- 冒烟新增 `currentSessionTitle()`：当前会话的「需要你」正文以会话标题开头、不含「当前对话」；「回复完成」正文等于标题；没有标题的会话仍回落「当前对话」。`modernHost()` 里当前会话「回复完成」的断言从占位符改为列表标题。`npm test` 全绿（冒烟 + cordis 真宿主两套）。
+
+### 文档
+
+- `docs/listing.md` 版本口径同步到 1.14.3。
+
 ## [1.14.2] — 2026-10-24
 
 ### 修复

package/README.en.md

@@ -80,7 +80,7 @@ Web users can also test the approval buttons, which then appear on the notificat
 window.__dshNotifyMe.test("done")        // "reply finished" sample
 window.__dshNotifyMe.test("attention")   // "needs you" sample
 window.__dshNotifyMe.test("approval")    // Approve / Reject when the bridge is available; a plain notification otherwise (which is what Desktop gets)
-window.__dshNotifyMe.debug()             // the bridge field reports the state: "active" = buttons work
+window.__dshNotifyMe.debug()             // the bridge field reports the state ("active" = buttons work); a refused toast leaves its platform message in lastToastReject
 ```
 
 If no test notification appears, check in this order: whether the notification permission was declined (click once on the page and choose **Allow**; or address-bar lock → Site settings → Notifications → Allow → reload), whether DSH was restarted after installing, and whether the browser's notifications are switched off in the OS settings.
@@ -327,6 +327,7 @@ The cases where it will not raise are the same ones listed under [Known limitati
 **Platform differences**
 
 - Quick-decision buttons need a Service Worker: `http://127.0.0.1` and `https` work, `http://192.168.x.x`-style LAN addresses do not; **the Desktop (`dsh-app://`) is tested and cannot register a Service Worker** (the host does not grant the `allowServiceWorkers` privilege), so approval toasts fall back to their buttonless form. When the host renders no notification buttons, the `bridge` field of `debug()` explains why, and nothing else is affected.
+- Windows caps a toast tag at 64 characters, and Chromium hands the platform the whole `n#<origin>#<tag>` string — the desktop page's `dsh-app://app` alone takes 16. The plugin sizes each tag against the current `location.origin` and, when it does not fit, keeps a readable prefix and swaps the tail for a short hash, so a tag seen through `debug()` may be shortened; if the platform still refuses one, its message lands in `debug().lastToastReject` and the settings test button reports it instead of claiming the toast was sent.
 - On Desktop (Windows) a toast click can still fail to raise the window: when the target window is owned by a higher integrity level (elevated / UAC), sits on another virtual desktop, has its foreground repeatedly stolen by another process, or is hidden to the tray with `SW_HIDE`, the host script answers `FOCUSED=0` and the route answers `202`, with the conversation switch intact (see [How the Desktop window gets raised](#how-the-desktop-window-gets-raised)).
 - macOS: alerts, sound, the title marker and toast-click navigation carry no platform assumptions and work as usual; but DSH Desktop (Electron) system notifications require the app to be signed — an unsigned build simply emits no notification — and whether the official macOS build meets that precondition is untested; notification button rendering on the macOS desktop host is likewise untested (the Windows desktop host is tested and renders none).
 
@@ -349,7 +350,7 @@ The cases where it will not raise are the same ones listed under [Known limitati
 ```powershell
 node --check lib\client.js
 node --check lib\index.js
-node smoke\smoke-test.cjs        # offline state-machine test: three host generations + master switch + zh/en cases + the quick-decision bridge (worker half included) + idle detection and toast self-dismiss
+node smoke\smoke-test.cjs        # offline state-machine test: three host generations + master switch + zh/en cases + the quick-decision bridge (worker half included) + idle detection and toast self-dismiss + toast tag length handling
 node smoke\cordis-host-test.mjs  # real-cordis end-to-end (skips when no local DSH installation is found)
 powershell -NoProfile -File lib\focus-window.ps1 -ProcessId 0   # manual raise test, the last line should be FOCUSED=1
 npm pack --dry-run               # preview the published tarball

package/README.md

@@ -80,7 +80,7 @@ Web 用户可再测审批按钮，通知上会带「同意 / 拒绝」。桌面
 window.__dshNotifyMe.test("done")        // 「完成」示例
 window.__dshNotifyMe.test("attention")   // 「需要你」示例
 window.__dshNotifyMe.test("approval")    // 桥可用时带「同意 / 拒绝」按钮；否则只发普通通知（桌面端即如此）
-window.__dshNotifyMe.debug()             // 桥接状态看 bridge 字段，active = 按钮可用
+window.__dshNotifyMe.debug()             // 桥接状态看 bridge 字段（active = 按钮可用）；最近一次被平台拒发的原因在 lastToastReject
 ```
 
 没有测试通知时，先检查：通知权限是否被拒绝（在页面上点一下 → 选「允许」；或地址栏锁 → 站点设置 → 通知 → 允许 → 刷新）、装完没重启 DSH、系统设置里浏览器通知被关。
@@ -326,6 +326,7 @@ DSH Desktop 是一层 Electron 壳，页面跑在 `dsh-app://app` 下：DOM 的
 **平台差异**
 
 - 快捷裁决按钮要 Service Worker：`http://127.0.0.1`、`https` 可用，`http://192.168.x.x` 这类局域网地址不行；**桌面端（`dsh-app://`）已实测无法注册 Service Worker**（宿主未开放 `allowServiceWorkers` 特权），审批通知退回无按钮样式。宿主不渲染通知按钮时，`debug()` 的 `bridge` 字段会说明原因，其余功能不受影响。
+- Windows 的系统通知标签上限 64 字符，而 Chromium 交给平台的是 `n#<origin>#<tag>` 整串——桌面页面 `dsh-app://app` 一项就占去 16 个。插件按当前 `location.origin` 算剩余预算，超长时保留可读前缀、尾部换成短哈希，所以 `debug()` 里看到的标签可能被截短；平台仍然拒发时，原文记在 `debug().lastToastReject`，设置页的测试按钮也会如实报出来，不再「提示已发送但什么都没弹」。
 - 桌面端（Windows）点通知后窗口仍可能抬不起来：目标窗口属于更高完整性级别（提权 / UAC）、在另一个虚拟桌面、前台被别的进程反复抢回去，或窗口被 `SW_HIDE` 隐藏到托盘时，宿主脚本回 `FOCUSED=0`、路由回 `202`，对话照常切（详见[桌面端怎么抬窗的](#桌面端怎么抬窗的)）。
 - macOS：提醒、提示音、标题标记、点通知跳转都没有平台假设，照常工作；但 DSH Desktop（Electron）的系统通知要求应用已签名，未签名的通知直接发不出去，官方 macOS 版是否满足这一前提未实测；审批按钮在 macOS 桌面宿主上的渲染同样未实测（Windows 桌面端已实测不渲染）。
 
@@ -348,7 +349,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 时自动跳过）
 powershell -NoProfile -File lib\focus-window.ps1 -ProcessId 0   # 手动验证抬窗脚本，末行应是 FOCUSED=1
 npm pack --dry-run               # 预览发布包

package/lib/client.js

@@ -1702,13 +1702,26 @@
         fire("attention", copy.title, copy.body, false, copy.sessionId, copy.quick || null);
       }
     }
-    // A display label for a session row ("current" maps to the localized
-    // "当前对话 / Current conversation" placeholder).
+    // A display label for a session row; an empty label and the legacy
+    // "current" sentinel fall back to the localized "当前对话 / Current
+    // conversation" placeholder, which now only stands in for a session whose
+    // title the list cannot supply yet.
     function sessionLabelText(row) {
       var raw = row && row.label;
       if (!raw || raw === "current") return texts().current;
       return raw;
     }
+    // The session's own sidebar title, or "" while the host has not published
+    // one (a brand-new session) or the list does not carry the row at all.
+    // Read live, so a title the host fills in later reaches the next alert.
+    function sessionTitleOf(sid) {
+      try {
+        var st = listStore && listStore.getSnapshot();
+        var sum = st && st.byId && st.byId[sid];
+        if (sum) return sum.displayTitle || sum.title || "";
+      } catch (e) {}
+      return "";
+    }
     // The session the user is looking at, or null while the list is not ready.
     // Two host generations own this fact differently:
     //   * <= 0.1.5-rc.3: the list snapshot carried `current`;
@@ -2001,7 +2014,11 @@
       }
     }
 
-    // face -> row adapter (selected session, rich data)
+    // face -> row adapter (selected session, rich data). The label is the
+    // session's own sidebar title like any other row, so "needs you" and
+    // "reply finished" name the conversation instead of the old placeholder;
+    // the placeholder remains the fallback while the title is unknown
+    // (issue #20).
     function evalSessionFace(sessionId, snap) {
       if (sessionId !== currentFaceId) return;
       var pend = (snap.pending || []).map(function (p) {
@@ -2015,7 +2032,7 @@
         face: true,
         faceSnap: snap,
         currentId: sessionId,
-        label: "current"
+        label: sessionTitleOf(sessionId) || "current"
       });
     }
     // list row -> adapter (every other listed session)
@@ -2302,7 +2319,7 @@
       });
     } catch (e) {}
     // keep in sync with package.json "version" on every release
-    api.version = "1.14.2";
+    api.version = "1.14.3";
     api.setConfig = function (patch) { return setConfigLocal(patch); };
     api.resetConfig = function () {
       try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-notify-me",
-  "version": "1.14.2",
+  "version": "1.14.3",
   "description": "离开 DSH 页面也能收到提醒：需要你操作 / 后台回复完成时发系统通知、标题标记与提示音，支持审批快捷裁决与外部推送，Web 版与桌面版均可用。",
   "license": "MIT",
   "type": "module",