[PR #4716] fix(javascript): bound alias-cycle call-target and returned-reference expansion #6368

New issue

Open

opened 2026-10-31 01:13:55 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:13:55 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4716
Author: @ericbyz
Created: 10/17/2026
Status: 🔄 Open

Base: main ← Head: fix/javascript-alias-cycle-expansion

---

📝 Commits (2)

• 418bf0b fix(javascript): bound alias-cycle call-target and returned-reference expansion
• 2139d9b fix(javascript): keep degraded expansions conservative and settle scans bounded

📊 Changes

4 files changed (+348 additions, -163 deletions)

View changed files

📝 src/domain/javascript/javascriptSemanticCallResolution.test.ts (+130 -2)
📝 src/domain/javascript/javascriptSemanticCallResolution.ts (+154 -32)
📝 src/domain/javascript/javascriptSemanticCalls.ts (+5 -1)
📝 src/domain/javascript/javascriptSemanticReturnedReferences.ts (+59 -128)

📄 Description

Summary

Fixes #4348. analyze-javascript-application exhausted the owned JavaScript worker heap on React bundles (playwright-core@1.58.2 recorder/trace-viewer assets) since #4243; the same files analyzed in about 1.5 s before it. Both explosion sites named in the issue are bounded now: alias-cycle call-target resolution and the returned-reference expansion.

Problem and expected behavior

• Call-target resolution: #4243 moved cycle cuts to initializer identity and correctly stopped memoizing cycleDependent results. Every read of a binding inside an alias cluster therefore re-enumerated initializer orders — an exponential simple-path search, repeated per call site.
• Returned references: the same clusters were re-walked with path-scoped blocker contexts; the number of minimal blocker contexts per (expression, projection) multiplies combinatorially. Instrumented run: one callee in index-BhTWtUlo.js reached 3.7M task pops before the 4 GiB worker heap died.

Expected: bundle analysis completes with results equal on all acyclic and pinned cyclic shapes.

Change and scope

• javascriptSemanticCallResolution.ts: resolution now runs a per-binding fixpoint. Expansion still cuts at re-entry (unchanged first-cut behavior), but cut results become provisional per binding and recompute monotonically until a pass changes nothing, then settle. The settled per-binding candidate set is canonical, so warm and cold resolutions agree (the "does not memoize alias cycle cuts across entry paths" semantics are preserved and its union reachability — e.g. fallback reachable through b → a → conditional — still resolves), and per-read results are deterministic, so they cache again.
• javascriptSemanticReturnedReferences.ts: the blocker-context/frame machinery is replaced by a single expansion that visits each (expression, projection) pair once, and past a per-callee expansion budget (20k expansions) — or a 128-entry projection cap — degrades to unknown-projection navigation instead of dropping the branch (over-approximation). Degradation is an over-approximation: every function reachable at the empty projection is still reported, which stays on the conservative side for the only consumer (markEscaped in the member-mutation pass). Acyclic and small-cluster results are unchanged.
• javascriptSemanticCalls.ts: one resolution memory per collection pass (replaces the per-call-site seenInitializers); settlement tracks provisional bindings in a dedicated set, so cycle-free files pay O(1) per call site.

Not included: precision recovery for wildcard-degraded clusters (only reachable on inputs that already exhausted the old expansion), and any change to reference/callable shapes.

Follow the contribution scope: not applicable — static-analysis-only fix, no provider/capability change.

Contract and boundary impact

• Semantic owner and earliest changed stage: JavaScript semantic derived analysis; first affected stage is call-site/member-mutation collection over an indexed source.
• Contribution scope fit and linked maintainer decision: not applicable.
• CLI and MCP/tool-catalog contract: none; analyze-javascript-application inputs/outputs unchanged.
• Provider, bridge, target-format, or platform compatibility: none.
• Evidence, artifact, provenance, or reconstruction contract: none.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
• Generated metadata/package impact: none.

Expected effects:

• Read existing files or captured data.

Evidence and regression coverage

• Tests added or updated (the scaling assertions fail on unchanged main; the semantic assertions pass on it):
  • "bounds alias-cycle initializer chains to the settled fixpoint" — pins warm≡cold and cycleDependent union results on the issue's alternating-write chain, and bounds scope lookups at depth 12 under 3× depth 8 (old code: exponential, 5.1 s at depth 12).
  • "bounds projecting alias-cycle expansion in returned references" — pins non-empty references through a projecting alias cycle and the same 3× lookup bound.
  • "degrades over-deep projections to unknown selection instead of dropping them" — 130-deep destructuring projection keeps its reference (review finding 1).
  • "keeps class members reachable when expansion degrades to unknown projections" — 20,001-alias chain past the expansion budget keeps C.make() reachable (review finding 2).
• Base reproduction (executed, Windows 11, Node 22.23.3):
  • Synthetic chain, semantic phase in-process: depth 8/10/12 = 11 ms / 100 ms / 5,146 ms before; 1.4 / 0.3 / 0.2 ms after.
  • analyze-javascript-application on index-BhTWtUlo.js (363,108 B, SHA-256 c909272a…, matches the issue) and defaultSettingsView-CJSZINFr.js (640,870 B, SHA-256 212b6c02…): both exhaust the heap on unchanged main ("Owned JavaScript worker exhausted its heap"); both complete with sealed graphs and terminal: true on this branch (~19–46 s wall incl. worker startup).
  • Instrumented expansion of the exploding callee: 3.7M+ pops before OOM on unchanged main; bounded budget after.
• Remaining proof gaps: results equality is proven by the existing 2,114 domain tests plus the two new scaling tests, not by an independent oracle; wildcard degradation precision is only exercised by inputs that previously exploded, so no user-visible before/after output exists for that mode.

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 src/domain/javascript — 80 files / 2,117 tests pass (includes the review-follow-up commit 2139d9b2a).
• npx vitest run tests/acceptance/applications — 265 passed / 4 failed; the same 4 tests fail identically on unchanged main (verified by stashing this diff and rerunning the three files: 4 failed / 1 passed both ways).
• npm run lint — 0 errors (3,902 pre-existing warnings).
• npx tsc --noEmit -p tsconfig.json — clean.
• npm run check:fast (pre-push) — passed.
• Full npx vitest run (1,465 files) — 15,324 passed / 631 failed; failures concentrate in unrelated subsystems (adb, ghidra, hopper, gdb, cutter, wasm, install script — this Windows box lacks the toolchains; e.g. installScript 35/35, sourceToBundlePaths 52/58 fail on their own). Cross-checked the impact zone against unchanged main as above; unrelated subsystems were not re-baselined on clean main.

Compatibility, safety, and release

• Breaking changes or migration steps: none.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable to this change; Windows-only run.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: not applicable.

Author readiness

Human owner: @ericbyz

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

(Left unchecked for the human owner per CONTRIBUTING — this PR was prepared with AI assistance.)

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/4716 **Author:** [@ericbyz](https://github.com/ericbyz) **Created:** 10/17/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/javascript-alias-cycle-expansion` --- ### 📝 Commits (2) - [`418bf0b`](https://github.com/morluto/rea/commit/418bf0b6371273e41175c04b3c3b849c7b12f40d) fix(javascript): bound alias-cycle call-target and returned-reference expansion - [`2139d9b`](https://github.com/morluto/rea/commit/2139d9b2a59a3f0eaa20181ce0898e971fb182e1) fix(javascript): keep degraded expansions conservative and settle scans bounded ### 📊 Changes **4 files changed** (+348 additions, -163 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/javascript/javascriptSemanticCallResolution.test.ts` (+130 -2) 📝 `src/domain/javascript/javascriptSemanticCallResolution.ts` (+154 -32) 📝 `src/domain/javascript/javascriptSemanticCalls.ts` (+5 -1) 📝 `src/domain/javascript/javascriptSemanticReturnedReferences.ts` (+59 -128) </details> ### 📄 Description ## Summary Fixes #4348. `analyze-javascript-application` exhausted the owned JavaScript worker heap on React bundles (playwright-core@1.58.2 recorder/trace-viewer assets) since #4243; the same files analyzed in about 1.5 s before it. Both explosion sites named in the issue are bounded now: alias-cycle call-target resolution and the returned-reference expansion. ## Problem and expected behavior - Call-target resolution: #4243 moved cycle cuts to initializer identity and correctly stopped memoizing `cycleDependent` results. Every read of a binding inside an alias cluster therefore re-enumerated initializer orders — an exponential simple-path search, repeated per call site. - Returned references: the same clusters were re-walked with path-scoped blocker contexts; the number of minimal blocker contexts per (expression, projection) multiplies combinatorially. Instrumented run: one callee in `index-BhTWtUlo.js` reached 3.7M task pops before the 4 GiB worker heap died. Expected: bundle analysis completes with results equal on all acyclic and pinned cyclic shapes. ## Change and scope - `javascriptSemanticCallResolution.ts`: resolution now runs a per-binding fixpoint. Expansion still cuts at re-entry (unchanged first-cut behavior), but cut results become provisional per binding and recompute monotonically until a pass changes nothing, then settle. The settled per-binding candidate set is canonical, so warm and cold resolutions agree (the "does not memoize alias cycle cuts across entry paths" semantics are preserved and its union reachability — e.g. `fallback` reachable through `b → a → conditional` — still resolves), and per-read results are deterministic, so they cache again. - `javascriptSemanticReturnedReferences.ts`: the blocker-context/frame machinery is replaced by a single expansion that visits each (expression, projection) pair once, and past a per-callee expansion budget (20k expansions) — or a 128-entry projection cap — degrades to unknown-projection navigation instead of dropping the branch (over-approximation). Degradation is an over-approximation: every function reachable at the empty projection is still reported, which stays on the conservative side for the only consumer (`markEscaped` in the member-mutation pass). Acyclic and small-cluster results are unchanged. - `javascriptSemanticCalls.ts`: one resolution memory per collection pass (replaces the per-call-site `seenInitializers`); settlement tracks provisional bindings in a dedicated set, so cycle-free files pay O(1) per call site. Not included: precision recovery for wildcard-degraded clusters (only reachable on inputs that already exhausted the old expansion), and any change to reference/callable shapes. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope): not applicable — static-analysis-only fix, no provider/capability change. ## Contract and boundary impact - Semantic owner and earliest changed stage: JavaScript semantic derived analysis; first affected stage is call-site/member-mutation collection over an indexed source. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: none; `analyze-javascript-application` inputs/outputs unchanged. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata/package impact: none. Expected effects: - [x] Read existing files or captured data. ## Evidence and regression coverage - Tests added or updated (the scaling assertions fail on unchanged main; the semantic assertions pass on it): - "bounds alias-cycle initializer chains to the settled fixpoint" — pins warm≡cold and `cycleDependent` union results on the issue's alternating-write chain, and bounds scope lookups at depth 12 under 3× depth 8 (old code: exponential, 5.1 s at depth 12). - "bounds projecting alias-cycle expansion in returned references" — pins non-empty references through a projecting alias cycle and the same 3× lookup bound. - "degrades over-deep projections to unknown selection instead of dropping them" — 130-deep destructuring projection keeps its reference (review finding 1). - "keeps class members reachable when expansion degrades to unknown projections" — 20,001-alias chain past the expansion budget keeps `C.make()` reachable (review finding 2). - Base reproduction (executed, Windows 11, Node 22.23.3): - Synthetic chain, semantic phase in-process: depth 8/10/12 = 11 ms / 100 ms / **5,146 ms** before; 1.4 / 0.3 / **0.2 ms** after. - `analyze-javascript-application` on `index-BhTWtUlo.js` (363,108 B, SHA-256 `c909272a…`, matches the issue) and `defaultSettingsView-CJSZINFr.js` (640,870 B, SHA-256 `212b6c02…`): both exhaust the heap on unchanged main ("Owned JavaScript worker exhausted its heap"); both complete with sealed graphs and `terminal: true` on this branch (~19–46 s wall incl. worker startup). - Instrumented expansion of the exploding callee: 3.7M+ pops before OOM on unchanged main; bounded budget after. - Remaining proof gaps: results equality is proven by the existing 2,114 domain tests plus the two new scaling tests, not by an independent oracle; wildcard degradation precision is only exercised by inputs that previously exploded, so no user-visible before/after output exists for that mode. 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 src/domain/javascript` — 80 files / 2,117 tests pass (includes the review-follow-up commit 2139d9b2a). - `npx vitest run tests/acceptance/applications` — 265 passed / 4 failed; the same 4 tests fail identically on unchanged main (verified by stashing this diff and rerunning the three files: 4 failed / 1 passed both ways). - `npm run lint` — 0 errors (3,902 pre-existing warnings). - `npx tsc --noEmit -p tsconfig.json` — clean. - `npm run check:fast` (pre-push) — passed. - Full `npx vitest run` (1,465 files) — 15,324 passed / 631 failed; failures concentrate in unrelated subsystems (adb, ghidra, hopper, gdb, cutter, wasm, install script — this Windows box lacks the toolchains; e.g. `installScript` 35/35, `sourceToBundlePaths` 52/58 fail on their own). Cross-checked the impact zone against unchanged main as above; unrelated subsystems were not re-baselined on clean main. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable to this change; Windows-only run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: not applicable. ## Author readiness Human owner: @ericbyz - [ ] 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. (Left unchecked for the human owner per CONTRIBUTING — this PR was prepared with AI assistance.) ## 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. - [ ] 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.}

bsakaguchi added the

pull-request

label 2026-10-31 01:13:55 +00:00

bsakaguchi referenced this issue 2026-11-01 21:42:49 +00:00

[PR #5044] [CLOSED] feat(docs): add VitePress dead-link verification to CI workflow (#5030) #6755

bsakaguchi referenced this issue 2026-11-01 21:46:57 +00:00

[PR #6368] [MERGED] docs(limits): describe how to design admission recovery #7314

bsakaguchi referenced this issue 2026-11-01 21:47:00 +00:00

[PR #6375] [MERGED] test: repair remaining bulk-merge regression fixtures #7319

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

No description provided.