From 69be514c67c8b2eb8b450355a9782d9237748fda Mon Sep 17 00:00:00 2001 From: morluto <76467478+morluto@users.noreply.github.com> Date: Wed, 7 Oct 2026 02:32:55 +0800 Subject: [PATCH] docs: update release boundary to npm 4.1.0 with Windows native bundle --- README.md | 2 +- README_ar.md | 2 +- README_ja.md | 2 +- README_ko.md | 2 +- README_zh.md | 2 +- docs/android-analysis.md | 2 +- docs/installation.md | 11 +++++------ docs/javascript-application-workflows.md | 2 +- docs/windows-ghidra-p0.md | 4 ++-- .../references/android-applications.md | 4 ++-- .../references/javascript-applications.md | 2 +- 11 files changed, 17 insertions(+), 18 deletions(-) diff --git a/README.md b/README.md index 7dfe4c310..22ec8072f 100644 --- a/README.md +++ b/README.md @@ -131,7 +131,7 @@ Firmware region inspection and explicit extraction use caller-supplied Binwalk a Static APK analysis uses a separately supplied headless JADX JAR and Java, with no emulator or APK execution. See [Android analysis](docs/android-analysis.md) for setup, CLI/MCP operations, coverage and public test fixtures. -Repository main includes experimental Windows x64 Ghidra support for native x86-64 PE applications on local NTFS, with bundled Job Object, private-DACL, and path-admission controls. Check the [release boundary](docs/installation.md#released-package-and-main) before expecting this from an npm package. See [Windows Ghidra P0](docs/windows-ghidra-p0.md) for prerequisites and verified scope. +Repository main and npm 4.1.0 include experimental Windows x64 Ghidra support for native x86-64 PE applications on local NTFS, with bundled Job Object, private-DACL, and path-admission controls. Check the [release boundary](docs/installation.md#released-package-and-main) before expecting this from an older npm package. See [Windows Ghidra P0](docs/windows-ghidra-p0.md) for prerequisites and verified scope. If something is not working, run: diff --git a/README_ar.md b/README_ar.md index ecc13639d..ec2d2ae6e 100644 --- a/README_ar.md +++ b/README_ar.md @@ -150,7 +150,7 @@ rea setup يستطيع Setup التحقق من التثبيت وحفظ المسارات؛ ولا يثبت أو يحدّث Ghidra أو Java أو Node.js أو npm أو Homebrew. -Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are implemented; npm 4.0.1 does not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). +Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are bundled in npm 4.1.0; older releases do not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). ### تشخيص المشكلات diff --git a/README_ja.md b/README_ja.md index d3dd483dd..42e0b12e4 100644 --- a/README_ja.md +++ b/README_ja.md @@ -150,7 +150,7 @@ Ghidra は Linux x64 と macOS x64/arm64 に対応します。Ghidra 12.1.4 と Setup はインストールを確認し、パスを保存できます。Ghidra、Java、Node.js、npm、Homebrew のインストールや更新は行いません。 -Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are implemented; npm 4.0.1 does not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). +Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are bundled in npm 4.1.0; older releases do not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). ### トラブルシューティング diff --git a/README_ko.md b/README_ko.md index 9ba04f05b..f3f39b3f5 100644 --- a/README_ko.md +++ b/README_ko.md @@ -151,7 +151,7 @@ Ghidra는 Linux x64와 macOS x64/arm64를 지원합니다. Ghidra 12.1.4와 완 Setup은 설치를 확인하고 경로를 저장할 수 있습니다. Ghidra, Java, Node.js, npm, Homebrew를 설치하거나 업데이트하지 않습니다. -Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are implemented; npm 4.0.1 does not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). +Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are bundled in npm 4.1.0; older releases do not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). ### 문제 해결 diff --git a/README_zh.md b/README_zh.md index fc033f542..368b70dcb 100644 --- a/README_zh.md +++ b/README_zh.md @@ -150,7 +150,7 @@ Ghidra 支持 Linux x64 和 macOS x64/arm64。单独安装 Ghidra 12.1.4 和完 Setup 可以验证安装并保存路径，不会安装或升级 Ghidra、Java、Node.js、npm 或 Homebrew。 -Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are implemented; npm 4.0.1 does not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). +Repository main includes experimental Windows x64 Ghidra P0 for native, non-managed, non-DLL x86-64 PE applications on fixed local NTFS. The native controls are bundled in npm 4.1.0; older releases do not contain them. See the [release boundary](docs/installation.md#released-package-and-main) and [Windows Ghidra P0](docs/windows-ghidra-p0.md). ### 故障排查 diff --git a/docs/android-analysis.md b/docs/android-analysis.md index 3e4b4d213..84585a07e 100644 --- a/docs/android-analysis.md +++ b/docs/android-analysis.md @@ -5,7 +5,7 @@ kept as an unmodified, commit-pinned Git submodule; see [upstream provenance](../third_party/README.md). CLI and MCP use the same application workflow and return artifact-bound Evidence inline. -This family is present on repository main and absent from npm 4.0.1. Check the +This family is present on repository main and in npm 4.1.0. Check the [released package boundary](installation.md#released-package-and-main) and the connected server's tool list before selecting it. diff --git a/docs/installation.md b/docs/installation.md index 3420e4a12..408470534 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -68,13 +68,12 @@ selects the npm release, and persistent MCP registrations are pinned to the version that performed setup. Installing newer instructions does not update a running server or its registration. -The release checked on **2026-10-06** was **4.0.1** (116 MCP tools). That artifact -has static JavaScript inspection and full inline Evidence workflows, but does -not include main's Windows native control bundle, Android/JADX or firmware -tools, Ghidra function annotation workflow, or retained application-Evidence +The release checked on **2026-10-06** was **4.1.0** (125 MCP tools). That artifact +includes main's Windows native control bundle, Android/JADX and firmware +tools, Ghidra function annotation workflow, and retained application-Evidence references. -Main's catalog describes those additions; a source build or a subsequent -release containing them is required. Package startup alone does not verify a +Main's catalog describes the current code; a source build or a subsequent +release containing later changes is required for anything newer. Package startup alone does not verify a provider's real platform workflow. To check the published version, run `npm view rea-agents dist-tags.latest`. diff --git a/docs/javascript-application-workflows.md b/docs/javascript-application-workflows.md index 1a5d3bc1d..8bcd6ce1b 100644 --- a/docs/javascript-application-workflows.md +++ b/docs/javascript-application-workflows.md @@ -164,7 +164,7 @@ in `application`, or `left`/`right` for comparisons. `RETURNED_ID` is a template not a literal valid ID. Native Evidence arrays still use complete records. References are scoped to one connection; `close_binary` clears them. Export a bundle before closing and import it on another connection, or supply the full -inline Evidence there. npm 4.0.1 accepts full inline Evidence only; installing +inline Evidence there. Versions before 4.1.0 accept full inline Evidence only; installing newer skill instructions does not change that schema. See [MCP Evidence inputs](mcp-contracts.md#retained-application-evidence-inputs). diff --git a/docs/windows-ghidra-p0.md b/docs/windows-ghidra-p0.md index ab83c17b9..abfc4451f 100644 --- a/docs/windows-ghidra-p0.md +++ b/docs/windows-ghidra-p0.md @@ -1,8 +1,8 @@ # Windows Ghidra P0 -This guide describes repository main. npm 4.0.1 does not include the Windows +This guide describes repository main. npm 4.1.0 includes the Windows native bundle; check the [release boundary](installation.md#released-package-and-main) -before applying these instructions to a published package. +before applying these instructions to an older published package. Status: experimental Windows x64 support for the read-only P0 boundary. Windows package builds bundle native process, filesystem, and DACL controls. REA diff --git a/skills/reverse-engineer-anything/references/android-applications.md b/skills/reverse-engineer-anything/references/android-applications.md index 1b0411aae..297e88677 100644 --- a/skills/reverse-engineer-anything/references/android-applications.md +++ b/skills/reverse-engineer-anything/references/android-applications.md @@ -1,7 +1,7 @@ # Android application artifacts -Use the connected server's advertised Android tools. Repository main includes -this family; npm 4.0.1 does not. A skill installation alone cannot add it to an +Use the connected server's advertised Android tools. Repository main and npm +4.1.0 include this family. A skill installation alone cannot add it to an older server. Start with `inspect_android_package` on the caller's APK path for package diff --git a/skills/reverse-engineer-anything/references/javascript-applications.md b/skills/reverse-engineer-anything/references/javascript-applications.md index efbc10a58..e19c3cdc8 100644 --- a/skills/reverse-engineer-anything/references/javascript-applications.md +++ b/skills/reverse-engineer-anything/references/javascript-applications.md @@ -44,7 +44,7 @@ When advertised by the connected server, application trace and compare tools accept complete inline Evidence or `{"kind":"retained-evidence","evidence_id":"ev_<64 lowercase hex characters>"}` for their application input (`application`, or `left`/`right`). This notation is -a template: replace it with the actual returned ID. npm 4.0.1 accepts only full +a template: replace it with the actual returned ID. Versions before 4.1.0 accept only full inline Evidence. Use the exact ID returned by the producer on the same MCP connection. Resolution does not run analysis or select a provider; findings remain inline. Native observation