dsh-ntr 0.1.3 → 0.1.5

package/README.en.md

@@ -22,7 +22,11 @@ In one sentence: your host agent acts as an ACP client, negotiates capabilities
 
 This plugin is a DSH **bundle**: `package.json`'s `dsh.bundle.patch` declares the two patches shipped with the package — the plugin's own `cordis.patch.yml`, and the NTR-mode preset at `presets/acp/acp.patch.yml`. After `dsh plugin` installs it, the package joins the profile's `dsh.profile.bundles` and the patch layers take effect **automatically** — no config file needs editing by hand.
 
-### Option 1: from the npm registry
+### Option 1: from the official UI
+
+Open the **Plugins** page in DSH's sidebar, click **Add plugin**, enter `dsh-ntr`, and click install. Refresh the page and it's ready to use.
+
+### Option 2: from the npm registry
 
 ```bash
 dsh plugin --profile web add dsh-ntr@latest
@@ -32,7 +36,7 @@ Run the same command again to upgrade.
 
 > **Always pass `@latest`**: without it the package manager keeps reusing the version it wrote the first time, and `update` won't get you off it afterwards.
 
-### Option 2: via the [dsh-market](https://github.com/dsh-market/dsh-market) plugin market
+### Option 3: via the [dsh-market](https://github.com/dsh-market/dsh-market) plugin market
 
 First install the market itself:
 
@@ -42,9 +46,9 @@ dsh plugin --profile web add dshmarket
 
 Restart `dsh web` and open the **Plugins** page: on dsh 0.2.1+ the market is the **Plugin Market** tab next to **Installed**; on older hosts it lives under **Settings → Plugin Market**. Search for `dsh-ntr`, confirm the source, and install in one click — refresh the page and it's live; update checks and upgrades afterwards also happen in the market. The official DSH Desktop app ships with this market preset, so just search and install from the app's **Plugins** page.
 
-> The market's catalog comes from the curated [awesome-dsh-plugin](https://awesome-dsh-plugin.com) registry and refreshes daily. If `dsh-ntr` doesn't show up in search yet, install it from npm with Option 1 — nothing is lost.
+> The market's catalog comes from the curated [awesome-dsh-plugin](https://awesome-dsh-plugin.com) registry and refreshes daily. If `dsh-ntr` doesn't show up in search yet, install it from npm with Option 2 — nothing is lost.
 
-### Option 3: from source
+### Option 4: from source
 
 Requires Node.js ≥ 22.12.0.
 
@@ -236,7 +240,26 @@ Mount it in your profile's `cordis.patch.yml`. When `cwd` / `allowedCwdRoots` ar
         allowedCwdRoots: [~/.dsh/dsh-ntr/workspaces]
 ```
 
-Optional agent fields: `npmPackage` (auto `npm install -g` when not found on PATH), `exposedModels` (which variants the NTR seat menu lists), `idleTimeoutMs` (idle-release window for chat processes; `0` = never release, default 30 minutes). Plugin-level there are also `transcriptMaxEntries` (per-conversation event buffer cap, default 600) and `probeModelsOnBoot` (kept for compatibility; boot-time per-agent probing no longer happens — see the comment on `bootstrapCatalogs`). Reliability timeouts and retries (`startupTimeoutMs`, `cancelFallbackMs`, `staleCancelRetryDelayMs`, `staleCancelMaxRetries`, `permissionTimeoutMs`, `permissionFallbackTimeoutMs`) are covered by [AGENTS.md](./AGENTS.md) constraints 12 and 13; anything editable in the Settings page should be edited there.
+Optional agent fields: `npmPackage` (auto `npm install -g` when not found on PATH), `exposedModels` (which variants the NTR seat menu lists), `idleTimeoutMs` (idle-release window for chat processes; `0` = never release, default 30 minutes), `mcpServers` (extra MCP servers handed to the agent). Plugin-level there are also `transcriptMaxEntries` (per-conversation event buffer cap, default 600) and `probeModelsOnBoot` (kept for compatibility; boot-time per-agent probing no longer happens — see the comment on `bootstrapCatalogs`). Reliability timeouts and retries (`startupTimeoutMs`, `cancelFallbackMs`, `staleCancelRetryDelayMs`, `staleCancelMaxRetries`, `permissionTimeoutMs`, `permissionFallbackTimeoutMs`) are covered by [AGENTS.md](./AGENTS.md) constraints 12 and 13; anything editable in the Settings page should be edited there.
+
+`mcpServers` uses the plugin's OWN shape (every entry carries a `name` and a `transport`), not the ACP wire shape — the wire's stdio entry has no `type`, and an entry written in the wire shape is silently dropped by the agent:
+
+```yaml
+      - id: pi
+        command: pi-acp
+        mcpServers:
+          - name: codegraph
+            transport: stdio          # stdio needs command; http / sse need url
+            command: /opt/bin/codegraph
+            args: ["serve", "--mcp"]
+            env: { CODEGRAPH_INDEX: /srv/index }
+          - name: remote
+            transport: http
+            url: https://mcp.example.com/mcp
+            headers: { Authorization: "Bearer …" }
+```
+
+These servers are handed to the agent when a session is created; the agent launches and uses them itself. The MCP servers the agent configures for itself are unaffected — this only adds more.
 
 ### Build & install
 

