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 #4668] [MERGED] fix(electron): retain fuse descriptor ownership through failed final close #6351

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4668
Author: @nosmile99
Created: 10/17/2026
Status: ✅ Merged
Merged: 10/17/2026
Merged by: @morluto

Base: main ← Head: fix/electron-fuse-final-close-ownership

📝 Commits (3)

  • 3136977 fix(electron): retain fuse descriptor ownership through failed final close
  • 1d88a75 fix(electron): keep cleanup report and partial evidence through cancel and successful reads
  • 6bb9491 fix(electron): resolve fuse cleanup cancellation conflicts

📊 Changes

3 files changed (+471 additions, -35 deletions)

View changed files

📝 src/electron/ElectronFuseProvider.ts (+122 -0)
📝 src/electron/ElectronFuseReader.ts (+46 -35)
➕ src/electron/ElectronFuseReaderCleanup.test.ts (+303 -0)

📄 Description

Summary

Fixes #4658. Static Electron fuse inspection admitted a file descriptor and closed it in a bare finally: a rejecting final close() replaced the in-flight read error, was classified by errno (e.g. EACCES) as a read permission failure, and silently dropped ownership of the still-live descriptor.

AI-assisted contribution (no human owner available): Author readiness declarations are left unchecked per the repo's AGENTS.md. @morluto marked this PR ready for review on 2026-10-17; the automated-review findings below were addressed after that.

Problem and expected behavior

Smallest trigger: fault close() on the admitted descriptor (reject with EACCES) while a read fails with EIO. Violated invariants:

  1. The close rejection replaced the primary EIO read error (throw in finally).
  2. The response classified the close error as a filesystem read permission failure (AnalysisAccessDeniedError, "Selected artifact could not be read (EACCES)").
  3. Ownership of the still-live descriptor was lost with no incomplete-cleanup report.

Expected: the primary error keeps its classification, the close failure is reported as incomplete cleanup, and the descriptor owner is retained.

Change and scope

  • src/electron/ElectronFuseReader.ts: route the admitted read through the existing withOwnedRegularFile primitive (same one used by the adb/jadx/linux-hopper providers) instead of a bare try/finally. A failed close now throws RegularFileCleanupFailure carrying the read outcome (primary error preserved), the cleanup cause, and the exact owner. New optional retainFailedClose passthrough on readElectronFuseImage options; no caller changes required.
  • src/electron/ElectronFuseProvider.ts: map RegularFileCleanupFailure in failureFor — the primary outcome keeps its own classification (recursed through failureFor), combined with a ProviderCleanupError (cleanupIncomplete=true) via analysisErrorWithCleanupFailure, mirroring JadxProvider.executionError. A close failure can no longer surface as a read permission denial.
  • Intentionally not included: no retry of the failed close, no new CLI/MCP surface, no retention registry — the error retains the owner for the caller/operator, and incomplete cleanup is reported rather than silently recovered.

Contribution scope: ordinary fix within existing boundaries (no new provider, no target execution/injection/mutation, no protection recovery) — maintainer scope decision not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: filesystem ownership primitive, at the final-close stage of readElectronFuseImage.
  • Contribution scope fit and linked maintainer decision: ordinary fix; not applicable.
  • CLI and MCP/tool-catalog contract: no signature or schema change; error classification changes only in the failed-close path.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: cleanup is now reported incomplete instead of silently dropped.

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: src/electron/ElectronFuseReaderCleanup.test.ts (6 tests) — faults close() with EACCES with and without a primary read error (EIO), via the same vi.mock("node:fs/promises") open-wrapper convention as RegularFileAdmission.test.ts.

  • Base reproduction or other evidence: executed. The two fault tests fail on the pre-fix revision (stashed fix, tests kept): close rejection replaced the primary error, and the provider mapped EACCES to AnalysisAccessDeniedError. All 3 pass with the fix. Fault-assertion details: outcome.cause is the original EIO error (identity), cleanupCause is the EACCES error, owner.handle is the admitted handle, and fstatSync(fd) still succeeds on the retained descriptor.

  • User-visible CLI/MCP output: none (error-path only).

  • Remaining proof gaps: Windows taskkill-style abrupt termination and real Chrome-less CI coverage of the close path are unavailable here; the fault injection is controlled and local-only.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Current merge-resolution validation

