dsh-plugin-rea 0.0.0-stage → 1.0.5

package/CHANGELOG.md

@@ -0,0 +1,86 @@
+# Changelog
+
+本插件遵循语义化版本。版本号变化说明「配置组合」这层的变化，与 REA 自身的版本无关。
+
+## 1.0.5 — 2026-10-13
+
+把 1.0.4 留下的形状问题收尾，并让承诺过的 CI 真正跑在仓库上。
+
+- **CI 首次真正进仓库**：1.0.4 的 CHANGELOG 与 README 都写了 `validate.yml` / `release.yml`，
+  但 `.github/` 当时没有提交，GitHub 上 `actions/workflows` 是空的——现已推送并在 push 上跑通。
+- **校验范围扩到示例**：机器路径检查从只查 `cordis.patch.yml` 扩到 `examples/*.yml`（读者会照抄的文件）；
+  新增一步断言 npm 包必须带齐 `screenshots.json`、`assets/`、`examples/`——`files[]` 的回归守卫。
+- **`examples/cordis.patch.with-env.yml` 不再提供可照抄的假路径**：原来的 `C:\tools\...` 是编造值，
+  现改为 `<your Ghidra 12.1.x extraction directory>`，并补上 `!!js process.env.GHIDRA_INSTALL_DIR`
+  这一「安装者零改配置」的写法（entry-list dialect 支持 `!!js`；引擎变量本来就会被 MCP 子进程继承）。
+- **`check-updates.ps1` 加固**：`Test-NodeEngines` 去掉会先于函数体抛异常的类型约束；
+  两个 registry 都查不通时不再静默跳过版本比对；`rea` 优先解析 `rea.cmd`（与发布行的
+  `cmd.exe /c rea` 对齐，此前 `Get-Command rea` 会先命中 `.ps1` 垫片）；`rea doctor` 非零退出码会提示。
+- **`assets/make-screenshots.ps1` 补 BOM**：该文件自己的注释要求 UTF-8 with BOM，此前漏做。
+- **`package.json` description 真正缩短**：239 → 约 186 字符（1.0.4 只是改写，仍会被 npm 列表页截断）。
+- **文档口径修正**：README 的 harness 版本拆成「桌面运行时 / 自带 dsh CLI」两个口径；
+  投稿条目注释里的 Release 版本改为当前值。
+
+## 1.0.4 — 2026-10-13
+
+按外部评审修订：发布物不再携带任何机器相关路径。
+
+- **发布用的那一行改为可移植**：Windows 用 `cmd.exe /c rea mcp`（走 PATH），macOS/Linux 用
+  `command: rea` + `args: ['mcp']`；`cordis.patch.yml` 里**不再出现** `D:\...` 之类的绝对路径。
+- **新增 `examples/`**：`cordis.patch.posix.yml`（POSIX 变体）、`cordis.patch.with-env.yml`（需要为
+  MCP 子进程固定引擎环境时的写法）。
+- **机器相关值改放本机 profile 覆盖**（`id: mcp-rea` 的 id-targeted config override）。README 两个
+  语言版本都补了这一工作流；profile 覆盖永不随插件发布。
+- **`check-updates.ps1` 重写**：Node engines 判断改为按 `^`/`~`/`>=` 逐项匹配（此前 Node 26+ 会误报，
+  且 `[version]'6.5.0-rc.1'` 会抛异常）；node/rea/npm 不在 PATH 时有降级路径；profile 结构访问加防御；
+  识别本机 profile 是否覆盖了 `mcp-rea`。
+- **`files` 白名单补齐** `screenshots.json`、`assets/`、`examples/`（npm 包里也带上展示图与示例）。
+- **`package.json` description 缩短**（npm 列表页会截断长描述）。
+- **新增 CI**：`.github/workflows/validate.yml` 校验 manifest/JSON/YAML，并**守住"发布物不得含机器
+  绝对路径"**这条约束；`.github/workflows/release.yml` 在发 Release 时自动打包成版本无关资产名并上传，
+  另含（默认关闭的）npm Trusted Publishing 发布任务。
+- **README 顶部去掉 awesome 徽章**：本插件尚未被该列表收录，收录后再加回。
+
+## 1.0.3 — 2026-10-12
+
+仓库展示与发布范围调整，无行为变更。
+
+- 新增 `assets/screenshot-1.png`、`assets/screenshot-2.png` 与 `screenshots.json`（市场详情页展示用，
+  由 `assets/make-screenshots.ps1` 可复现生成）。
+- 维护记录改为**仅本机保留**：本机维护记录 `docs/project-notes.md` 既不进仓库也不进 tarball；
+  投稿条目 `docs/marketplace-entry.yml` 留在仓库里，但不进 npm 包。
+
+## 1.0.2 — 2026-10-12
+
+文档补强，无行为变更。
+
+- 新增「能做什么、不能做什么」：明确**无法完整还原源代码**——上游原生分析返回的是伪代码与汇编、
+  APK 返回反编译的方法、JEB 返回伪代码，均非原始源码，且不保证文本等价或可直接编译；
+  变量名/类型/注释/宏、优化与去符号、混淆加壳等因素都会降低可读性。
+- 更新章节措辞按实际安装来源区分：从插件市场安装的在**市场里更新**，本地 `file:` 目录方式则覆盖后重装。
+
+## 1.0.1 — 2026-10-12
+
+文档与措辞修正，无行为变更。
+
+- 「作用」改为依据上游 REA 自己的说明撰写（含上游列出的可分析目标），明确逆向能力由上游提供、
+  本插件只做配置组合与引擎环境变量隔离。
+- 新增「更新」章节，区分两件独立且都需手动完成的事：**本插件不会自动更新**（有新版时在插件
+  管理器重装），上游 REA 用 `npm i -g rea-agents@latest` 更新。
+
+## 1.0.0 — 2026-10-12
+
+首个版本。
+
+- 新增纯配置型 Cordis bundle：插入一条 `@deepseek-ai/dsh-mcp-client` 记录，注册 `rea mcp`（stdio）。
+- 工具命名沿用官方约定 `mcp__rea__<tool>`；`failOnStartupError: false`，REA 缺失时不阻塞 harness 启动。
+- 新增 `check-updates.ps1`：检查 REA(npm) / Node engines / Ghidra 版本与 doctor 子项 / 插件登记状态。
+- 实测矩阵：REA 6.4.0、DSH 桌面运行时 0.2.0-rc.2、Ghidra 12.1.4、Node 24.21.0、Windows 11 x64。
+
+<!--
+维护提示（发布新版本时）：
+1. 改 package.json 的 version，并在此文件顶部加一节；
+2. 若改动涉及路径/字段，同步更新 README 的「配置」与「上游更新怎么办」；
+3. 若发 Release tarball，资产名保持不带版本号（dsh-plugin-rea.tgz），
+   否则市场里 latest/download 形式的链接会在下次发版后 404。
+-->

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 czcdr
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,256 @@
-# Temporary Holding Version
+# dsh-plugin-rea
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+[![npm version](https://img.shields.io/npm/v/dsh-plugin-rea?style=flat-square&color=cb3837)](https://www.npmjs.com/package/dsh-plugin-rea)
+
+把 **[REA — Reverse Engineer Anything](https://github.com/morluto/rea)** 接入 **DeepSeek Harness (dsh)**：
+一个**纯配置型 Cordis bundle**，复用官方 MCP 客户端插件 `@deepseek-ai/dsh-mcp-client`，
+把本机已安装的 `rea mcp`（stdio）注册成原生工具。装载后模型直接拥有 `mcp__rea__*` 工具。
+
+> **与上游的关系（重要）**
+> 本仓库是**第三方适配封装，不是 REA 项目的组成部分**，也不包含 REA 的任何源码，
+> 更不由 REA 作者维护。它只做一件事：向 dsh 的配置组合里插入一条指向你本机 `rea` 安装的 MCP 服务器记录。
+> - 上游项目：**REA — Reverse Engineer Anything** — <https://github.com/morluto/rea>（MIT）
+> - 上游文档：<https://github.com/morluto/rea#what-you-can-analyze> · [中文](https://github.com/morluto/rea/blob/main/README_zh.md#可以分析什么) · 站点 <https://rea.tools/>
+> - 上游 npm 包：`rea-agents`
+> - 本插件仓库：**<https://github.com/czcdr/dsh-plugin-rea>** · npm：`dsh-plugin-rea`
+> - 问题反馈：REA 本身的问题请提到上游；本插件的问题提到 [本仓库 Issues](https://github.com/czcdr/dsh-plugin-rea/issues)。
+
+---
+
+![dsh-plugin-rea：会话经官方 MCP 客户端行调用本机 rea mcp，再把 Evidence 带回会话](assets/screenshot-1.png)
+
+## English
+
+**What it does.** This plugin performs **no reverse engineering itself**. It connects the upstream REA
+MCP server to DeepSeek Harness, so the tools REA ships become callable in a session as
+`mcp__rea__*`.
+
+In upstream's own words, REA is *"one MCP for reverse engineering across binaries, applications, and
+runtime behavior"* — *"see a feature you like. Understand how it works, down to the binary level."* It
+*connects your agent to tools for inspecting native binaries, JavaScript and Electron apps, .NET
+assemblies, and websites*; analysis runs locally, and results include the evidence and limitations
+behind each conclusion. Native analysis can use an existing Hopper, Ghidra, or IDA installation, and
+static JavaScript analysis needs no native engine.
+
+Upstream's own coverage list (`README.md#what-you-can-analyze`): native binaries — pseudocode,
+assembly, strings, symbols, calls and references; JavaScript/Electron apps — modules, imports, source
+maps, routes, IPC; websites — page structure, scripts, network observations, screenshots; .NET
+assemblies; Android APKs; Android devices over adb; JEB projects; Android resources; firmware;
+packages and assets; process behavior; plus offline ELF layout, EVM bytecode, recorded Linux crashes
+and saved network captures.
+
+**What this plugin adds.** Exactly two things: it registers that MCP server into DSH's tool layer
+under the `mcp__rea__*` names, and it lets the engine environment (`GHIDRA_INSTALL_DIR`, …) be scoped
+to that MCP child process instead of the whole harness.
+
+**What it can and cannot do.** The analysis is upstream's; this section only restates upstream's own
+contract so expectations are right.
+
+- **It cannot recover complete source code.** For native binaries upstream returns *pseudocode and
+  assembly*, for Android APKs *decompiled methods*, for JEB units *pseudocode*, and for
+  JavaScript/Electron *modules and their relations*. Upstream's tool contract states the pseudocode
+  "is decompiler output, not original source and not text-equivalent" to another provider's output.
+- Not recoverable in practice: original identifier names, types, comments, macros and template
+  expansion, build scripts and assets. Optimisation (inlining, reordering), symbol stripping,
+  obfuscation, packing and VM protection only make the output worse.
+- Every result carries **confidence and limitations** (`observed` / `derived` / `inferred`, plus an
+  explicit limitations list). Read them as evidence, never as recovered source.
+- Good for: understanding behaviour, locating an implementation, interoperability and compatible
+  re-implementation, security review, migration reference. To obtain actual source code, use the
+  legitimate route — the upstream repository, vendor authorisation, or the vendor's own SDK.
+
+**Verified against** (author's machine, 2026-10-12/13):
+
+| Component | Version |
+|---|---|
+| REA (`rea-agents`) | **6.4.0** |
+| DeepSeek Harness | desktop runtime **0.2.0-rc.2**, with its bundled dsh CLI 0.1.7-rc.2 |
+| `@deepseek-ai/dsh-mcp-client` (row provider) | bundled by the harness; npm latest `0.0.1-rc.1` |
+| Ghidra | 12.1.4 (REA currently accepts 12.1.x) |
+| Node.js | 24.21.0 (REA engines: `^22.19.0 \|\| ^24.11.0 \|\| >=26.0.0`) |
+| Host | Windows 11 x64 |
+
+The shipped row was exercised live: `list_documents` answered through the `cmd.exe` form, and
+`open_binary` completed with the `ghidra` provider while the engine directory came only from a
+profile-level override.
+
+**Prerequisites.** Node.js (a version REA accepts) and the REA CLI installed globally
+(`npm i -g rea-agents`). For native analysis, Ghidra 12.1.x (Hopper / IDA are alternatives under
+their own licences). Static JavaScript/Electron and .NET analysis need no engine.
+
+**Install.**
+
+```
+dsh plugin --profile <profile> add github:czcdr/dsh-plugin-rea
+# or, from npm:
+dsh plugin --profile <profile> add dsh-plugin-rea
+```
+
+A prebuilt tarball is attached to [Releases](https://github.com/czcdr/dsh-plugin-rea/releases)
+(version-free asset name, so the link keeps resolving).
+
+**Configure — usually nothing.** The shipped row carries **no machine-specific path**:
+
+- Windows: `command: cmd.exe`, `args: ['/c', 'rea', 'mcp']` — the npm shim is a `.cmd`, so a shell is
+  required.
+- macOS/Linux: `command: rea`, `args: ['mcp']` — see
+  [`examples/cordis.patch.posix.yml`](examples/cordis.patch.posix.yml).
+
+The only optional piece is the analysis engine. REA reads `GHIDRA_INSTALL_DIR` from its environment,
+so either:
+
+1. set it as an **OS-level environment variable** and (re)start the harness, or
+2. pin it for the MCP child only — see
+   [`examples/cordis.patch.with-env.yml`](examples/cordis.patch.with-env.yml).
+
+Either way the variable reaches REA without any literal path: the client hands the parent
+environment to the child (minus names that look like secrets), and the patch dialect evaluates
+`!!js` expressions, so `GHIDRA_INSTALL_DIR: !!js process.env.GHIDRA_INSTALL_DIR` also works.
+
+**Keep machine-specific values out of the plugin.** Override the row from your own profile's
+`cordis.patch.yml` (id-targeted config override). That file is machine-local and never published:
+
+```yaml
+- id: mcp-rea
+  config:
+    env:
+      GHIDRA_INSTALL_DIR: '<your Ghidra 12.1.x directory>'
+```
+
+Only one row may use `serverName: rea` in a profile.
+
+**Verify.** Ask for a `mcp__rea__*` call — `binary_session` reports the engine checks
+(`configuration` / `installation` / `headless` / `native_decompiler` / `java`), all of which should be
+`ok: true`. Then `open_binary` a PE, `binary_overview`, and `procedure_pseudo_code`.
+
+**Scope and caveats.** REA exposes 170+ tools at 6.4.0, so every session's tool list grows; the row
+sets `failOnStartupError: false` so a missing REA never blocks harness startup. Some REA tools launch
+processes, write files and access the network — DSH's permission policy applies. Analyse only
+artifacts you are authorized to inspect.
+
+**Updating — two independent things, both manual.**
+
+- **This plugin** never updates itself. Installed from a plugin market? Update it **in that market**.
+  Installed from a local `file:` checkout? Overwrite the directory and install it again. Updating REA
+  below does **not** update this plugin, and updating this plugin does not touch REA.
+- **Upstream REA**: `npm i -g rea-agents@latest`. Its `bin` entry (`scripts/rea.mjs`) is stable across
+  releases, so this needs no change here.
+- **Ghidra** is version-gated by REA (12.1.x today): update REA first, then check that it accepts a
+  newer Ghidra.
+- **DeepSeek Harness**: a harness upgrade may change the MCP client's config schema — inspect the row
+  with `Config.listConfigs name=@deepseek-ai/dsh-mcp-client` and adjust the field names.
+
+`check-updates.ps1` (Windows PowerShell) reports the state of all four at once, and
+`.github/workflows/validate.yml` enforces the bundle's shape — including "the shipped patch must not
+contain a machine-specific path" — in CI.
+
+**License.** MIT (this adapter). REA is MIT and owned by its authors; Ghidra is Apache-2.0 and owned
+by the NSA. No upstream code is redistributed here.
+
+---
+
+## 中文
+
+**作用。** 本插件**自身不做任何逆向分析**。它把上游 REA 的 MCP 服务接入 DeepSeek Harness，
+让 REA 提供的那套工具在会话里变成可直接调用的 `mcp__rea__*`。
+
+按上游自述，REA 是「**通过一个 MCP 服务，逆向分析二进制文件、应用程序和运行时行为**」——
+「看到喜欢的功能，弄清它的工作原理，深入到二进制层面」。它「将智能体连接到分析工具，用于检查
+原生二进制文件、JavaScript 和 Electron 应用、.NET 程序集以及网站」；分析在本机运行，结果包含
+支撑各项结论的证据和相关限制。原生分析可以使用已有的 Hopper、Ghidra 或 IDA，静态 JavaScript 分析
+不需要原生引擎。
+
+上游列出的可分析目标（原文见 [README_zh.md#可以分析什么](https://github.com/morluto/rea/blob/main/README_zh.md#可以分析什么)）：
+原生二进制文件——伪代码、汇编、字符串、符号、调用和引用；JavaScript / Electron——模块、导入、
+source map、路由与 IPC；网站——页面结构、脚本、网络观察结果与截图；.NET 程序集；Android APK；
+Android 设备（adb）；JEB 项目；Android 资源；固件；软件包与资源；进程行为；以及离线 ELF 布局、
+EVM 字节码、已记录的 Linux 崩溃与已保存的网络捕获。
+
+**本插件在此之上只增加两件事**：把该 MCP 服务注册进 DSH 的工具层（工具名 `mcp__rea__*`），
+以及让引擎环境变量（`GHIDRA_INSTALL_DIR` 等）只作用于这个 MCP 子进程，而不是整个 harness。
+
+**能做什么、不能做什么（重要）。** 分析能力由上游提供；这里只复述上游自己的契约，避免预期错位。
+
+- **无法完整还原源代码。** 上游对原生二进制返回的是**伪代码与汇编**，对 Android APK 返回
+  **反编译的方法**，对 JEB 单元返回**伪代码**，对 JavaScript/Electron 返回**模块及其关系**。
+  上游的工具契约明确写着：伪代码是反编译器输出，**不是原始源码**，且与其他提供方的输出
+  **不保证文本等价**。
+- 实践中不可恢复的内容：原始标识符命名、类型、注释、宏与模板展开、构建脚本与资源；
+  优化（内联、指令重排）、去符号（strip）、混淆、加壳与 VM 保护只会让可读性更差。
+- 每条结论都自带**置信度与限制**（`observed` / `derived` / `inferred`，另有 limitations 列表）：
+  请把它们当作证据使用，而不要当作"已还原的源码"。
+- 适合做：理解行为、定位实现、互操作与兼容实现、安全审计、迁移参考。
+  **要拿到真正的源码，请走正规渠道**——上游代码仓库、厂商授权，或厂商自己的 SDK。
+
+**已验证版本**（作者机器，2026-10-12/13）：REA `6.4.0`、DeepSeek Harness 桌面运行时 `0.2.0-rc.2`
+（自带 dsh CLI `0.1.7-rc.2`）、Ghidra `12.1.4`、Node `24.21.0`、Windows 11 x64。行提供方
+`@deepseek-ai/dsh-mcp-client` 由 harness 自带（npm 最新 `0.0.1-rc.1`）。发布用的这一行**实测跑通过**：
+`list_documents` 在 `cmd.exe` 形式下正常应答，`open_binary` 走 `ghidra` 提供方成功，
+而引擎目录仅来自本机 profile 覆盖。
+
+**前置条件。** 满足 REA 要求的 Node；全局安装 REA（`npm i -g rea-agents`）。原生分析需要
+Ghidra 12.1.x（Hopper / IDA 为替代方案，各自需授权）；静态 JavaScript/Electron 与 .NET 分析
+不需要引擎。
+
+**安装。**
+
+```
+dsh plugin --profile <profile> add github:czcdr/dsh-plugin-rea
+# 或从 npm 安装：
+dsh plugin --profile <profile> add dsh-plugin-rea
+```
+
+[Releases](https://github.com/czcdr/dsh-plugin-rea/releases) 附带预构建 tarball（资产名不带版本号，
+链接不会失效）。
+
+**配置——通常什么都不用改。** 发布出去的那一行**不含任何机器相关路径**：
+
+- Windows：`command: cmd.exe`、`args: ['/c', 'rea', 'mcp']` —— npm 的 shim 是 `.cmd`，必须经 shell。
+- macOS/Linux：`command: rea`、`args: ['mcp']` —— 见
+  [`examples/cordis.patch.posix.yml`](examples/cordis.patch.posix.yml)。
+
+唯一可选的是分析引擎。REA 从环境读取 `GHIDRA_INSTALL_DIR`，二选一：
+
+1. 设为**系统级环境变量**，然后重启 harness（让 MCP 子进程继承）；
+2. 只为这个 MCP 子进程指定 —— 见
+   [`examples/cordis.patch.with-env.yml`](examples/cordis.patch.with-env.yml)。
+
+两种方式都不需要在插件里写死路径：客户端会把父进程环境传给子进程（只剔除名字像密钥的变量），
+而补丁方言支持 `!!js` 表达式，所以 `GHIDRA_INSTALL_DIR: !!js process.env.GHIDRA_INSTALL_DIR`
+同样可用。
+
+**机器相关值不要写进插件。** 用你自己的 profile `cordis.patch.yml` **按 id 覆盖**这一行即可；
+该文件只在你本机、永不随插件发布：
+
+```yaml
+- id: mcp-rea
+  config:
+    env:
+      GHIDRA_INSTALL_DIR: '<你的 Ghidra 12.1.x 目录>'
+```
+
+同一 profile 内 `serverName: rea` 只能有一条记录。
+
+**验证。** 调用任一 `mcp__rea__*` 工具：`binary_session` 会给出引擎检查项
+（configuration / installation / headless / native_decompiler / java），应全部 `ok: true`；
+随后 `open_binary` 打开一个 PE → `binary_overview` → `procedure_pseudo_code`。
+
+**范围与注意。** REA 在 6.4.0 暴露 170+ 个工具，注入后每个会话的工具列表都会变大；行内设置
+`failOnStartupError: false`，因此 REA 缺失也不会阻塞 harness 启动。部分 REA 工具会启动进程、
+写文件、访问网络，按 DSH 的权限策略执行。请仅分析你已获得授权的目标。
+
+**更新：两件事，且都要手动。**
+
+- **本插件**不会自动更新。**从插件市场安装的，就在市场里更新**；本地 `file:` 目录方式安装的，
+  覆盖目录后在插件管理器里重装。下面更新 REA **不会**更新本插件，反过来也一样。
+- **上游 REA**：用 `npm i -g rea-agents@latest` 更新。它的 `bin` 入口（`scripts/rea.mjs`）
+  跨版本稳定，所以本插件无需改动。
+- **Ghidra**：受 REA 版本门槛限制（当前 12.1.x），先升 REA，再确认它接受新版 Ghidra。
+- **DeepSeek Harness**：升级可能改变 MCP 客户端配置结构，用
+  `Config.listConfigs name=@deepseek-ai/dsh-mcp-client` 看该行 schema 并调整字段名。
+
+`check-updates.ps1`（Windows PowerShell）会把上述四项一次跑完；
+`.github/workflows/validate.yml` 在 CI 里守住 bundle 的形状（含「发布物不得含机器路径」这一条）。
+
+**许可。** 本适配器为 MIT；REA 为 MIT，版权归其作者；Ghidra 为 Apache-2.0，版权归 NSA。
+本仓库不再分发上游代码。

package/assets/make-screenshots.ps1

@@ -0,0 +1,153 @@
+<#
+  生成市场展示图（assets/screenshot-*.png）。
+  可复现：改完文案后重跑本脚本即可，无需设计工具。
+
+  运行方式：
+    Windows PowerShell 5.1 :  powershell -NoProfile -File .\make-screenshots.ps1
+    PowerShell 7 (pwsh)    :  pwsh -NoProfile -File ./make-screenshots.ps1
+  两者都可用；脚本内部用 OutDir 参数，默认写到本文件所在目录。
+
+  注意：Windows PowerShell 5.1 按 ANSI 读取 .ps1，本文件必须保存为 UTF-8 with BOM
+  （用 pwsh 7 编辑则无此限制，但保持 BOM 对两者都安全）。
+#>
+[CmdletBinding()]
+param([string]$OutDir = (Join-Path $PSScriptRoot '.'))
+
+Add-Type -AssemblyName System.Drawing
+
+$W = 1280; $H = 720
+$bg      = [System.Drawing.Color]::FromArgb(255, 248, 250, 252)
+$ink     = [System.Drawing.Color]::FromArgb(255, 15, 23, 42)
+$muted   = [System.Drawing.Color]::FromArgb(255, 100, 116, 139)
+$accent  = [System.Drawing.Color]::FromArgb(255, 37, 99, 235)
+$accent2 = [System.Drawing.Color]::FromArgb(255, 22, 163, 74)
+$warn    = [System.Drawing.Color]::FromArgb(255, 220, 38, 38)
+$line    = [System.Drawing.Color]::FromArgb(255, 203, 213, 225)
+
+$fTitle = New-Object System.Drawing.Font('Microsoft YaHei UI', 30, [System.Drawing.FontStyle]::Bold)
+$fSub   = New-Object System.Drawing.Font('Microsoft YaHei UI', 15)
+$fBox   = New-Object System.Drawing.Font('Microsoft YaHei UI', 15, [System.Drawing.FontStyle]::Bold)
+$fBody  = New-Object System.Drawing.Font('Microsoft YaHei UI', 13)
+$fSmall = New-Object System.Drawing.Font('Microsoft YaHei UI', 11)
+$fChip  = New-Object System.Drawing.Font('Microsoft YaHei UI', 13)
+
+function New-Canvas {
+  $bmp = New-Object System.Drawing.Bitmap $W, $H
+  $g = [System.Drawing.Graphics]::FromImage($bmp)
+  $g.SmoothingMode = [System.Drawing.Drawing2D.SmoothingMode]::AntiAlias
+  $g.TextRenderingHint = [System.Drawing.Text.TextRenderingHint]::ClearTypeGridFit
+  $g.Clear($bg)
+  return @($bmp, $g)
+}
+function Draw-Text($g, $text, $font, $color, $x, $y, $w = 0) {
+  $br = New-Object System.Drawing.SolidBrush $color
+  if ($w -gt 0) { $r = New-Object System.Drawing.RectangleF $x, $y, $w, 400; $g.DrawString($text, $font, $br, $r) }
+  else { $g.DrawString($text, $font, $br, $x, $y) }
+  $br.Dispose()
+}
+function Draw-Box($g, $x, $y, $w, $h, $fill, $border, $radius = 12) {
+  $path = New-Object System.Drawing.Drawing2D.GraphicsPath
+  $d = $radius * 2
+  $path.AddArc($x, $y, $d, $d, 180, 90); $path.AddArc($x + $w - $d, $y, $d, $d, 270, 90)
+  $path.AddArc($x + $w - $d, $y + $h - $d, $d, $d, 0, 90); $path.AddArc($x, $y + $h - $d, $d, $d, 90, 90)
+  $path.CloseFigure()
+  $fb = New-Object System.Drawing.SolidBrush $fill
+  $g.FillPath($fb, $path)
+  $p = New-Object System.Drawing.Pen $border, 1.6
+  $g.DrawPath($p, $path)
+  $fb.Dispose(); $p.Dispose(); $path.Dispose()
+}
+function Draw-Arrow($g, $x1, $y1, $x2, $y2, $color, $width = 2.4) {
+  $p = New-Object System.Drawing.Pen $color, $width
+  $p.CustomEndCap = New-Object System.Drawing.Drawing2D.AdjustableArrowCap 6, 7
+  $g.DrawLine($p, $x1, $y1, $x2, $y2)
+  $p.Dispose()
+}
+function Draw-Line($g, $x1, $y1, $x2, $y2, $color, $width = 2.4) {
+  $p = New-Object System.Drawing.Pen $color, $width
+  $g.DrawLine($p, $x1, $y1, $x2, $y2)
+  $p.Dispose()
+}
+function Save-Png($bmp, $g, $path) { $g.Dispose(); $bmp.Save($path, [System.Drawing.Imaging.ImageFormat]::Png); $bmp.Dispose() }
+
+# ---------------------------------------------------------------- 图 1：插件做了什么
+$r = New-Canvas; $bmp = $r[0]; $g = $r[1]
+Draw-Text $g 'dsh-plugin-rea：把 REA 接入 DeepSeek Harness' $fTitle $ink 60 46
+Draw-Text $g '第三方适配 · 自身不做逆向分析 · 只插入一条 MCP 客户端记录，并把引擎环境变量限制在该子进程内' $fSub $muted 62 98
+
+$rowY = 180; $boxH = 158; $boxW = 250
+Draw-Box $g 60 $rowY $boxW $boxH $([System.Drawing.Color]::White) $line
+Draw-Text $g 'DeepSeek Harness 会话' $fBox $ink 80 ($rowY + 18)
+Draw-Text $g "mcp__rea__* 工具`n（6.4.0 暴露 170+）`n工具随会话注入`n按 DSH 权限策略执行" $fBody $muted 80 ($rowY + 50)
+
+Draw-Box $g 360 $rowY $boxW $boxH $([System.Drawing.Color]::FromArgb(255,239,246,255)) $accent
+Draw-Text $g '官方 MCP 客户端行' $fBox $accent 380 ($rowY + 18)
+Draw-Text $g "@deepseek-ai/dsh-mcp-client`nserverName = rea`ntransport = stdio`ncommand = node" $fBody $muted 380 ($rowY + 50)
+Draw-Text $g '↑ 本插件插入的就是这一行' $fSmall $accent 360 ($rowY + $boxH + 8)
+
+Draw-Box $g 660 $rowY $boxW $boxH $([System.Drawing.Color]::White) $line
+Draw-Text $g 'rea mcp（本机进程）' $fBox $ink 680 ($rowY + 18)
+Draw-Text $g "node …`n  \rea-agents\scripts`n  \rea.mjs  mcp`nenv: GHIDRA_INSTALL_DIR`n      JAVA_HOME（仅此处）" $fBody $muted 680 ($rowY + 50)
+
+Draw-Box $g 960 $rowY $boxW $boxH $([System.Drawing.Color]::FromArgb(255,240,253,244)) $accent2
+Draw-Text $g '分析引擎' $fBox $accent2 980 ($rowY + 18)
+Draw-Text $g "Ghidra 12.1.4（本机已装）`nHopper / IDA（可选，`n各自需授权）`n静态 JS / .NET 无需引擎" $fBody $muted 980 ($rowY + 50)
+
+Draw-Arrow $g 310 ($rowY + 40) 358 ($rowY + 40) $muted
+Draw-Arrow $g 610 ($rowY + 40) 658 ($rowY + 40) $muted
+Draw-Arrow $g 910 ($rowY + 40) 958 ($rowY + 40) $muted
+
+# Evidence 回传：引擎 → 结果框 → 会话（左侧折返）
+Draw-Box $g 360 404 850 84 $([System.Drawing.Color]::FromArgb(255,254,249,195)) $([System.Drawing.Color]::FromArgb(255,202,138,4))
+Draw-Text $g 'Evidence 回到会话（置信度 observed / derived / inferred + 明确的 limitations）' $fBox $ink 380 416
+Draw-Text $g '反编译器输出的是伪代码与汇编 —— 不是原始源码，也不保证文本等价' $fBody $muted 380 448
+Draw-Arrow $g 1085 340 1085 400 $muted
+Draw-Line  $g 358 446 150 446 $muted
+Draw-Arrow $g 150 446 150 342 $muted
+
+Draw-Text $g '上游 REA（MIT）：github.com/morluto/rea      本插件：github.com/czcdr/dsh-plugin-rea' $fSmall $muted 60 620
+Draw-Text $g '实测 REA 6.4.0 + DSH 桌面运行时 0.2.0-rc.2 + Ghidra 12.1.4 + Node 24.21.0（Windows 11 x64，2026-10-12）' $fSmall $muted 60 646
+Draw-Text $g 'Ghidra 为 Apache-2.0（NSA）；REA 为 MIT。本仓库不分发上游代码。' $fSmall $muted 60 672
+Save-Png $bmp $g (Join-Path $OutDir 'screenshot-1.png')
+
+# ---------------------------------------------------------------- 图 2：范围与边界
+$r = New-Canvas; $bmp = $r[0]; $g = $r[1]
+Draw-Text $g '上游 REA 的分析范围（插件原样提供）' $fTitle $ink 60 44
+Draw-Text $g '下列目标类型来自上游 README「可以分析什么」；本插件不改变、不扩展这些能力' $fSub $muted 62 96
+
+$chips = @(
+  '原生二进制：伪代码/汇编/字符串/符号/调用与引用',
+  'JavaScript / Electron：模块、导入、source map、路由、IPC',
+  '.NET 程序集：元数据、CIL、原生依赖声明',
+  '网站：页面结构、脚本、网络观察、截图',
+  'Android APK：清单、类、反编译的方法、引用',
+  'Android 设备：adb 包/进程/日志/截图/文件传输',
+  'JEB 项目：单元、工件摘要、类型与方法伪代码',
+  'Android 资源：解码清单、字符串表、语言区域',
+  '固件：区域、提取结果、转交原生分析',
+  '软件包与资源：清单、摘要、plist、Apple bundle',
+  '进程行为：终端输出、交互、退出、文件系统观察',
+  '离线 ELF 布局：节、段、符号/重定位、防护候选项',
+  'EVM 字节码：分派选择器、字节偏移、可变性',
+  '已记录的 Linux 崩溃：note、线程寄存器、映射候选',
+  '已保存的网络捕获：HAR / mitmproxy 记录'
+)
+$cx = 60; $cy = 146; $cw = 570; $ch = 40; $gap = 8
+for ($i = 0; $i -lt $chips.Count; $i++) {
+  $col = $i % 2; $rowi = [math]::Floor($i / 2)
+  $x = $cx + $col * ($cw + 20); $y = $cy + $rowi * ($ch + $gap)
+  Draw-Box $g $x $y $cw $ch $([System.Drawing.Color]::White) $line 8
+  Draw-Text $g $chips[$i] $fChip $ink ($x + 14) ($y + 9)
+}
+
+$by = $cy + 8 * ($ch + $gap) + 16
+Draw-Box $g 60 $by 1190 92 $([System.Drawing.Color]::FromArgb(255,254,242,242)) $warn
+Draw-Text $g '不能完整还原源代码' $fBox $warn 80 ($by + 10)
+Draw-Text $g '返回的是伪代码/汇编/反编译方法，不是原始源码；标识符、类型、注释、宏与模板、构建脚本与资源多不可恢复；不保证文本等价或可直接编译。' $fBody $ink 80 ($by + 38)
+Draw-Text $g '优化（内联/重排）、strip、混淆、加壳与 VM 保护会让可读性更差。要真正的源码，请走上游仓库、厂商授权或官方 SDK。' $fBody $muted 80 ($by + 60)
+
+Draw-Text $g '上游 REA（MIT）：github.com/morluto/rea      本插件：github.com/czcdr/dsh-plugin-rea' $fSmall $muted 60 686
+Save-Png $bmp $g (Join-Path $OutDir 'screenshot-2.png')
+
+Write-Host "written: $(Join-Path $OutDir 'screenshot-1.png')"
+Write-Host "written: $(Join-Path $OutDir 'screenshot-2.png')"

package/check-updates.ps1

@@ -0,0 +1,222 @@
+<#
+.SYNOPSIS
+  检查 dsh-plugin-rea 整条链路是否需要跟进上游更新。
+
+.DESCRIPTION
+  覆盖 4 类上游：REA(npm) / Node 运行时 / Ghidra 引擎 / DSH 插件登记。
+  只读：不安装、不修改任何配置，只报告现状与建议动作。
+  对 PATH 缺失、profile 结构缺失、预发布版本号均有防御。
+
+.EXAMPLE
+  powershell -NoProfile -File .\check-updates.ps1
+.EXAMPLE
+  powershell -NoProfile -File .\check-updates.ps1 -Registry https://registry.npmjs.org
+.NOTES
+  Windows PowerShell 5.1 按 ANSI 读取 .ps1，本文件必须保存为 UTF-8 with BOM。
+#>
+[CmdletBinding()]
+param(
+  [string]$Registry = 'https://registry.npmmirror.com',
+  [string]$ReaPackageDir,
+  [string]$ProfileDir
+)
+
+$ErrorActionPreference = 'Continue'
+function Head($t) { Write-Host "`n=== $t ===" -ForegroundColor Cyan }
+function Ok($t)   { Write-Host "  [OK]   $t" -ForegroundColor Green }
+function Warn($t) { Write-Host "  [注意] $t" -ForegroundColor Yellow }
+function Bad($t)  { Write-Host "  [动作] $t" -ForegroundColor Red }
+function Info($t) { Write-Host "  $t" -ForegroundColor Gray }
+
+$actions = [System.Collections.Generic.List[string]]::new()
+
+# 只取数字部分，丢掉 -rc.1 / +build 之类的后缀，避免 [version] 转换抛异常
+function Get-NumericVersion([string]$v) {
+  if (-not $v) { return $null }
+  $core = ($v -replace '^v', '') -replace '[-+].*$', ''
+  try { return [version]$core } catch { return $null }
+}
+
+# 判断 Node 版本是否满足 engines 字符串（支持 ^X.Y.Z / ~X.Y.Z / >=X.Y.Z，用 || 分隔）
+# 参数收 string 不收 [version]：类型约束在函数体之前生效，调用方一旦传入
+# 'abc' / '' / 'v24.21.0' 这类值就会抛 ParameterBindingArgumentTransformationException。
+function Test-NodeEngines([string]$node, [string]$engines) {
+  if (-not $engines -or -not $node) { return $null }
+  # 必须用新变量接收：$node 带 [string] 约束，赋 [version] 会被强制转回字符串，
+  # 之后 $node.Major 为 $null，所有 ^ / ~ 分支都会判假（曾因此把 Node 24 判成不满足）。
+  $v = Get-NumericVersion $node
+  if (-not $v) { return $null }
+  foreach ($term in ($engines -split '\|\|')) {
+    $t = $term.Trim()
+    if ($t -match '^\^(\d+\.\d+\.\d+)$') {
+      $base = [version]$Matches[1]
+      if ($v.Major -eq $base.Major -and $v -ge $base) { return $true }
+    } elseif ($t -match '^>=(\d+\.\d+\.\d+)$') {
+      if ($v -ge [version]$Matches[1]) { return $true }
+    } elseif ($t -match '^~(\d+\.\d+\.\d+)$') {
+      $base = [version]$Matches[1]
+      if ($v.Major -eq $base.Major -and $v.Minor -eq $base.Minor -and $v -ge $base) { return $true }
+    }
+  }
+  return $false
+}
+
+# ------------------------------------------------------- 定位 REA 与 profile
+if (-not $ReaPackageDir) {
+  $npmRoot = $null
+  if (Get-Command npm -ErrorAction SilentlyContinue) {
+    try { $npmRoot = (& npm root -g 2>$null | Select-Object -First 1).Trim() } catch { }
+  }
+  $ReaPackageDir = if ($npmRoot) { Join-Path $npmRoot 'rea-agents' } else { Join-Path $env:APPDATA 'npm\node_modules\rea-agents' }
+}
+if (-not $ProfileDir) {
+  if ($env:DSH_PROFILE_DIR) { $ProfileDir = $env:DSH_PROFILE_DIR }
+  else {
+    $profiles = @(Get-ChildItem (Join-Path $env:USERPROFILE '.dsh\profiles') -Directory -ErrorAction SilentlyContinue)
+    $ProfileDir = if ($profiles.Count -gt 0) { $profiles[0].FullName } else { Join-Path $env:USERPROFILE '.dsh\profiles\desktop' }
+  }
+}
+
+# ---------------------------------------------------------------- REA (npm)
+Head 'REA 本体（npm 包 rea-agents）'
+$installed = $null; $engines = $null; $binPath = $null; $reaEntry = $null
+$pkgFile = Join-Path $ReaPackageDir 'package.json'
+if (Test-Path $pkgFile) {
+  try {
+    $pkg = Get-Content $pkgFile -Raw -Encoding UTF8 | ConvertFrom-Json
+    $installed = $pkg.version; $engines = $pkg.engines.node
+    $binPath = ($pkg.bin.PSObject.Properties | Select-Object -First 1).Value
+    if ($binPath) { $reaEntry = Join-Path $ReaPackageDir ($binPath -replace '/', '\') }
+    Ok "本地已安装: $installed"
+    Info "入口(bin): $binPath   ← 插件通过 PATH 上的 rea 调用它，跨版本稳定"
+    if ($engines) { Info "Node 要求: $engines" }
+  } catch { Bad "package.json 解析失败: $($_.Exception.Message)" }
+} else { Bad "找不到 $pkgFile —— REA 全局包丢了？重装: npm i -g rea-agents" }
+
+$latest = $null
+foreach ($r in @($Registry, 'https://registry.npmjs.org')) {
+  if (-not $r) { continue }
+  try { $latest = (Invoke-RestMethod "$r/rea-agents/latest" -TimeoutSec 20).version; Info "最新版本($r): $latest"; break }
+  catch { Warn "查询失败 $r : $($_.Exception.Message)" }
+}
+if ($installed -and $latest) {
+  $vi = Get-NumericVersion $installed; $vl = Get-NumericVersion $latest
+  if ($vi -and $vl -and $vl -gt $vi) {
+    Warn "有新版本：$installed → $latest"
+    $actions.Add("升级上游 REA:  npm i -g rea-agents@$latest    （只更新 REA；本插件不会自动更新——从市场装的在市场里更新，file: 装的覆盖目录后重装）")
+  } elseif ($vi -and $vl -and $vl -eq $vi -and $installed -ne $latest) {
+    Warn "同版本号但通道不同：$installed → $latest（预发布/正式）"
+  } else { Ok '已是最新版本' }
+} else {
+  Warn '未能取到上游最新版本（两个 registry 都查不通？）—— 已跳过版本比对'
+}
+
+# ------------------------------------------------------------- Node 运行时
+Head 'Node 运行时'
+if (Get-Command node -ErrorAction SilentlyContinue) {
+  $nodeRaw = (& node -v 2>$null) -replace '^v', ''
+  $nodeV = Get-NumericVersion $nodeRaw
+  Info "当前 node: $nodeRaw"
+  if ($nodeV -and $engines) {
+    $ok = Test-NodeEngines $nodeV $engines
+    if ($ok -eq $true) { Ok "满足当前 engines（$engines）" }
+    elseif ($ok -eq $false) { Bad "不满足 engines（$engines）—— 请升级 Node；插件侧走 PATH，无需改配置" }
+    else { Warn "无法解析 engines：$engines" }
+  }
+} else {
+  Warn 'node 不在 PATH —— 跳过 Node 检查；若 harness 也看不到它，MCP 服务器将无法启动'
+  $actions.Add('把 node 加入 PATH，或在本机 profile 覆盖里给 mcp-rea 的 command 写绝对路径')
+}
+
+# ------------------------------------------------------------ Ghidra 引擎
+Head 'Ghidra 引擎'
+$gd = [Environment]::GetEnvironmentVariable('GHIDRA_INSTALL_DIR', 'User')
+if (-not $gd) { $gd = $env:GHIDRA_INSTALL_DIR }
+if ($gd -and (Test-Path $gd)) {
+  Ok "GHIDRA_INSTALL_DIR = $gd"
+  $props = Join-Path $gd 'Ghidra\application.properties'
+  if (Test-Path $props) {
+    $v = (Select-String -Path $props -Pattern '^application\.version=' | Select-Object -First 1).Line -replace '^application\.version=', ''
+    Ok "已安装版本: $v"
+    if ($v -notmatch '^12\.1\.') { Bad "REA 当前要求 Ghidra 12.1.x，当前为 $v —— 先确认新版 REA 是否放开版本门槛" }
+  } else { Bad '缺少 Ghidra\application.properties —— 目录不完整' }
+} else {
+  Warn "GHIDRA_INSTALL_DIR 未设置或目录不存在（当前值: $gd）"
+  Info '原生分析会报引擎不可用；静态 JavaScript/Electron 与 .NET 分析不受影响'
+}
+try {
+  $rel = Invoke-RestMethod 'https://api.github.com/repos/NationalSecurityAgency/ghidra/releases/latest' -TimeoutSec 25 -Headers @{ 'User-Agent' = 'rea-check' }
+  Info "Ghidra 官方最新: $($rel.tag_name)  ($($rel.published_at))"
+  if ($rel.tag_name -notmatch 'Ghidra_12\.1') { Warn '官方已有更新；升级前先确认 REA 是否接受该版本' }
+} catch { Warn "GitHub API 查询失败（可跳过）: $($_.Exception.Message)" }
+
+# --------------------------------------------------------- REA 引擎自检
+Head 'REA 引擎自检（rea doctor）'
+$env:GHIDRA_INSTALL_DIR = $gd
+# 优先取 .cmd：发布出去的那一行是 `cmd.exe /c rea mcp`（走 cmd 的 PATHEXT，命中 rea.cmd），
+# 而 PowerShell 的 Get-Command rea 会先命中同目录的 rea.ps1 垫片，两者行为（尤其退出码）并不相同。
+$reaCmd = (Get-Command 'rea.cmd' -ErrorAction SilentlyContinue).Source
+if (-not $reaCmd) { $reaCmd = (Get-Command rea -ErrorAction SilentlyContinue).Source }
+$reaArgs = @()
+if (-not $reaCmd) {
+  if ($reaEntry -and (Test-Path $reaEntry) -and (Get-Command node -ErrorAction SilentlyContinue)) {
+    $reaCmd = 'node'; $reaArgs = @($reaEntry)
+    Warn 'rea 不在 PATH —— 回退到 node <包内入口>'
+  } else { Warn 'rea 与 node 均不可用 —— 跳过引擎自检' }
+}
+if ($reaCmd) {
+  try {
+    $raw = & $reaCmd @reaArgs doctor --format json 2>$null
+    if ($LASTEXITCODE -ne 0) { Warn "rea doctor 退出码 $LASTEXITCODE —— 报告了不健康状态，下面按输出解析" }
+    $doc = ($raw -join "`n") | ConvertFrom-Json
+    $g = @($doc.providerInspections) | Where-Object { $_.id -eq 'ghidra' }
+    if ($g) {
+      if ($g.available) { Ok "ghidra provider 可用，版本 $($g.providerVersion)" }
+      else { Bad 'ghidra provider 不可用 —— 运行 rea doctor 看 remediation' }
+      $fails = @($g.checks | Where-Object { -not $_.ok })
+      if ($fails.Count -eq 0) { Ok '全部子项通过（configuration/installation/headless/native_decompiler/java）' }
+      else { $fails | ForEach-Object { Bad "$($_.name): $($_.detail)" } }
+    }
+    if ($doc.identity.cli_package_version) {
+      $toolCount = $null
+      if ($doc.identity.catalog -and $doc.identity.catalog.counts) { $toolCount = $doc.identity.catalog.counts.mcp_tools }
+      Info "doctor 识别到的 CLI 版本: $($doc.identity.cli_package_version)$(if ($toolCount) { "，MCP 工具数: $toolCount" })"
+    }
+  } catch { Warn "rea doctor 解析失败，请手动运行: rea doctor" }
+}
+
+# ---------------------------------------------------- DSH 插件登记状态
+Head 'DSH 插件登记'
+$profPkg = Join-Path $ProfileDir 'package.json'
+if (Test-Path $profPkg) {
+  try {
+    $p = Get-Content $profPkg -Raw -Encoding UTF8 | ConvertFrom-Json
+    $dep = $null
+    if ($p.PSObject.Properties.Name -contains 'dependencies' -and $p.dependencies) { $dep = $p.dependencies.'dsh-plugin-rea' }
+    $bundles = @()
+    if ($p.PSObject.Properties.Name -contains 'dsh' -and $p.dsh -and $p.dsh.profile -and $p.dsh.profile.bundles) { $bundles = @($p.dsh.profile.bundles) }
+    if ($dep) { Ok "依赖已登记: dsh-plugin-rea = $dep" } else { Bad '依赖未登记 —— 用插件管理器重新安装本插件' }
+    if ($bundles -contains 'dsh-plugin-rea') { Ok '已列入 dsh.profile.bundles（装载层已生效）' }
+    elseif ($bundles.Count -eq 0) { Warn '未读到 dsh.profile.bundles（profile 结构可能不同）' }
+    else { Bad '未列入 bundles —— 插件不会加载' }
+    Info '本插件不会自动更新：从插件市场安装的在市场里更新；本地 file: 目录方式则覆盖目录后在插件管理器里重装'
+    if ($dep -like 'file:*') {
+      $p2 = $dep -replace '^file:', ''
+      if (Test-Path $p2) { Ok "插件目录存在: $p2" } else { Bad "插件目录不存在: $p2 —— 移走目录会加载失败" }
+    }
+  } catch { Warn "profile package.json 解析失败: $($_.Exception.Message)" }
+} else { Warn "找不到 profile: $profPkg" }
+
+$profPatch = Join-Path $ProfileDir 'cordis.patch.yml'
+if (Test-Path $profPatch) {
+  if (Select-String -Path $profPatch -Pattern 'id:\s*mcp-rea' -Quiet) {
+    Info '检测到本机 profile 覆盖了 mcp-rea（机器相关值应放在这里，不随插件发布）'
+  }
+}
+
+# ------------------------------------------------------------------ 汇总
+Head '结论'
+if ($actions.Count -eq 0) { Ok '无需动作：整条链路与上游保持一致' }
+else { $actions | ForEach-Object { Bad $_ } }
+Write-Host ''
+Write-Host '提示：DSH 侧更新（应用升级可能改变 MCP 客户端配置结构）后，请重跑本脚本并调用一次 mcp__rea__binary_session 验证。' -ForegroundColor Gray

package/cordis.patch.yml

@@ -0,0 +1,43 @@
+# dsh-plugin-rea — REA (Reverse Engineer Anything) as native DSH tools
+#
+# Configuration-only bundle: no Host/Client entry files. It inserts one row of
+# the official MCP client plugin and points it at the installed `rea mcp`
+# stdio server; the model then sees mcp__rea__<tool>.
+#
+# ---------------------------------------------------------------------------
+# PORTABLE BY DEFAULT — this file carries no machine-specific path.
+#
+#   Prerequisite: `rea` must be reachable from the PATH the harness sees.
+#                 (`npm i -g rea-agents` puts it there.)
+#
+#   Windows    : command: cmd.exe   args: ['/c', 'rea', 'mcp']   (as below)
+#   macOS/Linux: command: 'rea'     args: ['mcp']
+#                → see examples/cordis.patch.posix.yml
+#
+#   Analysis engines: REA reads GHIDRA_INSTALL_DIR from its environment.
+#     - Option 1 (recommended): set it as an OS-level environment variable,
+#       then start/restart the harness so the MCP child inherits it.
+#     - Option 2: put an `env:` block in the row —
+#       see examples/cordis.patch.with-env.yml.
+#     Without it, native analysis reports the engine as unavailable while every
+#     other REA capability keeps working. Static JavaScript/Electron and .NET
+#     analysis need no engine at all.
+#
+#   Only ONE row may use serverName: rea in a profile. To adapt this bundle for
+#   your machine without touching the upstream file, override `mcp-rea` from
+#   your profile's own cordis.patch.yml (id-targeted config override) — that
+#   file is never published.
+# ---------------------------------------------------------------------------
+
+- insert:
+    - id: mcp-rea
+      name: '@deepseek-ai/dsh-mcp-client'
+      config:
+        serverName: rea
+        transport: stdio
+        command: 'cmd.exe'
+        args:
+          - '/c'
+          - 'rea'
+          - 'mcp'
+        failOnStartupError: false

package/examples/cordis.patch.posix.yml

@@ -0,0 +1,18 @@
+# macOS / Linux variant of the row.
+#
+# `npm i -g rea-agents` installs a `rea` executable on PATH, so no shell wrapper
+# is needed here (on Windows the shim is a .cmd/.ps1 file, which is why the
+# default cordis.patch.yml goes through cmd.exe).
+#
+# Copy the block below into cordis.patch.yml, replacing the Windows row.
+
+- insert:
+    - id: mcp-rea
+      name: '@deepseek-ai/dsh-mcp-client'
+      config:
+        serverName: rea
+        transport: stdio
+        command: 'rea'
+        args:
+          - 'mcp'
+        failOnStartupError: false

package/examples/cordis.patch.with-env.yml

@@ -0,0 +1,42 @@
+# Windows variant that also pins the analysis-engine environment for the MCP child.
+#
+# Use this when GHIDRA_INSTALL_DIR is NOT set as an OS-level environment variable
+# the harness can inherit — for example after setting it up just now, without
+# restarting the harness.
+#
+# The value below is a placeholder in angle brackets, not a real directory:
+# replace it with your own, or use the `!!js` form to read the variable the
+# harness already has. REA reads only GHIDRA_INSTALL_DIR; `java` comes from PATH
+# or JAVA_HOME.
+#
+# Copy the block into cordis.patch.yml, or — better — keep it out of the plugin
+# entirely and override the row from your profile's own cordis.patch.yml:
+#
+#   - id: mcp-rea
+#     config:
+#       env:
+#         GHIDRA_INSTALL_DIR: '<your Ghidra directory>'
+#
+# A profile-level override is machine-local and is never published.
+
+- insert:
+    - id: mcp-rea
+      name: '@deepseek-ai/dsh-mcp-client'
+      config:
+        serverName: rea
+        transport: stdio
+        command: 'cmd.exe'
+        args:
+          - '/c'
+          - 'rea'
+          - 'mcp'
+        env:
+          # Replace with your own Ghidra 12.1.x extraction directory.
+          # Leaving the placeholder in place is harmless: REA then reports the
+          # native engine as unavailable, exactly as when the variable is unset.
+          GHIDRA_INSTALL_DIR: '<your Ghidra 12.1.x extraction directory>'
+          # Or read it from the environment the harness already has — the
+          # entry-list dialect evaluates `!!js` expressions at activation:
+          # GHIDRA_INSTALL_DIR: !!js process.env.GHIDRA_INSTALL_DIR
+          # JAVA_HOME: '<your JDK 21 or newer home>'   # only when java is not on PATH
+        failOnStartupError: false

package/package.json

@@ -1,6 +1,48 @@
 {
   "name": "dsh-plugin-rea",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "1.0.5",
+  "description": "Registers the upstream REA MCP server into DeepSeek Harness as mcp__rea__* tools — a third-party adapter, analysis is upstream's. · 把上游 REA 的 MCP 服务接入 DeepSeek Harness，提供 mcp__rea__* 工具（第三方适配，分析能力属上游）。",
+  "type": "module",
+  "license": "MIT",
+  "author": "czcdr",
+  "homepage": "https://github.com/czcdr/dsh-plugin-rea",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/czcdr/dsh-plugin-rea.git"
+  },
+  "bugs": {
+    "url": "https://github.com/czcdr/dsh-plugin-rea/issues"
+  },
+  "keywords": [
+    "deepseek",
+    "deepseek-harness",
+    "dsh",
+    "dsh-plugin",
+    "cordis",
+    "cordis-plugin",
+    "bundle",
+    "mcp",
+    "rea",
+    "reverse-engineering",
+    "ghidra",
+    "binary-analysis"
+  ],
+  "files": [
+    "cordis.patch.yml",
+    "README.md",
+    "LICENSE",
+    "CHANGELOG.md",
+    "check-updates.ps1",
+    "screenshots.json",
+    "assets/",
+    "examples/"
+  ],
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    }
+  },
+  "scripts": {
+    "check-updates": "powershell -NoProfile -File ./check-updates.ps1"
+  }
+}

package/screenshots.json

@@ -0,0 +1,4 @@
+[
+  "assets/screenshot-1.png",
+  "assets/screenshot-2.png"
+]