[PR #5324] fix(javascript-recovery): run Wakaru on macOS arm64 with shell resource limits #6880

New issue

Open

opened 2026-11-01 21:43:47 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:43:47 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5324
Author: @IOkal
Created: 10/20/2026
Status: 🔄 Open

Base: main ← Head: fix/wakaru-macos-arm64-limiter

---

📝 Commits (1)

• ea9286d fix(javascript-recovery): run Wakaru on macOS arm64 with shell resource limits

📊 Changes

6 files changed (+257 additions, -27 deletions)

View changed files

📝 docs/javascript-recovery.md (+17 -4)
📝 src/application/CapabilityInventory.ts (+1 -1)
📝 src/javascript/recovery/WakaruCommand.test.ts (+161 -1)
📝 src/javascript/recovery/WakaruCommand.ts (+59 -15)
📝 src/javascript/recovery/WakaruPublication.ts (+2 -2)
📝 src/javascript/recovery/WakaruRelease.ts (+17 -4)

📄 Description

Summary

recover_javascript_sources / rea recover-javascript-sources refuses to run on any host except Linux x64, even when the caller supplies a working Wakaru binary. Wakaru publishes a native darwin-arm64 build (@wakaru/cli-darwin-arm64, pulled in by npm install wakaru@1.14.0), but REA rejects it before launch.

This lets macOS arm64 hosts use caller-supplied Wakaru, and makes the weaker resource containment on that host explicit in the result instead of reusing Linux wording.

Problem and expected behavior

Smallest trigger (macOS arm64, Wakaru 1.14.0 installed from npm):

REA_WAKARU_COMMAND="$(realpath node_modules/@wakaru/cli-darwin-arm64/wakaru)" \
  rea recover-javascript-sources app.js out --extraction-mode structural --format json

Observed on rea-agents 6.7.0:

{"code":"capability_unavailable","category":"unsupported_provider","message":"Provide an absolute REA_WAKARU_COMMAND pointing to a Wakaru ^1.13.0 Linux x64 binary (verified with 1.14.0); ..."}

Two checks cause it: resolveWakaruCommand requires process.platform === "linux" && process.arch === "x64", and every run is launched through util-linux prlimit, which does not exist on macOS.

Expected: a configured, working Wakaru runs on macOS arm64, bounded as far as the host allows, and the result says which bounds apply.

Change and scope

The resource limiter is now chosen from the host (WakaruCommand.ts):

• Linux x64: unchanged. Same prlimit binary, same argument list, same REA_JAVASCRIPT_PRLIMIT_COMMAND override.
• macOS arm64: the engine is started through /bin/sh -c 'ulimit -f N && ulimit -c 0 && ulimit -t 120 && exec "$0" "$@"' <engine> <args...>.
  • -f is RECOVERY_LIMITS.outputBytes / 512 blocks, -c 0 disables core dumps, -t is the 120 s CPU limit.
  • The limits are chained with &&, so a limit that cannot be set stops the run instead of starting the engine unbounded.
  • The engine path and arguments are positional parameters ($0, "$@"), never interpolated into the script.
  • REA_JAVASCRIPT_PRLIMIT_COMMAND is not used on this host.
• Other hosts: still refused. The refusal text now names the supported hosts.

macOS does not allow an address-space ceiling: ulimit -v and ulimit -d fail with Invalid argument, and a 200 MB allocation succeeds under ulimit -v 65536. So the 1 GiB memory cap that Linux applies is not enforced on macOS. The result's limitations now come from recoveryLimitations(limiterKind): the Linux string is unchanged, and the macOS string states that memory use is not capped. RECOVERY_LIMITATIONS keeps its existing value.

Not included: Intel macOS, Windows, and Linux arm64 (not verified). A memory ceiling for macOS.

Contract and boundary impact

• Semantic owner and earliest changed stage: javascript-recovery engine resolution (resolveWakaruCommand) and command construction (runWakaruCommand).
• Contribution scope fit and linked maintainer decision: not applicable (ordinary fix within the existing Wakaru provider; no new capability or target interaction).
• CLI and MCP/tool-catalog contract: no schema change. limitations strings differ on macOS. The capability-inventory remediation text and the refusal message now mention macOS arm64.
• Provider, bridge, target-format, or platform compatibility: adds macOS arm64 for Wakaru ^1.13.0 (verified with 1.14.0). Linux x64 behavior unchanged.
• Evidence, artifact, provenance, or reconstruction contract: unchanged. resource_limiter reports /bin/sh on macOS.
• Target selection, authority, upstream behavior, and cleanup details: process ownership and cleanup paths are unchanged; the shell execs the engine, so the supervised process is the engine.
• Generated metadata, package, or installation impact: none committed. Docs updated (docs/javascript-recovery.md).

Expected effects:

• Read existing files or captured data.
• Launch or attach to a process. (Launches the caller-supplied Wakaru, as before.)
• 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

Executed on Darwin 25.6.0 arm64 (macOS), unless noted.

• Tests added or updated (src/javascript/recovery/WakaruCommand.test.ts, 7 new):

  • unsupported host (win32) is refused and the message names Linux x64 / macOS arm64;
  • macOS host selects /bin/sh / shell-ulimit without requiring prlimit;
  • the prlimit override is ignored on macOS;
  • the Linux invocation (prlimit + args) is asserted byte-for-byte unchanged;
  • the macOS invocation passes the engine and arguments as positional parameters (a path containing $(...) and spaces does not reach the script);
  • the macOS limitation says memory is not capped and does not claim the 1 GiB ceiling; the Linux wording is unchanged;
  • darwin-arm64 only: a real run of an engine script that prints ulimit -f, -c, -t shows 262144, 0, 120 were applied before it started.

• Base reproduction: installed rea-agents 6.7.0 with REA_WAKARU_COMMAND set to the darwin binary returns the capability_unavailable refusal above.

• User-visible output with this branch (compiled with tsc + scripts/bundle-runtime.mjs), recovering a real 73 KB webpack bundle with Wakaru 1.14.0 darwin-arm64:

  • exit 0, 15 modules recovered, 0 failed, runtime_equivalence: "unknown";
  • last limitation: macOS adapter: one worker, 120-second CPU and wall-clock deadline, ... macOS cannot enforce an address-space ceiling, so memory use is not capped. ...

• Remaining proof gaps: the Linux real-provider workflow (verify:javascript:recovery, real-javascript-recovery.yml) was not run here; Linux behavior is covered only by the unchanged-invocation unit test. Intel macOS is untested.

• 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/javascript/recovery/WakaruCommand.test.ts — 14 passed (includes the darwin-arm64 real-host test).
• npx vitest run wakaru recovery Recovery CapabilityInventory capabilit — 153 passed, 7 failed, 44 skipped. The same 7 fail on the base commit without this change (hopperStartupRecovery, sessionEvidenceRecovery, processCleanupRecoveryCli: they need a built dist/ or Hopper). Base run: 146 passed, 7 failed.
• npx tsc --noEmit — exit 0.
• npx oxfmt --check on the changed paths — all files correctly formatted.
• npx oxlint src/javascript/recovery src/application/CapabilityInventory.ts — 8 warnings before and after (none new).
• npm run verify:module-boundaries — passed (2231 source files).
• Not run: npm run check, verify:javascript:recovery, Linux CI.

Compatibility, safety, and release

• Breaking changes or migration steps: none. Linux x64 configuration and output are unchanged. macOS arm64 hosts that were refused are now accepted.
• Real Hopper/Ghidra, browser, or OS coverage: macOS arm64 real-host unit test and one end-to-end recovery run (above). No Linux run here.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: on macOS the memory ceiling is not enforced (OS limitation). CPU time, output size, core dumps, REA's 120 s deadline, input/output/entry caps and process-group cleanup still apply. A limit that cannot be applied prevents the engine from starting. Resource limits remain per operation, not aggregate host containment, as already documented.

Author readiness

Human owner:

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

🤖 Generated with Claude Code

---

_{🔄 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/5324 **Author:** [@IOkal](https://github.com/IOkal) **Created:** 10/20/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/wakaru-macos-arm64-limiter` --- ### 📝 Commits (1) - [`ea9286d`](https://github.com/morluto/rea/commit/ea9286ddb275d92428471b6a599de7edd4d2a829) fix(javascript-recovery): run Wakaru on macOS arm64 with shell resource limits ### 📊 Changes **6 files changed** (+257 additions, -27 deletions) <details> <summary>View changed files</summary> 📝 `docs/javascript-recovery.md` (+17 -4) 📝 `src/application/CapabilityInventory.ts` (+1 -1) 📝 `src/javascript/recovery/WakaruCommand.test.ts` (+161 -1) 📝 `src/javascript/recovery/WakaruCommand.ts` (+59 -15) 📝 `src/javascript/recovery/WakaruPublication.ts` (+2 -2) 📝 `src/javascript/recovery/WakaruRelease.ts` (+17 -4) </details> ### 📄 Description ## Summary `recover_javascript_sources` / `rea recover-javascript-sources` refuses to run on any host except Linux x64, even when the caller supplies a working Wakaru binary. Wakaru publishes a native `darwin-arm64` build (`@wakaru/cli-darwin-arm64`, pulled in by `npm install wakaru@1.14.0`), but REA rejects it before launch. This lets macOS arm64 hosts use caller-supplied Wakaru, and makes the weaker resource containment on that host explicit in the result instead of reusing Linux wording. ## Problem and expected behavior Smallest trigger (macOS arm64, Wakaru 1.14.0 installed from npm): ```sh REA_WAKARU_COMMAND="$(realpath node_modules/@wakaru/cli-darwin-arm64/wakaru)" \ rea recover-javascript-sources app.js out --extraction-mode structural --format json ``` Observed on `rea-agents` 6.7.0: ```json {"code":"capability_unavailable","category":"unsupported_provider","message":"Provide an absolute REA_WAKARU_COMMAND pointing to a Wakaru ^1.13.0 Linux x64 binary (verified with 1.14.0); ..."} ``` Two checks cause it: `resolveWakaruCommand` requires `process.platform === "linux" && process.arch === "x64"`, and every run is launched through util-linux `prlimit`, which does not exist on macOS. Expected: a configured, working Wakaru runs on macOS arm64, bounded as far as the host allows, and the result says which bounds apply. ## Change and scope The resource limiter is now chosen from the host (`WakaruCommand.ts`): - **Linux x64**: unchanged. Same `prlimit` binary, same argument list, same `REA_JAVASCRIPT_PRLIMIT_COMMAND` override. - **macOS arm64**: the engine is started through `/bin/sh -c 'ulimit -f N && ulimit -c 0 && ulimit -t 120 && exec "$0" "$@"' <engine> <args...>`. - `-f` is `RECOVERY_LIMITS.outputBytes / 512` blocks, `-c 0` disables core dumps, `-t` is the 120 s CPU limit. - The limits are chained with `&&`, so a limit that cannot be set stops the run instead of starting the engine unbounded. - The engine path and arguments are positional parameters (`$0`, `"$@"`), never interpolated into the script. - `REA_JAVASCRIPT_PRLIMIT_COMMAND` is not used on this host. - **Other hosts**: still refused. The refusal text now names the supported hosts. macOS does not allow an address-space ceiling: `ulimit -v` and `ulimit -d` fail with `Invalid argument`, and a 200 MB allocation succeeds under `ulimit -v 65536`. So the 1 GiB memory cap that Linux applies is not enforced on macOS. The result's limitations now come from `recoveryLimitations(limiterKind)`: the Linux string is unchanged, and the macOS string states that memory use is not capped. `RECOVERY_LIMITATIONS` keeps its existing value. Not included: Intel macOS, Windows, and Linux arm64 (not verified). A memory ceiling for macOS. ## Contract and boundary impact - Semantic owner and earliest changed stage: javascript-recovery engine resolution (`resolveWakaruCommand`) and command construction (`runWakaruCommand`). - Contribution scope fit and linked maintainer decision: not applicable (ordinary fix within the existing Wakaru provider; no new capability or target interaction). - CLI and MCP/tool-catalog contract: no schema change. `limitations` strings differ on macOS. The capability-inventory remediation text and the refusal message now mention macOS arm64. - Provider, bridge, target-format, or platform compatibility: adds macOS arm64 for Wakaru ^1.13.0 (verified with 1.14.0). Linux x64 behavior unchanged. - Evidence, artifact, provenance, or reconstruction contract: unchanged. `resource_limiter` reports `/bin/sh` on macOS. - Target selection, authority, upstream behavior, and cleanup details: process ownership and cleanup paths are unchanged; the shell `exec`s the engine, so the supervised process is the engine. - Generated metadata, package, or installation impact: none committed. Docs updated (`docs/javascript-recovery.md`). Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. (Launches the caller-supplied Wakaru, as before.) - [ ] 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 Executed on Darwin 25.6.0 arm64 (macOS), unless noted. - Tests added or updated (`src/javascript/recovery/WakaruCommand.test.ts`, 7 new): - unsupported host (win32) is refused and the message names Linux x64 / macOS arm64; - macOS host selects `/bin/sh` / `shell-ulimit` without requiring prlimit; - the prlimit override is ignored on macOS; - the Linux invocation (`prlimit` + args) is asserted byte-for-byte unchanged; - the macOS invocation passes the engine and arguments as positional parameters (a path containing `$(...)` and spaces does not reach the script); - the macOS limitation says memory is not capped and does not claim the 1 GiB ceiling; the Linux wording is unchanged; - darwin-arm64 only: a real run of an engine script that prints `ulimit -f`, `-c`, `-t` shows `262144`, `0`, `120` were applied before it started. - Base reproduction: installed `rea-agents` 6.7.0 with `REA_WAKARU_COMMAND` set to the darwin binary returns the `capability_unavailable` refusal above. - User-visible output with this branch (compiled with `tsc` + `scripts/bundle-runtime.mjs`), recovering a real 73 KB webpack bundle with Wakaru 1.14.0 darwin-arm64: - exit 0, 15 modules recovered, 0 failed, `runtime_equivalence: "unknown"`; - last limitation: `macOS adapter: one worker, 120-second CPU and wall-clock deadline, ... macOS cannot enforce an address-space ceiling, so memory use is not capped. ...` - Remaining proof gaps: the Linux real-provider workflow (`verify:javascript:recovery`, `real-javascript-recovery.yml`) was not run here; Linux behavior is covered only by the unchanged-invocation unit test. Intel macOS is untested. - [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/javascript/recovery/WakaruCommand.test.ts` — 14 passed (includes the darwin-arm64 real-host test). - `npx vitest run wakaru recovery Recovery CapabilityInventory capabilit` — 153 passed, 7 failed, 44 skipped. The same 7 fail on the base commit without this change (`hopperStartupRecovery`, `sessionEvidenceRecovery`, `processCleanupRecoveryCli`: they need a built `dist/` or Hopper). Base run: 146 passed, 7 failed. - `npx tsc --noEmit` — exit 0. - `npx oxfmt --check` on the changed paths — all files correctly formatted. - `npx oxlint src/javascript/recovery src/application/CapabilityInventory.ts` — 8 warnings before and after (none new). - `npm run verify:module-boundaries` — passed (2231 source files). - Not run: `npm run check`, `verify:javascript:recovery`, Linux CI. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Linux x64 configuration and output are unchanged. macOS arm64 hosts that were refused are now accepted. - Real Hopper/Ghidra, browser, or OS coverage: macOS arm64 real-host unit test and one end-to-end recovery run (above). No Linux run here. - Package or release metadata impact: none. - Security, privacy, process, or containment review: on macOS the memory ceiling is not enforced (OS limitation). CPU time, output size, core dumps, REA's 120 s deadline, input/output/entry caps and process-group cleanup still apply. A limit that cannot be applied prevents the engine from starting. Resource limits remain per operation, not aggregate host containment, as already documented. ## Author readiness Human owner: <!-- @GitHub-handle --> - [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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi added the

pull-request

label 2026-11-01 21:43:47 +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

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

No description provided.