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 #2981] [CLOSED] fix(ghidra): warn when Borland SEH handlers fall outside the function body #5535

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2981
Author: @sx4im
Created: 10/13/2026
Status: ❌ Closed

Base: main ← Head: fix/2926-seh-handler-limitations

📝 Commits (7)

  • b8b88f8 fix(ghidra): warn when Borland SEH handlers fall outside the function body
  • 8611926 fix(ghidra): tighten SEH prologue matching and stream boundary scan
  • b40ba8d fix(ghidra): gate SEH matching on 32-bit x86 and preserve handler address space
  • eb46d69 fix(ghidra): harden SEH detection against non-Win32 targets and complete reference coverage
  • b90ff8b fix(ghidra): recognize zero-valued register FS slots in SEH detection
  • a61cccd fix(ghidra): stop SEH xor proof at any control-flow instruction
  • 961672c fix(ghidra): qualify SEH attribution, hoist target check, require single-entry xor

📊 Changes

6 files changed (+388 additions, -51 deletions)

View changed files

📝 bridge/ghidra/ReaGhidraBridge.java (+347 -45)
📝 docs/ghidra-provider.md (+7 -3)
📝 src/ghidra/GhidraAnalysisProfile.ts (+2 -2)
📝 src/ghidra/GhidraFunctionValues.test.ts (+30 -0)
📝 src/ghidra/GhidraFunctionValues.ts (+1 -0)
📝 tests/boundary/mcp/ghidraEvidenceMcp.test.ts (+1 -1)

📄 Description

Summary

Fixes #2926. Delphi and C++Builder register exception handlers through the SEH chain with a push imm32; push fs:[reg]; mov fs:[reg], esp prologue. Ghidra's flow model never follows that chain, so the handler block lands outside the analyzed function body, and REA reported the function's callees, strings, and references as complete with no hint that a handler region was missing.

Problem and expected behavior

Smallest trigger: any Delphi function containing a try block. The compiler emits the SEH registration prologue at the function head; Ghidra keeps the pushed handler address out of the function body because nothing in its flow graph reaches it. REA's function views then silently presented incomplete results as complete. Expected: a reader of procedure_info, procedure_callees, or analyze_function is told when a known handler region is excluded, the same way #2326/#2360 handled truncated bodies from terminal calls.

Change and scope

bridge/ghidra/ReaGhidraBridge.java gains sehHandlerLimitations, which scans a function's instructions for the consecutive prologue triple (push with a 32-bit scalar operand, push with an fs: segment memory operand, mov to an fs: segment operand from esp). When the pushed handler address falls outside function.getBody(), the six function views that already carry terminal-call qualifications (procedure_pseudo_code, procedure_assembly, read_function_instructions, procedure_callees, procedure_callers, procedure_info, plus the analyze_function dossier) include an Evidence limitation naming the registration site and the excluded handler address.

I took the issue's report branch rather than the seed-as-code branch: the bridge only observes and reports, it does not rewrite Ghidra function bodies. Detection is strict by design. A partial match emits nothing, so a missed variant keeps the old behavior instead of producing noise.

src/ghidra/GhidraAnalysisProfile.ts versions the boundary-observation contract to ghidra-terminal-call-limitations-v3 so older snapshots cannot replay unqualified results. docs/ghidra-provider.md documents the new observation.

Follow the contribution scope. Unresolved scope, authority, side effects, or required verification block integration: not applicable, this is an ordinary fix within existing boundaries (read-only observation, no target execution, injection, mutation, or protection recovery).

Contract and boundary impact

  • Semantic owner and earliest changed stage: Ghidra provider bridge (ReaGhidraBridge.java), function-view result shaping.
  • Contribution scope fit and linked maintainer decision: ordinary bug fix within existing boundaries; no maintainer scope decision required.
  • CLI and MCP/tool-catalog contract: unchanged tool shapes; results may carry additional limitation strings.
  • Provider, bridge, target-format, or platform compatibility: bridge-only; the pattern is x86-32 specific and inert elsewhere (a 32-bit push imm32 scalar never matches in 16-bit code, and the fs: triple does not occur in 64-bit code).
  • Evidence, artifact, provenance, or reconstruction contract: function_boundary_observations v2 to v3; snapshots recorded under v2 fail profile match on replay, which is the intended invalidation.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata, package, or installation impact: none.

Expected effects:

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

