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 #2977] feat(ghidra): report computed branches without a recovered jump table #5533

New issue
Open
opened 2026-10-31 01:07:22 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:07:22 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2977
Author: @RishTheFish21
Created: 10/13/2026
Status: 🔄 Open

Base: main ← Head: feat/487-unresolved-indirect-branches

📝 Commits (10+)

  • 26fd63c feat(ghidra): report computed branches without a recovered jump table
  • ac520aa test(ghidra): assert computed branch warning evidence
  • 523cad5 Merge commit '2895a18ca9' into codex/ci-review-pr2977-20261014
  • fb77645 fix(ghidra): address review on unresolved indirect branches
  • 9a4866d Merge remote-tracking branch 'origin/main' into HEAD
  • d170ed2 fix(native): preserve indirect branch unknowns without API coverage
  • 50b39ef fix(workflows): invalidate stale native API inspection snapshots
  • 903e659 fix(ghidra): attribute indirect-branch warnings by source address
  • 0e18a17 merge(main): integrate indirect-branch warning attribution with upstream
  • a02741b Merge main into feat/487-unresolved-indirect-branches

📊 Changes

27 files changed (+1716 additions, -44 deletions)

View changed files

📝 bridge/ghidra/ReaGhidraBridge.java (+214 -0)
📝 docs/native-investigation.md (+26 -1)
📝 docs/testing-lanes.md (+6 -0)
📝 knip.json (+1 -0)
📝 scripts/verify-real-ghidra-assertions.mjs (+3 -0)
📝 scripts/verify-real-ghidra-function.mjs (+153 -0)
➕ scripts/verify-real-ghidra-warning-attribution.mjs (+191 -0)
📝 scripts/verify-real-ghidra.mjs (+57 -25)
📝 src/application/WorkflowAnalysisProfile.ts (+5 -3)
📝 src/application/WorkflowEvidence.test.ts (+14 -4)
📝 src/application/binary/AnalysisSnapshotCache.test.ts (+35 -0)
📝 src/application/native/NativeApiInspection.test.ts (+235 -1)
📝 src/application/native/NativeApiInspection.ts (+34 -4)
📝 src/domain/ghidraValues.fixture.ts (+1 -0)
📝 src/domain/native/nativeApiBoundary.ts (+37 -0)
📝 src/ghidra/GhidraAnalysisProfile.ts (+1 -0)
📝 src/ghidra/GhidraFunctionValues.test.ts (+63 -0)
📝 src/ghidra/GhidraNativeAnalysisValues.ts (+11 -0)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+4 -0)
📝 src/ghidra/GhidraRawProfileDigest.test.ts (+4 -2)

...and 7 more files

📄 Description

Summary

Part of #487 (second of the steps proposed there; the first was #1592). When Ghidra cannot recover a jump table for a computed br, its decompiler rewrites the branch as a call or return (FlowInfo::truncateIndirectJump), so nothing reached REA's output: jump_tables and unsupported_branches stayed empty and the dossier read as complete. This is the gap @CassieFox23 reported for the RenderScript blur kernels.

This PR reports those sites in a new optional field, native_api.unresolved_indirect_branches, and surfaces each one as a residual unknown in inspect_native_api.

Problem and expected behavior

