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 #7017] fix(discovery): advertise attached IDA navigation effects #7577

New issue
Open
opened 2026-11-03 13:38:50 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:38:50 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7017
Author: @dhruvac29
Created: 10/24/2026
Status: 🔄 Open

Base: main ← Head: fix/5829-ida-tool-effects

📝 Commits (10+)

  • 279c7fb fix(discovery): advertise attached IDA navigation effects
  • ef32dc2 fix(discovery): cover IDA provider effects across tools and workflows
  • d9035ee test(discovery): isolate IDA metadata from host tool probes
  • f5de206 test(discovery): compare live identity with session effect bases
  • 38c53d7 fix(discovery): audit complete IDA provider effect union
  • 2497500 fix(discovery): exclude unreachable provider workflow effects
  • 3cbf3ce Merge origin/main into fix/5829-ida-tool-effects
  • 197388a fix(discovery): propagate IDA effects through composed tools
  • f6f5047 Merge origin/main into fix/5829-ida-tool-effects
  • b61201f fix(artifacts): deduplicate keyed archive path diagnostics

📊 Changes

9 files changed (+644 additions, -58 deletions)

View changed files

📝 src/application/AnalysisContextQueries.ts (+10 -7)
📝 src/application/CapabilityInventory.ts (+48 -11)
📝 src/contracts/toolEffects.test.ts (+61 -0)
📝 src/contracts/toolEffects.ts (+105 -32)
➕ tests/boundary/mcp/idaToolEffects.test.ts (+162 -0)
📝 tests/boundary/mcp/serverIdentity.test.ts (+11 -5)
📝 tests/boundary/mcp/toolSchemaValidity.test.ts (+1 -1)
📝 tests/boundary/providers/ida/idaCapabilityInventory.test.ts (+240 -1)
📝 website/wrangler.toml (+6 -1)

📄 Description

Summary

Fixes #5829. tools/list now advertises possible IDA UI, network, process, and filesystem effects, while binary_session reports effects composed from the selected provider. The affected attached IDA navigation tools no longer present openWorldHint: false when their supported IDA route may access the network.

Problem and expected behavior

With the recording producer in an attached legacy IDA session, binary_session reported UI and network effects for procedure_pseudo_code, procedure_assembly, read_function_instructions, and analyze_function; the canonical tool audit omitted them. A caller reading SDK discovery before invocation therefore received contradictory side-effect metadata. Composed workflows and ordinary IDA operations had similar possible-network omissions.

Change and scope

  • toolEffects.ts keeps each affected tool's provider-neutral session base with conservative global additions for supported IDA routes. toolSessionEffects derives the base from that entry; the separate navigation override list is removed.
  • CapabilityInventory.ts composes the session base with selected-provider descriptors. Requirement groups prevent unreachable workflow steps from lending effects. AnalysisContextQueries.ts shares the address-context facet list used by this composition and retains current cancellation handling.
  • Source, provider-boundary, and MCP tests cover global versus selected-provider effects, attached/native/headless distinctions, direct and composed workflows, and the four reported operations through the recording producer.
  • Lifecycle cleanup can call IDA's configured MCP transport while opening another target, opening bundle resources, closing a binary, or resetting the investigation. The canonical audit now includes network access for those four tools, even when cleanup belongs to a prior provider.

This is an ordinary discovery-metadata fix within existing provider boundaries. It adds no target authority or IDA execution path; a maintainer scope decision is not applicable. The branch is merged with main at b912ec184. The diff contains eight discovery and regression-test files plus a formatting-only fix to website/wrangler.toml, whose new main version failed the repository formatter in merged CI.

