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 #3742] feat(experiments): prototype Electron IPC effect attribution #5874

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3742
Author: @JNTMTMTM
Created: 10/14/2026
Status: 🔄 Open

Base: main ← Head: codex/electron-feature-path-prototype

📝 Commits (5)

  • a6acdfe feat(experiments): prototype Electron IPC effect attribution
  • bf464ab fix(experiments): retain cleanup ownership and capture evidence
  • eaf931b test(cli): batch selected client profile readiness checks
  • c05c082 Merge remote-tracking branch 'origin/main' into sweep/3742
  • e732f61 test(experiments): verify macOS head and gate Electron Node regressions

📊 Changes

17 files changed (+3272 additions, -0 deletions)

View changed files

📝 .github/workflows/ci.yml (+4 -0)
➕ experiments/electron-feature-path/README.md (+268 -0)
➕ experiments/electron-feature-path/fixture/main.cjs (+60 -0)
➕ experiments/electron-feature-path/fixture/preload.cjs (+7 -0)
➕ experiments/electron-feature-path/fixture/renderer.html (+7 -0)
➕ experiments/electron-feature-path/fixture/renderer.js (+8 -0)
➕ experiments/electron-feature-path/mcp-lifecycle.mjs (+208 -0)
➕ experiments/electron-feature-path/mcp-lifecycle.test.mjs (+425 -0)
➕ experiments/electron-feature-path/recorder.mjs (+225 -0)
➕ experiments/electron-feature-path/recorder.test.mjs (+503 -0)
➕ experiments/electron-feature-path/trace-contract.mjs (+90 -0)
➕ experiments/electron-feature-path/trace-contract.test.mjs (+308 -0)
➕ experiments/electron-feature-path/verifier-run.mjs (+119 -0)
➕ experiments/electron-feature-path/verifier-run.test.mjs (+322 -0)
➕ experiments/electron-feature-path/verify-mcp.mjs (+459 -0)
➕ experiments/electron-feature-path/verify-mcp.test.mjs (+205 -0)
📝 tests/boundary/filesystem/ciFeedback.test.ts (+54 -0)

📄 Description

Summary

An isolated, unregistered fixture experiment associates one selected main IPC invocation with a selected file-write call in its async context. It preserves invocation/effect identity and unknown lifetime; it does not establish UI causality, renderer/preload execution, cross-process tracing or native calls. No production tools, arbitrary-app injection or package integration are added.

Maintainer scope decision: pending / integration hold. Tracker #4027 now tracks this proposal, but grants no runtime authority or scope approval. The latest human review's hold remains. CI success and existing human readiness declarations do not replace that decision; this PR must not be merged or enabled without it.

Current verification and changes

Validated the merged head c05c082bf700f719c4efd5f60f103bf45b293292 on 2026-10-15 in a fresh worktree, preserving the original checkout. Follow-up head e732f6199940233345b69c6cde28a5441c893d25 changes only the experiment README, CI and a CI regression; all runtime, recorder, fixture and verifier bytes are unchanged from the real-provider runs.

The audit found that Vitest discovers .test.ts, while CI never ran the experimental .test.mjs. Build package now runs all five experiment files in a separate uncached step after test:prepare builds their required runtime. The existing build/required gate propagates failures. No timeout changes, retries, weakened assertions or automatic Electron installation. A workflow regression failed before this step was added and verifies preparation order plus required-gate rejection of failed/cancelled/skipped/missing builds.

Host/tools: macOS 27.0.1 (26A434), arm64; Node 24.18.0 / npm 11.16.0; MCP client/server 2.3.1; existing explicitly selected Electron 44.4.3. Electron executable SHA-256: 52591945c62a357a093d45bab2a13ef95636e5e16c40ea960e428123ce58365e. No host security settings changed.