Before: a function whose only dispatch is an unbounded computed jump (adr x8, …; add x8, x8, x0, lsl #3; br x8) produces jump_tables: [], unsupported_branches: [], and no residual unknown.

After, for the same function:

  • unresolved_indirect_branches: [{ branch_address, decompiler_outcome: "jump_table_recovery_failed", listing_targets: [], evidence: [...] }], with Ghidra's warning ("Could not recover jumptable at … Too many branches") retained as evidence
  • unsupported_branches: ["indirect-branch-target-recovery"]
  • residual unknown: "Which targets can the indirect branch at 0x… reach? The decompiler could not recover a jump table there and treated it as a call; it may be a dispatch inside this function or an indirect tail call."

Change and scope

  • Bridge (ReaGhidraBridge.java): every listing instruction in the function body whose flow type is a computed jump (not a call or terminator), and whose address is not a recovered JumpTable switch, is reported. decompiler_outcome is jump_table_recovery_failed when the decompiler's pseudocode contains "Could not recover jumptable at ", otherwise no_jump_table_warning. listing_targets are the listing's flow references (no case values implied).
  • Schema (nativeApiBoundary.ts): new unresolved_indirect_branches field using exactOptional(): absent means the provider did not inspect indirect branches, so Hopper/IDA output and older snapshots parse unchanged. New evidence kind indirect-branch.
  • Projection (NativeApiInspection.ts): one residual unknown per site and indirect-branch-target-recovery in unsupported_branches.
  • Ghidra address validation also covers the new addresses.

Deliberately not attempted: telling a dispatch apart from an indirect tail call. On real Ghidra 12.1.4 both produce the same recovery failure (see Validation), so REA reports the uncertainty instead of guessing. Not included: the decompiler-failure handling from #487 (a separate follow-up), and sites in regions where Ghidra created no function.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Ghidra bridge native API boundary.
  • CLI and MCP/tool-catalog contract: additive. analyze_function/inspect_native_api output gains the optional unresolved_indirect_branches field, the evidence kind indirect-branch, and the unsupported_branches value indirect-branch-target-recovery. Existing fields are unchanged.
  • Provider, bridge, target-format, or platform compatibility: Ghidra only; other providers omit the field.
  • Evidence, artifact, provenance, or reconstruction contract: new facts are listing and decompiler-warning observations with their source recorded; no targets or case values are inferred.
  • Process execution, authorization, cleanup, or containment impact: none.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: output schemas regenerate in CI; no tracked metadata changes.

Evidence and regression coverage

  • Tests added or updated:
    • NativeApiInspection.test.ts: residual unknowns and unsupported_branches for both outcomes; empty or absent inventory adds nothing; a branch without evidence is rejected.
    • GhidraFunctionValues.test.ts: a non-canonical branch address is rejected.
    • New real-Ghidra fixture tests/conformance/ghidra/indirect-branches.S (unbounded computed jump plus an indirect tail call) in the aarch64-jump-table lane, as ELF and, on arm64 hosts, Mach-O. The lane asserts the computed jump is reported and not mistaken for a jump table, and records the tail call's classification.
    • The existing relative-switch fixtures now assert that recovered switches are not reported as unresolved.
  • Base reproduction or other evidence: on main the field doesn't exist, so the fixture's computed jump leaves no trace in the dossier.
  • User-visible CLI/MCP output: see "Problem and expected behavior".
  • Remaining proof gaps: not run against the real librenderscript-toolkit.so from the issue thread; no Linux run.

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:focused -- src/application/native/NativeApiInspection.test.ts src/ghidra/GhidraFunctionValues.test.ts: passed
  • npm run check:fast: passed
  • npm run lint, npm run knip: passed
  • npm run docs:check: passed
  • npm run verify:ghidra:aarch64-jump-table on an Apple Silicon Mac (Ghidra 12.1.4, JDK 21): ok: true.
    • Computed jump: reported as jump_table_recovery_failed with the decompiler warning, on ELF (0x10000c) and Mach-O (0xc).
    • Indirect tail call: also reported as jump_table_recovery_failed ("Could not recover jumptable at … Too many branches") on both formats.
    • All relative-* switch fixtures passed, including the new "not unresolved" check.

Note on that run: on current main the lane stops early in the host-native native-value check, where compare_functions of a function against itself returns unknown instead of unchanged. Reproduced on main without this PR. The comments facet is empty with no declared coverage, and calls lacks relationship coverage, which looks related to #2450 (b17487f4). I skipped that one assertion locally to reach the fixtures this PR adds, and will report it separately.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; the field is optional and additive.
  • Real Hopper/Ghidra, browser, or OS coverage: real Ghidra on macOS arm64 only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: static analysis only; reads the existing listing and decompiler output.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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.

Author readiness

Human owner: @RishTheFish21

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

🔄 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/2977 **Author:** [@RishTheFish21](https://github.com/RishTheFish21) **Created:** 10/13/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/487-unresolved-indirect-branches` --- ### 📝 Commits (10+) - [`26fd63c`](https://github.com/morluto/rea/commit/26fd63c3966f7845145df8d9ca2437a0134eac22) feat(ghidra): report computed branches without a recovered jump table - [`ac520aa`](https://github.com/morluto/rea/commit/ac520aab522882e75f96fa72b1f04701db634ced) test(ghidra): assert computed branch warning evidence - [`523cad5`](https://github.com/morluto/rea/commit/523cad54fc41c2bb5762679d2b96caef8e02cde4) Merge commit '2895a18ca92f415ae62f87167ba9c7a672e3b7dc' into codex/ci-review-pr2977-20261014 - [`fb77645`](https://github.com/morluto/rea/commit/fb77645644435c7092700f9e1b0f0495466cf80f) fix(ghidra): address review on unresolved indirect branches - [`9a4866d`](https://github.com/morluto/rea/commit/9a4866d0fbb687e631efda477321401a3be00c73) Merge remote-tracking branch 'origin/main' into HEAD - [`d170ed2`](https://github.com/morluto/rea/commit/d170ed2ceaa327a0fd8081735f613b3becf1a695) fix(native): preserve indirect branch unknowns without API coverage - [`50b39ef`](https://github.com/morluto/rea/commit/50b39effa77e3cf15c1f821c5608b2a9d705d6ea) fix(workflows): invalidate stale native API inspection snapshots - [`903e659`](https://github.com/morluto/rea/commit/903e6592d8f7f4bc0f64b678b54e233cfb84831f) fix(ghidra): attribute indirect-branch warnings by source address - [`0e18a17`](https://github.com/morluto/rea/commit/0e18a17dbd7c6d8151bfd25ace37f385b3e96915) merge(main): integrate indirect-branch warning attribution with upstream - [`a02741b`](https://github.com/morluto/rea/commit/a02741b2117f99a179bef1f1ca821fff5fd30711) Merge main into feat/487-unresolved-indirect-branches ### 📊 Changes **27 files changed** (+1716 additions, -44 deletions) <details> <summary>View changed files</summary> 📝 `bridge/ghidra/ReaGhidraBridge.java` (+214 -0) 📝 `docs/native-investigation.md` (+26 -1) 📝 `docs/testing-lanes.md` (+6 -0) 📝 `knip.json` (+1 -0) 📝 `scripts/verify-real-ghidra-assertions.mjs` (+3 -0) 📝 `scripts/verify-real-ghidra-function.mjs` (+153 -0) ➕ `scripts/verify-real-ghidra-warning-attribution.mjs` (+191 -0) 📝 `scripts/verify-real-ghidra.mjs` (+57 -25) 📝 `src/application/WorkflowAnalysisProfile.ts` (+5 -3) 📝 `src/application/WorkflowEvidence.test.ts` (+14 -4) 📝 `src/application/binary/AnalysisSnapshotCache.test.ts` (+35 -0) 📝 `src/application/native/NativeApiInspection.test.ts` (+235 -1) 📝 `src/application/native/NativeApiInspection.ts` (+34 -4) 📝 `src/domain/ghidraValues.fixture.ts` (+1 -0) 📝 `src/domain/native/nativeApiBoundary.ts` (+37 -0) 📝 `src/ghidra/GhidraAnalysisProfile.ts` (+1 -0) 📝 `src/ghidra/GhidraFunctionValues.test.ts` (+63 -0) 📝 `src/ghidra/GhidraNativeAnalysisValues.ts` (+11 -0) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+4 -0) 📝 `src/ghidra/GhidraRawProfileDigest.test.ts` (+4 -2) _...and 7 more files_ </details> ### 📄 Description ## Summary Part of #487 (second of the steps proposed there; the first was #1592). When Ghidra cannot recover a jump table for a computed `br`, its decompiler rewrites the branch as a call or return (`FlowInfo::truncateIndirectJump`), so nothing reached REA's output: `jump_tables` and `unsupported_branches` stayed empty and the dossier read as complete. This is the gap @CassieFox23 reported for the RenderScript blur kernels. This PR reports those sites in a new optional field, `native_api.unresolved_indirect_branches`, and surfaces each one as a residual unknown in `inspect_native_api`. ## Problem and expected behavior Before: a function whose only dispatch is an unbounded computed jump (`adr x8, …; add x8, x8, x0, lsl #3; br x8`) produces `jump_tables: []`, `unsupported_branches: []`, and no residual unknown. After, for the same function: - `unresolved_indirect_branches: [{ branch_address, decompiler_outcome: "jump_table_recovery_failed", listing_targets: [], evidence: [...] }]`, with Ghidra's warning ("Could not recover jumptable at … Too many branches") retained as evidence - `unsupported_branches: ["indirect-branch-target-recovery"]` - residual unknown: "Which targets can the indirect branch at 0x… reach? The decompiler could not recover a jump table there and treated it as a call; it may be a dispatch inside this function or an indirect tail call." ## Change and scope - Bridge (`ReaGhidraBridge.java`): every listing instruction in the function body whose flow type is a computed jump (not a call or terminator), and whose address is not a recovered `JumpTable` switch, is reported. `decompiler_outcome` is `jump_table_recovery_failed` when the decompiler's pseudocode contains "Could not recover jumptable at <that address>", otherwise `no_jump_table_warning`. `listing_targets` are the listing's flow references (no case values implied). - Schema (`nativeApiBoundary.ts`): new `unresolved_indirect_branches` field using `exactOptional()`: absent means the provider did not inspect indirect branches, so Hopper/IDA output and older snapshots parse unchanged. New evidence kind `indirect-branch`. - Projection (`NativeApiInspection.ts`): one residual unknown per site and `indirect-branch-target-recovery` in `unsupported_branches`. - Ghidra address validation also covers the new addresses. Deliberately not attempted: telling a dispatch apart from an indirect tail call. On real Ghidra 12.1.4 both produce the same recovery failure (see Validation), so REA reports the uncertainty instead of guessing. Not included: the decompiler-failure handling from #487 (a separate follow-up), and sites in regions where Ghidra created no function. ## Contract and boundary impact - Semantic owner and earliest changed stage: Ghidra bridge native API boundary. - CLI and MCP/tool-catalog contract: additive. `analyze_function`/`inspect_native_api` output gains the optional `unresolved_indirect_branches` field, the evidence kind `indirect-branch`, and the `unsupported_branches` value `indirect-branch-target-recovery`. Existing fields are unchanged. - Provider, bridge, target-format, or platform compatibility: Ghidra only; other providers omit the field. - Evidence, artifact, provenance, or reconstruction contract: new facts are listing and decompiler-warning observations with their source recorded; no targets or case values are inferred. - Process execution, authorization, cleanup, or containment impact: none. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: output schemas regenerate in CI; no tracked metadata changes. ## Evidence and regression coverage - Tests added or updated: - `NativeApiInspection.test.ts`: residual unknowns and `unsupported_branches` for both outcomes; empty or absent inventory adds nothing; a branch without evidence is rejected. - `GhidraFunctionValues.test.ts`: a non-canonical branch address is rejected. - New real-Ghidra fixture `tests/conformance/ghidra/indirect-branches.S` (unbounded computed jump plus an indirect tail call) in the `aarch64-jump-table` lane, as ELF and, on arm64 hosts, Mach-O. The lane asserts the computed jump is reported and not mistaken for a jump table, and records the tail call's classification. - The existing relative-switch fixtures now assert that recovered switches are not reported as unresolved. - Base reproduction or other evidence: on `main` the field doesn't exist, so the fixture's computed jump leaves no trace in the dossier. - User-visible CLI/MCP output: see "Problem and expected behavior". - Remaining proof gaps: not run against the real `librenderscript-toolkit.so` from the issue thread; no Linux run. 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:focused -- src/application/native/NativeApiInspection.test.ts src/ghidra/GhidraFunctionValues.test.ts`: passed - `npm run check:fast`: passed - `npm run lint`, `npm run knip`: passed - `npm run docs:check`: passed - `npm run verify:ghidra:aarch64-jump-table` on an Apple Silicon Mac (Ghidra 12.1.4, JDK 21): `ok: true`. - Computed jump: reported as `jump_table_recovery_failed` with the decompiler warning, on ELF (`0x10000c`) and Mach-O (`0xc`). - Indirect tail call: also reported as `jump_table_recovery_failed` ("Could not recover jumptable at … Too many branches") on both formats. - All `relative-*` switch fixtures passed, including the new "not unresolved" check. Note on that run: on current `main` the lane stops early in the host-native native-value check, where `compare_functions` of a function against itself returns `unknown` instead of `unchanged`. Reproduced on `main` without this PR. The `comments` facet is empty with no declared coverage, and `calls` lacks relationship coverage, which looks related to #2450 (`b17487f4`). I skipped that one assertion locally to reach the fixtures this PR adds, and will report it separately. ## Compatibility, safety, and release - Breaking changes or migration steps: none; the field is optional and additive. - Real Hopper/Ghidra, browser, or OS coverage: real Ghidra on macOS arm64 only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: static analysis only; reads the existing listing and decompiler output. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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. ## Author readiness Human owner: @RishTheFish21 - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#5533
No description provided.