dsh-ntr 0.1.6 → 0.2.1

package/README.en.md

@@ -70,12 +70,12 @@ To upgrade later: `git pull` → `npm run build` → restart `dsh web`. `add .`
 
 ---
 
-## Getting started
+## Quick start
 
 ### What you need
 
 1. A working DSH install (web or desktop).
-2. At least one ACP agent CLI. The plugin ships presets for common ones, and accepts any stdio-capable ACP agent.
+2. At least one ACP-capable agent, using its terminal build (CLI / TUI). For example Qoder CLI (`qodercli`), CodeBuddy Code (`codebuddy`), Claude Code, or OpenCode — presets for these ship with the plugin; any other agent that starts from the command line in the same `xxx --acp` style can be filled in directly.
 
 ### Three steps
 
@@ -113,7 +113,7 @@ DSH's own `/model`, `/permission`, `/export`, etc. are **not** intercepted by th
 
 ### Approvals and the agent's own permission modes
 
-When the agent wants to touch something sensitive, it asks you. The approval card shows up right in the chat composer; you click Allow or Deny, and it obeys.
+When the agent wants to touch something sensitive, it asks you. The ask appears in the conversation on a card just above the composer (the plugin's own card); the options are exactly the agent's, and what you click is what it receives. The Settings page's "Pending Permission Requests" card is the cross-session mirror — answer there when the conversation isn't open.
 
 Every agent asks differently: some offer a set of options, some only allow/deny, some attach the exact command they are about to run. The plugin presents these as-is, and never pre-decides for you.
 
@@ -267,11 +267,14 @@ These servers are handed to the agent when a session is created; the agent launc
 
 ```bash
 npm install          # dependencies
+git config core.hooksPath .githooks   # enable the commit-msg check (rejects AI attribution)
 npm run build        # host TS declarations + browser bundle
 npm test             # test suite
 dsh plugin --profile web add ./   # mount into the Web profile
 ```
 
+`.githooks/commit-msg` only inspects the commit message: it rejects AI-tool attribution in `Co-Authored-By` / `Generated with` lines, while ordinary prose and human attribution pass. `core.hooksPath` is local config — run this once after cloning.
+
 ### Implementation notes
 
 Each item below corresponds to a real past failure; read the linked doc before changing code. The browser half talks to the host half via `/acp` RPC and `/api/acp/stream` SSE; the host half runs one `AgentBridge` per conversation, driving the agent child process over stdio JSON-RPC.

package/README.md

@@ -70,12 +70,12 @@ dsh plugin --profile web add ./
 
 ---
 
-## 上手
+## 快速开始
 
 ### 你需要什么
 
 1. 一个已经装好的 DSH（Web 或桌面版）。
-2. 至少一个 ACP agent 的命令行程序。插件内置了几个常见预设，也可以填任何支持 stdio 的 ACP agent。
+2. 至少一个支持 ACP 协议的 agent，用它的终端版本（CLI / TUI）即可。例如 Qoder CLI（`qodercli`）、CodeBuddy Code（`codebuddy`）、Claude Code、OpenCode——插件内置了这些常见预设；其他 agent 只要能以类似 `xxx --acp` 的方式从命令行启动，也可以直接填。
 
 ### 三步接入
 
@@ -113,7 +113,7 @@ DSH 自己的 `/model`、`/permission`、`/export` 等在这一模式下**不会
 
 ### 审批与 agent 自己的权限模式
 
-agent 要动敏感的东西时会问你。审批卡直接出现在聊天输入框里，你点允许或拒绝，它照着做。
+agent 要动敏感的东西时会问你。询问卡出现在对话里、聊天输入框上方（插件自己的卡片），选项就是 agent 给的那些，你点哪个它照着做；设置页的「待处理权限请求」是跨会话镜像，对话没打开时在那里回答。
 
 每个 agent 问法不一样：有的给一组选项，有的只给允许/拒绝，有的会附上它要执行的具体命令。插件把这些原样呈现给你，不预先替你决定。
 
@@ -267,11 +267,14 @@ agent 要动敏感的东西时会问你。审批卡直接出现在聊天输入
 
 ```bash
 npm install          # 依赖
+git config core.hooksPath .githooks   # 启用 commit-msg 校验（拒绝 AI 署名）
 npm run build        # 宿主 TS 声明 + 浏览器 Bundle
 npm test             # 测试套件
 dsh plugin --profile web add ./   # 挂载到 Web Profile
 ```
 
+`.githooks/commit-msg` 只校验提交信息：拒绝把 AI 工具写进 `Co-Authored-By` / `Generated with` 之类署名，普通正文与人类署名不受影响。`core.hooksPath` 是本地配置，clone 后执行一次即可。
+
 ### 实现要点
 
 以下每条都对应一处真实故障，改代码前先读对应文档。浏览器半区经 `/acp` RPC 与 `/api/acp/stream` SSE 和宿主半区通信；宿主半区每会话一个 `AgentBridge`，经 stdio JSON-RPC 驱动 agent 子进程。

package/cordis.patch.yml

@@ -31,25 +31,25 @@
         # startupTimeoutMs: 60000    # budget for initialize / session/new / session/load
         # permissionTimeoutMs: 300000
         #                              How long a permission ask may sit unanswered
-        #                              before the deadline fires. ONE window for both
-        #                              places an ask can live — the conversation's
-        #                              approval card and the settings panel's ledger
-        #                              ("待处理权限请求"): they ask the same question,
-        #                              so they get the same answer.
+        #                              before the deadline fires. ONE window for every
+        #                              ask, wherever it is answered — the conversation
+        #                              card above the composer (`PermissionDock`) or
+        #                              the Settings page's cross-session mirror
+        #                              ("待处理权限请求"): one question, one answer.
         #                              0 = 不等待: the ask is settled the moment it
-        #                              arrives, nobody is asked (no composer card, no
-        #                              ledger entry). That rung belongs to the
-        #                              `auto` mode ONLY — it ANSWERS the ask, so the
-        #                              agent continues. Under `abort` the same zero
-        #                              would refuse every ask on arrival (the agent
-        #                              stops at every gate), so `abort` starts at the
-        #                              shortest real wait. "Never expires" is NOT
-        #                              this key's business — that is `wait` mode
-        #                              below.
-        #                              When the deadline fires, the ask is
-        #                              settled WHERE IT WAS ASKED — it is not handed to
-        #                              the settings panel. What happens is
-        #                              `permissionTimeoutMode`'s business.
+        #                              arrives, nobody is asked (no conversation card,
+        #                              no pending entry on the Settings page). That
+        #                              rung belongs to the `auto` mode ONLY — it
+        #                              ANSWERS the ask, so the agent continues. Under
+        #                              `abort` the same zero would refuse every ask on
+        #                              arrival (the agent stops at every gate), so
+        #                              `abort` starts at the shortest real wait. "Never
+        #                              expires" is NOT this key's business — that is
+        #                              `wait` mode below.
+        #                              When the deadline fires, the ask is settled IN
+        #                              PLACE: the card goes away and `permission/expired`
+        #                              records the outcome in the conversation. What
+        #                              happens is `permissionTimeoutMode`'s business.
         #                              LEGACY: `nativeApprovalTimeoutMs` and
         #                              `permissionFallbackTimeoutMs` are still accepted
         #                              and folded into this key (this key wins when it