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 #6832] [MERGED] fix(windows): explain when Windows refuses to load the verified native addon #7422

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6832
Author: @dark13b
Created: 10/23/2026
Status: ✅ Merged
Merged: 10/24/2026
Merged by: @morluto

Base: main ← Head: fix/windows-native-block-and-posix-hopper-paths

📝 Commits (1)

  • 0c03802 fix(windows): explain when Windows refuses to load the verified native addon

📊 Changes

5 files changed (+65 additions, -10 deletions)

View changed files

📝 docs/user-visible-errors.csv (+1 -0)
📝 docs/windows-ghidra-p0.md (+5 -2)
📝 src/process/WindowsAuthority.ts (+9 -6)
📝 src/windows/WindowsNativeLoader.test.ts (+29 -0)
📝 src/windows/WindowsNativeLoader.ts (+21 -2)

📄 Description

Summary

Fixes #5723

When Windows refuses to load rea-windows-x64.node (for example Smart App Control or an App Control policy), rea doctor and the provider diagnostics told the user to restore or rebuild the native files. The file had already passed the manifest version and SHA-256 checks, so that advice cannot help. This reports the refusal as its own failure stage with accurate guidance.

Problem and expected behavior

Smallest trigger: the loader's loadArtifact() throws because the OS blocked the module load (the report quotes "An Application Control policy has blocked this file").

Before: loadWindowsNativeAuthority caught that in its outer catch and returned failureStage: "artifact". inspectWindowsNativeReadiness maps that stage to "Use the matching Windows x64 REA package, or restore native/windows/build/manifest.json and native/windows/build/rea-windows-x64.node ...".

Expected (from the issue): doctor says what the user can do without disabling Smart App Control.

Change and scope

  • src/windows/WindowsNativeLoader.ts: only the host.loadArtifact() call is wrapped. A throw there returns the new failureStage: "load" (still not retryable). The reason keeps the OS error text and adds the exported WINDOWS_NATIVE_LOAD_REFUSED_REMEDIATION: the file matched the manifest so restoring it will not help; if Windows reports an Application Control block, Smart App Control or an App Control for Business policy refused it; Ghidra and JADX need the native controls on Windows while rea setup can still register clients; run REA on a host whose policy allows the file, or ask the maintainers about a signed build. It does not tell the user to disable Smart App Control.
  • src/process/WindowsAuthority.ts: the load stage keeps the documented code runtime_missing (docs/windows-ghidra-p0.md already documents unloadable artifacts that way) and uses the new remediation.
  • docs/windows-ghidra-p0.md (one sentence) and docs/user-visible-errors.csv (row 93) describe the new stage and copy.

Not included:

  • Signing or any release change for the addon. That is a maintainer decision.
  • A setup change. The issue says rea setup returned needs_human with no planned actions. Nothing in src/application/Setup*.ts uses the native controls. With the addon unavailable, the published rea-agents@6.7.0 CLI still planned and applied the claude_code registration (details below), so there is no gate to remove.
  • The generic JADX remediation and the Ghidra ghidra-java row ("Update JAVA_HOME") for this failure. That mapping is separate.
  • Matching on the OS error text. WindowsAuthority.ts says not to guess from it, so the guidance is phrased conditionally.

Contract and boundary impact

  • Semantic owner and earliest changed stage: loadWindowsNativeAuthority in src/windows/WindowsNativeLoader.ts, at the module load, after the manifest and digest checks.
  • Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable.
  • CLI and MCP/tool-catalog contract: the windows_native_failure stage can now be load, and the readiness remediation text changes for that case. Codes are unchanged (runtime_missing). No tool schema changes.
  • Provider, bridge, target-format, or platform compatibility: Windows only; no provider change.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: 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: src/windows/WindowsNativeLoader.test.ts, one case using the existing loader fixture. loadArtifact throws "An Application Control policy has blocked this file." The test checks failureStage: "load", the OS text kept in reason, no retryable, code runtime_missing, a remediation that mentions Smart App Control, and no "restore native/windows/build" advice.
  • Base reproduction or other evidence: the new test fails without the change (expected load, received artifact) and passes with it. This is a simulated refusal. I could not reproduce the real block because Smart App Control is off on my machine.
  • Setup finding: I ran the published rea-agents@6.7.0 CLI with the addon temporarily unavailable (renamed, restored afterwards) and a scratch HOME/USERPROFILE/APPDATA/LOCALAPPDATA. rea setup --client claude_code --yes --format json returned ready, planned and applied configure_client:claude_code and install_skill:claude_code. A second run returned ready with nothing planned. The unscoped rea doctor showed the native failure only in the jadx and ghidra-java rows. That simulated failure was ENOENT (artifact stage), not the real OS refusal.
  • Where needs_human with an empty plan can come from: registration already present plus a failing in-scope doctor check (Setup.ts returns "Run rea doctor and apply each reported remediation."). I reproduced that shape on main with a failing Node version check, with the addon present or absent. Which in-scope check failed for the reporter is unknown; their report quotes only the out-of-scope jadx row.
  • User-visible CLI/MCP output (if applicable): the new reason reads "REA Windows native controls are unavailable: Windows refused to load the verified native/windows/build/rea-windows-x64.node: The file matched the package manifest, so restoring or reinstalling it will not help. ..." (full text in docs/user-visible-errors.csv, row 93).
  • Remaining proof gaps: no real Smart App Control block, so the exact ERR_DLOPEN_FAILED message format is not observed live; the test uses the text quoted in the issue.

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

