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 #3029] fix(ghidra): recover registered Borland SEH handler gaps #5568

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

📋 Pull Request Information

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

Base: main ← Head: fix/ghidra-delphi-seh-regions

📝 Commits (7)

  • c872381 fix(ghidra): recover registered Borland SEH handler gaps
  • 46d7013 fix(ghidra): verify handler recovery cleanup on updated upstream
  • 25736d7 fix(ghidra): gate SEH continuations and preserve boundary evidence
  • 299f82d Merge remote-tracking branch 'upstream/main' into fix/ghidra-delphi-seh-regions
  • 495089d fix(ghidra): bound SEH recovery and preserve containment provenance
  • 4917e8d fix(ghidra): retain instruction-level SEH boundaries and observations
  • b361a3d fix(ghidra): discard speculative SEH units and retain source provenance

📊 Changes

28 files changed (+1590 additions, -55 deletions)

View changed files

➕ bridge/ghidra/ReaGhidraBorlandSeh.java (+312 -0)
📝 bridge/ghidra/ReaGhidraBridge.java (+77 -20)
📝 docs/ghidra-provider.md (+26 -0)
➕ docs/specs/ghidra/borland-seh/plan.md (+134 -0)
➕ docs/specs/ghidra/borland-seh/spec.md (+46 -0)
➕ docs/specs/ghidra/borland-seh/tasks.md (+46 -0)
📝 package.json (+2 -0)
➕ scripts/lib/borland-seh-fixture.mjs (+61 -0)
➕ scripts/verify-real-ghidra-borland-seh.mjs (+379 -0)
📝 src/domain/flutter/flutterBuildAnalysis.ts (+1 -1)
📝 src/ghidra/GhidraAnalysisProfile.ts (+10 -1)
📝 src/ghidra/GhidraBridgeSources.ts (+1 -0)
📝 src/ghidra/GhidraClient.ts (+19 -5)
📝 src/ghidra/GhidraFunctionValues.test.ts (+24 -0)
📝 src/ghidra/GhidraFunctionValues.ts (+3 -0)
📝 src/ghidra/GhidraInventoryValues.test.ts (+105 -8)
📝 src/ghidra/GhidraInventoryValues.ts (+19 -0)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+30 -0)
📝 src/ghidra/GhidraSnapshotCache.test.ts (+2 -2)
📝 src/server/http/NodeHttpRequestOwner.ts (+2 -3)

...and 8 more files

📄 Description

Summary

Refs #2926. Recover registered Delphi/Borland PE32 SEH handler gaps in Ghidra's ephemeral function body, making handler addresses, calls and strings visible through existing CLI/MCP function queries. Known unrecovered registrations remain explicit limitations with partial callee coverage.

Problem and expected behavior

An exception handler entered through the Win32 SEH chain can lie between two observed function ranges without ordinary control-flow references. Recovery is bounded to unowned gaps and requires a supplied/imported Borland RTL symbol before interpreting bytes after a non-fallthrough jump. An arbitrary executable jump target leaves an explicit omission, never an inferred catch body. Related omission-reporting work: #2981.

Change and scope

One Ghidra-owned Java producer recognizes exact decoded zero-offset FS registration patterns, recovers only unowned executable gaps, respects defined data/independent functions, traverses a continuation justified by a supplied/imported RTL identity, and refreshes references using the caller-enabled Ghidra analyzers. Existing queries consume the corrected FunctionManager body. Diagnostics enter main's shared function-boundary producer, including procedure references. SEH omissions augment its coverage without replacing unresolved/indirect-call diagnostics. Analysis profile invalidation is limited to PE32/x86.

Real validation exposed an ownership-token race during JVM exit. After a validated session acknowledges shutdown, close can wait for the retained original child and retry full owned-group verification once. Child exit alone never authorizes deletion; unresolved cleanup retains files and supervision. Startup failures and forced cancellation retain their existing behavior.

Contract and boundary impact

  • Semantic owner: Ghidra function-body and reference producer before decompiler initialization; provider boundary parses coverage once.
  • Contribution scope: ordinary provider fix within existing POSIX ephemeral-database authority; no new target execution/provider/protection path, so an additional scope decision is not applicable.
  • CLI/MCP: existing function operations and containment Evidence limitations; optional relationship_coverage on producer callee results, preserving Evidence limitations.
  • Compatibility: PE32 x86 only; Windows P0 observes registrations without body mutation. Existing names/signatures and independent owners are preserved.
  • Evidence/provenance: registration observation is not proof of runtime execution; recognized omissions remain visible.
  • Target/cleanup: executable bytes unchanged; own bounded gaps only; group identity must be verified before runtime removal.
  • Package: ship the helper beside the bridge and require it in packed-bridge verification; no binaries/projects/build outputs committed.

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.

