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 #3407] [MERGED] refactor(pcap): give TShark selection and version admission one owner #5725

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3407
Author: @555aaditya
Created: 10/14/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: refactor/tshark-single-owner

📝 Commits (10+)

  • bbecf6f refactor(pcap): give TShark selection and version admission one owner
  • f4eeba3 fix(pcap): execute the TShark the shared locator selects
  • e74e4d8 Merge remote-tracking branch 'origin/main' into refactor/tshark-single-owner
  • a22adc7 Merge origin/main into refactor/tshark-single-owner
  • 658c29b chore: restore main's copies of files the merge hook reformatted
  • cb6dc4f fix(pcap): share selected tool identity verification
  • 211d4b2 perf(pcap): retain compact executable identity
  • 4924706 fix(pcap): report missing selected tools clearly
  • 5e046bb fix(pcap): read historical capture evidence
  • f2cffbd fix(pcap): preserve executable read failures

📊 Changes

21 files changed (+1038 additions, -129 deletions)

View changed files

📝 docs/packet-captures.md (+9 -2)
📝 docs/pcap-analysis.md (+10 -1)
📝 src/application/CapabilityInventory.ts (+1 -1)
📝 src/application/captures/PacketCaptureService.test.ts (+1 -0)
📝 src/captures/TsharkCaptureProvider.ts (+27 -18)
📝 src/contracts/captures/captureToolContracts.ts (+2 -2)
📝 src/domain/analysisView/pcapCaptureView.test.ts (+17 -0)
📝 src/domain/analysisView/pcapCaptureView.ts (+2 -2)
📝 src/domain/captures/packetCapture.ts (+5 -0)
📝 src/domain/pcap/pcapAnalysis.ts (+27 -0)
📝 src/pcap/PcapConfiguration.test.ts (+131 -2)
📝 src/pcap/PcapConfiguration.ts (+128 -54)
📝 src/pcap/PcapProvider.ts (+200 -39)
📝 src/server/createServer.ts (+20 -1)
📝 tests/boundary/captures/captureProvider.test.ts (+67 -2)
📝 tests/boundary/cli/pcapCli.test.ts (+1 -1)
➕ tests/boundary/mcp/packetCaptureAvailability.test.ts (+104 -0)
📝 tests/boundary/mcp/pcapMcp.test.ts (+6 -0)
📝 tests/boundary/pcap/pcapProvider.test.ts (+40 -1)
📝 tests/boundary/pcap/pcapProviderCancellation.test.ts (+134 -2)

...and 1 more files

📄 Description

Summary

Refs #3403, milestone 1. Share caller-selected TShark/Capinfos selection, version parsing and executable identity facts between pcap and packet-capture workflows, including server availability.

An absolute environment path is honored; an invalid relative value is refused. Without a configured value, selection uses an executable in an absolute PATH directory where the platform locator supports it. Both providers reuse the shared size/SHA owner and verify the selected binary before and after a run. Retained identity contains byte count/digest, not whole executable buffers.

Current inspect_pcap_client output includes resolved path, digest and verified/unresolved status for each tool. The advertised output schema requires these facts; historical retained Evidence is read through a separate compatibility schema that supplies null/unresolved for absent old fields. It never invents verified identity.

Executable-read cancellation and failed descriptor cleanup pass through ArtifactAnalysisResources, preserving the primary cancellation, cleanup observations and retry owner. Missing configured tools remain typed capability failures instead of unreadable output.

Validation

On pinned Node 24.18.0/npm 11.16.0, current focused schema/view/MCP/cross-platform tests passed 17 tests with 2 platform skips; npm run check:fast passed. Earlier focused configuration/provider sets passed 84 tests, with 25 host-gated skips.

The real Linux TShark/Capinfos lane 39682764813 passed on ancestor 4924706e, including focused Linux tests and verify-packet-capture.mjs. The later changes fix retained-Evidence compatibility, current fixtures and read-error mapping. The fresh exact-head real-provider run 39685186476 also passed on f2cffbdf, including Linux focused tests and verify-packet-capture.mjs. This is current-head Linux provider verification; Windows remains outside that proof.

