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 #6402] [MERGED] fix(javascript): associate requested bindings only with resolved native addons #7337

New issue
Closed
opened 2026-11-01 21:47:10 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:47:10 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6402
Author: @pablodiazjorge
Created: 10/22/2026
Status: ✅ Merged
Merged: 10/23/2026
Merged by: @morluto

Base: main ← Head: fix/electron-native-addon-js-resolution

📝 Commits (3)

  • e04697c fix(javascript): associate requested bindings only with resolved native addons
  • cdeda06 test(javascript): cover the exact native addon association
  • 6fe1159 chore(javascript): resolve native-addon merge conflict

📊 Changes

2 files changed (+59 additions, -1 deletions)

View changed files

📝 src/application/javascript/ElectronBoundaryGraphNative.ts (+7 -1)
📝 tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts (+52 -0)

📄 Description

Summary

Fixes #5929. When require("./addon.node") resolves through extension probing to addon.node.js and no addon.node exists, the application graph added an associate-native-addon-requested-exports edge from that JavaScript file, with a limitation saying the .node artifact path is resolved. The same result reported resolved_native_addon_bindings: 0. The association now requires the resolved file to be classified as native-addon, the rule the summary already uses.

Thanks to @coygeek for the report and the three-case reproduction.

Problem and expected behavior

addNativeBinding in ElectronBoundaryGraphNative.ts took any file node at the resolved path and only checked that it existed before adding the association. resolveArtifactPath allows the .js fallback, so a JavaScript asset could receive a native-addon association. The summary's resolved_native_addon_bindings (ElectronBoundaryAnalysis.ts) already requires kind: "native-addon".

Expected, as the issue asks: the JavaScript fallback keeps its requested binding and ordinary dependency information, with no native-addon association; a missing target stays without one; an exact .node target keeps its association.

Change and scope

  • src/application/javascript/ElectronBoundaryGraphNative.ts: the addon node is taken only when context.filesByPath classifies the resolved file as native-addon; otherwise no association edge is added.
  • Unchanged: the requested-binding node (including its resolved_path), the map-native-addon-binding edge from the requesting file, and the exact-native case.
  • The merge retains main's resolveArtifactPathByContext resolver, including JSON-document and module-kind context, and applies the native-addon file-kind guard to its result. Summary and graph now both use the context-aware resolver and the same file-kind rule.

Contract and boundary impact

  • Semantic owner and earliest changed stage: native-addon graph projection (addNativeBinding).
  • Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable.
  • CLI and MCP/tool-catalog contract: analyze / analyze_javascript_application results no longer contain this association for non-native resolved files; no schema or catalog change.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: one inferred edge is no longer emitted when its source is not a native addon; the graph and the summary now agree on file kind.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • 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/filesystem/javascript-applications/electronApplicationAnalysis.test.ts, new describe "native addon association", through reconstructJavaScriptArtifact, with main.js requiring ./addon.node and an addon.node.js beside it:
    • without an exact addon.node: one requested binding, zero resolved native bindings, one native-export node, and no associate-native-addon-requested-exports edge;
    • with an exact addon.node (inventory-only bytes, never loaded): one resolved native binding and exactly one association, from the native-addon node with resolved_path addon.node, so the test also fails if valid associations stop being emitted.
  • Base reproduction or other evidence: the issue's three cases, rebuilt as a temporary local test that calls buildJavaScriptArtifactGraph directly (not committed):
    • on main 7af1b2068: the JavaScript fallback gets one association (expected [ Array(1) ] to deeply equal []); the missing target has none; the exact native target has one from a native-addon node;
    • with the change: the fallback has none; the other two are unchanged.
  • User-visible CLI/MCP output (if applicable): not captured.
  • Remaining proof gaps: the original Windows run could not execute the committed public-workflow test because packaged native controls were unavailable. Both committed association cases passed in the macOS merge-head run below. MCP and ASAR inputs were not 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

