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 #6152] [MERGED] fix(artifacts): refuse thin Mach-O extraction before inventory #7166

New issue
Closed
opened 2026-11-01 21:45:52 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:45:52 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6152
Author: @viniciusdsandrade
Created: 10/21/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: fix/6098-thin-macho-extraction-reader

📝 Commits (4)

  • 65ff901 fix(artifacts): refuse thin Mach-O extraction before inventory
  • 7799905 test(artifacts): cover the thin Mach-O extraction refusal
  • f6e3128 fix(artifacts): keep embedded packs behind a thin Mach-O extractable
  • acd3054 test(artifacts): cover a thin Mach-O PyInstaller onefile extraction

📊 Changes

2 files changed (+83 additions, -6 deletions)

View changed files

📝 src/artifacts/extraction/ArtifactExtraction.ts (+7 -6)
📝 tests/boundary/providers/native/artifactProvider.extractionFormat.test.ts (+76 -0)

📄 Description

Summary

Fixes #6098

extract_artifact disagreed with its own inventory for a thin Mach-O. inspect_artifact lists a thin Mach-O as one root occurrence with no child entries, while extraction routed the same file through the universal slice reader, which yields a slices/<arch> entry that the root-only inventory never recorded. The writer then failed with integrity_mismatch (Regular artifact entry is missing from inventory: slices/arm64e) and recommended an integrity policy retry that returns the same failure.

Extraction now admits only mach-o-universal to the slice reader. A thin mach-o target receives the typed refusal other formats without an extraction reader already get, AnalysisUnsupportedTargetError with reason Artifact format has no extraction reader: mach-o, before any inventory or output work.

Problem and expected behavior

  • Smallest trigger: rea extract-artifact <thin Mach-O> --json (the issue used lipo /bin/echo -thin arm64e).
  • Violated invariant: extraction must materialize the inventory it scanned. src/artifacts/inventory/reader.ts selects MachOSliceArtifactReader only for mach-o-universal, but requireExtractableFormat admitted both Mach-O formats through isMachOFormat, and createReader fell through to the slice reader for the thin file.
  • Expected: a truthful typed refusal that does not report unchanged source bytes as corrupt and does not recommend --integrity-policy record-and-continue.

Change and scope

  • src/artifacts/extraction/ArtifactExtraction.ts: requireExtractableFormat treats only mach-o-universal as having an extraction reader, matching the inventory reader selection. A thin mach-o takes the same embedded-pack probe as ELF and PE: a detected PyInstaller CArchive or Godot PCK proceeds to inventory, whose pyinstaller or godot-pck root selects that reader before the Mach-O fallback, so onefile executables with a thin Mach-O bootloader stay extractable. The now unused isMachOFormat import is removed.
  • tests/boundary/providers/native/artifactProvider.extractionFormat.test.ts: a thin arm64e Mach-O image is refused with the typed unsupported-target error and no output directory is created; a thin Mach-O bootloader followed by a CArchive still extracts its hello member.
  • Not included: merging the extraction and inventory reader selections into one function. They differ by design beyond this format: extraction refuses before inventory runs and never admits DMG, while inventory tolerates a missing reader by reporting unknown coverage. Returning an empty successful extraction for root-only artifacts is also not included, because ELF and PE targets without a packaged payload already receive this refusal and a thin Mach-O should not diverge from them.

Follow the contribution scope.
Scope decision: not applicable (ordinary fix within the existing artifact extraction boundary).

