morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #4342] [MERGED] fix(javascript): preserve uncertainty in compound assignment results #6187

New issue
Closed
opened 2026-10-31 01:12:32 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:12:32 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4342
Author: @maxazure
Created: 10/16/2026
Status: ✅ Merged
Merged: 10/16/2026
Merged by: @morluto

Base: main ← Head: fix/compound-assignment-paths-4206

📝 Commits (7)

  • f03c800 fix(javascript): preserve uncertainty in compound assignment results
  • 0e6b112 fix(javascript): retain callable logical assignment alternatives
  • 26b6e7f Merge current main and validate guarded factory compatibility
  • 56753ed fix(javascript): read prior module export assignment values
  • 95bed8f fix: keep mutable module export assignment candidates conservative
  • ac4a1df fix: preserve mixed receiver values and wrapped assignment targets
  • 221ed54 fix: carry mutable export uncertainty through copied values

📊 Changes

4 files changed (+705 additions, -36 deletions)

View changed files

📝 src/domain/javascript/electronWrappedCallPaths.test.ts (+618 -0)
📝 src/domain/javascript/javascriptSymbolicBindings.ts (+83 -36)
📝 src/domain/javascript/javascriptSymbolicControlFlow.ts (+1 -0)
📝 src/domain/javascript/javascriptSymbolicValues.ts (+3 -0)

📄 Description

Summary

Fixes #4206. Preserve guarded IPC path alternatives when a compound assignment's result is not modeled, instead of pruning a branch using its right-hand side.

Problem and expected behavior

With let flag = 1; if (flag -= 1), the symbolic evaluator used the literal RHS 1 and kept only the unguarded then-channel. The subtraction actually produces zero. A conservative static analysis must preserve the alternatives when it cannot evaluate the operation.

Change and scope

Plain = still evaluates its RHS. Arithmetic and bitwise compound assignment results become unknown. Logical assignments (&&=, ||=, ??=) use the existing logical-selection semantics and preserve selected or guarded callable alternatives. Stored namespace writes retain the full assignment node, so export-property writes and module.exports replacements use the same operator-aware evaluator. This removes the second place that stripped the operator.

No arithmetic interpreter or target execution is added. This does not change the separate native-addon binding classifier addressed by #4338.

Contract and boundary impact

  • Semantic owner and earliest changed stage: JavaScriptSymbolicBindings, before contextual path selection.
  • Contribution scope fit and linked maintainer decision: ordinary static-analysis correctness fix; no new authority, decision not applicable.
  • CLI and MCP/tool-catalog contract: unchanged shape; unknown results retain guarded static candidates.
  • Provider, bridge, target-format, or platform compatibility: no provider changes.
  • Evidence, artifact, provenance, or reconstruction contract: preserve raw IPC observations and predicates; do not imply runtime invocation.
  • Target selection, authority, upstream behavior, and cleanup details: unchanged.
  • Generated metadata, package, or installation impact: 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

12 added static-analysis boundary cases cover inline arithmetic, bitwise and logical assignments, unknown operands, plain-assignment controls, and stored namespace property/replacement writes.

On base 42fc6c5, the new cases produce 8 failures with 57 passing existing/control cases. With the fix, all 65 pass.

The exact three-case public CLI reproduction from #4206 was run before and after against inert extracted applications:

  • Before: compound keeps only unguarded then.
  • After: compound retains both then/else with their predicates.
  • Plain flag = 0 stays else-only; unknown operand stays guarded both.
  • Both raw IPC calls survive in every case.

Fixture JavaScript was never executed and Electron was not loaded.

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

Initial revision validation (f03c800)

Pinned Node 24.18.0 / npm 11.16.0, Linux:

  • npm run test:focused -- src/domain/javascript/electronWrappedCallPaths.test.ts src/domain/javascript/javascriptSymbolicBindings.test.ts src/domain/javascript/electronModuleInterop.test.ts src/domain/javascript/electronBundledRequireIdentity.test.ts — 332 passed.
  • npm run build:cached and exact issue CLI reproduction — passed before/after with results above.
  • npm run check:fast — passed.
  • npm run check — passed.
  • npm run verify:test-discovery — 1,400 files discovered exactly once.
  • Normal commit hooks and diff whitespace checks — passed.

An independent macOS arm64 review of the initial f03c800 head repeated the four focused suites (332 passed), check:fast, check, discovery (1,400 files), and the exact CLI before/after reproduction with the pinned toolchain. Baseline production plus the regression tests produced the expected 8 failures / 57 passes; the PR head passed all 65. Additional inert static probes for nested assignments, later plain writes, and returned-function branches passed. No code changes were needed.

