morluto/rea

Fork

You've already forked rea

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 #4774] [CLOSED] fix(ghidra): recognize OutOfMemoryError beyond the diagnostic budget #6404

New issue

Closed

opened 2026-10-31 01:14:12 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:14:12 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4774
Author: @sx4im
Created: 10/17/2026
Status: ❌ Closed

Base: main ← Head: fix/4682-ghidra-oom-beyond-diagnostic-budget

📝 Commits (5)

6edf099 fix(ghidra): report unconfirmed memory cause when OOME output is truncated
037900f fix(ghidra): detect OutOfMemoryError beyond the diagnostic budget
7bef62f docs(ghidra): describe OOME observation beyond the retention budget
31935e1 Merge pull request #3 from sx4im/reason/4682-oome-marker-scan
1825647 Merge upstream main into fix/4682-ghidra-oom-beyond-diagnostic-budget

📊 Changes

11 files changed (+658 additions, -17 deletions)

View changed files

📝 docs/binary-diagnostics.md (+6 -1)
📝 src/ghidra/GhidraClient.ts (+6 -10)
📝 src/ghidra/GhidraDiagnostics.ts (+43 -1)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+39 -0)
📝 src/ghidra/GhidraProviderClient.ts (+19 -2)
➕ src/process/ProcessOutputMarkerScanner.test.ts (+158 -0)
➕ src/process/ProcessOutputMarkerScanner.ts (+127 -0)
📝 src/process/ProviderProcess.ts (+60 -2)
📝 tests/boundary/providers/ghidra/ghidraClient.fixture.ts (+5 -0)
➕ tests/boundary/providers/ghidra/ghidraOomRetention.test.ts (+159 -0)
📝 tests/fixtures/fakeGhidra.mjs (+36 -1)

📄 Description

Fixes #4682

Summary

Ghidra output is kept only up to an 8 MiB budget, so an OutOfMemoryError printed after that was lost and reported as execution_failure ("run rea doctor"). It is now reported as resource_constraint (memory) with the Java heap detail and configured_jvm_max_heap, however much output came first.

Problem and expected behavior

Trigger: >8 MiB of earlier output, then a failing operation prints java.lang.OutOfMemoryError: Java heap space. Expected: the same result as without the earlier output.

Change and scope

ProviderProcessSupervisor takes an outputMarker and checks every chunk before the budget applies (new ProcessOutputMarkerScanner). It keeps a small tail per stream so a marker split across chunks is found, and stores only the latest match (offset + line, max 1 KiB each side).
snapshotOutputSince returns a match only if its offset is inside the checkpoint range, so an OOME from an earlier operation or before resetOutput is ignored.
GhidraClient sets the marker to java.lang.OutOfMemoryError and adds matches as failure_output.observed_oome (redacted). projectObservedJvmMemoryFailure reads them through the existing OOME path.
Removes the earlier complete === false guess, which turned cancelled drains, earlier budget use and startup timeouts into memory errors. Incomplete output with no OOME keeps the original code.
Scope: ordinary fix within existing boundaries; no maintainer decision needed.

Contract and boundary impact

Owner: src/process scans output; Ghidra projection reads it.
CLI/MCP: additive failure_output.observed_oome; codes change only when an OOME was actually printed.
Provider/platform: Ghidra only; other providers don't set a marker.
Evidence: line copy is bounded, redacted, keeps its stream and byte offset.
Generated metadata/package: none.

Expected effects:

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: new tests/boundary/providers/ghidra/ghidraOomRetention.test.ts (real provider/client/capture/projection, fake Ghidra modes oom_exit_tools, flood_then_oom_exit_tools, flood_then_exit_tools, flood_then_malformed, flood_silent); src/process/ProcessOutputMarkerScanner.test.ts (after budget, split marker, earlier checkpoint, reset, limits); updated GhidraProvider.behavior.test.ts. The existing cancelled-drain protocol test still passes.
Base: the new test fails on e5ee3ac and upstream main 5d6029e (only the >8 MiB case: execution_failure), and passes here. Thanks to @RishTheFish21, who offered this regression in #4682; the fake-Ghidra modes follow it.
Output (>8 MiB case): resource_constraint, resource: memory, reported_limits.configured_jvm_max_heap: "4G", message "...reports java.lang.OutOfMemoryError: Java heap space...", failure_output.complete: false, stdout 11014752 bytes / 8388608 retained, one observed_oome entry from stderr.
Gaps: real Ghidra not run (the JVM is simulated); Windows not run.
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 src/ghidra src/process tests/boundary/providers/ghidra (NODE_OPTIONS=--no-warnings) — 67 files, 1134 tests pass (7 skipped). Without the flag, 7 tests fail only because the sandbox proxy makes Node print a warning into captured child output; the same 7 fail on unchanged e5ee3ac
New regression ghidraOomRetention.test.ts — fails on e5ee3ac and upstream main 5d6029e (>8 MiB case reports execution_failure), passes here
npm run lint — exit 0; npm run format:check — clean on the branch; npm run docs:check — pass
npx tsc --noEmit — pass
Scanner: 512 MiB in 64 KiB chunks in 115 ms, constant memory
CI on 31935e1: test shards 1–5, Portable tests, Source tests, Build package, Docs Generation pass. Static checks fail on tests/boundary/cli/keyedArchivePrototypeKeyCli.test.ts (from main; upstream main 7aa4b98 fails the same check), not on files in this PR