Merged main at f85a932d7 in 6bb94914e. Keep failed-close handling before cancellation mapping so the cleanup report and descriptor owner survive. Use main's regularFileCancellation facts for cancellation recorded by the operation/final close. A read failure that precedes cancellation during close retains its own classification, alongside incomplete cleanup. Completed fuse observations remain attached as partial Evidence.

Added a synchronized read-failure + abort-during-close + close-failure regression; reused the fault helper for close-boundary cancellation. Executed on macOS with Node 24.18.0:

  • npm run test:focused -- src/electron/ElectronFuseProvider.test.ts src/electron/ElectronFuseReaderCleanup.test.ts tests/boundary/filesystem/regularFileCancellation.test.ts tests/boundary/mcp/electronFusesMcp.test.ts: passed, 63 tests across four files, including the public MCP fuse workflow.
  • After splitting the new regression into a separate describe block to satisfy the function line limit, npm run test:local -- src/electron/ElectronFuseReaderCleanup.test.ts: passed, 7 tests.
  • npm run check:fast: passed (typecheck and lint).
  • git diff origin/main...HEAD --check: passed; pre-commit formatting/lint passed.

Close/cancellation faults are controlled filesystem-boundary injections. No real failing OS close, Windows runtime, abrupt process termination, or retained-owner retry registry was verified or added by this resolution. Existing limitations concerning provider/session retry ownership remain.

Original validation (before merge resolution)

  • npx vitest run src/electron/ElectronFuseReaderCleanup.test.ts — 3/3 pass with fix; 2/3 fail pre-fix (fault tests), 1/3 pass pre-fix (control).
  • npx vitest run src/electron/ src/application/electron/ src/domain/electron/ src/filesystem/ — 36/36 pass.
  • npm run check:fast — typecheck + lint clean.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: Linux only (Node 24); the fault is injected at the node:fs/promises boundary and is platform-independent by construction.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the retained failed-close owner keeps a live fd until process exit; this is now reported via cleanupIncomplete instead of being silently dropped. No target interaction changes.

Automated-review follow-up

Greptile/Codex findings addressed in commit 1d88a75 ("fix(electron): keep cleanup report and partial evidence through cancel and successful reads"):

  • Cancellation hid failed cleanup (P1, both bots): confirmed by code reading — failureFor returned a bare AnalysisCancelledError when signal.aborted fired before the RegularFileCleanupFailure branch, silently dropping the descriptor owner. The cleanup-failure branch now runs first; on abort it composes AnalysisCancelledError (cause = signal.reason) with the incomplete-cleanup error, keeping cleanupIncomplete, cleanupResources, and the owner in the cause chain.
  • Completed fuse evidence discarded (Codex P1): confirmed — the completed branch discarded the successful read. The completed ElectronFuseImage is now attached as explicitly-partial Evidence (confidence observed, sha256/bytes/format + slices, limitations marking cleanup incomplete) on the primary error; the abort-after-completion path attaches the same evidence to the composed cancellation error, mirroring PcapProvider.
  • Combined-fault coverage (Greptile P2): added a provider-level test with faulted read (EIO) + faulted close (EACCES) asserting the primary diagnostic keeps the read classification, cleanupIncomplete, and the retained owner in the cause chain.
  • Retry lease for failed closes (Codex P1): acknowledged, not implemented here. Verified the descriptor owner is retained in the error cause chain (RegularFileCleanupFailure.owner carried by ProviderCleanupError.cause); retention.kind === "not_requested" only means no retainFailedClose callback was registered. A session/provider-scoped retry lease is a design decision for the long-lived MCP server — left for the maintainer.

Validation: the abort fires inside the faulted close (synchronized with the finalization boundary, no fixed delay). The abort-during-close and partial-evidence tests fail pre-fix (stashed provider) and pass post-fix; the combined-fault test guards the already-working failed-branch mapping. 29/29 electron tests green; npm run check:fast clean.

Author readiness