Executed locally:

  • npm ci and npm run build:cached: passed.
  • node --test experiments/electron-feature-path/*.test.mjs: 61 passed / 0 failed / 0 skipped. Includes actual installed-SDK cancellation, retained-owner subprocess and real-MCP failed-capture/checkpoint-collision cases.
  • npm run test:focused -- tests/boundary/mcp/electronMcp.test.ts tests/boundary/browser/electronActiveHook.test.ts tests/boundary/cli/electronCli.test.ts: 16 passed / 0 failed / 0 skipped.
  • Five related CI workflow/selection/cache/report/gate files: 254 passed / 0 failed / 0 skipped.
  • npm run check, npm run docs:check (5 README cases), npm run verify:test-discovery (1,321 unique Vitest files), pre-commit formatting/lint, pre-push npm run check:fast, and git diff --check: passed. Existing bundler/lint warnings remain.
  • Real stdio MCP baseline, prototype and --cancel-after-ready: passed, then repeated with a local SDK JSON-message recorder. Every run used a new absolute directory/profile and the explicit existing Electron executable.
  • Actual compiled node scripts/rea.mjs capture-electron-scenario ABS_REQUEST_JSON --json: separate baseline/prototype fixture runs passed.
  • npm pack --dry-run --ignore-scripts --json: 1,678 files, zero experimental files. Actual TypeScript build-file inventory (1,989 inputs), runtime/source import search and the 207-tool catalog also exclude the experiment.

Evidence, ownership and limitations

Both normal surfaces produced exactly fixture exported\n; baseline retained zero experimental events, prototype four. The selected fulfilled file effect shares the invocation ID, selected output path and active handler context. It remains fixture-probe async-context authority with unknown UI association. Nine source digests and the executable digest remained unchanged, including after the CLI runs.

Normal MCP runs preserve a parsed complete static-parent checkpoint and final four-record Evidence bundle, plus separate before/after export requests/replies. The historical automated “Failed runs lose complete analysis” finding is covered by the unconditional pre-capture checkpoint and the executed real-MCP failure/collision regressions.

Cancellation observed fixture readiness, sent notification for the actual request ID, received an independent session-drain acknowledgement and checked run-token process absence against the prelaunch identity baseline: cleaned: true, signaled: false. The recorded run preserved 14 unrelated unreadable-process observations. The suppressed/unavailable capture reply is not cleanup proof. Cancellation retains the complete checkpoint; no final capture reply or post-drain bundle is fabricated. No run required unresolved owner retention.

Complete-workflow samples include discovery, schema checks, analysis, follow-ups, evidence exports and cleanup. Unrecorded baseline/prototype MCP runs: 7.28 / 7.33 s elapsed, 8.48 / 8.67 s child wait4 CPU, 1,332 / 1,437 MiB sampled summed family RSS. SDK-recorded repeats: 6.91 / 6.11 s, 8.24 / 7.64 s CPU, 1,405 / 1,419 MiB RSS. CLI baseline/prototype: 2.30 / 2.87 s, 2.76 / 3.03 s CPU, 881 / 852 MiB RSS. These are fresh-process/profile samples on a prepared build with warm filesystem; no performance improvement is claimed.

RSS sampling is 30 ms plus ps time, may miss peaks/short children and counts shared pages multiple times. wait4 descendant accounting depends on OS/reaping. The local recorder retains parsed SDK messages until exit; its cost is included. tokenx 1.3.0 estimates serialized request/reply values, including initialization, catalog and follow-ups: baseline 789 / 1,094,470, prototype 786 / 1,094,462; catalog alone 974,771. These are heuristics, not actual model tokens/billing. No model is called by the verifiers; agent rendering/prompt/reasoning, hosted CI resources, OS-cold and warm-session costs remain unmeasured. Some probes overlapped CI regression work.

Raw logs and large evidence remain local under outputs/macos-c05c082-20261015/ in the task workspace, including selections/digests, raw tool replies, parsed SDK JSON messages (not original wire bytes), CLI requests/results, checkpoints/bundles, command metrics and independent evidence-audit.json. No binaries, dist, dependencies, profiles or environment credentials are committed. The README verification record gives the exact local evidence root and measurement limits.

Historical evidence and remaining gaps

Earlier macOS records and the Windows test-only/hosted-CI results for eaf931bb99cffb7ac607e752e4b8a0ee46807f08 remain historical, separately labeled in the README; they do not validate the later main merge. The earlier intermittent Windows module-trace timeout root cause remains unconfirmed. No new Windows/Linux Electron, arbitrary-app, renderer/preload, cross-process or native-call proof is claimed.

Current CI / automated review

Pushed without force. CI run 38767674862 completed successfully: all 35 jobs passed, including the five built-test shards, Source tests, Windows capability/package lane, Apple artifact lane, portable aggregation and CI required. The new experiment step actually ran 61 passed / 0 failed / 0 skipped. The run is associated with exact PR head e732f6199940233345b69c6cde28a5441c893d25; GitHub executed synthetic merge adfb29f1831430bafaebebe7eb8ccad248fdb829 against base 5b16f2431062eea6ffd245a9e05512790007cb13. The local experiment suite was also rerun directly on final head: 61 / 0 / 0. Greptile Review passed at that head (5/5), with no new inline findings. The earlier Codex review-limit notice does not establish an additional review. The human maintainer scope hold remains unresolved. No merge or human readiness attestation is performed by this verification.

Author readiness

Human owner: @JNTMTMTM

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

Before merge

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

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

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/3742 **Author:** [@JNTMTMTM](https://github.com/JNTMTMTM) **Created:** 10/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `codex/electron-feature-path-prototype` --- ### 📝 Commits (5) - [`a6acdfe`](https://github.com/morluto/rea/commit/a6acdfe7fd423741256adf2e2259b2ce834816e9) feat(experiments): prototype Electron IPC effect attribution - [`bf464ab`](https://github.com/morluto/rea/commit/bf464ab7b6aec967a1ff649cbf7244ed7b6164a8) fix(experiments): retain cleanup ownership and capture evidence - [`eaf931b`](https://github.com/morluto/rea/commit/eaf931bb99cffb7ac607e752e4b8a0ee46807f08) test(cli): batch selected client profile readiness checks - [`c05c082`](https://github.com/morluto/rea/commit/c05c082bf700f719c4efd5f60f103bf45b293292) Merge remote-tracking branch 'origin/main' into sweep/3742 - [`e732f61`](https://github.com/morluto/rea/commit/e732f6199940233345b69c6cde28a5441c893d25) test(experiments): verify macOS head and gate Electron Node regressions ### 📊 Changes **17 files changed** (+3272 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/ci.yml` (+4 -0) ➕ `experiments/electron-feature-path/README.md` (+268 -0) ➕ `experiments/electron-feature-path/fixture/main.cjs` (+60 -0) ➕ `experiments/electron-feature-path/fixture/preload.cjs` (+7 -0) ➕ `experiments/electron-feature-path/fixture/renderer.html` (+7 -0) ➕ `experiments/electron-feature-path/fixture/renderer.js` (+8 -0) ➕ `experiments/electron-feature-path/mcp-lifecycle.mjs` (+208 -0) ➕ `experiments/electron-feature-path/mcp-lifecycle.test.mjs` (+425 -0) ➕ `experiments/electron-feature-path/recorder.mjs` (+225 -0) ➕ `experiments/electron-feature-path/recorder.test.mjs` (+503 -0) ➕ `experiments/electron-feature-path/trace-contract.mjs` (+90 -0) ➕ `experiments/electron-feature-path/trace-contract.test.mjs` (+308 -0) ➕ `experiments/electron-feature-path/verifier-run.mjs` (+119 -0) ➕ `experiments/electron-feature-path/verifier-run.test.mjs` (+322 -0) ➕ `experiments/electron-feature-path/verify-mcp.mjs` (+459 -0) ➕ `experiments/electron-feature-path/verify-mcp.test.mjs` (+205 -0) 📝 `tests/boundary/filesystem/ciFeedback.test.ts` (+54 -0) </details> ### 📄 Description ## Summary An isolated, unregistered fixture experiment associates one selected main IPC invocation with a selected file-write call in its async context. It preserves invocation/effect identity and unknown lifetime; it does not establish UI causality, renderer/preload execution, cross-process tracing or native calls. No production tools, arbitrary-app injection or package integration are added. Maintainer scope decision: **pending / integration hold**. [Tracker #4027](https://github.com/morluto/rea/issues/4027) now tracks this proposal, but grants no runtime authority or scope approval. The latest human review's hold remains. CI success and existing human readiness declarations do not replace that decision; this PR must not be merged or enabled without it. ## Current verification and changes Validated the merged head `c05c082bf700f719c4efd5f60f103bf45b293292` on 2026-10-15 in a fresh worktree, preserving the original checkout. Follow-up head **`e732f6199940233345b69c6cde28a5441c893d25`** changes only the experiment README, CI and a CI regression; all runtime, recorder, fixture and verifier bytes are unchanged from the real-provider runs. The audit found that Vitest discovers `.test.ts`, while CI never ran the experimental `.test.mjs`. Build package now runs all five experiment files in a separate uncached step after `test:prepare` builds their required runtime. The existing build/required gate propagates failures. No timeout changes, retries, weakened assertions or automatic Electron installation. A workflow regression failed before this step was added and verifies preparation order plus required-gate rejection of failed/cancelled/skipped/missing builds. Host/tools: **macOS 27.0.1 (26A434), arm64; Node 24.18.0 / npm 11.16.0; MCP client/server 2.3.1; existing explicitly selected Electron 44.4.3**. Electron executable SHA-256: `52591945c62a357a093d45bab2a13ef95636e5e16c40ea960e428123ce58365e`. No host security settings changed. Executed locally: - `npm ci` and `npm run build:cached`: passed. - `node --test experiments/electron-feature-path/*.test.mjs`: **61 passed / 0 failed / 0 skipped**. Includes actual installed-SDK cancellation, retained-owner subprocess and real-MCP failed-capture/checkpoint-collision cases. - `npm run test:focused -- tests/boundary/mcp/electronMcp.test.ts tests/boundary/browser/electronActiveHook.test.ts tests/boundary/cli/electronCli.test.ts`: **16 passed / 0 failed / 0 skipped**. - Five related CI workflow/selection/cache/report/gate files: **254 passed / 0 failed / 0 skipped**. - `npm run check`, `npm run docs:check` (5 README cases), `npm run verify:test-discovery` (1,321 unique Vitest files), pre-commit formatting/lint, pre-push `npm run check:fast`, and `git diff --check`: passed. Existing bundler/lint warnings remain. - Real stdio MCP baseline, prototype and `--cancel-after-ready`: passed, then repeated with a local SDK JSON-message recorder. Every run used a new absolute directory/profile and the explicit existing Electron executable. - Actual compiled `node scripts/rea.mjs capture-electron-scenario ABS_REQUEST_JSON --json`: separate baseline/prototype fixture runs passed. - `npm pack --dry-run --ignore-scripts --json`: 1,678 files, **zero experimental files**. Actual TypeScript build-file inventory (1,989 inputs), runtime/source import search and the 207-tool catalog also exclude the experiment. ## Evidence, ownership and limitations Both normal surfaces produced exactly `fixture exported\n`; baseline retained zero experimental events, prototype four. The selected fulfilled file effect shares the invocation ID, selected output path and active handler context. It remains fixture-probe async-context authority with unknown UI association. Nine source digests and the executable digest remained unchanged, including after the CLI runs. Normal MCP runs preserve a parsed complete static-parent checkpoint and final **four-record Evidence bundle**, plus separate before/after export requests/replies. The historical automated “Failed runs lose complete analysis” finding is covered by the unconditional pre-capture checkpoint and the executed real-MCP failure/collision regressions. Cancellation observed fixture readiness, sent notification for the actual request ID, received an independent session-drain acknowledgement and checked run-token process absence against the prelaunch identity baseline: **`cleaned: true`, `signaled: false`**. The recorded run preserved 14 unrelated unreadable-process observations. The suppressed/unavailable capture reply is not cleanup proof. Cancellation retains the complete checkpoint; no final capture reply or post-drain bundle is fabricated. No run required unresolved owner retention. Complete-workflow samples include discovery, schema checks, analysis, follow-ups, evidence exports and cleanup. Unrecorded baseline/prototype MCP runs: **7.28 / 7.33 s** elapsed, **8.48 / 8.67 s** child wait4 CPU, **1,332 / 1,437 MiB** sampled summed family RSS. SDK-recorded repeats: **6.91 / 6.11 s**, **8.24 / 7.64 s CPU**, **1,405 / 1,419 MiB RSS**. CLI baseline/prototype: **2.30 / 2.87 s**, **2.76 / 3.03 s CPU**, **881 / 852 MiB RSS**. These are fresh-process/profile samples on a prepared build with warm filesystem; no performance improvement is claimed. RSS sampling is 30 ms plus `ps` time, may miss peaks/short children and counts shared pages multiple times. wait4 descendant accounting depends on OS/reaping. The local recorder retains parsed SDK messages until exit; its cost is included. `tokenx` 1.3.0 estimates serialized request/reply values, including initialization, catalog and follow-ups: baseline **789 / 1,094,470**, prototype **786 / 1,094,462**; catalog alone **974,771**. These are heuristics, **not actual model tokens/billing**. No model is called by the verifiers; agent rendering/prompt/reasoning, hosted CI resources, OS-cold and warm-session costs remain unmeasured. Some probes overlapped CI regression work. Raw logs and large evidence remain local under `outputs/macos-c05c082-20261015/` in the task workspace, including selections/digests, raw tool replies, parsed SDK JSON messages (not original wire bytes), CLI requests/results, checkpoints/bundles, command metrics and independent `evidence-audit.json`. No binaries, dist, dependencies, profiles or environment credentials are committed. The [README verification record](https://github.com/JNTMTMTM/rea/blob/e732f6199940233345b69c6cde28a5441c893d25/experiments/electron-feature-path/README.md#current-macos-verification--2026-10-15) gives the exact local evidence root and measurement limits. ## Historical evidence and remaining gaps Earlier macOS records and the Windows test-only/hosted-CI results for `eaf931bb99cffb7ac607e752e4b8a0ee46807f08` remain historical, separately labeled in the README; they do not validate the later main merge. The earlier intermittent Windows module-trace timeout root cause remains unconfirmed. No new Windows/Linux Electron, arbitrary-app, renderer/preload, cross-process or native-call proof is claimed. ## Current CI / automated review Pushed without force. [CI run 38767674862](https://github.com/morluto/rea/actions/runs/38767674862) completed **successfully: all 35 jobs passed**, including the five built-test shards, Source tests, Windows capability/package lane, Apple artifact lane, portable aggregation and CI required. The new experiment step actually ran **61 passed / 0 failed / 0 skipped**. The run is associated with exact PR head `e732f6199940233345b69c6cde28a5441c893d25`; GitHub executed synthetic merge `adfb29f1831430bafaebebe7eb8ccad248fdb829` against base `5b16f2431062eea6ffd245a9e05512790007cb13`. The local experiment suite was also rerun directly on final head: **61 / 0 / 0**. **Greptile Review passed at that head (5/5), with no new inline findings.** The earlier Codex review-limit notice does not establish an additional review. The human maintainer scope hold remains unresolved. No merge or human readiness attestation is performed by this verification. ## Author readiness Human owner: @JNTMTMTM - [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 - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#5874
No description provided.