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 #4387] [MERGED] fix(electron): cancel windowless waits and state reads #6210

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4387
Author: @Adolanium
Created: 10/16/2026
Status: ✅ Merged
Merged: 10/16/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/electron-wait-cancellation

📝 Commits (10+)

  • b1e7bbd fix(electron): cancel windowless waits and state reads
  • d47aa1f fix(electron): observe operations abandoned by prior cancellation
  • 39ec10e Merge upstream/main into fix/electron-wait-cancellation
  • 0f40cef fix(electron): check cancellation after capture finalization
  • 344c774 fix(electron): carry the caller abort reason through cancellation
  • af732dd fix(electron): report final state grace expiry as the caller's cancellation
  • 781d575 fix(pwntools): preserve worker ownership across launcher exec
  • b25d351 fix(browser): report cancellation after cleanup and source-map abort (#2893)
  • c884864 fix(filesystem): observe cancellation after file finalization
  • fe2a398 fix(managed): retain descriptor ownership through hash cancellation

📊 Changes

26 files changed (+5435 additions, -258 deletions)

View changed files

📝 docs/electron-observation.md (+7 -2)
➕ docs/verification/electron-cancellation-2026-10-16.json (+2895 -0)
➕ docs/verification/electron-cancellation-2026-10-16.md (+158 -0)
➕ experiments/analysis-efficiency/electron-cancellation-oracles.py (+154 -0)
➕ experiments/analysis-efficiency/electron-cancellation.mjs (+273 -0)
➕ experiments/analysis-efficiency/joplin-cli-cancellation.py (+123 -0)
📝 src/adb/AdbProvider.ts (+31 -20)
📝 src/application/RegularFileRead.ts (+16 -7)
📝 src/browser/PlaywrightElectronActiveActions.test.ts (+188 -2)
📝 src/browser/PlaywrightElectronActiveActions.ts (+68 -6)
📝 src/browser/PlaywrightElectronActiveProvider.test.ts (+456 -5)
📝 src/browser/PlaywrightElectronActiveProvider.ts (+49 -14)
📝 src/dotnet/ManagedSnapshot.ts (+33 -23)
📝 src/filesystem/OwnedRegularFile.ts (+35 -0)
📝 src/native/pwntools/PwntoolsDecoder.ts (+7 -4)
📝 tests/boundary/binaryDiagnostics/recordedCrashProvider.test.ts (+94 -19)
📝 tests/boundary/browser/cdpBrowserProvider.lifecycle_failures.test.ts (+195 -0)
➕ tests/boundary/filesystem/regularFileCancellation.test.ts (+233 -0)
📝 tests/boundary/filesystem/stableFileHashOwnership.test.ts (+49 -1)
📝 tests/boundary/mcp/fridaLifecycleMcp.test.ts (+5 -4)

...and 6 more files

📄 Description

Summary

Fixes #4388. Electron scenario capture now observes cancellation while waiting for the first window and while reading initial/final state. Cancellation already observed before cleanup retains its caller reason when cleanup subsequently fails.

Problem and expected behavior

An unbounded firstWindow or state read could prevent cancellation from reaching finalization. The earlier PR also replaced cancellation with success after a settled final snapshot, so a later cleanup failure changed the public category to execution_failure. Capture must preserve cancellation, partial observations and cleanup uncertainty independently.

Change and scope

The shared Electron provider bounds the initial snapshot by the startup deadline, observes cancellation during window waits and final reads, and grants the final snapshot the existing five-second post-cancellation grace. It records cancellation before finalization and checks cancellation first observed during cleanup afterward. One constructor owns early/late partial-capture cancellation errors; cleanup failures retain precedence and their diagnostics.

Scope decision: not applicable; ordinary fix within the existing capture boundary. No new execution authority, provider, tool, cache or normal-case result field.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Electron active action/state execution and provider outcome construction.
  • Contribution scope fit and linked maintainer decision: existing authorized capture boundary; no new capability.
  • CLI and MCP/tool-catalog contract: same shared implementation and input/result schemas; interrupted calls return typed errors rather than waiting indefinitely. Recorded catalog metadata is byte-identical to main.
  • Provider, bridge, target-format, or platform compatibility: deterministic regressions and Linux Joplin probes; packaged-runtime compatibility remains unverified.
  • Evidence, artifact, provenance, or reconstruction contract: retain caller cancellation cause, cancelled actions, partial snapshots and grace-expiry diagnostics; never convert unverified cleanup into success.
  • Target selection, authority, upstream behavior, and cleanup details: existing explicit target/lifecycle; process ownership policy unchanged. Linux cleanup/first-signal CLI exit remains an observed gap (#4282).
  • Generated metadata, package, or installation impact: none.

Expected effects retain the existing Electron capture authority:

  • 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

  • Base reproduction: original main remains pending 20.001 s after cancellation with a controlled first-window stall. Two new cleanup-cause cases fail on the previously reviewed PR (20 pass, 2 fail), then pass after the producing-outcome fix.
  • Real app: unchanged Joplin 3.7.21 ASAR plus complete unpacked assets, generic Electron 44.7.0, fresh profiles/Xvfb. Controlled REA-side window/initial/final reply stalls return cancellation in 5.658/5.335/10.262 s respectively. These do not establish naturally occurring Joplin stalls or a completed GUI workflow.
  • Public CLI: main/fixed replies preserve code: cleanup_incomplete, category: cancelled and cancelled actions. The reviewed PR lost that category. All real CLI trials still fail the first-signal exit deadline; recorded recovery is not provider cleanup.
  • Remaining proof gaps: every real probe has incomplete/unverified Linux cleanup and a nonzero verifier exit. The official packaged runtime failed initial Inspector evaluation before reaching cancellation. No Windows/macOS, complete-task speedup or live-agent token savings claimed.

Reproduction scripts, exact source/input identities, all failures and resource observations.

  • 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

Review follow-up: both verifier success paths now require complete provider cleanup, including when the main process/CLI has exited. Six controlled oracle cases pass; both previous scripts fail the negative controls. Frozen real Joplin reruns retain cancellation and explicitly fail on unverified cleanup/first-signal CLI exit. These controlled replies are not real-provider evidence; production source and original historical records are unchanged.

  • npm run test:focused -- src/browser/PlaywrightElectronActiveActions.test.ts src/browser/PlaywrightElectronActiveProvider.test.ts tests/boundary/mcp/serverIdentity.test.ts — 49 passed across three files.
  • npm run check:fast — six tasks and architecture guards passed.
  • npm run docs:check — six tasks (two cached) plus five README consistency cases passed.
  • Preserved real Joplin shared-provider/public-CLI probes — cancellation phases verified; complete workflows partial/failed as explained above.
  • Serial one-CPU/8 GiB scopes; full static gate 153.534 s wall, 152.274161 family CPU s, 6,442,016,768 peak cgroup bytes including cache. No OOM. Payload-exit counters are not final whole-scope counters.

Earlier-head CI (39 successful checks) and clear Codex review preceded the verifier follow-up; they do not establish current-head validation. Fresh CI and review results are being tracked on this head.

Compatibility, safety, and release

No breaking call, dependency or installation change. Existing instrumentation/lifecycle authority and strict process ownership remain unchanged. External owned-scope recovery is recorded separately from provider cleanup. Application binaries, profiles and regenerable large outputs are excluded from Git.

Author readiness

Human owner: @Adolanium

  • 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/4387 **Author:** [@Adolanium](https://github.com/Adolanium) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/16/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/electron-wait-cancellation` --- ### 📝 Commits (10+) - [`b1e7bbd`](https://github.com/morluto/rea/commit/b1e7bbddf97140692bbf656cd969a204c2d58305) fix(electron): cancel windowless waits and state reads - [`d47aa1f`](https://github.com/morluto/rea/commit/d47aa1fbca8d1f9d9de03c13d043ffe9245085b1) fix(electron): observe operations abandoned by prior cancellation - [`39ec10e`](https://github.com/morluto/rea/commit/39ec10e18dcbea68f98b06dff7b1b0c425336560) Merge upstream/main into fix/electron-wait-cancellation - [`0f40cef`](https://github.com/morluto/rea/commit/0f40cef32c1c5cb70d291d731ad3029cf0b179c5) fix(electron): check cancellation after capture finalization - [`344c774`](https://github.com/morluto/rea/commit/344c7744686e6c1c14a0e2950b11cc2f5eac8d61) fix(electron): carry the caller abort reason through cancellation - [`af732dd`](https://github.com/morluto/rea/commit/af732dd805cc4c881757ba6d02916841e7706863) fix(electron): report final state grace expiry as the caller's cancellation - [`781d575`](https://github.com/morluto/rea/commit/781d5751ad18b25a1fe1ffa8c6035388be8c3283) fix(pwntools): preserve worker ownership across launcher exec - [`b25d351`](https://github.com/morluto/rea/commit/b25d3517b68ad4352fa44e435f23c26de4bce54a) fix(browser): report cancellation after cleanup and source-map abort (#2893) - [`c884864`](https://github.com/morluto/rea/commit/c884864876c2568d8567235737b32e3f5893751d) fix(filesystem): observe cancellation after file finalization - [`fe2a398`](https://github.com/morluto/rea/commit/fe2a398dd9ab290ba6cb3411403d319cec8d07a2) fix(managed): retain descriptor ownership through hash cancellation ### 📊 Changes **26 files changed** (+5435 additions, -258 deletions) <details> <summary>View changed files</summary> 📝 `docs/electron-observation.md` (+7 -2) ➕ `docs/verification/electron-cancellation-2026-10-16.json` (+2895 -0) ➕ `docs/verification/electron-cancellation-2026-10-16.md` (+158 -0) ➕ `experiments/analysis-efficiency/electron-cancellation-oracles.py` (+154 -0) ➕ `experiments/analysis-efficiency/electron-cancellation.mjs` (+273 -0) ➕ `experiments/analysis-efficiency/joplin-cli-cancellation.py` (+123 -0) 📝 `src/adb/AdbProvider.ts` (+31 -20) 📝 `src/application/RegularFileRead.ts` (+16 -7) 📝 `src/browser/PlaywrightElectronActiveActions.test.ts` (+188 -2) 📝 `src/browser/PlaywrightElectronActiveActions.ts` (+68 -6) 📝 `src/browser/PlaywrightElectronActiveProvider.test.ts` (+456 -5) 📝 `src/browser/PlaywrightElectronActiveProvider.ts` (+49 -14) 📝 `src/dotnet/ManagedSnapshot.ts` (+33 -23) 📝 `src/filesystem/OwnedRegularFile.ts` (+35 -0) 📝 `src/native/pwntools/PwntoolsDecoder.ts` (+7 -4) 📝 `tests/boundary/binaryDiagnostics/recordedCrashProvider.test.ts` (+94 -19) 📝 `tests/boundary/browser/cdpBrowserProvider.lifecycle_failures.test.ts` (+195 -0) ➕ `tests/boundary/filesystem/regularFileCancellation.test.ts` (+233 -0) 📝 `tests/boundary/filesystem/stableFileHashOwnership.test.ts` (+49 -1) 📝 `tests/boundary/mcp/fridaLifecycleMcp.test.ts` (+5 -4) _...and 6 more files_ </details> ### 📄 Description ## Summary Fixes #4388. Electron scenario capture now observes cancellation while waiting for the first window and while reading initial/final state. Cancellation already observed before cleanup retains its caller reason when cleanup subsequently fails. ## Problem and expected behavior An unbounded `firstWindow` or state read could prevent cancellation from reaching finalization. The earlier PR also replaced cancellation with success after a settled final snapshot, so a later cleanup failure changed the public category to `execution_failure`. Capture must preserve cancellation, partial observations and cleanup uncertainty independently. ## Change and scope The shared Electron provider bounds the initial snapshot by the startup deadline, observes cancellation during window waits and final reads, and grants the final snapshot the existing five-second post-cancellation grace. It records cancellation before finalization and checks cancellation first observed during cleanup afterward. One constructor owns early/late partial-capture cancellation errors; cleanup failures retain precedence and their diagnostics. Scope decision: not applicable; ordinary fix within the existing capture boundary. No new execution authority, provider, tool, cache or normal-case result field. ## Contract and boundary impact - Semantic owner and earliest changed stage: Electron active action/state execution and provider outcome construction. - Contribution scope fit and linked maintainer decision: existing authorized capture boundary; no new capability. - CLI and MCP/tool-catalog contract: same shared implementation and input/result schemas; interrupted calls return typed errors rather than waiting indefinitely. Recorded catalog metadata is byte-identical to main. - Provider, bridge, target-format, or platform compatibility: deterministic regressions and Linux Joplin probes; packaged-runtime compatibility remains unverified. - Evidence, artifact, provenance, or reconstruction contract: retain caller cancellation cause, cancelled actions, partial snapshots and grace-expiry diagnostics; never convert unverified cleanup into success. - Target selection, authority, upstream behavior, and cleanup details: existing explicit target/lifecycle; process ownership policy unchanged. Linux cleanup/first-signal CLI exit remains an observed gap (#4282). - Generated metadata, package, or installation impact: none. Expected effects retain the existing Electron capture authority: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [x] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. - [ ] 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 - Base reproduction: original main remains pending 20.001 s after cancellation with a controlled first-window stall. Two new cleanup-cause cases fail on the previously reviewed PR (20 pass, 2 fail), then pass after the producing-outcome fix. - Real app: unchanged Joplin 3.7.21 ASAR plus complete unpacked assets, generic Electron 44.7.0, fresh profiles/Xvfb. Controlled REA-side window/initial/final reply stalls return cancellation in 5.658/5.335/10.262 s respectively. These do not establish naturally occurring Joplin stalls or a completed GUI workflow. - Public CLI: main/fixed replies preserve `code: cleanup_incomplete`, `category: cancelled` and cancelled actions. The reviewed PR lost that category. All real CLI trials still fail the first-signal exit deadline; recorded recovery is not provider cleanup. - Remaining proof gaps: every real probe has incomplete/unverified Linux cleanup and a nonzero verifier exit. The official packaged runtime failed initial Inspector evaluation before reaching cancellation. No Windows/macOS, complete-task speedup or live-agent token savings claimed. [Reproduction scripts, exact source/input identities, all failures and resource observations](https://github.com/Adolanium/rea/blob/de3733147496f1231db614b996b5c143003c622b/docs/verification/electron-cancellation-2026-10-16.md). - [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 Review follow-up: both verifier success paths now require complete provider cleanup, including when the main process/CLI has exited. Six controlled oracle cases pass; both previous scripts fail the negative controls. Frozen real Joplin reruns retain cancellation and explicitly fail on unverified cleanup/first-signal CLI exit. These controlled replies are not real-provider evidence; production source and original historical records are unchanged. - `npm run test:focused -- src/browser/PlaywrightElectronActiveActions.test.ts src/browser/PlaywrightElectronActiveProvider.test.ts tests/boundary/mcp/serverIdentity.test.ts` — 49 passed across three files. - `npm run check:fast` — six tasks and architecture guards passed. - `npm run docs:check` — six tasks (two cached) plus five README consistency cases passed. - Preserved real Joplin shared-provider/public-CLI probes — cancellation phases verified; complete workflows partial/failed as explained above. - Serial one-CPU/8 GiB scopes; full static gate 153.534 s wall, 152.274161 family CPU s, 6,442,016,768 peak cgroup bytes including cache. No OOM. Payload-exit counters are not final whole-scope counters. Earlier-head CI (39 successful checks) and clear Codex review preceded the verifier follow-up; they do not establish current-head validation. Fresh CI and review results are being tracked on this head. ## Compatibility, safety, and release No breaking call, dependency or installation change. Existing instrumentation/lifecycle authority and strict process ownership remain unchanged. External owned-scope recovery is recorded separately from provider cleanup. Application binaries, profiles and regenerable large outputs are excluded from Git. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @Adolanium - [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. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:12:42 +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#6210
No description provided.