[PR #3081] [CLOSED] fix(ghidra): discover an installed Ghidra from a launcher on PATH #5600

New issue

Closed

opened 2026-10-31 01:07:52 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:07:52 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3081
Author: @0xLLVEL
Created: 10/14/2026
Status: ❌ Closed

Base: main ← Head: fix/ghidra-path-discovery

---

📝 Commits (1)

• 8ca6948 fix(ghidra): discover an installed Ghidra from a launcher on PATH

📊 Changes

2 files changed (+180 additions, -3 deletions)

View changed files

📝 src/ghidra/GhidraInstallation.test.ts (+104 -0)
📝 src/ghidra/GhidraInstallation.ts (+76 -3)

📄 Description

Summary

rea doctor reports a Ghidra that is installed and reachable on PATH as not_configured, because installation discovery read only GHIDRA_INSTALL_DIR. On a distribution that links the launcher into PATH — the reporter's CachyOS box has /usr/bin/ghidra -> /opt/ghidra/ghidraRun, owned by ghidra 12.1.2-2.1 — the installation is never found, every Ghidra provider check fails, and the remediation only mentions the variable.

This covers the PATH-discovery half of #3008 (suggestion 2). It deliberately does not cover suggestion 1 (reporting a provider row for every advertised tool surface), which touches DoctorProviderIds.ts, doctorRuntime.ts, and composition/binary.ts.

Refs #3008

Problem and expected behavior

Smallest trigger: a Ghidra release extracted to /opt/ghidra, with /usr/bin/ghidra linked at its ghidraRun, and GHIDRA_INSTALL_DIR unset.

Violated invariant: a provider that is genuinely installed and runnable on the host should not be reported as absent. The reporter confirmed that setting GHIDRA_INSTALL_DIR=/opt/ghidra flips the same host to configured=true, available=true, providerVersion=12.1.2, so only the discovery step is missing.

Expected: installation coordinates resolve a ghidra launcher on PATH to its canonical release root and inspect it exactly as an explicit GHIDRA_INSTALL_DIR would.

Change and scope

• GhidraInstallationHost gains an optional resolvePathExecutable(name, environment) seam. An omitted seam leaves discovery dependent on GHIDRA_INSTALL_DIR alone, so existing callers and tests keep their behavior.
• discoveredInstallDir runs only when options.installDir is absent, and only when the caller-selected environment actually supplies a PATH. It resolves ghidra, ghidraRun, ghidra.bat, ghidraRun.bat in that order and takes the canonical launcher's parent directory.
• The system host implements the seam by walking PATH entries, requiring the entry to be an executable file, and returning the resolved real path so a linked launcher resolves to the release root the launcher belongs to.
• An explicit GHIDRA_INSTALL_DIR still wins; the seam is not consulted at all in that case.
• A launcher whose parent directory holds no Ghidra application properties is rejected by the existing installation check rather than trusted, so a stray ghidra on PATH cannot become a provider. Verified below.
• The not_configured detail and remediation now mention PATH so an operator is told the launcher is a supported route.

Not included: any provider-row reporting for other tool surfaces (see Summary), and any change to setup, registration, or the Hopper and IDA lanes.

Contribution scope: not applicable — an ordinary fix within existing boundaries; no target execution, injection, mutation, or protection recovery.

Contract and boundary impact

• Semantic owner and earliest changed stage: src/ghidra/GhidraInstallation.ts, installation-coordinate resolution. Earliest changed stage is provider installation discovery, upstream of doctor projection and of provider selection.
• Contribution scope fit and linked maintainer decision: not applicable; ordinary fix within existing boundaries.
• CLI and MCP/tool-catalog contract: no new tool, no schema change, no catalog change. rea doctor keeps the same check names (configuration, installation, version, headless, native_decompiler, java); only the configuration failure detail and remediation strings, and the reported install_dir on a PATH-only host, change.
• Provider, bridge, target-format, or platform compatibility: Ghidra lane only, on the platforms already accepted by the native-platform table. POSIX probes ghidra and ghidraRun; Windows additionally probes the .bat launchers. Hopper and IDA are untouched.
• Evidence, artifact, provenance, or reconstruction contract: none; this is host discovery, not target evidence.
• Target selection, authority, upstream behavior, and cleanup details: none. The seam is read-only — it opens executables for reading and does not launch Ghidra, mutate the host, or write configuration.
• Generated metadata, package, or installation impact: none; no generated catalog or skill content is affected.

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.

Evidence and regression coverage

• Tests added or updated: six cases in a new Ghidra PATH discovery block in src/ghidra/GhidraInstallation.test.ts — discovery through a linked launcher; explicit GHIDRA_INSTALL_DIR preferred with the seam proven unconsulted; a launcher whose directory holds no release rejected as executable_missing; no PATH seam stays not_configured; absent or empty PATH stays not_configured; and a Windows launcher resolved under the inspected platform.
• Base reproduction or other evidence: on base 242e2b000, a release root placed on PATH yields installDir=null and configuration: failed — GHIDRA_INSTALL_DIR is not set. With this change the same host yields installDir=<release root>, configuration: passed, installation: passed. A stray launcher directory on PATH yields installation: failed, confirming an untrusted directory is not adopted. Executed against the real system host on Windows x64.
• User-visible CLI/MCP output: the configuration check on a PATH-only host moves from failed to passing; when nothing is found the detail becomes GHIDRA_INSTALL_DIR is not set and no Ghidra launcher was found on PATH.
• Remaining proof gaps: no live, licensed Ghidra was contacted on a Linux distribution, so the symlinked-launcher path is covered by the unit seam and by real-path resolution on a real file, not by a real ghidra package install. Symlink creation is unavailable unprivileged on this Windows host, so the Windows live check used a release root placed on PATH directly.

Validation performed

• npm run typecheck — pass.
• npm run check:fast (typecheck + lint) — pass.
• npx vitest run src/ghidra/GhidraInstallation.test.ts src/ghidra/GhidraDoctor.test.ts — 80 passed (69 + 11).
• npx vitest run src/ghidra/ — 13 failures in GhidraAnalysisSeeds, GhidraLanguageOverride, GhidraPowerPcProfile, and GhidraSnapshotCache. Confirmed pre-existing: stashing this change and re-running the same four files on base 242e2b000 produces the identical 4 failed files and 13 failed tests. None of those files touch installation discovery.
• Live Windows x64 check against the real system host, three scenarios (baseline / release root on PATH / stray launcher on PATH) — observed results as described above.

Compatibility, safety, and release

• Breaking changes or migration steps: none. Existing GHIDRA_INSTALL_DIR registrations behave identically; the seam is optional.
• Real Hopper/Ghidra, browser, or OS coverage: Windows x64 live, three scenarios. No live Ghidra engine was launched; installation discovery is read-only and stops short of launching Ghidra, matching the existing doctor boundary.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: PATH-derived directories are treated as untrusted input. The derived root must still satisfy every existing check, including application properties, the headless launcher, the native-decompiler format and architecture probe, and the Java bounds, before a provider reports available. The seam reads executables only and never executes a discovered launcher.

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/3081 **Author:** [@0xLLVEL](https://github.com/0xLLVEL) **Created:** 10/14/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/ghidra-path-discovery` --- ### 📝 Commits (1) - [`8ca6948`](https://github.com/morluto/rea/commit/8ca69488eac73e10a733e955a320fe131ff8e87c) fix(ghidra): discover an installed Ghidra from a launcher on PATH ### 📊 Changes **2 files changed** (+180 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/ghidra/GhidraInstallation.test.ts` (+104 -0) 📝 `src/ghidra/GhidraInstallation.ts` (+76 -3) </details> ### 📄 Description ## Summary `rea doctor` reports a Ghidra that is installed and reachable on `PATH` as `not_configured`, because installation discovery read only `GHIDRA_INSTALL_DIR`. On a distribution that links the launcher into PATH — the reporter's CachyOS box has `/usr/bin/ghidra -> /opt/ghidra/ghidraRun`, owned by `ghidra 12.1.2-2.1` — the installation is never found, every Ghidra provider check fails, and the remediation only mentions the variable. This covers the PATH-discovery half of #3008 (suggestion 2). It deliberately does **not** cover suggestion 1 (reporting a provider row for every advertised tool surface), which touches `DoctorProviderIds.ts`, `doctorRuntime.ts`, and `composition/binary.ts`. Refs #3008 ## Problem and expected behavior Smallest trigger: a Ghidra release extracted to `/opt/ghidra`, with `/usr/bin/ghidra` linked at its `ghidraRun`, and `GHIDRA_INSTALL_DIR` unset. Violated invariant: a provider that is genuinely installed and runnable on the host should not be reported as absent. The reporter confirmed that setting `GHIDRA_INSTALL_DIR=/opt/ghidra` flips the same host to `configured=true, available=true, providerVersion=12.1.2`, so only the discovery step is missing. Expected: installation coordinates resolve a `ghidra` launcher on PATH to its canonical release root and inspect it exactly as an explicit `GHIDRA_INSTALL_DIR` would. ## Change and scope - `GhidraInstallationHost` gains an optional `resolvePathExecutable(name, environment)` seam. An omitted seam leaves discovery dependent on `GHIDRA_INSTALL_DIR` alone, so existing callers and tests keep their behavior. - `discoveredInstallDir` runs only when `options.installDir` is absent, and only when the caller-selected environment actually supplies a PATH. It resolves `ghidra`, `ghidraRun`, `ghidra.bat`, `ghidraRun.bat` in that order and takes the canonical launcher's parent directory. - The system host implements the seam by walking PATH entries, requiring the entry to be an executable file, and returning the resolved real path so a linked launcher resolves to the release root the launcher belongs to. - An explicit `GHIDRA_INSTALL_DIR` still wins; the seam is not consulted at all in that case. - A launcher whose parent directory holds no Ghidra application properties is rejected by the existing `installation` check rather than trusted, so a stray `ghidra` on PATH cannot become a provider. Verified below. - The `not_configured` detail and remediation now mention PATH so an operator is told the launcher is a supported route. Not included: any provider-row reporting for other tool surfaces (see Summary), and any change to setup, registration, or the Hopper and IDA lanes. Contribution scope: not applicable — an ordinary fix within existing boundaries; no target execution, injection, mutation, or protection recovery. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/ghidra/GhidraInstallation.ts`, installation-coordinate resolution. Earliest changed stage is provider installation discovery, upstream of doctor projection and of provider selection. - Contribution scope fit and linked maintainer decision: not applicable; ordinary fix within existing boundaries. - CLI and MCP/tool-catalog contract: no new tool, no schema change, no catalog change. `rea doctor` keeps the same check names (`configuration`, `installation`, `version`, `headless`, `native_decompiler`, `java`); only the `configuration` failure detail and remediation strings, and the reported `install_dir` on a PATH-only host, change. - Provider, bridge, target-format, or platform compatibility: Ghidra lane only, on the platforms already accepted by the native-platform table. POSIX probes `ghidra` and `ghidraRun`; Windows additionally probes the `.bat` launchers. Hopper and IDA are untouched. - Evidence, artifact, provenance, or reconstruction contract: none; this is host discovery, not target evidence. - Target selection, authority, upstream behavior, and cleanup details: none. The seam is read-only — it opens executables for reading and does not launch Ghidra, mutate the host, or write configuration. - Generated metadata, package, or installation impact: none; no generated catalog or skill content is affected. 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. ## Evidence and regression coverage - Tests added or updated: six cases in a new `Ghidra PATH discovery` block in `src/ghidra/GhidraInstallation.test.ts` — discovery through a linked launcher; explicit `GHIDRA_INSTALL_DIR` preferred with the seam proven unconsulted; a launcher whose directory holds no release rejected as `executable_missing`; no PATH seam stays `not_configured`; absent or empty PATH stays `not_configured`; and a Windows launcher resolved under the inspected platform. - Base reproduction or other evidence: on base `242e2b000`, a release root placed on PATH yields `installDir=null` and `configuration: failed — GHIDRA_INSTALL_DIR is not set`. With this change the same host yields `installDir=<release root>`, `configuration: passed`, `installation: passed`. A stray launcher directory on PATH yields `installation: failed`, confirming an untrusted directory is not adopted. Executed against the real system host on Windows x64. - User-visible CLI/MCP output: the `configuration` check on a PATH-only host moves from failed to passing; when nothing is found the detail becomes `GHIDRA_INSTALL_DIR is not set and no Ghidra launcher was found on PATH`. - Remaining proof gaps: no live, licensed Ghidra was contacted on a Linux distribution, so the symlinked-launcher path is covered by the unit seam and by real-path resolution on a real file, not by a real `ghidra` package install. Symlink creation is unavailable unprivileged on this Windows host, so the Windows live check used a release root placed on PATH directly. ## Validation performed - `npm run typecheck` — pass. - `npm run check:fast` (typecheck + lint) — pass. - `npx vitest run src/ghidra/GhidraInstallation.test.ts src/ghidra/GhidraDoctor.test.ts` — 80 passed (69 + 11). - `npx vitest run src/ghidra/` — 13 failures in `GhidraAnalysisSeeds`, `GhidraLanguageOverride`, `GhidraPowerPcProfile`, and `GhidraSnapshotCache`. Confirmed pre-existing: stashing this change and re-running the same four files on base `242e2b000` produces the identical 4 failed files and 13 failed tests. None of those files touch installation discovery. - Live Windows x64 check against the real system host, three scenarios (baseline / release root on PATH / stray launcher on PATH) — observed results as described above. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Existing `GHIDRA_INSTALL_DIR` registrations behave identically; the seam is optional. - Real Hopper/Ghidra, browser, or OS coverage: Windows x64 live, three scenarios. No live Ghidra engine was launched; installation discovery is read-only and stops short of launching Ghidra, matching the existing doctor boundary. - Package or release metadata impact: none. - Security, privacy, process, or containment review: PATH-derived directories are treated as untrusted input. The derived root must still satisfy every existing check, including application properties, the headless launcher, the native-decompiler format and architecture probe, and the Java bounds, before a provider reports available. The seam reads executables only and never executes a discovered launcher. ## 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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:07:52 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-01 21:11:07 +00:00

[GH-ISSUE #5654] [Tracker] Open PRs that can't merge yet: conflicts and red CI (October 2026) #3425

bsakaguchi referenced this issue 2026-11-01 21:44:32 +00:00

[PR #5600] [MERGED] feat(environment): apply evidence-gated write effects to the served state #6989

bsakaguchi referenced this issue 2026-11-01 21:44:47 +00:00

[PR #5664] [MERGED] feat(analysis-view): share templated positions across manifest tools #7021

bsakaguchi referenced this issue 2026-11-01 21:44:51 +00:00

[PR #5699] [MERGED] feat(environment): compare an environment with probe captures of its application #7034

bsakaguchi referenced this issue 2026-11-01 21:44:53 +00:00

[PR #5722] [CLOSED] feat(environment): build an environment from several recording sessions #7037

bsakaguchi referenced this issue 2026-11-01 21:45:04 +00:00

[PR #5787] [MERGED] feat(environment): list every entity on a list's whole lines #7062

bsakaguchi referenced this issue 2026-11-01 21:45:10 +00:00

[PR #5800] [MERGED] feat(environment): answer list filters, search, sorting and paging from the state #7072

bsakaguchi referenced this issue 2026-11-01 21:45:56 +00:00

[PR #6162] [CLOSED] feat(environment): render more read tools from the state and describe responses #7175

bsakaguchi referenced this issue 2026-11-01 21:45:56 +00:00

[PR #6163] [CLOSED] feat(environment): apply evidence-gated write effects to the served state #7176

bsakaguchi referenced this issue 2026-11-01 21:45:56 +00:00

[PR #6164] [CLOSED] feat(environment): compare an environment with probe captures of its application #7177

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

Subscribe

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#5600

No description provided.