dsh-winrm 0.1.0

package/LICENSE

@@ -0,0 +1,73 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+     (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
+
+     (b) You must cause any modified files to carry prominent notices stating that You changed the files; and
+
+     (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+
+     (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
+
+     You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!)  The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -0,0 +1,112 @@
+# dsh-winrm — Windows 远程管理插件（WinRM / PowerShell Remoting）
+
+[中文文档](README.zh.md) | English
+
+仿照 [dsh-ssh](https://github.com/zhu1090093659/dsh-web-ui/tree/main/packages/dsh-ssh) 开发的 DSH 插件：用 Windows 原生的 **WinRM / PowerShell Remoting** 协议远程管理 Windows 服务器，**目标机不需要装 OpenSSH**。
+
+## 功能
+
+| 面 | 说明 |
+| --- | --- |
+| GUI 侧边栏「Windows」入口 | 居中面板：**主机** / **控制台** / **服务** / **进程** / **传输** 五个页签 |
+| Agent 工具 | `winrm_list` `winrm_exec` `winrm_service` `winrm_process` `winrm_upload` `winrm_download` `winrm_cluster` |
+| PowerShell 控制台 | WebSocket 命令会话（每条命令通过原生 Node WinRM 客户端执行，输出实时返回） |
+| 服务管理 | 列出 / 启动 / 停止 / 重启 / 改启动类型（自动/手动/禁用） |
+| 进程管理 | 列出（CPU/内存/路径）/ 按 PID 结束 |
+| 文件传输 | base64 分块读写，**不依赖 SMB**，任意路径可传；上传自动建目录 |
+| 集群 | 一条命令并发跑多台主机（按 aliases / environment / tags 过滤） |
+
+## 认证与传输
+
+- 使用原生 Node.js WinRM 客户端（[winrm-client](https://github.com/shide1989/winrm-client)），按传输自动选择认证：HTTPS 优先 Basic、HTTP 优先 NTLM，两者均自动回退（HTTP Basic 仅限受信内网，公网必须使用 HTTPS）
+- 本地账户可写 `Administrator`；域账户可写 `DOMAIN\user` 或 `user@domain`
+- 本机无需 Python —— WinRM 走纯 Node 依赖（winrm-client），随插件一起安装
+- 传输：HTTP(5985) 或 HTTPS(5986)；HTTPS 可勾选「接受自签名证书」
+- 中文输出不乱码：所有命令走 **UTF-8 base64 信封**（`-EncodedCommand` + `Out-String` 包装），绕过 WinRM 传输的代码页问题
+- 命令结果的 `stderr` 已自动剥离 PowerShell 的 CLIXML 宿主机记录；真实的进程级 stderr（如 `[Console]::Error`）原样保留
+
+## 目标机准备（一次性）
+
+在要管理的 Windows 机器上，**以管理员身份**运行：
+
+```powershell
+powershell -ExecutionPolicy Bypass -File .\scripts\enable-winrm.ps1
+```
+
+脚本自动：启用 WinRM 服务与 5985 监听 → 开放 Basic/Negotiate 认证 → 允许 HTTP 明文（内网）→ WinRS 内存上限 512MB → 放行防火墙 → 打印本机 IP。
+
+> ⚠️ **安全**：HTTP + Basic 是明文，仅限受信内网；公网请配置 HTTPS + 自签名证书，并在插件里勾选「接受自签名证书」。密码明文存于本机 `~/.dsh/dsh-winrm.json`（0600 权限，仅当前用户可读），插件界面永不回显。
+
+## 安装
+
+> 需要 DeepSeek Harness **0.1.7 系列**（`0.1.7-alpha.2` 及以后，含 `0.1.7-rc.1`）。插件的 `peerDependencies` 声明为 `^0.1.7-alpha.2`，DSH 启动时会据此校验：0.1.x 各版本可加载，`0.2.0` 起会被拒绝（确需冒险可用 `dsh plugin allow-version` 逐版本放行）。
+
+从 [Releases](https://github.com/MoRanYue/dsh-winrm/releases) 下载最新的 `dsh-winrm-*.tgz`，加入 profile：
+
+```powershell
+dsh plugin --profile web add D:\downloads\dsh-winrm-0.1.0.tgz
+```
+
+也可以直接从 npm 安装：
+
+```powershell
+dsh plugin --profile web add dsh-winrm
+```
+
+本地开发可用 profile 链接安装：
+
+```bash
+dsh plugin --profile web add link:D:\项目\dsh-winrm
+```
+
+安装后 **重启 dsh web**（退出再启动 `dsh web`）使插件生效。侧边栏出现「Windows」入口；对话中可直接用 `winrm_list` 等工具。
+
+### 从源码构建
+
+```bash
+cd D:\项目\dsh-winrm
+pnpm install
+npm run build     # tsc 声明 + tsdown 宿主/客户端打包 + postbuild 包装
+```
+
+## 使用示例（agent 工具）
+
+```
+winrm_list                                        # 列出已配置主机
+winrm_exec  alias=web1 command="Get-Service | Select -First 5 | Format-Table"
+winrm_service alias=web1 name=W3SVC action=restart
+winrm_process alias=web1 action=list
+winrm_process alias=web1 id=1234 action=kill
+winrm_upload alias=web1 localPath=D:\a.zip remotePath=C:\temp\a.zip
+winrm_download alias=web1 remotePath=C:\logs\app.log localPath=D:\app.log
+winrm_cluster command="Get-Date" tags=prod
+```
+
+## 架构
+
+```
+src/
+  index.ts            Cordis 插件入口（webServer/tools/systemPrompt 挂载 + 设置面板 + 公告）
+  engine.ts           WinRmEngine 门面：exec / services / processes / ls / upload / download / console / cluster / test
+  store.ts            ~/.dsh/dsh-winrm.json 主机存储（原子写，0600）
+  protocol.ts         宿主↔浏览器 wire 类型
+  powershell.ts       PS 片段构造器（UTF-8 信封 / 服务 / 进程 / 目录 / 分块读写）
+  routes.ts           /api/dsh-winrm 路由族 + 控制台 WebSocket（loopback 围栏）
+  tools.ts            7 个 winrm_* agent 工具
+  engine/client.ts    winrm-client 传输层：进程内认证（NTLM/Basic）、UTF-8 信封、分块传输
+  engine/console.ts   流式 PowerShell 控制台会话
+  client/             浏览器半：侧边栏入口 + 居中面板（5 页签）
+scripts/
+  enable-winrm.ps1    目标机一键启用 WinRM
+  postbuild.mjs       客户端产物 __ModuleLoader__ 包装
+```
+
+传输依赖原生 Node.js 的 [winrm-client](https://github.com/shide1989/winrm-client)（NTLM/Basic，进程内认证）；密码只在宿主进程内使用，不出现在任何子进程命令行参数中。
+
+## 已知限制
+
+- 控制台是命令会话，不保持 PowerShell 变量和当前目录状态；每条命令独立执行
+- WinRM 单次响应受 150KB 信封上限约束，传输按 48KB 分块，大文件较慢（每块一次往返）
+- 单命令默认 60s 超时，可传 `timeoutMs`
+- 目标机需已启用 WinRM（见上）；HTTP 明文 Basic 不应用于公网
+- 面板关闭再打开会回到「主机」页签：面板是 `main` 插槽的占用者，切回对话时卸载，页签状态不跨开关保留

package/README.zh.md

@@ -0,0 +1,119 @@
+# dsh-winrm — Windows 远程管理插件（WinRM / PowerShell Remoting）
+
+仿照 [dsh-ssh](https://github.com/zhu1090093659/dsh-web-ui/tree/main/packages/dsh-ssh) 开发的 DSH 插件：用 Windows 原生的 **WinRM / PowerShell Remoting** 协议远程管理 Windows 服务器，**目标机不需要装 OpenSSH**。
+
+## 功能
+
+| 面 | 说明 |
+| --- | --- |
+| GUI 侧边栏「Windows」入口 | 居中面板：**主机** / **控制台** / **服务** / **进程** / **传输** 五个页签 |
+| Agent 工具 | `winrm_list` `winrm_exec` `winrm_service` `winrm_process` `winrm_upload` `winrm_download` `winrm_cluster` |
+| PowerShell 控制台 | WebSocket 命令会话（每条命令通过原生 Node WinRM 客户端执行，输出实时返回） |
+| 服务管理 | 列出 / 启动 / 停止 / 重启 / 改启动类型（自动/手动/禁用） |
+| 进程管理 | 列出（CPU/内存/路径）/ 按 PID 结束 |
+| 文件传输 | base64 分块读写，**不依赖 SMB**，任意路径可传；上传自动建目录 |
+| 集群 | 一条命令并发跑多台主机（按 aliases / environment / tags 过滤） |
+
+## 认证与传输
+
+- 使用原生 Node.js WinRM 客户端（[winrm-client](https://github.com/shide1989/winrm-client)），按传输自动选择认证：HTTPS 优先 Basic、HTTP 优先 NTLM，两者均自动回退（HTTP Basic 仅限受信内网，公网必须使用 HTTPS）
+- 本地账户可写 `Administrator`；域账户可写 `DOMAIN\\user` 或 `user@domain`
+- 本机无需 Python —— WinRM 走纯 Node 依赖（winrm-client），随插件一起安装
+- 传输：HTTP(5985) 或 HTTPS(5986)；HTTPS 可勾选「接受自签名证书」
+- 中文输出不乱码：所有命令走 **UTF-8 base64 信封**（`-EncodedCommand` + `Out-String` 包装），绕过 WinRM 传输的代码页问题
+- 命令结果的 `stderr` 已自动剥离 PowerShell 的 CLIXML 宿主机记录；真实的进程级 stderr（如 `[Console]::Error`）原样保留
+
+## 目标机准备（一次性）
+
+在要管理的 Windows 机器上，**以管理员身份**运行：
+
+```powershell
+powershell -ExecutionPolicy Bypass -File .\scripts\enable-winrm.ps1
+```
+
+脚本自动：启用 WinRM 服务与 5985 监听 → 开放 Basic/Negotiate 认证 → 允许 HTTP 明文（内网）→ WinRS 内存上限 512MB → 放行防火墙 → 打印本机 IP。
+
+> ⚠️ **安全**：HTTP + Basic 是明文，仅限受信内网；公网请配置 HTTPS + 自签名证书，并在插件里勾选「接受自签名证书」。密码明文存于本机 `~/.dsh/dsh-winrm.json`（0600 权限，仅当前用户可读），插件界面永不回显。
+
+## 截图
+
+![dsh-winrm 截图](docs/screenshots/winrm-panel.png)
+
+
+## 安装
+
+> 需要 DeepSeek Harness **0.1.7 系列**（`0.1.7-alpha.2` 及以后，含 `0.1.7-rc.1`）。插件的 `peerDependencies` 声明为 `^0.1.7-alpha.2`，DSH 启动时会据此校验：0.1.x 各版本可加载，`0.2.0` 起会被拒绝（确需冒险可用 `dsh plugin allow-version` 逐版本放行）。
+
+从 [Releases](https://github.com/MoRanYue/dsh-winrm/releases) 下载最新的 `dsh-winrm-*.tgz`，加入 profile：
+
+```powershell
+dsh plugin --profile web add D:\downloads\dsh-winrm-0.1.0.tgz
+```
+
+也可以直接从 npm 安装：
+
+```powershell
+dsh plugin --profile web add dsh-winrm
+```
+
+本地开发可用 profile 链接安装：
+
+```bash
+dsh plugin --profile web add link:D:\项目\dsh-winrm
+```
+
+安装后 **重启 dsh web**（退出再启动 `dsh web`）使插件生效。侧边栏出现「Windows」入口；对话中可直接用 `winrm_list` 等工具。
+
+### 从源码构建
+
+```bash
+cd D:\项目\dsh-winrm
+pnpm install
+npm run build     # tsc 声明 + tsdown 宿主/客户端打包 + postbuild 包装
+```
+
+## 使用示例（agent 工具）
+
+```
+winrm_list                                        # 列出已配置主机
+winrm_exec  alias=web1 command="Get-Service | Select -First 5 | Format-Table"
+winrm_service alias=web1 name=W3SVC action=restart
+winrm_process alias=web1 action=list
+winrm_process alias=web1 id=1234 action=kill
+winrm_upload alias=web1 localPath=D:\a.zip remotePath=C:\temp\a.zip
+winrm_download alias=web1 remotePath=C:\logs\app.log localPath=D:\app.log
+winrm_cluster command="Get-Date" tags=prod
+```
+
+## 架构
+
+```
+src/
+  index.ts            Cordis 插件入口（webServer/tools/systemPrompt 挂载 + 设置面板 + 公告）
+  engine.ts           WinRmEngine 门面：exec / services / processes / ls / upload / download / console / cluster / test
+  store.ts            ~/.dsh/dsh-winrm.json 主机存储（原子写，0600）
+  protocol.ts         宿主↔浏览器 wire 类型
+  powershell.ts       PS 片段构造器（UTF-8 信封 / 服务 / 进程 / 目录 / 分块读写）
+  routes.ts           /api/dsh-winrm 路由族 + 控制台 WebSocket（loopback 围栏）
+  tools.ts            7 个 winrm_* agent 工具
+  engine/client.ts    winrm-client 传输层：进程内认证（NTLM/Basic）、UTF-8 信封、分块传输
+  engine/console.ts   流式 PowerShell 控制台会话
+  client/             浏览器半：侧边栏入口 + 居中面板（5 页签）
+scripts/
+  enable-winrm.ps1    目标机一键启用 WinRM
+  postbuild.mjs       客户端产物 __ModuleLoader__ 包装
+```
+
+传输依赖原生 Node.js 的 [winrm-client](https://github.com/shide1989/winrm-client)（NTLM/Basic，进程内认证）；密码只在宿主进程内使用，不出现在任何子进程命令行参数中。
+
+## 已知限制
+
+- 控制台是命令会话，不保持 PowerShell 变量和当前目录状态；每条命令独立执行
+- WinRM 单次响应受 150KB 信封上限约束，传输按 48KB 分块，大文件较慢（每块一次往返）
+- 单命令默认 60s 超时，可传 `timeoutMs`
+- 目标机需已启用 WinRM（见上）；HTTP 明文 Basic 不应用于公网
+- 面板关闭再打开会回到「主机」页签：面板是 `main` 插槽的占用者，切回对话时卸载，页签状态不跨开关保留
+
+---
+
+English documentation: see [README.md](README.md).

package/RELEASING.md

@@ -0,0 +1,75 @@
+# Releasing
+
+The package publishes to npm as `dsh-winrm`. Releases are cut by pushing a
+version tag; the [release workflow](.github/workflows/release.yml) then
+publishes that exact commit.
+
+## One-time bootstrap: the first version
+
+**npm cannot publish a package's first version over OIDC.** Trusted publishing
+is configured on the package's page on npmjs.com, and a package that does not
+exist yet has no such page — a chicken-and-egg limit tracked in
+[npm/cli#8544](https://github.com/npm/cli/issues/8544). The first release
+therefore has to be published manually, with a token or `npm login`:
+
+```sh
+npm login          # or export a granular publish token
+npm publish
+```
+
+Verify the result, then finish the setup:
+
+```sh
+npm view dsh-winrm version
+```
+
+Tagging that same commit (`git tag v0.1.0 && git push origin v0.1.0`) is safe:
+the workflow checks the registry first and skips publishing a version that is
+already there, so the bootstrap release does not fail the run.
+
+## One-time bootstrap: authorize this workflow
+
+After the first version exists, open the package on npmjs.com →
+**Settings → Trusted publishing → GitHub Actions** and register:
+
+| Field | Value |
+| --- | --- |
+| Organization or user | `MoRanYue` |
+| Repository | `dsh-winrm` |
+| Workflow filename | `release.yml` |
+| Environment name | *(leave empty)* |
+
+The workflow filename must match exactly, including the `.yml` extension;
+npm does not validate the entry when it is saved, so a typo only shows up as an
+`ENEEDAUTH` failure on the next release.
+
+Once trusted publishing works, consider restricting token-based publishing
+(Settings → Publishing access) and revoking unused automation tokens.
+
+## Cutting a release
+
+1. Update `version` in `package.json` and add a matching `CHANGELOG.md` entry.
+2. Run the checks locally:
+
+   ```sh
+   pnpm install
+   npm run check     # typecheck + build + tests
+   ```
+
+3. Commit, then tag and push:
+
+   ```sh
+   git tag v0.1.1
+   git push origin main v0.1.1
+   ```
+
+The workflow rejects a tag whose version does not match `package.json`, and
+`npm publish` runs the `prepack` script, so a revision that fails the checks is
+never published. Provenance attestations are generated automatically: this is
+a public package built from a public repository.
+
+## Manual publish
+
+The workflow is a convenience, not a requirement — a maintainer can always
+publish by hand from a clean checkout (`npm run check && npm publish`). OIDC is
+preferred because it needs no long-lived token in the repository.

package/cordis.patch.yml

@@ -0,0 +1,8 @@
+# dsh-winrm bundle patch: inserts the dual-face plugin row into the web
+# profile roster. The row is a bare plugin by package name: the node half
+# (exports ".") runs in the host process (WinRM engine, /api/dsh-winrm
+# routes, agent tools), and the dsh.client declaration in package.json makes
+# the browser half (exports "./client") load in the web GUI.
+- insert:
+    - id: winrm
+      name: 'dsh-winrm'