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 #6288] feat(harmony): add xpanda-backed Ark bytecode analysis #7259

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6288
Author: @asmjmp0
Created: 10/22/2026
Status: 🔄 Open

Base: main ← Head: feat/harmony/xpanda

📝 Commits (1)

  • 3c608c2 feat(harmony): add xpanda-backed Ark bytecode analysis

📊 Changes

71 files changed (+5005 additions, -461 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/SKILL.md (+7 -0)
📝 README.md (+3 -1)
📝 docs/cli.md (+7 -5)
➕ docs/harmony-abc-analysis.md (+103 -0)
📝 docs/harmony-analysis.md (+4 -2)
📝 docs/index.md (+13 -13)
📝 docs/installation.md (+7 -7)
📝 docs/readme/README_ar.md (+25 -25)
📝 docs/readme/README_de.md (+2 -2)
📝 docs/readme/README_el.md (+2 -2)
📝 docs/readme/README_es.md (+2 -2)
📝 docs/readme/README_fa.md (+2 -2)
📝 docs/readme/README_fr.md (+2 -2)
📝 docs/readme/README_id.md (+2 -2)
📝 docs/readme/README_it.md (+2 -2)
📝 docs/readme/README_ja.md (+2 -2)
📝 docs/readme/README_ko.md (+2 -2)
📝 docs/readme/README_ml.md (+2 -2)
📝 docs/readme/README_pl.md (+25 -25)
📝 docs/readme/README_pt-BR.md (+2 -2)

...and 51 more files

📄 Description

Summary

Adds a dedicated HarmonyOS provider for Ark bytecode (.abc) analysis, backed by a caller-supplied xpanda checkout. docs/harmony-analysis.md deferred bytecode contents and versions until a dedicated HarmonyOS provider existed; this is that provider (roadmap #1431).

No issue is linked: the scope comes from the deferred-provider statement in docs/harmony-analysis.md.

Problem and expected behavior

Before: REA could inventory HAP/HSP/.app package structure but could not read Ark bytecode. Analysts had to leave REA to inspect classes, decompiled JavaScript or method disassembly.

After: six new MCP tools and matching one-shot CLI commands answer header facts, class inventory, single-class and whole-file decompilation, method disassembly, and string-pool search. Results are inline Evidence bound to the selected .abc file.

Change and scope

  • src/harmony/ owns the adapter: configuration (REA_XPANDA_ROOT, absolute path, 2.x admitted), engine tree digest, producer protocol/response parsing, the retained stdio MCP bridge, failure capture, and doctor readiness.
  • Proxy shape follows the JADX MCP bridge: one owned, serialized bridge per REA instance, 60 s idle retirement, shutdown cleanup, and a fresh respawn after fatal transport or deadline failures. Producer coherence errors (unknown class/method) keep the bridge.
  • Every operation stages a private snapshot of the selected input, verifies it against a stable source read, and binds Evidence to the analyzed bytes. A new abc Evidence subject format carries the file identity.
  • Producer output is parsed at one boundary: JSON tool results are schema-validated, the two text-shaped tools keep producer rendering verbatim behind strictly parsed header lines with payload-length and truncation checks, and producer errors map onto the existing tagged error algebra.
  • src/providers/McpStdioTransport.ts extracts the newline-framed MCP stdio transport previously embedded in the JADX adapter; src/android/JadxMcpTransport.ts is now a thin subclass preserving JADX attribution.
  • Wired availability (binary_session reporting), doctor (--provider xpanda), setup registration environment propagation, tool effects audit, product/MCP catalogs, authored skill guidance, and provider documentation.

Intentionally not included: deep-provider integration (open_binary + provider selection) for .abc targets; that remains a follow-up increment. Windows is not enabled because process-tree ownership for the bridge is unverified there.

Scope decision: static parsing and rendering only — no target execution, injection, mutation, or protection recovery, so the new-provider maintainer scope decision does not apply. The provider does launch the caller-supplied engine process, consistent with existing JADX/Binwalk/Kuna integrations.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/harmony/ owns producer semantics from bridge launch through response parsing; src/domain/harmony/harmonyAbcAnalysis.ts owns caller contracts.
  • Contribution scope fit and linked maintainer decision: static analysis capability; not applicable (no execution/injection/mutation/protection recovery).
  • CLI and MCP/tool-catalog contract: +6 MCP tools and +6 CLI commands; docs/public/product-catalog.json regenerated; CLI/MCP share one service.
  • Provider, bridge, target-format, or platform compatibility: provider id xpanda; xpanda 2.x admitted (verified 2.1.0), other majors refused; Linux and macOS only.
  • Evidence, artifact, provenance, or reconstruction contract: new abc subject format; staged-input SHA-256; engine package.json+src tree digest; producer version and explicit limitations.
  • Target selection, authority, upstream behavior, and cleanup details: no target execution. Owned bridge process with proven stop and retained cleanup retry; failed producer session close is reported in raw facts (producer LRU bounds leaks).
  • Generated metadata: catalogs, recorded digests, product catalog, and packaged skill regenerated by the build; authored instructions updated in .agents/skills/reverse-engineer-anything/. No build outputs committed.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process. (Caller-configured xpanda MCP server.)
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration. (Writes decompiled JavaScript only into the caller-selected absent output directory.)
  • 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/harmony/XpandaProtocol.test.ts, src/harmony/XpandaConfiguration.test.ts, tests/boundary/providers/harmony/* (scripted fake MCP engine with captured producer reply shapes), tests/boundary/mcp/harmonyAbcMcp.test.ts, tests/boundary/cli/harmonyAbcCommands.test.ts, plus absolute-path coverage in tests/boundary/mcp/absoluteLocalPathSchema.test.ts and effect-wording audit entries.

  • Base reproduction or other evidence: behavior is new; the provider absence was documented in docs/harmony-analysis.md.

  • User-visible CLI/MCP output: verify:xpanda exercises the compiled CLI and SDK-connected MCP server; representative output is the inline Evidence with subject.format: "abc".

  • Remaining proof gaps: the full npm run test:boundary suite was not completed in this environment; the affected built suites were run individually (listed below). Decompilation fidelity for arbitrary bytecode versions and untested xpanda 2.x releases is producer-owned and not independently verified.

  • 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 — typecheck and lint pass (0 errors).
  • npm run test:fast — 832 files, 13,921 tests passed, 22 skipped.
  • npm run test:focused -- tests/boundary/providers/harmony/xpandaProvider.test.ts tests/boundary/mcp/harmonyAbcMcp.test.ts tests/boundary/cli/harmonyAbcCommands.test.ts tests/boundary/mcp/absoluteLocalPathSchema.test.ts — 4 files, 20 tests passed.
  • npm run test:local -- src/harmony/XpandaProtocol.test.ts src/harmony/XpandaConfiguration.test.ts — 31 tests passed.
  • Focused built suites for tool coverage, product catalog, server identity, tool schema validity, compact schemas, input admission, output schema profile, deferred runtime, CLI startup imports, setup/doctor, JADX transport regression, and acceptance/conformance — all passed.
  • npm run docs:check — passed.
  • REA_XPANDA_ROOT=/Users/jmp0/xpanda npm run verify:xpanda — passed against a local xpanda 2.1.0 checkout through the compiled CLI and SDK-connected stdio MCP: header inspection (2 classes, bytecode 11.0.2.0), class listing, single-class decompilation, method disassembly, string search, whole-file decompilation, CLI/MCP parity, and a typed absent-class failure.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable (no native provider changes). Real xpanda 2.1.0 verified on macOS arm64; Linux path is shared but not run in this environment; Windows is refused.
  • Package or release metadata impact: no new runtime dependency; new environment variable REA_XPANDA_ROOT; catalogs and skill tool count regenerated.
  • Security, privacy, process, or containment review: the bridge runs the caller's own checkout with REA-owned process supervision, stages input under a 256 MiB bound in a private runtime root, never executes decompiled output, and records engine provenance without inheriting unneeded environment values.

Author readiness

Human owner: @asmjmp0

  • 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/6288 **Author:** [@asmjmp0](https://github.com/asmjmp0) **Created:** 10/22/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/harmony/xpanda` --- ### 📝 Commits (1) - [`3c608c2`](https://github.com/morluto/rea/commit/3c608c2b672c4b570f97306f29f6884676add1b5) feat(harmony): add xpanda-backed Ark bytecode analysis ### 📊 Changes **71 files changed** (+5005 additions, -461 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/SKILL.md` (+7 -0) 📝 `README.md` (+3 -1) 📝 `docs/cli.md` (+7 -5) ➕ `docs/harmony-abc-analysis.md` (+103 -0) 📝 `docs/harmony-analysis.md` (+4 -2) 📝 `docs/index.md` (+13 -13) 📝 `docs/installation.md` (+7 -7) 📝 `docs/readme/README_ar.md` (+25 -25) 📝 `docs/readme/README_de.md` (+2 -2) 📝 `docs/readme/README_el.md` (+2 -2) 📝 `docs/readme/README_es.md` (+2 -2) 📝 `docs/readme/README_fa.md` (+2 -2) 📝 `docs/readme/README_fr.md` (+2 -2) 📝 `docs/readme/README_id.md` (+2 -2) 📝 `docs/readme/README_it.md` (+2 -2) 📝 `docs/readme/README_ja.md` (+2 -2) 📝 `docs/readme/README_ko.md` (+2 -2) 📝 `docs/readme/README_ml.md` (+2 -2) 📝 `docs/readme/README_pl.md` (+25 -25) 📝 `docs/readme/README_pt-BR.md` (+2 -2) _...and 51 more files_ </details> ### 📄 Description ## Summary Adds a dedicated HarmonyOS provider for Ark bytecode (`.abc`) analysis, backed by a caller-supplied [xpanda](https://github.com/asmjmp0/xpanda) checkout. `docs/harmony-analysis.md` deferred bytecode contents and versions until a dedicated HarmonyOS provider existed; this is that provider (roadmap #1431). No issue is linked: the scope comes from the deferred-provider statement in `docs/harmony-analysis.md`. ## Problem and expected behavior Before: REA could inventory HAP/HSP/.app package structure but could not read Ark bytecode. Analysts had to leave REA to inspect classes, decompiled JavaScript or method disassembly. After: six new MCP tools and matching one-shot CLI commands answer header facts, class inventory, single-class and whole-file decompilation, method disassembly, and string-pool search. Results are inline Evidence bound to the selected `.abc` file. ## Change and scope - `src/harmony/` owns the adapter: configuration (`REA_XPANDA_ROOT`, absolute path, 2.x admitted), engine tree digest, producer protocol/response parsing, the retained stdio MCP bridge, failure capture, and doctor readiness. - Proxy shape follows the JADX MCP bridge: one owned, serialized bridge per REA instance, 60 s idle retirement, shutdown cleanup, and a fresh respawn after fatal transport or deadline failures. Producer coherence errors (unknown class/method) keep the bridge. - Every operation stages a private snapshot of the selected input, verifies it against a stable source read, and binds Evidence to the analyzed bytes. A new `abc` Evidence subject format carries the file identity. - Producer output is parsed at one boundary: JSON tool results are schema-validated, the two text-shaped tools keep producer rendering verbatim behind strictly parsed header lines with payload-length and truncation checks, and producer errors map onto the existing tagged error algebra. - `src/providers/McpStdioTransport.ts` extracts the newline-framed MCP stdio transport previously embedded in the JADX adapter; `src/android/JadxMcpTransport.ts` is now a thin subclass preserving JADX attribution. - Wired availability (`binary_session` reporting), doctor (`--provider xpanda`), setup registration environment propagation, tool effects audit, product/MCP catalogs, authored skill guidance, and provider documentation. Intentionally not included: deep-provider integration (`open_binary` + provider selection) for `.abc` targets; that remains a follow-up increment. Windows is not enabled because process-tree ownership for the bridge is unverified there. Scope decision: static parsing and rendering only — no target execution, injection, mutation, or protection recovery, so the new-provider maintainer scope decision does not apply. The provider does launch the caller-supplied engine process, consistent with existing JADX/Binwalk/Kuna integrations. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/harmony/` owns producer semantics from bridge launch through response parsing; `src/domain/harmony/harmonyAbcAnalysis.ts` owns caller contracts. - Contribution scope fit and linked maintainer decision: static analysis capability; not applicable (no execution/injection/mutation/protection recovery). - CLI and MCP/tool-catalog contract: +6 MCP tools and +6 CLI commands; `docs/public/product-catalog.json` regenerated; CLI/MCP share one service. - Provider, bridge, target-format, or platform compatibility: provider id `xpanda`; xpanda 2.x admitted (verified 2.1.0), other majors refused; Linux and macOS only. - Evidence, artifact, provenance, or reconstruction contract: new `abc` subject format; staged-input SHA-256; engine `package.json`+`src` tree digest; producer version and explicit limitations. - Target selection, authority, upstream behavior, and cleanup details: no target execution. Owned bridge process with proven stop and retained cleanup retry; failed producer session close is reported in raw facts (producer LRU bounds leaks). - Generated metadata: catalogs, recorded digests, product catalog, and packaged skill regenerated by the build; authored instructions updated in `.agents/skills/reverse-engineer-anything/`. No build outputs committed. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. (Caller-configured xpanda MCP server.) - [ ] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. (Writes decompiled JavaScript only into the caller-selected absent output directory.) - [ ] 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/harmony/XpandaProtocol.test.ts`, `src/harmony/XpandaConfiguration.test.ts`, `tests/boundary/providers/harmony/*` (scripted fake MCP engine with captured producer reply shapes), `tests/boundary/mcp/harmonyAbcMcp.test.ts`, `tests/boundary/cli/harmonyAbcCommands.test.ts`, plus absolute-path coverage in `tests/boundary/mcp/absoluteLocalPathSchema.test.ts` and effect-wording audit entries. - Base reproduction or other evidence: behavior is new; the provider absence was documented in `docs/harmony-analysis.md`. - User-visible CLI/MCP output: `verify:xpanda` exercises the compiled CLI and SDK-connected MCP server; representative output is the inline Evidence with `subject.format: "abc"`. - Remaining proof gaps: the full `npm run test:boundary` suite was not completed in this environment; the affected built suites were run individually (listed below). Decompilation fidelity for arbitrary bytecode versions and untested xpanda 2.x releases is producer-owned and not independently verified. - [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` — typecheck and lint pass (0 errors). - `npm run test:fast` — 832 files, 13,921 tests passed, 22 skipped. - `npm run test:focused -- tests/boundary/providers/harmony/xpandaProvider.test.ts tests/boundary/mcp/harmonyAbcMcp.test.ts tests/boundary/cli/harmonyAbcCommands.test.ts tests/boundary/mcp/absoluteLocalPathSchema.test.ts` — 4 files, 20 tests passed. - `npm run test:local -- src/harmony/XpandaProtocol.test.ts src/harmony/XpandaConfiguration.test.ts` — 31 tests passed. - Focused built suites for tool coverage, product catalog, server identity, tool schema validity, compact schemas, input admission, output schema profile, deferred runtime, CLI startup imports, setup/doctor, JADX transport regression, and acceptance/conformance — all passed. - `npm run docs:check` — passed. - `REA_XPANDA_ROOT=/Users/jmp0/xpanda npm run verify:xpanda` — passed against a local xpanda 2.1.0 checkout through the compiled CLI and SDK-connected stdio MCP: header inspection (2 classes, bytecode 11.0.2.0), class listing, single-class decompilation, method disassembly, string search, whole-file decompilation, CLI/MCP parity, and a typed absent-class failure. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable (no native provider changes). Real xpanda 2.1.0 verified on macOS arm64; Linux path is shared but not run in this environment; Windows is refused. - Package or release metadata impact: no new runtime dependency; new environment variable `REA_XPANDA_ROOT`; catalogs and skill tool count regenerated. - Security, privacy, process, or containment review: the bridge runs the caller's own checkout with REA-owned process supervision, stages input under a 256 MiB bound in a private runtime root, never executes decompiled output, and records engine provenance without inheriting unneeded environment values. ## Author readiness Human owner: @asmjmp0 - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <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#7259
No description provided.