morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #7657] [Bug] Aegis latest-release walkthrough omits native Windows x64 setup #4581

New issue

Closed

opened 2026-10-31 00:50:58 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-31 00:50:58 +00:00

Owner

Originally created by @coygeek on GitHub (Oct 28, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7657

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Documentation

Observed behavior

Source-only finding. A Windows reader following “Inspect the APK yourself” is directed to use Linux, such as WSL. That section runs npx rea-agents@latest inspect-android-package and links current setup instructions, but does not mention the conditional native Windows x64 route documented by the Android provider guide.

I ran the read-only comparison below and the local CLI version command. I did not execute APK analysis on Windows or inspect the live website.

Reproduction

At source revision 65f1c447344a423fa2785847dbcea1e9a9e2454a, run this comparison with Python 3:

from pathlib import Path
import re
page = Path('website/public/showcase/aegis/index.html').read_text()
section = page.split('<section class="article-section" id="try">', 1)[1].split('</section>', 1)[0]
setup = section.split('<p>', 1)[1].split('</p>', 1)[0]
print('Setup advice:', re.sub(r'\s+', ' ', re.sub(r'<[^>]+>', '', setup)).strip())
print('Rerun selects latest:', 'rea-agents@latest inspect-android-package' in section)
print('Historical inspection names 6.1.0:', 'Inspected with REA 6.1.0' in page)
guide = Path('docs/android-analysis.md').read_text()
print('Provider guide supplies PowerShell setup:', 'On Windows, run the equivalent in PowerShell:' in guide)
print('Provider guide documents native Windows x64:', 'On Windows x64, use a REA package with its matching bundled Windows native' in guide)
source = Path('src/android/JadxConfiguration.ts').read_text()
print('Host guard admits Windows x64 with protocol stdin:', all(s in source for s in ['process.platform === "win32" && process.arch === "x64"', 'if (loaded.authority.inspection.protocolStdin === true) return;']))

Read the applicability rule:

sed -n '51,53p' website/AGENTS.md
sed -n '163,166p' website/README.md

The comparison ran once and returned the output below. It needs no APK, provider, fixture, or configuration change.

Expected behavior

Setup advice for the section's latest-release command should acknowledge the documented Windows x64 route with its prerequisites, or clearly scope its older host restriction to the recorded investigation.

The website maintenance contract requires setup/support claims to agree with current guides and released software. It separately preserves a case study's recorded version and date. The Aegis investigation records REA 6.1.0, which should remain unchanged; the rerun command explicitly selects the latest release. Preserving historical findings does not require retaining old host advice for that command.

Impact and scope

P3: the verified effect is incomplete platform guidance in the English Aegis rerun section. No unnecessary WSL installation, failed analysis, or other consequential user action was demonstrated. Readers can find native PowerShell instructions in the Android provider guide.

Native support is conditional on Windows x64, a matching bundled native component with owned protocol stdin, and valid caller-supplied Java/JADX prerequisites. Windows arm64 is outside that boundary. This report does not establish a fresh Windows execution or live-site deployment result.

REA version

Exact stdout from node scripts/rea.mjs --version:

6.8.0

Source revision: 65f1c447344a423fa2785847dbcea1e9a9e2454a.

Runtime and platform

Node.js v24.22.1; macOS 27.0.1, Darwin arm64. The CLI version command used isolated HOME and XDG directories. Source comparison used Python 3. No Android provider was launched.

Target and artifact context

English Aegis showcase HTML and the Android provider's setup documentation/source. No APK or target process was opened.

Interface

Other

Earliest failure stage

Unknown

Relevant output or evidence

The comparison returned:

Setup advice: Set up REA on macOS or Linux, then download these two files into the same folder. On Windows, use a Linux environment such as WSL.
Rerun selects latest: True
Historical inspection names 6.1.0: True
Provider guide supplies PowerShell setup: True
Provider guide documents native Windows x64: True
Host guard admits Windows x64 with protocol stdin: True

Source anchors at the stated revision:

website/public/showcase/aegis/index.html:712-750: current setup link, WSL advice, and latest-release rerun command. Lines 793-795 identify the historical inspection version separately.
website/AGENTS.md:51-53 and website/README.md:163-166: current setup/support comparison rule and protection of recorded case-study provenance.
docs/android-analysis.md:164-199: PowerShell configuration, native Windows x64 prerequisites, older-package caveat, and Windows arm64 exclusion. Lines 209-215 limit the real-host verification claims; this report does not extend them.
src/cli/androidCommands.ts:150-177 and src/android/JadxProvider.ts:549-560: public package-inspection entry point and configuration resolution for APK input.
src/android/JadxConfiguration.ts:287-297 and 508-558: production host check and conditional Windows x64 admission, with explicit rejection when native controls are missing.

I also checked rea-agents-6.8.0 release-tag source: it contains the admission branch and lists the Windows native manifest/addon in its package files. GitHub identifies that tag as a published stable release. These checks concern released source, not a freshly installed npm package's native behavior.

Analysis or suspected cause

Source-derived: this section combines a latest-release rerun with host advice that matched the earlier investigation. A conditional native Windows setup reference would resolve the documentation mismatch while preserving REA 6.1.0 provenance. The Unix command block's “macOS / Linux” label is appropriate; its shell syntax is not a PowerShell recipe.

Additional context

Duplicate searches covered open/closed issues, issue comments, and open/closed/merged PRs. Issue #1262 and merged PR #1276 concern the earlier runtime Windows rejection, now addressed in source; they do not report the surviving Aegis setup advice. PR #1266 introduced that advice. Issues #3423 and #7641 concern different setup-documentation problems. PRs #4480/#6156 concern Korean terminology; #5248 retains historical provider-version provenance while proposing a provider update. No same-defect report or correction was found.

Triage assessment

Impact level: P3
Assessment status: supported
Impact basis: Static inspection establishes incomplete Windows environment guidance for a latest-release walkthrough, without demonstrated runtime failure or consequential user action.
Workaround status: available
Workaround basis: The Android provider guide already supplies native PowerShell configuration and the exact Windows x64 prerequisites; users can consult that guide. Native execution was not rerun in this verification.

Originally created by @coygeek on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7657 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Documentation ### Observed behavior Source-only finding. A Windows reader following “Inspect the APK yourself” is directed to use Linux, such as WSL. That section runs `npx rea-agents@latest inspect-android-package` and links current setup instructions, but does not mention the conditional native Windows x64 route documented by the Android provider guide. I ran the read-only comparison below and the local CLI version command. I did not execute APK analysis on Windows or inspect the live website. ### Reproduction 1. At source revision `65f1c447344a423fa2785847dbcea1e9a9e2454a`, run this comparison with Python 3: ```python from pathlib import Path import re page = Path('website/public/showcase/aegis/index.html').read_text() section = page.split('<section class="article-section" id="try">', 1)[1].split('</section>', 1)[0] setup = section.split('<p>', 1)[1].split('</p>', 1)[0] print('Setup advice:', re.sub(r'\s+', ' ', re.sub(r'<[^>]+>', '', setup)).strip()) print('Rerun selects latest:', 'rea-agents@latest inspect-android-package' in section) print('Historical inspection names 6.1.0:', 'Inspected with REA 6.1.0' in page) guide = Path('docs/android-analysis.md').read_text() print('Provider guide supplies PowerShell setup:', 'On Windows, run the equivalent in PowerShell:' in guide) print('Provider guide documents native Windows x64:', 'On Windows x64, use a REA package with its matching bundled Windows native' in guide) source = Path('src/android/JadxConfiguration.ts').read_text() print('Host guard admits Windows x64 with protocol stdin:', all(s in source for s in ['process.platform === "win32" && process.arch === "x64"', 'if (loaded.authority.inspection.protocolStdin === true) return;'])) ``` 2. Read the applicability rule: ```sh sed -n '51,53p' website/AGENTS.md sed -n '163,166p' website/README.md ``` The comparison ran once and returned the output below. It needs no APK, provider, fixture, or configuration change. ### Expected behavior Setup advice for the section's latest-release command should acknowledge the documented Windows x64 route with its prerequisites, or clearly scope its older host restriction to the recorded investigation. The website maintenance contract requires setup/support claims to agree with current guides and released software. It separately preserves a case study's recorded version and date. The Aegis investigation records REA 6.1.0, which should remain unchanged; the rerun command explicitly selects the latest release. Preserving historical findings does not require retaining old host advice for that command. ### Impact and scope P3: the verified effect is incomplete platform guidance in the English Aegis rerun section. No unnecessary WSL installation, failed analysis, or other consequential user action was demonstrated. Readers can find native PowerShell instructions in the Android provider guide. Native support is conditional on Windows x64, a matching bundled native component with owned protocol stdin, and valid caller-supplied Java/JADX prerequisites. Windows arm64 is outside that boundary. This report does not establish a fresh Windows execution or live-site deployment result. ### REA version Exact stdout from `node scripts/rea.mjs --version`: ```text 6.8.0 ``` Source revision: `65f1c447344a423fa2785847dbcea1e9a9e2454a`. ### Runtime and platform Node.js v24.22.1; macOS 27.0.1, Darwin arm64. The CLI version command used isolated HOME and XDG directories. Source comparison used Python 3. No Android provider was launched. ### Target and artifact context English Aegis showcase HTML and the Android provider's setup documentation/source. No APK or target process was opened. ### Interface Other ### Earliest failure stage Unknown ### Relevant output or evidence The comparison returned: ```text Setup advice: Set up REA on macOS or Linux, then download these two files into the same folder. On Windows, use a Linux environment such as WSL. Rerun selects latest: True Historical inspection names 6.1.0: True Provider guide supplies PowerShell setup: True Provider guide documents native Windows x64: True Host guard admits Windows x64 with protocol stdin: True ``` Source anchors at the stated revision: - `website/public/showcase/aegis/index.html:712-750`: current setup link, WSL advice, and latest-release rerun command. Lines 793-795 identify the historical inspection version separately. - `website/AGENTS.md:51-53` and `website/README.md:163-166`: current setup/support comparison rule and protection of recorded case-study provenance. - `docs/android-analysis.md:164-199`: PowerShell configuration, native Windows x64 prerequisites, older-package caveat, and Windows arm64 exclusion. Lines 209-215 limit the real-host verification claims; this report does not extend them. - `src/cli/androidCommands.ts:150-177` and `src/android/JadxProvider.ts:549-560`: public package-inspection entry point and configuration resolution for APK input. - `src/android/JadxConfiguration.ts:287-297` and `508-558`: production host check and conditional Windows x64 admission, with explicit rejection when native controls are missing. I also checked `rea-agents-6.8.0` release-tag source: it contains the admission branch and lists the Windows native manifest/addon in its package files. GitHub identifies that tag as a published stable release. These checks concern released source, not a freshly installed npm package's native behavior. ### Analysis or suspected cause Source-derived: this section combines a latest-release rerun with host advice that matched the earlier investigation. A conditional native Windows setup reference would resolve the documentation mismatch while preserving REA 6.1.0 provenance. The Unix command block's “macOS / Linux” label is appropriate; its shell syntax is not a PowerShell recipe. ### Additional context Duplicate searches covered open/closed issues, issue comments, and open/closed/merged PRs. Issue #1262 and merged PR #1276 concern the earlier runtime Windows rejection, now addressed in source; they do not report the surviving Aegis setup advice. PR #1266 introduced that advice. Issues #3423 and #7641 concern different setup-documentation problems. PRs #4480/#6156 concern Korean terminology; #5248 retains historical provider-version provenance while proposing a provider update. No same-defect report or correction was found. ## Triage assessment - Impact level: P3 - Assessment status: supported - Impact basis: Static inspection establishes incomplete Windows environment guidance for a latest-release walkthrough, without demonstrated runtime failure or consequential user action. - Workaround status: available - Workaround basis: The Android provider guide already supplies native PowerShell configuration and the exact Windows x64 prerequisites; users can consult that guide. Native execution was not rerun in this verification.

bsakaguchi referenced this issue

2026-10-31 01:13:32 +00:00

[PR #4580] [CLOSED] fix(uninstall): preserve the configuration as it was before uninstall edits it #6320

bsakaguchi closed this issue

2026-11-01 21:11:12 +00:00

bsakaguchi commented

2026-11-01 21:11:13 +00:00

Author

Owner

@coygeek commented on GitHub (Oct 31, 2026):

I checked this against the latest main, and the issue appears resolved. The "Inspect the APK yourself" section of the English Aegis showcase page (website/public/showcase/aegis/index.html) no longer directs Windows readers only to WSL for the latest-release rerun. It now states that on Windows x64, they should use a package with matching Windows native controls and owned protocol stdin support, and it links to the Android provider guide for prerequisites and PowerShell setup, with a Linux environment such as WSL kept only as another option. That matches the conditional native Windows x64 route I reported as omitted: Windows x64, a matching bundled native component with owned protocol stdin, and the Java/JADX prerequisites documented in the provider guide. This was changed by PR #7925 (merge commit d3ecf6800, merged into main on 2026-10-29), and I verified the new wording is present on main and that the historical "Inspected with REA 6.1.0" provenance line is unchanged. Closing as resolved.

@coygeek commented on GitHub (Oct 31, 2026): I checked this against the latest main, and the issue appears resolved. The "Inspect the APK yourself" section of the English Aegis showcase page (`website/public/showcase/aegis/index.html`) no longer directs Windows readers only to WSL for the latest-release rerun. It now states that on Windows x64, they should use a package with matching Windows native controls and owned protocol stdin support, and it links to the Android provider guide for prerequisites and PowerShell setup, with a Linux environment such as WSL kept only as another option. That matches the conditional native Windows x64 route I reported as omitted: Windows x64, a matching bundled native component with owned protocol stdin, and the Java/JADX prerequisites documented in the provider guide. This was changed by [PR #7925](https://github.com/morluto/rea/pull/7925) (merge commit [`d3ecf6800`](https://github.com/morluto/rea/commit/d3ecf6800015f2183a298d78ffb30a266a9efd2a), merged into main on 2026-10-29), and I verified the new wording is present on main and that the historical "Inspected with REA 6.1.0" provenance line is unchanged. Closing as resolved.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#4581

No description provided.

Rows
Columns