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 #5671] [MERGED] fix(errors): preserve caller abort reasons at admission #7025

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

📋 Pull Request Information

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

Base: main ← Head: cursor/caller-abort-reason-6040

📝 Commits (2)

  • 026ee20 fix(errors): preserve caller abort reasons at admission
  • ae52ee0 fix(reverse): keep a foreign digest ABORT_ERR as an adapter failure

📊 Changes

6 files changed (+324 additions, -10 deletions)

View changed files

➕ src/application/pcap/PcapAnalysisService.test.ts (+28 -0)
📝 src/application/pcap/PcapAnalysisService.ts (+5 -1)
📝 src/application/reverse/ReverseEngineeringService.ts (+60 -8)
📝 src/application/sqlite/SqliteDatabaseService.test.ts (+22 -0)
📝 src/application/sqlite/SqliteDatabaseService.ts (+5 -1)
📝 tests/composition/reverseEngineeringAdmission.test.ts (+204 -0)

📄 Description

Summary

Fixes #5670. Reverse, pcap, and SQLite application admission were dropping the caller's abort reason, and a reverse-engineering digest or command failure could be reclassified as cancellation whenever the caller signal was already aborted.

Problem and expected behavior

docs/tool-design.md requires the exact caller abort reason as AnalysisCancelledError.cause, including cancellation observed after provider completion, and requires a recognized primary failure to keep its classification.

On 40428da1dd6308f6f407547fd23b0a912232895a, an injected probe with AbortController.abort({ requested: "stop" }) observed:

  • inspectWithObjdump before launch returned AnalysisCancelledError with cause absent and did not run the provider.
  • The same call, aborted after the command returned stdout, kept partial Evidence and still omitted cause.
  • An injected digest that aborted and then rejected EACCES returned AnalysisCancelledError whose cause was that EACCES error.
  • PcapAnalysisService.execute and SqliteDatabaseService.inspect did the same at admission: cause absent, provider not called.

Change and scope

Cancellation is now published with signal.reason. A recognized physical code (EACCES, EPERM, ETIMEDOUT, ENOENT, and the other host failures already classified by this service) stays that failure when a late abort is also observed. A non-physical rejection while the signal is aborted, including the existing plain digest cancelled case, remains cancellation and now carries the caller reason.

A command ABORT_ERR remains cancellation, which is the previous command contract, and uses the caller reason when the signal is aborted. A digest or stat ABORT_ERR without an aborted signal stays ProviderAdapterError.

Follow the contribution scope. This is an ordinary classification fix inside existing reverse, pcap, and SQLite boundaries. Not applicable: no new provider, target execution, injection, mutation, or protection recovery.

Intentionally not included: GDB, native command, owned-command, pcap command, SQLite provider, and EVM cleanup bugs in the same audit cluster. Those already preserve the caller reason or primary failure on this main. Other application services that still omit signal.reason at admission are left for a separate change.

Contract and boundary impact

  • Semantic owner and earliest changed stage: application admission and reverse-engineering failure projection, before provider launch or after a settled command/digest result.
  • Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable.
  • CLI and MCP/tool-catalog contract: no schema or catalog change. Typed cancellation cause now carries the caller reason for these three services.
  • Provider, bridge, target-format, or platform compatibility: none. Injected service ports only.
  • Evidence, artifact, provenance, or reconstruction contract: post-output cancellation still retains partial Evidence and now also retains the abort reason.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): no target launch and no cleanup-owner change.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

Expected effects (check known effects; use documentation-only on its own).

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