Windows 11 x64 (10.0.26200), Node 24.21.0. .nvmrc pins 24.22.1 and main requires ^24.22.1, so this ran below the pin and npm ci needed --engine-strict=false.

  • npm run build:cached — passed
  • npm run test:focused -- src/windows/WindowsNativeLoader.test.ts src/ghidra/GhidraDoctor.test.ts src/ghidra/GhidraProvider.behavior.test.ts src/application/Setup.planning.test.ts src/application/Doctor.test.ts — 5 files, 282 passed
  • npm run test:focused -- tests/boundary/process/providerProcess.test.ts — 3 failed, 18 passed, 5 skipped; the same 3 fail on clean main (checked with my change stashed)
  • npm run check:fast — passed
  • npm run check — exit 0 (lint 0 errors, warnings only; format, knip, metadata and architecture checks passed)
  • npm run docs:check — exit 0

Compatibility, safety, and release

  • Breaking changes or migration steps: none. A caller that matched failureStage: "artifact" for an OS load refusal now sees load.
  • Real Hopper/Ghidra, browser, or OS coverage: no real Ghidra run; the change is in the native loader diagnostics. Windows 11 x64 only; not run on Linux or macOS.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the loader still verifies version, ABI, architecture and digest before loading and still grants no authority on failure. Only the failure classification and message change.

Author readiness

