[PR #3129] feat(ghidra): admit ELF and thin Mach-O targets on Windows #5634

New issue

Open

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

bsakaguchi commented 2026-10-31 01:08:08 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3129
Author: @dkemper-maker
Created: 10/14/2026
Status: 🔄 Open

Base: main ← Head: feat/windows-ghidra-elf-targets

---

📝 Commits (1)

• cac5bd4 feat(ghidra): admit ELF and thin Mach-O targets on Windows

📊 Changes

4 files changed (+64 additions, -20 deletions)

View changed files

📝 docs/windows-ghidra-p0.md (+15 -5)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+35 -10)
📝 src/ghidra/GhidraProvider.ts (+13 -4)
📝 src/ghidra/GhidraProviderCapabilities.ts (+1 -1)

📄 Description

Draft. This widens the Windows Ghidra P0 admission boundary and follows the shape of #2186 / #2631, which set the verification gate for that kind of change (source-built fixtures with decompiler readback plus the real-provider verifier lane). This PR currently has the admission change, tests, docs, and one real-target verification on a proprietary binary. It does not yet have a source-owned ELF fixture or verify:ghidra coverage. Maintainer scope guidance is requested before that work is done; see "Contribution scope fit" below.

Summary

On Windows, the Ghidra provider refused every non-PE executable with target_format_unsupported, so an analyst on a Windows host could not open an Android, Linux, or macOS binary even with a working Ghidra installation. This PR admits ELF and thin Mach-O images on Windows through the same shared processor checks the POSIX hosts use, and verifies the path on a real Windows host with a 44 MB AArch64 Android shared library.

Related: #2186 and #2631 (bounded ARM/ARM64 PE admission on Windows P0; adjacent lane in the same gate, kept compatible here: PE AArch64 remains rejected by this PR and is left to #2631). #3111 (Windows host blocked on Android analysis; different cause, same user need). #1048 / #2150 / #2358 (re-import cost per CLI call, which the real-target verification below hit in practice).

Problem and expected behavior

Trigger: rea analyze libpdandroid.so --provider ghidra on Windows 11 x64 with Ghidra 12.1.4 and JDK 21 configured. Observed: rejection in about two seconds with target_format_unsupported, while rea doctor reports the provider available. Expected: the same import, overview, and decompile workflow the provider offers for that target on Linux and macOS.

The PE-only rule recorded the scope that had been verified when Windows P0 shipped, not a technical constraint. The native Windows addon under native/windows performs path admission, private runtime creation, snapshotting, and Job Object ownership; it does no executable-format classification. The launcher and snapshot paths are format-agnostic, and Ghidra's own importer selects the loader from the header.

Change and scope