package/README.md

@@ -22,7 +22,11 @@
 
 本插件是一个 DSH **bundle**：`package.json` 的 `dsh.bundle.patch` 声明了随包分发的两层补丁——插件本体的 `cordis.patch.yml`，与 NTR 模式 preset 的 `presets/acp/acp.patch.yml`。用 `dsh plugin` 安装后，包会加入 profile 的 `dsh.profile.bundles`，补丁层**自动生效**，无需手动编辑任何配置文件。
 
-### 方式一：从 npm registry 安装
+### 方式一：从官方界面安装
+
+打开 DSH 侧边栏的**插件**页，点**添加插件**，输入 `dsh-ntr`，点安装。装完刷新页面即可使用。
+
+### 方式二：从 npm registry 安装
 
 ```bash
 dsh plugin --profile web add dsh-ntr@latest
@@ -32,7 +36,7 @@ dsh plugin --profile web add dsh-ntr@latest
 
 > `add` 时**务必带 `@latest`**：不带的话包管理器会一直复用首次写入的版本号，之后连 `update` 也升不上去。
 
-### 方式二：经 [dsh-market](https://github.com/dsh-market/dsh-market) 插件市场安装
+### 方式三：经 [dsh-market](https://github.com/dsh-market/dsh-market) 插件市场安装
 
 先装市场本体：
 
@@ -42,9 +46,9 @@ dsh plugin --profile web add dshmarket
 
 重启 `dsh web`，打开**插件**页：dsh 0.2.1 起市场是「已安装」旁边的**插件市场**标签页；更早的版本在**设置 → 插件市场**。搜索 `dsh-ntr`，确认来源后一键安装，装完刷新页面即可使用；之后的更新检查与升级也在市场里完成。官方 DSH 桌面 App 自带这个市场，直接在 App 的**插件**页里搜索安装即可。
 
-> 市场的插件清单来自 [awesome-dsh-plugin](https://awesome-dsh-plugin.com) 精选目录，每天自动刷新。若搜索结果里暂时没有 `dsh-ntr`，用方式一从 npm 安装，不影响使用。
+> 市场的插件清单来自 [awesome-dsh-plugin](https://awesome-dsh-plugin.com) 精选目录，每天自动刷新。若搜索结果里暂时没有 `dsh-ntr`，用方式二从 npm 安装，不影响使用。
 
-### 方式三：从源码安装
+### 方式四：从源码安装
 
 需要 Node.js ≥ 22.12.0。
 
@@ -236,7 +240,26 @@ agent 要动敏感的东西时会问你。审批卡直接出现在聊天输入
         allowedCwdRoots: [~/.dsh/dsh-ntr/workspaces]
 ```
 
