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 #7210] feat(javascript): retain source-proven main-to-renderer IPC sends #7720

New issue

Open

opened 2026-11-03 13:39:53 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-03 13:39:53 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7210
Author: @frabcd
Created: 10/26/2026
Status: 🔄 Open

Base: main ← Head: codex/electron-main-transmissions

📝 Commits (1)

eef1244 feat(javascript): retain source-proven main-to-renderer IPC sends

📊 Changes

18 files changed (+897 additions, -101 deletions)

View changed files

📝 docs/javascript-artifact-reconstruction.md (+20 -0)
📝 src/application/javascript/ElectronBoundaryAnalysis.ts (+3 -0)
📝 src/application/javascript/ElectronBoundaryGraphIpc.ts (+10 -0)
📝 src/contracts/javascript/javascriptExportShapeComparisonExample.ts (+1 -0)
📝 src/contracts/javascript/javascriptRuntimeReconciliationExample.ts (+1 -0)
📝 src/domain/javascript/electronStaticAnalysisIpc.ts (+30 -21)
📝 src/domain/javascript/electronStaticAnalysisTypes.ts (+7 -0)
📝 src/domain/javascript/electronStaticReceiverAdmission.test.ts (+9 -0)
📝 src/domain/javascript/electronStaticRenderer.ts (+22 -68)
📝 src/domain/javascript/electronWrappedCallPaths.ts (+1 -2)
📝 src/domain/javascript/javascriptApplicationAnalysis.ts (+2 -0)
📝 src/domain/javascript/javascriptSemanticAnalysis.ts (+54 -0)
➕ src/domain/javascript/javascriptSemanticElectronReceiver.ts (+146 -0)
➕ src/domain/javascript/javascriptSemanticElectronReceivers.test.ts (+259 -0)
📝 src/domain/javascript/javascriptSemanticMemberMutations.ts (+54 -8)
📝 src/javascript/analysis/JavaScriptAnalysisWorkerSchemas.test.ts (+24 -0)
📝 src/javascript/analysis/JavaScriptAnalysisWorkerSchemas.ts (+13 -2)
➕ tests/boundary/cli/electronMainTransmissions.test.ts (+241 -0)

📄 Description

Summary

Retain source-proven main-to-renderer Electron IPC sends in static application analysis. BrowserWindow.webContents.send/postMessage and webContents.mainFrame.send/postMessage previously disappeared while corresponding renderer listeners remained visible.

Problem and expected behavior

On base 1173c0a9, a directory containing two main sends and two renderer listeners reports only 2 IPC operations. The change retains all 4, with main_transmissions: 2, source ranges and destination allocation identity. This is a static syntax result, not proof of delivery.

Change and scope

The existing BrowserWindow allocation/mutation resolver admits the four supported receiver/method combinations. Its allocation proof is shared with the mutation producer: proven native messaging and existing loadFile/loadURL operations preserve receiver identity, while argument escapes and invalidated receivers retain conservative effects. Loading checks the delegated WebContents methods too. This prevents a preceding load or send from hiding later sends on the same window. Main sends require receiver provenance in both the domain type and worker transport. Summary and graph consumers use those facts; no second receiver parser or runtime probe is added.

Distinct window allocations retain distinct channel nodes. Same channel text does not pair a main send with an arbitrary renderer listener. Dynamic channels stay unresolved; replaced, shadowed and lookalike receivers are excluded.

Contract and boundary impact

Semantic owner: Electron static IPC analysis, using the existing BrowserWindow receiver owner. Consumers: worker transfer, application summary and graph.
Contribution scope: existing static JavaScript/Electron boundary; no provider or target-execution authority change. No linked issue: this omission was reproduced while checking existing Electron work; the webview/wrapper work in #2094 is separate.
CLI/MCP: existing analyze-javascript-application / analyze_javascript_application gain main send facts and summary.ipc.main_transmissions.
Compatibility: the new summary count is optional when reading retained Evidence. Historical absence remains unmeasured, not zero; current analysis emits the count.
Evidence: constructor location, receiver kind, call-site range, artifact identity and unknown delivery state survive projection.
Installation/package: no dependencies, setup behavior or release metadata changes. Generated catalogs and build outputs are not committed.

Expected effects:

Read existing files or captured data.
Launch or attach to a process. Existing internal analysis workers only.
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 baseline: the six new public CLI/MCP cases fail for missing main sends; four existing scoped IPC controls pass. The later repeated-send regression also failed on the intermediate implementation in both transports (11 operations instead of 12). Producer regressions exposed receiver escape after native loading. On the final change, 1,156 tests pass across 24 files, covering the semantic producer, both public transports, application projection, worker schema validation and receiver admission.

