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 #4443] [MERGED] fix(filesystem): observe cancellation after file finalization #6248

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

📋 Pull Request Information

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

Base: main ← Head: fix/regular-file-finalization-4379

📝 Commits (5)

  • fce5078 fix(filesystem): observe cancellation after file finalization
  • ce876b9 test(kuna): distinguish cancellation across installation phases
  • b8f2a4a fix(filesystem): retain completed reads when cleanup fails
  • 3d20ad1 fix(filesystem): retain completed values under cancellation
  • 025fd7d fix(filesystem): bind cancellation markers to their file owner

📊 Changes

7 files changed (+543 additions, -178 deletions)

View changed files

📝 src/adb/AdbProvider.ts (+31 -20)
📝 src/application/RegularFileRead.ts (+16 -7)
📝 src/filesystem/OwnedRegularFile.ts (+35 -0)
➕ tests/boundary/filesystem/regularFileCancellation.test.ts (+233 -0)
📝 tests/boundary/filesystem/stableFileHashOwnership.test.ts (+49 -1)
📝 tests/boundary/providers/adb/adbInputSnapshotOwnership.test.ts (+125 -100)
📝 tests/boundary/providers/kuna/kunaInstallationLifetime.test.ts (+54 -50)

📄 Description

Summary

Fixes #4379. Regular-file reads observe cancellation after metadata, descriptor closure and close retries. Completed file facts remain available under cancellation, including digests of already acquired ADB files. Part of #4227.

Problem and expected behavior

An unchanged file could be returned successfully after cancellation during its final real stat or close. Checking cancellation must also retain physical observations already completed: reporting a known acquired-file digest as unknown loses evidence. An incomplete close must retain its original outcome and exact cleanup owner.

Change and scope

The descriptor owner emits RegularFileCancelled only after confirmed close, carrying the completed read outcome and caller reason separately. Existing read errors stay primary; failed close keeps RegularFileCleanupFailure and its original physical outcome. Ordinary withRegularFile readers unwrap only cancellation tied to their admitted FileHandle object, preserve exact raw abort reasons and nested callback failures, and check again after resource-scope retries; the redundant forwarding wrapper is removed. Caller-provided reason objects stay opaque.

ADB uses one digest-failure mapper for file, package and bugreport acquisition. It retains completed hashes from either cancellation or failed cleanup, without claiming cleanup uncertainty after confirmed close. The former cleanup-only wrapper/normalizer is replaced. No extra file I/O, cache or normal-path data copy is introduced.

Contract and boundary impact

  • Semantic owner: shared descriptor finalization, application-owned retries, then ADB's existing partial-observation mapping.
  • Contribution scope: existing file-read/acquisition lifecycle fix; new-capability maintainer decision not applicable.
  • CLI/MCP/catalog: shared implementation; no input, schema or success-response change. Cancellation can retain known digest fields in the existing partial-result shape.
  • Compatibility: Linux x64 executed; other local hosts and physical ADB devices unavailable.
  • Evidence: source bytes/record IDs/artifact metadata preserved; completed observations, caller cancellation and cleanup proof remain distinct.
  • Authority: existing read-only file access and caller-selected ADB acquisition/output paths; no new device, execution or cleanup authority.
  • Generated/package/installation impact: none.

Existing affected operations have these effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Change process memory, registers, files, or configuration.
  • Contact network services.

The latter effects belong to existing ADB helper/service interaction and host output files. Deterministic ADB tests use a simulated command transport and real local files; no physical-device execution is claimed.

Evidence and regression coverage

  • Original reporter probe reproduced on fresh Linux main 781d5751a: final real descriptor stat settles after abort, but bytes are returned; descriptor closes. Five finalization regressions fail on base while both physical-result/primary-failure retention controls pass.

  • Compiled probes on a genuine public Evidence export: final metadata/close cancellation preserves the exact caller reason; denied close retains payload and owner for successful retry. Completed stable-file hash remains available under cancellation after successful close. Typed Evidence consumer keeps the original reason in its cause chain.

  • ADB single-file/split-package tests preserve completed hashes through both successful close cancellation and failed cleanup, retain original abort causes, and distinguish cleared from pending cleanup. The successful-close digest regression failed on reviewed head b8f2a4ae2 before this follow-up (1 failed,14 passed).

  • Nested regression: both same-path cases (shared and independent signals) fail on reviewed head 3d20ad181 before the owner-identity fix (2 failed, 8 passed). Final compiled probes preserve the inner owner, path and completed value, and close both descriptors. Matching uses actual FileHandle identity, not path or signal equality.

  • Kuna lifetime coverage separately proves early cancellation stops before shebang admission and later cancellation keeps cleanup waiting through shebang reading.

  • Public compiled CLI/actual stdio MCP: import → filtered summaries → malformed-input recovery → complete export → close/reimport passes twice per revision, preserving all 3 record IDs and artifact metadata.

  • Gaps: exact cancellation timing is production-boundary fault injection around real filesystem calls, not a public SDK cancellation reproduction. ADB transport is simulated; no new native-engine or physical-device claim. Separate stream-abort ownership report #4381 remains outside this fix.

  • 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

