morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #2792] [MERGED] fix(ghidra): fail doctor when the JVM os.arch selects an unvalidated decompiler directory #5396

New issue
Closed
opened 2026-10-31 01:06:19 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:06:19 +00:00
Owner
Copy link

📋 Pull Request Information

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

Base: main ← Head: fix/2785-ghidra-jvm-osarch-decompiler

📝 Commits (10+)

  • b23460b fix(ghidra): fail doctor when the JVM os.arch selects an unvalidated decompiler directory
  • 53bb0c1 fix(ghidra): tighten JVM arch remediation and cover os.arch extraction
  • 295d81c fix(ghidra): refuse unrecognized JVM native architectures
  • d005343 docs(ghidra): align doctor prerequisites with JVM architecture admission
  • c523d1a fix(ghidra): reject unreported JVM architecture
  • f2b98fd test(ghidra): separate JVM and executable admission cases
  • 5f84c61 fix(ghidra): defer decompiler arch validation when Java is absent
  • 5730da1 fix(ghidra): reject JVM native architecture override
  • 62e4229 fix(ghidra): validate JVM platform overrides
  • 1dbfac8 fix(ghidra): validate JVM os.name and helper-environment platform overrides

📊 Changes

14 files changed (+593 additions, -54 deletions)

View changed files

📝 docs/installation.md (+12 -1)
📝 src/ghidra/GhidraDoctor.test.ts (+6 -1)
📝 src/ghidra/GhidraInstallation.fixture.ts (+2 -0)
📝 src/ghidra/GhidraInstallation.test.ts (+238 -3)
📝 src/ghidra/GhidraInstallation.ts (+126 -0)
📝 src/ghidra/GhidraJavaLaunch.ts (+62 -2)
📝 src/ghidra/GhidraLauncher.ts (+41 -36)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+17 -9)
📝 src/ghidra/GhidraSnapshotCache.test.ts (+2 -0)
📝 tests/boundary/filesystem/ghidraPspExtension.test.ts (+2 -0)
📝 tests/boundary/mcp/ghidraMcpHarness.ts (+2 -0)
📝 tests/boundary/mcp/ghidraReopen.test.ts (+2 -0)
📝 tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts (+67 -2)
📝 tests/boundary/providers/ghidra/ghidraLauncher.test.ts (+14 -0)

📄 Description

Summary

rea doctor --provider ghidra reported a healthy Ghidra installation while every analysis failed with execution_failure, when the JDK Ghidra runs on has a different architecture than the host (x86_64 Temurin under Rosetta on Apple silicon, decompiler built for mac_arm_64). Doctor validated the native decompiler for Node's process.arch; Ghidra picks the decompiler directory from the JVM's os.arch, which probeJava never read. Now probeJava reads os.arch, and the native_decompiler check fails with a remediation pointing at a matching-arch JDK when the JVM would select a different, unvalidated directory.

Fixes #2785

Problem and expected behavior

Smallest trigger from the issue: Apple silicon host, Ghidra 12.1.4 with only Ghidra/Features/Decompiler/build/os/mac_arm_64/decompile built, and an x86_64 JDK 21 as the default java. rea doctor --provider ghidra --json returned healthy: true; rea function <arm64 Mach-O> <function> returned execution_failure every time. The diagnostics showed ERROR os/mac_x86_64/decompile does not exist from Ghidra's DecompileProcessFactory. Expected: doctor reports the provider as unavailable in this state, with a remediation such as pointing JAVA_HOME at an arm64 JDK.

Change and scope

  • probeJava in src/ghidra/GhidraInstallation.ts now also reads the os.arch property from the existing java -XshowSettings:properties -version output into GhidraJavaObservation.osArch (omitted when the probe cannot establish it).
  • nativeDecompilerCheck fails the check when the observed os.arch maps to a different native directory than the one validated from the host architecture, with detail naming both directories and a remediation to point JAVA_HOME at a JDK matching the built decompiler. Unrecognized os.arch values keep the previous behavior (unknown stays unknown).
  • The observed value is exposed as java_os_arch in ghidraInstallationDiagnostics.

Contribution scope fit: ordinary fix within existing boundaries; no new providers or capabilities, no change to target execution, injection, mutation, or protection recovery. Maintainer scope decision: not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Ghidra installation inspection (inspectGhidraInstallation), consumed by rea doctor and provider registration via projectGhidraDoctorInspection.
  • Contribution scope fit and linked maintainer decision: ordinary fix; not applicable.
  • CLI and MCP/tool-catalog contract: doctor JSON gains a java_os_arch diagnostic key (null when unobserved); the native_decompiler check can now report failed where it previously passed, with remediation text. No tool schema changes.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

(The two checked items are the pre-existing java -XshowSettings -version probe and install-path reads; this change only parses one more property from the same output.)