Contract and boundary impact

  • Semantic owner and earliest changed stage: requireExtractableFormat in src/artifacts/extraction/ArtifactExtraction.ts, before inventory scanning.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: schemas unchanged. For a thin Mach-O, extract_artifact and rea extract-artifact now return the existing unsupported-target error instead of integrity_mismatch.
  • Provider, bridge, target-format, or platform compatibility: thin Mach-O extraction on every platform; universal Mach-O extraction is unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: no false integrity contradiction is reported for an unchanged thin Mach-O.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable; the refusal happens before any reader or output owner exists.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

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: tests/boundary/providers/native/artifactProvider.extractionFormat.test.ts, refuses a thin Mach-O that inventory lists as root-only and keeps a thin Mach-O PyInstaller onefile extractable.
  • Base reproduction or other evidence: source-derived. On the base revision requireExtractableFormat admits mach-o through isMachOFormat and createReader falls through to MachOSliceArtifactReader, whose entries yields slices/${architecture.name} for the single architecture lipo reports (src/artifacts/MachOSliceArtifactReader.ts). writeSelectedEntries then throws the integrity failure because the root-only inventory has no such path. The issue reports that failure from the built CLI on macOS with real lipo. By reading, the refusal test would reach the slice reader on the base revision instead of the asserted AnalysisUnsupportedTargetError. The PyInstaller test passes on the base revision and guards the review finding that a refusal of every thin Mach-O would have dropped embedded packs.
  • User-visible CLI/MCP output (if applicable): a thin Mach-O now reports Artifact format has no extraction reader: mach-o, the same error shape rea extract-artifact Image.dmg already produces.
  • Remaining proof gaps: no real lipo run and no CLI replay in this PR.

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

  • No local commands were run; verification is source-derived and CI executes the test suite. The repository pre-commit hook formatted and linted the staged files without changes.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. A thin Mach-O never extracted successfully; only the failure category changes from integrity_mismatch to the unsupported-target refusal.
  • Real Hopper/Ghidra, browser, or OS coverage: none run.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no change to process ownership or output handling.

Author readiness