Compatibility, safety, and release

Breaking changes: none (additive field).
Real Ghidra/OS coverage: Linux, simulated Ghidra only.
Package metadata: none.
Security: OOME lines are redacted like other output.

Author readiness

Human owner: @sx4im

I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
I declare this PR ready for initial maintainer review.

Before merge

This PR addresses a concrete problem or an agreed enhancement.
Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
The PR has one focused outcome and the title follows type(scope): outcome.
Related issue is linked, or the reason for not linking one is stated above.
Tests cover changed observable behavior and meaningful failure paths.
Owning docs, contracts, and generated metadata are updated where needed.
User-visible CLI/MCP changes include representative output.
I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/4774 **Author:** [@sx4im](https://github.com/sx4im) **Created:** 10/17/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/4682-ghidra-oom-beyond-diagnostic-budget` --- ### 📝 Commits (5) - [`6edf099`](https://github.com/morluto/rea/commit/6edf0996ba92ec4f31201aecd633bf7123e916fa) fix(ghidra): report unconfirmed memory cause when OOME output is truncated - [`037900f`](https://github.com/morluto/rea/commit/037900fbba8a541484c5a7f63cc26dc4e86c23a7) fix(ghidra): detect OutOfMemoryError beyond the diagnostic budget - [`7bef62f`](https://github.com/morluto/rea/commit/7bef62f2b70eac5e46e2178cdada9b1ea716c0be) docs(ghidra): describe OOME observation beyond the retention budget - [`31935e1`](https://github.com/morluto/rea/commit/31935e13007ff8f6cedda814111a4084a1e6fec9) Merge pull request #3 from sx4im/reason/4682-oome-marker-scan - [`1825647`](https://github.com/morluto/rea/commit/18256474e149093085b3dc25719770da844605f9) Merge upstream main into fix/4682-ghidra-oom-beyond-diagnostic-budget ### 📊 Changes **11 files changed** (+658 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `docs/binary-diagnostics.md` (+6 -1) 📝 `src/ghidra/GhidraClient.ts` (+6 -10) 📝 `src/ghidra/GhidraDiagnostics.ts` (+43 -1) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+39 -0) 📝 `src/ghidra/GhidraProviderClient.ts` (+19 -2) ➕ `src/process/ProcessOutputMarkerScanner.test.ts` (+158 -0) ➕ `src/process/ProcessOutputMarkerScanner.ts` (+127 -0) 📝 `src/process/ProviderProcess.ts` (+60 -2) 📝 `tests/boundary/providers/ghidra/ghidraClient.fixture.ts` (+5 -0) ➕ `tests/boundary/providers/ghidra/ghidraOomRetention.test.ts` (+159 -0) 📝 `tests/fixtures/fakeGhidra.mjs` (+36 -1) </details> ### 📄 Description Fixes #4682 ## Summary Ghidra output is kept only up to an 8 MiB budget, so an OutOfMemoryError printed after that was lost and reported as `execution_failure` ("run `rea doctor`"). It is now reported as `resource_constraint` (memory) with the Java heap detail and `configured_jvm_max_heap`, however much output came first. ## Problem and expected behavior Trigger: >8 MiB of earlier output, then a failing operation prints `java.lang.OutOfMemoryError: Java heap space`. Expected: the same result as without the earlier output. ## Change and scope - `ProviderProcessSupervisor` takes an `outputMarker` and checks every chunk before the budget applies (new `ProcessOutputMarkerScanner`). It keeps a small tail per stream so a marker split across chunks is found, and stores only the latest match (offset + line, max 1 KiB each side). - `snapshotOutputSince` returns a match only if its offset is inside the checkpoint range, so an OOME from an earlier operation or before `resetOutput` is ignored. - `GhidraClient` sets the marker to `java.lang.OutOfMemoryError` and adds matches as `failure_output.observed_oome` (redacted). `projectObservedJvmMemoryFailure` reads them through the existing OOME path. - Removes the earlier `complete === false` guess, which turned cancelled drains, earlier budget use and startup timeouts into memory errors. Incomplete output with no OOME keeps the original code. Scope: ordinary fix within existing boundaries; no maintainer decision needed. ## Contract and boundary impact - Owner: `src/process` scans output; Ghidra projection reads it. - CLI/MCP: additive `failure_output.observed_oome`; codes change only when an OOME was actually printed. - Provider/platform: Ghidra only; other providers don't set a marker. - Evidence: line copy is bounded, redacted, keeps its stream and byte offset. - Generated metadata/package: none. Expected effects: - [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 - Tests: new `tests/boundary/providers/ghidra/ghidraOomRetention.test.ts` (real provider/client/capture/projection, fake Ghidra modes `oom_exit_tools`, `flood_then_oom_exit_tools`, `flood_then_exit_tools`, `flood_then_malformed`, `flood_silent`); `src/process/ProcessOutputMarkerScanner.test.ts` (after budget, split marker, earlier checkpoint, reset, limits); updated `GhidraProvider.behavior.test.ts`. The existing cancelled-drain protocol test still passes. - Base: the new test fails on e5ee3ac and upstream main 5d6029e (only the >8 MiB case: `execution_failure`), and passes here. Thanks to @RishTheFish21, who offered this regression in #4682; the fake-Ghidra modes follow it. - Output (>8 MiB case): `resource_constraint`, `resource: memory`, `reported_limits.configured_jvm_max_heap: "4G"`, message "...reports java.lang.OutOfMemoryError: Java heap space...", `failure_output.complete: false`, stdout 11014752 bytes / 8388608 retained, one `observed_oome` entry from stderr. - Gaps: real Ghidra not run (the JVM is simulated); Windows not run. - [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 src/ghidra src/process tests/boundary/providers/ghidra` (NODE_OPTIONS=--no-warnings) — 67 files, 1134 tests pass (7 skipped). Without the flag, 7 tests fail only because the sandbox proxy makes Node print a warning into captured child output; the same 7 fail on unchanged e5ee3ac - New regression `ghidraOomRetention.test.ts` — fails on e5ee3ac and upstream main 5d6029e (>8 MiB case reports `execution_failure`), passes here - `npm run lint` — exit 0; `npm run format:check` — clean on the branch; `npm run docs:check` — pass - `npx tsc --noEmit` — pass - Scanner: 512 MiB in 64 KiB chunks in 115 ms, constant memory - CI on 31935e1: test shards 1–5, Portable tests, Source tests, Build package, Docs Generation pass. Static checks fail on `tests/boundary/cli/keyedArchivePrototypeKeyCli.test.ts` (from main; upstream main 7aa4b98 fails the same check), not on files in this PR ## Compatibility, safety, and release - Breaking changes: none (additive field). - Real Ghidra/OS coverage: Linux, simulated Ghidra only. - Package metadata: none. - Security: OOME lines are redacted like other output. ## Author readiness Human owner: @sx4im - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 01:14:12 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-11-01 21:10:57 +00:00

[GH-ISSUE #3796] [Tracker] Open feature requests by area (October 2026) #1471

bsakaguchi referenced this issue

2026-11-01 21:11:00 +00:00

[GH-ISSUE #5653] [Tracker] New issue intake by area (October 2026) #3423

bsakaguchi referenced this issue

2026-11-01 21:11:08 +00:00

[GH-ISSUE #6405] [Feature] Ghidra: export analyst names and comments from a session and re-apply them when the target is reopened #3835

bsakaguchi referenced this issue

2026-11-01 21:11:08 +00:00

[GH-ISSUE #6404] [Feature] Ghidra: admit comment / inline_comment / set_comment / set_inline_comment at any mapped address #3837

bsakaguchi referenced this issue

2026-11-01 21:12:16 +00:00

[GH-ISSUE #8363] [Bug] Ghidra address context hides available function comments and suggests unsupported calls #6562

bsakaguchi referenced this issue

2026-11-01 21:12:17 +00:00

[GH-ISSUE #8364] [Design] Preserve contributing evidence for address-context handoffs #6566

bsakaguchi referenced this issue

2026-11-01 21:13:00 +00:00

[GH-ISSUE #8583] fix(ghidra): clarify interior selectors before function annotation #6658

No Branch/Tag specified

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

Mirrored from GitHub Pull Request

No labels

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

Reference in a new issue

Repository

morluto/rea

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns