dsh-plugin-rea 2.0.1 → 2.0.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.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,12 @@
2
2
 
3
3
  本插件遵循语义化版本。版本号变化说明「配置组合」这层的变化,与 REA 自身的版本无关。
4
4
 
5
+ ## 2.0.2 — 2026-10-15
6
+
7
+ **仅文档,无行为变更。**
8
+
9
+ - 两份 README 的**末尾**(许可证之前)新增一节,说明**什么时候该用 1.x 线**以及它的安装方式
10
+ (`dsh-plugin-rea@1.0.6` 或 `github:czcdr/dsh-plugin-rea#v1.0.6`)—— 此前 1.x 只出现在开头的版本说明与升级章节里。
5
11
  ## 2.0.1 — 2026-10-15
6
12
 
7
13
  **仅文档与版式,无行为变更。**
package/README.md CHANGED
@@ -248,6 +248,22 @@ back on the next start.
248
248
 
249
249
  `check-updates.ps1` (Windows PowerShell) reports the state of all of these at once.
250
250
 
251
+ ## Still prefer the configuration-only 1.x line?
252
+
253
+ 1.x is the adapter **without** provisioning: one row that launches `rea mcp` from PATH and expects Ghidra to be
254
+ installed by you. It is the right choice when you already manage REA and Ghidra yourself, when you do not want
255
+ the plugin fetching anything, or when you want the row to keep pointing at your own `rea` binary:
256
+
257
+ ```
258
+ dsh plugin --profile <profile> add dsh-plugin-rea@1.0.6
259
+ # or pin the branch instead of the version:
260
+ dsh plugin --profile <profile> add github:czcdr/dsh-plugin-rea#v1.0.6
261
+ ```
262
+
263
+ Both lines publish the same patch shape and the same `mcp__rea__*` surface. 1.x is maintained on the
264
+ [`v1` branch](https://github.com/czcdr/dsh-plugin-rea/tree/v1), where its own install notes live (Node on REA's
265
+ engines, `npm i -g rea-agents`, Ghidra 12.1.x for native analysis).
266
+
251
267
  ## License
252
268
 
253
269
  MIT (this adapter). REA is MIT and owned by its authors; Ghidra is Apache-2.0 and owned by the NSA; Temurin
package/README.zh-CN.md CHANGED
@@ -233,6 +233,21 @@ node scripts/setup.mjs # 或:powershell -File scripts\rea-bundle-boot
233
233
 
234
234
  `check-updates.ps1`(Windows PowerShell)会一次性报告以上各项的状态。
235
235
 
236
+ ## 还想用纯配置的 1.x 线?
237
+
238
+ 1.x 是**不带供给**的适配器:一行配置,从 PATH 上启动 `rea mcp`,并假设 Ghidra 由你自己装好。这些情况它是更合适的选择 ——
239
+ 你已经自己管理 REA 与 Ghidra、不希望插件去下载任何东西、或者想让那一行继续指向你自己的 `rea`:
240
+
241
+ ```
242
+ dsh plugin --profile <profile> add dsh-plugin-rea@1.0.6
243
+ # 或钉住分支而不是版本号:
244
+ dsh plugin --profile <profile> add github:czcdr/dsh-plugin-rea#v1.0.6
245
+ ```
246
+
247
+ 两条线发布的 patch 形态与 `mcp__rea__*` 工具面完全相同。1.x 维护在
248
+ [`v1` 分支](https://github.com/czcdr/dsh-plugin-rea/tree/v1),它自己的安装说明也在那里(Node 满足 REA engines、
249
+ `npm i -g rea-agents`、原生分析需要 Ghidra 12.1.x)。
250
+
236
251
  ## 许可证
237
252
 
238
253
  MIT(本适配器)。REA 是 MIT、归其作者;Ghidra 是 Apache-2.0、归 NSA;Temurin 是 GPLv2+CE;Node.js 是
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dsh-plugin-rea",
3
- "version": "2.0.1",
3
+ "version": "2.0.2",
4
4
  "description": "One-plugin bundle: provisions Node/REA/JDK/Ghidra for you, then registers the upstream REA MCP server as mcp__rea__* tools. · 一体包:自动准备 Node/REA/JDK/Ghidra,并把上游 REA 的 MCP 服务接入 DeepSeek Harness。",
5
5
  "type": "module",
6
6
  "license": "MIT",