[PR #1890] [MERGED] fix(android): bound inline search Evidence with retained inventory provenance #4881

New issue

Closed

opened 2026-10-31 00:56:23 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 00:56:23 +00:00

Owner

Copy link

📋 Pull Request Information

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

Base: main ← Head: fix/1850-android-search-inventory

---

📝 Commits (1)

• 5a6c0e8 fix(android): bound inline search Evidence with retained inventory provenance

📊 Changes

5 files changed (+295 additions, -4 deletions)

View changed files

➕ src/application/android/AndroidSearchEvidenceSummary.ts (+120 -0)
📝 src/server/registerAndroidTools.ts (+23 -2)
➕ tests/boundary/process/androidSearchEvidenceBudget.test.ts (+131 -0)
📝 tests/fixtures/android/jadx-mcp.mjs (+11 -1)
📝 tests/fixtures/android/jadx.ts (+10 -1)

📄 Description

Summary

Focused and zero-match search_android_classes responses embedded every examined class name: a single-match search on a 7,096-class APK returned a 382,435-byte tool response because the complete raw provider inventory rode inside the inline Evidence. When the server session retains Evidence, the complete raw-call record is now written to the retained store and the tool response delivers a bounded summary Evidence that keeps the pagination audit, the unchanged normalized matches and truthful coverage metadata, and links the retained complete inventory by Evidence ID (Fixes #1850).

Problem and expected behavior

Smallest trigger: load a 7,096-class APK through the jadx bridge and call search_android_classes with a query matching exactly one class. Prior behavior: the response's inline raw_result contained every list_classes page with all 7,096 class names, because the raw provider call record was captured whole and serialized into every tool response. The violated invariant: a bounded, focused search response should not grow with the size of the unfiltered inventory, and a single match must not cost the full class list on the wire. Expected behavior: the inline Evidence carries the pagination audit (total, offset, limit, per-page items_omitted), an inventory_elided marker, the unchanged normalized matches and coverage: complete / total_classes, and evidence_links + complete_evidence_id pointing at the retained complete record; sessions without retention keep the complete inline delivery, so CLI JSON output is unchanged and no provenance is discarded.

Change and scope

Root cause chain: src/android/JadxSession.ts records each list_classes page's complete MCP envelope into #observedCalls (src/android/JadxSession.ts:220-221); those calls ride into the execution as rawResult through createAnalysisExecution (src/android/JadxSession.ts:145-152); src/application/android/AndroidAnalysisService.ts embeds them into the Evidence (src/application/android/AndroidAnalysisService.ts:44-55); and src/server/contractToolHandler.ts serializes the complete Evidence into every tool response (src/server/contractToolHandler.ts:66-71). The normalized result (src/domain/android/JadxAnalysis.ts:175) is itself bounded; only the raw-call record is not.

Fix: new src/application/android/AndroidSearchEvidenceSummary.ts, applied on the search_android_classes registration path in src/server/registerAndroidTools.ts. When the session retains Evidence, the complete Evidence (with the full raw-call inventory) is recorded first via recordEvidence, then a summary Evidence is delivered with items_omitted counts replacing the full per-page name lists. Sessions without retention skip summarization entirely, preserving the previous complete inline behavior for CLI consumers. Intentionally not included: no change to the normalized search contract, no change to non-search Android tools, and no budgeting for retention-free sessions.

Contract and boundary impact

• Semantic owner and earliest changed stage: the MCP tool-response boundary in src/server/registerAndroidTools.ts, after the normalized result and raw-call record exist and before serialization.
• CLI and MCP/tool-catalog contract: the advertised search_android_classes schema is unchanged and the normalized result is byte-identical; the inline raw_result for retaining sessions now elides inventory items behind items_omitted counts plus complete_evidence_id, which is an output-size bound, not a shape change to the advertised contract.
• Provider, bridge, target-format, or platform compatibility: none; the jadx bridge protocol is untouched (the fixture updates only extend the test protocol fixture to paginate at the same limits as the real bridge).
• Evidence, artifact, provenance, or reconstruction contract: no provenance is discarded — the complete raw-call record is retained and addressable by Evidence ID through evidence_links; observed vs. elided content remains distinguishable via inventory_elided and items_omitted.
• Process execution, authorization, cleanup, or containment impact: none; no new process, engine, or target acquisition.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none; no catalog, package, or installation contract changes and no generated outputs committed.

Evidence and regression coverage

• Tests added or updated: tests/boundary/process/androidSearchEvidenceBudget.test.ts drives a real 7,096-class jadx protocol fixture through the MCP server and asserts (1) with a retaining session: the single-match and zero-match inline raw_result contain no class names, stay under 32 KiB, carry items_omitted, and link a retained complete record whose raw calls hold all 7,096 names; (2) without a retaining session: the complete inventory stays inline.
• Base reproduction or other evidence: with the src/ change removed (test and fixtures in place) on the rebased base, the retaining-session case fails exactly on the inline-raw assertion — the single-match response contains the full 7,096-name inventory, i.e. the issue symptom.
• User-visible CLI/MCP output: MCP responses for retaining sessions shrink from ~382 KB to a bounded summary for focused/zero-match searches; complete CLI JSON output is unchanged.
• Remaining proof gaps: no real-device or real-APK lane was run; the fixture reproduces the real bridge's pagination envelope at the same 4,096 page limit.

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

Rebased onto origin/main (fa9a7e5e, which touches src/domain/evidence.ts), artifacts refreshed with npm run test:prepare, then:

• npx vitest run --project process-boundary tests/boundary/process/androidSearchEvidenceBudget.test.ts with the src/ fix removed — 1 failed / 1 passed; the failure is the bounded-Evidence assertion with the full 7,096-name inventory present in a single-match response (base reproduction).
• Same command with the fix restored — Test Files 1 passed, Tests 2 passed.
• npx vitest run tests/boundary/android/ tests/boundary/process/ src/server/ src/domain/android/ src/contracts/android/ — 36 files passed, 237 passed + 2 skipped, 0 failed.
• npx vitest run src/android/ src/server/ — 2 files passed, 12 passed. (Note: npx vitest run src/android/ alone exits 1 with "No test files found"; src/android/ has no test files in this repository.)
• npx vitest run tests/acceptance/tools/localToolContracts.test.ts tests/boundary/mcp/ — 97 files (95 passed + 2 skipped), 370 passed + 3 skipped, 0 failed.
• npx tsc --noEmit — exit 0.
• npx oxlint — 0 errors (the max-params(5) warning on registerAndroidTools is pre-existing at origin/main); npx oxfmt --check src/ tests/ — clean.
• Real Hopper/Ghidra, browser, or OS lanes: not exercised; the change is covered by the jadx protocol fixture suites above.

Compatibility, safety, and release

• Breaking changes or migration steps: none. Retaining-session MCP consumers that parsed the full inventory out of the inline raw record should read the retained complete record via evidence_links/complete_evidence_id; CLI output (no retention) is byte-identical in shape.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable; Android jadx bridge fixture only.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: bounds a response-size amplification (one focused query cost the entire class inventory on the wire); no new network, process, or authority surface.

Review checklist

• This PR addresses a concrete problem or an agreed enhancement.
• 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.

🤖 Generated with AI assistance (disclosure voluntary per repo policy)

---

_{🔄 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/1890 **Author:** [@akushonkamen](https://github.com/akushonkamen) **Created:** 10/11/2026 **Status:** ✅ Merged **Merged:** 10/11/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/1850-android-search-inventory` --- ### 📝 Commits (1) - [`5a6c0e8`](https://github.com/morluto/rea/commit/5a6c0e8a4844e96cd0930d204a38c7b3aa999eb8) fix(android): bound inline search Evidence with retained inventory provenance ### 📊 Changes **5 files changed** (+295 additions, -4 deletions) <details> <summary>View changed files</summary> ➕ `src/application/android/AndroidSearchEvidenceSummary.ts` (+120 -0) 📝 `src/server/registerAndroidTools.ts` (+23 -2) ➕ `tests/boundary/process/androidSearchEvidenceBudget.test.ts` (+131 -0) 📝 `tests/fixtures/android/jadx-mcp.mjs` (+11 -1) 📝 `tests/fixtures/android/jadx.ts` (+10 -1) </details> ### 📄 Description ## Summary Focused and zero-match `search_android_classes` responses embedded every examined class name: a single-match search on a 7,096-class APK returned a 382,435-byte tool response because the complete raw provider inventory rode inside the inline Evidence. When the server session retains Evidence, the complete raw-call record is now written to the retained store and the tool response delivers a bounded summary Evidence that keeps the pagination audit, the unchanged normalized matches and truthful coverage metadata, and links the retained complete inventory by Evidence ID (Fixes #1850). ## Problem and expected behavior Smallest trigger: load a 7,096-class APK through the jadx bridge and call `search_android_classes` with a query matching exactly one class. Prior behavior: the response's inline `raw_result` contained every `list_classes` page with all 7,096 class names, because the raw provider call record was captured whole and serialized into every tool response. The violated invariant: a bounded, focused search response should not grow with the size of the unfiltered inventory, and a single match must not cost the full class list on the wire. Expected behavior: the inline Evidence carries the pagination audit (`total`, `offset`, `limit`, per-page `items_omitted`), an `inventory_elided` marker, the unchanged normalized matches and `coverage: complete` / `total_classes`, and `evidence_links` + `complete_evidence_id` pointing at the retained complete record; sessions without retention keep the complete inline delivery, so CLI JSON output is unchanged and no provenance is discarded. ## Change and scope Root cause chain: `src/android/JadxSession.ts` records each `list_classes` page's complete MCP envelope into `#observedCalls` (src/android/JadxSession.ts:220-221); those calls ride into the execution as `rawResult` through `createAnalysisExecution` (src/android/JadxSession.ts:145-152); `src/application/android/AndroidAnalysisService.ts` embeds them into the Evidence (src/application/android/AndroidAnalysisService.ts:44-55); and `src/server/contractToolHandler.ts` serializes the complete Evidence into every tool response (src/server/contractToolHandler.ts:66-71). The normalized result (`src/domain/android/JadxAnalysis.ts:175`) is itself bounded; only the raw-call record is not. Fix: new `src/application/android/AndroidSearchEvidenceSummary.ts`, applied on the `search_android_classes` registration path in `src/server/registerAndroidTools.ts`. When the session retains Evidence, the complete Evidence (with the full raw-call inventory) is recorded first via `recordEvidence`, then a summary Evidence is delivered with `items_omitted` counts replacing the full per-page name lists. Sessions without retention skip summarization entirely, preserving the previous complete inline behavior for CLI consumers. Intentionally not included: no change to the normalized search contract, no change to non-search Android tools, and no budgeting for retention-free sessions. ## Contract and boundary impact - Semantic owner and earliest changed stage: the MCP tool-response boundary in `src/server/registerAndroidTools.ts`, after the normalized result and raw-call record exist and before serialization. - CLI and MCP/tool-catalog contract: the advertised `search_android_classes` schema is unchanged and the normalized result is byte-identical; the inline `raw_result` for retaining sessions now elides inventory items behind `items_omitted` counts plus `complete_evidence_id`, which is an output-size bound, not a shape change to the advertised contract. - Provider, bridge, target-format, or platform compatibility: none; the jadx bridge protocol is untouched (the fixture updates only extend the test protocol fixture to paginate at the same limits as the real bridge). - Evidence, artifact, provenance, or reconstruction contract: no provenance is discarded — the complete raw-call record is retained and addressable by Evidence ID through `evidence_links`; observed vs. elided content remains distinguishable via `inventory_elided` and `items_omitted`. - Process execution, authorization, cleanup, or containment impact: none; no new process, engine, or target acquisition. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none; no catalog, package, or installation contract changes and no generated outputs committed. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/process/androidSearchEvidenceBudget.test.ts` drives a real 7,096-class jadx protocol fixture through the MCP server and asserts (1) with a retaining session: the single-match and zero-match inline `raw_result` contain no class names, stay under 32 KiB, carry `items_omitted`, and link a retained complete record whose raw calls hold all 7,096 names; (2) without a retaining session: the complete inventory stays inline. - Base reproduction or other evidence: with the `src/` change removed (test and fixtures in place) on the rebased base, the retaining-session case fails exactly on the inline-raw assertion — the single-match response contains the full 7,096-name inventory, i.e. the issue symptom. - User-visible CLI/MCP output: MCP responses for retaining sessions shrink from ~382 KB to a bounded summary for focused/zero-match searches; complete CLI JSON output is unchanged. - Remaining proof gaps: no real-device or real-APK lane was run; the fixture reproduces the real bridge's pagination envelope at the same 4,096 page limit. 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 Rebased onto `origin/main` (`fa9a7e5e`, which touches `src/domain/evidence.ts`), artifacts refreshed with `npm run test:prepare`, then: - `npx vitest run --project process-boundary tests/boundary/process/androidSearchEvidenceBudget.test.ts` with the `src/` fix removed — 1 failed / 1 passed; the failure is the bounded-Evidence assertion with the full 7,096-name inventory present in a single-match response (base reproduction). - Same command with the fix restored — Test Files 1 passed, Tests 2 passed. - `npx vitest run tests/boundary/android/ tests/boundary/process/ src/server/ src/domain/android/ src/contracts/android/` — 36 files passed, 237 passed + 2 skipped, 0 failed. - `npx vitest run src/android/ src/server/` — 2 files passed, 12 passed. (Note: `npx vitest run src/android/` alone exits 1 with "No test files found"; `src/android/` has no test files in this repository.) - `npx vitest run tests/acceptance/tools/localToolContracts.test.ts tests/boundary/mcp/` — 97 files (95 passed + 2 skipped), 370 passed + 3 skipped, 0 failed. - `npx tsc --noEmit` — exit 0. - `npx oxlint` — 0 errors (the `max-params(5)` warning on `registerAndroidTools` is pre-existing at `origin/main`); `npx oxfmt --check src/ tests/` — clean. - Real Hopper/Ghidra, browser, or OS lanes: not exercised; the change is covered by the jadx protocol fixture suites above. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Retaining-session MCP consumers that parsed the full inventory out of the inline raw record should read the retained complete record via `evidence_links`/`complete_evidence_id`; CLI output (no retention) is byte-identical in shape. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; Android jadx bridge fixture only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: bounds a response-size amplification (one focused query cost the entire class inventory on the wire); no new network, process, or authority surface. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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. 🤖 Generated with AI assistance (disclosure voluntary per repo policy) --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 00:56:23 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-01 21:42:38 +00:00

[PR #5012] [MERGED] docs(setup): clarify prebuild-install warning from optional dependencies (#4881) #6730

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

Subscribe

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#4881

No description provided.