Evidence and regression coverage

  • Tests added or updated: tests/boundary/mcp/ghidraEvidenceMcp.test.ts now expects the v3 contract string.
  • Base reproduction or other evidence: the updated test failed against the v2 profile (red) and passes after the bump (green). The Java detection itself could not be executed here; every Ghidra API call it uses (getMnemonicString, getNumOperands, getOpObjects, Scalar/Register checks, getDefaultOperandRepresentation, function.getBody().contains) already appears in the same file, and the file parses clean under tree-sitter's Java grammar.
  • User-visible CLI/MCP output (if applicable): a new limitation string, e.g. "Ghidra Listing shows a Borland/Delphi SEH frame registration at 0x5353ac (push 0x5355c3 followed by fs-segment stack chaining); the handler 0x5355c3 lies outside this procedure's body, so callees, strings, and cross-references may omit the handler region."
  • Remaining proof gaps: no execution against a real Ghidra instance with a Delphi binary; the real-Ghidra CI lane is the first place this runs against live analysis.

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 -- tests/boundary/mcp/ghidraEvidenceMcp.test.ts — 4/4 passed (1 failed before the profile change, confirming the red step)
  • npm run test:focused -- src/ghidra/GhidraFunctionValues.test.ts — 50/50 passed
  • npm run test:focused -- src/ghidra/GhidraProvider.behavior.test.ts src/ghidra/GhidraSnapshotCache.test.ts — 60/60 passed
  • npm run check:fast — typecheck and lint green
  • npm run docs:check — green
  • npm run verify:test-discovery — 1112 test files, green

Compatibility, safety, and release

  • Breaking changes or migration steps: none. The v2 to v3 contract bump intentionally invalidates old analysis snapshots on replay; they re-run instead of replaying unqualified results.
  • Real Hopper/Ghidra, browser, or OS coverage: real Ghidra lane unavailable in this sandbox (no Ghidra installed). Stated plainly rather than assumed; the detection runs first in CI's real-Ghidra lane.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: read-only observation of the analyzed program; no new process, network, or mutation surface.