Coverage includes load-then-repeated-send, aliases, webContents/mainFrame operations, two same-channel windows, existing renderer-to-main pairing, dynamic channels, fake/shadowed/modified receivers, delegated loading method replacement, mandatory worker provenance and historical count absence. Targets are inert fixtures; no fixture code is executed. Scoped independent review found the loading regression fixed with no remaining actionable issue.

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

Source Vitest run over 20 affected Electron/member-mutation/Map/builtin regression files — 1,125 passed, 46.30s.
npm run test:focused -- tests/boundary/cli/electronMainTransmissions.test.ts tests/boundary/cli/electronScopedIpc.test.ts src/javascript/analysis/JavaScriptAnalysisWorkerSchemas.test.ts tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts — runtime build succeeded; 31 passed, 45.03s.
node scripts/rea.mjs analyze-javascript-application <fixture> --source-path main.cjs --source-path preload.cjs --format json — original two-send/two-listener fixture now reports operations: 4, main_transmissions: 2, renderer_listeners: 2; no speculative pairing.
npm run check — exit 0: typecheck, lint, formatting, Knip, metadata, module boundaries, architecture guards, reachability and typed lint. Typed lint reports 0 errors and 3,670 advisory warnings across 5,433 files; this is not a warning-free claim.
npm run docs:check — exit 0, including 9 README conformance tests.
npm run verify:test-discovery — all 2,498 test files discovered exactly once.
git diff --check — passed.

Windows x64, Node24.22.1, npm11.16.0, Vitest5.0.3. The locked Vite8.3.5 Rolldown native binding is blocked by Windows Application Control; its WASM backend cannot resolve the Windows source paths. Tests ran with Vitest's supported Vite7.3.7 peer in ignored local dependencies, using the repository's unchanged config. Manifests/lockfile and security controls were not modified. Exact locked Vite8 test execution remains unverified on this host.

Compatibility, safety, and release

No migration or target authority change. sendToFrame, event.reply, dynamically obtained WebContents and wrapper substitution beyond source-proven receivers remain unsupported by this pass. Receiving renderer identity, listener reachability and runtime delivery remain unverified. No real Electron GUI, Hopper, Ghidra or IDA session was exercised. This is not a performance improvement claim; agent tokens, CPU and process-family peak memory were not benchmarked.

Author readiness

Human owner: @frabcd

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

Human ownership and initial readiness declared.
CI and maintainer review completed; material scope questions resolved.