Current conflict-resolution head 6fe11598bd42b874a9fe29148b2c94b34d4c0370, merging main 572d0c234089605f120dcfea340f11e38a3c3705 (macOS, Node 24.22.1/npm 11.16.0):

  • Retained main's context-aware path resolution and this PR's native-addon classification guard. The diff against the merged main remains limited to the original two files.
  • npm run test:focused -- tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts src/application/javascript/JavaScriptArtifactPathResolution.test.ts src/application/javascript/JavaScriptArtifactPathResolution.syntheticRootEscape.test.ts tests/boundary/filesystem/javascriptArtifactGraphObservationLookup.test.ts: 314 tests passed in 4 files (6.33s), including both committed native-addon association cases.
  • npm run check and formatting checks on both changed files passed. Normal pre-commit and pre-push (check:fast) checks passed.
  • No full suite, Windows rerun, MCP or ASAR validation on this merge head. Earlier validation below is historical.

Windows 11 x64 10.0.26300, Node 24.18.0, on main 7af1b2068:

  • The temporary graph-level test above: 3 of 3 pass with the change; on main the fallback case fails and the two controls pass.
  • npx vitest run src/application/javascript src/domain/javascript tests/boundary/filesystem/javascriptArtifactGraphObservationLookup.test.ts: 153 files, 4270 passed, 6 skipped.
  • npx vitest run tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts -t "resolved native addon": does not run on this host (REA Windows native controls are unavailable: Missing packaged Windows native file native/windows/build/manifest.json).
  • npm run check:fast: typecheck and lint pass.
  • npx oxfmt --check on the changed files: pass.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Consumers that relied on this association from a JavaScript asset no longer receive it; the issue describes it as incorrect.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; static JavaScript analysis only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none; no target is executed or loaded.

Author readiness