Human owner: @dark13b

  • 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/6832 **Author:** [@dark13b](https://github.com/dark13b) **Created:** 10/23/2026 **Status:** ✅ Merged **Merged:** 10/24/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/windows-native-block-and-posix-hopper-paths` --- ### 📝 Commits (1) - [`0c03802`](https://github.com/morluto/rea/commit/0c03802af5fdf06181938f9613b2e7eec18cbd39) fix(windows): explain when Windows refuses to load the verified native addon ### 📊 Changes **5 files changed** (+65 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `docs/user-visible-errors.csv` (+1 -0) 📝 `docs/windows-ghidra-p0.md` (+5 -2) 📝 `src/process/WindowsAuthority.ts` (+9 -6) 📝 `src/windows/WindowsNativeLoader.test.ts` (+29 -0) 📝 `src/windows/WindowsNativeLoader.ts` (+21 -2) </details> ### 📄 Description ## Summary Fixes #5723 When Windows refuses to load `rea-windows-x64.node` (for example Smart App Control or an App Control policy), `rea doctor` and the provider diagnostics told the user to restore or rebuild the native files. The file had already passed the manifest version and SHA-256 checks, so that advice cannot help. This reports the refusal as its own failure stage with accurate guidance. ## Problem and expected behavior Smallest trigger: the loader's `loadArtifact()` throws because the OS blocked the module load (the report quotes "An Application Control policy has blocked this file"). Before: `loadWindowsNativeAuthority` caught that in its outer `catch` and returned `failureStage: "artifact"`. `inspectWindowsNativeReadiness` maps that stage to "Use the matching Windows x64 REA package, or restore native/windows/build/manifest.json and native/windows/build/rea-windows-x64.node ...". Expected (from the issue): doctor says what the user can do without disabling Smart App Control. ## Change and scope - `src/windows/WindowsNativeLoader.ts`: only the `host.loadArtifact()` call is wrapped. A throw there returns the new `failureStage: "load"` (still not retryable). The reason keeps the OS error text and adds the exported `WINDOWS_NATIVE_LOAD_REFUSED_REMEDIATION`: the file matched the manifest so restoring it will not help; if Windows reports an Application Control block, Smart App Control or an App Control for Business policy refused it; Ghidra and JADX need the native controls on Windows while `rea setup` can still register clients; run REA on a host whose policy allows the file, or ask the maintainers about a signed build. It does not tell the user to disable Smart App Control. - `src/process/WindowsAuthority.ts`: the `load` stage keeps the documented code `runtime_missing` (`docs/windows-ghidra-p0.md` already documents unloadable artifacts that way) and uses the new remediation. - `docs/windows-ghidra-p0.md` (one sentence) and `docs/user-visible-errors.csv` (row 93) describe the new stage and copy. Not included: - Signing or any release change for the addon. That is a maintainer decision. - A setup change. The issue says `rea setup` returned `needs_human` with no planned actions. Nothing in `src/application/Setup*.ts` uses the native controls. With the addon unavailable, the published `rea-agents@6.7.0` CLI still planned and applied the `claude_code` registration (details below), so there is no gate to remove. - The generic JADX remediation and the Ghidra `ghidra-java` row ("Update JAVA_HOME") for this failure. That mapping is separate. - Matching on the OS error text. `WindowsAuthority.ts` says not to guess from it, so the guidance is phrased conditionally. ## Contract and boundary impact - Semantic owner and earliest changed stage: `loadWindowsNativeAuthority` in `src/windows/WindowsNativeLoader.ts`, at the module load, after the manifest and digest checks. - Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable. - CLI and MCP/tool-catalog contract: the `windows_native_failure` stage can now be `load`, and the readiness remediation text changes for that case. Codes are unchanged (`runtime_missing`). No tool schema changes. - Provider, bridge, target-format, or platform compatibility: Windows only; no provider change. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: 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. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/windows/WindowsNativeLoader.test.ts`, one case using the existing loader fixture. `loadArtifact` throws "An Application Control policy has blocked this file." The test checks `failureStage: "load"`, the OS text kept in `reason`, no `retryable`, code `runtime_missing`, a remediation that mentions Smart App Control, and no "restore native/windows/build" advice. - Base reproduction or other evidence: the new test fails without the change (expected `load`, received `artifact`) and passes with it. This is a simulated refusal. I could not reproduce the real block because Smart App Control is off on my machine. - Setup finding: I ran the published `rea-agents@6.7.0` CLI with the addon temporarily unavailable (renamed, restored afterwards) and a scratch HOME/USERPROFILE/APPDATA/LOCALAPPDATA. `rea setup --client claude_code --yes --format json` returned `ready`, planned and applied `configure_client:claude_code` and `install_skill:claude_code`. A second run returned `ready` with nothing planned. The unscoped `rea doctor` showed the native failure only in the `jadx` and `ghidra-java` rows. That simulated failure was ENOENT (artifact stage), not the real OS refusal. - Where `needs_human` with an empty plan can come from: registration already present plus a failing in-scope doctor check (`Setup.ts` returns "Run rea doctor and apply each reported remediation."). I reproduced that shape on `main` with a failing Node version check, with the addon present or absent. Which in-scope check failed for the reporter is unknown; their report quotes only the out-of-scope jadx row. - User-visible CLI/MCP output (if applicable): the new reason reads "REA Windows native controls are unavailable: Windows refused to load the verified native/windows/build/rea-windows-x64.node: <OS error> The file matched the package manifest, so restoring or reinstalling it will not help. ..." (full text in `docs/user-visible-errors.csv`, row 93). - Remaining proof gaps: no real Smart App Control block, so the exact `ERR_DLOPEN_FAILED` message format is not observed live; the test uses the text quoted in the issue. 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 Windows 11 x64 (10.0.26200), Node 24.21.0. `.nvmrc` pins 24.22.1 and `main` requires `^24.22.1`, so this ran below the pin and `npm ci` needed `--engine-strict=false`. - `npm run build:cached` — passed - `npm run test:focused -- src/windows/WindowsNativeLoader.test.ts src/ghidra/GhidraDoctor.test.ts src/ghidra/GhidraProvider.behavior.test.ts src/application/Setup.planning.test.ts src/application/Doctor.test.ts` — 5 files, 282 passed - `npm run test:focused -- tests/boundary/process/providerProcess.test.ts` — 3 failed, 18 passed, 5 skipped; the same 3 fail on clean `main` (checked with my change stashed) - `npm run check:fast` — passed - `npm run check` — exit 0 (lint 0 errors, warnings only; format, knip, metadata and architecture checks passed) - `npm run docs:check` — exit 0 ## Compatibility, safety, and release - Breaking changes or migration steps: none. A caller that matched `failureStage: "artifact"` for an OS load refusal now sees `load`. - Real Hopper/Ghidra, browser, or OS coverage: no real Ghidra run; the change is in the native loader diagnostics. Windows 11 x64 only; not run on Linux or macOS. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the loader still verifies version, ABI, architecture and digest before loading and still grants no authority on failure. Only the failure classification and message change. ## Author readiness Human owner: @dark13b - [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 - [ ] 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. --- <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:45 +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#7422
No description provided.