Remaining coverage

Windows PATH/PATHEXT identity remains explicitly unresolved where the locator cannot establish an absolute binary. Packet-capture host support stays Linux-only. Shared Windows native bounds and CPU-ceiling alignment remain later #3403 work. This pass adds no target execution or mutation authority; provider commands inspect caller-selected capture files. Host TShark/Capinfos are unavailable locally.

Compatibility

Breaking change for inspect_pcap_* on Linux and macOS: with REA_TSHARK_COMMAND or REA_CAPINFOS_COMMAND unset, the tool must now be in an absolute PATH entry. Previously the bare name went to the process launcher, which also searched relative PATH entries. A setup whose TShark/Capinfos is reachable only through a relative PATH entry now fails with tshark_missing / capinfos_missing. Migration: put the tool in an absolute PATH directory or set the absolute REA_TSHARK_COMMAND / REA_CAPINFOS_COMMAND. Absolute environment paths, absolute PATH installs and Windows PATH/PATHEXT selection behave as before. inspect_packet_* previously accepted only an absolute REA_TSHARK_COMMAND, so it gains PATH installs and loses nothing.

Review follow-ups (merge of main at b8c1b4531)

  • Resolved the import conflicts with main's parseAnalysisViewResult (pcapCaptureView.ts) and privateWorkspaceFailure (TsharkCaptureProvider.ts), keeping pcapEvidenceSchemas.
  • A missing selected tool now names its configured path again ("The selected tshark executable /nonexistent/tshark could not be found at its configured path."). This restores the public CLI refusal that tests/boundary/cli/pcapCli.test.ts checks.
  • New tests:
    • A 3.x TShark banner and a non-Wireshark banner through the packet provider. Each pins the capability-unavailable reason and that only the version probe ran.
    • The inspect_packet_capture session availability rule over MCP: PATH-only, absolute and relative REA_TSHARK_COMMAND, plus the no-absolute-PATH-entry case. The first three are Linux-gated.
  • main's new late-cancellation service fixture now has tool.selection_source.
  • On macOS arm64 with Node 26.5.0: npm run test:fast passed (13,966 passed, 23 skipped). The pcap/captures/MCP set passed (154 passed, 39 host-gated skipped). The pcap CLI boundary test passed with a fresh build, and npm run check:fast passed. I didn't run the Linux-gated availability cases or real TShark locally.

Author readiness

Human owner: @555aaditya

  • 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.

Maintainer blocker verification

The shared selection/version boundary now also owns executable identity projection and same-run size/SHA checks for both packet-capture and pcap consumers. It retains compact byte-count/digest facts rather than whole executable buffers between calls. Absolute configured paths remain caller-selected; invalid relative environment paths fail rather than silently selecting PATH. Windows PATH/PATHEXT resolution remains explicitly unresolved where the locator cannot establish an absolute binary identity.

On Node 24.18.0/npm 11.16.0, the latest focused configuration/pcap/capture set passed 84 tests, with 25 platform-gated skips; npm run check:fast passed. TShark/Capinfos are unavailable locally. An exact-head hosted real-provider workflow has been requested separately; queued execution is not provider proof. Existing file-only analysis authority suffices for this correction; no new target execution/injection capability is added.