• inspectWindowsP0TargetSupport now returns null for elf and mach-o targets so the shared MIPS/PSP, universal-slice, and supported-architecture checks decide, exactly as on other hosts. The raw NMOS 6502 lane added on main is kept. PE keeps its architecture, role, and managed checks unchanged. DOS, other raw-binary, and universal Mach-O images stay rejected on Windows, with a reason that names them.
• windowsP0Limitations and docs/windows-ghidra-p0.md state the new boundary and the exact verification performed.
• Not included: DOS and non-6502 raw-binary admission on Windows, PE ARM/ARM64 admission (#2631), and any change to the native addon.

Follows the contribution scope: static import and read-only analysis of a caller-selected file through an existing provider boundary. No execution, injection, mutation, or protection recovery.

Contract and boundary impact

• Semantic owner and earliest changed stage: GhidraProvider.inspectTargetSupport (provider adapter admission); no domain or application change.
• Contribution scope fit and linked maintainer decision: existing read-only Ghidra boundary extended to additional input formats on one host. No maintainer decision linked yet; #2186 is the closest precedent and its gate (fixtures + verifier) is not yet met here. Requesting guidance on whether a separate proposal issue is wanted, and whether a source-built ELF AArch64 fixture (same shape as the x86 PE DLL fixtures: no imports, two exported functions) plus a verify:ghidra Windows lane is the required bar.
• CLI and MCP/tool-catalog contract: none. Operation names, schemas, and error codes are unchanged; only the reason text of one target_format_unsupported rejection and one limitation string in the Ghidra capability inventory changed.
• Provider, bridge, target-format, or platform compatibility: Windows Ghidra P0 now admits ELF and thin Mach-O targets on x86, x86-64, ARM, and AArch64. The MIPS PSP profile remains Linux x64 only through the existing check.
• Evidence, artifact, provenance, or reconstruction contract: none.
• Target selection, authority, upstream behavior, and cleanup details: unchanged. ELF and Mach-O targets pass through the same native path admission, immutable private snapshot, digest match, Job Object ownership, and ephemeral-project cleanup as PE targets.
• Generated metadata, package, or installation impact: the limitation string flows into generated catalogs; npm run docs:check passes. No package or installation change.

Expected effects:

• Read existing files or captured data.
• Launch or attach to a process. (Ghidra headless, as for every existing Ghidra-backed operation; no new launch path.)
• 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. (On the verification bar only, not on effects.)

Evidence and regression coverage

• Tests added or updated: GhidraProvider.behavior.test.ts asserts that a win32 host admits ELF x86-64, ELF AArch64, and thin Mach-O AArch64, keeps universal Mach-O rejected with target_format_unsupported, and keeps PE AArch64 rejected with architecture_unsupported. Existing PE role and managed assertions, the raw 6502 lane assertions, and the native-failure diagnostics assertions are unchanged apart from the two ELF expectations that flip to supported.
• Base reproduction: on the pre-rebase base (83a4445) the same rea analyze call on the Android library failed in about two seconds with target_format_unsupported while rea doctor reported Ghidra available. Executed on this host.
• User-visible CLI output: after the change, rea analyze <lib> --provider ghidra returned segment_count: 29, procedure_count: 63343, string_count: 134169, and rea decompile <lib> --procedure _Z23Script_1051_GetVelocityfffiff --provider ghidra returned 3,737 characters of Ghidra pseudocode with the Windows P0 limitations attached.
• Remaining proof gaps: no source-owned ELF fixture and no verify:ghidra lane coverage, which is the gate #2186 established for Windows admission changes. ELF x86-64, ARM32, and thin Mach-O targets share the code path but were not run on a Windows host. The verified binary is proprietary and cannot be committed.

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

• npm run test:local -- src/ghidra/GhidraProvider.behavior.test.ts — 67 passed (after rebasing onto main at 767fe0f, which mocks the native loader in the Windows diagnostics tests).
• npm run check:fast — passed.
• npm run docs:check — passed.
• Real Windows 11 x64 host, Ghidra 12.1.4, JDK 21.0.12.1, released 6.4.0 native addon, REA_GHIDRA_STARTUP_TIMEOUT_MS=7200000: rea analyze on a 44 MB AArch64 ELF (sha256 94143e1c…682d52c4) completed in 8 min 47 s with the overview above; rea decompile of a named procedure completed in 8 min 40 s with pseudocode. Not run: npm run verify:ghidra.

Compatibility, safety, and release

• Breaking changes or migration steps: none. Previously rejected targets are now admitted; previously admitted targets behave identically.
• Real Hopper/Ghidra, browser, or OS coverage: real Ghidra 12.1.4 on Windows 11 x64 for one ELF AArch64 target, as listed above. No fixture-based coverage yet. No Hopper or IDA coverage.
• Package or release metadata impact: none beyond the limitation string.
• Security, privacy, process, or containment review: no change to native admission, snapshot, DACL, or Job Object handling. ELF and Mach-O targets are imported as immutable private snapshots exactly like PE targets; the read-only P0 boundary and the mutation refusal are unchanged.

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. (Pending: verification bar, see above.)
• 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. (No issue requests ELF on Windows specifically; #2186, #2631, and #3111 are the adjacent ones. An earlier revision of this description wrongly stated that no related issue existed; that was written without searching and is corrected here.)
• 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.

🤖 Generated with Claude Code

---

_{🔄 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/3129 **Author:** [@dkemper-maker](https://github.com/dkemper-maker) **Created:** 10/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/windows-ghidra-elf-targets` --- ### 📝 Commits (1) - [`cac5bd4`](https://github.com/morluto/rea/commit/cac5bd4ead918680e50a6c828c8430cc08e683fc) feat(ghidra): admit ELF and thin Mach-O targets on Windows ### 📊 Changes **4 files changed** (+64 additions, -20 deletions) <details> <summary>View changed files</summary> 📝 `docs/windows-ghidra-p0.md` (+15 -5) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+35 -10) 📝 `src/ghidra/GhidraProvider.ts` (+13 -4) 📝 `src/ghidra/GhidraProviderCapabilities.ts` (+1 -1) </details> ### 📄 Description > **Draft.** This widens the Windows Ghidra P0 admission boundary and follows the shape of #2186 / #2631, which set the verification gate for that kind of change (source-built fixtures with decompiler readback plus the real-provider verifier lane). This PR currently has the admission change, tests, docs, and one real-target verification on a proprietary binary. It does not yet have a source-owned ELF fixture or `verify:ghidra` coverage. Maintainer scope guidance is requested before that work is done; see "Contribution scope fit" below. ## Summary On Windows, the Ghidra provider refused every non-PE executable with `target_format_unsupported`, so an analyst on a Windows host could not open an Android, Linux, or macOS binary even with a working Ghidra installation. This PR admits ELF and thin Mach-O images on Windows through the same shared processor checks the POSIX hosts use, and verifies the path on a real Windows host with a 44 MB AArch64 Android shared library. Related: #2186 and #2631 (bounded ARM/ARM64 **PE** admission on Windows P0; adjacent lane in the same gate, kept compatible here: PE AArch64 remains rejected by this PR and is left to #2631). #3111 (Windows host blocked on Android analysis; different cause, same user need). #1048 / #2150 / #2358 (re-import cost per CLI call, which the real-target verification below hit in practice). ## Problem and expected behavior Trigger: `rea analyze libpdandroid.so --provider ghidra` on Windows 11 x64 with Ghidra 12.1.4 and JDK 21 configured. Observed: rejection in about two seconds with `target_format_unsupported`, while `rea doctor` reports the provider available. Expected: the same import, overview, and decompile workflow the provider offers for that target on Linux and macOS. The PE-only rule recorded the scope that had been verified when Windows P0 shipped, not a technical constraint. The native Windows addon under `native/windows` performs path admission, private runtime creation, snapshotting, and Job Object ownership; it does no executable-format classification. The launcher and snapshot paths are format-agnostic, and Ghidra's own importer selects the loader from the header. ## Change and scope - `inspectWindowsP0TargetSupport` now returns `null` for `elf` and `mach-o` targets so the shared MIPS/PSP, universal-slice, and supported-architecture checks decide, exactly as on other hosts. The raw NMOS 6502 lane added on main is kept. PE keeps its architecture, role, and managed checks unchanged. DOS, other raw-binary, and universal Mach-O images stay rejected on Windows, with a reason that names them. - `windowsP0Limitations` and `docs/windows-ghidra-p0.md` state the new boundary and the exact verification performed. - Not included: DOS and non-6502 raw-binary admission on Windows, PE ARM/ARM64 admission (#2631), and any change to the native addon. Follows the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope): static import and read-only analysis of a caller-selected file through an existing provider boundary. No execution, injection, mutation, or protection recovery. ## Contract and boundary impact - Semantic owner and earliest changed stage: `GhidraProvider.inspectTargetSupport` (provider adapter admission); no domain or application change. - Contribution scope fit and linked maintainer decision: existing read-only Ghidra boundary extended to additional input formats on one host. No maintainer decision linked yet; #2186 is the closest precedent and its gate (fixtures + verifier) is not yet met here. Requesting guidance on whether a separate proposal issue is wanted, and whether a source-built ELF AArch64 fixture (same shape as the x86 PE DLL fixtures: no imports, two exported functions) plus a `verify:ghidra` Windows lane is the required bar. - CLI and MCP/tool-catalog contract: none. Operation names, schemas, and error codes are unchanged; only the `reason` text of one `target_format_unsupported` rejection and one limitation string in the Ghidra capability inventory changed. - Provider, bridge, target-format, or platform compatibility: Windows Ghidra P0 now admits ELF and thin Mach-O targets on x86, x86-64, ARM, and AArch64. The MIPS PSP profile remains Linux x64 only through the existing check. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: unchanged. ELF and Mach-O targets pass through the same native path admission, immutable private snapshot, digest match, Job Object ownership, and ephemeral-project cleanup as PE targets. - Generated metadata, package, or installation impact: the limitation string flows into generated catalogs; `npm run docs:check` passes. No package or installation change. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. (Ghidra headless, as for every existing Ghidra-backed operation; no new launch path.) - [ ] 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. - [x] Not sure yet; investigation or maintainer guidance needed. (On the verification bar only, not on effects.) ## Evidence and regression coverage - Tests added or updated: `GhidraProvider.behavior.test.ts` asserts that a `win32` host admits ELF x86-64, ELF AArch64, and thin Mach-O AArch64, keeps universal Mach-O rejected with `target_format_unsupported`, and keeps PE AArch64 rejected with `architecture_unsupported`. Existing PE role and managed assertions, the raw 6502 lane assertions, and the native-failure diagnostics assertions are unchanged apart from the two ELF expectations that flip to supported. - Base reproduction: on the pre-rebase base (83a4445) the same `rea analyze` call on the Android library failed in about two seconds with `target_format_unsupported` while `rea doctor` reported Ghidra available. Executed on this host. - User-visible CLI output: after the change, `rea analyze <lib> --provider ghidra` returned `segment_count: 29`, `procedure_count: 63343`, `string_count: 134169`, and `rea decompile <lib> --procedure _Z23Script_1051_GetVelocityfffiff --provider ghidra` returned 3,737 characters of Ghidra pseudocode with the Windows P0 limitations attached. - Remaining proof gaps: no source-owned ELF fixture and no `verify:ghidra` lane coverage, which is the gate #2186 established for Windows admission changes. ELF x86-64, ARM32, and thin Mach-O targets share the code path but were not run on a Windows host. The verified binary is proprietary and cannot be committed. 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 - `npm run test:local -- src/ghidra/GhidraProvider.behavior.test.ts` — 67 passed (after rebasing onto main at 767fe0f, which mocks the native loader in the Windows diagnostics tests). - `npm run check:fast` — passed. - `npm run docs:check` — passed. - Real Windows 11 x64 host, Ghidra 12.1.4, JDK 21.0.12.1, released 6.4.0 native addon, `REA_GHIDRA_STARTUP_TIMEOUT_MS=7200000`: `rea analyze` on a 44 MB AArch64 ELF (sha256 `94143e1c…682d52c4`) completed in 8 min 47 s with the overview above; `rea decompile` of a named procedure completed in 8 min 40 s with pseudocode. Not run: `npm run verify:ghidra`. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Previously rejected targets are now admitted; previously admitted targets behave identically. - Real Hopper/Ghidra, browser, or OS coverage: real Ghidra 12.1.4 on Windows 11 x64 for one ELF AArch64 target, as listed above. No fixture-based coverage yet. No Hopper or IDA coverage. - Package or release metadata impact: none beyond the limitation string. - Security, privacy, process, or containment review: no change to native admission, snapshot, DACL, or Job Object handling. ELF and Mach-O targets are imported as immutable private snapshots exactly like PE targets; the read-only P0 boundary and the mutation refusal are unchanged. ## Before merge - [x] 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. (Pending: verification bar, see above.) - [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. (No issue requests ELF on Windows specifically; #2186, #2631, and #3111 are the adjacent ones. An earlier revision of this description wrongly stated that no related issue existed; that was written without searching and is corrected here.) - [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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi added the

pull-request

label 2026-10-31 01:08:08 +00:00

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

[PR #5634] [MERGED] ci: split fast and deep static checks #7005

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

[PR #5652] [MERGED] perf(ci): keep fast built shards under ten minutes #7015

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

[PR #5658] [MERGED] perf(test): reuse one stdio MCP server per JavaScript application file #7016

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

[PR #5655] [MERGED] ci: keep npm download caches from Turbo snapshot growth #7017

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

No description provided.