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 #6088] [MERGED] fix(engines): keep format ceilings fixed and recover the EVMole deadline #7144

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

📋 Pull Request Information

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

Base: main ← Head: cursor/engines-evmole-deadline-858c

📝 Commits (2)

  • d132ea7 fix(engines): keep format ceilings fixed and recover the EVMole deadline
  • 5e6052e fix(engines): recover the allowance that refused the request

📊 Changes

34 files changed (+851 additions, -106 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/SKILL.md (+3 -1)
📝 docs/evm-bytecode.md (+5 -1)
📝 src/application/evm/EvmInterfaceEvidence.ts (+7 -1)
📝 src/application/evm/EvmInterfaceService.test.ts (+38 -0)
📝 src/cli/evmCommands.ts (+8 -1)
📝 src/contracts/evm/evmToolContracts.ts (+1 -1)
📝 src/domain/evm/evmInterface.ts (+13 -0)
📝 src/domain/native/nativeAotPe.budget.test.ts (+33 -0)
📝 src/domain/native/nativeAotPe.ts (+49 -24)
📝 src/evm/EvmWorkerLimits.ts (+2 -2)
📝 src/evm/EvmoleFailures.test.ts (+63 -0)
📝 src/evm/EvmoleFailures.ts (+54 -16)
📝 src/evm/EvmoleInterfaceProvider.ts (+22 -4)
📝 src/evm/EvmoleRelease.ts (+5 -1)
📝 src/firmware/FirmwareCommand.test.ts (+80 -1)
📝 src/firmware/FirmwareCommand.ts (+54 -14)
📝 src/firmware/FirmwareDeadline.test.ts (+67 -0)
📝 src/firmware/FirmwareFailures.ts (+65 -3)
📝 src/firmware/FirmwareFiles.ts (+6 -3)
📝 src/go/GoBinaryProvider.ts (+1 -2)

...and 14 more files

📄 Description

Summary

Refs #5910 (parent #5808). When an EVMole worker deadline or a fixed format/runtime ceiling in this theme is hit, recovery names the budget, whether it can change, and what a related setting does not raise.

The owned EVMole worker wall clock is now timeout_ms (default 30000 ms, integer 1..2147483647) on inspect_evm_interface and --timeout-ms on rea inspect-evm-interface. Omission keeps 30000 ms and is omitted from Evidence. It applies on the next call and does not raise the fixed 4 MiB input, 16 MiB reply, 1 MiB diagnostic, 3 GiB address-space, or 30-second CPU ceilings.

Firmware already has analysis_timeout_ms. This PR does not add a second firmware analysis knob. CPU (cpuSeconds 120), file-size, diagnostic, report, and input refusals say analysis_timeout_ms does not raise them. Extract staging file size remains the caller-selected max_output_bytes. Address-space exhaustion has no dedicated signal; unclassified tool failures name the fixed address-space and CPU allowances without treating a format failure as a resource limit.

Review follow-up: model capacity recovery uses a structured limit (header-bytes, report-bytes, representation-bytes, exact-offset, metadata-nesting) instead of message text. The 100,000,000-byte header ceiling is shared by GGUF and Safetensors. Firmware SIGXCPU and SIGXFSZ errors keep captured stdout, stderr, byte counts, and the exit signal. An oversized firmware report no longer says both to rerun and that the same request fails. NativeAOT hydration work or memory exhaustion explains the fixed parser allowance on the partial report.

Problem and expected behavior

A 30000 ms EVMole worker deadline was a fixed owned-command wall clock. A longer wall clock can still expire from scheduling or I/O while CPU stays under 30 seconds, so the deadline is the same class of setting as WABT command_timeout_ms and SQLite worker_timeout_ms. Recovery did not name it.

Firmware CPU and byte failures did not say that raising analysis_timeout_ms leaves those allowances unchanged. Several agent-visible format and runtime ceilings in this theme were silent about having no runtime override. The shared model header ceiling is 100,000,000 bytes for both GGUF and Safetensors.

Change and scope

Promotion is limited to that EVMole wall clock. Sibling byte, address-space, and CPU caps stay fixed, and recovery says timeout_ms does not raise them.

Wording-only, and only where the refusal was agent-visible and did not already name a control or fixed allowance: firmware CPU/file-size/diagnostic/report/input, WABT input/output/tool bytes, SQLite diagnostic capture, concurrent inspection slots, and combined snapshot input, Go input bytes, GPU object/report allowances, PE hard input and directory ceilings (caller-selected max_file_bytes / max_entries branches still say to raise those settings), NativeAOT snapshot and parser budgets, and the model header, report, representation, exact-offset, and nesting allowances. SQLite worker_timeout_ms and WABT command_timeout_ms recovery are unchanged. SQLITE_ROW_LIMIT_DEFAULT stays overridable through row_limit.

Out of scope: ASAR streaming and hdiutil (#5910 PR 9), and the already-open MCP (#6005), provider (#6014), JavaScript (#6022), Android (#6024), browser (#6036), native (#6059), and swiftc (#6071) limit PRs. No global settings tool, no retry_after_ms, and no numeric increases.

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: domain inspect_evm_interface owns timeout_ms; the EVMole adapter applies it as the owned worker command deadline. Model capacity failures own their limit kind at ModelFormatFailure. Firmware signal errors own captured command output. NativeAOT hydration owns parser-budget explanation on the partial report. Firmware and the other engines keep their existing owners.
  • Contribution scope fit and linked maintainer decision: not applicable. Recovery and one existing deadline inside current read-only operations. No new provider and no target execution, injection, mutation, or protection recovery.
  • CLI and MCP/tool-catalog contract: inspect_evm_interface accepts optional timeout_ms; CLI flag --timeout-ms. Omission keeps 30000 ms. Other tool inputs are unchanged. Catalogs and skills/ stay generated; the authored skill text was updated.
  • Provider, bridge, target-format, or platform compatibility: EVMole 0.9.3 worker behavior is unchanged aside from the caller-selected wall clock. Fixed ceilings are unchanged. A tighter inherited Linux soft limit can still apply.
  • Evidence, artifact, provenance, or reconstruction contract: Evidence parameters record a selected timeout_ms and omit it when the caller omits it. Result identity is otherwise unchanged. Firmware resource errors retain captured tool output.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged. The worker still runs under the existing prlimit/CPU/byte ceilings.
  • 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): authored skill and docs/evm-bytecode.md updated. No package or installer change.

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: model recovery by limit kind, including GGUF header, exact-offset, and nesting refusals; firmware signal captured output, including a fixture SIGXCPU through runFirmwareCommand; oversized firmware report recovery; NativeAOT hydration work-budget text on the partial report.
  • Base reproduction or other evidence: source inspection of the fixed 30000 ms runOwnedCommand deadline versus the separate 30-second CPU ceiling. Firmware analysis_timeout_ms was already on main (default 120000, range 1..2147483647).
  • User-visible CLI/MCP output (if applicable): a worker timeout names timeout_ms, the effective milliseconds, the 30000 ms default when omitted, --timeout-ms, the maximum 2147483647, and the fixed caps it does not raise. No live CLI transcript was captured.
  • Remaining proof gaps: no live EVMole, binwalk, or unblob run. The firmware SIGXCPU path used a fixture process, not a live prlimit. Address-space death has no dedicated signal. The earlier EVMole, WABT, SQLite, and PE suite was not re-run on this revision.

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

  • npm run check:fast — passed (typecheck and lint, 2/2 tasks).
  • npx oxfmt --check on the touched files — passed.
  • npm run test:local -- src/firmware/FirmwareDeadline.test.ts src/firmware/FirmwareCommand.test.ts src/domain/native/nativeAotPe.budget.test.ts src/domain/native/nativeAotPe.test.ts — 38 passed.
  • npm run test:local -- src/domain/native/nativeAotPe.headerRanges.test.ts src/domain/native/nativeAotPe.sectionRanges.test.ts src/domain/native/nativeAotPe.budget.test.ts — 28 passed.
  • npm run test:focused -- tests/boundary/model/modelArtifact.test.ts tests/boundary/firmware/firmwareReportFiles.test.ts — firmware report 11 passed; model artifact 71 passed after the nesting fixture fix.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. timeout_ms is optional. Omitting it keeps the previous 30000 ms deadline. Fixed numeric ceilings are unchanged.
  • Real Hopper/Ghidra, browser, or OS coverage: not run. NativeAOT wording is on the parser partial report. Linux prlimit integration for a live SIGXCPU was not executed here.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the worker still uses the existing address-space, file-size, and CPU ceilings. A longer timeout_ms does not raise them. No new network or mutation authority.

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/6088 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/engines-evmole-deadline-858c` --- ### 📝 Commits (2) - [`d132ea7`](https://github.com/morluto/rea/commit/d132ea78190a0261c4d156cb626c5025391d53b1) fix(engines): keep format ceilings fixed and recover the EVMole deadline - [`5e6052e`](https://github.com/morluto/rea/commit/5e6052e5e40ec1ea049cf0836cd593de0af7270d) fix(engines): recover the allowance that refused the request ### 📊 Changes **34 files changed** (+851 additions, -106 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/SKILL.md` (+3 -1) 📝 `docs/evm-bytecode.md` (+5 -1) 📝 `src/application/evm/EvmInterfaceEvidence.ts` (+7 -1) 📝 `src/application/evm/EvmInterfaceService.test.ts` (+38 -0) 📝 `src/cli/evmCommands.ts` (+8 -1) 📝 `src/contracts/evm/evmToolContracts.ts` (+1 -1) 📝 `src/domain/evm/evmInterface.ts` (+13 -0) 📝 `src/domain/native/nativeAotPe.budget.test.ts` (+33 -0) 📝 `src/domain/native/nativeAotPe.ts` (+49 -24) 📝 `src/evm/EvmWorkerLimits.ts` (+2 -2) 📝 `src/evm/EvmoleFailures.test.ts` (+63 -0) 📝 `src/evm/EvmoleFailures.ts` (+54 -16) 📝 `src/evm/EvmoleInterfaceProvider.ts` (+22 -4) 📝 `src/evm/EvmoleRelease.ts` (+5 -1) 📝 `src/firmware/FirmwareCommand.test.ts` (+80 -1) 📝 `src/firmware/FirmwareCommand.ts` (+54 -14) 📝 `src/firmware/FirmwareDeadline.test.ts` (+67 -0) 📝 `src/firmware/FirmwareFailures.ts` (+65 -3) 📝 `src/firmware/FirmwareFiles.ts` (+6 -3) 📝 `src/go/GoBinaryProvider.ts` (+1 -2) _...and 14 more files_ </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Refs #5910 (parent #5808). When an EVMole worker deadline or a fixed format/runtime ceiling in this theme is hit, recovery names the budget, whether it can change, and what a related setting does not raise. The owned EVMole worker wall clock is now `timeout_ms` (default 30000 ms, integer 1..2147483647) on `inspect_evm_interface` and `--timeout-ms` on `rea inspect-evm-interface`. Omission keeps 30000 ms and is omitted from Evidence. It applies on the next call and does not raise the fixed 4 MiB input, 16 MiB reply, 1 MiB diagnostic, 3 GiB address-space, or 30-second CPU ceilings. Firmware already has `analysis_timeout_ms`. This PR does not add a second firmware analysis knob. CPU (`cpuSeconds` 120), file-size, diagnostic, report, and input refusals say `analysis_timeout_ms` does not raise them. Extract staging file size remains the caller-selected `max_output_bytes`. Address-space exhaustion has no dedicated signal; unclassified tool failures name the fixed address-space and CPU allowances without treating a format failure as a resource limit. Review follow-up: model capacity recovery uses a structured limit (`header-bytes`, `report-bytes`, `representation-bytes`, `exact-offset`, `metadata-nesting`) instead of message text. The 100,000,000-byte header ceiling is shared by GGUF and Safetensors. Firmware `SIGXCPU` and `SIGXFSZ` errors keep captured stdout, stderr, byte counts, and the exit signal. An oversized firmware report no longer says both to rerun and that the same request fails. NativeAOT hydration work or memory exhaustion explains the fixed parser allowance on the partial report. ## Problem and expected behavior A 30000 ms EVMole worker deadline was a fixed owned-command wall clock. A longer wall clock can still expire from scheduling or I/O while CPU stays under 30 seconds, so the deadline is the same class of setting as WABT `command_timeout_ms` and SQLite `worker_timeout_ms`. Recovery did not name it. Firmware CPU and byte failures did not say that raising `analysis_timeout_ms` leaves those allowances unchanged. Several agent-visible format and runtime ceilings in this theme were silent about having no runtime override. The shared model header ceiling is 100,000,000 bytes for both GGUF and Safetensors. ## Change and scope Promotion is limited to that EVMole wall clock. Sibling byte, address-space, and CPU caps stay fixed, and recovery says `timeout_ms` does not raise them. Wording-only, and only where the refusal was agent-visible and did not already name a control or fixed allowance: firmware CPU/file-size/diagnostic/report/input, WABT input/output/tool bytes, SQLite diagnostic capture, concurrent inspection slots, and combined snapshot input, Go input bytes, GPU object/report allowances, PE hard input and directory ceilings (caller-selected `max_file_bytes` / `max_entries` branches still say to raise those settings), NativeAOT snapshot and parser budgets, and the model header, report, representation, exact-offset, and nesting allowances. SQLite `worker_timeout_ms` and WABT `command_timeout_ms` recovery are unchanged. `SQLITE_ROW_LIMIT_DEFAULT` stays overridable through `row_limit`. Out of scope: ASAR streaming and hdiutil (#5910 PR 9), and the already-open MCP (#6005), provider (#6014), JavaScript (#6022), Android (#6024), browser (#6036), native (#6059), and swiftc (#6071) limit PRs. No global settings tool, no `retry_after_ms`, and no numeric increases. 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: domain `inspect_evm_interface` owns `timeout_ms`; the EVMole adapter applies it as the owned worker command deadline. Model capacity failures own their limit kind at `ModelFormatFailure`. Firmware signal errors own captured command output. NativeAOT hydration owns parser-budget explanation on the partial report. Firmware and the other engines keep their existing owners. - Contribution scope fit and linked maintainer decision: not applicable. Recovery and one existing deadline inside current read-only operations. No new provider and no target execution, injection, mutation, or protection recovery. - CLI and MCP/tool-catalog contract: `inspect_evm_interface` accepts optional `timeout_ms`; CLI flag `--timeout-ms`. Omission keeps 30000 ms. Other tool inputs are unchanged. Catalogs and `skills/` stay generated; the authored skill text was updated. - Provider, bridge, target-format, or platform compatibility: EVMole 0.9.3 worker behavior is unchanged aside from the caller-selected wall clock. Fixed ceilings are unchanged. A tighter inherited Linux soft limit can still apply. - Evidence, artifact, provenance, or reconstruction contract: Evidence parameters record a selected `timeout_ms` and omit it when the caller omits it. Result identity is otherwise unchanged. Firmware resource errors retain captured tool output. - Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged. The worker still runs under the existing prlimit/CPU/byte ceilings. - 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): authored skill and `docs/evm-bytecode.md` updated. No package or installer change. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] 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: model recovery by limit kind, including GGUF header, exact-offset, and nesting refusals; firmware signal captured output, including a fixture `SIGXCPU` through `runFirmwareCommand`; oversized firmware report recovery; NativeAOT hydration work-budget text on the partial report. - Base reproduction or other evidence: source inspection of the fixed 30000 ms `runOwnedCommand` deadline versus the separate 30-second CPU ceiling. Firmware `analysis_timeout_ms` was already on main (default 120000, range 1..2147483647). - User-visible CLI/MCP output (if applicable): a worker timeout names `timeout_ms`, the effective milliseconds, the 30000 ms default when omitted, `--timeout-ms`, the maximum 2147483647, and the fixed caps it does not raise. No live CLI transcript was captured. - Remaining proof gaps: no live EVMole, binwalk, or unblob run. The firmware `SIGXCPU` path used a fixture process, not a live prlimit. Address-space death has no dedicated signal. The earlier EVMole, WABT, SQLite, and PE suite was not re-run on this revision. 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 - `npm run check:fast` — passed (typecheck and lint, 2/2 tasks). - `npx oxfmt --check` on the touched files — passed. - `npm run test:local -- src/firmware/FirmwareDeadline.test.ts src/firmware/FirmwareCommand.test.ts src/domain/native/nativeAotPe.budget.test.ts src/domain/native/nativeAotPe.test.ts` — 38 passed. - `npm run test:local -- src/domain/native/nativeAotPe.headerRanges.test.ts src/domain/native/nativeAotPe.sectionRanges.test.ts src/domain/native/nativeAotPe.budget.test.ts` — 28 passed. - `npm run test:focused -- tests/boundary/model/modelArtifact.test.ts tests/boundary/firmware/firmwareReportFiles.test.ts` — firmware report 11 passed; model artifact 71 passed after the nesting fixture fix. ## Compatibility, safety, and release - Breaking changes or migration steps: none. `timeout_ms` is optional. Omitting it keeps the previous 30000 ms deadline. Fixed numeric ceilings are unchanged. - Real Hopper/Ghidra, browser, or OS coverage: not run. NativeAOT wording is on the parser partial report. Linux prlimit integration for a live SIGXCPU was not executed here. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the worker still uses the existing address-space, file-size, and CPU ceilings. A longer `timeout_ms` does not raise them. No new network or mutation authority. ## 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 - [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-e087aadb-712b-5ef6-b90c-160d123b858c?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-e087aadb-712b-5ef6-b90c-160d123b858c&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:45:42 +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#7144
No description provided.