Contract and boundary impact

  • Semantic owner and earliest changed stage: canonical effects in src/contracts/toolEffects.ts; session composition in src/application/CapabilityInventory.ts.
  • Contribution scope fit and linked maintainer decision: ordinary fix; not applicable.
  • CLI and MCP/tool-catalog contract: no schema change. SDK openWorldHint derives from conservative possible effects; binary_session retains selected-provider facts.
  • Provider, bridge, target-format, or platform compatibility: attached legacy IDA exposes UI on the four navigation operations; native attached and headless profiles retain their profile-specific UI/process behavior. IDA transport may access the network.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged.
  • Target selection, authority, upstream behavior, and cleanup execution: unchanged; only the advertised effects of existing cleanup paths changed.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • 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: src/contracts/toolEffects.test.ts, tests/boundary/providers/ida/idaCapabilityInventory.test.ts, tests/boundary/mcp/idaToolEffects.test.ts, tests/boundary/mcp/serverIdentity.test.ts, and tests/boundary/mcp/toolSchemaValidity.test.ts.
  • Base evidence: the issue's executed reproduction recorded false UI/network tool effects and openWorldHint: false for the four attached operations. I did not rerun the base revision. The new MCP assertions would fail against that base audit.
  • User-visible MCP output: the production server with a recording IDA producer returned provider may_show_ui: true, tool changesUiState: true, provider may_access_network: true, tool accessesNetwork: true, and tools/list openWorldHint: true for all four operations.
  • Relevant boundary coverage: SDK tools/list and binary_session on the same recording session, direct calls, selected-provider capabilities, composed workflow effects, and lifecycle cleanup metadata. No lifecycle execution behavior changed.
  • Remaining proof gap: no real IDA engine, GUI movement, or network traffic was observed. The tests establish discovery metadata, not real-provider behavior.

The existing Evidence contract is unchanged; tests preserve unavailable and profile-specific effects rather than inferring them from a global audit.

Validation performed

  • npm run test:local -- src/contracts/toolEffects.test.ts src/application/CapabilityInventory.test.ts src/application/AnalysisContextQueries.test.ts src/application/javascript/JavaScriptArtifactGraphStructure.test.ts — 105 passed on the final merged tree.
  • npm run test:focused -- tests/boundary/providers/ida/idaCapabilityInventory.test.ts tests/boundary/mcp/idaToolEffects.test.ts tests/boundary/mcp/serverIdentity.test.ts — 22 passed on the final merged tree.
  • npm run test:focused -- src/contracts/toolEffects.test.ts tests/boundary/providers/ida/idaCapabilityInventory.test.ts tests/boundary/mcp/idaToolEffects.test.ts — 22 passed after the lifecycle audit fix.
  • npm run test:focused -- tests/boundary/mcp/toolSchemaValidity.test.ts — 16 passed after aligning its close_binary authority hint with the lifecycle audit.
  • npm run test:focused -- src/contracts/toolEffects.test.ts tests/boundary/providers/ida/idaCapabilityInventory.test.ts tests/boundary/mcp/idaToolEffects.test.ts tests/boundary/mcp/toolSchemaValidity.test.ts — 38 passed after merging current main.
  • npm run test:focused -- tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts — 10 passed after removing the superseded JavaScript change from the final diff.
  • Seven additional boundary fixture files passed 35 tests during conflict resolution; their files were retained from current main.
  • npm run check:ci:fast — typecheck, lint, module-boundary verification, and repository-wide formatting passed after the lifecycle audit fix.
  • git diff --check origin/main...HEAD — passed.
  • GitHub CI on edd11d036 found one stale close_binary hint assertion in shard 7; shards 1, 5, and 6 were canceled after that failure. The assertion is fixed in d14295e84, and full CI on this current head is pending.
  • GitHub CI on d14295e84 found website/wrangler.toml unformatted in the newly merged main. The one-line list is formatted in a113717c4; npm run check:ci:fast passed locally on the merged tree. Full CI on the current head passed, including all eight test shards, source tests, static checks, and website checks.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; this corrects advertised possible effects without changing calls or configuration.
  • Real provider coverage: recording IDA producer only; no IDA engine or GUI.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no additional authority. The advertised network and UI effects already exist in the IDA provider descriptors.

Author readiness

Human owner: @dhruvac29

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

