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 #6512] [CLOSED] fix(pcap): report capture summaries unsupported off their verified hosts #7375

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6512
Author: @kittimzhe
Created: 10/23/2026
Status: ❌ Closed

Base: main ← Head: fix/pcap-capture-host-availability

📝 Commits (1)

  • 652e56f fix(pcap): report capture summaries unsupported off their verified hosts

📊 Changes

6 files changed (+64 additions, -12 deletions)

View changed files

📝 src/application/CapabilityInventory.test.ts (+18 -0)
📝 src/application/CapabilityInventory.ts (+10 -0)
📝 src/composition/pcap.ts (+3 -0)
📝 src/pcap/PcapNativeBound.ts (+18 -10)
📝 src/server/createServer.ts (+9 -1)
📝 tests/process-global/hostRestrictedAvailabilityMcp.test.ts (+6 -1)

📄 Description

Fixes #5711

Related: #6179 proposed the same classification before #5793 introduced the host-restriction mechanism. This PR follows that mechanism on current main and adds MCP-level coverage; happy to defer if the maintainers prefer rebasing #6179 instead.

Summary

Target-free discovery advertises inspect_pcap_capture as available: true on hosts whose capture execution refuses: the pcap-provider kind fallback in the availability projection returns available unconditionally, so on macOS the catalog promises a callable operation while the native bound gate rejects the host at execution with capability_unavailable. The host-independent inspect_pcap_client version probe keeps its availability either way.

Problem and expected behavior

  • Smallest trigger: on a non-Linux, non-Windows host with a tshark on PATH, run a target-free binary_session {} and read tool_availability; inspect_pcap_capture reports {"available": true, "reason": "available"} even though calling it returns the typed refusal Packet summaries require an enforceable native memory bound: Linux with util-linux prlimit, or Windows with owned Job Objects. This host's capture boundary remains unsupported. The same over-advertisement appears with no tshark configured.
  • Violated invariant: the same one #5793 established for the other Linux-only integrations — an unavailable tool's machine-readable reason should name the actual blocker, and no configuration can make a host-restricted integration pass its execution host check. The mechanism this adds to is HOST_RESTRICTED_FEATURES / hostUnsupported / verifiedHost from #5793.
  • Expected: inspect_pcap_capture reports unsupported_host with the execution gate's remediation on hosts outside its verified set; Linux and Windows (Job Object bound) stay available; the client probe keeps available on every host; injected pcap services own their availability on any host.

Change and scope

  • src/pcap/PcapNativeBound.ts now owns and exports pcapCaptureHostSupported (linux || win32) and its gate uses it — discovery and execution share the one check, replacing the inline platform pair that previously lived only in the gate.
  • src/composition/pcap.ts re-exports it; src/server/createServer.ts records pcapCapture in verifiedHost and in hostUnsupported through the existing outsideVerifiedHost(options.pcapAnalysis, ...) injection exemption.
  • src/application/CapabilityInventory.ts adds "pcapCapture" to HOST_RESTRICTED_FEATURES and classifies inspect_pcap_capture through hostRestrictedAvailability with the gate's exact remediation text. The enabled argument is true: the pcap family registers on every host, so the remaining unavailability dimension is configuration at execution, which is out of this issue's scope (noted below).
  • inspect_pcap_client is untouched — it stays on the kind fallback and remains available wherever the provider is constructed.
  • Intentionally not included: the no-tshark case still reports available for the family, exactly as before; #5711 asks for the host limitation split, and a configuration-aware availability for the pcap family can follow the pattern #5793 uses for packetCaptureEnabled if the maintainers want it. #6179's approach (a separate pcapCaptureHostSupported policy field) achieves the same classification but predates the hostUnsupported mechanism and conflicts with current main.
  • Contribution scope: ordinary fix within existing boundaries — no maintainer scope decision required ("not applicable").

