[PR #2361] [MERGED] fix(ghidra): bound the Java version probe output #5187

New issue

Closed

opened 2026-10-31 01:04:39 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:04:39 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2361
Author: @DeryFerd
Created: 10/12/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @morluto

Base: main ← Head: fix/ghidra-probe-output-budget

---

📝 Commits (1)

• 4a46eed fix(ghidra): bound the Java version probe output

📊 Changes

2 files changed (+50 additions, -1 deletions)

View changed files

📝 src/ghidra/GhidraInstallation.ts (+10 -1)
📝 tests/boundary/filesystem/ghidraJavaProbe.test.ts (+40 -0)

📄 Description

Summary

The Ghidra installation check runs the caller-selected Java launcher with -XshowSettings:properties -version to read java.version, java.home, and the VM name. That probe captured stdout and stderr with maxBuffer set to Number.POSITIVE_INFINITY, so a launcher that prints without limit could grow the capture until REA ran out of memory. This change gives the probe a 1 MiB capture budget, the same budget REA already uses for other Java listings. There is no linked issue.

Problem and expected behavior

inspectGhidraInstallation resolves the Java command from JAVA_HOME or PATH and calls probeJava on the installation host. In the production host, probeJava is a synchronous spawnSync whose options set maxBuffer: Number.POSITIVE_INFINITY. Node buffers every byte the child writes to stdout and stderr, and with no cap those buffers can reach whatever the child produces. A JVM that is misconfigured, wrapped by a script that echoes a large banner, or simply hostile can therefore make a read-only installation check consume unbounded memory.

The smallest trigger is a Java launcher that writes more than the capture budget while the probe is running. The violated invariant is that a bounded, read-only installation check should never allocate memory in proportion to a child's unbounded output. The expected behavior is that a probe which produces more text than a sane JVM ever would is treated as a probe that could not be read, not as a reason to keep allocating.

Change and scope

Add a module constant JAVA_PROBE_MAX_OUTPUT_BYTES = 1024 * 1024 next to the existing EXECUTABLE_HEADER_PROBE_BYTES, and pass it as maxBuffer in probeJava. One mebibyte is far more than a well-behaved JVM needs, since -XshowSettings:properties prints a few kilobytes. It is also the budget REA already chose for the analogous Java module listing in src/android/JadxConfiguration.ts, so the two Java probes now agree on what "too much output" means.

When the child exceeds maxBuffer, spawnSync returns an ENOBUFS error and a null status. The probe already bails on any error or non-zero status and returns no observation, so the overflow path needs no new branch. javaCheck then reports the Java check as failed with runtime_missing, which is the same outcome the check already produces whenever the probe yields nothing.

I did not change the timeout, the argv, the encoding flags, or the parsing. I also did not add a distinct rejection code for an over-budget probe. The installation check has no "unknown" status to carry, and runtime_missing is the existing code for "the probe produced no observation", so a separate code would be a larger contract change than this fix needs.

Contract and boundary impact

• Semantic owner and earliest changed stage: src/ghidra/GhidraInstallation.ts, in the production GhidraInstallationHost.probeJava implementation. The observation type and the javaCheck mapping are unchanged.
• Contribution scope fit and linked maintainer decision: routine fix inside existing boundaries. The probe reads Ghidra's application.properties and runs the caller-selected Java launcher, both of which the installation check already did. Not applicable for a maintainer scope decision.
• CLI and MCP/tool-catalog contract: no change. No tool schema, catalog entry, or handler changes.
• Provider, bridge, target-format, or platform compatibility: no change. The bounded probe behaves the same on every platform.
• Evidence, artifact, provenance, or reconstruction contract: the Java check still reports its detail and remediation. An over-budget probe loses the truncated text, which the probe already discards on any failure.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): none new. The probe does not touch the analysis target.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none. No generated catalog, skill, or package file changes.

Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible.

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

Evidence and regression coverage