Before merge

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

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

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7017 **Author:** [@dhruvac29](https://github.com/dhruvac29) **Created:** 10/24/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/5829-ida-tool-effects` --- ### 📝 Commits (10+) - [`279c7fb`](https://github.com/morluto/rea/commit/279c7fba4c342bc2d7de1b9f7cd1de820a8f4eb9) fix(discovery): advertise attached IDA navigation effects - [`ef32dc2`](https://github.com/morluto/rea/commit/ef32dc2be8f0d615edd7b5d680b9b3f6908f851a) fix(discovery): cover IDA provider effects across tools and workflows - [`d9035ee`](https://github.com/morluto/rea/commit/d9035eec99212d6ed24f7d21f5732820b3c7f1b5) test(discovery): isolate IDA metadata from host tool probes - [`f5de206`](https://github.com/morluto/rea/commit/f5de2061893e5b4f8cecd97864cd45a456abf997) test(discovery): compare live identity with session effect bases - [`38c53d7`](https://github.com/morluto/rea/commit/38c53d74bedc221499394f86eac6ceb0e963d80d) fix(discovery): audit complete IDA provider effect union - [`2497500`](https://github.com/morluto/rea/commit/2497500ddfc8726fb035d445790854a190f19e18) fix(discovery): exclude unreachable provider workflow effects - [`3cbf3ce`](https://github.com/morluto/rea/commit/3cbf3ce4f7d973f519d6d81d6eb58c49d04f0216) Merge origin/main into fix/5829-ida-tool-effects - [`197388a`](https://github.com/morluto/rea/commit/197388adc5c41e453e6e41263776e05152858c79) fix(discovery): propagate IDA effects through composed tools - [`f6f5047`](https://github.com/morluto/rea/commit/f6f50475daefd724430a51126e45851171cd2335) Merge origin/main into fix/5829-ida-tool-effects - [`b61201f`](https://github.com/morluto/rea/commit/b61201f3c39905934ce7d94244e9c773a466a510) fix(artifacts): deduplicate keyed archive path diagnostics ### 📊 Changes **9 files changed** (+644 additions, -58 deletions) <details> <summary>View changed files</summary> 📝 `src/application/AnalysisContextQueries.ts` (+10 -7) 📝 `src/application/CapabilityInventory.ts` (+48 -11) 📝 `src/contracts/toolEffects.test.ts` (+61 -0) 📝 `src/contracts/toolEffects.ts` (+105 -32) ➕ `tests/boundary/mcp/idaToolEffects.test.ts` (+162 -0) 📝 `tests/boundary/mcp/serverIdentity.test.ts` (+11 -5) 📝 `tests/boundary/mcp/toolSchemaValidity.test.ts` (+1 -1) 📝 `tests/boundary/providers/ida/idaCapabilityInventory.test.ts` (+240 -1) 📝 `website/wrangler.toml` (+6 -1) </details> ### 📄 Description ## Summary Fixes #5829. `tools/list` now advertises possible IDA UI, network, process, and filesystem effects, while `binary_session` reports effects composed from the selected provider. The affected attached IDA navigation tools no longer present `openWorldHint: false` when their supported IDA route may access the network. ## Problem and expected behavior With the recording producer in an attached legacy IDA session, `binary_session` reported UI and network effects for `procedure_pseudo_code`, `procedure_assembly`, `read_function_instructions`, and `analyze_function`; the canonical tool audit omitted them. A caller reading SDK discovery before invocation therefore received contradictory side-effect metadata. Composed workflows and ordinary IDA operations had similar possible-network omissions. ## Change and scope - `toolEffects.ts` keeps each affected tool's provider-neutral session base with conservative global additions for supported IDA routes. `toolSessionEffects` derives the base from that entry; the separate navigation override list is removed. - `CapabilityInventory.ts` composes the session base with selected-provider descriptors. Requirement groups prevent unreachable workflow steps from lending effects. `AnalysisContextQueries.ts` shares the address-context facet list used by this composition and retains current cancellation handling. - Source, provider-boundary, and MCP tests cover global versus selected-provider effects, attached/native/headless distinctions, direct and composed workflows, and the four reported operations through the recording producer. - Lifecycle cleanup can call IDA's configured MCP transport while opening another target, opening bundle resources, closing a binary, or resetting the investigation. The canonical audit now includes network access for those four tools, even when cleanup belongs to a prior provider. This is an ordinary discovery-metadata fix within existing provider boundaries. It adds no target authority or IDA execution path; a maintainer scope decision is not applicable. The branch is merged with `main` at `b912ec184`. The diff contains eight discovery and regression-test files plus a formatting-only fix to `website/wrangler.toml`, whose new `main` version failed the repository formatter in merged CI. ## Contract and boundary impact - Semantic owner and earliest changed stage: canonical effects in `src/contracts/toolEffects.ts`; session composition in `src/application/CapabilityInventory.ts`. - Contribution scope fit and linked maintainer decision: ordinary fix; not applicable. - CLI and MCP/tool-catalog contract: no schema change. SDK `openWorldHint` derives from conservative possible effects; `binary_session` retains selected-provider facts. - Provider, bridge, target-format, or platform compatibility: attached legacy IDA exposes UI on the four navigation operations; native attached and headless profiles retain their profile-specific UI/process behavior. IDA transport may access the network. - Evidence, artifact, provenance, or reconstruction contract: unchanged. - Target selection, authority, upstream behavior, and cleanup execution: unchanged; only the advertised effects of existing cleanup paths changed. - Generated metadata, package, or installation impact: none. Expected effects: - [x] 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: `src/contracts/toolEffects.test.ts`, `tests/boundary/providers/ida/idaCapabilityInventory.test.ts`, `tests/boundary/mcp/idaToolEffects.test.ts`, `tests/boundary/mcp/serverIdentity.test.ts`, and `tests/boundary/mcp/toolSchemaValidity.test.ts`. - Base evidence: the issue's executed reproduction recorded false UI/network tool effects and `openWorldHint: false` for the four attached operations. I did not rerun the base revision. The new MCP assertions would fail against that base audit. - User-visible MCP output: the production server with a recording IDA producer returned provider `may_show_ui: true`, tool `changesUiState: true`, provider `may_access_network: true`, tool `accessesNetwork: true`, and `tools/list` `openWorldHint: true` for all four operations. - Relevant boundary coverage: SDK `tools/list` and `binary_session` on the same recording session, direct calls, selected-provider capabilities, composed workflow effects, and lifecycle cleanup metadata. No lifecycle execution behavior changed. - Remaining proof gap: no real IDA engine, GUI movement, or network traffic was observed. The tests establish discovery metadata, not real-provider behavior. The existing Evidence contract is unchanged; tests preserve unavailable and profile-specific effects rather than inferring them from a global audit. ## Validation performed - `npm run test:local -- src/contracts/toolEffects.test.ts src/application/CapabilityInventory.test.ts src/application/AnalysisContextQueries.test.ts src/application/javascript/JavaScriptArtifactGraphStructure.test.ts` — 105 passed on the final merged tree. - `npm run test:focused -- tests/boundary/providers/ida/idaCapabilityInventory.test.ts tests/boundary/mcp/idaToolEffects.test.ts tests/boundary/mcp/serverIdentity.test.ts` — 22 passed on the final merged tree. - `npm run test:focused -- src/contracts/toolEffects.test.ts tests/boundary/providers/ida/idaCapabilityInventory.test.ts tests/boundary/mcp/idaToolEffects.test.ts` — 22 passed after the lifecycle audit fix. - `npm run test:focused -- tests/boundary/mcp/toolSchemaValidity.test.ts` — 16 passed after aligning its `close_binary` authority hint with the lifecycle audit. - `npm run test:focused -- src/contracts/toolEffects.test.ts tests/boundary/providers/ida/idaCapabilityInventory.test.ts tests/boundary/mcp/idaToolEffects.test.ts tests/boundary/mcp/toolSchemaValidity.test.ts` — 38 passed after merging current `main`. - `npm run test:focused -- tests/boundary/filesystem/javascript-applications/electronApplicationAnalysis.test.ts` — 10 passed after removing the superseded JavaScript change from the final diff. - Seven additional boundary fixture files passed 35 tests during conflict resolution; their files were retained from current `main`. - `npm run check:ci:fast` — typecheck, lint, module-boundary verification, and repository-wide formatting passed after the lifecycle audit fix. - `git diff --check origin/main...HEAD` — passed. - GitHub CI on `edd11d036` found one stale `close_binary` hint assertion in shard 7; shards 1, 5, and 6 were canceled after that failure. The assertion is fixed in `d14295e84`, and full CI on this current head is pending. - GitHub CI on `d14295e84` found `website/wrangler.toml` unformatted in the newly merged `main`. The one-line list is formatted in `a113717c4`; `npm run check:ci:fast` passed locally on the merged tree. [Full CI on the current head](https://github.com/morluto/rea/actions/runs/41564809466) passed, including all eight test shards, source tests, static checks, and website checks. ## Compatibility, safety, and release - Breaking changes or migration steps: none; this corrects advertised possible effects without changing calls or configuration. - Real provider coverage: recording IDA producer only; no IDA engine or GUI. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no additional authority. The advertised network and UI effects already exist in the IDA provider descriptors. ## Author readiness Human owner: @dhruvac29 - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7577
No description provided.