These are the owned Ghidra process, bridge scripts and ephemeral analysis database. The analyzed program is never executed; its bytes are never modified.

Evidence and regression coverage

  • Source-owned PE32 fixture verified through real Ghidra CLI/MCP, with a real producer probe for nonzero FS offsets, independently owned handlers and observe-only behavior.
  • The pre-review public reproduction used the old permissive jump heuristic. It has not been rerun with the stricter RTL-identity gate and is not proof of the current branch's recovery on that executable.
  • Typed malformed-coverage tests and provider projection regressions preserve limitations and locations. Client tests cover successful retry and retained files when group verification remains incomplete.
  • No actual Windows host verification; observe-only policy was exercised on POSIX. General register dataflow, other prologues, outside-span recovery and guessed RTL names remain outside scope.

Instruction inspection and call-target resolution now retain the same producer-owned SEH provenance as containment and function views. Reused path destinations must be decoded instruction starts, including already-owned handler entries. Recognized terminal flows remain static Ghidra classifications, with an explicit non-return caveat. The tar-listing fixture consumes the canonical packaged-source manifest rather than an obsolete duplicated source list.

Omitted or cancelled traversal clears only its newly decoded units and generated references, preserving pre-existing listing/references and earlier successful candidates. Procedure selectors and byte-match owners retain their SEH observations; callers, incoming procedure references, xrefs, instruction inspection and dossiers retain provenance from returned source addresses. Observations are deduplicated and unrelated queries do not inherit another function's SEH facts.

Representative output: a recognized handler jump without a supplied RTL identity retains the original function body, reports the omitted continuation in procedure_references limitations, and returns procedure_callees coverage partial alongside its existing indirect-call diagnostics.

  • 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 check — passed.
  • npm run verify:package — not completed on the current review revision. One attempt exceeded the packaged MCP startup probe's 5-second timeout; the next completed installation, then failed in the update fixture with ERR_HTTP_HEADERS_SENT at scripts/verify-package-update.mjs:29 while proxying registry responses. The preceding review revision passed full package verification; this is not a claim that the current full-package gate passed. Follow-up: #6038.
  • Latest focused suites — 238 passed across function/inventory contracts, snapshot admission, MCP Evidence, client lifecycle and bridge-source packaging on upstream ccc7da309. Both failing CI tests used stale observation-profile expectations; the snapshot test now explicitly rejects prior v5 semantics. Earlier revision: 122 passed, including the tar-listing regression.
  • node scripts/verify-real-ghidra-borland-seh.mjs after build — passed on Ghidra 12.1.4/JDK 21, darwin/arm64. Covers omitted/cancelled speculative-unit and generated-reference cleanup, preserved pre-existing listing/user references and earlier successful recovery; procedure-address selection, byte-match ownership, reverse callers/references/xrefs and incoming instruction/dossier provenance; unrelated-query controls; and the prior RTL, budget, ownership, containment and instruction-boundary cases. Target unchanged, runtime empty and process lineage positively verified empty.
  • npm run docs:check — passed; the old #3022 drift is resolved in main.

No controlled before/after speed benchmark, live model token usage, CPU measurement or process-family peak-memory comparison was performed for this recovery pass; no performance gain is claimed.

Compatibility, safety, and release

Normalized public result shapes remain unchanged. The internal bridge now requires observation envelopes for procedure_address, search_bytes and xrefs. POSIX PE32/x86 recovery profile v5 includes speculative-unit cleanup; shared function/address observation profile v6 invalidates older results for every format. Existing Windows P0 read-only policy remains authoritative. Recovery has one analysis-wide admission budget (16,384 visits, 64 KiB newly decoded instruction bytes, 4,096 pending addresses), restricts each disassembly request to at most 15 x86 bytes, and stops at unresolved flow, ownership and data boundaries; known omissions are retained. Specifications: docs/specs/ghidra/borland-seh/.

Author readiness

Human owner: @matbrgz

  • 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.

