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 #6352] [MERGED] refactor(process): share paired prlimit ceiling ownership #7299

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

📋 Pull Request Information

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

Base: main ← Head: cursor/resource-limit-ownership-78f5

📝 Commits (3)

  • 5634d9f refactor(process): share paired prlimit ceiling ownership
  • 3909888 test(pcap): admit capture limits without host prlimit
  • 4b79c10 style(pcap): format the capture ceiling test

📊 Changes

12 files changed (+222 additions, -46 deletions)

View changed files

📝 scripts/verify/architecture-guards.mjs (+37 -11)
📝 src/firmware/FirmwareCommand.ts (+11 -7)
📝 src/firmware/FirmwareRelease.ts (+3 -1)
📝 src/javascript/recovery/WakaruCommand.test.ts (+47 -0)
📝 src/javascript/recovery/WakaruCommand.ts (+9 -6)
📝 src/javascript/recovery/WakaruRelease.ts (+4 -1)
➕ src/pcap/PcapNativeBound.test.ts (+66 -0)
📝 src/pcap/PcapNativeBound.ts (+13 -11)
📝 src/process/LinuxResourceLimits.test.ts (+9 -3)
📝 src/process/LinuxResourceLimits.ts (+11 -4)
📝 tests/boundary/firmware/firmwareIntegration.test.ts (+6 -1)
📝 tests/process-global/firmwarePublicationDeadline.test.ts (+6 -1)

📄 Description

Summary

Paired Linux prlimit ceilings now come from prlimitArgumentVector and prlimitCeilingArguments in src/process/LinuxResourceLimits.ts. Firmware, Wakaru, and pcap stop spelling those options inline. Byte and CPU budgets are unchanged.

The capture-ceiling test uses a temporary executable, so it does not require /usr/bin/prlimit.

Problem and expected behavior

Architecture guards already required one owner for paired soft and hard ceilings, but the census only matched the --core=0:0 spelling. Firmware and Wakaru passed a bare value (--cpu=120, --core=0). util-linux 2.39.3 treats a bare value as both soft and hard, the same as soft:hard when the numbers are equal. Pcap spelled the paired form itself, including 1024 ** 3 and 64 * 1024 ** 2 for the same 1 GiB and 64 MiB ceilings as BOUNDED_PRODUCER_LIMITS.

Those producers now call the shared owner. Enforced ceilings stay the same numbers.