Evidence and regression coverage

  • Tests added or updated: tests/composition/reverseEngineeringAdmission.test.ts (pre-abort reason, post-output reason, digest EACCES precedence, foreign digest ABORT_ERR, and aborted command EACCES/ETIMEDOUT/ABORT_ERR with and without captured output); src/application/sqlite/SqliteDatabaseService.test.ts; src/application/pcap/PcapAnalysisService.test.ts.
  • Base reproduction or other evidence: executed in-process probe on 40428da1d before the change. Reverse pre-abort was { tag: "AnalysisCancelledError", exact: false, causeAbsent: true, runs: 0 }. Digest denial was { tag: "AnalysisCancelledError", code: "EACCES" }. Pcap and SQLite pre-abort had causeAbsent: true and zero provider calls. The new assertions fail on that base because they require cause === reason or the physical error tag.
  • User-visible CLI/MCP output (if applicable): not exercised. These are service-boundary results.
  • Remaining proof gaps: no real objdump, tshark, capinfos, or SQLite worker. CLI/MCP delivery of the reason was not rechecked. Other application services that still construct a cause-less AnalysisCancelledError from a caller signal were not changed.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm run test:local -- tests/composition/reverseEngineeringAdmission.test.ts tests/composition/reverseEngineeringEdgeCases.test.ts tests/composition/reverseEngineering.test.ts tests/composition/reverseEngineeringCancellation.test.ts tests/composition/reverseEngineeringUnknownFailures.test.ts src/application/sqlite/SqliteDatabaseService.test.ts src/application/pcap/PcapAnalysisService.test.ts — 125 passed after ae52ee01d.
  • npm run verify:test-discovery — 1850 test files exactly once, on the previous commit.
  • npm run check:fast — typecheck and lint succeeded after ae52ee01d.
  • Node.js 24.18.0 on Linux. Real Hopper, Ghidra, objdump, tshark, and SQLite were not run.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Callers that previously saw cause === undefined on these cancellations now see the abort reason. Recognized physical failures are no longer replaced by cancellation solely because the signal is aborted. A digest ABORT_ERR without an aborted signal stays an adapter failure, matching the previous preflight classification.
  • Real Hopper/Ghidra, browser, or OS coverage: not run. Injected service ports only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new process, network, or target authority. The opaque abort reason is returned only as the typed error cause the caller supplied.

Author readiness

Human owner: @morluto

  • 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.
Open in Web Open in Cursor 