Before merge

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

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/2981 **Author:** [@sx4im](https://github.com/sx4im) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/2926-seh-handler-limitations` --- ### 📝 Commits (7) - [`b8b88f8`](https://github.com/morluto/rea/commit/b8b88f83cec1130646cb27c77726dec2824b12bb) fix(ghidra): warn when Borland SEH handlers fall outside the function body - [`8611926`](https://github.com/morluto/rea/commit/8611926cfaae0ebcae57b6977d09ce7e255b2921) fix(ghidra): tighten SEH prologue matching and stream boundary scan - [`b40ba8d`](https://github.com/morluto/rea/commit/b40ba8d50e84893e76e43dde0f502e6e8bc21682) fix(ghidra): gate SEH matching on 32-bit x86 and preserve handler address space - [`eb46d69`](https://github.com/morluto/rea/commit/eb46d6958a1c6e8320d9c1cf3f024dea27934c96) fix(ghidra): harden SEH detection against non-Win32 targets and complete reference coverage - [`b90ff8b`](https://github.com/morluto/rea/commit/b90ff8b73975f77a507231cc97e8feb405f201f1) fix(ghidra): recognize zero-valued register FS slots in SEH detection - [`a61cccd`](https://github.com/morluto/rea/commit/a61cccdba5a1a44eddb73567cfcbd9939bf74bd2) fix(ghidra): stop SEH xor proof at any control-flow instruction - [`961672c`](https://github.com/morluto/rea/commit/961672cd5fe13026ee2f8dbf90fd4bb349fdff45) fix(ghidra): qualify SEH attribution, hoist target check, require single-entry xor ### 📊 Changes **6 files changed** (+388 additions, -51 deletions) <details> <summary>View changed files</summary> 📝 `bridge/ghidra/ReaGhidraBridge.java` (+347 -45) 📝 `docs/ghidra-provider.md` (+7 -3) 📝 `src/ghidra/GhidraAnalysisProfile.ts` (+2 -2) 📝 `src/ghidra/GhidraFunctionValues.test.ts` (+30 -0) 📝 `src/ghidra/GhidraFunctionValues.ts` (+1 -0) 📝 `tests/boundary/mcp/ghidraEvidenceMcp.test.ts` (+1 -1) </details> ### 📄 Description ## Summary Fixes #2926. Delphi and C++Builder register exception handlers through the SEH chain with a `push imm32; push fs:[reg]; mov fs:[reg], esp` prologue. Ghidra's flow model never follows that chain, so the handler block lands outside the analyzed function body, and REA reported the function's callees, strings, and references as complete with no hint that a handler region was missing. ## Problem and expected behavior Smallest trigger: any Delphi function containing a `try` block. The compiler emits the SEH registration prologue at the function head; Ghidra keeps the pushed handler address out of the function body because nothing in its flow graph reaches it. REA's function views then silently presented incomplete results as complete. Expected: a reader of `procedure_info`, `procedure_callees`, or `analyze_function` is told when a known handler region is excluded, the same way #2326/#2360 handled truncated bodies from terminal calls. ## Change and scope `bridge/ghidra/ReaGhidraBridge.java` gains `sehHandlerLimitations`, which scans a function's instructions for the consecutive prologue triple (`push` with a 32-bit scalar operand, `push` with an `fs:` segment memory operand, `mov` to an `fs:` segment operand from `esp`). When the pushed handler address falls outside `function.getBody()`, the six function views that already carry terminal-call qualifications (`procedure_pseudo_code`, `procedure_assembly`, `read_function_instructions`, `procedure_callees`, `procedure_callers`, `procedure_info`, plus the `analyze_function` dossier) include an Evidence limitation naming the registration site and the excluded handler address. I took the issue's report branch rather than the seed-as-code branch: the bridge only observes and reports, it does not rewrite Ghidra function bodies. Detection is strict by design. A partial match emits nothing, so a missed variant keeps the old behavior instead of producing noise. `src/ghidra/GhidraAnalysisProfile.ts` versions the boundary-observation contract to `ghidra-terminal-call-limitations-v3` so older snapshots cannot replay unqualified results. `docs/ghidra-provider.md` documents the new observation. Follow the contribution scope. Unresolved scope, authority, side effects, or required verification block integration: not applicable, this is an ordinary fix within existing boundaries (read-only observation, no target execution, injection, mutation, or protection recovery). ## Contract and boundary impact - Semantic owner and earliest changed stage: Ghidra provider bridge (`ReaGhidraBridge.java`), function-view result shaping. - Contribution scope fit and linked maintainer decision: ordinary bug fix within existing boundaries; no maintainer scope decision required. - CLI and MCP/tool-catalog contract: unchanged tool shapes; results may carry additional limitation strings. - Provider, bridge, target-format, or platform compatibility: bridge-only; the pattern is x86-32 specific and inert elsewhere (a 32-bit `push imm32` scalar never matches in 16-bit code, and the `fs:` triple does not occur in 64-bit code). - Evidence, artifact, provenance, or reconstruction contract: `function_boundary_observations` v2 to v3; snapshots recorded under v2 fail profile match on replay, which is the intended invalidation. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata, package, or installation impact: none. Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/mcp/ghidraEvidenceMcp.test.ts` now expects the v3 contract string. - Base reproduction or other evidence: the updated test failed against the v2 profile (red) and passes after the bump (green). The Java detection itself could not be executed here; every Ghidra API call it uses (`getMnemonicString`, `getNumOperands`, `getOpObjects`, `Scalar`/`Register` checks, `getDefaultOperandRepresentation`, `function.getBody().contains`) already appears in the same file, and the file parses clean under tree-sitter's Java grammar. - User-visible CLI/MCP output (if applicable): a new limitation string, e.g. "Ghidra Listing shows a Borland/Delphi SEH frame registration at 0x5353ac (push 0x5355c3 followed by fs-segment stack chaining); the handler 0x5355c3 lies outside this procedure's body, so callees, strings, and cross-references may omit the handler region." - Remaining proof gaps: no execution against a real Ghidra instance with a Delphi binary; the real-Ghidra CI lane is the first place this runs against live analysis. 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 -- tests/boundary/mcp/ghidraEvidenceMcp.test.ts` — 4/4 passed (1 failed before the profile change, confirming the red step) - `npm run test:focused -- src/ghidra/GhidraFunctionValues.test.ts` — 50/50 passed - `npm run test:focused -- src/ghidra/GhidraProvider.behavior.test.ts src/ghidra/GhidraSnapshotCache.test.ts` — 60/60 passed - `npm run check:fast` — typecheck and lint green - `npm run docs:check` — green - `npm run verify:test-discovery` — 1112 test files, green ## Compatibility, safety, and release - Breaking changes or migration steps: none. The v2 to v3 contract bump intentionally invalidates old analysis snapshots on replay; they re-run instead of replaying unqualified results. - Real Hopper/Ghidra, browser, or OS coverage: real Ghidra lane unavailable in this sandbox (no Ghidra installed). Stated plainly rather than assumed; the detection runs first in CI's real-Ghidra lane. - Package or release metadata impact: none. - Security, privacy, process, or containment review: read-only observation of the analyzed program; no new process, network, or mutation surface. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:07:23 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#5535
No description provided.