npm - dsh-lark-bot - Versions diffs - 0.15.0 → 0.15.2 - Mend

dsh-lark-bot 0.15.0 → 0.15.2

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 (2) hide show

package/README.md +253 -579
package/package.json +12 -4

package/README.md CHANGED Viewed

@@ -1,31 +1,11 @@
-> [!CAUTION]
-> **⚠️ 官方渠道声明 · Official channels only**
->
-> 唯一官方仓库是 [PlutoKeating/dsh-lark-bot](https://github.com/PlutoKeating/dsh-lark-bot)；唯一官方 npm 包是
-> `dsh-lark-bot`（同源双包 `dsh-feishu-bot`，维护者 `plutokeating`）。**本项目从不提供 Windows 可执行文件
-> （.exe），也没有任何“下载即运行”的安装包。** 任何以本项目名义提供 exe / “下载后双击运行”的页面、仓库或
-> 第三方分发渠道（例如 `tarraencompassing61/dsh-lark-bot` 这类仿冒仓库）均为**假冒 / 恶意来源**——请勿下载
-> 或运行其中的任何附件。官方安装唯一命令：
->
-> `npx dsh-lark-bot@latest setup --profile dsh-lark`
->
-> The **only official repository** is [PlutoKeating/dsh-lark-bot](https://github.com/PlutoKeating/dsh-lark-bot);
-> the **only official npm packages** are `dsh-lark-bot` and `dsh-feishu-bot` (maintainer `plutokeating`).
-> **This project never ships Windows executables (.exe) or any “download-and-run” installer.** Any page,
-> repository, or third-party channel offering such downloads under this project’s name (including impostor
-> repositories like `tarraencompassing61/dsh-lark-bot`) is a **counterfeit / malicious source** — do not download
-> or execute anything from it. The only official install command:
->
-> `npx dsh-lark-bot@latest setup --profile dsh-lark`
->
-> 仿冒仓库停留在 v0.7.0 快照；正版版本差距见上方徽章。Evidence:
-> [docs/security/2026-08-17-impostor-repo-evidence/](docs/security/2026-08-17-impostor-repo-evidence/README.md) ·
-> Official download page: [docs/DOWNLOAD.md](docs/DOWNLOAD.md)
+> **⚠️ 仅认准官方渠道：** 唯一官方仓库 [PlutoKeating/dsh-lark-bot](https://github.com/PlutoKeating/dsh-lark-bot)，唯一官方 npm 包 `dsh-lark-bot`（同源双包 `dsh-feishu-bot`，维护者 `plutokeating`）。**本项目从不提供 Windows 可执行文件（.exe），也没有任何“下载即运行”的安装包**——任何以本项目名义提供 exe / “下载后双击运行”的页面、仓库或第三方分发渠道均为**假冒 / 恶意来源**，请勿下载或运行。官方安装唯一命令：`npx dsh-lark-bot@latest setup --profile dsh-lark`。仿冒仓库取证与完整声明见文末「假冒仓库警告」及 [docs/security/2026-08-17-impostor-repo-evidence/](docs/security/2026-08-17-impostor-repo-evidence/README.md)。
 <h1 align="center">dsh-lark-bot</h1>
+<p align="center">🌏 英文版：[README_EN.md](README_EN.md)</p>
 <p align="center">
-  <strong>把 DeepSeek Harness 接入飞书 | Bridge DeepSeek Harness into Feishu / Lark</strong>
+  <strong>把 DeepSeek Harness 接入飞书</strong>
 </p>
 <p align="center">
@@ -35,6 +15,7 @@
   <img src="https://img.shields.io/badge/License-AGPLv3-blue" alt="License">
   <img src="https://img.shields.io/badge/status-released-blue" alt="Status">
   <a href="https://dshfind.com/zh/plugins/PlutoKeating/dsh-lark-bot?ref=badge"><img src="https://dshfind.com/api/badge/PlutoKeating/dsh-lark-bot?lang=zh" alt="dshfind"></a>
+  <a href="https://dshbase.com/zh/plugins/dsh-lark-bot"><img src="https://dshbase.com/badges/dsh-lark-bot.svg" alt="dshbase 实测可装"></a>
   <a href="https://github.com/PlutoKeating/dsh-lark-bot/releases"><img src="https://img.shields.io/github/v/release/PlutoKeating/dsh-lark-bot?sort=semver&label=latest%20release" alt="Latest release"></a>
   <a href="https://github.com/PlutoKeating/dsh-lark-bot/commits/main"><img src="https://img.shields.io/github/commits-since/PlutoKeating/dsh-lark-bot/v0.7.0?label=commits%20since%20v0.7.0" alt="Commits since v0.7.0"></a>
 </p>
@@ -45,184 +26,119 @@
 让 **DeepSeek Harness（`dsh`）** 成为你飞书里的一员：在手机、群聊、话题里指挥本机 coding agent，把对话、任务、卡片和**项目工作区**都收进同一个协作流。
-<br>
-*Turn **DeepSeek Harness (`dsh`)** into a member of your Feishu / Lark workspace — drive your local coding agent from mobile, group chats and topics, and fold conversations, tasks, cards and **project workspaces** into one collaborative flow.*
 </div>
-<div align="center">
+<p align="center">
+  🌐 官网落地页 <a href="https://dsh-lark-bot.arr2018.dpdns.org">dsh-lark-bot.arr2018.dpdns.org</a>
+  · 备用 <a href="https://plutokeating.github.io/dsh-lark-bot/">GitHub Pages</a>
+</p>
-<a href="https://dshfind.com/zh/plugins/PlutoKeating/dsh-lark-bot?ref=badge"><img src="https://dshfind.com/api/card/PlutoKeating/dsh-lark-bot?lang=zh" alt="dshfind" width="440"></a>
+---
-</div>
+## 场景
----
+**你的 DeepSeek Harness 只能“贴身”用？** dsh 跑在本机，每次看进度、改任务都得回到电脑前；离开工位后任务卡住、跑偏甚至 dsh 崩了，你都收不到任何消息——回来才发现白等半天。
-## 项目介绍 | What & Why
-**用在什么场景？** 你在飞书 / Lark（私聊、群聊、话题）里指挥本机 DeepSeek Harness（`dsh`）
-coding agent：发消息就收流式卡片与工具调用过程，把项目工作区、并行任务、会话归档都收进同一
-个协作流。适合需要多项目隔离、角色分工、并行任务与故障自愈的开发者与团队。
-**Where does it fit?** Drive your local DeepSeek Harness (`dsh`) coding agent from Feishu /
-Lark — DMs, group chats and topics — with streaming cards, isolated project workspaces,
-parallel tasks, session archival and self-healing when things break.
-**功能亮点（以下六项为 dsh-lark-bot 全网独有组合）| Highlights (exclusive to dsh-lark-bot)**：
-- 🆘 **Guardian 安全网守护 —— “永远叫得应”**：DSH 进程一崩，其他方案的机器人就变成死号，只能回
-  服务器手动重启；dsh-lark-bot 的守护进程在 DSH 崩溃后**仍然会在飞书回复你**——告诉你引擎已挂、
-  可进入仅核心安全模式，直接在飞书对话里发控制信号把它重启。**唯一“出故障时用户不会失联”的项目。**
-  *When DSH crashes, this bot still answers in Feishu: enter core-only safe mode and send a
-  control signal to restart it. The only project where users never lose contact.*
-- 👥 **多角色 Agent —— “一个机器人，一整个团队”**：在飞书里用 `/role` 切换或指派 PM / 开发 /
-  文档等角色，每个角色有持久化的人设、模型偏好与规则。
-  *Switch or assign PM / dev / docs personas in chat with `/role` — each with its own
-  persisted persona. One bot, a whole team.*
-- ⚡ **并行多任务 —— “不用排队”**：同一群里可以**同时跑多个任务**，各自会话隔离；其他方案同聊
-  串行，上一个没跑完下一个只能等。
-  *Run multiple tasks in the same chat simultaneously with isolated sessions — no queueing.*
-- 🗂 **会话归档与清理 —— “会话列表不会烂掉”**：`/archive` 归档旧任务、`/retention` 配置自动保留
-  策略；长期使用也不会越积越多。
-  *Archive old tasks and auto-prune with retention policies — your session list stays clean.*
-- 📣 **跨会话主动通知 + @人 —— “活干完了它会来找你”**：Agent 在 A 群跑完任务，可以**主动发消息到
-  B 群或私聊并 @ 你**；而不是“你问它答”。
-  *Agents proactively report to other chats or DMs and @mention you when work finishes.*
-- 🔑 **对话内管理模型和密钥 —— “不用离开飞书”**：`/providers` `/provider` `/key` 直接在聊天里
-  查看、切换供应商、热更新密钥，全程闭环。
-  *View providers, switch vendors and hot-update API keys entirely in chat — no server-side
-  edits.*
+**dsh-lark-bot 把遥控器装进你的飞书**：在私聊、群聊、话题里直接指挥本机 dsh coding agent，流式卡片实时看思考与工具调用；任务完成主动推送到你所在的任何群并 @ 你；即使 dsh 崩溃下线，飞书里依然叫得应——发 `/safemode` 进入仅核心安全模式，直接在聊天里定位问题、重启引擎。**这是唯一“dsh 挂了你不会失联”的桥接方案。**
----
+## 能做什么
-## 快速开始 | Quick Start（普通用户先看这里 | for end users）
+**基础能力**：
-### 1. 安装（唯一路径）| Install (the only path)
+- 私聊、群聊、话题（thread）里指挥本机 dsh coding agent，图片 / 文本文件直接发给 bot 即可；
+- 流式卡片实时展示思考、工具调用与结果，支持交互按钮（停止 / 审批 / 问答卡）；
+- 会话自动归档与保留策略；Git 仓库内为每个会话自动创建隔离 worktree 项目工作区，多项目互不干扰。
-本项目以 **dsh 标准 profile bundle** 交付：一行命令把它装进一个 dsh profile，dsh 启动时以
-标准插件方式加载桥接引擎（`dsh.bundle.patch` 已声明，`dsh plugin add` 可直接安装）。
+**六项全网独有组合**：
-This project ships as a **standard dsh profile bundle**: one command installs it into a dsh
-profile, and dsh loads the bridge engine as a standard plugin on boot (the package declares
-`dsh.bundle.patch`, so `dsh plugin add` works directly).
+- 🆘 **Guardian 安全网守护——“永远叫得应”**：DSH 崩溃后飞书仍会回复你，`/safemode` 进入仅核心安全模式直接重启。
+- 👥 **多角色 Agent——“一个机器人，一整个团队”**：`/role` 切换或指派 PM / 开发 / 文档等角色，每个角色独立人设、模型偏好与规则。
+- ⚡ **并行多任务——“不用排队”**：同一群聊同时跑多个任务、会话隔离；其他方案只能串行排队。
+- 🗂 **会话归档与清理——“会话列表不会烂掉”**：`/archive` 归档旧任务、`/retention` 配置自动保留策略。
+- 📣 **跨会话主动通知 + @人——“活干完了它会来找你”**：A 群跑完任务主动推送到 B 群 / 私聊并 @ 你。
+- 🔑 **对话内管理模型和密钥——“不用离开飞书”**：`/providers` `/provider` `/key` 直接查看、切换供应商、热更新密钥。
-```bash
-# 唯一安装命令（无需先全局安装任何东西）| the only install command (no prior global install)
-npx dsh-lark-bot@latest setup --profile dsh-lark
-```
+## 30 秒上手
-`setup` 会自动完成：发现本机 dsh → 预批准 pnpm 构建策略 → 执行标准的
-`dsh plugin --profile dsh-lark add dsh-lark-bot@<版本>`（版本号由当前包固定，避免 pnpm
-裸名解析到旧版本），并**默认同时安装「安全网守护」**——系统级
-常驻、dsh 全部下线后仍保留飞书救援入口（核心能力之一，见下文「安全网守护」一节）。
-一条命令即完成全部安装。
+**前置条件（先装好本体，再装遥控器）**：
-`setup` automatically: locates your dsh install → pre-approves pnpm's build policy → runs the
-standard `dsh plugin --profile dsh-lark add dsh-lark-bot@<version>` (pinned to the running
-package so pnpm never resolves an outdated bare-name release), and **also installs the safety-net
-guardian by default** — a system-level resident process that keeps the Feishu rescue entrance
-alive even when dsh is fully down (one of the core features; see "Safety-net guardian" below).
-One command installs everything.
+1. **DeepSeek Harness（`dsh`）已安装并配置好 `DEEPSEEK_API_KEY`** —— dsh-lark-bot 是 dsh 的插件，dsh 才是 agent 本体，缺一不可；
+2. **Node.js ≥ 22.19**（见 `package.json` engines）与一个飞书 / Lark 账号。
-### 2. 启动并扫码绑定 | Start and bind with one scan
+**三步上线**：
 ```bash
+# ① 一键安装（无需先全局安装任何东西；自动装进 dsh profile，并默认同时安装「安全网守护」）
+npx dsh-lark-bot@latest setup --profile dsh-lark
+# ② 启动
 dsh --profile dsh-lark
 ```
-首次启动会在终端打印二维码：用飞书 / Lark App 扫码创建或选择 PersonalAgent 应用，绑定后
-dsh-lark-bot 的桥接引擎即在 dsh 进程内运行（飞书通道、会话/工作区、卡片、通知回调），
-私聊直接发消息，群聊 / 话题里 `@bot`。常驻与守护由 dsh 自己负责。
-On first boot the terminal prints a QR code: scan it with the Feishu / Lark app to create or
-choose a PersonalAgent app. After binding, the bridge engine runs **inside the dsh process**
-(Feishu channel, sessions/workspaces, cards, notify callback); message it directly in private
-chat, or use `@bot` in groups/topics. dsh owns the daemon lifecycle.
+③ 首次启动终端打印二维码 → 飞书 / Lark App 扫码创建或选择 PersonalAgent 应用 → 绑定后私聊直接发消息，群聊 / 话题里 `@bot`。
-已有 PersonalAgent 应用时可在 profile 环境变量中直接提供凭据跳过扫码（见「配置」）：
-With an existing PersonalAgent app, provide credentials via profile env to skip the QR step
-(see Configuration):
+`setup` 会自动完成：定位本机 dsh → 预批准 pnpm 构建策略（protobufjs）→ 执行标准
+`dsh plugin --profile dsh-lark add dsh-lark-bot@<版本>`（版本号由当前包固定）→ 默认安装「安全网守护」系统服务。
+一条命令即完成全部安装。
-```bash
-DSH_LARK_APP_ID=cli_xxx DSH_LARK_APP_SECRET=<secret> DSH_LARK_TENANT=feishu \
-  dsh --profile dsh-lark
-```
+> **无需公网 IP / 域名 / 服务器 / 内网穿透**（飞书 WebSocket 出站长连接），Linux / macOS / Windows 通用。
+> 已有 PersonalAgent 应用时可跳过扫码（见「配置」）：`DSH_LARK_APP_ID=cli_xxx DSH_LARK_APP_SECRET=<secret> DSH_LARK_TENANT=feishu dsh --profile dsh-lark`
+> 升级同样一条命令：`npx dsh-lark-bot@latest upgrade --profile dsh-lark --yes`
-> 卸载：`dsh plugin --profile dsh-lark remove dsh-lark-bot`。
-> Uninstall: `dsh plugin --profile dsh-lark remove dsh-lark-bot`.
+## 完整使用方式
-### 3. 基本使用 | Basic usage
+### 常用命令
 在飞书里向 bot 发送普通消息即可开始工作，常用命令：
-Just send a normal message to the bot in Feishu to get started. Common commands:
-| 命令 Command | 作用 Description |
+| 命令 | 作用 |
 | --- | --- |
-| `/new` `/reset` | 开始新会话<br>Start a new session |
-| `/newg <群名>` | 自动新建群聊（拉你入群）并开新会话，当前会话保留<br>Auto-create a group chat (with you invited) and start a fresh session there; the current session is untouched |
-| `/cd <path>` | 切换工作目录并重置会话<br>Change working directory and reset the session |
-| `/ws list` | 查看命名工作空间<br>List named workspaces |
-| `/ws save <name>` | 保存当前工作空间<br>Save the current workspace |
-| `/ws use <name>` | 切换到命名工作空间<br>Switch to a named workspace |
-| `/ws remove <name>` | 删除命名工作空间<br>Remove a named workspace |
-| `/status` | 查看当前状态<br>Show current status |
-| `/resume` | 查看当前会话最近上下文<br>Show the session's recent context |
-| `/stop` | 终止当前任务<br>Stop the current task |
-| `/timeout [N\|off\|default]` | 查看或设置当前会话运行超时<br>View or set the current session run timeout |
-| `/concurrency [N\|default]` | 查看或设置当前 scope 并行任务数（默认 2）<br>View or set the concurrent-run limit for this scope (default 2) |
-| `/role list`、`/role show <id>` | 查看角色列表 / 详情<br>List roles / show a role |
-| `/role set <id>`、`/role clear` | 为当前 scope 绑定 / 解除角色<br>Bind / unbind a role for this scope |
-| `/role save <id> <name> [--persona 文案] [--model <id>] [--tools <csv>] [--rules 文案]` | 创建 / 更新角色（管理员）<br>Create / update a role (admin) |
-| `/role remove <id>` | 删除角色（管理员）<br>Remove a role (admin) |
-| `/notify <scope\|chatId> <text>` | 跨会话发送通知（管理员）<br>Push a cross-session notification (admin) |
-| `/notify list` | 查看 bridge 已注册的 scope<br>List scopes known to the bridge |
-| `/retention [N\|default]` | 查看或设置保留消息条数（超出自动归档）<br>View or set the live message retention window (overflow is archived) |
-| `/archive [note]`、`/archive list [N]`、`/archive clean` | 手动归档 / 查看 / 清理会话记录<br>Archive / list / clean session transcripts |
-| `/density [compact\|standard\|detailed]` | 查看或设置卡片密度<br>View or set card density |
-| `/model` | 查看当前模型、dsh 默认模型与可用模型列表<br>View current model, dsh default model and available models |
-| `/model use <id>` | 热切换当前会话模型（下一轮生效，无需重启）<br>Hot-switch the current session model (effective next message, no restart) |
-| `/model default <id>` | 写入 dsh 默认模型 `agent-default-model`（管理员）<br>Write the dsh default model `agent-default-model` (admin) |
-| `/model add\|remove <provider> <modelId>` | 添加 / 删除 provider 的模型（管理员）<br>Add / remove a provider model (admin) |
-| `/providers` | 查看 dsh 已配置 providers、模型与凭据状态<br>View configured dsh providers, models and credential status |
-| `/provider add\|update\|remove <id>` | 管理 provider（管理员；deepseek-official 与自定义 pi-ai）<br>Manage providers (admin; deepseek-official and custom pi-ai) |
-| `/key set\|remove\|list <引用名>` | 管理 dsh 凭据（set / remove 需管理员）<br>Manage dsh credentials (set / remove require admin) |
-| `/ask <问题>` | 发送问答卡，回答写入会话上下文<br>Send a Q&A card; the answer is written back to session context |
-| `/invite user\|admin\|group <id>`、`/invite list`、`/invite remove user\|group <id>` | 管理访问白名单<br>Manage the access allowlist |
-| `/help` | 查看帮助<br>Show help |
+| `/new` `/reset` | 开始新会话|
+| `/newg <群名>` | 自动新建群聊（拉你入群）并开新会话，当前会话保留|
+| `/cd <path>` | 切换工作目录并重置会话|
+| `/ws list` | 查看命名工作空间|
+| `/ws save <name>` | 保存当前工作空间|
+| `/ws use <name>` | 切换到命名工作空间|
+| `/ws remove <name>` | 删除命名工作空间|
+| `/status` | 查看当前状态|
+| `/resume` | 查看当前会话最近上下文|
+| `/stop` | 终止当前任务|
+| `/timeout [N\|off\|default]` | 查看或设置当前会话运行超时|
+| `/concurrency [N\|default]` | 查看或设置当前 scope 并行任务数（默认 2）|
+| `/role list`、`/role show <id>` | 查看角色列表 / 详情|
+| `/role set <id>`、`/role clear` | 为当前 scope 绑定 / 解除角色|
+| `/role save <id> <name> [--persona 文案] [--model <id>] [--tools <csv>] [--rules 文案]` | 创建 / 更新角色（管理员）|
+| `/role remove <id>` | 删除角色（管理员）|
+| `/notify <scope\|chatId> <text>` | 跨会话发送通知（管理员）|
+| `/notify list` | 查看 bridge 已注册的 scope|
+| `/retention [N\|default]` | 查看或设置保留消息条数（超出自动归档）|
+| `/archive [note]`、`/archive list [N]`、`/archive clean` | 手动归档 / 查看 / 清理会话记录|
+| `/density [compact\|standard\|detailed]` | 查看或设置卡片密度|
+| `/model` | 查看当前模型、dsh 默认模型与可用模型列表|
+| `/model use <id>` | 热切换当前会话模型（下一轮生效，无需重启）|
+| `/model default <id>` | 写入 dsh 默认模型 `agent-default-model`（管理员）|
+| `/model add\|remove <provider> <modelId>` | 添加 / 删除 provider 的模型（管理员）|
+| `/providers` | 查看 dsh 已配置 providers、模型与凭据状态|
+| `/provider add\|update\|remove <id>` | 管理 provider（管理员；deepseek-official 与自定义 pi-ai）|
+| `/key set\|remove\|list <引用名>` | 管理 dsh 凭据（set / remove 需管理员）|
+| `/ask <问题>` | 发送问答卡，回答写入会话上下文|
+| `/invite user\|admin\|group <id>`、`/invite list`、`/invite remove user\|group <id>` | 管理访问白名单|
+| `/help` | 查看帮助|
 飞书消息中的图片会下载到本地 media 目录并传给 dsh；文本类文件会读取内容并注入任务上下文。
-Images in Feishu messages are downloaded to the local media directory and passed to dsh; text files are read and their content is injected into the task context.
 **`/newg <群名>`**：通过飞书 API 自动新建一个私密群、把发送者拉入群，并回复群链接——在新群里发消息即为新 scope / 新会话，当前会话不受影响。需要应用具备 `im:chat` 与 `im:chat.members:write_only` 权限（在开发者后台「权限管理」申请）。
-**`/newg <group name>`**: auto-creates a private group via the Feishu API, invites the sender, and replies with a group link — chatting in the new group starts a fresh scope/session while the current session is untouched. Requires the `im:chat` and `im:chat.members:write_only` scopes (apply in the developer console).
 同一 scope（私聊 / 群聊 / 话题）默认允许 **2 个任务并行**（`DSH_LARK_SCOPE_CONCURRENCY` 或
 `/concurrency` 调整）：连续发来的多条消息会以独立 run 并行推进，每个 run 使用独立的 dsh
 session 与独立 runId，`/status` 展示全部运行中的 run，`/stop` 一次性终止全部任务。
-Each scope (DM / group / topic) runs up to **2 tasks in parallel** by default (adjust with
-`DSH_LARK_SCOPE_CONCURRENCY` or `/concurrency`): successive messages become independent runs,
-each with its own dsh session and run id. `/status` lists every active run and `/stop` interrupts
-them all.
 **多角色 Agent**：管理员用 `/role save <id> <name> --persona <文案> [--model <id>] [--tools
 <csv>] [--rules <文案>]` 定义 PM / 开发 / 文档等角色（persona、模型偏好、工具指引、角色规则），
 `/role set <id>` 把角色绑定到当前 scope：下一轮起该 scope 的每个 run 都携带角色 persona 与
 规则，并优先使用角色模型（角色模型 < 每会话 `/model use`）。角色定义持久化在
 `~/.dsh-lark/profiles/<profile>/roles.json`。
-**Multi-role agents**: admins define roles (PM / dev / docs / …) with `/role save <id> <name>
---persona <text> [--model <id>] [--tools <csv>] [--rules <text>]` — persona, model preference,
-tool guidance and role rules — then bind one to the current scope with `/role set <id>`. Every
-run in that scope carries the role instructions, and the role model wins below the per-session
-`/model use` override. Role definitions persist in
-`~/.dsh-lark/profiles/<profile>/roles.json`.
 **出站 @ 提及与跨会话通知**：bridge 出站契约支持 `mentions`（@ 提及）与跨 chat/thread 发送；
 `/notify <scope|chatId> <text>` 可向其他会话推送汇报（管理员）。agent 侧还内置 `lark_notify`
 dsh 工具（SDK / ACP 两种 runtime 均可装配）：agent 完成任务后可主动向其他群 / 话题发消息并
@@ -233,20 +149,7 @@ dsh 工具（SDK / ACP 两种 runtime 均可装配）：agent 完成任务后可
 你回答后任务自动继续——无需额外命令。问答卡等待期间任务不会被运行超时打断。
 （与 `/ask` 的“你主动发结构化问题”方向相反：这是 agent 主动来问你。）
-**Outbound mentions & cross-session notify**: the outbound contract supports `mentions` and
-cross-chat/thread sends; `/notify <scope|chatId> <text>` pushes a report to another session
-(admin). The agent also gets a built-in `lark_notify` dsh tool (wired into both SDK and ACP
-runtime profiles): after a task finishes it can push messages to other groups/topics and @mention
-members. The bridge listens on 127.0.0.1 with a random per-boot token — nothing is exposed to the
-public network.
-**Mid-task questions (question cards)**: when the agent needs a decision, confirmation, or
-missing information, it proactively sends a **question card** to the current chat via the
-`lark_ask_user` tool (single choice / multi choice / free text) and resumes automatically once
-you answer — no extra command needed. The run-timeout watchdog pauses while a card is waiting.
-(This is the opposite direction of `/ask`, which is you asking the agent.)
-**安全网守护（Safe-mode guardian）**：默认随 `setup` 一起安装的、独立于 dsh 进程、系统级常驻的
+**安全网守护**：默认随 `setup` 一起安装的、独立于 dsh 进程、系统级常驻的
 最小守护进程（Linux systemd user unit / macOS LaunchAgent / Windows 启动项）。dsh 正常运行时守护保持静默；
 一旦 dsh 进程下线或无法 boot（例如某个第三方插件破坏了整个 profile 组合），守护自动接管飞书
 通道，用户无需接触命令行即可发送控制信号自救：
@@ -272,45 +175,11 @@ dsh-lark-bot guardian install --dsh-profile dsh-lark
 ```
 不需要守护时，安装时加 `--no-guardian` 跳过；单独卸载用 `dsh-lark-bot guardian uninstall`。
-**Safety-net guardian**: a minimal system-level resident process installed **by default with
-`setup`**, independent of the dsh process. While dsh runs, the guardian stays silent; once dsh goes down or
-fails to boot (e.g. a third-party plugin breaks the whole profile composition), the guardian
-takes over the Feishu channel so you can self-heal without touching the command line:
-- `/safemode`: enter **core-only safe mode** — the guardian provisions
-  `~/.dsh/profiles/<profile>-safe` with only the two official core bundles (`dsh-base` +
-  `dsh-headless`, **no third-party plugins**) and proxies a restricted conversation to that core
-  dsh so you can locate / fix / disable the offending plugin. Safe mode prefers the official
-  **SDK streaming engine** (real-time reasoning / tool calls / web search / typewriter text on the
-  same streaming card as normal mode) and falls back to headless with a live activity card
-  ("thinking / elapsed Ns / no response Ns") when the SDK runtime cannot be provisioned;
-- `/safemode plugins`: list the plugins installed into the broken profile;
-- `/safemode status`: show guardian / dsh / safe-mode state;
-- `/safemode stop`: interrupt the currently running safe-mode task (or use the ⏹ button on the card);
-- `/safemode exit`: leave safe mode — the guardian relaunches the full profile and hands the
-  Feishu channel back;
-Safe-mode tasks are bounded by an **idle timeout**
-(`DSH_LARK_GUARDIAN_SAFE_TIMEOUT_MS`, default 10 minutes: a task is stopped only after it has
-been silent for the whole window, so active streaming work is never cut short); timeouts and failures always surface a
-clear terminal state on the card instead of hanging silently. No command line is needed for the
-whole rescue flow; once dsh is back, the guardian releases the channel automatically. Install:
-```bash
-# Installed by default with setup (no extra flag); can also be installed / refreshed later:
-dsh-lark-bot guardian install --dsh-profile dsh-lark
-```
-Pass `--no-guardian` to setup to skip it; remove it later with `dsh-lark-bot guardian uninstall`.
-### 模型 / Provider / 凭据管理 | Models / Providers / Credentials
+### 模型 / Provider / 凭据管理
 模型与 provider 的配置以 dsh 官方方式持久化（与 dsh Web **Settings → Models** 页面完全相同的
 存储协议），改动在下一个请求生效，无需重启 bot：
-Model and provider configuration is persisted the official dsh way (the exact storage protocol
-used by the dsh Web **Settings → Models** page); changes take effect on the next request without
-restarting the bot:
 - `/model use <id>`：按会话热切换模型，下一轮消息即用新模型。
 - `/model default <id>`：写入 dsh 的 `agent-default-model`，作为新会话的默认模型。
 - `/providers`：展示 dsh 已配置的 provider、模型与凭据状态（DeepSeek 官方 + 自定义 pi-ai）。
@@ -320,30 +189,15 @@ restarting the bot:
 - `/key set|remove|list`：读写 `~/.dsh/.credentials.yaml`（0600）。settings 只保存 `apiKeyEnv`
   引用，字面密钥不进入 settings 或聊天记录。
-- `/model use <id>`: hot-switch the model for this session; the next message uses it.
-- `/model default <id>`: write the dsh `agent-default-model` as the default for new sessions.
-- `/providers`: show configured providers, models and credential status (official DeepSeek + custom pi-ai).
-- `/provider add|update|remove`: manage custom providers (`llm-pi-ai`) or `deepseek-official`;
-  a custom provider needs `--api` (`openai-completions` / `openai-responses` / `anthropic-messages`),
-  `--base-url` and at least one `--model`, matching the official schema.
-- `/key set|remove|list`: read / write `~/.dsh/.credentials.yaml` (0600). Settings keep only
-  `apiKeyEnv` references; literal keys never enter settings or chat history.
 安全提醒：在飞书会话里输入密钥会对该会话的可见成员暴露密钥，建议仅在私聊中使用，或优先用
 `--api-key-env` 引用已配置的环境变量 / dsh Web 页面录入。bot 不会在任何回复中回显密钥值。
-Security note: typing a key in a Feishu conversation exposes it to everyone who can see that
-chat; prefer private chats, `--api-key-env` references to existing environment variables, or the
-dsh Web UI. The bot never echoes key values in any reply.
-## 安装与卸载 | Install & Uninstall
+## 安装与卸载
-### 安装 | Install
+### 安装
 唯一安装方式（标准 dsh profile bundle）：
-The only install path (a standard dsh profile bundle):
 ```bash
 npx dsh-lark-bot@latest setup --profile dsh-lark
 ```
@@ -352,12 +206,7 @@ npx dsh-lark-bot@latest setup --profile dsh-lark
 `dsh plugin --profile dsh-lark add dsh-lark-bot`，并**默认同时安装「安全网守护」**
 （见「安全网守护」一节；不需要时加 `--no-guardian` 跳过）。已安装时重复执行即升级到最新版。
-`setup` locates your dsh, pre-approves pnpm's build policy (protobufjs) and runs the standard
-`dsh plugin --profile dsh-lark add dsh-lark-bot`. It **also installs the safety-net guardian by
-default** (see "Safety-net guardian" above; pass `--no-guardian` to skip). Re-running it upgrades
-to the latest version.
-### 升级 | Upgrade
+### 升级
 **推荐：一行命令彻底升级（v0.12.0+ 新增，issue #10）**
@@ -386,92 +235,80 @@ npx dsh-lark-bot@latest upgrade --profile dsh-lark --yes
 - CLI 工具（可选）：`npm i -g dsh-lark-bot@latest`；使用 `npx` 时无需全局安装。
 - 升级后重启 profile（未用 `--restart` 时）：`dsh --profile dsh-lark`。
-- **Recommended: one-command full upgrade (new in v0.12.0, issue #10)**
+### 禁用
+保持插件加载但停止桥接引擎：启动 profile 前导出 `DSH_LARK_DISABLED=1`。彻底移除见下节。
+### 卸载
 ```bash
-npx dsh-lark-bot@latest upgrade --profile dsh-lark --yes
+dsh plugin --profile dsh-lark remove dsh-lark-bot
 ```
-`upgrade` detects the installed / running / npm-latest versions, upgrades the **package**
-(`dsh plugin add <name>@<latest>`), **idempotently reinstalls and restarts the guardian
-service**, then runs `doctor` verification. Running instances are handled safely:
+卸载后 profile 不再加载本插件。本地状态（配置 / 会话 / 归档 / 角色）保留在 `~/.dsh-lark`；
+如需清除，先备份再删除该目录。
-- By default the running dsh profile is never interrupted — you only get the restart command
-  (config / sessions / credentials are untouched);
-- `--restart`: also restarts the guardian service and (managed/detached) dsh profile processes;
-- `--check`: report versions and running state only, no changes;
-- `--rollback`: reinstall the version recorded before the last upgrade
-  (`~/.dsh-lark/upgrade-state.json`);
-- `--force`: reinstall the running version when npm is unreachable (offline);
-- `--no-guardian`: skip the guardian upgrade.
+更详细的安装、状态目录、日志和排障说明见 [`docs/QUICK_START.md`](docs/QUICK_START.md)。
-Pass `--yes` to skip the interactive confirmation (non-interactive runs fail closed without it).
-Alternatives:
+---
-- Plugin: re-run `setup` (or `dsh plugin --profile <name> add dsh-lark-bot`) to pull the latest
-  npm release.
-- Safety-net guardian: installed / upgraded together with `upgrade` / `setup` (idempotent), or
-  standalone via `dsh-lark-bot guardian install`.
-- CLI tool (optional): `npm i -g dsh-lark-bot@latest`; not needed when using `npx`.
-- Restart the profile after upgrading (when not using `--restart`): `dsh --profile dsh-lark`.
+## FAQ（典型用例与常见问题）
-### 禁用 | Disable
+### 典型用例
-保持插件加载但停止桥接引擎：启动 profile 前导出 `DSH_LARK_DISABLED=1`。彻底移除见下节。
+**Q: 出门在外，想用手机指挥本机的 DeepSeek Harness？**
-Keep the plugin loaded but stop the bridge engine: export `DSH_LARK_DISABLED=1` before booting
-the profile. For full removal see the next subsection.
+**A:** 可以。安装并扫码绑定后，用飞书手机 App 给机器人发消息即可指挥本机 dsh coding agent 读代码、跑命令、完成任务；任务完成还能跨会话主动推送并 @ 你。安装只需：`npx dsh-lark-bot@latest setup --profile dsh-lark` → `dsh --profile dsh-lark` → 飞书扫码 → 开聊。
-### 卸载 | Uninstall
+**Q: 多个项目 / 多人协作，怎么隔离与分工？**
-```bash
-dsh plugin --profile dsh-lark remove dsh-lark-bot
-```
+**A:** 每个会话自动落在独立的 git worktree（`~/.dsh-lark/profiles/<profile>/worktrees/<scope>/`），项目级 `AGENTS.md` 规则自动注入，多项目互不干扰；管理员用 `/role` 定义 PM / 开发 / 文档等角色并绑定到群，用 `/invite` 管理访问白名单；同一群内默认 2 个任务并行（`/concurrency` 调整），`/archive` + `/retention` 控制会话归档与保留。
-卸载后 profile 不再加载本插件。本地状态（配置 / 会话 / 归档 / 角色）保留在 `~/.dsh-lark`；
-如需清除，先备份再删除该目录。
+**Q: dsh 崩溃 / 掉线后，飞书机器人还能用吗？**
-Removal unloads the plugin from the profile. Local state (config / sessions / archives / roles)
-stays in `~/.dsh-lark`; back it up before deleting it.
+**A:** 能。`setup` 默认安装独立于 dsh 进程的「安全网守护」（systemd / LaunchAgent / Windows 启动项）。dsh 崩溃或无法启动时，守护自动接管飞书通道并先尝试自动重启完整 profile；仍失败时你直接发 `/safemode` 进入仅核心安全模式（官方核心 bundle，不加载任何第三方插件），在聊天里定位 / 修复问题，`/safemode exit` 重启完整 profile 并交还通道。全程不需要命令行。
-更详细的安装、状态目录、日志和排障说明见 [`docs/QUICK_START.md`](docs/QUICK_START.md)。
+### 常见问题
+**Q: DeepSeek Harness 怎么接入飞书？**
+**A:** 安装 Node.js ≥ 22 与 DeepSeek Harness（已配置 `DEEPSEEK_API_KEY`），执行 `npx dsh-lark-bot@latest setup --profile dsh-lark`，再 `dsh --profile dsh-lark` 启动并用飞书 App 扫描终端二维码绑定 PersonalAgent 应用。私聊直接发消息，群聊 / 话题里 `@bot`。
+**Q: 需要公网 IP、域名或服务器吗？**
+**A:** 不需要。飞书通道使用 WebSocket 长连接（出站连接），本机在 NAT 后面也能用，免公网服务器、免域名、免内网穿透。
+**Q: dsh-lark-bot 和其他 DeepSeek Harness 飞书插件（如 harness-lark）有什么区别？**
+**A:** 功能组合最全：安全网守护（dsh 崩溃后飞书仍叫得应）、多角色 Agent、并行多任务、会话归档、跨会话主动通知、对话内模型 / 密钥管理六项合为一体；安装上是标准 dsh profile bundle，`npx dsh-lark-bot@latest setup` 一条命令装进 dsh profile，无需独立 Docker / 后台服务。
+**Q: 项目从哪下载？会不会有假冒版本？**
-See [`docs/QUICK_START.md`](docs/QUICK_START.md) for installation details, state directories,
-logs and troubleshooting.
+**A:** 唯一官方仓库是 [github.com/PlutoKeating/dsh-lark-bot](https://github.com/PlutoKeating/dsh-lark-bot)，唯一官方 npm 包是 `dsh-lark-bot` / `dsh-feishu-bot`（维护者 `plutokeating`）。本项目从不提供 .exe 或“下载即运行”的安装包；任何以项目名义分发 exe 的仓库或页面都是假冒来源，请勿运行（详见文末「假冒仓库警告」）。
 ---
-## 关键词 | Keywords
+## 关键词
-`dsh` · `deepseek` · `deepseek harness` · `feishu` · `lark` · `bridge` · `bot`
+`dsh` · `deepseek` · `deepseek harness` · `feishu` · `lark` · `bridge` · `bot` ·
+`chatbot` · `messaging` · `qrcode` · `typescript` · `feishu-bot` · `lark-bot` ·
+`dsh-plugin` · `deepseek-harness` · `im-bridge` · `ai-agent` · `workspace` · `self-healing`
-## 这是什么 | What it is
+## 这是什么
 **dsh-lark-bot** 是一个轻量桥接工具，把本机的 DeepSeek Harness（`dsh`）接入飞书 / Lark，复刻当年 OpenCode Telegram Bot / MiMoCode Telegram Bot 的体验——在 IM 里与 coding agent 对话、收流式卡片、审阅 diff，并在此基础上叠加**完整的项目工作区管理**。
-**dsh-lark-bot** is a lightweight bridge that connects your local DeepSeek Harness (`dsh`) into Feishu / Lark, recreating the beloved OpenCode / MiMoCode Telegram-bot experience — chat with your coding agent, receive streaming cards, review diffs — and adds **full project workspace management** on top.
-**适合谁 / Who it is for**：在飞书 / Lark（私聊、群聊、话题）里指挥本机 dsh coding agent 的
+**适合谁**：在飞书 / Lark（私聊、群聊、话题）里指挥本机 dsh coding agent 的
 开发者与团队，尤其是需要多项目隔离、角色分工、并行任务与会话归档的协作场景。
-Developers and teams who drive a local dsh coding agent from Feishu / Lark (DMs, groups,
-topics) — especially those needing multi-project isolation, role-based collaboration, parallel
-tasks and session archival.
-## 目标 | Goals
+## 目标
 - **一条命令安装部署**：`npx dsh-lark-bot@latest setup --profile dsh-lark` 装进 dsh profile，
   随后 `dsh --profile dsh-lark` 启动并扫码，桥接引擎作为标准插件在 dsh 进程内运行。
 - **飞书原生体验**：流式卡片、交互按钮、图片 / 文件，全程双语（文档评论为规划中能力）。
 - **完整工作区管理**：多项目隔离、git worktree、项目级规则注入、上下文持久化。
-- **One-command install & deploy**: `npx dsh-lark-bot@latest setup --profile dsh-lark`, then
-  `dsh --profile dsh-lark` and scan once — the bridge engine runs as a standard plugin inside
-  the dsh process.
-- **Native Feishu experience**: streaming cards, interactive buttons, images / files, doc comments.
-- **Full workspace management**: multi-project isolation, git worktrees, per-project rules, persistent context.
-## 兼容性 | Compatibility
+## 兼容性
 - **DeepSeek Harness（`dsh`）**：已验证 **dsh 0.1.0-rc.6**（最后验证 2026-08-15：SDK JSON-RPC / ACP runtime 握手 +
   真实任务流式验证），通过官方 `@deepseek-ai/dsh-sdk-client` / `@deepseek-ai/dsh-acp` 接入；
@@ -485,23 +322,7 @@ tasks and session archival.
   `/api/events.mux`，网页端成为唯一写者，从根上消除多写者会话损坏）。首次启动自动在
   `~/.dsh/profiles/dsh-lark-sdk`（或 `dsh-lark-acp`）创建 runtime profile。
-- **DeepSeek Harness (`dsh`)**: verified against **dsh 0.1.0-rc.6** (last verified 2026-08-15: SDK JSON-RPC / ACP
-  runtime handshake + real streaming task verification), connected through the official
-  `@deepseek-ai/dsh-sdk-client` / `@deepseek-ai/dsh-acp`; see
-  [`docs/COMPATIBILITY.md`](docs/COMPATIBILITY.md) for pinned versions, the upgrade policy and
-  automated probing, and [`docs/adapter-notes.md`](docs/adapter-notes.md) for adapter details.
-- **Runtime**: Node.js ≥ 22.19 (see `engines` in `package.json`).
-- **Platform**: Linux / macOS / Windows (Feishu outbound WebSocket long connection; no public
-  server, domain or tunneling required).
-- The default adapter is the official **`@deepseek-ai/dsh-sdk-client`** (SDK JSON-RPC runtime with
-  native session continuation and token-level streaming events); `DSH_LARK_ADAPTER=acp` switches
-  to the official **ACP server** (approval cards); `headless` keeps the legacy subprocess
-  fallback; `DSH_LARK_ADAPTER=web` drives the **local dsh web agent** (`session.prompt` +
-  `/api/events.mux` — the web agent becomes the single writer, eliminating multi-writer
-  session-log corruption at the root). On first start the bot creates the runtime profile at
-  `~/.dsh/profiles/dsh-lark-sdk` (or `dsh-lark-acp`).
-## 已知限制 | Known limitations
+## 已知限制
 - ACP 模式会话每次全新（上游限制，无续跑）；SDK 协议暂无 mid-turn cancel，`/stop` 会关闭
   对应 runtime 并自动重建。
@@ -514,19 +335,7 @@ tasks and session archival.
   `ERR_PNPM_IGNORED_BUILDS`，按官方指引在 profile 的 `pnpm-workspace.yaml` 加
   `allowBuilds: { protobufjs: true }` 后重试。
-- ACP sessions are always fresh (an upstream limit); the SDK protocol has no mid-turn cancel,
-  so `/stop` closes and recreates the runtime.
-- The engine runs in-process as a dsh plugin; agent execution uses the official dsh SDK runtime
-  subprocess — a deliberate nested-runtime design for per-workspace runtime pools and parallel
-  runs. The one process-level exception is the optional safety-net guardian — a minimal
-  resident process independent of dsh / Cordis that only takes over the Feishu channel after
-  dsh goes down and stays silent otherwise.
-- Feishu doc comments and rich-text replies are planned, not yet implemented.
-- pnpm ≥ 10 build policy is handled by `setup`; when installing manually and
-  `ERR_PNPM_IGNORED_BUILDS` appears, add `allowBuilds: { protobufjs: true }` to the profile's
-  `pnpm-workspace.yaml` and retry.
-## 配置 | Configuration
+## 配置
 - 本地配置：`~/.dsh-lark/config.json`
 - 状态根目录可用 `DSH_LARK_HOME` 覆盖
@@ -535,81 +344,58 @@ tasks and session archival.
 - 敏感项：`DSH_LARK_APP_SECRET`、`DEEPSEEK_API_KEY` 等凭据只保存在本机配置 / 环境中，日志与
   卡片自动脱敏，仓库只提交 `.env.example` 模板。
-- Local config: `~/.dsh-lark/config.json`
-- The state root can be overridden with `DSH_LARK_HOME`
-- Environment variables use the `DSH_LARK_*` prefix
-- Template: [`.env.example`](.env.example)
-- Sensitive values: credentials (`DSH_LARK_APP_SECRET`, `DEEPSEEK_API_KEY`, …) stay in local
-  config/env only; logs and cards are redacted; only `.env.example` is committed.
 会话运行在 Git 仓库中时，会自动在 `~/.dsh-lark/profiles/<profile>/worktrees/<scope>/` 创建隔离 worktree，并复制项目级 `AGENTS.md`。
-When the session runs inside a Git repository, an isolated worktree is created at
-`~/.dsh-lark/profiles/<profile>/worktrees/<scope>/` and a project-level `AGENTS.md` is copied in.
 每个飞书 scope 默认保存最近 40 条对话消息（可用 `/retention` 或 `DSH_LARK_RETENTION_MSGS`
 调整）；超出保留窗口的消息自动归档到 `~/.dsh-lark/profiles/<profile>/archives/`（Markdown +
 JSONL，目录本身是 Git 仓库，每次归档独立 commit），支持 `/archive` 手动归档与保留策略清理。
 SDK 模式下 dsh 原生 session 续跑，headless 模式则把历史注入下一次 prompt 实现近似记忆。
-Each Feishu scope keeps the last 40 conversation messages by default (adjustable with
-`/retention` or `DSH_LARK_RETENTION_MSGS`); messages beyond the retention window are archived to
-`~/.dsh-lark/profiles/<profile>/archives/` (Markdown + JSONL inside a Git repository, one commit
-per archive), and `/archive` exports the full session on demand. The SDK mode continues the native
-dsh session, while headless mode approximates memory by injecting history into the next prompt.
 当前核心环境变量：
-Core environment variables:
-| 变量 Variable | 默认值 Default | 说明 Description |
+| 变量 | 默认值 | 说明 |
 | :--- | :--- | :--- |
-| `DSH_LARK_HOME` | `~/.dsh-lark` | 本地状态根目录<br>Local state root directory |
-| `DSH_LARK_TENANT` | `feishu` | `feishu` 或 `lark`<br>`feishu` or `lark` |
-| `DSH_LARK_WORKSPACE` | 未设置 | 新会话默认工作目录<br>Default working directory for new sessions |
-| `DSH_LARK_DSH_COMMAND` | `自动发现` | dsh 启动命令；通常无需设置<br>dsh launch command; usually not needed |
-| `DSH_LARK_DSH_ARGS` | `自动发现` | dsh 启动参数，逗号分隔；通常无需设置<br>dsh launch args, comma-separated; usually not needed |
-| `DSH_LARK_ADAPTER` | `sdk` | `sdk`（默认）/ `acp`（审批）/ `headless`（legacy）/ `web`（本地 dsh web agent，单写者）<br>`sdk` (default) / `acp` (approval) / `headless` (legacy) / `web` (local dsh web agent, single writer) |
-| `DSH_LARK_PROVIDER` | `deepseek-official` | 模型 provider<br>Model provider |
-| `DSH_LARK_MODEL` | `deepseek-v4-flash` | 默认模型<br>Default model |
-| `DSH_LARK_MAX_TOKENS` | 未设置 | SDK agent 每请求输出 token 上限<br>Per-request output token cap for SDK agents |
-| `DSH_LARK_WEB_URL` | `http://127.0.0.1:3080` | `web` 适配器：本地 dsh web agent 的 base URL<br>`web` adapter: base URL of the local dsh web agent |
-| `DSH_LARK_WEB_PUSH` | `true` | `web` 适配器：网页端回合完成时推送到飞书并自动切换会话映射（`0` 关闭）<br>`web` adapter: push web-GUI turn completions to Feishu and auto-switch the chat mapping (`0` disables) |
-| `DSH_LARK_ACCESS_DEFAULT_DENY` | `false` | 无白名单时拒绝私聊<br>Reject private chats when no allowlist is configured |
-| `DSH_LARK_EVENT_FRESHNESS_MS` | `600000` | 过期消息拒绝窗口（0 关闭）<br>Stale-message rejection window (0 disables) |
-| `DSH_LARK_RUN_TIMEOUT_MS` | `300000` | 单次运行空闲超时：持续无活动事件才终止（活跃任务不会被误杀）<br>Idle timeout for a single run: stops only after the run has been silent for this long |
-| `DSH_LARK_STOP_GRACE_MS` | `5000` | SIGTERM 后等待优雅退出再 SIGKILL 的宽限期<br>Grace period after SIGTERM before SIGKILL |
-| `DSH_LARK_SCOPE_CONCURRENCY` | `2` | 每个 scope 的并行任务数（1=严格串行）<br>Concurrent runs per scope (1 = strictly serial) |
-| `DSH_LARK_RETENTION_MSGS` | `40` | 每个 scope 保留的消息条数（0=全部保留）<br>Messages kept per scope (0 keeps everything) |
-| `DSH_LARK_ARCHIVE_MAX` | `50` | 每个 scope 最多保留的归档数（0=不清理）<br>Max archives kept per scope (0 disables pruning) |
-| `DSH_LARK_ARCHIVE_MAX_AGE_DAYS` | `90` | 归档最大保留天数（0=不清理）<br>Max archive age in days (0 disables pruning) |
-| `DSH_LARK_HEARTBEAT_MS` | `5000` | 桥接引擎心跳写入间隔（守护存活信号）<br>Bridge heartbeat write interval (guardian liveness signal) |
-| `DSH_LARK_GUARDIAN_DISABLED` | `false` | `1` 时安全网守护进程保持停止<br>`1` keeps the safety-net guardian stopped |
-| `DSH_LARK_GUARDIAN_PROFILE` | `dsh-lark` | 守护监视 / 重启的 dsh profile（首次安装时写入状态）<br>dsh profile the guardian watches / relaunches (persisted on install) |
-| `DSH_LARK_GUARDIAN_BRIDGE_PROFILE` | `default` | 提供飞书凭据与白名单的桥接状态 profile<br>Bridge state profile providing Feishu credentials / allowlist |
-| `DSH_LARK_GUARDIAN_POLL_MS` | `2000` | 守护看门狗轮询间隔<br>Guardian watchdog poll interval |
-| `DSH_LARK_GUARDIAN_STALE_MS` | `15000` | 心跳超时阈值，超过且无 dsh 进程则接管飞书通道<br>Heartbeat staleness threshold before channel takeover |
-| `DSH_LARK_GUARDIAN_ENGINE_DEAD_MS` | `120000` | dsh 进程存活但心跳持续超时该时长，判定桥接引擎已死并接管<br>Live dsh process with heartbeat stale this long is treated as engine-dead (takeover) |
-| `DSH_LARK_GUARDIAN_SAFE_ADAPTER` | `auto` | 安全模式引擎：`auto` 优先 SDK 流式、失败回退 headless；`sdk` 强制 SDK；`headless` 跳过预置<br>Safe-mode engine: `auto` tries the SDK streaming runtime then falls back to headless; `sdk` requires it; `headless` skips provisioning |
-| `DSH_LARK_GUARDIAN_SAFE_TIMEOUT_MS` | `600000` | 安全模式单任务空闲超时（持续无活动事件才停止并出超时卡）<br>Safe-mode per-task idle timeout (stops the run after it has been silent this long and renders a timeout card) |
-| `DSH_LARK_GUARDIAN_CARD_DENSITY` | `detailed` | 安全模式任务卡片密度（compact / standard / detailed）<br>Card density for safe-mode run cards |
-| `DSH_LARK_UPGRADE_REGISTRY` | `https://registry.npmjs.org` | `upgrade` 探测最新版本的 npm registry（可指向镜像）<br>npm registry used by `upgrade` to discover the latest version (mirrors supported) |
-| `DSH_LARK_UPGRADE_CHECK` | `1` | `doctor` / `/version` 是否探测 npm 最新版本（`0` 关闭，best-effort）<br>Whether `doctor` / `/version` probe npm latest (`0` disables; best-effort) |
-| `DSH_LARK_UPGRADE_CHECK_INTERVAL_MS` | `21600000` | 桥接引擎检查新版本的间隔（`0` 关闭，默认 6h）<br>Bridge new-version check interval (`0` disables; default 6h) |
-| `DSH_LARK_UPGRADE_NOTIFY` | `false` | `true` 时发现新版本向指定 chat 推送飞书通知（默认仅日志）<br>Push a Feishu notification to the target chat when a newer version is found (default: log-only) |
-| `DSH_LARK_UPGRADE_NOTIFY_CHAT` | — | 接收更新通知的 chat id（配合 `DSH_LARK_UPGRADE_NOTIFY=true`）<br>Chat receiving update notifications (with `DSH_LARK_UPGRADE_NOTIFY=true`) |
+| `DSH_LARK_HOME` | `~/.dsh-lark` | 本地状态根目录|
+| `DSH_LARK_TENANT` | `feishu` | `feishu` 或 `lark`|
+| `DSH_LARK_WORKSPACE` | 未设置 | 新会话默认工作目录|
+| `DSH_LARK_DSH_COMMAND` | `自动发现` | dsh 启动命令；通常无需设置|
+| `DSH_LARK_DSH_ARGS` | `自动发现` | dsh 启动参数，逗号分隔；通常无需设置|
+| `DSH_LARK_ADAPTER` | `sdk` | `sdk`（默认）/ `acp`（审批）/ `headless`（legacy）/ `web`（本地 dsh web agent，单写者）|
+| `DSH_LARK_PROVIDER` | `deepseek-official` | 模型 provider|
+| `DSH_LARK_MODEL` | `deepseek-v4-flash` | 默认模型|
+| `DSH_LARK_MAX_TOKENS` | 未设置 | SDK agent 每请求输出 token 上限|
+| `DSH_LARK_WEB_URL` | `http://127.0.0.1:3080` | `web` 适配器：本地 dsh web agent 的 base URL|
+| `DSH_LARK_WEB_PUSH` | `true` | `web` 适配器：网页端回合完成时推送到飞书并自动切换会话映射（`0` 关闭）|
+| `DSH_LARK_ACCESS_DEFAULT_DENY` | `false` | 无白名单时拒绝私聊|
+| `DSH_LARK_EVENT_FRESHNESS_MS` | `600000` | 过期消息拒绝窗口（0 关闭）|
+| `DSH_LARK_RUN_TIMEOUT_MS` | `300000` | 单次运行空闲超时：持续无活动事件才终止（活跃任务不会被误杀）|
+| `DSH_LARK_STOP_GRACE_MS` | `5000` | SIGTERM 后等待优雅退出再 SIGKILL 的宽限期|
+| `DSH_LARK_SCOPE_CONCURRENCY` | `2` | 每个 scope 的并行任务数（1=严格串行）|
+| `DSH_LARK_RETENTION_MSGS` | `40` | 每个 scope 保留的消息条数（0=全部保留）|
+| `DSH_LARK_ARCHIVE_MAX` | `50` | 每个 scope 最多保留的归档数（0=不清理）|
+| `DSH_LARK_ARCHIVE_MAX_AGE_DAYS` | `90` | 归档最大保留天数（0=不清理）|
+| `DSH_LARK_HEARTBEAT_MS` | `5000` | 桥接引擎心跳写入间隔（守护存活信号）|
+| `DSH_LARK_GUARDIAN_DISABLED` | `false` | `1` 时安全网守护进程保持停止|
+| `DSH_LARK_GUARDIAN_PROFILE` | `dsh-lark` | 守护监视 / 重启的 dsh profile（首次安装时写入状态）|
+| `DSH_LARK_GUARDIAN_BRIDGE_PROFILE` | `default` | 提供飞书凭据与白名单的桥接状态 profile|
+| `DSH_LARK_GUARDIAN_POLL_MS` | `2000` | 守护看门狗轮询间隔|
+| `DSH_LARK_GUARDIAN_STALE_MS` | `15000` | 心跳超时阈值，超过且无 dsh 进程则接管飞书通道|
+| `DSH_LARK_GUARDIAN_ENGINE_DEAD_MS` | `120000` | dsh 进程存活但心跳持续超时该时长，判定桥接引擎已死并接管|
+| `DSH_LARK_GUARDIAN_SAFE_ADAPTER` | `auto` | 安全模式引擎：`auto` 优先 SDK 流式、失败回退 headless；`sdk` 强制 SDK；`headless` 跳过预置|
+| `DSH_LARK_GUARDIAN_SAFE_TIMEOUT_MS` | `600000` | 安全模式单任务空闲超时（持续无活动事件才停止并出超时卡）|
+| `DSH_LARK_GUARDIAN_CARD_DENSITY` | `detailed` | 安全模式任务卡片密度（compact / standard / detailed）|
+| `DSH_LARK_UPGRADE_REGISTRY` | `https://registry.npmjs.org` | `upgrade` 探测最新版本的 npm registry（可指向镜像）|
+| `DSH_LARK_UPGRADE_CHECK` | `1` | `doctor` / `/version` 是否探测 npm 最新版本（`0` 关闭，best-effort）|
+| `DSH_LARK_UPGRADE_CHECK_INTERVAL_MS` | `21600000` | 桥接引擎检查新版本的间隔（`0` 关闭，默认 6h）|
+| `DSH_LARK_UPGRADE_NOTIFY` | `false` | `true` 时发现新版本向指定 chat 推送飞书通知（默认仅日志）|
+| `DSH_LARK_UPGRADE_NOTIFY_CHAT` | — | 接收更新通知的 chat id（配合 `DSH_LARK_UPGRADE_NOTIFY=true`）|
 启动时会自动查找本机常见的 `@deepseek-ai/dsh` 安装位置。只有自动发现失败或需要指定特殊 profile 时，才需要设置这两个变量。
-On startup the bot auto-discovers common local `@deepseek-ai/dsh` installations. Set these two
-variables only when auto-discovery fails or a special profile is required.
-## 权限与数据 | Permissions & Data
+## 权限与数据
 本工具在**本机**运行，安装前请知悉它会访问：
-This tool runs **locally**; before installing, be aware that it accesses:
 - **飞书凭据**：PersonalAgent 应用的 `app_id` / `app_secret`，明文写入本机 `~/.dsh-lark/config.json`（文件权限 600）。
 - **文件系统**：读取 / 写入你通过 `/cd`、`/ws` 指定的工作目录（含执行 shell 命令、修改文件）。
 - **网络**：向飞书开放平台建立 WebSocket 出站长连接收发消息；向 DeepSeek API 发送任务上下文。
@@ -624,106 +410,49 @@ This tool runs **locally**; before installing, be aware that it accesses:
   `/safemode` 时创建仅官方核心的 dsh profile（headless 或 SDK JSON-RPC runtime，均无第三方插件）
   并逐条执行任务；SDK 引擎会以官方 `dsh-sdk-jsonrpc-server` 子进程提供实时流式事件。
-- **Feishu credentials**: the PersonalAgent app `app_id` / `app_secret`, stored in plaintext at
-  `~/.dsh-lark/config.json` (file mode 600).
-- **File system**: reads / writes the working directories you choose with `/cd` and `/ws`
-  (including running shell commands and modifying files).
-- **Network**: an outbound WebSocket long connection to the Feishu open platform for messages, and
-  task context sent to the DeepSeek API.
-- **Local callback**: when the `lark_notify` tool runs, the dsh runtime subprocess calls the
-  bridge process back over a random 127.0.0.1 port with a per-boot token (loopback only).
-- **Processes**: spawns local `dsh` runtime subprocesses (`dsh-sdk-jsonrpc-server` / `dsh-acp`
-  profiles) to run agent tasks.
-- **dsh configuration**: `/model` `/providers` `/provider` `/key` read / write
-  `~/.dsh/settings.yaml` and `~/.dsh/.credentials.yaml` using the official dsh storage protocol
-  (admin-only writes; settings keep only `apiKeyEnv` references; credentials file mode 0600,
-  directory 0700; literal keys never enter settings or chat history).
-- **Safety-net guardian (optional)**: when installed, a system-level resident process reads the
-  Feishu credentials from `~/.dsh-lark/config.json`; it takes over the same bot's Feishu long
-  connection only after dsh goes down and scans local processes (command lines via `ps` only, no
-  memory access). On `/safemode` it provisions a core-only dsh profile at
-  `~/.dsh/profiles/<profile>-safe` and runs `dsh --profile <safe> "<prompt>"` per message.
 所有数据仅在本机与飞书、DeepSeek 之间流转，不收集、不上传任何遥测。密钥不会提交进仓库（见 `.gitignore`）。
-All data flows only between this machine, Feishu and DeepSeek; nothing is collected or uploaded
-as telemetry. Keys are never committed to the repository (see `.gitignore`).
-## 排障 | Troubleshooting
+## 排障
 先运行 `dsh-lark-bot doctor`，它会检查 profile、工作目录，并对当前 adapter 做真实可用性探测
 （`sdk` / `acp` / `headless` 对应 runtime 的初始化握手）。
-Run `dsh-lark-bot doctor` first; it checks the profile and working directory and performs a real
-availability probe for the current adapter (`sdk` / `acp` / `headless` runtime handshake).
 常见问题：
-Common issues:
 - **bot 静默 / 长连接失败**：查看 stderr 上的 JSONL 日志，关注 `channel` 与 `channel-command` 类别；SDK 会自动重连。
 - **agent 无响应**：发送 `/status` 查看当前 scope、cwd 和 active run；发送 `/stop` 终止当前任务；持续无响应超过 `DSH_LARK_RUN_TIMEOUT_MS` 时看门狗会自动终止（空闲超时，活跃任务不会被误杀）。
 - **首次扫码失败**：确认本机时间准确、网络可访问飞书开放平台；已拿到 App ID/Secret 时可用 `--app-id` / `--app-secret` 跳过扫码。
-- **Silent bot / long-connection failure**: check the JSONL logs on stderr, focusing on the
-  `channel` and `channel-command` categories; the SDK reconnects automatically.
-- **Unresponsive agent**: send `/status` to view the scope, cwd and active run; send `/stop` to
-  terminate the current task; the idle watchdog terminates it automatically after it has been
-  silent for `DSH_LARK_RUN_TIMEOUT_MS` (active streaming work is never cut short).
-- **First QR binding fails**: make sure the local clock is accurate and the Feishu open platform
-  is reachable; with an existing App ID/Secret you can skip scanning via `--app-id` /
-  `--app-secret`.
 桥接引擎日志以 JSON Lines 输出到 stderr（由 dsh 宿主进程捕获；`logs/bot.log` 是 0.6.0
 独立服务时代的遗留路径，0.7.0 起不再写入）；dsh 宿主日志走 dsh 自己的日志体系。
-The bridge engine logs JSON Lines to stderr (captured by the dsh host; `logs/bot.log` is a
-leftover path from the 0.6.0 standalone-service era and is no longer written since 0.7.0); the
-dsh host uses its own logging.
-**回滚 / Rollback**：`dsh plugin --profile dsh-lark remove dsh-lark-bot` 后重装固定版本即可
+**回滚**：`dsh plugin --profile dsh-lark remove dsh-lark-bot` 后重装固定版本即可
 （如 `dsh plugin --profile dsh-lark add dsh-lark-bot@0.6.0`）；`~/.dsh-lark` 状态独立于插件
 本体，升级 / 回滚不会丢失配置与会话。
-To roll back: remove the plugin and reinstall a pinned version (e.g.
-`dsh plugin --profile dsh-lark add dsh-lark-bot@0.6.0`); `~/.dsh-lark` state is independent of
-the package, so config and sessions survive upgrades / rollbacks.
-## 开发 | Development
+## 开发
 ```bash
 pnpm install
 pnpm typecheck
 pnpm test
 pnpm build
-pnpm check:publish-bundle   # 校验 dist 与全部 exports/bin 入口一致（发布前防线）| verifies dist matches every export & the CLI entry (release gate)
+pnpm check:publish-bundle   # 校验 dist 与全部 exports/bin 入口一致（发布前防线）
 pnpm ci:local
-pnpm release:check   # ci:local + 上游一致性检查 | ci:local + upstream consistency check
-pnpm compat:probe    # 临时 DSH_HOME 安装锁定版 dsh，跑真实 SDK 握手 | installs pinned dsh into a temp DSH_HOME and runs a real SDK handshake
-pnpm dsh:upstream    # 对比 npm 上游 stable 与锁定矩阵 | compares npm upstream stable with the pinned matrix
-pnpm security:monitor # 假冒仓库与仿冒包监控（建议每周）| impostor-repo & npm copycat monitor (recommended weekly)
+pnpm release:check   # ci:local + 上游一致性检查
+pnpm compat:probe    # 临时 DSH_HOME 安装锁定版 dsh，跑真实 SDK 握手
+pnpm dsh:upstream    # 对比 npm 上游 stable 与锁定矩阵
+pnpm security:monitor # 假冒仓库与仿冒包监控（建议每周）
 ```
 开发规范见 [`AGENTS.md`](AGENTS.md)，模块契约见 [`docs/API.md`](docs/API.md)，架构见 [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md)。
 兼容矩阵的升级政策与自动化见 [`docs/COMPATIBILITY.md`](docs/COMPATIBILITY.md)。
-See [`AGENTS.md`](AGENTS.md) for the development workflow, [`docs/API.md`](docs/API.md) for
-module contracts, and [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) for the architecture. See
-[`docs/COMPATIBILITY.md`](docs/COMPATIBILITY.md) for the compatibility matrix, upgrade policy
-and automation.
-**贡献 / Contributing**：欢迎 Issue 与 PR。开发流程见 [`AGENTS.md`](AGENTS.md)（必读文档、
+**贡献**：欢迎 Issue 与 PR。开发流程见 [`AGENTS.md`](AGENTS.md)（必读文档、
 提交规范与推送边界），生态交付标准见 [`docs/ECOSYSTEM.md`](docs/ECOSYSTEM.md)。
-Contributions are welcome via Issues and PRs; see [`AGENTS.md`](AGENTS.md) for the workflow
-(required reading, commit conventions, push policy) and [`docs/ECOSYSTEM.md`](docs/ECOSYSTEM.md)
-for ecosystem delivery standards.
 发布双包（`dsh-lark-bot` 与 `dsh-feishu-bot` 共享同一份 dist / 版本 / 依赖）：
-Publishing both packages (`dsh-lark-bot` and `dsh-feishu-bot` share the same dist / version /
-dependencies):
 ```bash
 pnpm publish:dual:dry-run
 pnpm publish:dual
@@ -731,64 +460,37 @@ pnpm publish:dual
 `scripts/publish-dual-packages.mjs` 从根 `package.json` 生成两份仅 `name` / `bin` 不同的发布清单，避免两份源码漂移。发布时整目录同步 `dist/`，并在发布前校验 `package.json` 每个 `exports` 子路径与 CLI 入口在产物中都存在——任何缺失（如 v0.9.0 的 `ask` 入口漏拷）都会直接中止发布。GitHub tag `v*` 会触发 [`release.yml`](.github/workflows/release.yml) 自动发布两个 npm 包并创建 Release。
-`scripts/publish-dual-packages.mjs` generates two publish manifests from the root
-`package.json`, differing only in `name` / `bin`, so the two copies never drift. A GitHub tag
-`v*` triggers [`release.yml`](.github/workflows/release.yml) to publish both npm packages and
-create a Release automatically.
 同一份 dist 还会以 `@plutokeating/dsh-lark-bot` 和 `@plutokeating/dsh-feishu-bot` 发布到 GitHub Packages，便于在 GitHub Packages 页面查看。
-The same dist is also published to GitHub Packages as `@plutokeating/dsh-lark-bot` and
-`@plutokeating/dsh-feishu-bot`, viewable on the GitHub Packages page.
-## 维护与支持 | Maintenance
+## 维护与支持
-- 状态：**活跃维护（Active）**。主维护者：**PlutoKeating**。
+- 状态：**活跃维护**。主维护者：**PlutoKeating**。
 - 问题 / 建议：优先在 GitHub Issues 提交；安全漏洞请走 [`SECURITY.md`](SECURITY.md) 的私下报告渠道。
-- Status: **active**. Primary maintainer: **PlutoKeating**.
-- Bugs / feature requests: GitHub Issues; security issues via the private channel in
-  [`SECURITY.md`](SECURITY.md).
-社区收录情况见下节「社区收录情况 | Community Listings」。
+社区收录情况见下节「社区收录情况」。
-See "Community Listings" in the next section for ecosystem registration status.
-## 作者 | Author
+## 作者
 本项目由 **PlutoKeating** 开发并维护。作者专注于自动化与开发者工具，习惯从真实使用场景出发
 做软件：本项目正是从“用飞书 / Lark 群聊驱动 DeepSeek Agent”的日常需求长出来的，逐步演进为
 一套带守护、自愈与一键升级能力的完整桥接方案。更多信息见个人主页：
 [PlutoKeating](https://github.com/PlutoKeating)。
-This project is developed and maintained by **PlutoKeating**, who focuses on automation and
-developer tooling and prefers building software from real usage. It grew out of the daily need
-to drive DeepSeek agents from Feishu/Lark group chats, evolving into a complete bridge with
-guardian, self-healing, and one-command upgrade capabilities. See the author's profile:
-[PlutoKeating](https://github.com/PlutoKeating).
-## 贡献者 | Contributors
+## 贡献者
 感谢以下贡献者（按合入 / 提交时间）：
-Thanks to the following contributors (by merge / submission time):
-| 贡献者 Contributor | 贡献 Contribution | 状态 Status |
+| 贡献者 | 贡献 | 状态 |
 | :--- | :--- | :--- |
-| [koprivnikarurnaa-oss](https://github.com/koprivnikarurnaa-oss) | [PR #9](https://github.com/PlutoKeating/dsh-lark-bot/pull/9)：web 单写者适配器 + self-heal v2 + 守护自动重启<br>Web single-writer adapter + self-heal v2 + guardian auto-relaunch | ✅ 已合入<br>Merged |
-| [Normanyin](https://github.com/Normanyin) | [PR #11](https://github.com/PlutoKeating/dsh-lark-bot/pull/11)：`/newg` 自动建群命令<br>`/newg` auto-create group chat command | ✅ 已合入（cherry-pick）<br>Merged (cherry-pick) |
+| [koprivnikarurnaa-oss](https://github.com/koprivnikarurnaa-oss) | [PR #9](https://github.com/PlutoKeating/dsh-lark-bot/pull/9)：web 单写者适配器 + self-heal v2 + 守护自动重启| ✅ 已合入|
+| [Normanyin](https://github.com/Normanyin) | [PR #11](https://github.com/PlutoKeating/dsh-lark-bot/pull/11)：`/newg` 自动建群命令| ✅ 已合入（cherry-pick）|
 > 说明：GitHub 贡献者图按 commit 作者邮箱归因。PR #9 合入时的提交使用了本地通用身份
 > `dsh-user <dsh-user@local>`（未绑定 GitHub 账号），因此未自动计入贡献者图；本表为仓库侧
 > 的明确署名，PR #11 的提交身份已绑定其账号，合入后会自动计入。
 >
-> Note: GitHub's contributor graph attributes commits by author email. The commits merged via
-> PR #9 carried a local generic identity (`dsh-user <dsh-user@local>`, not linked to a GitHub
-> account), so they are not auto-counted in the graph; this table is the repository's explicit
-> acknowledgment. PR #11's commits are authored under the contributor's linked account and will
-> be credited automatically once merged.
-## 许可与安全 | License & Security
+## 许可与安全
 - **许可证**：GNU Affero General Public License v3.0（见 `LICENSE`）。
 - **版权归属**：源码版权归项目维护者所有，按 AGPL-3.0 授权；「DeepSeek」「飞书 / Lark」等
@@ -797,39 +499,30 @@ Thanks to the following contributors (by merge / submission time):
 - **安全模型**：默认拒绝、密钥脱敏、路径 containment、SSRF 防护、过期事件拒绝与交互工具
   默认禁用——详见 [`SECURITY.md`](SECURITY.md)。
-- **License**: GNU Affero General Public License v3.0 (see `LICENSE`).
-- **Copyright**: source is owned by the maintainers and licensed under AGPL-3.0; "DeepSeek" and
-  "Feishu / Lark" trademarks belong to their respective owners.
-- **Security reports**: report vulnerabilities privately via GitHub Security Advisory; do not
-  open a public issue.
-- **Security model**: default-deny, secret redaction, path containment, SSRF protection, stale
-  event rejection and default-disabled interactive tools — see [`SECURITY.md`](SECURITY.md).
-## 文档 | Documentation
+## 文档
 > 接手本项目的工程师：**先读 [`docs/REQUIREMENTS.md`](docs/REQUIREMENTS.md) 和 [`docs/RESEARCH.md`](docs/RESEARCH.md)**，即可完整理解项目诉求与来龙去脉，无需线下沟通。
-> Engineers taking over this project: **read [`docs/REQUIREMENTS.md`](docs/REQUIREMENTS.md) and [`docs/RESEARCH.md`](docs/RESEARCH.md) first**.
-| 文档 Doc | 内容 Content |
+| 文档 | 内容 |
 | :--- | :--- |
-| [`docs/REQUIREMENTS.md`](docs/REQUIREMENTS.md) | 完整项目诉求、产出预期、规范与约束<br>Complete requirements, outputs & specifications |
-| [`docs/RESEARCH.md`](docs/RESEARCH.md) | 调研报告：官方现状、参考项目、可行性、技术差异<br>Research: official status, references, feasibility |
-| [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) | 架构分层与目录映射<br>Architecture layering & directory mapping |
-| [`docs/API.md`](docs/API.md) | 模块接口与契约<br>Module interfaces & contracts |
-| [`docs/QUICK_START.md`](docs/QUICK_START.md) | 安装与快速开始<br>Install & quick start |
-| [`docs/COMPATIBILITY.md`](docs/COMPATIBILITY.md) | 兼容矩阵、升级政策与自动化<br>Compatibility matrix, upgrade policy & automation |
-| [`docs/MANUAL.md`](docs/MANUAL.md) | 完整用户手册<br>Complete user manual |
-| [`docs/adapter-notes.md`](docs/adapter-notes.md) | dsh adapter 接入说明（接口 / 落点 / 路线）<br>How to plug the dsh adapter |
-| [`docs/UPGRADE.md`](docs/UPGRADE.md) | 更新链路架构审查、生效机制与已知边界（issue #15）<br>Upgrade flow architecture, activation & known boundaries |
-| [`docs/ECOSYSTEM.md`](docs/ECOSYSTEM.md) | 生态兼容与交付标准（实现工程师必读）<br>Ecosystem & delivery standards (for engineers) |
-| [`docs/roadmap.md`](docs/roadmap.md) | 路线图与里程碑<br>Roadmap & milestones |
-| [`docs/PLAN.md`](docs/PLAN.md) | 主线开发计划与验收标准<br>Development plan & acceptance criteria |
-| [`SECURITY.md`](SECURITY.md) | 安全模型与报告渠道<br>Security model & reporting |
-| [`AGENTS.md`](AGENTS.md) | AI Agent 开发工作流规范<br>AI agent workflow spec |
-## 架构 | Architecture
-> 详见 [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) | See [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) for details.
+| [`docs/REQUIREMENTS.md`](docs/REQUIREMENTS.md) | 完整项目诉求、产出预期、规范与约束|
+| [`docs/RESEARCH.md`](docs/RESEARCH.md) | 调研报告：官方现状、参考项目、可行性、技术差异|
+| [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) | 架构分层与目录映射|
+| [`docs/API.md`](docs/API.md) | 模块接口与契约|
+| [`docs/QUICK_START.md`](docs/QUICK_START.md) | 安装与快速开始|
+| [`docs/COMPATIBILITY.md`](docs/COMPATIBILITY.md) | 兼容矩阵、升级政策与自动化|
+| [`docs/MANUAL.md`](docs/MANUAL.md) | 完整用户手册|
+| [`docs/adapter-notes.md`](docs/adapter-notes.md) | dsh adapter 接入说明（接口 / 落点 / 路线）|
+| [`docs/UPGRADE.md`](docs/UPGRADE.md) | 更新链路架构审查、生效机制与已知边界（issue #15）|
+| [`docs/ECOSYSTEM.md`](docs/ECOSYSTEM.md) | 生态兼容与交付标准（实现工程师必读）|
+| [`docs/roadmap.md`](docs/roadmap.md) | 路线图与里程碑|
+| [`docs/PLAN.md`](docs/PLAN.md) | 主线开发计划与验收标准|
+| [`SECURITY.md`](SECURITY.md) | 安全模型与报告渠道|
+| [`AGENTS.md`](AGENTS.md) | AI Agent 开发工作流规范|
+## 架构
+> 详见 [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md)。
 ```
 飞书 / Lark ──WebSocket 长连接──▶ bridge/ ──▶ session/ ──▶ workspace/ ──▶ adapters/ ──▶ dsh ──▶ DeepSeek V4
@@ -841,102 +534,83 @@ Thanks to the following contributors (by merge / submission time):
 通道接收 `/safemode` 控制信号，以仅核心 profile（`dsh-base` + `dsh-headless`）拉起受限对话
 用于自愈，`/safemode exit` 重启完整 profile 并交还通道。
-The core idea: **decouple the Feishu channel from the agent backend**. The bridge layer follows the battle-tested `lark-channel-bridge` approach (WebSocket long-connection + streaming cards + session routing); the agent backend is abstracted behind an adapter, defaulting to the official DeepSeek Harness SDK (`DSH_LARK_ADAPTER=sdk`), with an optional ACP approval mode and the legacy headless fallback.
-The optional safety-net guardian (`src/guardian/`) runs as a separate resident process: silent
-while dsh is up, it takes over the Feishu channel when dsh goes down, accepts `/safemode` control
-signals, runs a restricted core-only conversation (`dsh-base` + `dsh-headless`) for self-healing,
-and relaunches the full profile on `/safemode exit`.
+## 目录结构
-## 目录结构 | Directory Structure
-| 目录 Dir | 职责 Responsibility |
+| 目录 | 职责 |
 | :--- | :--- |
-| `src/bridge/` | 飞书通道接入（消息、卡片、媒体）<br>Feishu channel integration |
-| `src/onboard/` | 首次扫码创建 / 绑定 PersonalAgent 应用<br>First-run QR onboarding |
-| `src/session/` | 会话路由、排队、访问控制<br>Session routing, queueing, access control |
-| `src/workspace/` | 项目工作区、git worktree 隔离与规则注入<br>Project workspace, git worktree isolation & rule injection |
-| `src/adapters/` | agent 后端适配器（sdk 默认 / acp 审批 / headless legacy / web 单写者）<br>Agent backend adapters (sdk / acp / headless / web single-writer) |
-| `src/card/` | 流式卡片状态与渲染<br>Streaming card state & rendering |
-| `src/bot/` | 运行注册、消息排队、审批/问答注册表<br>Run registry, queueing, approval/question registries |
-| `src/commands/` | 斜杠命令（/cd /ws /new …）<br>Slash commands |
-| `src/cli/` | CLI 入口：`setup`（唯一安装命令）/ `doctor`（诊断）/ `upgrade`（一键升级）/ 隐藏 `run`<br>CLI entry: setup / doctor / upgrade / hidden run |
-| `src/upgrade/` | 一键升级（issue #10）：版本探测、升级状态、运行检测、guardian/profile 重启助手、runtime 链接修复<br>One-command upgrade (issue #10): version probe, upgrade state, running-state detection, restart helpers, runtime link repair |
-| `src/guardian/` | 安全网守护：心跳、进程观察、仅核心安全 profile、接管状态机、系统服务安装<br>Safety-net guardian: heartbeat, process watch, core-only safe profile, takeover state machine, service install |
-| `src/config/` | profile / 配置 / 访问白名单 / dsh 配置管理<br>Profile, config, access & dsh config management |
-| `src/core/` | 结构化日志<br>Structured logging |
-| `src/media/` | 附件下载与文本注入<br>Attachment download & text injection |
-| `src/platform/` | 跨平台原子写入<br>Cross-platform atomic writes |
-| `docs/` | 架构、路线图等文档<br>Architecture, roadmap & docs |
-| `reference/` | 参考研究用的克隆仓库（不提交）<br>Cloned reference repos (not committed) |
-## 路线图 | Roadmap
-见 [`docs/roadmap.md`](docs/roadmap.md) | See [`docs/roadmap.md`](docs/roadmap.md).
-## 参考项目 | References
-| 项目 Project | 说明 About |
+| `src/bridge/` | 飞书通道接入（消息、卡片、媒体）|
+| `src/onboard/` | 首次扫码创建 / 绑定 PersonalAgent 应用|
+| `src/session/` | 会话路由、排队、访问控制|
+| `src/workspace/` | 项目工作区、git worktree 隔离与规则注入|
+| `src/adapters/` | agent 后端适配器（sdk 默认 / acp 审批 / headless legacy / web 单写者）|
+| `src/card/` | 流式卡片状态与渲染|
+| `src/bot/` | 运行注册、消息排队、审批/问答注册表|
+| `src/commands/` | 斜杠命令（/cd /ws /new …）|
+| `src/cli/` | CLI 入口：`setup`（唯一安装命令）/ `doctor`（诊断）/ `upgrade`（一键升级）/ 隐藏 `run`|
+| `src/upgrade/` | 一键升级（issue #10）：版本探测、升级状态、运行检测、guardian/profile 重启助手、runtime 链接修复|
+| `src/guardian/` | 安全网守护：心跳、进程观察、仅核心安全 profile、接管状态机、系统服务安装|
+| `src/config/` | profile / 配置 / 访问白名单 / dsh 配置管理|
+| `src/core/` | 结构化日志|
+| `src/media/` | 附件下载与文本注入|
+| `src/platform/` | 跨平台原子写入|
+| `docs/` | 架构、路线图等文档|
+| `reference/` | 参考研究用的克隆仓库（不提交）|
+## 路线图
+见 [`docs/roadmap.md`](docs/roadmap.md)。
+## 参考项目
+| 项目 | 说明 |
 | :--- | :--- |
-| [`zarazhangrui/lark-coding-agent-bridge`](https://github.com/zarazhangrui/lark-coding-agent-bridge) | 飞书 ↔ Claude Code / Codex 桥接，本项目的直接参照<br>Feishu ↔ Claude Code / Codex bridge; the direct reference for this project |
-| [`deepseek-ai/deepseek-harness`](https://github.com/deepseek-ai/deepseek-harness) | DeepSeek Harness（`dsh`），agent 后端<br>DeepSeek Harness (`dsh`), the agent backend |
-| [`grinev/opencode-telegram-bot`](https://github.com/grinev/opencode-telegram-bot) | OpenCode 的 Telegram 手机端，另一参照<br>Telegram mobile client for OpenCode; another reference |
+| [`zarazhangrui/lark-coding-agent-bridge`](https://github.com/zarazhangrui/lark-coding-agent-bridge) | 飞书 ↔ Claude Code / Codex 桥接，本项目的直接参照|
+| [`deepseek-ai/deepseek-harness`](https://github.com/deepseek-ai/deepseek-harness) | DeepSeek Harness（`dsh`），agent 后端|
+| [`grinev/opencode-telegram-bot`](https://github.com/grinev/opencode-telegram-bot) | OpenCode 的 Telegram 手机端，另一参照|
-## 社区收录情况 | Community Listings
+## 社区收录情况
-> 本项目的社区收录 / 推荐状态，随提交的更新请求持续维护。截至 v0.14.0（2026-08-17 复核）：
-> Community listing & recommendation status, kept current as update requests land. As of v0.14.0 (re-verified 2026-08-17):
+<div align="center">
-| 平台 Platform | 状态 Status | 说明 Notes |
-| :--- | :--- | :--- |
-| [awesome-dsh-plugins](https://github.com/AdamPlatin123/awesome-dsh-plugins) | ✅ 已收录 · 运行级可用<br>Listed · runtime-verified | 社区榜单标注 `✅ 运行级可用`（agent 实测通过）；收录条目 v0.8.0 经 [PR #127](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/127) 合并，榜单行同步 [issue #139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) 已关闭；数据刷新至 v0.14.0 待跟进<br>Shown as `✅ 运行级可用` (agent-tested); v0.8.0 entry merged via [PR #127](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/127); leaderboard sync [#139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) closed; refresh to v0.14.0 pending |
-| [dshfind](https://dshfind.com/zh/plugins/PlutoKeating/dsh-lark-bot) | ✅ 已收录 · 详情页在线<br>Listed · detail page live | 条目名称修正 [issue #2](https://github.com/hikariming/dshfind/issues/2) 已关闭；v0.10.1 数据刷新 [issue #6](https://github.com/hikariming/dshfind/issues/6) 待处理；v0.14.0 刷新待跟进；顶部徽章 / 展示卡来自 dshfind<br>Entry name fixed ([issue #2](https://github.com/hikariming/dshfind/issues/2) closed); v0.10.1 refresh ([issue #6](https://github.com/hikariming/dshfind/issues/6)) pending; v0.14.0 refresh pending; the header badge / card comes from dshfind |
-| [omdsh-dev/community](https://github.com/orgs/omdsh-dev/discussions/11) | ✅ 收录申请通过 · 讨论活跃<br>Accepted · discussion active | `[Plugin]` 收录申请（Discussion #11）已通过并持续维护，最新更新说明 v0.10.2；v0.14.0 更新待跟进<br>`[Plugin]` submission (Discussion #11) accepted and active, latest notes v0.10.2; v0.14.0 update pending |
+<a href="https://dshfind.com/zh/plugins/PlutoKeating/dsh-lark-bot?ref=badge"><img src="https://dshfind.com/api/card/PlutoKeating/dsh-lark-bot?lang=zh" alt="dshfind" width="440"></a>
-**更新请求进度 / Update request status（截至 2026-08-17 复核 | as of 2026-08-17）**：
+</div>
-- awesome-dsh-plugins 收录条目 v0.8.0：[#127](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/127) — ✅ 已合并；榜单行同步：[#139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) — ✅ 已关闭
-- dshfind 条目名称修正 + v0.8.0 刷新：[#2](https://github.com/hikariming/dshfind/issues/2) — ✅ 已关闭；v0.10.1 刷新：[#6](https://github.com/hikariming/dshfind/issues/6) — 📨 待处理
-- omdsh-dev/community 收录：[Discussion #11](https://github.com/orgs/omdsh-dev/discussions/11) — ✅ 通过，讨论活跃（最新更新说明 v0.10.2）
-- 平台数据刷新至 v0.14.0 — ⏸ 暂缓提交（安全窗口内保持低调，见「假冒仓库警告」）
+> 本项目的社区收录 / 推荐状态，随提交的更新请求持续维护。截至 v0.15.1（2026-08-17 复核）：
+| 平台 | 状态 | 说明 |
+| :--- | :--- | :--- |
+| [awesome-dsh-plugins](https://github.com/AdamPlatin123/awesome-dsh-plugins) | ✅ 已收录 · 运行级可用| 社区榜单标注 `✅ 运行级可用`（agent 实测通过）；收录条目 v0.8.0 经 [PR #127](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/127) 合并，榜单行同步 [issue #139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) 已关闭；**v0.15.1 数据刷新 [PR #230](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/230) 已提交 · 待合并**|
+| [awesome-dsh-plugin](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin) | 📨 收录 PR 已提交 · 待合并| 7.2k+ star 的社区插件精选大榜（`dsh-plugin` 生态流量入口）；收录 PR [#1408](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/1408) 已提交，合并后回填状态|
+| [dshfind](https://dshfind.com/zh/plugins/PlutoKeating/dsh-lark-bot) | ✅ 已收录 · 详情页在线| 条目名称修正 [issue #2](https://github.com/hikariming/dshfind/issues/2) 已关闭；**v0.15.1 数据刷新请求 [#6 跟进评论](https://github.com/hikariming/dshfind/issues/6#issuecomment-5317081509) 已提交 · 待维护方处理**；顶部徽章 / 展示卡来自 dshfind|
+| [dshbase](https://dshbase.com/zh/plugins/dsh-lark-bot) | ✅ 已收录 · 实测可装| 中文插件目录（收录 1771+ 插件），自动化 CI 实测 `dsh plugin add` 可装可启动，标注 `✅ 已验证 · 实测可装`；顶部徽章来自 dshbase|
+| [omdsh-dev/community](https://github.com/orgs/omdsh-dev/discussions/11) | ✅ 收录申请通过 · 讨论活跃| `[Plugin]` 收录申请（Discussion #11）已通过并持续维护，最新更新说明 v0.10.2；**v0.15.1 更新说明已备妥，待人工粘贴（org 级 discussion 不支持 API）**|
-**Update requests**:
+**更新请求进度（截至 2026-08-17 复核）**：
-- awesome-dsh-plugins v0.8.0 entry: [#127](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/127) — ✅ merged; leaderboard sync: [#139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) — ✅ closed
-- dshfind name fix + v0.8.0 refresh: [#2](https://github.com/hikariming/dshfind/issues/2) — ✅ closed; v0.10.1 refresh: [#6](https://github.com/hikariming/dshfind/issues/6) — 📨 pending
-- omdsh-dev/community listing: [Discussion #11](https://github.com/orgs/omdsh-dev/discussions/11) — ✅ accepted, discussion active (latest notes v0.10.2)
-- Platform refresh to v0.14.0 — ⏸ deferred (staying low-key during the security window; see "Impostor warning" below)
+- awesome-dsh-plugins 收录条目 v0.8.0：[#127](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/127) — ✅ 已合并；榜单行同步：[#139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) — ✅ 已关闭
+- awesome-dsh-plugin 大榜收录：[#1408](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/1408) — 📨 已提交（2026-08-17，v0.15.0 数据；v0.15.1 [跟进评论](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/1408#issuecomment-5317081726) 已提交）
+- dshfind 条目名称修正 + v0.8.0 刷新：[#2](https://github.com/hikariming/dshfind/issues/2) — ✅ 已关闭；v0.10.1 刷新：[#6](https://github.com/hikariming/dshfind/issues/6) — 📨 待处理（v0.15.1 [跟进评论](https://github.com/hikariming/dshfind/issues/6#issuecomment-5317081509) 已提交）
+- omdsh-dev/community 收录：[Discussion #11](https://github.com/orgs/omdsh-dev/discussions/11) — ✅ 通过，讨论活跃（最新更新说明 v0.10.2）；v0.15.1 更新说明 — 📨 已备妥，待人工粘贴
+- 平台数据刷新（v0.14.0 → v0.15.1）— ✅ 已恢复提交（2026-08-17）：awesome-dsh-plugins [PR #230](https://github.com/AdamPlatin123/awesome-dsh-plugins/pull/230) · dshfind [#6 跟进](https://github.com/hikariming/dshfind/issues/6#issuecomment-5317081509) · omdsh 说明备妥
-**亮点跟进 / Highlights follow-ups**（六项独家能力与 issue #6 设计实现）：
+**亮点跟进**（六项独家能力与 issue #6 设计实现）：
 - awesome-dsh-plugins 榜单行同步（仓库描述 → 最新）与 agent-test 报告名称异常：[#139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) — 📨 已提交（维护方已确认，等待渲染周期同步）
 - dshfind 详情页补「对话内管理模型和密钥」亮点：[#2 跟进评论](https://github.com/hikariming/dshfind/issues/2#issuecomment-5301019067) — 📨 已提交
 - omdsh 六项独家亮点补充（含 Guardian 设计实现）：[Discussion #11 亮点评论](https://github.com/orgs/omdsh-dev/discussions/11#discussioncomment-18026370) — 📨 已提交
-**Highlights follow-ups** (six exclusive capabilities & the issue #6 design):
-- awesome-dsh-plugins leaderboard row sync (repo description → latest) & agent-test name anomaly: [#139](https://github.com/AdamPlatin123/awesome-dsh-plugins/issues/139) — 📨 submitted (maintainer confirmed; awaiting the snapshot/render cycle)
-- dshfind detail page: add the in-chat model/key management highlight: [#2 follow-up](https://github.com/hikariming/dshfind/issues/2#issuecomment-5301019067) — 📨 submitted
-- omdsh six-exclusive-highlights summary (incl. the Guardian design): [Discussion #11 highlights comment](https://github.com/orgs/omdsh-dev/discussions/11#discussioncomment-18026370) — 📨 submitted
-## 假冒仓库警告 | Impostor Repository Warning
+## 假冒仓库警告
-> [!WARNING]
 > 2026-08-17 发现假冒仓库 **`tarraencompassing61/dsh-lark-bot`**：非 fork 重新上传、114 个 commit 中
 > 113 个作者为 PlutoKeating、删除全部 CI、关闭 Issues、Releases 为 0，却以“下载 Windows exe 双击运行”的
 > SEO 诱饵 README 冒充官方分发。**本项目从不提供 exe，任何此类下载均为假冒 / 恶意来源。**
-> On 2026-08-17 an impostor repository **`tarraencompassing61/dsh-lark-bot`** was found: re-uploaded as a
-> non-fork with 113/114 commits authored by PlutoKeating, all CI deleted, Issues disabled, zero Releases,
-> and a SEO-bait README offering “Windows exe download & run”. **This project never ships executables —
-> treat any such download as counterfeit / malicious.**
 >
-> 取证存档 Evidence: [`docs/security/2026-08-17-impostor-repo-evidence/`](docs/security/2026-08-17-impostor-repo-evidence/README.md) ·
-> 官方下载渠道 Official download: [`docs/DOWNLOAD.md`](docs/DOWNLOAD.md) ·
-> 持续监控 Ongoing monitor: `pnpm security:monitor`
+> 取证存档：[`docs/security/2026-08-17-impostor-repo-evidence/`](docs/security/2026-08-17-impostor-repo-evidence/README.md) ·
+> 官方下载渠道：[`docs/DOWNLOAD.md`](docs/DOWNLOAD.md) ·
+> 持续监控：`pnpm security:monitor`
-## 免责声明 | Disclaimer
+## 免责声明
-> [!NOTE]
 > 本项目为非官方社区工具，与 DeepSeek、字节跳动 / 飞书（Lark）无关联，亦未获得其背书。DeepSeek Harness、Feishu / Lark 及相关商标归各自权利人所有。
 >
-> This is an unofficial community tool, not affiliated with or endorsed by DeepSeek or ByteDance / Feishu (Lark). DeepSeek Harness, Feishu / Lark and related trademarks belong to their respective owners.

package/package.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "name": "dsh-lark-bot",
-  "version": "0.15.0",
-  "description": "Bridge DeepSeek Harness (dsh) into Feishu / Lark with streaming cards, project workspaces, approvals and scheduling",
+  "version": "0.15.2",
+  "description": "把 DeepSeek Harness (dsh) 装进飞书/Lark 的 bot，扫码即用：流式卡片、项目工作区、并行任务、多角色 Agent、安全网守护。| Bridge DeepSeek Harness (dsh) into Feishu / Lark, scan-to-connect: streaming cards, project workspaces, parallel tasks, multi-role agents, safety-net guardian.",
   "type": "module",
   "packageManager": "pnpm@10.33.0",
   "bin": {
@@ -92,15 +92,23 @@
     "dsh",
     "deepseek",
     "deepseek harness",
+    "deepseek-harness 插件",
+    "deepseek harness 飞书",
     "feishu",
+    "飞书",
+    "飞书机器人",
     "lark",
     "bridge",
     "bot",
+    "扫码",
+    "scan to connect",
     "typescript",
     "chatbot",
-    "messaging",
     "deepseek-harness",
-    "dsh-plugin"
+    "dsh-plugin",
+    "feishu-plugin",
+    "lark-integration",
+    "remote-coding"
   ],
   "license": "AGPL-3.0",
   "engines": {