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 #3265] [CLOSED] fix(target): classify cancellation during file admission #5685

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3265
Author: @SII-YDD
Created: 10/14/2026
Status: ❌ Closed

Base: main ← Head: fix/target-admission-cancellation

📝 Commits (1)

  • 136a9ed fix(target): classify cancellation during file admission

📊 Changes

2 files changed (+260 additions, -0 deletions)

View changed files

📝 src/application/BinaryTargetResolver.ts (+4 -0)
➕ tests/process-global/binaryTargetAdmissionCancellation.test.ts (+256 -0)

📄 Description

Summary

Fixes #3197. Cancelling file admission during its first descriptor stat now returns the existing cancelled diagnostic instead of UNKNOWN or a raw rejected cancellation value.

Problem and expected behavior

Run rea inspect sample.bin --format json or rea analyze sample.bin --format json and send SIGINT after the first real FileHandle.stat() completes, before admission continues. Previously both commands reported UNKNOWN; cancellation after the resolver's second stat already reported cancelled. SDK cancellation of open_binary could likewise leave the server-side operation rejected with its raw signal reason.

The resolver's declared result includes AnalysisCancelledError, so both cancellation checkpoints should settle with that error after successful descriptor cleanup. The issue reporter describes P2 impact; this PR does not claim an upstream P1 classification.

Change and scope

parseBinaryTarget now recognizes a caught value that is exactly the aborted signal's reason and wraps it as AnalysisCancelledError("resolve_binary_target"). openRegularFile remains a generic filesystem primitive using Node's cancellation semantics; the application resolver owns this domain normalization.

The identity check preserves unrelated I/O failures occurring alongside cancellation and does not hide the RegularFileAdmissionFailure wrapper or its retained cleanup owner. Existing tagged cancellation errors keep their metadata. No new provider, execution capability, or configuration is introduced; additional maintainer scope authorization is not applicable to this correction within the existing admission boundary.

