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 #5673] [MERGED] test(cli): keep IPC trace input under the Linux spawn limit #7028

New issue
Closed
opened 2026-11-01 21:44:49 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:44:49 +00:00
Owner
Copy link

📋 Pull Request Information

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

Base: main ← Head: cursor/fix-ipc-trace-e2big-a55b

📝 Commits (4)

  • 4a31a01 test(cli): keep IPC trace input under the Linux spawn limit
  • 7bfc2a5 Merge remote-tracking branch 'origin/main' into cursor/fix-ipc-trace-e2big-a55b
  • e975bcb test(process): size the spawn ceiling from ARG_MAX and MAX_ARG_STRLEN
  • 05f4b93 style(test): format files rejected by oxfmt in static checks

📊 Changes

5 files changed (+273 additions, -11 deletions)

View changed files

📝 tests/acceptance/applications/electronIpcListenerCallsiteCli.test.ts (+20 -4)
➕ tests/boundary/process/spawnArgumentLimit.test.ts (+181 -0)
📝 tests/composition/reverseEngineeringAdmission.test.ts (+4 -4)
📝 tests/support/cli/cliFixture.ts (+2 -3)
➕ tests/support/process/spawnArgumentLimit.ts (+66 -0)

📄 Description

Summary

electronIpcListenerCallsiteCli dies on GitHub Actions with spawn E2BIG while starting trace-application-feature. The trace request is one argv string of the full application Evidence document (~292 KiB). Linux rejects a single argv or env string at MAX_ARG_STRLEN (32 pages, 131071 bytes on the 4 KiB Actions runners) before the process starts. The CLI already reads that JSON from a file. This keeps the file path, requires the spawned argv to fit the per-string ceiling, and locks both that ceiling and the aggregate ARG_MAX budget with a process-registry regression that does not need Electron.

Human owner: @morluto

Cited failures, both on the inline-JSON revision:

Both stacks are processFixture spawn ← cliFixture.run ← the CLI case at the trace invocation. The earlier analyze-javascript-application spawn uses the same minimal environment and succeeds, so this is the argument string, not inherited env or NODE_OPTIONS.

Problem and expected behavior

createTestCli spawns node scripts/rea.mjs with PATH only (plus the Windows temp roots). Placing JSON.stringify({ application, seed, direction }) in argv makes one argument of 292118 bytes for this fixture. On this host getconf PAGE_SIZE is 4096 and getconf ARG_MAX is 2097152. A 131071-byte argument exits 0; 131072 bytes throws spawn E2BIG synchronously. With RLIMIT_STACK of 512 KiB, ARG_MAX drops to 131072 and a payload at the single-string ceiling still fails because the filename, other argv, environment, NULs, and pointer table consume the rest. The trace command must still count the exposed pong listener callsites and return matched_seeds: 1.

Change and scope

The acceptance CLI case writes the trace request to trace-input.json and passes that path. It requires the serialized document to stay past the 4 KiB-page ceiling and the actual argv to fit under it, so putting the document back on argv fails on every host.

acceptedSpawnPayloadBytes takes the minimum of the per-string ceiling and the bytes left in ARG_MAX after the filename (copied before argv), the other argv strings, each KEY=value environment string, their NULs, and one native pointer per argv and env string. The registry test spawns that derived size. When the fixed image already fills ARG_MAX, it skips the success spawn. One byte past the per-string ceiling, and one byte past a tighter aggregate budget, must throw E2BIG.

check:ci:fast failed oxfmt --check on tests/support/cli/cliFixture.ts and, on the merge with main, tests/composition/reverseEngineeringAdmission.test.ts. Those two files are formatted and nothing else.

Contribution scope: not applicable. Test-only. No new provider, target execution, injection, mutation, or protection recovery.

Intentionally left alone: production CLI parsing, Evidence size, and a harness-wide argv guard in createTestCli (other tests pass intentional inline JSON).