• Tests added or updated: tests/boundary/filesystem/ghidraJavaProbe.test.ts gains one case, "bounds the Java version probe and reports an over-budget probe as a failed Java check". It mocks spawnSync to return status: null with an ENOBUFS error, the shape Node produces when the capture overflows, and asserts that the probe passed maxBuffer: 1024 * 1024, that no Java version is reported, that the configured JAVA_HOME is preserved, and that the Java check is { status: "failed", code: "runtime_missing" }.
• Base reproduction or other evidence: the new case fails on the unmodified source. With maxBuffer: Number.POSITIVE_INFINITY, the assertion expect(options.maxBuffer).toBe(1024 * 1024) reports - Infinity + 1048576. That is the red state this change fixes.
• User-visible CLI/MCP output (if applicable): the Java installation check is what surfaces in rea doctor and provider diagnostics. An over-budget launcher now produces the same check shape a launcher that cannot be read produces, { name: "java", status: "failed", code: "runtime_missing" }, and the detail line falls back to the launcher command while the remediation still tells the caller how to point JAVA_HOME at a supported JDK.
• Remaining proof gaps: the case is a boundary test with a mocked spawnSync. I did not reproduce the memory growth with a real unbounded JVM, because that would mean deliberately exhausting the machine. The Node maxBuffer and ENOBUFS behavior the test relies on is stable across the supported Node versions, and CI runs the real suite.

For evidence-bearing changes:

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

Validation performed

• npx vitest run tests/boundary/filesystem/ghidraJavaProbe.test.ts — 4 passed, including the new bounded-probe case.
• npm run check:fast — typecheck and lint passed, run as the pre-push hook on the rebased commit.
• npx vitest run src/ghidra/GhidraInstallation.test.ts src/ghidra/GhidraDoctor.test.ts — GhidraInstallation.test.ts passed fully. GhidraDoctor.test.ts reported 2 failures in its Windows native-authority group. I reproduced those same 2 failures on an unmodified checkout of main, so they are pre-existing and unrelated to this change.

Compatibility, safety, and release