🔄 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/3407 **Author:** [@555aaditya](https://github.com/555aaditya) **Created:** 10/14/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `refactor/tshark-single-owner` --- ### 📝 Commits (10+) - [`bbecf6f`](https://github.com/morluto/rea/commit/bbecf6fb0551509e0b1e4790e7114a7399622b34) refactor(pcap): give TShark selection and version admission one owner - [`f4eeba3`](https://github.com/morluto/rea/commit/f4eeba365486b20ead0772bff44c0a0a3bf76486) fix(pcap): execute the TShark the shared locator selects - [`e74e4d8`](https://github.com/morluto/rea/commit/e74e4d8f0b8c56a712dd86bb7d91019deb55d804) Merge remote-tracking branch 'origin/main' into refactor/tshark-single-owner - [`a22adc7`](https://github.com/morluto/rea/commit/a22adc78092f3668fd5c3329aca1975eb5651713) Merge origin/main into refactor/tshark-single-owner - [`658c29b`](https://github.com/morluto/rea/commit/658c29b7fc8770252de3970e1713aea0457a1912) chore: restore main's copies of files the merge hook reformatted - [`cb6dc4f`](https://github.com/morluto/rea/commit/cb6dc4f3eff27ed2576c85a2f631b3811dc38dbb) fix(pcap): share selected tool identity verification - [`211d4b2`](https://github.com/morluto/rea/commit/211d4b221997cd0b5bbb3cf481b7c66f85d5c84c) perf(pcap): retain compact executable identity - [`4924706`](https://github.com/morluto/rea/commit/4924706e25106f3a0e463d3268cdee7906872cf9) fix(pcap): report missing selected tools clearly - [`5e046bb`](https://github.com/morluto/rea/commit/5e046bb374dca1d6342aba66bf910bde0c806e66) fix(pcap): read historical capture evidence - [`f2cffbd`](https://github.com/morluto/rea/commit/f2cffbdfdcac24755c38e71b923b8d7a43fb3c98) fix(pcap): preserve executable read failures ### 📊 Changes **21 files changed** (+1038 additions, -129 deletions) <details> <summary>View changed files</summary> 📝 `docs/packet-captures.md` (+9 -2) 📝 `docs/pcap-analysis.md` (+10 -1) 📝 `src/application/CapabilityInventory.ts` (+1 -1) 📝 `src/application/captures/PacketCaptureService.test.ts` (+1 -0) 📝 `src/captures/TsharkCaptureProvider.ts` (+27 -18) 📝 `src/contracts/captures/captureToolContracts.ts` (+2 -2) 📝 `src/domain/analysisView/pcapCaptureView.test.ts` (+17 -0) 📝 `src/domain/analysisView/pcapCaptureView.ts` (+2 -2) 📝 `src/domain/captures/packetCapture.ts` (+5 -0) 📝 `src/domain/pcap/pcapAnalysis.ts` (+27 -0) 📝 `src/pcap/PcapConfiguration.test.ts` (+131 -2) 📝 `src/pcap/PcapConfiguration.ts` (+128 -54) 📝 `src/pcap/PcapProvider.ts` (+200 -39) 📝 `src/server/createServer.ts` (+20 -1) 📝 `tests/boundary/captures/captureProvider.test.ts` (+67 -2) 📝 `tests/boundary/cli/pcapCli.test.ts` (+1 -1) ➕ `tests/boundary/mcp/packetCaptureAvailability.test.ts` (+104 -0) 📝 `tests/boundary/mcp/pcapMcp.test.ts` (+6 -0) 📝 `tests/boundary/pcap/pcapProvider.test.ts` (+40 -1) 📝 `tests/boundary/pcap/pcapProviderCancellation.test.ts` (+134 -2) _...and 1 more files_ </details> ### 📄 Description ## Summary Refs #3403, milestone 1. Share caller-selected TShark/Capinfos selection, version parsing and executable identity facts between pcap and packet-capture workflows, including server availability. An absolute environment path is honored; an invalid relative value is refused. Without a configured value, selection uses an executable in an absolute PATH directory where the platform locator supports it. Both providers reuse the shared size/SHA owner and verify the selected binary before and after a run. Retained identity contains byte count/digest, not whole executable buffers. Current `inspect_pcap_client` output includes resolved path, digest and verified/unresolved status for each tool. The advertised output schema requires these facts; historical retained Evidence is read through a separate compatibility schema that supplies null/unresolved for absent old fields. It never invents verified identity. Executable-read cancellation and failed descriptor cleanup pass through `ArtifactAnalysisResources`, preserving the primary cancellation, cleanup observations and retry owner. Missing configured tools remain typed capability failures instead of unreadable output. ## Validation On pinned Node 24.18.0/npm 11.16.0, current focused schema/view/MCP/cross-platform tests passed 17 tests with 2 platform skips; `npm run check:fast` passed. Earlier focused configuration/provider sets passed 84 tests, with 25 host-gated skips. The real Linux TShark/Capinfos lane [39682764813](https://github.com/morluto/rea/actions/runs/39682764813) passed on ancestor `4924706e`, including focused Linux tests and `verify-packet-capture.mjs`. The later changes fix retained-Evidence compatibility, current fixtures and read-error mapping. The fresh exact-head [real-provider run 39685186476](https://github.com/morluto/rea/actions/runs/39685186476) also passed on `f2cffbdf`, including Linux focused tests and `verify-packet-capture.mjs`. This is current-head Linux provider verification; Windows remains outside that proof. ## Remaining coverage Windows PATH/PATHEXT identity remains explicitly unresolved where the locator cannot establish an absolute binary. Packet-capture host support stays Linux-only. Shared Windows native bounds and CPU-ceiling alignment remain later #3403 work. This pass adds no target execution or mutation authority; provider commands inspect caller-selected capture files. Host TShark/Capinfos are unavailable locally. ## Compatibility Breaking change for `inspect_pcap_*` on Linux and macOS: with `REA_TSHARK_COMMAND` or `REA_CAPINFOS_COMMAND` unset, the tool must now be in an **absolute** PATH entry. Previously the bare name went to the process launcher, which also searched relative PATH entries. A setup whose TShark/Capinfos is reachable only through a relative PATH entry now fails with `tshark_missing` / `capinfos_missing`. Migration: put the tool in an absolute PATH directory or set the absolute `REA_TSHARK_COMMAND` / `REA_CAPINFOS_COMMAND`. Absolute environment paths, absolute PATH installs and Windows PATH/PATHEXT selection behave as before. `inspect_packet_*` previously accepted only an absolute `REA_TSHARK_COMMAND`, so it gains PATH installs and loses nothing. ## Review follow-ups (merge of `main` at b8c1b4531) - Resolved the import conflicts with `main`'s `parseAnalysisViewResult` (`pcapCaptureView.ts`) and `privateWorkspaceFailure` (`TsharkCaptureProvider.ts`), keeping `pcapEvidenceSchemas`. - A missing selected tool now names its configured path again ("The selected tshark executable /nonexistent/tshark could not be found at its configured path."). This restores the public CLI refusal that `tests/boundary/cli/pcapCli.test.ts` checks. - New tests: - A 3.x TShark banner and a non-Wireshark banner through the packet provider. Each pins the capability-unavailable reason and that only the version probe ran. - The `inspect_packet_capture` session availability rule over MCP: PATH-only, absolute and relative `REA_TSHARK_COMMAND`, plus the no-absolute-PATH-entry case. The first three are Linux-gated. - `main`'s new late-cancellation service fixture now has `tool.selection_source`. - On macOS arm64 with Node 26.5.0: `npm run test:fast` passed (13,966 passed, 23 skipped). The pcap/captures/MCP set passed (154 passed, 39 host-gated skipped). The pcap CLI boundary test passed with a fresh build, and `npm run check:fast` passed. I didn't run the Linux-gated availability cases or real TShark locally. ## 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: @555aaditya - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] 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. <!-- maintainer-blocker-review --> ### Maintainer blocker verification The shared selection/version boundary now also owns executable identity projection and same-run size/SHA checks for both packet-capture and pcap consumers. It retains compact byte-count/digest facts rather than whole executable buffers between calls. Absolute configured paths remain caller-selected; invalid relative environment paths fail rather than silently selecting PATH. Windows PATH/PATHEXT resolution remains explicitly unresolved where the locator cannot establish an absolute binary identity. On Node 24.18.0/npm 11.16.0, the latest focused configuration/pcap/capture set passed 84 tests, with 25 platform-gated skips; `npm run check:fast` passed. TShark/Capinfos are unavailable locally. An exact-head hosted real-provider workflow has been requested separately; queued execution is not provider proof. Existing file-only analysis authority suffices for this correction; no new target execution/injection capability is added. --- <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:57 +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#5725
No description provided.