Before merge

  • This PR addresses a concrete problem.
  • Material scope and authority questions are resolved.
  • The PR has one focused outcome and a conventional title.
  • Related issue and alternative PR are linked.
  • Tests cover changed behavior and meaningful failure paths.
  • Owning docs, contracts, and package metadata are updated.
  • Representative user-visible output is included.
  • Final diff reviewed 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/3029 **Author:** [@matbrgz](https://github.com/matbrgz) **Created:** 10/13/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/ghidra-delphi-seh-regions` --- ### 📝 Commits (7) - [`c872381`](https://github.com/morluto/rea/commit/c8723811f05f6e6747f71db79025f5b4675beb0c) fix(ghidra): recover registered Borland SEH handler gaps - [`46d7013`](https://github.com/morluto/rea/commit/46d70133e94447a6ef3b6d72a03ded4e0d01cbb8) fix(ghidra): verify handler recovery cleanup on updated upstream - [`25736d7`](https://github.com/morluto/rea/commit/25736d74faf2b5d8b10a724d7362926ff96ab1de) fix(ghidra): gate SEH continuations and preserve boundary evidence - [`299f82d`](https://github.com/morluto/rea/commit/299f82dc2ca9a32643ae09a5745c1a7c21ae12b5) Merge remote-tracking branch 'upstream/main' into fix/ghidra-delphi-seh-regions - [`495089d`](https://github.com/morluto/rea/commit/495089d1b6c90e769d4691dfa85f1c9ece863bab) fix(ghidra): bound SEH recovery and preserve containment provenance - [`4917e8d`](https://github.com/morluto/rea/commit/4917e8ded62138894f41045c601a5927984a2460) fix(ghidra): retain instruction-level SEH boundaries and observations - [`b361a3d`](https://github.com/morluto/rea/commit/b361a3dd2eb530a9dfebbf7592f6514df842d730) fix(ghidra): discard speculative SEH units and retain source provenance ### 📊 Changes **28 files changed** (+1590 additions, -55 deletions) <details> <summary>View changed files</summary> ➕ `bridge/ghidra/ReaGhidraBorlandSeh.java` (+312 -0) 📝 `bridge/ghidra/ReaGhidraBridge.java` (+77 -20) 📝 `docs/ghidra-provider.md` (+26 -0) ➕ `docs/specs/ghidra/borland-seh/plan.md` (+134 -0) ➕ `docs/specs/ghidra/borland-seh/spec.md` (+46 -0) ➕ `docs/specs/ghidra/borland-seh/tasks.md` (+46 -0) 📝 `package.json` (+2 -0) ➕ `scripts/lib/borland-seh-fixture.mjs` (+61 -0) ➕ `scripts/verify-real-ghidra-borland-seh.mjs` (+379 -0) 📝 `src/domain/flutter/flutterBuildAnalysis.ts` (+1 -1) 📝 `src/ghidra/GhidraAnalysisProfile.ts` (+10 -1) 📝 `src/ghidra/GhidraBridgeSources.ts` (+1 -0) 📝 `src/ghidra/GhidraClient.ts` (+19 -5) 📝 `src/ghidra/GhidraFunctionValues.test.ts` (+24 -0) 📝 `src/ghidra/GhidraFunctionValues.ts` (+3 -0) 📝 `src/ghidra/GhidraInventoryValues.test.ts` (+105 -8) 📝 `src/ghidra/GhidraInventoryValues.ts` (+19 -0) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+30 -0) 📝 `src/ghidra/GhidraSnapshotCache.test.ts` (+2 -2) 📝 `src/server/http/NodeHttpRequestOwner.ts` (+2 -3) _...and 8 more files_ </details> ### 📄 Description ## Summary Refs #2926. Recover registered Delphi/Borland PE32 SEH handler gaps in Ghidra's ephemeral function body, making handler addresses, calls and strings visible through existing CLI/MCP function queries. Known unrecovered registrations remain explicit limitations with partial callee coverage. ## Problem and expected behavior An exception handler entered through the Win32 SEH chain can lie between two observed function ranges without ordinary control-flow references. Recovery is bounded to unowned gaps and requires a supplied/imported Borland RTL symbol before interpreting bytes after a non-fallthrough jump. An arbitrary executable jump target leaves an explicit omission, never an inferred catch body. Related omission-reporting work: #2981. ## Change and scope One Ghidra-owned Java producer recognizes exact decoded zero-offset FS registration patterns, recovers only unowned executable gaps, respects defined data/independent functions, traverses a continuation justified by a supplied/imported RTL identity, and refreshes references using the caller-enabled Ghidra analyzers. Existing queries consume the corrected FunctionManager body. Diagnostics enter main's shared function-boundary producer, including procedure references. SEH omissions augment its coverage without replacing unresolved/indirect-call diagnostics. Analysis profile invalidation is limited to PE32/x86. Real validation exposed an ownership-token race during JVM exit. After a validated session acknowledges shutdown, close can wait for the retained original child and retry full owned-group verification once. Child exit alone never authorizes deletion; unresolved cleanup retains files and supervision. Startup failures and forced cancellation retain their existing behavior. ## Contract and boundary impact - Semantic owner: Ghidra function-body and reference producer before decompiler initialization; provider boundary parses coverage once. - Contribution scope: ordinary provider fix within existing POSIX ephemeral-database authority; no new target execution/provider/protection path, so an additional scope decision is not applicable. - CLI/MCP: existing function operations and containment Evidence limitations; optional `relationship_coverage` on producer callee results, preserving Evidence limitations. - Compatibility: PE32 x86 only; Windows P0 observes registrations without body mutation. Existing names/signatures and independent owners are preserved. - Evidence/provenance: registration observation is not proof of runtime execution; recognized omissions remain visible. - Target/cleanup: executable bytes unchanged; own bounded gaps only; group identity must be verified before runtime removal. - Package: ship the helper beside the bridge and require it in packed-bridge verification; no binaries/projects/build outputs committed. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [x] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. These are the owned Ghidra process, bridge scripts and ephemeral analysis database. The analyzed program is never executed; its bytes are never modified. ## Evidence and regression coverage - Source-owned PE32 fixture verified through real Ghidra CLI/MCP, with a real producer probe for nonzero FS offsets, independently owned handlers and observe-only behavior. - The pre-review public reproduction used the old permissive jump heuristic. It has not been rerun with the stricter RTL-identity gate and is not proof of the current branch's recovery on that executable. - Typed malformed-coverage tests and provider projection regressions preserve limitations and locations. Client tests cover successful retry and retained files when group verification remains incomplete. - No actual Windows host verification; observe-only policy was exercised on POSIX. General register dataflow, other prologues, outside-span recovery and guessed RTL names remain outside scope. Instruction inspection and call-target resolution now retain the same producer-owned SEH provenance as containment and function views. Reused path destinations must be decoded instruction starts, including already-owned handler entries. Recognized terminal flows remain static Ghidra classifications, with an explicit non-return caveat. The tar-listing fixture consumes the canonical packaged-source manifest rather than an obsolete duplicated source list. Omitted or cancelled traversal clears only its newly decoded units and generated references, preserving pre-existing listing/references and earlier successful candidates. Procedure selectors and byte-match owners retain their SEH observations; callers, incoming procedure references, xrefs, instruction inspection and dossiers retain provenance from returned source addresses. Observations are deduplicated and unrelated queries do not inherit another function's SEH facts. Representative output: a recognized handler jump without a supplied RTL identity retains the original function body, reports the omitted continuation in `procedure_references` limitations, and returns `procedure_callees` coverage `partial` alongside its existing indirect-call diagnostics. - [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 check` — passed. - `npm run verify:package` — **not completed on the current review revision**. One attempt exceeded the packaged MCP startup probe's 5-second timeout; the next completed installation, then failed in the update fixture with `ERR_HTTP_HEADERS_SENT` at `scripts/verify-package-update.mjs:29` while proxying registry responses. The preceding review revision passed full package verification; this is not a claim that the current full-package gate passed. Follow-up: [#6038](https://github.com/morluto/rea/issues/6038). - Latest focused suites — **238 passed** across function/inventory contracts, snapshot admission, MCP Evidence, client lifecycle and bridge-source packaging on upstream `ccc7da309`. Both failing CI tests used stale observation-profile expectations; the snapshot test now explicitly rejects prior v5 semantics. Earlier revision: 122 passed, including the tar-listing regression. - `node scripts/verify-real-ghidra-borland-seh.mjs` after build — passed on Ghidra 12.1.4/JDK 21, darwin/arm64. Covers omitted/cancelled speculative-unit and generated-reference cleanup, preserved pre-existing listing/user references and earlier successful recovery; procedure-address selection, byte-match ownership, reverse callers/references/xrefs and incoming instruction/dossier provenance; unrelated-query controls; and the prior RTL, budget, ownership, containment and instruction-boundary cases. Target unchanged, runtime empty and process lineage positively verified empty. - `npm run docs:check` — passed; the old #3022 drift is resolved in main. No controlled before/after speed benchmark, live model token usage, CPU measurement or process-family peak-memory comparison was performed for this recovery pass; no performance gain is claimed. ## Compatibility, safety, and release Normalized public result shapes remain unchanged. The internal bridge now requires observation envelopes for procedure_address, search_bytes and xrefs. POSIX PE32/x86 recovery profile v5 includes speculative-unit cleanup; shared function/address observation profile v6 invalidates older results for every format. Existing Windows P0 read-only policy remains authoritative. Recovery has one analysis-wide admission budget (16,384 visits, 64 KiB newly decoded instruction bytes, 4,096 pending addresses), restricts each disassembly request to at most 15 x86 bytes, and stops at unresolved flow, ownership and data boundaries; known omissions are retained. Specifications: `docs/specs/ghidra/borland-seh/`. ## Author readiness Human owner: @matbrgz - [ ] 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. ## Before merge - [x] This PR addresses a concrete problem. - [x] Material scope and authority questions are resolved. - [x] The PR has one focused outcome and a conventional title. - [x] Related issue and alternative PR are linked. - [x] Tests cover changed behavior and meaningful failure paths. - [x] Owning docs, contracts, and package metadata are updated. - [x] Representative user-visible output is included. - [x] Final diff reviewed for secrets, unrelated cleanup and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#5568
No description provided.