[PR #2699] [MERGED] docs(android): link the JADX provider download #5322

New issue

Closed

opened 2026-10-31 01:05:44 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:05:44 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2699
Author: @Seelly
Created: 10/13/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @N0zoM1z0

Base: main ← Head: patch-1

📝 Commits (6)

56e856a Update supply tools section in android-analysis.md
3a0140e docs(android): verify the JADX engine before use
6d47094 docs(android): clarify provider downloads for npm installations
7956168 docs(android): provide a verified JADX download path
c95be3c docs(android): stop setup after failed download verification
39372cc chore: sync main documentation and CI repairs

📊 Changes

1 file changed (+34 additions, -4 deletions)

View changed files

📝 docs/android-analysis.md (+34 -4)

📄 Description

Summary

Make the pinned JADX 0.7.1 download usable from both npm installations and repository checkouts. Link the release asset and pinned digest, provide shell/PowerShell commands, and identify the fixture helper as checkout-only. Set the POSIX provider path only after the download and checksum check succeed.

Scope

The Android guide owns this documentation-only change. Existing provider, CLI/MCP, Evidence and package contracts are unchanged. Maintainer scope approval is not applicable to this clarification. The contributor's missing download link prompted this PR; there is no linked issue.

Validation

Downloaded the release JAR and verified SHA-256 6e5eacf500b64292bfb73c49797c1958f6ee44646e43e868039ae7feb573ff75 against the source pin. The fixture helper also verified its test APK.
Ran the documented Linux download commands and both checksum paths. Reproduced the original corrupt-file case, then verified that corrupt files and failed downloads leave the provider path unset after the correction.
POSIX syntax, npm run docs:check (5 conformance tests), typecheck/lint, formatting and diff checks passed.

Native macOS/PowerShell commands and provider execution were not repeated. The shasum fallback was exercised on Linux.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/2699 **Author:** [@Seelly](https://github.com/Seelly) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (6) - [`56e856a`](https://github.com/morluto/rea/commit/56e856a26e51b85d60aedf17b3b9c927893b73b5) Update supply tools section in android-analysis.md - [`3a0140e`](https://github.com/morluto/rea/commit/3a0140eecb42972baecc19638458829cbfe6e387) docs(android): verify the JADX engine before use - [`6d47094`](https://github.com/morluto/rea/commit/6d470940c6c68df11c04bd399fd817074744a8a6) docs(android): clarify provider downloads for npm installations - [`7956168`](https://github.com/morluto/rea/commit/7956168a93354be7c372d08024901c1b66eac825) docs(android): provide a verified JADX download path - [`c95be3c`](https://github.com/morluto/rea/commit/c95be3cca5a6c1f37a359440a8a8f1c2105a52fd) docs(android): stop setup after failed download verification - [`39372cc`](https://github.com/morluto/rea/commit/39372cc6513f035fcf2a34fc5137180587c0c6f4) chore: sync main documentation and CI repairs ### 📊 Changes **1 file changed** (+34 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `docs/android-analysis.md` (+34 -4) </details> ### 📄 Description ## Summary Make the pinned JADX 0.7.1 download usable from both npm installations and repository checkouts. Link the release asset and pinned digest, provide shell/PowerShell commands, and identify the fixture helper as checkout-only. Set the POSIX provider path only after the download and checksum check succeed. ## Scope The Android guide owns this documentation-only change. Existing provider, CLI/MCP, Evidence and package contracts are unchanged. Maintainer scope approval is not applicable to this clarification. The contributor's missing download link prompted this PR; there is no linked issue. ## Validation - Downloaded the release JAR and verified SHA-256 `6e5eacf500b64292bfb73c49797c1958f6ee44646e43e868039ae7feb573ff75` against the source pin. The fixture helper also verified its test APK. - Ran the documented Linux download commands and both checksum paths. Reproduced the original corrupt-file case, then verified that corrupt files and failed downloads leave the provider path unset after the correction. - POSIX syntax, `npm run docs:check` (5 conformance tests), typecheck/lint, formatting and diff checks passed. Native macOS/PowerShell commands and provider execution were not repeated. The shasum fallback was exercised on Linux. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 01:05:44 +00:00