Human owner: @pablodiazjorge

  • 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 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/6402 **Author:** [@pablodiazjorge](https://github.com/pablodiazjorge) **Created:** 10/22/2026 **Status:** ✅ Merged **Merged:** 10/23/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/electron-native-addon-js-resolution` --- ### 📝 Commits (3) - [`e04697c`](https://github.com/morluto/rea/commit/e04697c3dc3e8ea8482c769f4972361f99b87681) fix(javascript): associate requested bindings only with resolved native addons - [`cdeda06`](https://github.com/morluto/rea/commit/cdeda062f8198f2b16cdad8254e5158ede527b5b) test(javascript): cover the exact native addon association - [`6fe1159`](https://github.com/morluto/rea/commit/6fe11598bd42b874a9fe29148b2c94b34d4c0370) chore(javascript): resolve native-addon merge conflict ### 📊 Changes **2 files changed** (+59 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/application/javascript/ElectronBoundaryGraphNative.ts` (+7 -1) 📝 `tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts` (+52 -0) </details> ### 📄 Description ## Summary Fixes #5929. When `require("./addon.node")` resolves through extension probing to `addon.node.js` and no `addon.node` exists, the application graph added an `associate-native-addon-requested-exports` edge from that JavaScript file, with a limitation saying the `.node` artifact path is resolved. The same result reported `resolved_native_addon_bindings: 0`. The association now requires the resolved file to be classified as `native-addon`, the rule the summary already uses. Thanks to @coygeek for the report and the three-case reproduction. ## Problem and expected behavior `addNativeBinding` in `ElectronBoundaryGraphNative.ts` took any file node at the resolved path and only checked that it existed before adding the association. `resolveArtifactPath` allows the `.js` fallback, so a JavaScript asset could receive a native-addon association. The summary's `resolved_native_addon_bindings` (`ElectronBoundaryAnalysis.ts`) already requires `kind: "native-addon"`. Expected, as the issue asks: the JavaScript fallback keeps its requested binding and ordinary dependency information, with no native-addon association; a missing target stays without one; an exact `.node` target keeps its association. ## Change and scope - `src/application/javascript/ElectronBoundaryGraphNative.ts`: the addon node is taken only when `context.filesByPath` classifies the resolved file as `native-addon`; otherwise no association edge is added. - Unchanged: the requested-binding node (including its `resolved_path`), the `map-native-addon-binding` edge from the requesting file, and the exact-native case. - The merge retains main's `resolveArtifactPathByContext` resolver, including JSON-document and module-kind context, and applies the native-addon file-kind guard to its result. Summary and graph now both use the context-aware resolver and the same file-kind rule. ## Contract and boundary impact - Semantic owner and earliest changed stage: native-addon graph projection (`addNativeBinding`). - Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable. - CLI and MCP/tool-catalog contract: `analyze` / `analyze_javascript_application` results no longer contain this association for non-native resolved files; no schema or catalog change. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: one inferred edge is no longer emitted when its source is not a native addon; the graph and the summary now agree on file kind. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [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/filesystem/javascript-applications/electronApplicationAnalysis.test.ts`, new describe "native addon association", through `reconstructJavaScriptArtifact`, with `main.js` requiring `./addon.node` and an `addon.node.js` beside it: - without an exact `addon.node`: one requested binding, zero resolved native bindings, one `native-export` node, and no `associate-native-addon-requested-exports` edge; - with an exact `addon.node` (inventory-only bytes, never loaded): one resolved native binding and exactly one association, from the `native-addon` node with `resolved_path` `addon.node`, so the test also fails if valid associations stop being emitted. - Base reproduction or other evidence: the issue's three cases, rebuilt as a temporary local test that calls `buildJavaScriptArtifactGraph` directly (not committed): - on main `7af1b2068`: the JavaScript fallback gets one association (`expected [ Array(1) ] to deeply equal []`); the missing target has none; the exact native target has one from a `native-addon` node; - with the change: the fallback has none; the other two are unchanged. - User-visible CLI/MCP output (if applicable): not captured. - Remaining proof gaps: the original Windows run could not execute the committed public-workflow test because packaged native controls were unavailable. Both committed association cases passed in the macOS merge-head run below. MCP and ASAR inputs were not 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 Current conflict-resolution head `6fe11598bd42b874a9fe29148b2c94b34d4c0370`, merging main `572d0c234089605f120dcfea340f11e38a3c3705` (macOS, Node 24.22.1/npm 11.16.0): - Retained main's context-aware path resolution and this PR's native-addon classification guard. The diff against the merged main remains limited to the original two files. - `npm run test:focused -- tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts src/application/javascript/JavaScriptArtifactPathResolution.test.ts src/application/javascript/JavaScriptArtifactPathResolution.syntheticRootEscape.test.ts tests/boundary/filesystem/javascriptArtifactGraphObservationLookup.test.ts`: 314 tests passed in 4 files (6.33s), including both committed native-addon association cases. - `npm run check` and formatting checks on both changed files passed. Normal pre-commit and pre-push (`check:fast`) checks passed. - No full suite, Windows rerun, MCP or ASAR validation on this merge head. Earlier validation below is historical. Windows 11 x64 10.0.26300, Node 24.18.0, on main `7af1b2068`: - The temporary graph-level test above: 3 of 3 pass with the change; on main the fallback case fails and the two controls pass. - `npx vitest run src/application/javascript src/domain/javascript tests/boundary/filesystem/javascriptArtifactGraphObservationLookup.test.ts`: 153 files, 4270 passed, 6 skipped. - `npx vitest run tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts -t "resolved native addon"`: does not run on this host (`REA Windows native controls are unavailable: Missing packaged Windows native file native/windows/build/manifest.json`). - `npm run check:fast`: typecheck and lint pass. - `npx oxfmt --check` on the changed files: pass. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Consumers that relied on this association from a JavaScript asset no longer receive it; the issue describes it as incorrect. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; static JavaScript analysis only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none; no target is executed or loaded. ## Author readiness Human owner: @pablodiazjorge - [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. ## 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. - [ ] 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-11-01 21:47:10 +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#7337
No description provided.