Human owner: @viniciusdsandrade

  • 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/6152 **Author:** [@viniciusdsandrade](https://github.com/viniciusdsandrade) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/6098-thin-macho-extraction-reader` --- ### 📝 Commits (4) - [`65ff901`](https://github.com/morluto/rea/commit/65ff90122f8d755feca7b9d210373c4a941e7cb3) fix(artifacts): refuse thin Mach-O extraction before inventory - [`7799905`](https://github.com/morluto/rea/commit/7799905fead7ea0567394cd79315f3072eaa39f7) test(artifacts): cover the thin Mach-O extraction refusal - [`f6e3128`](https://github.com/morluto/rea/commit/f6e3128e97344f77a260cf6ececd134b0845b52f) fix(artifacts): keep embedded packs behind a thin Mach-O extractable - [`acd3054`](https://github.com/morluto/rea/commit/acd3054d3c799dbe955671b87b23ab8672c49d7b) test(artifacts): cover a thin Mach-O PyInstaller onefile extraction ### 📊 Changes **2 files changed** (+83 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `src/artifacts/extraction/ArtifactExtraction.ts` (+7 -6) 📝 `tests/boundary/providers/native/artifactProvider.extractionFormat.test.ts` (+76 -0) </details> ### 📄 Description ## Summary Fixes #6098 `extract_artifact` disagreed with its own inventory for a thin Mach-O. `inspect_artifact` lists a thin Mach-O as one root occurrence with no child entries, while extraction routed the same file through the universal slice reader, which yields a `slices/<arch>` entry that the root-only inventory never recorded. The writer then failed with `integrity_mismatch` (`Regular artifact entry is missing from inventory: slices/arm64e`) and recommended an integrity policy retry that returns the same failure. Extraction now admits only `mach-o-universal` to the slice reader. A thin `mach-o` target receives the typed refusal other formats without an extraction reader already get, `AnalysisUnsupportedTargetError` with reason `Artifact format has no extraction reader: mach-o`, before any inventory or output work. ## Problem and expected behavior - Smallest trigger: `rea extract-artifact <thin Mach-O> --json` (the issue used `lipo /bin/echo -thin arm64e`). - Violated invariant: extraction must materialize the inventory it scanned. `src/artifacts/inventory/reader.ts` selects `MachOSliceArtifactReader` only for `mach-o-universal`, but `requireExtractableFormat` admitted both Mach-O formats through `isMachOFormat`, and `createReader` fell through to the slice reader for the thin file. - Expected: a truthful typed refusal that does not report unchanged source bytes as corrupt and does not recommend `--integrity-policy record-and-continue`. ## Change and scope - `src/artifacts/extraction/ArtifactExtraction.ts`: `requireExtractableFormat` treats only `mach-o-universal` as having an extraction reader, matching the inventory reader selection. A thin `mach-o` takes the same embedded-pack probe as ELF and PE: a detected PyInstaller CArchive or Godot PCK proceeds to inventory, whose `pyinstaller` or `godot-pck` root selects that reader before the Mach-O fallback, so onefile executables with a thin Mach-O bootloader stay extractable. The now unused `isMachOFormat` import is removed. - `tests/boundary/providers/native/artifactProvider.extractionFormat.test.ts`: a thin arm64e Mach-O image is refused with the typed unsupported-target error and no output directory is created; a thin Mach-O bootloader followed by a CArchive still extracts its `hello` member. - Not included: merging the extraction and inventory reader selections into one function. They differ by design beyond this format: extraction refuses before inventory runs and never admits DMG, while inventory tolerates a missing reader by reporting unknown coverage. Returning an empty successful extraction for root-only artifacts is also not included, because ELF and PE targets without a packaged payload already receive this refusal and a thin Mach-O should not diverge from them. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Scope decision: not applicable (ordinary fix within the existing artifact extraction boundary). ## Contract and boundary impact - Semantic owner and earliest changed stage: `requireExtractableFormat` in `src/artifacts/extraction/ArtifactExtraction.ts`, before inventory scanning. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: schemas unchanged. For a thin Mach-O, `extract_artifact` and `rea extract-artifact` now return the existing unsupported-target error instead of `integrity_mismatch`. - Provider, bridge, target-format, or platform compatibility: thin Mach-O extraction on every platform; universal Mach-O extraction is unchanged. - Evidence, artifact, provenance, or reconstruction contract: no false integrity contradiction is reported for an unchanged thin Mach-O. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable; the refusal happens before any reader or output owner exists. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. 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. - [ ] 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: `tests/boundary/providers/native/artifactProvider.extractionFormat.test.ts`, `refuses a thin Mach-O that inventory lists as root-only` and `keeps a thin Mach-O PyInstaller onefile extractable`. - Base reproduction or other evidence: source-derived. On the base revision `requireExtractableFormat` admits `mach-o` through `isMachOFormat` and `createReader` falls through to `MachOSliceArtifactReader`, whose `entries` yields `slices/${architecture.name}` for the single architecture lipo reports (`src/artifacts/MachOSliceArtifactReader.ts`). `writeSelectedEntries` then throws the integrity failure because the root-only inventory has no such path. The issue reports that failure from the built CLI on macOS with real lipo. By reading, the refusal test would reach the slice reader on the base revision instead of the asserted `AnalysisUnsupportedTargetError`. The PyInstaller test passes on the base revision and guards the review finding that a refusal of every thin Mach-O would have dropped embedded packs. - User-visible CLI/MCP output (if applicable): a thin Mach-O now reports `Artifact format has no extraction reader: mach-o`, the same error shape `rea extract-artifact Image.dmg` already produces. - Remaining proof gaps: no real lipo run and no CLI replay in this PR. 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 - No local commands were run; verification is source-derived and CI executes the test suite. The repository pre-commit hook formatted and linted the staged files without changes. ## Compatibility, safety, and release - Breaking changes or migration steps: none. A thin Mach-O never extracted successfully; only the failure category changes from `integrity_mismatch` to the unsupported-target refusal. - Real Hopper/Ghidra, browser, or OS coverage: none run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no change to process ownership or output handling. ## Author readiness Human owner: @viniciusdsandrade - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:45:52 +00:00
bsakaguchi changed title from [PR #6152] [MERGED] fix(artifacts): refuse thin Mach-O extraction before inventory to [PR #6152] fix(artifacts): refuse thin Mach-O extraction before inventory 2026-11-04 16:32:31 +00:00
bsakaguchi changed title from [PR #6152] fix(artifacts): refuse thin Mach-O extraction before inventory to [PR #6152] [MERGED] fix(artifacts): refuse thin Mach-O extraction before inventory 2026-11-04 17:28:36 +00:00
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#7166
No description provided.