npm - dsh-dingtalk - Versions diffs - 0.2.2 → 0.3.0 - Mend

dsh-dingtalk 0.2.2 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (12) hide show

package/CHANGELOG.md ADDED Viewed

@@ -0,0 +1,22 @@
+# 更新记录
+[返回简介](README.md) · [使用说明](docs/USAGE.md) · [验证记录](docs/VALIDATION.md)
+## 0.3.0 (2026-10-26)
+- Add this plugin’s own update controls and independent preferences. Automatic installation stays off until explicitly enabled.
+- Confirm manual installs, preserve local sources and disabled state, pause for tasks or unsaved changes, and use native DSH recovery without forced restarts.
+- Require the public DSH 0.2.1-rc.3 update APIs; Suite components remain managed through Suite.
+## 0.2.3（2026-10-26）
+- 宿主取消信号传递到发送请求，超时覆盖响应体读取，错误脱敏机器人凭据与签名；超时明确提示送达状态未知，避免盲目重复发送。
+- Windows 回归 32 项通过、0 项跳过；宿主与未验收范围见[本次记录](docs/validation-0.2.3.md)。
+## 0.2.2 (2026-09-28)
+- 更新官方 Harness 0.2.0-rc.1 的兼容声明和共同加载验证；运行时代码未变。验证范围见[验证记录](docs/VALIDATION.md)。
+## 更早的改动
+完整历史可查阅 [GitHub 提交记录](https://github.com/STARDUSTLC666/dsh-dingtalk/commits/main)。

package/README.en.md CHANGED Viewed

@@ -1,131 +1,54 @@
 # dsh-dingtalk
-![npm](https://img.shields.io/npm/v/dsh-dingtalk) ![downloads](https://img.shields.io/npm/dm/dsh-dingtalk) ![license](https://img.shields.io/github/license/STARDUSTLC666/dsh-dingtalk) ![stars](https://img.shields.io/github/stars/STARDUSTLC666/dsh-dingtalk?style=social)
+[中文](README.md)
-[![Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com)
+![dsh-dingtalk whale girl plugin cover](https://raw.githubusercontent.com/STARDUSTLC666/dsh-dingtalk/main/assets/cover-whale-girl.png)
-DeepSeek Harness DingTalk group robot notification plugin: lets the agent **push Markdown / plain-text messages to a DingTalk group one-way**. Pure plugin implementation, zero core changes, works out of the box.
+Send task notifications to a DingTalk group robot.
-Pure Node implementation, **cross-platform** (one codebase for Windows / macOS / Linux), depends only on `node:crypto` and the built-in `fetch` — no runtime dependencies, no native binaries.
+[![npm](https://img.shields.io/npm/v/dsh-dingtalk)](https://www.npmjs.com/package/dsh-dingtalk) [![downloads](https://raw.githubusercontent.com/STARDUSTLC666/dsh-suite/npm-downloads/assets/dsh-dingtalk-downloads.svg)](https://www.npmjs.com/package/dsh-dingtalk)
-## Tools
+Feedback and contributions are welcome: report [issues](https://github.com/STARDUSTLC666/dsh-dingtalk/issues) or submit [pull requests](https://github.com/STARDUSTLC666/dsh-dingtalk/pulls).
-| Tool | Purpose |
-|---|---|
-| `dingtalk_notify` | Send a **Markdown** message to the configured DingTalk group (`title` heading + `text` Markdown body) |
-| `dingtalk_text` | Send a **plain-text** message to the configured DingTalk group (`content`) |
+## What it does
-Example:
+- Send Markdown or plain-text group notifications.
+- Support signed robot requests.
+- Check configuration and explain common errors.
-> Send a message to the DingTalk group: title "Build complete", body "Pipeline #123 passed ✅".
+## Install
-## Compatibility
-Validation host: Harness `0.2.0-rc.1` built from official sources (commit `407e65c8`) with Node `24.16.0` on 2026-09-28. All 28 plugin tests pass in an isolated environment; all 18 plugins mount together in one host registering 3 tools, with tool schemas and health-check contracts passing. No live ports or external services were exercised in this round.
-## Installation
-```sh
-dsh plugin --profile web add dsh-dingtalk
-```
-After installing, restart `dsh web`. The plugin ships with an empty config and **won't crash startup**; calling any `dingtalk_*` tool before configuration returns a clear Chinese configuration hint.
-## Uninstall
+In DSH Desktop, install `dsh-dingtalk` from the Plugins panel. If the bundled dsh command is available:
 ```bash
-dsh plugin --profile web remove dsh-dingtalk
-```
-Then restart the web service. To clean up fully, also remove the plugin entry from your profile `cordis.patch.yml` if you overrode it.
-## Step 1: Get the webhook and signing secret
-Use DingTalk's **custom robot** method — **no enterprise app or admin permission needed**:
-1. Open the target DingTalk group → **Group settings** → **Smart group assistant** → **Add robot** → **Custom (connect a custom service via Webhook)**
-2. The robot name is arbitrary; under **Security settings, check "Sign" (加签)**, then finish
-3. Copy two things:
-   - **Webhook URL**: like `https://oapi.dingtalk.com/robot/send?access_token=xxxx`
-   - **Signing secret (secret)**: like `SECxxxx` (only appears after checking "Sign")
-> For security settings it's recommended to check only "Sign". If you also check "Custom keywords", the robot validates whether the message contains the keyword — that's DingTalk server-side behavior, not handled by this plugin (see "Known limitations").
-## Configuration
-In your profile's `cordis.patch.yml` (under `$DSH_HOME/profiles/<name>/`), override the `tool-dingtalk` line, then restart:
-```yaml
-- id: tool-dingtalk
-  config:
-    webhook: https://oapi.dingtalk.com/robot/send?access_token=你的token
-    secret: SEC你的加签密钥        # 可选，但强烈建议；也可用环境变量 DSH_DINGTALK_SECRET
+dsh plugin --profile desktop add dsh-dingtalk
 ```
-### Full configuration
+For the web version, replace `desktop` with `web`. Restart DSH after installation.
-| Field | Default | Description |
-|---|---|---|
-| `webhook` | required | Full webhook URL of the robot (`?access_token=...`) |
-| `secret` | empty | Signing secret; when omitted, falls back to the `DSH_DINGTALK_SECRET` env var. Empty = no signing |
-| `timeoutMs` | `10000` | Request timeout in milliseconds (1000–60000) |
+## Start using it
-### Store the secret in an environment variable
+Configure the robot webhook and signing secret, then ask to send a result summary to your group.
-If you don't want to write the secret into YAML, write only `webhook` and set an environment variable:
+## Requirements and configuration
-```sh
-# Windows PowerShell
-$env:DSH_DINGTALK_SECRET = "SEC你的加签密钥"
-# 或系统环境变量里加一条 DSH_DINGTALK_SECRET
-```
+Requires a DingTalk robot webhook. This plugin provides one-way notifications.
-An explicit `secret` in YAML takes precedence over the environment variable.
+Detailed configuration, tool arguments and troubleshooting are in the [usage guide](docs/USAGE.en.md). For standalone development, follow the Node requirement in [package.json](package.json).
-## Security notes
+## Documentation
-- **The webhook is the key to group notifications**: anyone who knows it can post to the group. Don't commit `cordis.patch.yml` to any Git repo; for the `secret`, prefer the `DSH_DINGTALK_SECRET` env var.
-- This plugin is **one-way notification only** (agent → DingTalk group); it never reads messages from the group and has no two-way bot capability.
-- This plugin performs no outbound telemetry; the `secret` is used in memory only to compute an HMAC signature, which is appended to the URL and sent to DingTalk's official endpoint.
+- [Usage and troubleshooting](docs/USAGE.en.md)
+- [Changelog](CHANGELOG.md)
+- [Validation scope and history](docs/VALIDATION.md)
+- [Report a problem or suggest a feature](https://github.com/STARDUSTLC666/dsh-dingtalk/issues)
-## Signing algorithm (matches the official one)
-When a `secret` is present, the request URL appends `timestamp` (millisecond timestamp) and `sign`:
-```text
-stringToSign = timestamp + "
-" + secret
-sign = urlencode(base64(HmacSHA256(secret, stringToSign)))
-```
+## Plugin updates
-Identical to this plugin's `computeDingTalkSign`, equivalent to `urllib.parse.quote_plus(base64(...))` in the official Python example.
+Requires DSH 0.2.1-rc.3 or newer. Each plugin provides its own check, release-note and confirmed-install controls on its page or in settings. Preferences are independent. Automatic checks are on by default; **automatic installation is off by default**. Explicitly enabled automatic updates only install compatible stable patches while idle with no unsaved changes. Disable, defer or ignore reminders per plugin. DSH is never restarted or upgraded automatically, and local-source installs are preserved. Suite components clearly direct updates through Suite.
-## Known limitations
-- **One-way notification only**: no support for enterprise self-built apps, no receiving group messages / two-way bots (@robot replies, etc.); these are v0.2+ directions.
-- **No automatic workaround for custom keyword validation**: if the robot checks "Custom keywords" on DingTalk's side, messages must contain the keyword or DingTalk returns an error (errcode 310000 can also appear for this reason). This plugin attributes 310000 to signing; please also check the keyword setting.
-- **No settings page**: v0.1 is a "node half-body"; configuration only via `cordis.patch.yml` (+ env var). A Web settings page is planned for v0.2+.
-- **Message types**: currently only Markdown (`dingtalk_notify`) and plain text (`dingtalk_text`); image / Link / FeedCard / ActionCard etc. come later.
-- **Markdown rendering**: DingTalk robot Markdown syntax differs slightly from standard Markdown (e.g., headings, links); write according to DingTalk's syntax.
-## Error code reference
-| errcode | Meaning | Suggestion |
-|---|---|---|
-| `0` | Success | — |
-| `310000` | Signing validation failed (see the keyword note above) | Check that `secret` is correct and matches the robot's "Sign" setting |
-| `120001` | `access_token` expired | Re-copy the webhook URL from the DingTalk group and overwrite `webhook` |
-| other | Server error | Check the returned `errmsg` |
-## Development
-```sh
-pnpm install
-pnpm run build   # tsc → lib/
-pnpm test        # 构建 + node --test（加签算法/配置解析/客户端封装/注册与中文报错）
-```
+Older releases need one manual update in native plugin management to acquire these controls. Publishing to npm does not replace an existing user installation.
 ## License
-MIT. This is a community plugin, not affiliated with DeepSeek or DingTalk; `@deepseek-ai/*` is an officially reserved namespace.
+[MIT](LICENSE)

package/README.md CHANGED Viewed

@@ -1,146 +1,54 @@
-[English](README.en.md)
 # dsh-dingtalk
-> **让 agent 在钉钉群里说话**：Markdown / 纯文本通知，加签安全，零依赖。
-![npm version](https://img.shields.io/npm/v/dsh-dingtalk?label=npm&color=blue) ![npm downloads](https://img.shields.io/npm/dm/dsh-dingtalk) ![license](https://img.shields.io/npm/l/dsh-dingtalk) ![stars](https://img.shields.io/github/stars/STARDUSTLC666/dsh-dingtalk?style=social)
-[![Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com)
-DeepSeek Harness 钉钉群机器人通知插件：让 agent 能**单向推送 Markdown / 纯文本消息到钉钉群**。纯插件实现，零核心改动，安装即可用。
-纯 Node 实现，**全平台通用**（Windows / macOS / Linux 同一份代码），只依赖 `node:crypto` 与内置 `fetch`，无运行时依赖、无原生二进制。
-## 兼容性
-验证宿主：官方源码构建的 Harness `0.2.0-rc.1`（commit `407e65c8`）+ Node `24.16.0`（2026-09-28）。28 项插件测试在隔离环境全部通过；同一个宿主里 18 个插件共同加载，注册 3 个工具，工具 schema 与健康检查契约通过。本轮未启用真实端口与外部服务。
+[English](README.en.md)
-## 工具一览
+![dsh-dingtalk 鲸鱼娘插件封面](https://raw.githubusercontent.com/STARDUSTLC666/dsh-dingtalk/main/assets/cover-whale-girl.png)
-| 工具 | 作用 |
-|---|---|
-| `dingtalk_notify` | 向配置的钉钉群发一条 **Markdown** 消息（`title` 标题 + `text` Markdown 正文） |
-| `dingtalk_text` | 向配置的钉钉群发一条 **纯文本** 消息（`content`） |
+把任务结果发送到钉钉群机器人的通知插件。
-示例对话：
+[![npm](https://img.shields.io/npm/v/dsh-dingtalk)](https://www.npmjs.com/package/dsh-dingtalk) [![downloads](https://raw.githubusercontent.com/STARDUSTLC666/dsh-suite/npm-downloads/assets/dsh-dingtalk-downloads.svg)](https://www.npmjs.com/package/dsh-dingtalk)
-> 帮我给钉钉群发一条消息：标题「构建完成」，正文「流水线 #123 已通过 ✅」。
+欢迎使用，遇到问题或有改进建议，请提交 [issues](https://github.com/STARDUSTLC666/dsh-dingtalk/issues) 和 [PR](https://github.com/STARDUSTLC666/dsh-dingtalk/pulls)。
-## 兼容性
+## 功能
-已在官方 `@deepseek-ai/dsh@0.1.5-rc.1`、Node `24.16.0` 上验证（2026-09-11）：18 个组件与 Modlens 同载，工具 schema、技能注册及离线只读调用检查通过。采用 `cordis.patch.yml` + `dsh.bundle.patch` 组合包模型。Node 要求与该版本 Harness 一致：22.19 及以上的 22.x，或 24 及以上。外部服务的实际业务操作需按各组件配置单独验证。
+- 发送 Markdown 或纯文本群通知。
+- 支持机器人加签。
+- 提供配置自检与常见错误说明。
 ## 安装
-```sh
-dsh plugin --profile web add dsh-dingtalk
-```
-装好后重启 `dsh web`。插件自带空配置，**不会弄崩启动**；配置前调用任何 `dingtalk_*` 工具都会返回明确的中文配置提示。
-## 卸载
+桌面版可在「插件」面板按包名 `dsh-dingtalk` 安装。已配置 dsh 命令时也可使用：
 ```bash
-dsh plugin --profile web remove dsh-dingtalk
+dsh plugin --profile desktop add dsh-dingtalk
 ```
-卸载后重启 Web 服务。如需彻底清理，可再手动删除自己 profile `cordis.patch.yml` 中覆盖的插件行。
+网页版把命令中的 `desktop` 改为 `web`。安装后重启 DSH。
-## 第一步：拿到 webhook 与加签密钥
+## 开始使用
-用钉钉【自定义机器人】方式，**不需要企业应用、不需要管理员权限**：
+配置群机器人 webhook 和加签密钥后，可说：“把这份结果摘要发到钉钉群。”
-1. 打开目标钉钉群 → **群设置** → **智能群助手** → **添加机器人** → **自定义（通过 Webhook 接入自定义服务）**
-2. 机器人名称随意，**安全设置勾选「加签」**，完成
-3. 复制两样东西：
-   - **Webhook 地址**：形如 `https://oapi.dingtalk.com/robot/send?access_token=xxxx`
-   - **加签密钥（secret）**：形如 `SECxxxx`（勾选「加签」后才会出现）
+## 依赖与配置
-> 安全设置推荐只勾选「加签」。如果同时勾选了「自定义关键词」，机器人会校验消息里是否包含关键词——那是钉钉服务端行为，本插件不处理（见「已知限制」）。
-## 配置
-在你 profile 的 `cordis.patch.yml` 里覆盖 `tool-dingtalk` 行（在 `$DSH_HOME/profiles/<name>/` 下），然后重启：
-```yaml
-- id: tool-dingtalk
-  config:
-    webhook: https://oapi.dingtalk.com/robot/send?access_token=你的token
-    secret: SEC你的加签密钥        # 可选，但强烈建议；也可用环境变量 DSH_DINGTALK_SECRET
-```
+需要钉钉群机器人 webhook；本插件提供单向通知。
-### 完整配置项
+详细配置、工具参数与排错见[使用说明](docs/USAGE.md)。从源码独立开发时，Node 要求以 [package.json](package.json) 为准。
-| 字段 | 默认 | 说明 |
-|---|---|---|
-| `webhook` | 必填 | 机器人完整 Webhook 地址（`?access_token=...`） |
-| `secret` | 空 | 加签密钥；省略时回退环境变量 `DSH_DINGTALK_SECRET`。不填=不加签 |
-| `timeoutMs` | `10000` | 请求超时毫秒数（1000–60000） |
+## 文档
-### 用环境变量存 secret
+- [使用与排错](docs/USAGE.md)
+- [更新记录](CHANGELOG.md)
+- [验证范围与历史记录](docs/VALIDATION.md)
+- [问题反馈与功能建议](https://github.com/STARDUSTLC666/dsh-dingtalk/issues)
-不想把密钥写进 YAML 的话，可以只写 `webhook`，然后设置环境变量：
-```sh
-# Windows PowerShell
-$env:DSH_DINGTALK_SECRET = "SEC你的加签密钥"
-# 或系统环境变量里加一条 DSH_DINGTALK_SECRET
-```
-显式写在 YAML 里的 `secret` 优先于环境变量。
-## 安全须知
-- **webhook 就是群通知的钥匙**：知道它的人可以往群里发消息。请勿把 `cordis.patch.yml` 提交到任何 Git 仓库；`secret` 更推荐用环境变量 `DSH_DINGTALK_SECRET`。
-- 本插件**只做单向通知**（agent → 钉钉群），不会读取群里任何消息，也没有双向机器人能力。
-- 本插件不做任何联网上报；`secret` 只在内存中用于计算 HMAC 签名，签名拼进 URL 发给钉钉官方接口。
-## 加签算法（对照官方）
-`secret` 存在时，请求 URL 追加 `timestamp`（毫秒时间戳）与 `sign`：
-```text
-stringToSign = timestamp + "
-" + secret
-sign = urlencode(base64(HmacSHA256(secret, stringToSign)))
-```
-与本插件 `computeDingTalkSign` 一致，等价于官方 Python 示例的 `urllib.parse.quote_plus(base64(...))`。
-## 已知限制
-- **仅单向通知**：不支持企业自建应用、不支持接收群消息 / 双向机器人（@机器人 回复等），这些是 v0.2+ 的方向。
-- **不支持自定义关键词校验的自动规避**：如果机器人在钉钉侧勾选了「自定义关键词」，消息必须包含关键词，否则钉钉返回错误（errcode 310000 也可能因此出现）。本插件把 310000 归因于加签，请同时检查关键词设置。
-- **无设置页**：v0.1 是「node 半身」，配置只能走 `cordis.patch.yml`（+ 环境变量）。Web 设置页在 v0.2+。
-- **消息类型**：目前只支持 Markdown（`dingtalk_notify`）与纯文本（`dingtalk_text`）两种；图片/Link/FeedCard/ActionCard 等类型后续再加。
-- **Markdown 渲染**：钉钉机器人 Markdown 语法与标准 Markdown 略有差异（如标题、链接），请按钉钉语法书写。
-## 错误码速查
-| errcode | 含义 | 建议 |
-|---|---|---|
-| `0` | 成功 | — |
-| `310000` | 加签校验失败（也见上面关键词说明） | 检查 `secret` 是否填对、是否与机器人「加签」设置一致 |
-| `120001` | `access_token` 失效 | 到钉钉群重新复制 webhook 地址，覆盖 `webhook` |
-| 其他 | 服务端错误 | 看返回的 `errmsg` |
-## 开发
-```sh
-pnpm install
-pnpm run build   # tsc → lib/
-pnpm test        # 构建 + node --test（加签算法/配置解析/客户端封装/注册与中文报错）
-```
+## 插件更新
-## 协议
+需要 DSH 0.2.1-rc.3 或更新版本。每个插件在自己的页面或设置项提供检查、更新记录与确认安装入口，开关独立保存。自动检查默认开启；**自动安装默认关闭**，只有明确授权后，兼容的稳定补丁才会在空闲且没有未保存修改时安装。可单独关闭、推迟或忽略提醒；不会强制重启 DSH、升级 DSH 本体或替换本地源码安装。Suite 安装的组件会明确提示通过 Suite 整包更新。
-MIT。这是一个社区插件，与 DeepSeek 官方及钉钉官方无关；`@deepseek-ai/*` 为官方保留命名空间。
+旧版用户先在官方插件管理中手动更新一次，之后才会获得此入口。发布到 npm 不会直接替换用户已经安装的版本。
-## 相关插件
+## License
-- [dsh-calendar](https://github.com/STARDUSTLC666/dsh-calendar) — CalDAV 日历五件套
-- [dsh-dingtalk](https://github.com/STARDUSTLC666/dsh-dingtalk) — 钉钉群通知（零依赖）
-- [dsh-email](https://github.com/STARDUSTLC666/dsh-email) — 邮件六件套 + Web 设置页
+[MIT](LICENSE)

package/docs/USAGE.en.md ADDED Viewed

@@ -0,0 +1,124 @@
+# dsh-dingtalk usage guide
+[Overview](../README.en.md) · [Changelog](../CHANGELOG.md) · [Validation](VALIDATION.md)
+## Cancellation and delivery
+Cancellation aborts the HTTP wait, including response-body reads. A timeout does not prove the message was not received: check the group before retrying. The plugin never retries automatically and redacts robot credentials/signatures from errors.
+## Tools
+| Tool | Purpose |
+|---|---|
+| `dingtalk_notify` | Send a **Markdown** message to the configured DingTalk group (`title` heading + `text` Markdown body) |
+| `dingtalk_text` | Send a **plain-text** message to the configured DingTalk group (`content`) |
+Example:
+> Send a message to the DingTalk group: title "Build complete", body "Pipeline #123 passed ✅".
+## Installation
+```sh
+dsh plugin --profile web add dsh-dingtalk
+```
+After installing, restart `dsh web`. The plugin ships with an empty config and **won't crash startup**; calling any `dingtalk_*` tool before configuration returns a clear Chinese configuration hint.
+## Uninstall
+```bash
+dsh plugin --profile web remove dsh-dingtalk
+```
+Then restart the web service. To clean up fully, also remove the plugin entry from your profile `cordis.patch.yml` if you overrode it.
+## Step 1: Get the webhook and signing secret
+Use DingTalk's **custom robot** method — **no enterprise app or admin permission needed**:
+1. Open the target DingTalk group → **Group settings** → **Smart group assistant** → **Add robot** → **Custom (connect a custom service via Webhook)**
+2. The robot name is arbitrary; under **Security settings, check "Sign" (加签)**, then finish
+3. Copy two things:
+   - **Webhook URL**: like `https://oapi.dingtalk.com/robot/send?access_token=xxxx`
+   - **Signing secret (secret)**: like `SECxxxx` (only appears after checking "Sign")
+> For security settings it's recommended to check only "Sign". If you also check "Custom keywords", the robot validates whether the message contains the keyword — that's DingTalk server-side behavior, not handled by this plugin (see "Known limitations").
+## Configuration
+In your profile's `cordis.patch.yml` (under `$DSH_HOME/profiles/<name>/`), override the `tool-dingtalk` line, then restart:
+```yaml
+- id: tool-dingtalk
+  config:
+    webhook: https://oapi.dingtalk.com/robot/send?access_token=你的token
+    secret: SEC你的加签密钥        # 可选，但强烈建议；也可用环境变量 DSH_DINGTALK_SECRET
+```
+### Full configuration
+| Field | Default | Description |
+|---|---|---|
+| `webhook` | required | Full webhook URL of the robot (`?access_token=...`) |
+| `secret` | empty | Signing secret; when omitted, falls back to the `DSH_DINGTALK_SECRET` env var. Empty = no signing |
+| `timeoutMs` | `10000` | Request timeout in milliseconds (1000–60000) |
+### Store the secret in an environment variable
+If you don't want to write the secret into YAML, write only `webhook` and set an environment variable:
+```sh
+# Windows PowerShell
+$env:DSH_DINGTALK_SECRET = "SEC你的加签密钥"
+# 或系统环境变量里加一条 DSH_DINGTALK_SECRET
+```
+An explicit `secret` in YAML takes precedence over the environment variable.
+## Security notes
+- **The webhook is the key to group notifications**: anyone who knows it can post to the group. Don't commit `cordis.patch.yml` to any Git repo; for the `secret`, prefer the `DSH_DINGTALK_SECRET` env var.
+- This plugin is **one-way notification only** (agent → DingTalk group); it never reads messages from the group and has no two-way bot capability.
+- This plugin performs no outbound telemetry; the `secret` is used in memory only to compute an HMAC signature, which is appended to the URL and sent to DingTalk's official endpoint.
+## Signing algorithm (matches the official one)
+When a `secret` is present, the request URL appends `timestamp` (millisecond timestamp) and `sign`:
+```text
+stringToSign = timestamp + "
+" + secret
+sign = urlencode(base64(HmacSHA256(secret, stringToSign)))
+```
+Identical to this plugin's `computeDingTalkSign`, equivalent to `urllib.parse.quote_plus(base64(...))` in the official Python example.
+## Known limitations
+- **One-way notification only**: no support for enterprise self-built apps, no receiving group messages / two-way bots (@robot replies, etc.); these are v0.2+ directions.
+- **No automatic workaround for custom keyword validation**: if the robot checks "Custom keywords" on DingTalk's side, messages must contain the keyword or DingTalk returns an error (errcode 310000 can also appear for this reason). This plugin attributes 310000 to signing; please also check the keyword setting.
+- **No settings page**: v0.1 is a "node half-body"; configuration only via `cordis.patch.yml` (+ env var). A Web settings page is planned for v0.2+.
+- **Message types**: currently only Markdown (`dingtalk_notify`) and plain text (`dingtalk_text`); image / Link / FeedCard / ActionCard etc. come later.
+- **Markdown rendering**: DingTalk robot Markdown syntax differs slightly from standard Markdown (e.g., headings, links); write according to DingTalk's syntax.
+## Error code reference
+| errcode | Meaning | Suggestion |
+|---|---|---|
+| `0` | Success | — |
+| `310000` | Signing validation failed (see the keyword note above) | Check that `secret` is correct and matches the robot's "Sign" setting |
+| `120001` | `access_token` expired | Re-copy the webhook URL from the DingTalk group and overwrite `webhook` |
+| other | Server error | Check the returned `errmsg` |
+## Development
+```sh
+pnpm install
+pnpm run build   # tsc → lib/
+pnpm test        # 构建 + node --test（加签算法/配置解析/客户端封装/注册与中文报错）
+```
+## License
+MIT. This is a community plugin, not affiliated with DeepSeek or DingTalk; `@deepseek-ai/*` is an officially reserved namespace.

package/docs/USAGE.md ADDED Viewed

@@ -0,0 +1,130 @@
+# dsh-dingtalk 使用说明
+[返回简介](../README.md) · [更新记录](../CHANGELOG.md) · [验证记录](VALIDATION.md)
+## 取消和送达状态
+取消会终止正在等待的 HTTP 请求，包括响应体读取。超时无法证明远端未收到消息；先核对群记录再决定是否重发，插件不会自动重发。诊断错误会隐藏机器人凭据与签名。
+## 工具一览
+| 工具 | 作用 |
+|---|---|
+| `dingtalk_notify` | 向配置的钉钉群发一条 **Markdown** 消息（`title` 标题 + `text` Markdown 正文） |
+| `dingtalk_text` | 向配置的钉钉群发一条 **纯文本** 消息（`content`） |
+示例对话：
+> 帮我给钉钉群发一条消息：标题「构建完成」，正文「流水线 #123 已通过 ✅」。
+## 安装
+```sh
+dsh plugin --profile web add dsh-dingtalk
+```
+装好后重启 `dsh web`。插件自带空配置，**不会弄崩启动**；配置前调用任何 `dingtalk_*` 工具都会返回明确的中文配置提示。
+## 卸载
+```bash
+dsh plugin --profile web remove dsh-dingtalk
+```
+卸载后重启 Web 服务。如需彻底清理，可再手动删除自己 profile `cordis.patch.yml` 中覆盖的插件行。
+## 第一步：拿到 webhook 与加签密钥
+用钉钉【自定义机器人】方式，**不需要企业应用、不需要管理员权限**：
+1. 打开目标钉钉群 → **群设置** → **智能群助手** → **添加机器人** → **自定义（通过 Webhook 接入自定义服务）**
+2. 机器人名称随意，**安全设置勾选「加签」**，完成
+3. 复制两样东西：
+   - **Webhook 地址**：形如 `https://oapi.dingtalk.com/robot/send?access_token=xxxx`
+   - **加签密钥（secret）**：形如 `SECxxxx`（勾选「加签」后才会出现）
+> 安全设置推荐只勾选「加签」。如果同时勾选了「自定义关键词」，机器人会校验消息里是否包含关键词——那是钉钉服务端行为，本插件不处理（见「已知限制」）。
+## 配置
+在你 profile 的 `cordis.patch.yml` 里覆盖 `tool-dingtalk` 行（在 `$DSH_HOME/profiles/<name>/` 下），然后重启：
+```yaml
+- id: tool-dingtalk
+  config:
+    webhook: https://oapi.dingtalk.com/robot/send?access_token=你的token
+    secret: SEC你的加签密钥        # 可选，但强烈建议；也可用环境变量 DSH_DINGTALK_SECRET
+```
+### 完整配置项
+| 字段 | 默认 | 说明 |
+|---|---|---|
+| `webhook` | 必填 | 机器人完整 Webhook 地址（`?access_token=...`） |
+| `secret` | 空 | 加签密钥；省略时回退环境变量 `DSH_DINGTALK_SECRET`。不填=不加签 |
+| `timeoutMs` | `10000` | 请求超时毫秒数（1000–60000） |
+### 用环境变量存 secret
+不想把密钥写进 YAML 的话，可以只写 `webhook`，然后设置环境变量：
+```sh
+# Windows PowerShell
+$env:DSH_DINGTALK_SECRET = "SEC你的加签密钥"
+# 或系统环境变量里加一条 DSH_DINGTALK_SECRET
+```
+显式写在 YAML 里的 `secret` 优先于环境变量。
+## 安全须知
+- **webhook 就是群通知的钥匙**：知道它的人可以往群里发消息。请勿把 `cordis.patch.yml` 提交到任何 Git 仓库；`secret` 更推荐用环境变量 `DSH_DINGTALK_SECRET`。
+- 本插件**只做单向通知**（agent → 钉钉群），不会读取群里任何消息，也没有双向机器人能力。
+- 本插件不做任何联网上报；`secret` 只在内存中用于计算 HMAC 签名，签名拼进 URL 发给钉钉官方接口。
+## 加签算法（对照官方）
+`secret` 存在时，请求 URL 追加 `timestamp`（毫秒时间戳）与 `sign`：
+```text
+stringToSign = timestamp + "
+" + secret
+sign = urlencode(base64(HmacSHA256(secret, stringToSign)))
+```
+与本插件 `computeDingTalkSign` 一致，等价于官方 Python 示例的 `urllib.parse.quote_plus(base64(...))`。
+## 已知限制
+- **仅单向通知**：不支持企业自建应用、不支持接收群消息 / 双向机器人（@机器人 回复等），这些是 v0.2+ 的方向。
+- **不支持自定义关键词校验的自动规避**：如果机器人在钉钉侧勾选了「自定义关键词」，消息必须包含关键词，否则钉钉返回错误（errcode 310000 也可能因此出现）。本插件把 310000 归因于加签，请同时检查关键词设置。
+- **无设置页**：v0.1 是「node 半身」，配置只能走 `cordis.patch.yml`（+ 环境变量）。Web 设置页在 v0.2+。
+- **消息类型**：目前只支持 Markdown（`dingtalk_notify`）与纯文本（`dingtalk_text`）两种；图片/Link/FeedCard/ActionCard 等类型后续再加。
+- **Markdown 渲染**：钉钉机器人 Markdown 语法与标准 Markdown 略有差异（如标题、链接），请按钉钉语法书写。
+## 错误码速查
+| errcode | 含义 | 建议 |
+|---|---|---|
+| `0` | 成功 | — |
+| `310000` | 加签校验失败（也见上面关键词说明） | 检查 `secret` 是否填对、是否与机器人「加签」设置一致 |
+| `120001` | `access_token` 失效 | 到钉钉群重新复制 webhook 地址，覆盖 `webhook` |
+| 其他 | 服务端错误 | 看返回的 `errmsg` |
+## 开发
+```sh
+pnpm install
+pnpm run build   # tsc → lib/
+pnpm test        # 构建 + node --test（加签算法/配置解析/客户端封装/注册与中文报错）
+```
+## 协议
+MIT。这是一个社区插件，与 DeepSeek 官方及钉钉官方无关；`@deepseek-ai/*` 为官方保留命名空间。
+## 相关插件
+- [dsh-calendar](https://github.com/STARDUSTLC666/dsh-calendar) — CalDAV 日历五件套
+- [dsh-dingtalk](https://github.com/STARDUSTLC666/dsh-dingtalk) — 钉钉群通知（零依赖）
+- [dsh-email](https://github.com/STARDUSTLC666/dsh-email) — 邮件六件套 + Web 设置页

package/docs/VALIDATION.md ADDED Viewed

@@ -0,0 +1,15 @@
+# dsh-dingtalk 验证记录
+## 2026-10-26：0.2.3
+[本次修复、回归与未验收范围](validation-0.2.3.md)。
+本页整理原 README 的历史验证说明，保留当时的版本、日期与范围。自动测试、启动检查、浏览器操作和真实服务验收分别记录，不能相互替代。更详细的版本验收文件仍保留在仓库中。
+## 原中文记录
+验证宿主：官方源码构建的 Harness `0.2.0-rc.1`（commit `407e65c8`）+ Node `24.16.0`（2026-09-28）。28 项插件测试在隔离环境全部通过；同一个宿主里 18 个插件共同加载，注册 3 个工具，工具 schema 与健康检查契约通过。本轮未启用真实端口与外部服务。
+## Original English record
+Validation host: Harness `0.2.0-rc.1` built from official sources (commit `407e65c8`) with Node `24.16.0` on 2026-09-28. All 28 plugin tests pass in an isolated environment; all 18 plugins mount together in one host registering 3 tools, with tool schemas and health-check contracts passing. No live ports or external services were exercised in this round.

package/docs/validation-0.2.3.md ADDED Viewed

@@ -0,0 +1,19 @@
+# 0.2.3 验证记录
+日期：2026-10-26。官方 Windows 宿主：DSH 0.2.1-rc.3。
+## 行为变化
+宿主取消信号传递到发送请求，超时覆盖响应体读取，错误脱敏机器人凭据与签名；超时明确提示送达状态未知，避免盲目重复发送。
+## 验证与限制
+- Windows 本地：32 项，32 通过、0 跳过；没有把跳过计为通过。
+- 官方 RC.3 tools.execute 接入本地模拟 HTTP 对端，验证正常回执、读取响应体时取消和超时，以及连接关闭；没有向真实钉钉群发送消息。
+- GitHub 的跨平台 CI 和 npm 发布完整性以该版本工作流及 registry 为准；本记录不把本地测试等同于已发布。
+## English
+Host cancellation reaches the HTTP request; timeout also covers the response body. Errors redact webhook credentials and signatures. A timeout reports unknown delivery and asks users to check the group before retrying.
+Runtime/account limits are listed above. Synthetic peers and model adapters do not establish live account delivery or model quality.