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 #2923] feat(ghidra): admit bounded m68k ELF analysis through Ghidra #5498

New issue
Open
opened 2026-10-31 01:07:06 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:07:06 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2923
Author: @nplanel
Created: 10/13/2026
Status: 🔄 Open

Base: main ← Head: nplanel/m68k

📝 Commits (1)

  • a596221 feat(ghidra): admit bounded m68k ELF analysis through Ghidra

📊 Changes

21 files changed (+1590 additions, -25 deletions)

View changed files

📝 docs/firmware-analysis.md (+3 -2)
➕ docs/ghidra-m68k.md (+98 -0)
📝 package.json (+1 -0)
➕ scripts/verify-real-ghidra-m68k.mjs (+281 -0)
➕ src/domain/binaryTarget.m68k.test.ts (+78 -0)
📝 src/domain/binaryTarget.ts (+36 -16)
📝 src/domain/binaryTargetTypes.ts (+17 -0)
📝 src/ghidra/GhidraAnalysisProfile.ts (+36 -3)
➕ src/ghidra/GhidraM68kProfile.test.ts (+253 -0)
➕ src/ghidra/GhidraM68kProfile.ts (+120 -0)
📝 src/ghidra/GhidraProvider.ts (+11 -1)
📝 src/ghidra/GhidraProviderClient.ts (+19 -1)
📝 src/hopper/HopperAnalysisProfile.ts (+1 -0)
📝 src/hopper/HopperProvider.ts (+5 -1)
📝 src/ida/IdaProvider.ts (+5 -1)
➕ tests/composition/analysis-sessions/m68k-identity.test.ts (+91 -0)
➕ tests/conformance/ghidra/m68k-checks.d.mts (+16 -0)
➕ tests/conformance/ghidra/m68k-checks.mjs (+172 -0)
➕ tests/conformance/ghidra/m68k-checks.test.ts (+236 -0)
➕ tests/conformance/ghidra/m68k-fixture.d.mts (+26 -0)

...and 1 more files

📄 Description

Summary

Retain ELF EM_68K as the provider-neutral m68k family with class, byte order, e_type and raw e_flags, and admit big-endian ELF32 ET_EXEC with an EF_M68K_M68000 family declaration through a bounded Ghidra lane. CPU32, ColdFire, FIDO, unspecified flags, unknown architecture bits, ELF64, little-endian images and non-ET_EXEC inputs are refused with specific reasons instead of a guessed processor profile.

Ghidra's own ELF loader opinion resolves EM_68K to the ColdFire variant (observed on the tested Ghidra 12.1.x), whose instruction set is not an M68000 superset. REA therefore pins the admitted import language to 68000:BE:32:default (MC68040) through the provider-pinned profile mechanism, commits it in the analysis profile, and enforces the observed language and compiler specification; a caller-selected language that differs from the pin is refused. The m68k header and e_flags facts bind profile identity so interpretation changes invalidate snapshots. Hopper and IDA refuse m68k targets; Windows Ghidra P0 remains PE x86/x86-64 only.

The change also widens the advertised open_binary result architecture enum (and therefore Evidence and snapshot subject schemas) with the additive m68k value. No new CLI/MCP tools or inputs are introduced.

Verification: npm run verify:ghidra:m68k passed against Ghidra 12.1.2 and JDK 21.0.12.1 with a source-owned hand-built ELF fixture, verifying the pinned effective language, loaded identity and mapping, fixed MOVE.L/short BRA bytes with immediate and branch destination, global and marker bytes, Evidence/snapshot identity, CLI/MCP agreement and process cleanup without retained descendants. The source suite passes apart from one pre-existing unrelated failure set that reproduces on current main. docs/ghidra-m68k.md records the admission boundary, the ColdFire finding and the executed run.

Problem and expected behavior

EM_68K ELF targets were rejected during target resolution ("unsupported ELF architecture"), so no provider could analyze them, and Hopper has no m68k support. Expected behavior is a provider-neutral m68k family that routes admitted big-endian ELF32 ET_EXEC EF_M68K_M68000 images to the existing Ghidra provider with an explicitly pinned language, while every unverified variant stays refused with a specific reason.

Change and scope

Adds the bounded m68k ELF lane described above to the existing Ghidra provider. Non-goals: classic m68k containers (Amiga Hunk, Atari TOS, classic Mac PEF, headerless ROMs), ISA variants (ColdFire, CPU32, FIDO), IDA/Hopper m68k lanes, and Windows P0 coverage.

Contribution scope: static disassembly/decompilation and evidence reporting within an existing provider. No target execution, injection, mutation, or protection recovery; the only effects are the existing Ghidra headless launch and ephemeral project writes, so no new-provider advance scope decision is required (not applicable). No m68k issue exists upstream; this PR is the initial proposal and can be linked to a feature request or design discussion if maintainers prefer that route.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/domain/binaryTarget.ts recognizes EM_68K and provides the parsed m68k metadata; consumers use those facts instead of re-reading the header.
  • Contribution scope fit and linked maintainer decision: existing Ghidra provider, static analysis only; no execution, injection, mutation, or protection recovery. Advance maintainer decision not applicable.
  • CLI and MCP/tool-catalog contract: additive m68k value in the advertised open_binary result architecture enum and the Evidence/snapshot subject schemas. No new tools or inputs.
  • Provider, bridge, target-format, or platform compatibility: Ghidra only on Linux/macOS; Ghidra 12.1.x admission, real run on 12.1.2 (other builds keep the standard unverified-build limitation). Hopper and IDA explicitly refuse m68k; Windows P0 unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: the profile commits m68k_elf facts, the versioned m68k_support_lane, and language_selection: provider-pinned-v1; interpretation changes invalidate profile-bound snapshots.
  • Target selection, authority, upstream behavior, and cleanup details: existing Ghidra ephemeral import; executable bytes are never written; the real lane verifies final cleanup with no retained descendants.
  • Generated metadata: no authored generated files change; docs/public/product-catalog.json and skills/ remain CI-generated and uncommitted.

Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: src/domain/binaryTarget.m68k.test.ts, src/ghidra/GhidraM68kProfile.test.ts, tests/composition/analysis-sessions/m68k-identity.test.ts, tests/conformance/ghidra/m68k-checks.test.ts with m68k-fixture.mjs/m68k-checks.mjs, and scripts/verify-real-ghidra-m68k.mjs.
  • Base reproduction or other evidence: on the base revision EM_68K fails with "unsupported ELF architecture"; the source-owned fixture exercises header facts, admission refusals and the pinned profile. The first real run observed Ghidra selecting 68000:BE:32:Coldfire and the handshake refusing it, which motivated the pin.
  • User-visible CLI/MCP output (if applicable): open_binary returns architecture: "m68k"; rea instructions lists the fixed MOVE.L/short BRA bytes; snapshot parameters carry m68k_elf, m68k_support_lane and provider-pinned-v1.
  • Remaining proof gaps: one hand-built fixture only; no real 68000/68020/68030 corpus; MC68060-only semantics unverified; classic containers unsupported; the real run is on Ghidra 12.1.2 while the repository's verified build is 12.1.4.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm run verify:ghidra:m68k — passed (Ghidra 12.1.2, JDK 21.0.12.1; language 68000:BE:32:default, mappings, probe and data bytes, snapshot and CLI/MCP parity, clean process lineage).
  • npx vitest run --project domain --project services --project adapters --project composition --project conformance --project evaluation — 6314 passed, 4 skipped; a pre-existing failure set in src/domain/reconstructionVerification.functionSources.test.ts (5 tests) reproduces unchanged on current main and is unrelated to this diff.
  • npm run check:fast — passed (typecheck, lint, module boundaries).
  • npm run docs:check — passed.
  • npx oxfmt --check . — passes; the two inherited upstream formatting failures were repaired by upstream 8fef2aa (#2938).
  • Rebased onto current main (8fef2aa); the branch is no longer conflicted.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; the architecture enum addition is additive.
  • Real Hopper/Ghidra, browser, or OS coverage: real Ghidra 12.1.2 + JDK 21.0.12.1 on Linux x64; no Hopper or browser coverage claimed.
  • Package or release metadata impact: new verify:ghidra:m68k npm script only; no runtime dependency change.
  • Security, privacy, process, or containment review: no network, no target execution, no mutation; existing ephemeral-provider lifecycle and cleanup rules apply.

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/2923 **Author:** [@nplanel](https://github.com/nplanel) **Created:** 10/13/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `nplanel/m68k` --- ### 📝 Commits (1) - [`a596221`](https://github.com/morluto/rea/commit/a59622152ef7ce1cef11989f868d4282be44c979) feat(ghidra): admit bounded m68k ELF analysis through Ghidra ### 📊 Changes **21 files changed** (+1590 additions, -25 deletions) <details> <summary>View changed files</summary> 📝 `docs/firmware-analysis.md` (+3 -2) ➕ `docs/ghidra-m68k.md` (+98 -0) 📝 `package.json` (+1 -0) ➕ `scripts/verify-real-ghidra-m68k.mjs` (+281 -0) ➕ `src/domain/binaryTarget.m68k.test.ts` (+78 -0) 📝 `src/domain/binaryTarget.ts` (+36 -16) 📝 `src/domain/binaryTargetTypes.ts` (+17 -0) 📝 `src/ghidra/GhidraAnalysisProfile.ts` (+36 -3) ➕ `src/ghidra/GhidraM68kProfile.test.ts` (+253 -0) ➕ `src/ghidra/GhidraM68kProfile.ts` (+120 -0) 📝 `src/ghidra/GhidraProvider.ts` (+11 -1) 📝 `src/ghidra/GhidraProviderClient.ts` (+19 -1) 📝 `src/hopper/HopperAnalysisProfile.ts` (+1 -0) 📝 `src/hopper/HopperProvider.ts` (+5 -1) 📝 `src/ida/IdaProvider.ts` (+5 -1) ➕ `tests/composition/analysis-sessions/m68k-identity.test.ts` (+91 -0) ➕ `tests/conformance/ghidra/m68k-checks.d.mts` (+16 -0) ➕ `tests/conformance/ghidra/m68k-checks.mjs` (+172 -0) ➕ `tests/conformance/ghidra/m68k-checks.test.ts` (+236 -0) ➕ `tests/conformance/ghidra/m68k-fixture.d.mts` (+26 -0) _...and 1 more files_ </details> ### 📄 Description ## Summary Retain ELF `EM_68K` as the provider-neutral `m68k` family with class, byte order, `e_type` and raw `e_flags`, and admit big-endian ELF32 `ET_EXEC` with an `EF_M68K_M68000` family declaration through a bounded Ghidra lane. CPU32, ColdFire, FIDO, unspecified flags, unknown architecture bits, ELF64, little-endian images and non-`ET_EXEC` inputs are refused with specific reasons instead of a guessed processor profile. Ghidra's own ELF loader opinion resolves `EM_68K` to the ColdFire variant (observed on the tested Ghidra 12.1.x), whose instruction set is not an M68000 superset. REA therefore pins the admitted import language to `68000:BE:32:default` (MC68040) through the provider-pinned profile mechanism, commits it in the analysis profile, and enforces the observed language and compiler specification; a caller-selected language that differs from the pin is refused. The m68k header and `e_flags` facts bind profile identity so interpretation changes invalidate snapshots. Hopper and IDA refuse m68k targets; Windows Ghidra P0 remains PE x86/x86-64 only. The change also widens the advertised `open_binary` result `architecture` enum (and therefore Evidence and snapshot subject schemas) with the additive `m68k` value. No new CLI/MCP tools or inputs are introduced. Verification: `npm run verify:ghidra:m68k` passed against Ghidra 12.1.2 and JDK 21.0.12.1 with a source-owned hand-built ELF fixture, verifying the pinned effective language, loaded identity and mapping, fixed MOVE.L/short BRA bytes with immediate and branch destination, global and marker bytes, Evidence/snapshot identity, CLI/MCP agreement and process cleanup without retained descendants. The source suite passes apart from one pre-existing unrelated failure set that reproduces on current `main`. `docs/ghidra-m68k.md` records the admission boundary, the ColdFire finding and the executed run. ## Problem and expected behavior `EM_68K` ELF targets were rejected during target resolution ("unsupported ELF architecture"), so no provider could analyze them, and Hopper has no m68k support. Expected behavior is a provider-neutral `m68k` family that routes admitted big-endian ELF32 `ET_EXEC` `EF_M68K_M68000` images to the existing Ghidra provider with an explicitly pinned language, while every unverified variant stays refused with a specific reason. ## Change and scope Adds the bounded m68k ELF lane described above to the existing Ghidra provider. Non-goals: classic m68k containers (Amiga Hunk, Atari TOS, classic Mac PEF, headerless ROMs), ISA variants (ColdFire, CPU32, FIDO), IDA/Hopper m68k lanes, and Windows P0 coverage. Contribution scope: static disassembly/decompilation and evidence reporting within an existing provider. No target execution, injection, mutation, or protection recovery; the only effects are the existing Ghidra headless launch and ephemeral project writes, so no new-provider advance scope decision is required (not applicable). No m68k issue exists upstream; this PR is the initial proposal and can be linked to a feature request or design discussion if maintainers prefer that route. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/domain/binaryTarget.ts` recognizes `EM_68K` and provides the parsed `m68k` metadata; consumers use those facts instead of re-reading the header. - Contribution scope fit and linked maintainer decision: existing Ghidra provider, static analysis only; no execution, injection, mutation, or protection recovery. Advance maintainer decision not applicable. - CLI and MCP/tool-catalog contract: additive `m68k` value in the advertised `open_binary` result `architecture` enum and the Evidence/snapshot subject schemas. No new tools or inputs. - Provider, bridge, target-format, or platform compatibility: Ghidra only on Linux/macOS; Ghidra 12.1.x admission, real run on 12.1.2 (other builds keep the standard unverified-build limitation). Hopper and IDA explicitly refuse m68k; Windows P0 unchanged. - Evidence, artifact, provenance, or reconstruction contract: the profile commits `m68k_elf` facts, the versioned `m68k_support_lane`, and `language_selection: provider-pinned-v1`; interpretation changes invalidate profile-bound snapshots. - Target selection, authority, upstream behavior, and cleanup details: existing Ghidra ephemeral import; executable bytes are never written; the real lane verifies final cleanup with no retained descendants. - Generated metadata: no authored generated files change; `docs/public/product-catalog.json` and `skills/` remain CI-generated and uncommitted. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/domain/binaryTarget.m68k.test.ts`, `src/ghidra/GhidraM68kProfile.test.ts`, `tests/composition/analysis-sessions/m68k-identity.test.ts`, `tests/conformance/ghidra/m68k-checks.test.ts` with `m68k-fixture.mjs`/`m68k-checks.mjs`, and `scripts/verify-real-ghidra-m68k.mjs`. - Base reproduction or other evidence: on the base revision `EM_68K` fails with "unsupported ELF architecture"; the source-owned fixture exercises header facts, admission refusals and the pinned profile. The first real run observed Ghidra selecting `68000:BE:32:Coldfire` and the handshake refusing it, which motivated the pin. - User-visible CLI/MCP output (if applicable): `open_binary` returns `architecture: "m68k"`; `rea instructions` lists the fixed MOVE.L/short BRA bytes; snapshot parameters carry `m68k_elf`, `m68k_support_lane` and `provider-pinned-v1`. - Remaining proof gaps: one hand-built fixture only; no real 68000/68020/68030 corpus; MC68060-only semantics unverified; classic containers unsupported; the real run is on Ghidra 12.1.2 while the repository's verified build is 12.1.4. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run verify:ghidra:m68k` — passed (Ghidra 12.1.2, JDK 21.0.12.1; language `68000:BE:32:default`, mappings, probe and data bytes, snapshot and CLI/MCP parity, clean process lineage). - `npx vitest run --project domain --project services --project adapters --project composition --project conformance --project evaluation` — 6314 passed, 4 skipped; a pre-existing failure set in `src/domain/reconstructionVerification.functionSources.test.ts` (5 tests) reproduces unchanged on current `main` and is unrelated to this diff. - `npm run check:fast` — passed (typecheck, lint, module boundaries). - `npm run docs:check` — passed. - `npx oxfmt --check .` — passes; the two inherited upstream formatting failures were repaired by upstream `8fef2aa` (#2938). - Rebased onto current `main` (`8fef2aa`); the branch is no longer conflicted. ## Compatibility, safety, and release - Breaking changes or migration steps: none; the architecture enum addition is additive. - Real Hopper/Ghidra, browser, or OS coverage: real Ghidra 12.1.2 + JDK 21.0.12.1 on Linux x64; no Hopper or browser coverage claimed. - Package or release metadata impact: new `verify:ghidra:m68k` npm script only; no runtime dependency change. - Security, privacy, process, or containment review: no network, no target execution, no mutation; existing ephemeral-provider lifecycle and cleanup rules apply. ## 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#5498
No description provided.