Change and scope

  • prlimitArgumentVector is built from prlimitCeilingArguments, the command-less prefix. Pcap uses the prefix because PcapCommand appends the producer command. Its CPU ceiling stays 300 seconds.
  • Firmware and Wakaru call prlimitArgumentVector with their existing file-size and 120-second CPU budgets. Their 1 GiB address space is BOUNDED_PRODUCER_LIMITS.address_space_bytes.
  • The architecture guard now rejects a bare --core=0 and allowlists only the EVMole soft-only form (--core=0:), which leaves the inherited hard ceiling in place. EVMole budgets stay 3 GiB address space, 16 MiB file, and 30 CPU seconds. selectEvmWorkerLimits stays a separate selector because it returns Result, checks units, and rejects a soft limit above its hard limit.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/process/LinuxResourceLimits.ts owns paired prlimit options and the shared 1 GiB address-space and 64 MiB file ceilings. The change is at producer admission, before the owned command is spawned.
  • Contribution scope fit and linked maintainer decision: not applicable. This consolidates existing limiter arguments inside current provider boundaries. No new provider, target execution, injection, mutation, or protection recovery.
  • CLI and MCP/tool-catalog contract: none. Public budgets and tool descriptions are unchanged.
  • Provider, bridge, target-format, or platform compatibility: Firmware and Wakaru argv now uses explicit soft:hard (--cpu=120:120, --core=0:0) instead of a bare value. On util-linux 2.39.3 those forms set the same soft and hard numbers. Pcap's emitted vector is unchanged aside from taking it from the shared helper. EVMole stays soft-only.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. No target selection or cleanup change.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): 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: LinuxResourceLimits.test.ts locks the ceiling prefix. PcapNativeBound.test.ts locks the 1 GiB Windows job ceiling and the 300-second capture vector against a temporary executable. WakaruCommand.test.ts locks the shared vector. Firmware launch assertions expect the paired spelling.
  • Base reproduction or other evidence: On this host, prlimit from util-linux 2.39.3 set identical soft and hard rows for --cpu=5 --core=0 --as=1073741824 --fsize=4096 and the N:N form. --cpu=5: left the hard limits unlimited. That measurement is why firmware and Wakaru moved, and why EVMole did not.
  • User-visible CLI/MCP output (if applicable): none. Budgets reported to callers stay the same numbers.
  • Remaining proof gaps: real Binwalk, Unblob, Wakaru, and TShark runs were not executed. Equivalence is from prlimit itself plus unit and fixture launch assertions.

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

  • node scripts/verify/architecture-guards.mjs — passed across 1875 source files (on 5634d9fd).
  • npm run test:local -- src/process/LinuxResourceLimits.test.ts src/pcap/PcapNativeBound.test.ts src/javascript/recovery/WakaruCommand.test.ts — 3 files, 21 tests passed (on 5634d9fd).
  • npm run test:focused -- tests/boundary/firmware/firmwareIntegration.test.ts tests/process-global/firmwarePublicationDeadline.test.ts — 2 files, 57 tests passed (on 5634d9fd).
  • npm run test:local -- src/pcap/PcapNativeBound.test.ts — 2 tests passed after the temporary-executable change (39098883a).
  • npm run check:fast — typecheck and lint succeeded on 5634d9fd and again on 39098883a. check:fast does not run format:check.
  • npx oxfmt --check src/pcap/PcapNativeBound.test.ts — passed after formatting (4b79c104a).
  • npm run test:focused -- tests/boundary/filesystem/javascript-applications/javascriptArtifactReconstruction.test.ts — 44 tests passed locally, including the cancellation case that failed once in CI shard 4/8 on 39098883a.
  • prlimit 2.39.3 comparison of bare, N:N, and soft: forms — bare and N:N printed the same soft and hard rows; soft: left hard unlimited.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Numerical budgets are unchanged. The firmware and Wakaru limiter argv spelling is now explicit soft:hard.
  • Real Hopper/Ghidra, browser, or OS coverage: Linux prlimit 2.39.3 compared bare, paired, and soft-only forms. No Hopper, Ghidra, or browser coverage applies.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: containment ceilings are the same numbers. Pcap still uses 300 CPU seconds and no resident-input budget. EVMole still does not lower inherited hard ceilings.

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/6352 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/22/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/resource-limit-ownership-78f5` --- ### 📝 Commits (3) - [`5634d9f`](https://github.com/morluto/rea/commit/5634d9fdbf854ac2b2e7d43e66b5b01541b64429) refactor(process): share paired prlimit ceiling ownership - [`3909888`](https://github.com/morluto/rea/commit/39098883a75fb5052983085ce1a51eb31981a4f3) test(pcap): admit capture limits without host prlimit - [`4b79c10`](https://github.com/morluto/rea/commit/4b79c104a6967c0f85c4c751305e1fbcd0c4d387) style(pcap): format the capture ceiling test ### 📊 Changes **12 files changed** (+222 additions, -46 deletions) <details> <summary>View changed files</summary> 📝 `scripts/verify/architecture-guards.mjs` (+37 -11) 📝 `src/firmware/FirmwareCommand.ts` (+11 -7) 📝 `src/firmware/FirmwareRelease.ts` (+3 -1) 📝 `src/javascript/recovery/WakaruCommand.test.ts` (+47 -0) 📝 `src/javascript/recovery/WakaruCommand.ts` (+9 -6) 📝 `src/javascript/recovery/WakaruRelease.ts` (+4 -1) ➕ `src/pcap/PcapNativeBound.test.ts` (+66 -0) 📝 `src/pcap/PcapNativeBound.ts` (+13 -11) 📝 `src/process/LinuxResourceLimits.test.ts` (+9 -3) 📝 `src/process/LinuxResourceLimits.ts` (+11 -4) 📝 `tests/boundary/firmware/firmwareIntegration.test.ts` (+6 -1) 📝 `tests/process-global/firmwarePublicationDeadline.test.ts` (+6 -1) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Paired Linux `prlimit` ceilings now come from `prlimitArgumentVector` and `prlimitCeilingArguments` in `src/process/LinuxResourceLimits.ts`. Firmware, Wakaru, and pcap stop spelling those options inline. Byte and CPU budgets are unchanged. The capture-ceiling test uses a temporary executable, so it does not require `/usr/bin/prlimit`. ## Problem and expected behavior Architecture guards already required one owner for paired soft and hard ceilings, but the census only matched the `--core=0:0` spelling. Firmware and Wakaru passed a bare value (`--cpu=120`, `--core=0`). util-linux 2.39.3 treats a bare value as both soft and hard, the same as `soft:hard` when the numbers are equal. Pcap spelled the paired form itself, including `1024 ** 3` and `64 * 1024 ** 2` for the same 1 GiB and 64 MiB ceilings as `BOUNDED_PRODUCER_LIMITS`. Those producers now call the shared owner. Enforced ceilings stay the same numbers. ## Change and scope - `prlimitArgumentVector` is built from `prlimitCeilingArguments`, the command-less prefix. Pcap uses the prefix because `PcapCommand` appends the producer command. Its CPU ceiling stays 300 seconds. - Firmware and Wakaru call `prlimitArgumentVector` with their existing file-size and 120-second CPU budgets. Their 1 GiB address space is `BOUNDED_PRODUCER_LIMITS.address_space_bytes`. - The architecture guard now rejects a bare `--core=0` and allowlists only the EVMole soft-only form (`--core=0:`), which leaves the inherited hard ceiling in place. EVMole budgets stay 3 GiB address space, 16 MiB file, and 30 CPU seconds. `selectEvmWorkerLimits` stays a separate selector because it returns `Result`, checks units, and rejects a soft limit above its hard limit. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/process/LinuxResourceLimits.ts` owns paired prlimit options and the shared 1 GiB address-space and 64 MiB file ceilings. The change is at producer admission, before the owned command is spawned. - Contribution scope fit and linked maintainer decision: not applicable. This consolidates existing limiter arguments inside current provider boundaries. No new provider, target execution, injection, mutation, or protection recovery. - CLI and MCP/tool-catalog contract: none. Public budgets and tool descriptions are unchanged. - Provider, bridge, target-format, or platform compatibility: Firmware and Wakaru argv now uses explicit `soft:hard` (`--cpu=120:120`, `--core=0:0`) instead of a bare value. On util-linux 2.39.3 those forms set the same soft and hard numbers. Pcap's emitted vector is unchanged aside from taking it from the shared helper. EVMole stays soft-only. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. No target selection or cleanup change. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): 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: `LinuxResourceLimits.test.ts` locks the ceiling prefix. `PcapNativeBound.test.ts` locks the 1 GiB Windows job ceiling and the 300-second capture vector against a temporary executable. `WakaruCommand.test.ts` locks the shared vector. Firmware launch assertions expect the paired spelling. - Base reproduction or other evidence: On this host, `prlimit` from util-linux 2.39.3 set identical soft and hard rows for `--cpu=5 --core=0 --as=1073741824 --fsize=4096` and the `N:N` form. `--cpu=5:` left the hard limits unlimited. That measurement is why firmware and Wakaru moved, and why EVMole did not. - User-visible CLI/MCP output (if applicable): none. Budgets reported to callers stay the same numbers. - Remaining proof gaps: real Binwalk, Unblob, Wakaru, and TShark runs were not executed. Equivalence is from `prlimit` itself plus unit and fixture launch assertions. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `node scripts/verify/architecture-guards.mjs` — passed across 1875 source files (on `5634d9fd`). - `npm run test:local -- src/process/LinuxResourceLimits.test.ts src/pcap/PcapNativeBound.test.ts src/javascript/recovery/WakaruCommand.test.ts` — 3 files, 21 tests passed (on `5634d9fd`). - `npm run test:focused -- tests/boundary/firmware/firmwareIntegration.test.ts tests/process-global/firmwarePublicationDeadline.test.ts` — 2 files, 57 tests passed (on `5634d9fd`). - `npm run test:local -- src/pcap/PcapNativeBound.test.ts` — 2 tests passed after the temporary-executable change (`39098883a`). - `npm run check:fast` — typecheck and lint succeeded on `5634d9fd` and again on `39098883a`. `check:fast` does not run `format:check`. - `npx oxfmt --check src/pcap/PcapNativeBound.test.ts` — passed after formatting (`4b79c104a`). - `npm run test:focused -- tests/boundary/filesystem/javascript-applications/javascriptArtifactReconstruction.test.ts` — 44 tests passed locally, including the cancellation case that failed once in CI shard 4/8 on `39098883a`. - `prlimit` 2.39.3 comparison of bare, `N:N`, and `soft:` forms — bare and `N:N` printed the same soft and hard rows; `soft:` left hard unlimited. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Numerical budgets are unchanged. The firmware and Wakaru limiter argv spelling is now explicit `soft:hard`. - Real Hopper/Ghidra, browser, or OS coverage: Linux `prlimit` 2.39.3 compared bare, paired, and soft-only forms. No Hopper, Ghidra, or browser coverage applies. - Package or release metadata impact: none. - Security, privacy, process, or containment review: containment ceilings are the same numbers. Pcap still uses 300 CPU seconds and no resident-input budget. EVMole still does not lower inherited hard ceilings. ## Author 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 - [ ] 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. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-59c0458d-a519-5fbd-8ee7-be69fe8e78f5?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-59c0458d-a519-5fbd-8ee7-be69fe8e78f5&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:46:51 +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#7299
No description provided.