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

[GH-ISSUE #3578] [Bug] Hopper 6.6.0 Fedora feed main_exe_hash disagrees with the signed RPM launcher #1327

New issue
Closed
opened 2026-10-16 21:04:20 +00:00 by bsakaguchi · 5 comments
bsakaguchi commented 2026-10-16 21:04:20 +00:00
Owner
Copy link

Originally created by @N0zoM1z0 on GitHub (Oct 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3578

Area

Setup, packaging, or upgrade / external Hopper release metadata.

Observed behavior

The official public Hopper release API reports main_exe_hash=b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c for Fedora's 6.6.0 RPM. The RPM's authenticated file header and actual launcher payload instead have SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947.

Reproduction / evidence

Executed on 2026-10-14:

  1. Download the RPM and detached base64 signature selected by the official feed. The complete package verifies with GnuPG and OpenPGP.js under stable primary 7C2D73BAFAF5B9A710A69DA1A26DF815099B1BCD.
  2. In an official Fedora 44 container, query rpm -qp --nosignature --nodigest --qf '%{FILEDIGESTALGO}\n[%{FILENAMES} %{FILEDIGESTS}\n]' package.rpm: digest algorithm 8; /opt/hopper/bin/Hopper has 4d6c….
  3. Run rpm --root /tmp/installed --initdb, then rpm --root /tmp/installed --nodeps --noscripts --nosignature -i package.rpm. sha256sum /tmp/installed/opt/hopper/bin/Hopper gives the same 4d6c…. rpm -qp --scripts reports no scriptlets.
  4. REA's production package-verification probe with the actual feed row rejects it as integrity. A diagnostic copy of that row using 4d6c… passes the same signature and signed-header checks. The copied row is not a live-feed or full Fedora installer result.

Expected behavior / impact

The vendor's per-platform main_exe_hash should identify that platform's installed launcher. Until this RPM field is corrected, feed-based Fedora installation should fail before the package manager runs. Do not weaken the check or hardcode the discrepancy in REA. Ubuntu deb and Arch launcher hashes match the current field.

Environment / limitations

Linux x86_64; official Fedora 44 container; Hopper demo 6.6.0 RPM. Earliest stage: setup/provider admission. REA probe is an unmerged worktree based on ca1b2f8, not an existing release regression. No full Fedora GUI/analysis claim; this is verified external feed/package inconsistency. Relevant evidence is retained locally under /tmp/rea-linux-hopper-release-feed-20261014.

Originally created by @N0zoM1z0 on GitHub (Oct 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3578 ### Area Setup, packaging, or upgrade / external Hopper release metadata. ### Observed behavior The official [public Hopper release API](https://www.hopperapp.com/include/files-api.php?request=releases&public=true) reports `main_exe_hash=b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c` for Fedora's 6.6.0 RPM. The RPM's authenticated file header and actual launcher payload instead have SHA-256 `4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947`. ### Reproduction / evidence Executed on 2026-10-14: 1. Download the RPM and detached base64 signature selected by the official feed. The complete package verifies with GnuPG and OpenPGP.js under stable primary `7C2D73BAFAF5B9A710A69DA1A26DF815099B1BCD`. 2. In an official Fedora 44 container, query `rpm -qp --nosignature --nodigest --qf '%{FILEDIGESTALGO}\n[%{FILENAMES} %{FILEDIGESTS}\n]' package.rpm`: digest algorithm `8`; `/opt/hopper/bin/Hopper` has `4d6c…`. 3. Run `rpm --root /tmp/installed --initdb`, then `rpm --root /tmp/installed --nodeps --noscripts --nosignature -i package.rpm`. `sha256sum /tmp/installed/opt/hopper/bin/Hopper` gives the same `4d6c…`. `rpm -qp --scripts` reports no scriptlets. 4. REA's production package-verification probe with the actual feed row rejects it as `integrity`. A diagnostic copy of that row using `4d6c…` passes the same signature and signed-header checks. The copied row is not a live-feed or full Fedora installer result. ### Expected behavior / impact The vendor's per-platform `main_exe_hash` should identify that platform's installed launcher. Until this RPM field is corrected, feed-based Fedora installation should fail before the package manager runs. Do not weaken the check or hardcode the discrepancy in REA. Ubuntu deb and Arch launcher hashes match the current field. ### Environment / limitations Linux x86_64; official Fedora 44 container; Hopper demo 6.6.0 RPM. Earliest stage: setup/provider admission. REA probe is an unmerged worktree based on ca1b2f8, not an existing release regression. No full Fedora GUI/analysis claim; this is verified external feed/package inconsistency. Relevant evidence is retained locally under `/tmp/rea-linux-hopper-release-feed-20261014`.
bsakaguchi commented 2026-10-16 21:04:20 +00:00
Author
Owner
Copy link

@g9robot commented on GitHub (Oct 16, 2026):

Independent Fedora reproduction (REA 6.5.0, Fedora 44, official current feed — no workaround applied):

  • rea setup --yes --install-hopper fails fail-closed before the package manager (integrity_mismatch, appliedActions: 0). The downloaded RPM is otherwise authentic: SHA-1 933aa2502550923a865f79e837ba403494c4b4b3 matches the Fedora feed row, and publisher verification (detached PGP against pinned key 7C2D73BAFAF5B9A710A69DA1A26DF815099B1BCD) passes — the failure is exactly the launcher-digest comparison.
  • Launcher digest confirmed two ways from that same signed RPM: the RPM header %{FILEDIGESTS} for /opt/hopper/bin/Hopper and a cpio extraction both give SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947, while the feed main_exe_hash is b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c (also the launcher inside the official Arch package).
  • Both launchers share ELF Build ID 26308a094faabd038860592912f6d6ae2785dd32 and differ only from byte 41 (e_shoff) onward — a 152-byte section-layout difference, consistent with a packaging-time relayout rather than a different build.
  • This also blocks the manual route: after installing the official signed Fedora RPM directly, the provider is still refused at runtime — rea analyze <binary> --provider hopper → provider_unavailable, launch_rejection: {boundary: "publisher_verification", reason: "unsupported_hopper_build"} — and rea doctor reports hopper-version: config_drift / unsupported_hopper_build.

Net effect: Fedora users cannot use the Hopper provider at all until the feed row or the RPM is corrected. I did not weaken the check or retain modified feed metadata.

<!-- gh-comment-id:6205227293 --> @g9robot commented on GitHub (Oct 16, 2026): Independent Fedora reproduction (REA 6.5.0, Fedora 44, official current feed — no workaround applied): - `rea setup --yes --install-hopper` fails fail-closed before the package manager (`integrity_mismatch`, `appliedActions: 0`). The downloaded RPM is otherwise authentic: SHA-1 `933aa2502550923a865f79e837ba403494c4b4b3` matches the Fedora feed row, and publisher verification (detached PGP against pinned key `7C2D73BAFAF5B9A710A69DA1A26DF815099B1BCD`) passes — the failure is exactly the launcher-digest comparison. - Launcher digest confirmed two ways from that same signed RPM: the RPM header `%{FILEDIGESTS}` for `/opt/hopper/bin/Hopper` and a `cpio` extraction both give SHA-256 `4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947`, while the feed `main_exe_hash` is `b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c` (also the launcher inside the official Arch package). - Both launchers share ELF Build ID `26308a094faabd038860592912f6d6ae2785dd32` and differ only from byte 41 (`e_shoff`) onward — a 152-byte section-layout difference, consistent with a packaging-time relayout rather than a different build. - This also blocks the manual route: after installing the official signed Fedora RPM directly, the provider is still refused at runtime — `rea analyze <binary> --provider hopper` → `provider_unavailable`, `launch_rejection: {boundary: "publisher_verification", reason: "unsupported_hopper_build"}` — and `rea doctor` reports `hopper-version: config_drift` / `unsupported_hopper_build`. Net effect: Fedora users cannot use the Hopper provider at all until the feed row or the RPM is corrected. I did not weaken the check or retain modified feed metadata.
bsakaguchi commented 2026-10-31 00:30:38 +00:00
Author
Owner
Copy link

@singhaditya73 commented on GitHub (Oct 18, 2026):

Corroborating on the released package (not a worktree): rea-agents 6.7.0 on Fedora 44 x86_64 (Node 24.22.0).

rea setup --yes --client opencode --install-hopper → status: needs_human, appliedActions: [], exit 1:

code: integrity_mismatch
remediation: "The signed rpm package launcher SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947 differs from the release main_exe_hash b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c. The Hopper download failed integrity verification. Retry setup; if it repeats, update REA before installing."

Independent checks agree with the report:

  • RPM SHA-1 933aa2502550923a865f79e837ba403494c4b4b3 == feed file_hash (authentic bytes); RPM opt/hopper/bin/Hopper == 4d6c23b6….
  • .deb opt/hopper/bin/Hopper == b2271008… (feed main_exe_hash).
  • Extra datapoint for "same launcher": the RPM and deb launchers report the same ELF BuildID (26308a094faabd038860592912f6d6ae2785dd32) — consistent with one build re-signed (6.6.0 changelog: "Packages are now signed") while the feed carries a single main_exe_hash shared by Ubuntu/Fedora/Arch.

Confirming there is no launcher-path workaround on Fedora either: pointing HOPPER_LAUNCHER_PATH at the hash-matching .deb launcher still fails rea doctor's hopper-version with reason integrity (the same RPM hashes), because inspectLauncher re-verifies the Fedora family package. So the block is precisely as described, and the minimal fix is the vendor's per-platform field (or per-family fields), not relaxing the check.

Not weakening the check / not hardcoding the discrepancy is the right call. Minor note: 6.7.0 still surfaces the top-level remediation "update REA", which is not actionable when 6.7.0 is already the latest release.

<!-- gh-comment-id:6248326882 --> @singhaditya73 commented on GitHub (Oct 18, 2026): Corroborating on the **released** package (not a worktree): `rea-agents` **6.7.0** on **Fedora 44 x86_64** (Node 24.22.0). `rea setup --yes --client opencode --install-hopper` → `status: needs_human`, `appliedActions: []`, exit 1: ``` code: integrity_mismatch remediation: "The signed rpm package launcher SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947 differs from the release main_exe_hash b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c. The Hopper download failed integrity verification. Retry setup; if it repeats, update REA before installing." ``` Independent checks agree with the report: - RPM SHA-1 `933aa2502550923a865f79e837ba403494c4b4b3` == feed `file_hash` (authentic bytes); RPM `opt/hopper/bin/Hopper` == `4d6c23b6…`. - `.deb` `opt/hopper/bin/Hopper` == `b2271008…` (feed `main_exe_hash`). - Extra datapoint for "same launcher": the RPM and deb launchers report the **same ELF BuildID** (`26308a094faabd038860592912f6d6ae2785dd32`) — consistent with one build re-signed (6.6.0 changelog: "Packages are now signed") while the feed carries a single `main_exe_hash` shared by Ubuntu/Fedora/Arch. Confirming there is **no launcher-path workaround** on Fedora either: pointing `HOPPER_LAUNCHER_PATH` at the hash-matching `.deb` launcher still fails `rea doctor`'s `hopper-version` with reason `integrity` (the same RPM hashes), because `inspectLauncher` re-verifies the Fedora family package. So the block is precisely as described, and the minimal fix is the vendor's per-platform field (or per-family fields), not relaxing the check. Not weakening the check / not hardcoding the discrepancy is the right call. Minor note: 6.7.0 still surfaces the top-level remediation "update REA", which is not actionable when 6.7.0 is already the latest release.
bsakaguchi commented 2026-10-31 00:30:39 +00:00
Author
Owner
Copy link

@ghost commented on GitHub (Oct 19, 2026):

Third independent reproduction — Fedora 45, REA 6.7.0 (released)

Adding a datapoint on a newer Fedora release: same failure, same digests, deterministic across retries, no workaround applied. Observed 2026-10-19.

Environment

  • Fedora 45 (kernel 7.2.10-300.fc45.x86_64, x86_64)
  • Node v24.21.0, npm 11.19.0
  • rea-agents 6.7.0 (current npm latest — the remediation's "update REA" path is not actionable)
  • Client: OpenCode — rea setup --client opencode --install-hopper --yes

Reproduction (run twice; identical outcome both times)

npx -y rea-agents@latest setup --client opencode --install-hopper --yes

Result

  • Exit code 1, status: "needs_human", code: "integrity_mismatch", appliedActions: [] — fail-closed before anything is installed or written.
  • Remediation, verbatim:

The signed rpm package launcher SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947 differs from the release main_exe_hash b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c. The Hopper download failed integrity verification. Retry setup; if it repeats, update REA before installing.

Both digests match the report and the earlier corroborations exactly (4d6c… launcher from the signed RPM vs b227… feed main_exe_hash).

Additional observations

  • xorg-x11-server-Xvfb 21.1.25-1.fc45 is already installed and the doctor's demo-runtime probe reports healthy (strategy=direct, ready); the only blocker is the launcher-digest mismatch.
  • The pre-existing, unverified /opt/hopper/bin/Hopper installation (reported by rea doctor as unsupported_hopper_build) was left untouched; the failed run changed nothing.
  • No ~/.cache/rea artifacts were retained after the failure, so there is nothing to attach from this host.

Happy to run further diagnostics if that helps.

<!-- gh-comment-id:6260190210 --> @ghost commented on GitHub (Oct 19, 2026): **Third independent reproduction — Fedora 45, REA 6.7.0 (released)** Adding a datapoint on a newer Fedora release: same failure, same digests, deterministic across retries, no workaround applied. Observed 2026-10-19. **Environment** - Fedora 45 (kernel `7.2.10-300.fc45.x86_64`, x86_64) - Node `v24.21.0`, npm `11.19.0` - `rea-agents` `6.7.0` (current npm `latest` — the remediation's "update REA" path is not actionable) - Client: OpenCode — `rea setup --client opencode --install-hopper --yes` **Reproduction** (run twice; identical outcome both times) ``` npx -y rea-agents@latest setup --client opencode --install-hopper --yes ``` **Result** - Exit code `1`, `status: "needs_human"`, `code: "integrity_mismatch"`, `appliedActions: []` — fail-closed before anything is installed or written. - Remediation, verbatim: > The signed rpm package launcher SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947 differs from the release main_exe_hash b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c. The Hopper download failed integrity verification. Retry setup; if it repeats, update REA before installing. Both digests match the report and the earlier corroborations exactly (`4d6c…` launcher from the signed RPM vs `b227…` feed `main_exe_hash`). **Additional observations** - `xorg-x11-server-Xvfb` 21.1.25-1.fc45 is already installed and the doctor's demo-runtime probe reports healthy (`strategy=direct`, ready); the only blocker is the launcher-digest mismatch. - The pre-existing, unverified `/opt/hopper/bin/Hopper` installation (reported by `rea doctor` as `unsupported_hopper_build`) was left untouched; the failed run changed nothing. - No `~/.cache/rea` artifacts were retained after the failure, so there is nothing to attach from this host. Happy to run further diagnostics if that helps.
bsakaguchi commented 2026-10-31 00:30:39 +00:00
Author
Owner
Copy link

@neuroben commented on GitHub (Oct 23, 2026):

Hopper RPM integrity mismatch — Fedora 44, REA 6.7.0, OpenCode

Additional independent reproduction — Fedora 44, REA 6.7.0 (released)

Confirming the same Hopper installation failure on Fedora 44. Both SHA-256 digests match the previously reported values exactly. Observed 2026-10-23.

Environment

  • Fedora 44 (Linux x86_64)
  • Node.js v22.22.2, npm 10.9.7
  • rea-agents 6.7.0
  • Client: OpenCode
  • Ghidra 12.1.4, Java 25.0.4.1
  • REA skill v42

Reproduction

npx -y rea-agents@latest setup --client opencode

Approved the proposed changes, including the Hopper deep-analysis provider installation.

Result

Hopper installation failed during integrity verification:

The signed rpm package launcher SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947 differs from the release main_exe_hash b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c. The Hopper download failed integrity verification. Retry setup; if it repeats, update REA before installing.

Both digests match the earlier reports:

  • RPM launcher SHA-256: 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947
  • Release main_exe_hash: b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c

Additional observations

  • Ghidra 12.1.4 passes all REA provider checks, including headless analysis, native decompiler, and Java compatibility.
  • Re-running setup without the Hopper installation successfully configured OpenCode and installed the REA skill.
  • The subsequent diagnostic reports healthy: true, with the OpenCode MCP registration and REA skill v42 both aligned.
  • Hopper remains unavailable (missing_analysis_engine).
  • REA 6.7.0 is already installed, so the suggested remediation to update REA does not provide an actionable fix for this version.

This appears consistent with the previously reported RPM launcher hash mismatch rather than a Fedora-specific configuration issue.

Happy to provide additional diagnostic output if needed.

<!-- gh-comment-id:6364650600 --> @neuroben commented on GitHub (Oct 23, 2026): ## Hopper RPM integrity mismatch — Fedora 44, REA 6.7.0, OpenCode **Additional independent reproduction — Fedora 44, REA 6.7.0 (released)** Confirming the same Hopper installation failure on Fedora 44. Both SHA-256 digests match the previously reported values exactly. Observed 2026-10-23. ### Environment - Fedora 44 (Linux x86_64) - Node.js `v22.22.2`, npm `10.9.7` - `rea-agents` `6.7.0` - Client: OpenCode - Ghidra `12.1.4`, Java `25.0.4.1` - REA skill v42 ### Reproduction ```bash npx -y rea-agents@latest setup --client opencode ``` Approved the proposed changes, including the Hopper deep-analysis provider installation. ### Result Hopper installation failed during integrity verification: > The signed rpm package launcher SHA-256 4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947 differs from the release main_exe_hash b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c. The Hopper download failed integrity verification. Retry setup; if it repeats, update REA before installing. Both digests match the earlier reports: - **RPM launcher SHA-256:** `4d6c23b6ab4f50b811bb454956f56871737976d6655a44098ba1978baad12947` - **Release `main_exe_hash`:** `b2271008fb82bf14cfae5c3644cdde2b11fc6804bd7c99d67032ec1b1942d53c` ### Additional observations - Ghidra 12.1.4 passes all REA provider checks, including headless analysis, native decompiler, and Java compatibility. - Re-running setup without the Hopper installation successfully configured OpenCode and installed the REA skill. - The subsequent diagnostic reports `healthy: true`, with the OpenCode MCP registration and REA skill v42 both aligned. - Hopper remains unavailable (`missing_analysis_engine`). - REA 6.7.0 is already installed, so the suggested remediation to update REA does not provide an actionable fix for this version. This appears consistent with the previously reported RPM launcher hash mismatch rather than a Fedora-specific configuration issue. Happy to provide additional diagnostic output if needed.
bsakaguchi commented 2026-10-31 00:30:39 +00:00
Author
Owner
Copy link

@morluto commented on GitHub (Oct 26, 2026):

Thank you for the careful signature, RPM-header, and installed-payload checks. The same Fedora 6.6.0 feed/hash mismatch is now also tracked alongside the download problem in #7077, so I am consolidating discussion there. Your evidence and the original report remain linked, including the observation that the Ubuntu and Arch launcher hashes matched in this check. This closure does not mean the vendor metadata has been corrected or that package verification should be weakened; please reopen if there is a distinct remaining Fedora-specific issue.

<!-- gh-comment-id:6428590389 --> @morluto commented on GitHub (Oct 26, 2026): Thank you for the careful signature, RPM-header, and installed-payload checks. The same Fedora 6.6.0 feed/hash mismatch is now also tracked alongside the download problem in #7077, so I am consolidating discussion there. Your evidence and the original report remain linked, including the observation that the Ubuntu and Arch launcher hashes matched in this check. This closure does not mean the vendor metadata has been corrected or that package verification should be weakened; please reopen if there is a distinct remaining Fedora-specific issue.
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#1327
No description provided.