dsh-later 1.2.0 → 1.3.0

package/CHANGELOG.md

@@ -4,6 +4,16 @@
 
 ## 未发布
 
+## 1.3.0 — 2026-10-10
+
+- **feat** `/later` 附件支持：带图提交不再被拦截，附件写进 sidecar，到点按记录顺序拼在文本块之后代发。
+- **feat** 多次写法（Beta，默认开启）：`+1h*3`（等间隔×N）、`+1h+1h+0.5h`（相对链式）、`15:32+16:32`（绝对锚点）展开成 N 条独立 one-shot 任务。上限 10 条、最小间隔 60 秒。
+- **feat** 残片守卫：`+1h*3 x` 不再静默误解析成单条，一律显式报错。
+- **fix** 时区墙钟修复：UTC 负偏移时区（如 `America/Los_Angeles`）整体错一天的问题。
+- **refactor** UI 图标全部改用官方图标集 `@deepseek-ai/dsh-client-ui-primitives`（issue #19）：删掉 8 处手写内联 SVG 与 3 处文本符号，统一换 `<IconXxxRegular />`。dock 操作按钮改为 portal 化的 `DockTip` tooltip。
+- **fix** 定时配置面板抬升面对齐官方风格（issue #24）：背景/描边/阴影/圆角/层级对齐官方 PickerPopover，面板 portal 到 document.body，定位改用官方 `useAnchoredPosition`。
+- **docs** README 与微文案补上多次写法、附件与设置项说明。
+
 ## 1.2.0 — 2026-10-09
 
 - **feat** 暴露跨插件「定时任务摘要」公共 API（issue #17）。

package/README.en.md

@@ -36,7 +36,7 @@ Click the **"Schedule send"** button to the right of the input box. The panel us
 
 ### Time formats
 