Contract and boundary impact

  • Semantic owner and earliest changed stage: test process spawn. The failure is execve of the compiled CLI, before command dispatch.
  • Contribution scope fit and linked maintainer decision: ordinary test fix within the existing CLI JSON file input. Maintainer scope decision not applicable.
  • CLI and MCP/tool-catalog contract: none. parseCliJsonInput already reads a path when the argument is not JSON.
  • Provider, bridge, target-format, or platform compatibility: Linux single-argument limit and aggregate ARG_MAX. The shared budget is the 4 KiB-page ceiling Actions uses. Larger page sizes still check 32 * pageSize - 1. The kernel spawn case is skipped off Linux. Pointer width is 4 bytes for arm, ia32, mips, and mipsel, and 8 otherwise.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • 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

  • Tests added or updated: tests/acceptance/applications/electronIpcListenerCallsiteCli.test.ts, tests/boundary/process/spawnArgumentLimit.test.ts, tests/support/process/spawnArgumentLimit.ts. Format-only: tests/support/cli/cliFixture.ts, tests/composition/reverseEngineeringAdmission.test.ts.
  • Base reproduction: on Linux Node v24.18.0, the fixture trace argument is 292118 bytes and spawn throws E2BIG. Length 131071 exits 0; length 131072 throws E2BIG. The same document passed as a file path exits 0 with matched_seeds: 1. Re-introducing that string as an argv element fails assertSpawnArgumentsWithinLimit before spawn.
  • Aggregate headroom: under prlimit --stack=524288, getconf ARG_MAX is 131072. The derived payload (130532 bytes for this image) exits 0 and one more byte throws E2BIG. The same vitest file passes under that stack limit.
  • Static check: job https://github.com/morluto/rea/actions/runs/39490671462/job/118863805852 failed in npm run check:ci:fast because oxfmt --check . reported those two files. format:check is clean after the format commit.
  • User-visible CLI/MCP output (if applicable): none.
  • Remaining proof gaps: the updated tree has not yet finished a new GitHub Actions run.

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

  • Direct spawn probe — 292118-byte trace argument and a 131072-byte argument throw spawn E2BIG; 131071 bytes exits 0. File-path trace-application-feature exits 0 with summary.matched_seeds 1.
  • Reduced stack — prlimit --stack=524288 makes ARG_MAX 131072. Payload 130532 exits 0; 130533 throws E2BIG. vitest run tests/boundary/process/spawnArgumentLimit.test.ts --project process-boundary under that limit: 4 passed.
  • npm run test:focused -- tests/boundary/process/spawnArgumentLimit.test.ts tests/acceptance/applications/electronIpcListenerCallsiteCli.test.ts — 6 passed (CLI and stdio MCP acceptance, plus the four limit cases).
  • tsc --noEmit — exit 0.
  • oxfmt --check . — clean.
  • oxlint on the touched files — clean.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: Linux spawn ceiling measured on this host (4 KiB pages), including a 512 KiB stack. No Electron binary, Hopper, or Ghidra. The listener fixture is static source analysis.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: test processes only. The regression uses PATH and, on Windows, the same temp roots as the CLI fixture.

Author readiness

Human owner: @morluto

  • 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.
Open in Web Open in Cursor 