Evidence and regression coverage

  • Tests added or updated: three cases in src/ghidra/GhidraInstallation.test.ts under "Ghidra native decompiler admission": x86_64 JDK on darwin/arm64 now yields unavailable with native_decompiler failed; matching aarch64 JDK stays available; unrecognized riscv64 os.arch stays available.
  • Base reproduction or other evidence: the new mismatch test fails on the base revision (inspection comes back available, exactly the reported false-healthy) and passes with the fix.
  • User-visible CLI/MCP output: the failed check renders as ghidra-native_decompiler not ok with the JAVA_HOME remediation in doctor output.
  • Remaining proof gaps: no Apple-silicon host or Rosetta JDK in this environment, so the end-to-end Rosetta scenario itself was not executed; verification is at the unit level against the real inspection code path that doctor uses.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • GhidraInstallation.test.ts -- 54/54 pass. vitest workers SIGBUS in this sandbox, so the run used an esbuild bundle of the real test file executed under node with a minimal describe/it/expect shim against the real production modules (the shim was cross-checked: the full suite passes identically, and the new mismatch test fails on the unfixed code).
  • oxlint on both changed files -- 0 errors, 0 warnings.
  • tsc --noEmit could not run here: the repo pins TypeScript 7 whose native binary segfaults in this sandbox. The changes reuse the file's existing typed patterns (optional observation fields, the NATIVE_PLATFORMS lookup, the installationCheck constructor).

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Behavior change is the intended fix: doctor now reports the Ghidra provider unavailable (previously healthy) when the JVM architecture mismatches the validated decompiler.
  • Real Hopper/Ghidra, browser, or OS coverage: unit-level only; no real Ghidra or Rosetta JDK available in this environment.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the change only reads one more JVM property from the existing probe output; no new process launches, no network, no file writes.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 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/2792 **Author:** [@sx4im](https://github.com/sx4im) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/2785-ghidra-jvm-osarch-decompiler` --- ### 📝 Commits (10+) - [`b23460b`](https://github.com/morluto/rea/commit/b23460b4bcb4ebff654ec01a981cca32ff5b378b) fix(ghidra): fail doctor when the JVM os.arch selects an unvalidated decompiler directory - [`53bb0c1`](https://github.com/morluto/rea/commit/53bb0c1c2d70450af27e8f85ea0de015d72c9ca5) fix(ghidra): tighten JVM arch remediation and cover os.arch extraction - [`295d81c`](https://github.com/morluto/rea/commit/295d81ce36c97b60a3772a265b57a087f06d4f3b) fix(ghidra): refuse unrecognized JVM native architectures - [`d005343`](https://github.com/morluto/rea/commit/d0053431977bb36dc0634aec63d05fbc4758eb0b) docs(ghidra): align doctor prerequisites with JVM architecture admission - [`c523d1a`](https://github.com/morluto/rea/commit/c523d1acd0992fa5ef510756926b06995776dc59) fix(ghidra): reject unreported JVM architecture - [`f2b98fd`](https://github.com/morluto/rea/commit/f2b98fd97d9d0f135096f96370e1b4ddeda063ba) test(ghidra): separate JVM and executable admission cases - [`5f84c61`](https://github.com/morluto/rea/commit/5f84c613059bbe5ed46a1ebc258d032d339c9ceb) fix(ghidra): defer decompiler arch validation when Java is absent - [`5730da1`](https://github.com/morluto/rea/commit/5730da13fee5fe90c9b07b1b379378821002650e) fix(ghidra): reject JVM native architecture override - [`62e4229`](https://github.com/morluto/rea/commit/62e422953d7ab7dabfd9b2a93dbf3b21f9966be1) fix(ghidra): validate JVM platform overrides - [`1dbfac8`](https://github.com/morluto/rea/commit/1dbfac8b2540b013c24d882c40afc05a65f687c1) fix(ghidra): validate JVM os.name and helper-environment platform overrides ### 📊 Changes **14 files changed** (+593 additions, -54 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+12 -1) 📝 `src/ghidra/GhidraDoctor.test.ts` (+6 -1) 📝 `src/ghidra/GhidraInstallation.fixture.ts` (+2 -0) 📝 `src/ghidra/GhidraInstallation.test.ts` (+238 -3) 📝 `src/ghidra/GhidraInstallation.ts` (+126 -0) 📝 `src/ghidra/GhidraJavaLaunch.ts` (+62 -2) 📝 `src/ghidra/GhidraLauncher.ts` (+41 -36) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+17 -9) 📝 `src/ghidra/GhidraSnapshotCache.test.ts` (+2 -0) 📝 `tests/boundary/filesystem/ghidraPspExtension.test.ts` (+2 -0) 📝 `tests/boundary/mcp/ghidraMcpHarness.ts` (+2 -0) 📝 `tests/boundary/mcp/ghidraReopen.test.ts` (+2 -0) 📝 `tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts` (+67 -2) 📝 `tests/boundary/providers/ghidra/ghidraLauncher.test.ts` (+14 -0) </details> ### 📄 Description ## Summary `rea doctor --provider ghidra` reported a healthy Ghidra installation while every analysis failed with `execution_failure`, when the JDK Ghidra runs on has a different architecture than the host (x86_64 Temurin under Rosetta on Apple silicon, decompiler built for `mac_arm_64`). Doctor validated the native decompiler for Node's `process.arch`; Ghidra picks the decompiler directory from the JVM's `os.arch`, which `probeJava` never read. Now `probeJava` reads `os.arch`, and the `native_decompiler` check fails with a remediation pointing at a matching-arch JDK when the JVM would select a different, unvalidated directory. Fixes #2785 ## Problem and expected behavior Smallest trigger from the issue: Apple silicon host, Ghidra 12.1.4 with only `Ghidra/Features/Decompiler/build/os/mac_arm_64/decompile` built, and an x86_64 JDK 21 as the default `java`. `rea doctor --provider ghidra --json` returned `healthy: true`; `rea function <arm64 Mach-O> <function>` returned `execution_failure` every time. The diagnostics showed `ERROR os/mac_x86_64/decompile does not exist` from Ghidra's `DecompileProcessFactory`. Expected: doctor reports the provider as unavailable in this state, with a remediation such as pointing `JAVA_HOME` at an arm64 JDK. ## Change and scope - `probeJava` in `src/ghidra/GhidraInstallation.ts` now also reads the `os.arch` property from the existing `java -XshowSettings:properties -version` output into `GhidraJavaObservation.osArch` (omitted when the probe cannot establish it). - `nativeDecompilerCheck` fails the check when the observed `os.arch` maps to a different native directory than the one validated from the host architecture, with detail naming both directories and a remediation to point `JAVA_HOME` at a JDK matching the built decompiler. Unrecognized `os.arch` values keep the previous behavior (unknown stays unknown). - The observed value is exposed as `java_os_arch` in `ghidraInstallationDiagnostics`. Contribution scope fit: ordinary fix within existing boundaries; no new providers or capabilities, no change to target execution, injection, mutation, or protection recovery. Maintainer scope decision: not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: Ghidra installation inspection (`inspectGhidraInstallation`), consumed by `rea doctor` and provider registration via `projectGhidraDoctorInspection`. - Contribution scope fit and linked maintainer decision: ordinary fix; not applicable. - CLI and MCP/tool-catalog contract: doctor JSON gains a `java_os_arch` diagnostic key (null when unobserved); the `native_decompiler` check can now report failed where it previously passed, with remediation text. No tool schema changes. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. (The two checked items are the pre-existing `java -XshowSettings -version` probe and install-path reads; this change only parses one more property from the same output.) ## Evidence and regression coverage - Tests added or updated: three cases in `src/ghidra/GhidraInstallation.test.ts` under "Ghidra native decompiler admission": x86_64 JDK on darwin/arm64 now yields `unavailable` with `native_decompiler` failed; matching `aarch64` JDK stays `available`; unrecognized `riscv64` `os.arch` stays `available`. - Base reproduction or other evidence: the new mismatch test fails on the base revision (inspection comes back `available`, exactly the reported false-healthy) and passes with the fix. - User-visible CLI/MCP output: the failed check renders as `ghidra-native_decompiler` not ok with the `JAVA_HOME` remediation in doctor output. - Remaining proof gaps: no Apple-silicon host or Rosetta JDK in this environment, so the end-to-end Rosetta scenario itself was not executed; verification is at the unit level against the real inspection code path that doctor uses. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `GhidraInstallation.test.ts` -- 54/54 pass. vitest workers SIGBUS in this sandbox, so the run used an esbuild bundle of the real test file executed under node with a minimal describe/it/expect shim against the real production modules (the shim was cross-checked: the full suite passes identically, and the new mismatch test fails on the unfixed code). - `oxlint` on both changed files -- 0 errors, 0 warnings. - `tsc --noEmit` could not run here: the repo pins TypeScript 7 whose native binary segfaults in this sandbox. The changes reuse the file's existing typed patterns (optional observation fields, the `NATIVE_PLATFORMS` lookup, the `installationCheck` constructor). ## Compatibility, safety, and release - Breaking changes or migration steps: none. Behavior change is the intended fix: doctor now reports the Ghidra provider unavailable (previously healthy) when the JVM architecture mismatches the validated decompiler. - Real Hopper/Ghidra, browser, or OS coverage: unit-level only; no real Ghidra or Rosetta JDK available in this environment. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the change only reads one more JVM property from the existing probe output; no new process launches, no network, no file writes. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:06:19 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#5396
No description provided.