-All of these are accepted (`/schedule`, `/later`, and the panel's custom time share the same parser):
+All of these are accepted (`/schedule`, `/later`, and the panel's custom time share the same parser; the rows marked *commands only* are rejected by the panel):
 
 | Kind | Examples |
 |---|---|
@@ -44,23 +44,55 @@ All of these are accepted (`/schedule`, `/later`, and the panel's custom time sh
 | Time today | `15:32` · `9点` · `9点半` · `1532` |
 | Relative day + time | `明天9点` · `后天 10:00` |
 | Date + time | `8月21日 15:32` · `2026-08-21 15:32` · `0821-1532` |
+| Repeat, fixed interval (*commands only*) | `+1h*3 drink water` · `+30m×2 check build` |
+| Repeat, chained sequence (*commands only*) | `+1h+1h+0.5h watch the rollout` · `+1h +30m submit report` |
+| Anchor sequence (*commands only*) | `15:32+16:32+17:32 three meetings` · `9:00+1d+1d standup` · `明天9点+1h` |
+
+The three bolded rows above are **[Advanced syntax (Beta)](#configuration)** and can be switched off together in settings; every other form is unaffected.
 
 A bare time (like `1532`) rolls over to tomorrow if it has already passed today (up to 7 days). Writing `明天`/`后天` is taken literally — if that time has passed you are told to use a concrete date instead. A month/day only (like `8月21日`) rolls over to next year when this year's has passed.
 
+Multi-shot rules — **the first occurrence lands after the first interval**:
+
+| Input | Expands to |
+|---|---|
+| `+1h*3` | t+1h, t+2h, t+3h |
+| `+1h+1h+0.5h` | t+1h, t+2h, t+2.5h (chained — good for "2 h → 1 h → 30 min before the deadline" nagging) |
+| `15:32+16:32+17:32` | those three clock times today |
+| `23:00+01:00` | 23:00 today, **tomorrow** 01:00 (an earlier time in the chain rolls over, same rule as a single shot) |
+| `9:00+1d+1d` | 09:00 on three consecutive days |
+
+At most **10 tasks** per command, and multi-shot intervals must be **≥ 60 seconds** (single shots are unrestricted — `/later +5s` still works). `*`, `×` and `x` all work, an optional Chinese counter suffix is accepted (`*3次`), and the count must be followed by a space. Every occurrence is an **independent task**: cancel it, edit it or send it early on its own, and `/later` attachments are carried by each one. Absolute times (`15:32`, `明天9点`) do **not** accept `*count` — you get an explicit error instead of a silently wrong single task.
+
+Chains allow exactly **one direction: an absolute anchor, then forward accumulation.** `+1h+15:32` (a clock time after a duration) is rejected rather than guessed.
+
+One difference between anchor and relative chains (deliberate, not a bug):
+
+| Form | Stored as | Pausable | Across DST |
+|---|---|---|---|
+| `+1h*3` / `+1h+30m` (relative) | `after` | ✅ | —— |
+| `15:32+16:32` / `9:00+1d` (anchor) | `at` | ❌ (button disabled with a reason) | ✅ wall clock holds: on a fall-back day `9:00+1d` is **25 h** later and still 09:00, whereas adding 86400 s would drift to 08:00 |
+
+`+1d` advances by **calendar day**, not 86400 seconds — which is why `+1d*3` and `9:00+1d+1d` differ in zones with DST (the former counts real seconds, the latter counts wall clock). A wall clock that does not exist (the hour skipped by the spring-forward) is an error, never a silently shifted time.
+
 ### Commands
 
 | Command | Effect |
 |---|---|
 | `/schedule <time> <content>` | Create a reminder (shows up in the conversation when due) |
 | `/later <time> <content>` | Delayed send: deliver the content later as yourself |
-| `/schedule every <interval> <content>` | Recurring reminder (interval ≥ 5 min) |
+| `/later <time>*<count> <content>` | Same, expanded into N delayed sends (`+1h*3`) |
+| `/schedule <time>+<time> <content>` | Same, a chained sequence expanded into N reminders (`+1h+30m`) |
+| `/later <clock>+<clock> <content>` | Anchor sequence: expand by wall-clock instants (`15:32+16:32`, `9:00+1d+1d`) |
 
 ```
 /schedule 明天9点 提交周报
 /later 1532 提醒团队同步进度
+/later +1h*3 起来喝水
+/later +2h+1h+30m 催我交周报
 ```
 
-The model can also call user tools on your behalf to create/inspect/delete/edit reminders (`user_schedule_create` / `user_schedule_list` / `user_schedule_delete` / `user_schedule_edit`).
+The model can also call user tools on your behalf to create/inspect/delete/edit reminders (`user_schedule_create` / `user_schedule_list` / `user_schedule_delete` / `user_schedule_edit`). **Endlessly recurring** reminders (every hour, forever) are only reachable this way: ask the model "每小时提醒我喝水" and it creates an `every_seconds` schedule — such a task has no end condition and must be deleted by hand.
 
 ### Pending dock
 
@@ -186,6 +218,13 @@ Works out of the box. Adjust in **DSH Settings → Plugins → Session Scheduler
 | Allow long prompts | Lift the 1000-character default cap | Off |
 | Custom cap | Character cap when `allowLongPrompts` is on | 1000 |
 | Work hours / lunch / night quiet | Five HH:mm fields driving smart slots and auto-scheduling | See settings page |
+| Interjection delivery | Which queue "Send interjection" uses: own turn (default, safe) / current turn (faster, can drop in an edge case) | Own turn |
+| Delivery confirmation / on unconfirmed | Whether to verify a reminder really landed, and what to do when it isn't confirmed | On / keep |
+| Clock icon style | `auto` (by kernel version) / `modern` / `classic` | auto |
+| **Advanced syntax** (Beta) | Master switch for multi-shot forms: `+1h*3`, `+1h+1h+0.5h`, `15:32+16:32`, `9:00+1d`. When off, those forms are rejected with a pointer back to settings | **On** |
+
+> Advanced syntax is marked Beta not because it is untested (43 new unit tests cover it) but because **the expanded result still needs real-world observation**: whether 10 tasks flood the dock, and whether the 60-second floor and 10-task cap are the right sizes.
+> Turning it off does **not** restore the old silent mis-parse (`+1h*3 x` creating one task whose content is `*3 x`) — that was a bug, not a fallback. The residual-token guard is independent of this switch and always on.
 
 > Advanced: defaults can also be overridden at startup via `cordis.patch.yml` (e.g. `maxSchedules`) — see `docs/` and the schema.
 

package/README.md

@@ -36,7 +36,7 @@
 
 ### 时间格式
 
-以下写法都认（`/schedule`、`/later` 与面板自定义时间共用）：
+以下写法都认（`/schedule`、`/later` 与面板自定义时间共用；标了「仅 `/later` `/schedule`」的写法面板不收）：
 
 | 类型 | 示例 |
 |---|---|
@@ -44,23 +44,55 @@
 | 当天时刻 | `15:32` · `9点` · `9点半` · `1532` |
 | 相对日 + 时刻 | `明天9点` · `后天 10:00` |
 | 日期 + 时刻 | `8月21日 15:32` · `2026-08-21 15:32` · `0821-1532` |
+| **重复 · 等间隔**（仅 `/later` `/schedule`） | `+1h*3 喝水` · `+30m×2 看构建` · `两小时后×3次` |
+| **重复 · 链式序列**（仅 `/later` `/schedule`） | `+1h+1h+0.5h 盯发布` · `+1h +30m 交周报` |
+| **锚点序列**（仅 `/later` `/schedule`） | `15:32+16:32+17:32 三会` · `9:00+1d+1d 打卡` · `明天9点+1h` |
+
+上表三行加粗的都属于 **[高级语法（Beta）](#配置)**，可在设置里一键关闭；其余写法不受开关影响。
 
 只写时刻（如 `1532`）时，若今天已过会自动顺延到明天（最多 7 天）；写了 `明天`/`后天` 则按字面理解，该时刻已过会提示改用具体日期；只写月日（如 `8月21日`）时，今年已过则顺延到明年。
 
+多次写法的规则（**首次落在第一个间隔之后**）：
+
+| 写法 | 展开成 |
+|---|---|
+| `+1h*3` | t+1h、t+2h、t+3h |
+| `+1h+1h+0.5h` | t+1h、t+2h、t+2.5h（链式累加，用来写「提前 2h→1h→30m」这类梯度催办） |
+| `15:32+16:32+17:32` | 今天 15:32、16:32、17:32（三个挂钟时刻） |
+| `23:00+01:00` | 今天 23:00、**次日** 01:00（后一个时刻更早则自动顺延，规则同单条） |
+| `9:00+1d+1d` | 连续三天都是 9:00 |
+
+一次最多 **10 条**，多次写法的间隔不低于 **60 秒**（单条不受此限，`/later +5s` 照旧）。`*` `×` `x` 都认，可跟中文量词（`*3次`），次数后面要留空格。每条都是**独立任务**：可单独取消、编辑、插话发送（暂停见下表）。
+
+序列里只允许**「绝对时刻开头，往后累加」**这一个方向：`+1h+15:32` 会明确报错，不会猜。
+
+**锚点序列与相对序列的一处差别**（有意为之，不是 bug）：
+
+| 写法 | 落库类型 | 能暂停 | 跨夏令时 |
+|---|---|---|---|
+| `+1h*3` / `+1h+30m`（相对） | `after` | ✅ | —— |
+| `15:32+16:32` / `9:00+1d`（锚点） | `at` | ❌（按钮置灰并说明原因） | ✅ 墙钟不变：`9:00+1d` 在回拨日相隔 **25 小时**仍是 9:00，按 86400 秒累加会漂成 8:00 |
+
+`9:00+1d` 里的「一天」按**日历日**推进（不是 86400 秒），所以 `+1d*3` 与 `9:00+1d+1d` 在有夏令时的时区结果不同——前者按真实秒数、后者按墙钟。落到不存在的墙钟（前拨跳过的那一小时）会报错而不是悄悄挪时刻。绝对时刻（`15:32`、`明天9点`）不支持 `*次数`，会明确报错而不是悄悄变成一条。
+
 ### 命令
 
 | 命令 | 作用 |
 |---|---|
 | `/schedule <时间> <内容>` | 创建一条定时提醒（到点出现在对话里） |
 | `/later <时间> <内容>` | 延迟发送：到点以你的身份发出该内容 |
-| `/schedule every <周期> <内容>` | 周期性提醒（周期 ≥ 5 分钟） |
+| `/later <时间>*<次数> <内容>` | 同上，展开成 N 条代发（`+1h*3`） |
+| `/schedule <时间>+<时间> <内容>` | 同上，链式序列展开成 N 条提醒（`+1h+30m`） |
+| `/later <时刻>+<时刻> <内容>` | 锚点序列：按挂钟时刻展开（`15:32+16:32`、`9:00+1d+1d`） |
 
 ```
 /schedule 明天9点 提交周报
 /later 1532 提醒团队同步进度
+/later +1h*3 起来喝水
+/later +2h+1h+30m 催我交周报
 ```
 
-模型也可以直接调用用户工具为你创建/查询/修改提醒（`user_schedule_create` / `user_schedule_list` / `user_schedule_delete` / `user_schedule_edit`）。
+模型也可以直接调用用户工具为你创建/查询/修改提醒（`user_schedule_create` / `user_schedule_list` / `user_schedule_delete` / `user_schedule_edit`）。**无限周期**提醒（每 1 小时一直发下去）只有这条路：让模型说「每小时提醒我喝水」，它会用 `every_seconds` 建一条周期任务；周期任务没有结束条件，需要你手动删。
 
 ### 待发送 dock
 
@@ -186,6 +218,13 @@ dsh plugin --profile web add "file:/path/to/dsh-later"
 | 允许长文本 | 解除 1000 字符默认下限 | 关闭 |
 | 自定义上限 | `allowLongPrompts` 开启时的字符上限 | 1000 |
 | 工作时间 / 午休 / 晚间静默 | 智能时段 5 个 HH:mm 字段，决定快捷芯片与智能排期 | 见设置页 |
+| 插话投递方式 | 「插话发送」进哪个队列：独立成一轮（默认，安全）/ 当前轮（更快，极端情况下会丢） | 独立成一轮 |
+| 投递确认 / 未确认处理 | 是否核对提醒真的送达，以及未确认时保留还是丢弃 | 开 / 保留 |
+| 时钟图标风格 | `auto`（按内核版本）/ `modern` / `classic` | auto |
+| **高级语法** <span>Beta</span> | 多次写法总开关：`+1h*3`、`+1h+1h+0.5h`、`15:32+16:32`、`9:00+1d`。关闭后这些写法被明确拒绝并提示回设置开启 | **开启** |
+
+> 「高级语法」标 Beta 的原因不是没测（43 个新单测覆盖），而是**展开后的观感仍需观察**：一次命令写 10 条会不会刷屏、60 秒地板与 10 条上限是否合适。
+> 关闭它**不会**退回旧版的静默误解析（`+1h*3 x` 建成一条内容为 `*3 x` 的任务）——那是 bug，不在可回退的功能面里；残片守卫与本开关无关，始终生效。
 
 > 进阶：也可以用 `cordis.patch.yml` 在启动期覆盖默认值（如 `maxSchedules`），见 `docs/` 与 schema。