🔄 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/5673 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/20/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/fix-ipc-trace-e2big-a55b` --- ### 📝 Commits (4) - [`4a31a01`](https://github.com/morluto/rea/commit/4a31a01e452f5b0c3b9036a6cd54ae81486eb668) test(cli): keep IPC trace input under the Linux spawn limit - [`7bfc2a5`](https://github.com/morluto/rea/commit/7bfc2a5ebf41e4b846715edbba9d291950222dd9) Merge remote-tracking branch 'origin/main' into cursor/fix-ipc-trace-e2big-a55b - [`e975bcb`](https://github.com/morluto/rea/commit/e975bcb72b1e73dc8cdaca5b550a177ce6155852) test(process): size the spawn ceiling from ARG_MAX and MAX_ARG_STRLEN - [`05f4b93`](https://github.com/morluto/rea/commit/05f4b93e1653a6889e34a6ac4c7c1baecb85ef20) style(test): format files rejected by oxfmt in static checks ### 📊 Changes **5 files changed** (+273 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `tests/acceptance/applications/electronIpcListenerCallsiteCli.test.ts` (+20 -4) ➕ `tests/boundary/process/spawnArgumentLimit.test.ts` (+181 -0) 📝 `tests/composition/reverseEngineeringAdmission.test.ts` (+4 -4) 📝 `tests/support/cli/cliFixture.ts` (+2 -3) ➕ `tests/support/process/spawnArgumentLimit.ts` (+66 -0) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary `electronIpcListenerCallsiteCli` dies on GitHub Actions with `spawn E2BIG` while starting `trace-application-feature`. The trace request is one argv string of the full application Evidence document (~292 KiB). Linux rejects a single argv or env string at `MAX_ARG_STRLEN` (32 pages, 131071 bytes on the 4 KiB Actions runners) before the process starts. The CLI already reads that JSON from a file. This keeps the file path, requires the spawned argv to fit the per-string ceiling, and locks both that ceiling and the aggregate `ARG_MAX` budget with a process-registry regression that does not need Electron. Human owner: @morluto Cited failures, both on the inline-JSON revision: - main `1629266e3` run https://github.com/morluto/rea/actions/runs/39471426969 (shard 2/5) - #5652 `c70984e55` run https://github.com/morluto/rea/actions/runs/39475793479 (shard 2/8) Both stacks are `processFixture` spawn ← `cliFixture.run` ← the CLI case at the trace invocation. The earlier `analyze-javascript-application` spawn uses the same minimal environment and succeeds, so this is the argument string, not inherited env or `NODE_OPTIONS`. ## Problem and expected behavior `createTestCli` spawns `node scripts/rea.mjs` with `PATH` only (plus the Windows temp roots). Placing `JSON.stringify({ application, seed, direction })` in argv makes one argument of 292118 bytes for this fixture. On this host `getconf PAGE_SIZE` is 4096 and `getconf ARG_MAX` is 2097152. A 131071-byte argument exits 0; 131072 bytes throws `spawn E2BIG` synchronously. With `RLIMIT_STACK` of 512 KiB, `ARG_MAX` drops to 131072 and a payload at the single-string ceiling still fails because the filename, other argv, environment, NULs, and pointer table consume the rest. The trace command must still count the exposed `pong` listener callsites and return `matched_seeds: 1`. ## Change and scope The acceptance CLI case writes the trace request to `trace-input.json` and passes that path. It requires the serialized document to stay past the 4 KiB-page ceiling and the actual argv to fit under it, so putting the document back on argv fails on every host. `acceptedSpawnPayloadBytes` takes the minimum of the per-string ceiling and the bytes left in `ARG_MAX` after the filename (copied before argv), the other argv strings, each `KEY=value` environment string, their NULs, and one native pointer per argv and env string. The registry test spawns that derived size. When the fixed image already fills `ARG_MAX`, it skips the success spawn. One byte past the per-string ceiling, and one byte past a tighter aggregate budget, must throw `E2BIG`. `check:ci:fast` failed `oxfmt --check` on `tests/support/cli/cliFixture.ts` and, on the merge with main, `tests/composition/reverseEngineeringAdmission.test.ts`. Those two files are formatted and nothing else. Contribution scope: not applicable. Test-only. No new provider, target execution, injection, mutation, or protection recovery. Intentionally left alone: production CLI parsing, Evidence size, and a harness-wide argv guard in `createTestCli` (other tests pass intentional inline JSON). ## Contract and boundary impact - Semantic owner and earliest changed stage: test process spawn. The failure is `execve` of the compiled CLI, before command dispatch. - Contribution scope fit and linked maintainer decision: ordinary test fix within the existing CLI JSON file input. Maintainer scope decision not applicable. - CLI and MCP/tool-catalog contract: none. `parseCliJsonInput` already reads a path when the argument is not JSON. - Provider, bridge, target-format, or platform compatibility: Linux single-argument limit and aggregate `ARG_MAX`. The shared budget is the 4 KiB-page ceiling Actions uses. Larger page sizes still check `32 * pageSize - 1`. The kernel spawn case is skipped off Linux. Pointer width is 4 bytes for arm, ia32, mips, and mipsel, and 8 otherwise. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [ ] Read existing files or captured data. - [x] 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 - Tests added or updated: `tests/acceptance/applications/electronIpcListenerCallsiteCli.test.ts`, `tests/boundary/process/spawnArgumentLimit.test.ts`, `tests/support/process/spawnArgumentLimit.ts`. Format-only: `tests/support/cli/cliFixture.ts`, `tests/composition/reverseEngineeringAdmission.test.ts`. - Base reproduction: on Linux Node v24.18.0, the fixture trace argument is 292118 bytes and `spawn` throws `E2BIG`. Length 131071 exits 0; length 131072 throws `E2BIG`. The same document passed as a file path exits 0 with `matched_seeds: 1`. Re-introducing that string as an argv element fails `assertSpawnArgumentsWithinLimit` before spawn. - Aggregate headroom: under `prlimit --stack=524288`, `getconf ARG_MAX` is 131072. The derived payload (130532 bytes for this image) exits 0 and one more byte throws `E2BIG`. The same vitest file passes under that stack limit. - Static check: job https://github.com/morluto/rea/actions/runs/39490671462/job/118863805852 failed in `npm run check:ci:fast` because `oxfmt --check .` reported those two files. `format:check` is clean after the format commit. - User-visible CLI/MCP output (if applicable): none. - Remaining proof gaps: the updated tree has not yet finished a new GitHub Actions run. 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 - Direct spawn probe — 292118-byte trace argument and a 131072-byte argument throw `spawn E2BIG`; 131071 bytes exits 0. File-path `trace-application-feature` exits 0 with `summary.matched_seeds` 1. - Reduced stack — `prlimit --stack=524288` makes `ARG_MAX` 131072. Payload 130532 exits 0; 130533 throws `E2BIG`. `vitest run tests/boundary/process/spawnArgumentLimit.test.ts --project process-boundary` under that limit: 4 passed. - `npm run test:focused -- tests/boundary/process/spawnArgumentLimit.test.ts tests/acceptance/applications/electronIpcListenerCallsiteCli.test.ts` — 6 passed (CLI and stdio MCP acceptance, plus the four limit cases). - `tsc --noEmit` — exit 0. - `oxfmt --check .` — clean. - `oxlint` on the touched files — clean. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: Linux spawn ceiling measured on this host (4 KiB pages), including a 512 KiB stack. No Electron binary, Hopper, or Ghidra. The listener fixture is static source analysis. - Package or release metadata impact: none. - Security, privacy, process, or containment review: test processes only. The regression uses `PATH` and, on Windows, the same temp roots as the CLI fixture. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @morluto - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-bf2fc701-3414-56a2-950e-4c2e0f3ea55b?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-bf2fc701-3414-56a2-950e-4c2e0f3ea55b&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:44:49 +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#7028
No description provided.