_{🔄 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/7210 **Author:** [@frabcd](https://github.com/frabcd) **Created:** 10/26/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `codex/electron-main-transmissions` --- ### 📝 Commits (1) - [`eef1244`](https://github.com/morluto/rea/commit/eef1244b70276de074baa3fb1fcaf5acecd6c80b) feat(javascript): retain source-proven main-to-renderer IPC sends ### 📊 Changes **18 files changed** (+897 additions, -101 deletions) <details> <summary>View changed files</summary> 📝 `docs/javascript-artifact-reconstruction.md` (+20 -0) 📝 `src/application/javascript/ElectronBoundaryAnalysis.ts` (+3 -0) 📝 `src/application/javascript/ElectronBoundaryGraphIpc.ts` (+10 -0) 📝 `src/contracts/javascript/javascriptExportShapeComparisonExample.ts` (+1 -0) 📝 `src/contracts/javascript/javascriptRuntimeReconciliationExample.ts` (+1 -0) 📝 `src/domain/javascript/electronStaticAnalysisIpc.ts` (+30 -21) 📝 `src/domain/javascript/electronStaticAnalysisTypes.ts` (+7 -0) 📝 `src/domain/javascript/electronStaticReceiverAdmission.test.ts` (+9 -0) 📝 `src/domain/javascript/electronStaticRenderer.ts` (+22 -68) 📝 `src/domain/javascript/electronWrappedCallPaths.ts` (+1 -2) 📝 `src/domain/javascript/javascriptApplicationAnalysis.ts` (+2 -0) 📝 `src/domain/javascript/javascriptSemanticAnalysis.ts` (+54 -0) ➕ `src/domain/javascript/javascriptSemanticElectronReceiver.ts` (+146 -0) ➕ `src/domain/javascript/javascriptSemanticElectronReceivers.test.ts` (+259 -0) 📝 `src/domain/javascript/javascriptSemanticMemberMutations.ts` (+54 -8) 📝 `src/javascript/analysis/JavaScriptAnalysisWorkerSchemas.test.ts` (+24 -0) 📝 `src/javascript/analysis/JavaScriptAnalysisWorkerSchemas.ts` (+13 -2) ➕ `tests/boundary/cli/electronMainTransmissions.test.ts` (+241 -0) </details> ### 📄 Description ## Summary Retain source-proven main-to-renderer Electron IPC sends in static application analysis. `BrowserWindow.webContents.send/postMessage` and `webContents.mainFrame.send/postMessage` previously disappeared while corresponding renderer listeners remained visible. ## Problem and expected behavior On base `1173c0a9`, a directory containing two main sends and two renderer listeners reports only **2 IPC operations**. The change retains all **4**, with `main_transmissions: 2`, source ranges and destination allocation identity. This is a static syntax result, not proof of delivery. ## Change and scope The existing BrowserWindow allocation/mutation resolver admits the four supported receiver/method combinations. Its allocation proof is shared with the mutation producer: proven native messaging and existing `loadFile`/`loadURL` operations preserve receiver identity, while argument escapes and invalidated receivers retain conservative effects. Loading checks the delegated WebContents methods too. This prevents a preceding load or send from hiding later sends on the same window. Main sends require receiver provenance in both the domain type and worker transport. Summary and graph consumers use those facts; no second receiver parser or runtime probe is added. Distinct window allocations retain distinct channel nodes. Same channel text does not pair a main send with an arbitrary renderer listener. Dynamic channels stay unresolved; replaced, shadowed and lookalike receivers are excluded. ## Contract and boundary impact - Semantic owner: Electron static IPC analysis, using the existing BrowserWindow receiver owner. Consumers: worker transfer, application summary and graph. - Contribution scope: existing static JavaScript/Electron boundary; no provider or target-execution authority change. No linked issue: this omission was reproduced while checking existing Electron work; the webview/wrapper work in #2094 is separate. - CLI/MCP: existing `analyze-javascript-application` / `analyze_javascript_application` gain main send facts and `summary.ipc.main_transmissions`. - Compatibility: the new summary count is optional when reading retained Evidence. Historical absence remains unmeasured, not zero; current analysis emits the count. - Evidence: constructor location, receiver kind, call-site range, artifact identity and unknown delivery state survive projection. - Installation/package: no dependencies, setup behavior or release metadata changes. Generated catalogs and build outputs are not committed. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. Existing internal analysis workers only. - [ ] 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 baseline: the six new public CLI/MCP cases fail for missing main sends; four existing scoped IPC controls pass. The later repeated-send regression also failed on the intermediate implementation in both transports (11 operations instead of 12). Producer regressions exposed receiver escape after native loading. On the final change, **1,156 tests pass across 24 files**, covering the semantic producer, both public transports, application projection, worker schema validation and receiver admission. Coverage includes load-then-repeated-send, aliases, webContents/mainFrame operations, two same-channel windows, existing renderer-to-main pairing, dynamic channels, fake/shadowed/modified receivers, delegated loading method replacement, mandatory worker provenance and historical count absence. Targets are inert fixtures; no fixture code is executed. Scoped independent review found the loading regression fixed with no remaining actionable issue. - [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 - Source Vitest run over 20 affected Electron/member-mutation/Map/builtin regression files — **1,125 passed**, 46.30s. - `npm run test:focused -- tests/boundary/cli/electronMainTransmissions.test.ts tests/boundary/cli/electronScopedIpc.test.ts src/javascript/analysis/JavaScriptAnalysisWorkerSchemas.test.ts tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts` — runtime build succeeded; **31 passed**, 45.03s. - `node scripts/rea.mjs analyze-javascript-application <fixture> --source-path main.cjs --source-path preload.cjs --format json` — original two-send/two-listener fixture now reports `operations: 4`, `main_transmissions: 2`, `renderer_listeners: 2`; no speculative pairing. - `npm run check` — exit 0: typecheck, lint, formatting, Knip, metadata, module boundaries, architecture guards, reachability and typed lint. Typed lint reports 0 errors and 3,670 advisory warnings across 5,433 files; this is not a warning-free claim. - `npm run docs:check` — exit 0, including 9 README conformance tests. - `npm run verify:test-discovery` — all 2,498 test files discovered exactly once. - `git diff --check` — passed. Windows x64, Node24.22.1, npm11.16.0, Vitest5.0.3. The locked Vite8.3.5 Rolldown native binding is blocked by Windows Application Control; its WASM backend cannot resolve the Windows source paths. Tests ran with Vitest's supported Vite7.3.7 peer in ignored local dependencies, using the repository's unchanged config. Manifests/lockfile and security controls were not modified. Exact locked Vite8 test execution remains unverified on this host. ## Compatibility, safety, and release No migration or target authority change. `sendToFrame`, `event.reply`, dynamically obtained WebContents and wrapper substitution beyond source-proven receivers remain unsupported by this pass. Receiving renderer identity, listener reachability and runtime delivery remain unverified. No real Electron GUI, Hopper, Ghidra or IDA session was exercised. This is not a performance improvement claim; agent tokens, CPU and process-family peak memory were not benchmarked. ## Author readiness Human owner: @frabcd - [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] Human ownership and initial readiness declared. - [x] CI and maintainer review completed; material scope questions resolved. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-11-03 13:39:53 +00:00

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

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