• Breaking changes or migration steps: none. A launcher that stays under 1 MiB behaves exactly as before.
• Real Hopper/Ghidra, browser, or OS coverage: no real-provider run. This is a synchronous spawn change covered by a boundary test; the probe already ran the same argv on every platform.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: this closes a memory-exhaustion path where a caller-selected launcher could grow the installation probe without bound. The fix uses the existing failure path and adds no new authority.

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/2361 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/12/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/ghidra-probe-output-budget` --- ### 📝 Commits (1) - [`4a46eed`](https://github.com/morluto/rea/commit/4a46eed2def2ab4cac68ac814a9fd8c3987adf62) fix(ghidra): bound the Java version probe output ### 📊 Changes **2 files changed** (+50 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/ghidra/GhidraInstallation.ts` (+10 -1) 📝 `tests/boundary/filesystem/ghidraJavaProbe.test.ts` (+40 -0) </details> ### 📄 Description ## Summary The Ghidra installation check runs the caller-selected Java launcher with `-XshowSettings:properties -version` to read `java.version`, `java.home`, and the VM name. That probe captured stdout and stderr with `maxBuffer` set to `Number.POSITIVE_INFINITY`, so a launcher that prints without limit could grow the capture until REA ran out of memory. This change gives the probe a 1 MiB capture budget, the same budget REA already uses for other Java listings. There is no linked issue. ## Problem and expected behavior `inspectGhidraInstallation` resolves the Java command from `JAVA_HOME` or `PATH` and calls `probeJava` on the installation host. In the production host, `probeJava` is a synchronous `spawnSync` whose options set `maxBuffer: Number.POSITIVE_INFINITY`. Node buffers every byte the child writes to stdout and stderr, and with no cap those buffers can reach whatever the child produces. A JVM that is misconfigured, wrapped by a script that echoes a large banner, or simply hostile can therefore make a read-only installation check consume unbounded memory. The smallest trigger is a Java launcher that writes more than the capture budget while the probe is running. The violated invariant is that a bounded, read-only installation check should never allocate memory in proportion to a child's unbounded output. The expected behavior is that a probe which produces more text than a sane JVM ever would is treated as a probe that could not be read, not as a reason to keep allocating. ## Change and scope Add a module constant `JAVA_PROBE_MAX_OUTPUT_BYTES = 1024 * 1024` next to the existing `EXECUTABLE_HEADER_PROBE_BYTES`, and pass it as `maxBuffer` in `probeJava`. One mebibyte is far more than a well-behaved JVM needs, since `-XshowSettings:properties` prints a few kilobytes. It is also the budget REA already chose for the analogous Java module listing in `src/android/JadxConfiguration.ts`, so the two Java probes now agree on what "too much output" means. When the child exceeds `maxBuffer`, `spawnSync` returns an `ENOBUFS` error and a null status. The probe already bails on any error or non-zero status and returns no observation, so the overflow path needs no new branch. `javaCheck` then reports the Java check as failed with `runtime_missing`, which is the same outcome the check already produces whenever the probe yields nothing. I did not change the timeout, the argv, the encoding flags, or the parsing. I also did not add a distinct rejection code for an over-budget probe. The installation check has no "unknown" status to carry, and `runtime_missing` is the existing code for "the probe produced no observation", so a separate code would be a larger contract change than this fix needs. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/ghidra/GhidraInstallation.ts`, in the production `GhidraInstallationHost.probeJava` implementation. The observation type and the `javaCheck` mapping are unchanged. - Contribution scope fit and linked maintainer decision: routine fix inside existing boundaries. The probe reads Ghidra's `application.properties` and runs the caller-selected Java launcher, both of which the installation check already did. Not applicable for a maintainer scope decision. - CLI and MCP/tool-catalog contract: no change. No tool schema, catalog entry, or handler changes. - Provider, bridge, target-format, or platform compatibility: no change. The bounded probe behaves the same on every platform. - Evidence, artifact, provenance, or reconstruction contract: the Java check still reports its detail and remediation. An over-budget probe loses the truncated text, which the probe already discards on any failure. - Target selection, authority, upstream behavior, and cleanup details (if applicable): none new. The probe does not touch the analysis target. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. No generated catalog, skill, or package file changes. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/filesystem/ghidraJavaProbe.test.ts` gains one case, "bounds the Java version probe and reports an over-budget probe as a failed Java check". It mocks `spawnSync` to return `status: null` with an `ENOBUFS` error, the shape Node produces when the capture overflows, and asserts that the probe passed `maxBuffer: 1024 * 1024`, that no Java version is reported, that the configured `JAVA_HOME` is preserved, and that the Java check is `{ status: "failed", code: "runtime_missing" }`. - Base reproduction or other evidence: the new case fails on the unmodified source. With `maxBuffer: Number.POSITIVE_INFINITY`, the assertion `expect(options.maxBuffer).toBe(1024 * 1024)` reports `- Infinity + 1048576`. That is the red state this change fixes. - User-visible CLI/MCP output (if applicable): the Java installation check is what surfaces in `rea doctor` and provider diagnostics. An over-budget launcher now produces the same check shape a launcher that cannot be read produces, `{ name: "java", status: "failed", code: "runtime_missing" }`, and the detail line falls back to the launcher command while the remediation still tells the caller how to point `JAVA_HOME` at a supported JDK. - Remaining proof gaps: the case is a boundary test with a mocked `spawnSync`. I did not reproduce the memory growth with a real unbounded JVM, because that would mean deliberately exhausting the machine. The Node `maxBuffer` and `ENOBUFS` behavior the test relies on is stable across the supported Node versions, and CI runs the real suite. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npx vitest run tests/boundary/filesystem/ghidraJavaProbe.test.ts` — 4 passed, including the new bounded-probe case. - `npm run check:fast` — typecheck and lint passed, run as the pre-push hook on the rebased commit. - `npx vitest run src/ghidra/GhidraInstallation.test.ts src/ghidra/GhidraDoctor.test.ts` — `GhidraInstallation.test.ts` passed fully. `GhidraDoctor.test.ts` reported 2 failures in its Windows native-authority group. I reproduced those same 2 failures on an unmodified checkout of `main`, so they are pre-existing and unrelated to this change. ## Compatibility, safety, and release - Breaking changes or migration steps: none. A launcher that stays under 1 MiB behaves exactly as before. - Real Hopper/Ghidra, browser, or OS coverage: no real-provider run. This is a synchronous spawn change covered by a boundary test; the probe already ran the same argv on every platform. - Package or release metadata impact: none. - Security, privacy, process, or containment review: this closes a memory-exhaustion path where a caller-selected launcher could grow the installation probe without bound. The fix uses the existing failure path and adds no new authority. ## 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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:04:39 +00:00

• closed this issue
• added the
  pull-request
  label

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

Subscribe

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#5187

No description provided.