Contract and boundary impact

  • Semantic owner and earliest changed stage: application target resolution, catching an abort from regular-file admission.

  • Contribution scope fit and linked maintainer decision: ordinary correctness fix within an existing boundary; additional scope decision not applicable.

  • CLI and MCP/tool-catalog contract: existing cancelled error shape and operation; tool names, parameters and advertised schemas unchanged.

  • Provider, bridge, target-format, or platform compatibility: provider dispatch and format selection unchanged; cancellation happens before provider creation.

  • Evidence, artifact, provenance, or reconstruction contract: source bytes unchanged; no new evidence or reconstruction representation.

  • Target selection, authority, upstream behavior, and cleanup details: caller selections unchanged; failed admission closes its real descriptor, and a failed close retains its existing error and owner for retry.

  • Generated metadata, package, or installation impact: none; generated documentation checks passed without authored metadata changes.

  • 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

  • Added ten regressions using real open/stat/close operations, controlling only cancellation timing and injected failure cases. Default, Error and string reasons cover both stat checkpoints. Controls cover unsupported input, concurrent unrelated EIO, and failed close with retained ownership and successful close retry.

  • On unmodified base 7375ab6e34e511095a74d5a67e57cec28d56fd10, four regressions failed and six controls passed. The early cancellations threw raw reasons, including the actual SDK server signal's string reason. The corrected tests all pass, including on synchronized base 29d3dcb7ea85b3be37cd81e977ae4e09cebdd2fc.

  • Real SDK open_binary uses the existing application MCP harness and real session implementation. The test validates advertised input arguments, sends SDK cancellation, waits for the server operation to settle and its descriptor to close, then pings and retries on the same connection. The retry preserves the ordinary unsupported-format diagnostic; the provider factory is never called.

  • Executed compiled CLI proof used a local timing hook forwarding real descriptor stat and delivering SIGINT at the boundary. inspect and analyze changed from UNKNOWN to {code:"cancelled", category:"cancelled", retryable:true, details:{operation:"resolve_binary_target", cleanup:"complete"}}. Late-stat cancellation and noncancelled unsupported-format controls remain unchanged.

  • Remaining proof gaps: naturally occurring race frequency is not measured; SDK testing uses the project's in-memory transport, while CLI SIGINT is executed in real child processes. No native engine or other host-platform execution is claimed. Cancellation remediation contains no new tool/parameter instructions.

  • 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:focused -- tests/process-global/binaryTargetAdmissionCancellation.test.ts tests/boundary/filesystem/binaryTarget.test.ts tests/boundary/filesystem/rawBinaryTarget.test.ts tests/boundary/filesystem/targetDiagnostics.test.ts src/artifacts/RegularFileAdmission.test.ts — 110 tests passed across five files.
  • npm run check:fast, npm run check, npm run check:ci — passed; includes duplicate-code, TODO and architecture gates, without changing exclusions or thresholds.
  • npm run verify:test-discovery — all 1,253 test files discovered exactly once.
  • npm run docs:check — passed, including five README consistency tests.
  • Compiled CLI SIGINT proof — five invocations executed: early/late cancellation for inspect/analyze plus noncancelled unsupported input.
  • Independent read-only review — no findings; not a substitute for CI.
  • Upstream CI — completed successfully on head 136a9ed9df5b21a9110e412462fb5e8d20549935: 13 successful jobs and 17 conditional skips. At final verification the PR's associated checks are 16 successful / 17 conditional skips; required CI passed. Its fast tier does not execute coverage.
  • Unchanged full workflow in the author's fork — completed successfully on the same head, attempt 2: 36 successful jobs / 1 conditional skip (the source-only job is not selected in full tier). Six coverage shards and the portable coverage/timing merge passed: 14,150 tests passed, 125 conditional skips, 90.57% line coverage. The existing reverse-tools coverage and mutation tasks also passed; this does not claim mutation scoring of the new admission guard. The Apple lane's existing target-free sessionMcp.test.ts case initially hit its 10-second timeout. Its six tests passed unchanged locally (the timed-out case took 1.87 seconds), and the original Apple job and dependent required summary passed after one unchanged rerun. The initial failure is retained; no code, timeout, assertion, exclusion or threshold was altered to obtain this result. Fork checks are supplemental evidence, not upstream required checks.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. This restores the existing typed cancellation contract.
  • Real Hopper/Ghidra, browser, or OS coverage: macOS file admission and compiled CLI executed; no provider changes or claims of real-engine validation.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new target execution or network access; tests preserve source bytes and explicitly assert no provider creation. Existing shared harness, temporary-directory registration and owned cleanup are reused.
  • AI assistance: implementation, test design, investigation and review were assisted by OpenAI Codex; the commands and results above were executed, rather than inferred from generated code.

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/3265 **Author:** [@SII-YDD](https://github.com/SII-YDD) **Created:** 10/14/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/target-admission-cancellation` --- ### 📝 Commits (1) - [`136a9ed`](https://github.com/morluto/rea/commit/136a9ed9df5b21a9110e412462fb5e8d20549935) fix(target): classify cancellation during file admission ### 📊 Changes **2 files changed** (+260 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/application/BinaryTargetResolver.ts` (+4 -0) ➕ `tests/process-global/binaryTargetAdmissionCancellation.test.ts` (+256 -0) </details> ### 📄 Description ## Summary Fixes #3197. Cancelling file admission during its first descriptor stat now returns the existing `cancelled` diagnostic instead of `UNKNOWN` or a raw rejected cancellation value. ## Problem and expected behavior Run `rea inspect sample.bin --format json` or `rea analyze sample.bin --format json` and send SIGINT after the first real `FileHandle.stat()` completes, before admission continues. Previously both commands reported `UNKNOWN`; cancellation after the resolver's second stat already reported `cancelled`. SDK cancellation of `open_binary` could likewise leave the server-side operation rejected with its raw signal reason. The resolver's declared result includes `AnalysisCancelledError`, so both cancellation checkpoints should settle with that error after successful descriptor cleanup. The issue reporter describes P2 impact; this PR does not claim an upstream P1 classification. ## Change and scope `parseBinaryTarget` now recognizes a caught value that is exactly the aborted signal's `reason` and wraps it as `AnalysisCancelledError("resolve_binary_target")`. `openRegularFile` remains a generic filesystem primitive using Node's cancellation semantics; the application resolver owns this domain normalization. The identity check preserves unrelated I/O failures occurring alongside cancellation and does not hide the `RegularFileAdmissionFailure` wrapper or its retained cleanup owner. Existing tagged cancellation errors keep their metadata. No new provider, execution capability, or configuration is introduced; additional maintainer scope authorization is not applicable to this correction within the existing admission boundary. ## Contract and boundary impact - Semantic owner and earliest changed stage: application target resolution, catching an abort from regular-file admission. - Contribution scope fit and linked maintainer decision: ordinary correctness fix within an existing boundary; additional scope decision not applicable. - CLI and MCP/tool-catalog contract: existing cancelled error shape and operation; tool names, parameters and advertised schemas unchanged. - Provider, bridge, target-format, or platform compatibility: provider dispatch and format selection unchanged; cancellation happens before provider creation. - Evidence, artifact, provenance, or reconstruction contract: source bytes unchanged; no new evidence or reconstruction representation. - Target selection, authority, upstream behavior, and cleanup details: caller selections unchanged; failed admission closes its real descriptor, and a failed close retains its existing error and owner for retry. - Generated metadata, package, or installation impact: none; generated documentation checks passed without authored metadata changes. - [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 - Added ten regressions using real open/stat/close operations, controlling only cancellation timing and injected failure cases. Default, Error and string reasons cover both stat checkpoints. Controls cover unsupported input, concurrent unrelated EIO, and failed close with retained ownership and successful close retry. - On unmodified base `7375ab6e34e511095a74d5a67e57cec28d56fd10`, four regressions failed and six controls passed. The early cancellations threw raw reasons, including the actual SDK server signal's string reason. The corrected tests all pass, including on synchronized base `29d3dcb7ea85b3be37cd81e977ae4e09cebdd2fc`. - Real SDK `open_binary` uses the existing application MCP harness and real session implementation. The test validates advertised input arguments, sends SDK cancellation, waits for the server operation to settle and its descriptor to close, then pings and retries on the same connection. The retry preserves the ordinary unsupported-format diagnostic; the provider factory is never called. - Executed compiled CLI proof used a local timing hook forwarding real descriptor stat and delivering SIGINT at the boundary. `inspect` and `analyze` changed from `UNKNOWN` to `{code:"cancelled", category:"cancelled", retryable:true, details:{operation:"resolve_binary_target", cleanup:"complete"}}`. Late-stat cancellation and noncancelled unsupported-format controls remain unchanged. - Remaining proof gaps: naturally occurring race frequency is not measured; SDK testing uses the project's in-memory transport, while CLI SIGINT is executed in real child processes. No native engine or other host-platform execution is claimed. Cancellation remediation contains no new tool/parameter instructions. - [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:focused -- tests/process-global/binaryTargetAdmissionCancellation.test.ts tests/boundary/filesystem/binaryTarget.test.ts tests/boundary/filesystem/rawBinaryTarget.test.ts tests/boundary/filesystem/targetDiagnostics.test.ts src/artifacts/RegularFileAdmission.test.ts` — 110 tests passed across five files. - `npm run check:fast`, `npm run check`, `npm run check:ci` — passed; includes duplicate-code, TODO and architecture gates, without changing exclusions or thresholds. - `npm run verify:test-discovery` — all 1,253 test files discovered exactly once. - `npm run docs:check` — passed, including five README consistency tests. - Compiled CLI SIGINT proof — five invocations executed: early/late cancellation for inspect/analyze plus noncancelled unsupported input. - Independent read-only review — no findings; not a substitute for CI. - [Upstream CI](https://github.com/morluto/rea/actions/runs/38525920062) — completed successfully on head `136a9ed9df5b21a9110e412462fb5e8d20549935`: 13 successful jobs and 17 conditional skips. At final verification the PR's associated checks are 16 successful / 17 conditional skips; required CI passed. Its fast tier does not execute coverage. - [Unchanged full workflow in the author's fork](https://github.com/SII-YDD/rea/actions/runs/38526903032) — completed successfully on the same head, attempt 2: 36 successful jobs / 1 conditional skip (the source-only job is not selected in full tier). Six coverage shards and the portable coverage/timing merge passed: 14,150 tests passed, 125 conditional skips, 90.57% line coverage. The existing reverse-tools coverage and mutation tasks also passed; this does not claim mutation scoring of the new admission guard. The Apple lane's existing target-free `sessionMcp.test.ts` case initially hit its 10-second timeout. Its six tests passed unchanged locally (the timed-out case took 1.87 seconds), and the original Apple job and dependent required summary passed after one unchanged rerun. The initial failure is retained; no code, timeout, assertion, exclusion or threshold was altered to obtain this result. Fork checks are supplemental evidence, not upstream required checks. ## Compatibility, safety, and release - Breaking changes or migration steps: none. This restores the existing typed cancellation contract. - Real Hopper/Ghidra, browser, or OS coverage: macOS file admission and compiled CLI executed; no provider changes or claims of real-engine validation. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new target execution or network access; tests preserve source bytes and explicitly assert no provider creation. Existing shared harness, temporary-directory registration and owned cleanup are reused. - AI assistance: implementation, test design, investigation and review were assisted by OpenAI Codex; the commands and results above were executed, rather than inferred from generated code. ## 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:08:37 +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#5685
No description provided.