-可选的 agent 字段：`npmPackage`（PATH 里找不到时自动 `npm install -g`）、`exposedModels`（NTR 座位菜单列哪些变体）、`idleTimeoutMs`（聊天进程的空闲释放窗口，`0` = 永不释放，默认 30 分钟）。插件级还有 `transcriptMaxEntries`（会话事件缓冲上限，默认 600）与 `probeModelsOnBoot`（保留字段，启动时已不再为每个 agent 探测，见 `bootstrapCatalogs` 的注释）。可靠性超时与重试的默认值（`startupTimeoutMs`、`cancelFallbackMs`、`staleCancelRetryDelayMs`、`staleCancelMaxRetries`、`permissionTimeoutMs` 与 `permissionFallbackTimeoutMs`）见 [AGENTS.md](./AGENTS.md) 约束 12 与 13；设置页能改的都在设置页改。
+可选的 agent 字段：`npmPackage`（PATH 里找不到时自动 `npm install -g`）、`exposedModels`（NTR 座位菜单列哪些变体）、`idleTimeoutMs`（聊天进程的空闲释放窗口，`0` = 永不释放，默认 30 分钟）、`mcpServers`（额外交给 agent 连接的 MCP 服务器）。插件级还有 `transcriptMaxEntries`（会话事件缓冲上限，默认 600）与 `probeModelsOnBoot`（保留字段，启动时已不再为每个 agent 探测，见 `bootstrapCatalogs` 的注释）。可靠性超时与重试的默认值（`startupTimeoutMs`、`cancelFallbackMs`、`staleCancelRetryDelayMs`、`staleCancelMaxRetries`、`permissionTimeoutMs` 与 `permissionFallbackTimeoutMs`）见 [AGENTS.md](./AGENTS.md) 约束 12 与 13；设置页能改的都在设置页改。
+
+`mcpServers` 是**插件自己的形状**（每条必带 `name` 与 `transport`），不是 ACP 线格式——线格式里 stdio 那条不带 `type`，照线格式手写会被 agent 静默丢弃：
+
+```yaml
+      - id: pi
+        command: pi-acp
+        mcpServers:
+          - name: codegraph
+            transport: stdio          # stdio 需 command；http / sse 需 url
+            command: /opt/bin/codegraph
+            args: ["serve", "--mcp"]
+            env: { CODEGRAPH_INDEX: /srv/index }
+          - name: remote
+            transport: http
+            url: https://mcp.example.com/mcp
+            headers: { Authorization: "Bearer …" }
+```
+
+这些服务器在**建会话时**交给 agent，由 agent 自己拉起并使用；agent 自己配置的 MCP 服务器不受影响，这里只是额外追加。
 
 ### 构建与安装
 

package/cordis.patch.yml

@@ -34,6 +34,29 @@
         #                                DEGRADED native route the turn still ends, after
         #                                `permissionFallbackTimeoutMs` (default 300000) —
         #                                see `LedgerFallbackReason`.
+        # nativeApprovalTimeoutMs: 300000
+        #                              How long the native approval route (the composer
+        #                              takeover) may stay unanswered before the ask is
+        #                              WITHDRAWN and re-asked on the settings ledger. 0 waits
+        #                              for the host forever. Default matches
+        #                              `permissionFallbackTimeoutMs`: one window for "this
+        #                              route is not working", not two. Raise it if a
+        #                              deployment's users routinely deliberate for minutes
+        #                              before answering (withdrawing only relocates the
+        #                              question to Settings — it never answers for them).
+        # permissionFallbackTimeoutMs: 300000
+        #                              Deadline for a DEGRADED ask (`unavailable`, or
+        #                              `native-timeout` after the withdrawal above): past it
+        #                              the ask is answered `cancelled` instead of hanging the
+        #                              turn. 0 disables even this. `permissionTimeoutMs > 0`
+        #                              governs every path alike and overrides both.
+        #                              `nativeApprovalTimeoutMs` and
+        #                              `permissionFallbackTimeoutMs` are ALSO editable at
+        #                              runtime (NTR 设置 → 审批时限). The card's value is
+        #                              persisted in the plugin's own state file and OUTRANKS
+        #                              this file; the card shows what this file asked for and
+        #                              offers a reset back to it. Only `permissionTimeoutMs`
+        #                              stays config-file-only, as the override of both.
         # cancelFallbackMs: 15000    # force-finalize a turn the agent ignores after session/cancel (0 = off)
         # staleCancelRetryDelayMs: 600  # resend a prompt answered cancelled with no cancel requested (0 = at once)
         # staleCancelMaxRetries: 2      # cap on those resends before the cancelled stop is reported as-is
@@ -70,3 +93,12 @@
         #                                #   shows as connected) is released after
         #                                #   `probeIdleTimeoutMs` (5 min) whatever this
         #                                #   says, 0 included.
+        #     mcpServers:                # extra MCP servers handed to the agent at
+        #       - name: codegraph        #   session setup (the agent starts them
+        #         transport: stdio       #   itself). The plugin's OWN shape: every
+        #         command: /opt/bin/codegraph   #   entry carries a name and a transport.
+        #         args: [serve, --mcp]    #   `stdio` needs command, `http`/`sse` need
+        #         env: { KEY: value }    #   url. NOT the ACP wire shape, whose stdio
+        #                                #   variant has no `type` field (an entry
+        #                                #   written that way is silently dropped by
+        #                                #   the agent).