Review follow-up and CI preflight

The logical-assignment callable regression was reproduced with 11 failing cases before the follow-up. Fourteen added cases now cover RHS functions, resolvable LHS callables, skipped RHS and cyclic namespace reads. The focused suites passed 346 tests before syncing main.

After integrating main 2c75835 (including guarded factory completion), the tested tree is 4ff2da60:

  • Related regressions and upstream factory completion: 359 passed.
  • Cold check:ci, discovery (1,414 files), Python (106 tests), and test:prepare: passed.
  • Full source group: 8,574 passed, 12 failed, 8 skipped. All 12 failures reproduce on exact main in this environment.
  • Rechecked the 35 previously failing files: 153 failures across 29 files, all matching exact main by file and test name. Six formerly failing files passed.
  • Original issue CLI and logical-callable CLI reproductions passed.

Before syncing main, a clean-install CI-faithful source plus five built-shard run accounted for all 1,400 files: 16,032 passed, 159 failed, 141 skipped. All failures reproduced on the old base. Cold static/build, docs, real JavaScript recovery (12 observations), and Inspector (8 variants) passed. That complete shard run applies to the pre-sync tree, not the current tree. The full five built shards were not repeated after syncing.

Local host/provider restrictions prevent claiming a fully green local suite. Windows cross-build and the complete installed-package gate were not run because the cross-compiler/artifacts were unavailable. GitHub CI on the new head is pending.

Known pre-existing limitation: prior mutable namespace LHS callables can be lost through last-write lookup; this follow-up restores guarded RHS candidates without adding flow-sensitive write tracking.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: Linux and macOS arm64 static CLI; no external provider.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new target execution or authority.
  • Proof gaps: the current merged tree has not had all five built shards repeated locally; no complete installed-package or Windows cross-build validation. No performance claim; stored plain assignments add a bounded evaluation layer.

Author readiness

Human owner: @maxazure. Initial readiness was confirmed by the owner on 2026-10-16 for f03c800; subsequent review fixes and their verification are recorded above.

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