🔄 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/5671 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/20/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/caller-abort-reason-6040` --- ### 📝 Commits (2) - [`026ee20`](https://github.com/morluto/rea/commit/026ee2075e85d5a64f2d51f4d4ba9ba41d76023b) fix(errors): preserve caller abort reasons at admission - [`ae52ee0`](https://github.com/morluto/rea/commit/ae52ee01db16f32ece3b948740b9c4441a7a0f54) fix(reverse): keep a foreign digest ABORT_ERR as an adapter failure ### 📊 Changes **6 files changed** (+324 additions, -10 deletions) <details> <summary>View changed files</summary> ➕ `src/application/pcap/PcapAnalysisService.test.ts` (+28 -0) 📝 `src/application/pcap/PcapAnalysisService.ts` (+5 -1) 📝 `src/application/reverse/ReverseEngineeringService.ts` (+60 -8) 📝 `src/application/sqlite/SqliteDatabaseService.test.ts` (+22 -0) 📝 `src/application/sqlite/SqliteDatabaseService.ts` (+5 -1) 📝 `tests/composition/reverseEngineeringAdmission.test.ts` (+204 -0) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Fixes #5670. Reverse, pcap, and SQLite application admission were dropping the caller's abort reason, and a reverse-engineering digest or command failure could be reclassified as cancellation whenever the caller signal was already aborted. ## Problem and expected behavior `docs/tool-design.md` requires the exact caller abort reason as `AnalysisCancelledError.cause`, including cancellation observed after provider completion, and requires a recognized primary failure to keep its classification. On `40428da1dd6308f6f407547fd23b0a912232895a`, an injected probe with `AbortController.abort({ requested: "stop" })` observed: - `inspectWithObjdump` before launch returned `AnalysisCancelledError` with `cause` absent and did not run the provider. - The same call, aborted after the command returned stdout, kept partial Evidence and still omitted `cause`. - An injected digest that aborted and then rejected `EACCES` returned `AnalysisCancelledError` whose cause was that `EACCES` error. - `PcapAnalysisService.execute` and `SqliteDatabaseService.inspect` did the same at admission: `cause` absent, provider not called. ## Change and scope Cancellation is now published with `signal.reason`. A recognized physical code (`EACCES`, `EPERM`, `ETIMEDOUT`, `ENOENT`, and the other host failures already classified by this service) stays that failure when a late abort is also observed. A non-physical rejection while the signal is aborted, including the existing plain `digest cancelled` case, remains cancellation and now carries the caller reason. A command `ABORT_ERR` remains cancellation, which is the previous command contract, and uses the caller reason when the signal is aborted. A digest or stat `ABORT_ERR` without an aborted signal stays `ProviderAdapterError`. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). This is an ordinary classification fix inside existing reverse, pcap, and SQLite boundaries. Not applicable: no new provider, target execution, injection, mutation, or protection recovery. Intentionally not included: GDB, native command, owned-command, pcap command, SQLite provider, and EVM cleanup bugs in the same audit cluster. Those already preserve the caller reason or primary failure on this main. Other application services that still omit `signal.reason` at admission are left for a separate change. ## Contract and boundary impact - Semantic owner and earliest changed stage: application admission and reverse-engineering failure projection, before provider launch or after a settled command/digest result. - Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable. - CLI and MCP/tool-catalog contract: no schema or catalog change. Typed cancellation `cause` now carries the caller reason for these three services. - Provider, bridge, target-format, or platform compatibility: none. Injected service ports only. - Evidence, artifact, provenance, or reconstruction contract: post-output cancellation still retains partial Evidence and now also retains the abort reason. - Target selection, authority, upstream behavior, and cleanup details (if applicable): no target launch and no cleanup-owner change. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `tests/composition/reverseEngineeringAdmission.test.ts` (pre-abort reason, post-output reason, digest `EACCES` precedence, foreign digest `ABORT_ERR`, and aborted command `EACCES`/`ETIMEDOUT`/`ABORT_ERR` with and without captured output); `src/application/sqlite/SqliteDatabaseService.test.ts`; `src/application/pcap/PcapAnalysisService.test.ts`. - Base reproduction or other evidence: executed in-process probe on `40428da1d` before the change. Reverse pre-abort was `{ tag: "AnalysisCancelledError", exact: false, causeAbsent: true, runs: 0 }`. Digest denial was `{ tag: "AnalysisCancelledError", code: "EACCES" }`. Pcap and SQLite pre-abort had `causeAbsent: true` and zero provider calls. The new assertions fail on that base because they require `cause === reason` or the physical error tag. - User-visible CLI/MCP output (if applicable): not exercised. These are service-boundary results. - Remaining proof gaps: no real objdump, tshark, capinfos, or SQLite worker. CLI/MCP delivery of the reason was not rechecked. Other application services that still construct a cause-less `AnalysisCancelledError` from a caller signal were not changed. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run test:local -- tests/composition/reverseEngineeringAdmission.test.ts tests/composition/reverseEngineeringEdgeCases.test.ts tests/composition/reverseEngineering.test.ts tests/composition/reverseEngineeringCancellation.test.ts tests/composition/reverseEngineeringUnknownFailures.test.ts src/application/sqlite/SqliteDatabaseService.test.ts src/application/pcap/PcapAnalysisService.test.ts` — 125 passed after `ae52ee01d`. - `npm run verify:test-discovery` — 1850 test files exactly once, on the previous commit. - `npm run check:fast` — typecheck and lint succeeded after `ae52ee01d`. - Node.js 24.18.0 on Linux. Real Hopper, Ghidra, objdump, tshark, and SQLite were not run. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Callers that previously saw `cause === undefined` on these cancellations now see the abort reason. Recognized physical failures are no longer replaced by cancellation solely because the signal is aborted. A digest `ABORT_ERR` without an aborted signal stays an adapter failure, matching the previous preflight classification. - Real Hopper/Ghidra, browser, or OS coverage: not run. Injected service ports only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new process, network, or target authority. The opaque abort reason is returned only as the typed error cause the caller supplied. ## Author readiness Human owner: @morluto - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-f69ddd61-6ad5-558f-825d-393e2ec56040?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-f69ddd61-6ad5-558f-825d-393e2ec56040&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:44:49 +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#7025
No description provided.