Contract and boundary impact

  • Semantic owner and earliest changed stage: the target-free availability projection (src/application/CapabilityInventory.ts) plus the shared host gate (src/pcap/PcapNativeBound.ts).
  • CLI and MCP/tool-catalog contract: tool_availability for inspect_pcap_capture changes from available to available: false, reason: "unsupported_host" on hosts outside linux || win32 when no pcap service is injected; the complete tools/list catalog is unchanged; unsupported_host is an existing reason value.
  • Provider, bridge, target-format, or platform compatibility: Linux unchanged (supported); Windows unchanged (supported through the Job Object bound); injected services unchanged.
  • Evidence, artifact, provenance contract: none.
  • Generated metadata: none.

Expected effects:

  • Read existing files or captured data. (the probe reads discovery output and calls the client probe only)
  • 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

  • RED (executed on this machine, current main c106cf20c before the fix): a stdio MCP probe with isolated HOME/XDG state and a stub tshark 4.2.0 on PATH ran target-free binary_session {}; inspect_pcap_capture reported {"available": true, "reason": "available"} — the over-advertisement in #5711. A second probe without any tshark reported the same, so the kind fallback is unconditional.
  • GREEN (executed after the fix): the same probe reports {"available": false, "reason": "unsupported_host", "remediation": "Packet summaries require an enforceable native memory bound: ..."} for inspect_pcap_capture, and inspect_pcap_client stays available with a successful real call returning the stub version banner — the issue's proposed restoration.
  • Tests added: unit coverage in src/application/CapabilityInventory.test.ts (host-unsupported pcap capture vs available client) and MCP boundary coverage in tests/process-global/hostRestrictedAvailabilityMcp.test.ts (inspect_pcap_capture in the host-restricted table with its linux-or-win32 admitted set, plus a win32 x64 emulation row exercising the Job-Object side of the admitted set for every table entry).
  • Base reproduction: the issue's sequence and source analysis were rechecked against current main before fixing; the kind fallback and the gate text are unchanged from the issue's cited revisions.
  • Remaining proof gaps: a real Windows host was not executed here (the boundary test emulates win32 at discovery level only); CI covers Linux. The capture tool's typed execution refusal was documented by the issue and is unchanged by this fix.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable. (executed probes vs source-derived reasoning are labeled in Validation)
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm ci — locked dependencies, Node 24.18.0 (.nvmrc), macOS 14 arm64.
  • npm run test:local -- src/application/CapabilityInventory.test.ts — 39 passed (38 existing + 1 new).
  • npm run test:focused -- tests/process-global/hostRestrictedAvailabilityMcp.test.ts — 7 passed (6 existing scenarios + the win32 row; the table entry is asserted inside each platform scenario).
  • npm run test:focused -- tests/boundary/mcp/pcapMcp.test.ts src/pcap/PcapNativeBound.test.ts src/pcap/PcapConfiguration.test.ts — 40 passed.
  • npm run check:fast — typecheck + lint pass (uncached).
  • Probes (RED/GREEN above): local stdio MCP probe against node scripts/rea.mjs mcp with isolated HOME/XDG_*/TMPDIR, before and after the fix.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. The reason change only fires where available was already wrong; supported hosts and injected services are unchanged.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable — no provider is launched by the change; the probe's stub tshark only answers --version.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @kittimzhe

  • 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: Fixes #5711.
  • Tests cover changed observable behavior and meaningful failure paths. (unit + MCP boundary with platform emulation; win32 side of the admitted set covered)
  • Owning docs, contracts, and generated metadata are updated where needed. (no docs enumerate the pcap tools' discovery reasons; unsupported_host already exists in the output schema and docs)
  • User-visible CLI/MCP changes include representative output. (RED/GREEN probe output quoted in Evidence)
  • 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/6512 **Author:** [@kittimzhe](https://github.com/kittimzhe) **Created:** 10/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/pcap-capture-host-availability` --- ### 📝 Commits (1) - [`652e56f`](https://github.com/morluto/rea/commit/652e56f75dc52b0e13a631bf0c1a75cfc0adde78) fix(pcap): report capture summaries unsupported off their verified hosts ### 📊 Changes **6 files changed** (+64 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `src/application/CapabilityInventory.test.ts` (+18 -0) 📝 `src/application/CapabilityInventory.ts` (+10 -0) 📝 `src/composition/pcap.ts` (+3 -0) 📝 `src/pcap/PcapNativeBound.ts` (+18 -10) 📝 `src/server/createServer.ts` (+9 -1) 📝 `tests/process-global/hostRestrictedAvailabilityMcp.test.ts` (+6 -1) </details> ### 📄 Description Fixes #5711 Related: #6179 proposed the same classification before #5793 introduced the host-restriction mechanism. This PR follows that mechanism on current main and adds MCP-level coverage; happy to defer if the maintainers prefer rebasing #6179 instead. ## Summary Target-free discovery advertises `inspect_pcap_capture` as `available: true` on hosts whose capture execution refuses: the `pcap-provider` kind fallback in the availability projection returns available unconditionally, so on macOS the catalog promises a callable operation while the native bound gate rejects the host at execution with `capability_unavailable`. The host-independent `inspect_pcap_client` version probe keeps its availability either way. ## Problem and expected behavior - Smallest trigger: on a non-Linux, non-Windows host with a tshark on PATH, run a target-free `binary_session {}` and read `tool_availability`; `inspect_pcap_capture` reports `{"available": true, "reason": "available"}` even though calling it returns the typed refusal `Packet summaries require an enforceable native memory bound: Linux with util-linux prlimit, or Windows with owned Job Objects. This host's capture boundary remains unsupported.` The same over-advertisement appears with no tshark configured. - Violated invariant: the same one #5793 established for the other Linux-only integrations — an unavailable tool's machine-readable reason should name the actual blocker, and no configuration can make a host-restricted integration pass its execution host check. The mechanism this adds to is `HOST_RESTRICTED_FEATURES` / `hostUnsupported` / `verifiedHost` from #5793. - Expected: `inspect_pcap_capture` reports `unsupported_host` with the execution gate's remediation on hosts outside its verified set; Linux and Windows (Job Object bound) stay available; the client probe keeps `available` on every host; injected pcap services own their availability on any host. ## Change and scope - `src/pcap/PcapNativeBound.ts` now owns and exports `pcapCaptureHostSupported` (`linux || win32`) and its gate uses it — discovery and execution share the one check, replacing the inline platform pair that previously lived only in the gate. - `src/composition/pcap.ts` re-exports it; `src/server/createServer.ts` records `pcapCapture` in `verifiedHost` and in `hostUnsupported` through the existing `outsideVerifiedHost(options.pcapAnalysis, ...)` injection exemption. - `src/application/CapabilityInventory.ts` adds `"pcapCapture"` to `HOST_RESTRICTED_FEATURES` and classifies `inspect_pcap_capture` through `hostRestrictedAvailability` with the gate's exact remediation text. The `enabled` argument is `true`: the pcap family registers on every host, so the remaining unavailability dimension is configuration at execution, which is out of this issue's scope (noted below). - `inspect_pcap_client` is untouched — it stays on the kind fallback and remains available wherever the provider is constructed. - Intentionally not included: the no-tshark case still reports `available` for the family, exactly as before; #5711 asks for the host limitation split, and a configuration-aware availability for the pcap family can follow the pattern #5793 uses for `packetCaptureEnabled` if the maintainers want it. #6179's approach (a separate `pcapCaptureHostSupported` policy field) achieves the same classification but predates the `hostUnsupported` mechanism and conflicts with current main. - Contribution scope: ordinary fix within existing boundaries — no maintainer scope decision required ("not applicable"). ## Contract and boundary impact - Semantic owner and earliest changed stage: the target-free availability projection (`src/application/CapabilityInventory.ts`) plus the shared host gate (`src/pcap/PcapNativeBound.ts`). - CLI and MCP/tool-catalog contract: `tool_availability` for `inspect_pcap_capture` changes from `available` to `available: false, reason: "unsupported_host"` on hosts outside `linux || win32` when no pcap service is injected; the complete `tools/list` catalog is unchanged; `unsupported_host` is an existing reason value. - Provider, bridge, target-format, or platform compatibility: Linux unchanged (supported); Windows unchanged (supported through the Job Object bound); injected services unchanged. - Evidence, artifact, provenance contract: none. - Generated metadata: none. Expected effects: - [x] Read existing files or captured data. *(the probe reads discovery output and calls the client probe only)* - [ ] 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 - RED (executed on this machine, current main `c106cf20c` before the fix): a stdio MCP probe with isolated `HOME`/XDG state and a stub tshark 4.2.0 on PATH ran target-free `binary_session {}`; `inspect_pcap_capture` reported `{"available": true, "reason": "available"}` — the over-advertisement in #5711. A second probe without any tshark reported the same, so the kind fallback is unconditional. - GREEN (executed after the fix): the same probe reports `{"available": false, "reason": "unsupported_host", "remediation": "Packet summaries require an enforceable native memory bound: ..."}` for `inspect_pcap_capture`, and `inspect_pcap_client` stays `available` with a successful real call returning the stub version banner — the issue's proposed restoration. - Tests added: unit coverage in `src/application/CapabilityInventory.test.ts` (host-unsupported pcap capture vs available client) and MCP boundary coverage in `tests/process-global/hostRestrictedAvailabilityMcp.test.ts` (`inspect_pcap_capture` in the host-restricted table with its `linux-or-win32` admitted set, plus a `win32 x64` emulation row exercising the Job-Object side of the admitted set for every table entry). - Base reproduction: the issue's sequence and source analysis were rechecked against current main before fixing; the kind fallback and the gate text are unchanged from the issue's cited revisions. - Remaining proof gaps: a real Windows host was not executed here (the boundary test emulates `win32` at discovery level only); CI covers Linux. The capture tool's typed execution refusal was documented by the issue and is unchanged by this fix. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. *(executed probes vs source-derived reasoning are labeled in Validation)* - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm ci` — locked dependencies, Node 24.18.0 (`.nvmrc`), macOS 14 arm64. - `npm run test:local -- src/application/CapabilityInventory.test.ts` — 39 passed (38 existing + 1 new). - `npm run test:focused -- tests/process-global/hostRestrictedAvailabilityMcp.test.ts` — 7 passed (6 existing scenarios + the win32 row; the table entry is asserted inside each platform scenario). - `npm run test:focused -- tests/boundary/mcp/pcapMcp.test.ts src/pcap/PcapNativeBound.test.ts src/pcap/PcapConfiguration.test.ts` — 40 passed. - `npm run check:fast` — typecheck + lint pass (uncached). - Probes (RED/GREEN above): local stdio MCP probe against `node scripts/rea.mjs mcp` with isolated `HOME`/`XDG_*`/`TMPDIR`, before and after the fix. ## Compatibility, safety, and release - Breaking changes or migration steps: none. The reason change only fires where `available` was already wrong; supported hosts and injected services are unchanged. - Real Hopper/Ghidra, browser, or OS coverage: not applicable — no provider is launched by the change; the probe's stub tshark only answers `--version`. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @kittimzhe - [ ] 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. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked: Fixes #5711. - [x] Tests cover changed observable behavior and meaningful failure paths. *(unit + MCP boundary with platform emulation; win32 side of the admitted set covered)* - [x] Owning docs, contracts, and generated metadata are updated where needed. *(no docs enumerate the pcap tools' discovery reasons; `unsupported_host` already exists in the output schema and docs)* - [x] User-visible CLI/MCP changes include representative output. *(RED/GREEN probe output quoted in Evidence)* - [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-11-01 21:47:25 +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#7375
No description provided.