🔄 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/4342 **Author:** [@maxazure](https://github.com/maxazure) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/16/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/compound-assignment-paths-4206` --- ### 📝 Commits (7) - [`f03c800`](https://github.com/morluto/rea/commit/f03c800bcfd8ba4cc2b1388c4308cb9da20177bc) fix(javascript): preserve uncertainty in compound assignment results - [`0e6b112`](https://github.com/morluto/rea/commit/0e6b1123d5baf86ed0ea67fffad83386e2c8faf0) fix(javascript): retain callable logical assignment alternatives - [`26b6e7f`](https://github.com/morluto/rea/commit/26b6e7f7bb7f4842fb54cdc43d51bb68e19fdff2) Merge current main and validate guarded factory compatibility - [`56753ed`](https://github.com/morluto/rea/commit/56753ed27ef8a986d531887abc6f11e36c8d0c7f) fix(javascript): read prior module export assignment values - [`95bed8f`](https://github.com/morluto/rea/commit/95bed8f1961255062832670b8badbce89467969f) fix: keep mutable module export assignment candidates conservative - [`ac4a1df`](https://github.com/morluto/rea/commit/ac4a1df04427a86cc565ab6cf2afb571dde0d4ed) fix: preserve mixed receiver values and wrapped assignment targets - [`221ed54`](https://github.com/morluto/rea/commit/221ed547c10f72a92df23903db2de87b448e0be5) fix: carry mutable export uncertainty through copied values ### 📊 Changes **4 files changed** (+705 additions, -36 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/javascript/electronWrappedCallPaths.test.ts` (+618 -0) 📝 `src/domain/javascript/javascriptSymbolicBindings.ts` (+83 -36) 📝 `src/domain/javascript/javascriptSymbolicControlFlow.ts` (+1 -0) 📝 `src/domain/javascript/javascriptSymbolicValues.ts` (+3 -0) </details> ### 📄 Description ## Summary Fixes #4206. Preserve guarded IPC path alternatives when a compound assignment's result is not modeled, instead of pruning a branch using its right-hand side. ## Problem and expected behavior With `let flag = 1; if (flag -= 1)`, the symbolic evaluator used the literal RHS `1` and kept only the unguarded then-channel. The subtraction actually produces zero. A conservative static analysis must preserve the alternatives when it cannot evaluate the operation. ## Change and scope Plain `=` still evaluates its RHS. Arithmetic and bitwise compound assignment results become unknown. Logical assignments (`&&=`, `||=`, `??=`) use the existing logical-selection semantics and preserve selected or guarded callable alternatives. Stored namespace writes retain the full assignment node, so export-property writes and `module.exports` replacements use the same operator-aware evaluator. This removes the second place that stripped the operator. No arithmetic interpreter or target execution is added. This does not change the separate native-addon binding classifier addressed by #4338. ## Contract and boundary impact - Semantic owner and earliest changed stage: JavaScriptSymbolicBindings, before contextual path selection. - Contribution scope fit and linked maintainer decision: ordinary static-analysis correctness fix; no new authority, decision not applicable. - CLI and MCP/tool-catalog contract: unchanged shape; unknown results retain guarded static candidates. - Provider, bridge, target-format, or platform compatibility: no provider changes. - Evidence, artifact, provenance, or reconstruction contract: preserve raw IPC observations and predicates; do not imply runtime invocation. - Target selection, authority, upstream behavior, and cleanup details: unchanged. - Generated metadata, package, or installation impact: 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 12 added static-analysis boundary cases cover inline arithmetic, bitwise and logical assignments, unknown operands, plain-assignment controls, and stored namespace property/replacement writes. On base `42fc6c5`, the new cases produce 8 failures with 57 passing existing/control cases. With the fix, all 65 pass. The exact three-case public CLI reproduction from #4206 was run before and after against inert extracted applications: - Before: compound keeps only unguarded then. - After: compound retains both then/else with their predicates. - Plain `flag = 0` stays else-only; unknown operand stays guarded both. - Both raw IPC calls survive in every case. Fixture JavaScript was never executed and Electron was not loaded. - [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. ## Initial revision validation (`f03c800`) Pinned Node 24.18.0 / npm 11.16.0, Linux: - `npm run test:focused -- src/domain/javascript/electronWrappedCallPaths.test.ts src/domain/javascript/javascriptSymbolicBindings.test.ts src/domain/javascript/electronModuleInterop.test.ts src/domain/javascript/electronBundledRequireIdentity.test.ts` — 332 passed. - `npm run build:cached` and exact issue CLI reproduction — passed before/after with results above. - `npm run check:fast` — passed. - `npm run check` — passed. - `npm run verify:test-discovery` — 1,400 files discovered exactly once. - Normal commit hooks and diff whitespace checks — passed. An independent macOS arm64 review of the initial `f03c800` head repeated the four focused suites (332 passed), check:fast, check, discovery (1,400 files), and the exact CLI before/after reproduction with the pinned toolchain. Baseline production plus the regression tests produced the expected 8 failures / 57 passes; the PR head passed all 65. Additional inert static probes for nested assignments, later plain writes, and returned-function branches passed. No code changes were needed. ## Review follow-up and CI preflight The logical-assignment callable regression was reproduced with 11 failing cases before the follow-up. Fourteen added cases now cover RHS functions, resolvable LHS callables, skipped RHS and cyclic namespace reads. The focused suites passed 346 tests before syncing main. After integrating main `2c75835` (including guarded factory completion), the tested tree is `4ff2da60`: - Related regressions and upstream factory completion: 359 passed. - Cold `check:ci`, discovery (1,414 files), Python (106 tests), and `test:prepare`: passed. - Full source group: 8,574 passed, 12 failed, 8 skipped. All 12 failures reproduce on exact main in this environment. - Rechecked the 35 previously failing files: 153 failures across 29 files, all matching exact main by file and test name. Six formerly failing files passed. - Original issue CLI and logical-callable CLI reproductions passed. Before syncing main, a clean-install CI-faithful source plus five built-shard run accounted for all 1,400 files: 16,032 passed, 159 failed, 141 skipped. All failures reproduced on the old base. Cold static/build, docs, real JavaScript recovery (12 observations), and Inspector (8 variants) passed. That complete shard run applies to the pre-sync tree, not the current tree. The full five built shards were not repeated after syncing. Local host/provider restrictions prevent claiming a fully green local suite. Windows cross-build and the complete installed-package gate were not run because the cross-compiler/artifacts were unavailable. GitHub CI on the new head is pending. Known pre-existing limitation: prior mutable namespace LHS callables can be lost through last-write lookup; this follow-up restores guarded RHS candidates without adding flow-sensitive write tracking. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: Linux and macOS arm64 static CLI; no external provider. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new target execution or authority. - Proof gaps: the current merged tree has not had all five built shards repeated locally; no complete installed-package or Windows cross-build validation. No performance claim; stored plain assignments add a bounded evaluation layer. ## Author readiness Human owner: @maxazure. Initial readiness was confirmed by the owner on 2026-10-16 for `f03c800`; subsequent review fixes and their verification are recorded above. - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:12:32 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6187
No description provided.