Human owner:

  • 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/4668 **Author:** [@nosmile99](https://github.com/nosmile99) **Created:** 10/17/2026 **Status:** ✅ Merged **Merged:** 10/17/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/electron-fuse-final-close-ownership` --- ### 📝 Commits (3) - [`3136977`](https://github.com/morluto/rea/commit/313697791634f732b8a2826e52916d91977d3f03) fix(electron): retain fuse descriptor ownership through failed final close - [`1d88a75`](https://github.com/morluto/rea/commit/1d88a753d8bffb8db7cfbd96edd84652f6fe9942) fix(electron): keep cleanup report and partial evidence through cancel and successful reads - [`6bb9491`](https://github.com/morluto/rea/commit/6bb94914eb6270e0bc1f43f63c7247a7aa330508) fix(electron): resolve fuse cleanup cancellation conflicts ### 📊 Changes **3 files changed** (+471 additions, -35 deletions) <details> <summary>View changed files</summary> 📝 `src/electron/ElectronFuseProvider.ts` (+122 -0) 📝 `src/electron/ElectronFuseReader.ts` (+46 -35) ➕ `src/electron/ElectronFuseReaderCleanup.test.ts` (+303 -0) </details> ### 📄 Description ## Summary Fixes #4658. Static Electron fuse inspection admitted a file descriptor and closed it in a bare `finally`: a rejecting final `close()` replaced the in-flight read error, was classified by errno (e.g. `EACCES`) as a read permission failure, and silently dropped ownership of the still-live descriptor. AI-assisted contribution (no human owner available): Author readiness declarations are left unchecked per the repo's AGENTS.md. @morluto marked this PR ready for review on 2026-10-17; the automated-review findings below were addressed after that. ## Problem and expected behavior Smallest trigger: fault `close()` on the admitted descriptor (reject with `EACCES`) while a read fails with `EIO`. Violated invariants: 1. The close rejection replaced the primary `EIO` read error (throw in `finally`). 2. The response classified the close error as a filesystem **read** permission failure (`AnalysisAccessDeniedError`, "Selected artifact could not be read (EACCES)"). 3. Ownership of the still-live descriptor was lost with no incomplete-cleanup report. Expected: the primary error keeps its classification, the close failure is reported as incomplete cleanup, and the descriptor owner is retained. ## Change and scope - `src/electron/ElectronFuseReader.ts`: route the admitted read through the existing `withOwnedRegularFile` primitive (same one used by the adb/jadx/linux-hopper providers) instead of a bare `try/finally`. A failed close now throws `RegularFileCleanupFailure` carrying the read outcome (primary error preserved), the cleanup cause, and the exact owner. New optional `retainFailedClose` passthrough on `readElectronFuseImage` options; no caller changes required. - `src/electron/ElectronFuseProvider.ts`: map `RegularFileCleanupFailure` in `failureFor` — the primary outcome keeps its own classification (recursed through `failureFor`), combined with a `ProviderCleanupError` (`cleanupIncomplete=true`) via `analysisErrorWithCleanupFailure`, mirroring `JadxProvider.executionError`. A close failure can no longer surface as a read permission denial. - Intentionally not included: no retry of the failed close, no new CLI/MCP surface, no retention registry — the error retains the owner for the caller/operator, and incomplete cleanup is reported rather than silently recovered. Contribution scope: ordinary fix within existing boundaries (no new provider, no target execution/injection/mutation, no protection recovery) — maintainer scope decision not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: filesystem ownership primitive, at the final-close stage of `readElectronFuseImage`. - Contribution scope fit and linked maintainer decision: ordinary fix; not applicable. - CLI and MCP/tool-catalog contract: no signature or schema change; error classification changes only in the failed-close path. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: cleanup is now reported incomplete instead of silently dropped. 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: `src/electron/ElectronFuseReaderCleanup.test.ts` (6 tests) — faults `close()` with `EACCES` with and without a primary read error (`EIO`), via the same `vi.mock("node:fs/promises")` open-wrapper convention as `RegularFileAdmission.test.ts`. - Base reproduction or other evidence: executed. The two fault tests **fail on the pre-fix revision** (stashed fix, tests kept): close rejection replaced the primary error, and the provider mapped `EACCES` to `AnalysisAccessDeniedError`. All 3 pass with the fix. Fault-assertion details: `outcome.cause` is the original `EIO` error (identity), `cleanupCause` is the `EACCES` error, `owner.handle` is the admitted handle, and `fstatSync(fd)` still succeeds on the retained descriptor. - User-visible CLI/MCP output: none (error-path only). - Remaining proof gaps: Windows `taskkill`-style abrupt termination and real Chrome-less CI coverage of the close path are unavailable here; the fault injection is controlled and local-only. - [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. ## Current merge-resolution validation Merged main at `f85a932d7` in `6bb94914e`. Keep failed-close handling before cancellation mapping so the cleanup report and descriptor owner survive. Use main's `regularFileCancellation` facts for cancellation recorded by the operation/final close. A read failure that precedes cancellation during close retains its own classification, alongside incomplete cleanup. Completed fuse observations remain attached as partial Evidence. Added a synchronized read-failure + abort-during-close + close-failure regression; reused the fault helper for close-boundary cancellation. Executed on macOS with Node 24.18.0: - `npm run test:focused -- src/electron/ElectronFuseProvider.test.ts src/electron/ElectronFuseReaderCleanup.test.ts tests/boundary/filesystem/regularFileCancellation.test.ts tests/boundary/mcp/electronFusesMcp.test.ts`: passed, 63 tests across four files, including the public MCP fuse workflow. - After splitting the new regression into a separate describe block to satisfy the function line limit, `npm run test:local -- src/electron/ElectronFuseReaderCleanup.test.ts`: passed, 7 tests. - `npm run check:fast`: passed (typecheck and lint). - `git diff origin/main...HEAD --check`: passed; pre-commit formatting/lint passed. Close/cancellation faults are controlled filesystem-boundary injections. No real failing OS close, Windows runtime, abrupt process termination, or retained-owner retry registry was verified or added by this resolution. Existing limitations concerning provider/session retry ownership remain. ## Original validation (before merge resolution) - `npx vitest run src/electron/ElectronFuseReaderCleanup.test.ts` — 3/3 pass with fix; 2/3 fail pre-fix (fault tests), 1/3 pass pre-fix (control). - `npx vitest run src/electron/ src/application/electron/ src/domain/electron/ src/filesystem/` — 36/36 pass. - `npm run check:fast` — typecheck + lint clean. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: Linux only (Node 24); the fault is injected at the `node:fs/promises` boundary and is platform-independent by construction. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the retained failed-close owner keeps a live fd until process exit; this is now reported via `cleanupIncomplete` instead of being silently dropped. No target interaction changes. ## Automated-review follow-up Greptile/Codex findings addressed in commit 1d88a75 ("fix(electron): keep cleanup report and partial evidence through cancel and successful reads"): - **Cancellation hid failed cleanup (P1, both bots):** confirmed by code reading — `failureFor` returned a bare `AnalysisCancelledError` when `signal.aborted` fired before the `RegularFileCleanupFailure` branch, silently dropping the descriptor owner. The cleanup-failure branch now runs first; on abort it composes `AnalysisCancelledError` (cause = `signal.reason`) with the incomplete-cleanup error, keeping `cleanupIncomplete`, `cleanupResources`, and the owner in the cause chain. - **Completed fuse evidence discarded (Codex P1):** confirmed — the completed branch discarded the successful read. The completed `ElectronFuseImage` is now attached as explicitly-partial `Evidence` (confidence `observed`, sha256/bytes/format + slices, limitations marking cleanup incomplete) on the primary error; the abort-after-completion path attaches the same evidence to the composed cancellation error, mirroring `PcapProvider`. - **Combined-fault coverage (Greptile P2):** added a provider-level test with faulted read (`EIO`) + faulted close (`EACCES`) asserting the primary diagnostic keeps the read classification, `cleanupIncomplete`, and the retained owner in the cause chain. - **Retry lease for failed closes (Codex P1):** acknowledged, not implemented here. Verified the descriptor owner is retained in the error cause chain (`RegularFileCleanupFailure.owner` carried by `ProviderCleanupError.cause`); `retention.kind === "not_requested"` only means no `retainFailedClose` callback was registered. A session/provider-scoped retry lease is a design decision for the long-lived MCP server — left for the maintainer. Validation: the abort fires inside the faulted close (synchronized with the finalization boundary, no fixed delay). The abort-during-close and partial-evidence tests fail pre-fix (stashed provider) and pass post-fix; the combined-fault test guards the already-working failed-branch mapping. 29/29 electron tests green; `npm run check:fast` clean. ## Author readiness Human owner: - [ ] 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 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. - [ ] 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-10-31 01:13:48 +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#6351
No description provided.