Final head 025fd7df471d345c71299ebe185724311b442c5a (source checks immediately before the unchanged commit):

  • npm run test:focused -- 50 related filesystem, JSON, snapshot, ADB, managed/JADX/Kuna, publisher and setup files — 570 passed.
  • npm run check:fast and npm run docs:check — passed; docs include 5 README consistency cases.
  • Exact-head compiled real-file/stable-hash cancellation, denied-close/retry and nested-owner probes — passed; original public export SHA-256 8d1e5d911b4c0b49ec33f2e4884ad7a9ae7212517237c8c46de01814e02100e8 unchanged.
  • Exact-head public CLI/MCP task — passed twice; 9 MCP calls/task. Baseline 1f5ca5ade has the identical tree to starting main 781d5751a.

Completed public-task medians, two fresh-process runs/revision: base/fix wall 4.78/4.88s, CPU 5.95/5.97s, sampled family RSS 0.640/0.645GiB. All 9 MCP request+full-reply o200k proxy totals: base 2,668–2,673, fix 2,678–2,683. Schemas/control/CLI output/model billing and physical-device overhead are unmeasured. Filesystem/module caches uncontrolled; repeated import reuses its connection. No speedup or context-reduction claim. Serial jobs use 2 CPU cores and a 3 GiB Node heap. RSS sampling may double-count shared pages or miss short children; CPU includes only reaped descendants. Raw attempts and performance-owners.json: /tmp/rea-4379-file-finalization-20261016/.

Compatibility, safety, and release

No breaking change, migration, dependency, installation or generated-file change. Descriptor ownership checks stay intact; failed cleanup is never inferred complete. Only completed observations are retained, without extra copies. No ambient environment dump was persisted. Local real-provider scope is filesystem/Evidence workflows; GUI providers and physical ADB hardware were not used for this focused fix.

Author readiness

Human owner: @N0zoM1z0

Entered under the human owner's explicit working-session instruction to complete the declarations and request review. The assistant performed implementation and validation review; this does not claim a separate manual human review.

  • 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/4443 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/16/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/regular-file-finalization-4379` --- ### 📝 Commits (5) - [`fce5078`](https://github.com/morluto/rea/commit/fce5078509456c8f1dc050cd16e331a339d23fef) fix(filesystem): observe cancellation after file finalization - [`ce876b9`](https://github.com/morluto/rea/commit/ce876b92a1fe9ceb298eb13bbc4b2c97f9619ddf) test(kuna): distinguish cancellation across installation phases - [`b8f2a4a`](https://github.com/morluto/rea/commit/b8f2a4ae25c0859d96e57f56dc73197969aa3431) fix(filesystem): retain completed reads when cleanup fails - [`3d20ad1`](https://github.com/morluto/rea/commit/3d20ad181c5d51f26b02ad3f0b6eca8cb2f9a4c4) fix(filesystem): retain completed values under cancellation - [`025fd7d`](https://github.com/morluto/rea/commit/025fd7df471d345c71299ebe185724311b442c5a) fix(filesystem): bind cancellation markers to their file owner ### 📊 Changes **7 files changed** (+543 additions, -178 deletions) <details> <summary>View changed files</summary> 📝 `src/adb/AdbProvider.ts` (+31 -20) 📝 `src/application/RegularFileRead.ts` (+16 -7) 📝 `src/filesystem/OwnedRegularFile.ts` (+35 -0) ➕ `tests/boundary/filesystem/regularFileCancellation.test.ts` (+233 -0) 📝 `tests/boundary/filesystem/stableFileHashOwnership.test.ts` (+49 -1) 📝 `tests/boundary/providers/adb/adbInputSnapshotOwnership.test.ts` (+125 -100) 📝 `tests/boundary/providers/kuna/kunaInstallationLifetime.test.ts` (+54 -50) </details> ### 📄 Description ## Summary Fixes #4379. Regular-file reads observe cancellation after metadata, descriptor closure and close retries. Completed file facts remain available under cancellation, including digests of already acquired ADB files. Part of #4227. ## Problem and expected behavior An unchanged file could be returned successfully after cancellation during its final real stat or close. Checking cancellation must also retain physical observations already completed: reporting a known acquired-file digest as unknown loses evidence. An incomplete close must retain its original outcome and exact cleanup owner. ## Change and scope The descriptor owner emits `RegularFileCancelled` only after confirmed close, carrying the completed read outcome and caller reason separately. Existing read errors stay primary; failed close keeps `RegularFileCleanupFailure` and its original physical outcome. Ordinary `withRegularFile` readers unwrap only cancellation tied to their admitted FileHandle object, preserve exact raw abort reasons and nested callback failures, and check again after resource-scope retries; the redundant forwarding wrapper is removed. Caller-provided reason objects stay opaque. ADB uses one digest-failure mapper for file, package and bugreport acquisition. It retains completed hashes from either cancellation or failed cleanup, without claiming cleanup uncertainty after confirmed close. The former cleanup-only wrapper/normalizer is replaced. No extra file I/O, cache or normal-path data copy is introduced. ## Contract and boundary impact - Semantic owner: shared descriptor finalization, application-owned retries, then ADB's existing partial-observation mapping. - Contribution scope: existing file-read/acquisition lifecycle fix; new-capability maintainer decision not applicable. - CLI/MCP/catalog: shared implementation; no input, schema or success-response change. Cancellation can retain known digest fields in the existing partial-result shape. - Compatibility: Linux x64 executed; other local hosts and physical ADB devices unavailable. - Evidence: source bytes/record IDs/artifact metadata preserved; completed observations, caller cancellation and cleanup proof remain distinct. - Authority: existing read-only file access and caller-selected ADB acquisition/output paths; no new device, execution or cleanup authority. - Generated/package/installation impact: none. Existing affected operations have these effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [x] Change process memory, registers, files, or configuration. - [x] Contact network services. The latter effects belong to existing ADB helper/service interaction and host output files. Deterministic ADB tests use a simulated command transport and real local files; no physical-device execution is claimed. ## Evidence and regression coverage - Original reporter probe reproduced on fresh Linux main `781d5751a`: final real descriptor stat settles after abort, but bytes are returned; descriptor closes. Five finalization regressions fail on base while both physical-result/primary-failure retention controls pass. - Compiled probes on a genuine public Evidence export: final metadata/close cancellation preserves the exact caller reason; denied close retains payload and owner for successful retry. Completed stable-file hash remains available under cancellation after successful close. Typed Evidence consumer keeps the original reason in its cause chain. - ADB single-file/split-package tests preserve completed hashes through both successful close cancellation and failed cleanup, retain original abort causes, and distinguish cleared from pending cleanup. The successful-close digest regression failed on reviewed head `b8f2a4ae2` before this follow-up (1 failed,14 passed). - Nested regression: both same-path cases (shared and independent signals) fail on reviewed head `3d20ad181` before the owner-identity fix (2 failed, 8 passed). Final compiled probes preserve the inner owner, path and completed value, and close both descriptors. Matching uses actual FileHandle identity, not path or signal equality. - Kuna lifetime coverage separately proves early cancellation stops before shebang admission and later cancellation keeps cleanup waiting through shebang reading. - Public compiled CLI/actual stdio MCP: import → filtered summaries → malformed-input recovery → complete export → close/reimport passes twice per revision, preserving all 3 record IDs and artifact metadata. - Gaps: exact cancellation timing is production-boundary fault injection around real filesystem calls, not a public SDK cancellation reproduction. ADB transport is simulated; no new native-engine or physical-device claim. Separate stream-abort ownership report #4381 remains outside this fix. - [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 Final head `025fd7df471d345c71299ebe185724311b442c5a` (source checks immediately before the unchanged commit): - `npm run test:focused --` 50 related filesystem, JSON, snapshot, ADB, managed/JADX/Kuna, publisher and setup files — **570 passed**. - `npm run check:fast` and `npm run docs:check` — passed; docs include 5 README consistency cases. - Exact-head compiled real-file/stable-hash cancellation, denied-close/retry and nested-owner probes — passed; original public export SHA-256 `8d1e5d911b4c0b49ec33f2e4884ad7a9ae7212517237c8c46de01814e02100e8` unchanged. - Exact-head public CLI/MCP task — passed twice; 9 MCP calls/task. Baseline `1f5ca5ade` has the identical tree to starting main `781d5751a`. Completed public-task medians, two fresh-process runs/revision: base/fix wall 4.78/4.88s, CPU 5.95/5.97s, sampled family RSS 0.640/0.645GiB. All 9 MCP request+full-reply o200k proxy totals: base 2,668–2,673, fix 2,678–2,683. Schemas/control/CLI output/model billing and physical-device overhead are unmeasured. Filesystem/module caches uncontrolled; repeated import reuses its connection. No speedup or context-reduction claim. Serial jobs use 2 CPU cores and a 3 GiB Node heap. RSS sampling may double-count shared pages or miss short children; CPU includes only reaped descendants. Raw attempts and `performance-owners.json`: `/tmp/rea-4379-file-finalization-20261016/`. ## Compatibility, safety, and release No breaking change, migration, dependency, installation or generated-file change. Descriptor ownership checks stay intact; failed cleanup is never inferred complete. Only completed observations are retained, without extra copies. No ambient environment dump was persisted. Local real-provider scope is filesystem/Evidence workflows; GUI providers and physical ADB hardware were not used for this focused fix. ## Author readiness Human owner: @N0zoM1z0 Entered under the human owner's explicit working-session instruction to complete the declarations and request review. The assistant performed implementation and validation review; this does not claim a separate manual human review. - [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:13:00 +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#6248
No description provided.