[PR #5582] [CLOSED] fix(apple): trace LC_LAZY_LOAD_DYLIB_INFO lazy dylib dependencies #6979

New issue

Closed

opened 2026-11-01 21:44:27 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:44:27 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5582
Author: @kaoru0822-kitauji
Created: 10/20/2026
Status: ❌ Closed

Base: main ← Head: fix/dylib-lazy-load-commands

---

📝 Commits (1)

• 1ede7a0 fix(apple): trace LC_LAZY_LOAD_DYLIB_INFO lazy dylib dependencies

📊 Changes

8 files changed (+364 additions, -21 deletions)

View changed files

📝 docs/apple-application-analysis.md (+6 -3)
📝 src/artifacts/apple/MachoImage.fixture.ts (+67 -2)
📝 src/artifacts/apple/MachoLoadCommandReader.test.ts (+93 -0)
📝 src/artifacts/apple/MachoLoadCommandReader.ts (+109 -6)
📝 src/domain/apple/dylibResolution.test.ts (+1 -0)
📝 src/domain/apple/dylibResolution.ts (+13 -5)
📝 src/domain/apple/dylibResolutionFindings.ts (+6 -4)
📝 tests/boundary/cli/dylibResolutionCli.test.ts (+69 -1)

📄 Description

Summary

Fixes #5551

trace-dylib-resolution dropped dylibs linked with -lazy_library by current Apple linkers, but still reported coverage.status: "complete". These linkers encode the dependency as LC_LAZY_LOAD_DYLIB_INFO (0x3a) rather than the legacy LC_LAZY_LOAD_DYLIB (0x20). The dependency now shows up as a lazy edge. It resolves when the dylib is present. When the dylib is absent, the result has a lazy-load-unresolved finding, which stays distinct from a launch failure.

Problem and expected behavior

LC_LAZY_LOAD_DYLIB_INFO is a linkedit_data_command that points to a __LINKEDIT blob. That blob is dyld's LazyLoadDylibLinkEdit record: loadPathOffset, flagImageOffset, flags, pointerFormat, chainStartImageOffset, symbolsCount, symbolStringArrayOffset, followed by the path and symbol strings. The format is defined in apple-oss-distributions/dyld mach_o/LazyLoadDylib.{h,cpp}. MachoLoadCommandReader skipped unrecognized commands, so it never emitted this dependency. The trace then derived complete coverage from the dependencies it did emit.

Change and scope

• Parser (owning boundary): MachoLoadCommandReader now reads each LC_LAZY_LOAD_DYLIB_INFO payload, in load-command order, as a dependency with command: "LC_LAZY_LOAD_DYLIB_INFO" and encoding: "lazy_load_dylib_info".
  • Validation follows LazyLoadDylib::valid(): header size, path offset and termination, symbol-array bounds, and data inside the slice. It skips the flag and chain-start VM-offset checks, because they need the VM layout and do not change which dylib is named.
  • flags & 1 (dylibMayBeMissing) maps to weak.
  • Payloads over the existing 16 MiB limit are reported as unsupported.
• Lazy flag set once in the parser: dependencies get a parsed lazy boolean, set for both lazy commands. traceProcess and the findings now use lazy instead of comparing command names.
• Weak lazy dylibs: a missing weak lazy-info dylib gets a "continues without it" explanation, because dyld's _dyld_lazy_load halts only when the dylib is not weak.
• Null versions: lazy-info records carry no dylib versions, so current_version and compatibility_version are now nullable and are null for this encoding.
• Not included: native inspect_macho, which goes through otool -l, still does not list lazy-info dependencies. That is a separate parser and tool contract, left for a follow-up.

Scope: an ordinary fix within existing boundaries; no maintainer scope decision is needed.

Contract and boundary impact

• Semantic owner and earliest changed stage: src/artifacts/apple/MachoLoadCommandReader.ts (Mach-O load-command parsing).
• Contribution scope fit and linked maintainer decision: not applicable (bug fix inside the existing static-parsing tool).
• CLI and MCP/tool-catalog contract: additive changes to the trace_dylib_resolution output schema:
  • a new command enum value and a new encoding enum value;
  • a new lazy boolean on each edge;
  • current_version and compatibility_version are now nullable.
• Provider, bridge, target-format, or platform compatibility: Mach-O only; no Apple tool required.
• Evidence, artifact, provenance, or reconstruction contract: no change.
• Target selection, authority, upstream behavior, and cleanup details: not applicable.
• Generated metadata, package, or installation impact: none committed.

Expected effects:

• 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/cli/dylibResolutionCli.test.ts: a CLI test with a lazy-info executable. With the dylib present, the edge resolves and there are no findings. With it absent, the trace reports lazy-load-unresolved. Coverage stays complete in both cases.
  • src/artifacts/apple/MachoLoadCommandReader.test.ts: decoding, including weak flags and multiple symbols, plus each malformed-payload rejection.
  • The MachoImage.fixture.ts builder now lays out the payload exactly as Apple's linker did for the issue repro.
• Base reproduction: I rebuilt the issue repro on macOS 26.7.1 arm64 with Apple clang 21.0.0 and ld-27037.1, using -mmacosx-version-min=27.0. This linker ignores lazy-load at lower deployment targets. otool -l shows LC_LAZY_LOAD_DYLIB_INFO, datasize 56, and the payload bytes match the fixture layout. With the reader change reverted, the new reader tests fail: 4 failed / 26 passed.
• CLI output on that real binary after the fix:
  • Dylib present: edges = [LC_LOAD_DYLIB /usr/lib/libSystem.B.dylib undetermined] and [LC_LAZY_LOAD_DYLIB_INFO @rpath/libl.dylib lazy=true resolved lib/libl.dylib]; findings: []; coverage.status: "complete".
  • Dylib moved away: the lazy edge is unresolved, with lazy-load-unresolved: "No candidate for lazily loaded @rpath/libl.dylib exists in the analyzed root; dyld loads it on first use, which would fail unless the image is supplied elsewhere."
• Remaining proof gaps:
  • I did not run the binary. Its minos is 27.0 and this host runs 26.7.
  • The weak lazy-info path is checked only with synthetic bytes; no linker-produced weak lazy-info binary was tested.
  • Native inspect_macho coverage of lazy-info is not addressed.

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 test:focused -- tests/boundary/cli/dylibResolutionCli.test.ts tests/boundary/mcp/dylibResolutionMcp.test.ts src/artifacts/apple/MachoLoadCommandReader.test.ts src/domain/apple/dylibResolution.test.ts: 4 files, 153 tests passed.
• npm run test:local -- src/contracts/toolOutputReferences.test.ts src/contracts/tupleSchemaParity.test.ts: 59 passed.
• npm run check:fast: typecheck and lint passed.
• npm run docs:check: passed.
• node scripts/rea.mjs trace-dylib-resolution <clang-built lazy binary> --json, with the dylib present and absent: output as shown above.

Compatibility, safety, and release

• Breaking changes or migration steps: none intended. Output enums gain values and the version fields become nullable; a strict consumer that assumed version strings would now see null for lazy-info edges.
• Real Hopper/Ghidra, browser, or OS coverage: macOS 26.7.1 arm64 static trace of a real Apple-linker binary; no providers involved.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: read-only parsing with bounded reads (16 MiB payload limit, bounds-checked offsets).

Author readiness

Human owner: @kaoru0822-kitauji

• 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.

🤖 Generated with Claude Code

---

_{🔄 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/5582 **Author:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Created:** 10/20/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/dylib-lazy-load-commands` --- ### 📝 Commits (1) - [`1ede7a0`](https://github.com/morluto/rea/commit/1ede7a08647b485cdffe9918fdae278830bedcb8) fix(apple): trace LC_LAZY_LOAD_DYLIB_INFO lazy dylib dependencies ### 📊 Changes **8 files changed** (+364 additions, -21 deletions) <details> <summary>View changed files</summary> 📝 `docs/apple-application-analysis.md` (+6 -3) 📝 `src/artifacts/apple/MachoImage.fixture.ts` (+67 -2) 📝 `src/artifacts/apple/MachoLoadCommandReader.test.ts` (+93 -0) 📝 `src/artifacts/apple/MachoLoadCommandReader.ts` (+109 -6) 📝 `src/domain/apple/dylibResolution.test.ts` (+1 -0) 📝 `src/domain/apple/dylibResolution.ts` (+13 -5) 📝 `src/domain/apple/dylibResolutionFindings.ts` (+6 -4) 📝 `tests/boundary/cli/dylibResolutionCli.test.ts` (+69 -1) </details> ### 📄 Description ## Summary Fixes #5551 `trace-dylib-resolution` dropped dylibs linked with `-lazy_library` by current Apple linkers, but still reported `coverage.status: "complete"`. These linkers encode the dependency as `LC_LAZY_LOAD_DYLIB_INFO` (`0x3a`) rather than the legacy `LC_LAZY_LOAD_DYLIB` (`0x20`). The dependency now shows up as a lazy edge. It resolves when the dylib is present. When the dylib is absent, the result has a `lazy-load-unresolved` finding, which stays distinct from a launch failure. ## Problem and expected behavior `LC_LAZY_LOAD_DYLIB_INFO` is a `linkedit_data_command` that points to a `__LINKEDIT` blob. That blob is dyld's `LazyLoadDylibLinkEdit` record: `loadPathOffset`, `flagImageOffset`, `flags`, `pointerFormat`, `chainStartImageOffset`, `symbolsCount`, `symbolStringArrayOffset`, followed by the path and symbol strings. The format is defined in apple-oss-distributions/dyld `mach_o/LazyLoadDylib.{h,cpp}`. `MachoLoadCommandReader` skipped unrecognized commands, so it never emitted this dependency. The trace then derived complete coverage from the dependencies it did emit. ## Change and scope - **Parser (owning boundary):** `MachoLoadCommandReader` now reads each `LC_LAZY_LOAD_DYLIB_INFO` payload, in load-command order, as a dependency with `command: "LC_LAZY_LOAD_DYLIB_INFO"` and `encoding: "lazy_load_dylib_info"`. - Validation follows `LazyLoadDylib::valid()`: header size, path offset and termination, symbol-array bounds, and data inside the slice. It skips the flag and chain-start VM-offset checks, because they need the VM layout and do not change which dylib is named. - `flags & 1` (`dylibMayBeMissing`) maps to `weak`. - Payloads over the existing 16 MiB limit are reported as `unsupported`. - **Lazy flag set once in the parser:** dependencies get a parsed `lazy` boolean, set for both lazy commands. `traceProcess` and the findings now use `lazy` instead of comparing command names. - **Weak lazy dylibs:** a missing weak lazy-info dylib gets a "continues without it" explanation, because dyld's `_dyld_lazy_load` halts only when the dylib is not weak. - **Null versions:** lazy-info records carry no dylib versions, so `current_version` and `compatibility_version` are now nullable and are null for this encoding. - **Not included:** native `inspect_macho`, which goes through `otool -l`, still does not list lazy-info dependencies. That is a separate parser and tool contract, left for a follow-up. Scope: an ordinary fix within existing boundaries; no maintainer scope decision is needed. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/artifacts/apple/MachoLoadCommandReader.ts` (Mach-O load-command parsing). - Contribution scope fit and linked maintainer decision: not applicable (bug fix inside the existing static-parsing tool). - CLI and MCP/tool-catalog contract: additive changes to the `trace_dylib_resolution` output schema: - a new `command` enum value and a new `encoding` enum value; - a new `lazy` boolean on each edge; - `current_version` and `compatibility_version` are now nullable. - Provider, bridge, target-format, or platform compatibility: Mach-O only; no Apple tool required. - Evidence, artifact, provenance, or reconstruction contract: no change. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none committed. Expected effects: - [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/cli/dylibResolutionCli.test.ts`: a CLI test with a lazy-info executable. With the dylib present, the edge resolves and there are no findings. With it absent, the trace reports `lazy-load-unresolved`. Coverage stays complete in both cases. - `src/artifacts/apple/MachoLoadCommandReader.test.ts`: decoding, including weak flags and multiple symbols, plus each malformed-payload rejection. - The `MachoImage.fixture.ts` builder now lays out the payload exactly as Apple's linker did for the issue repro. - **Base reproduction:** I rebuilt the issue repro on macOS 26.7.1 arm64 with Apple clang 21.0.0 and ld-27037.1, using `-mmacosx-version-min=27.0`. This linker ignores lazy-load at lower deployment targets. `otool -l` shows `LC_LAZY_LOAD_DYLIB_INFO`, `datasize 56`, and the payload bytes match the fixture layout. With the reader change reverted, the new reader tests fail: 4 failed / 26 passed. - **CLI output on that real binary after the fix:** - Dylib present: `edges` = `[LC_LOAD_DYLIB /usr/lib/libSystem.B.dylib undetermined]` and `[LC_LAZY_LOAD_DYLIB_INFO @rpath/libl.dylib lazy=true resolved lib/libl.dylib]`; `findings: []`; `coverage.status: "complete"`. - Dylib moved away: the lazy edge is `unresolved`, with `lazy-load-unresolved`: "No candidate for lazily loaded @rpath/libl.dylib exists in the analyzed root; dyld loads it on first use, which would fail unless the image is supplied elsewhere." - **Remaining proof gaps:** - I did not run the binary. Its minos is 27.0 and this host runs 26.7. - The weak lazy-info path is checked only with synthetic bytes; no linker-produced weak lazy-info binary was tested. - Native `inspect_macho` coverage of lazy-info is not addressed. 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 test:focused -- tests/boundary/cli/dylibResolutionCli.test.ts tests/boundary/mcp/dylibResolutionMcp.test.ts src/artifacts/apple/MachoLoadCommandReader.test.ts src/domain/apple/dylibResolution.test.ts`: 4 files, 153 tests passed. - `npm run test:local -- src/contracts/toolOutputReferences.test.ts src/contracts/tupleSchemaParity.test.ts`: 59 passed. - `npm run check:fast`: typecheck and lint passed. - `npm run docs:check`: passed. - `node scripts/rea.mjs trace-dylib-resolution <clang-built lazy binary> --json`, with the dylib present and absent: output as shown above. ## Compatibility, safety, and release - Breaking changes or migration steps: none intended. Output enums gain values and the version fields become nullable; a strict consumer that assumed version strings would now see `null` for lazy-info edges. - Real Hopper/Ghidra, browser, or OS coverage: macOS 26.7.1 arm64 static trace of a real Apple-linker binary; no providers involved. - Package or release metadata impact: none. - Security, privacy, process, or containment review: read-only parsing with bounded reads (16 MiB payload limit, bounds-checked offsets). ## Author readiness Human owner: @kaoru0822-kitauji - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-11-01 21:44:27 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-01 21:48:13 +00:00

[PR #6979] [MERGED] fix(browser): report an out-of-range script_index as a selection fault #7490

bsakaguchi referenced this issue 2026-11-03 00:29:36 +00:00

[GH-ISSUE #5654] [Tracker] Open PRs that can't merge yet: conflicts and red CI (October 2026) #3425

bsakaguchi referenced this issue 2026-11-03 13:39:09 +00:00

[PR #7067] [MERGED] fix(capture): report an out-of-range record ordinal as a selection fault #7619

bsakaguchi referenced this issue 2026-11-03 13:39:29 +00:00

[PR #7133] fix(browser): report an out-of-range generated position as a selection fault #7665

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

codex/procedure-reference-stacked

release-please--branches--main--components--rea-agents

release-please--branches--main--components--rea-agents--release-notes

codex/kuna-independent-retry

codex/byte-search-overlay-coverage

codex/open-failure-target-receipt

codex/kuna-xref-evidence

codex/ghidra-ambiguous-procedure-recovery

codex/function-source-bundle

codex/trace-function-integration-prototype

codex/snapshot-source-closure

codex/recorded-evidence-array-pages

codex/evidence-recovery-redesign

codex/trace-feature-address-scope

codex/call-discovery-scope

codex/ghidra-literal-candidate-evidence

codex/decompile-directory-independent-retry

codex/retry-provenance-base

codex/value-flow-capability-experiment

codex/ghidra-containing-instruction

cursor/readme-discord-button-ef9f

dependabot/github_actions/actions/setup-node-7.1.0

dependabot/github_actions/actions/upload-artifact-7.0.2

dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df

codex/kuna-1989

fix/8559-native-ui-fixture-ownership

fix/8555-go-verifier-mcp-ownership

codex/provider-capability-recovery

fix/8642-rizin-target-stdin

codex/ghidra-memory-effect-scope

codex/ghidra-annotation-entry-selector

codex/ghidra-readonly-recovery

codex/ghidra-regex-verifier-recovery

codex/evidence-discovery-view-guidance

fix/8545-bulk-append-overflow

fix/8428-navigation-refusal-alternatives

codex/address-context-recovery

codex/matching-member-limitations

codex/unknown-scope-contract

codex/evidence-view-guidance

feat/8373-native-trace-views

codex/ghidra-snapshot-verifier-binding

codex/elf-export-visibility

codex/evidence-view-recovery

codex/native-reference-cli-help

codex/provider-candidate-observation-scope

codex/kuna-session-verification

codex/ghidra-switch-lifetime-guidance

codex/pseudocode-paging-discovery

codex/clarify-evidence-view-support

codex/kuna-xrefs-selector-recovery

codex/context-capacity-recovery

codex/evidence-closure-large-links

codex/same-function-evidence-identity

codex/ghidra-verifier-inspected-jdk

codex/audit-guided-workflows

codex/crash-prompt-retained-dossiers

codex/analysis-view-error-recovery

codex/kuna-verifier-target-selection

codex/ghidra-selected-project-call-coverage

codex/docs-native-analysis-scope

codex/ghidra-java-socket-boundary

codex/ghidra-retained-snapshot-verifier

codex/ghidra-search-inventory-facts

fix/8284-zero-argument-parameter-bindings

fix/8198-ui-action-handler-offset

fix/8257-elf-entry-label-identity

fix/8304-deferred-output-schema-projection

fix/8277-call-path-computed-target-uncertainty

fix/pr-8089-conflicts

fix/ci-static-duplicate-export

dependabot/npm_and_yarn/lint-staged-17.6.0

dependabot/github_actions/actions/download-artifact-8.0.2

dependabot/npm_and_yarn/write-file-atomic-8.0.0

dependabot/npm_and_yarn/canonicalize-5.1.0

dependabot/github_actions/actions/cache/restore-6.1.0

dependabot/npm_and_yarn/toon-format/toon-4.4.0

dependabot/github_actions/actions/deploy-pages-5.0.1

codex/review-fixes-pr-2403

codex/review-fixes-pr-2400

codex/process-terminal-width

codex/test-brittleness-cleanup

verify/7167-browser-connect-macos

fix/7167-browser-connect

feat/native-matching-allowance-setting

feat/browser-scenario-dry-run

test/managed-caller-parameters-20261024

codex/parser-fortythird-boundaries

fix/6926-pinvoke-platform-decorations-20261023

fix/6889-har-body-encoding-20261023

fix/6888-sqlite-schema-budget-20261023

fix/dependency-security-gates-6708

cursor/evidence-overwrite-rebase-b4ac

feat/4057-verify-native-exports

fix/windows-acl-observer-overhead-20261022

cursor/erlang-beam-restack-4476

cursor/pe-certificate-review-bf32

fix/6116-javascript-application-fs-errors

fix/6061-unmapped-runtime-script-unknown

feat/browser-scenario-summary

fix/pe-certificates

codex/verify-3407

cursor/rebase-5699

cursor/rebase-5352

cursor/rebase-5600

cursor/fix-cli-schema-omission-10a8

codex/audit-hopper-shutdown-reasons-20261021

fix/demangle-swift-omitted-record

fix/nib-boolean-value-types

cursor/cancellation-partial-observation-a5ac

fix/ib-object-limit-reasons

fix/electron-fuse-limit-advice

fix/kuna-doctor-dangling-cache

fix/fixed-budget-refusal-advice

fix/js-ipc-listener-dedup

fix/js-return-member-provenance

fix/dmg-integrity-retry-advice

fix/ida-doctor-readiness

fix/kuna-version-probe-output-drain

fix/legacy-swift-runtime-name-matching

fix/dylib-lazy-load-commands

fix/browser-scenario-startup-cancel

fix/swift-nested-punycode-classification

fix/compare-unselected-scopes

fix/objc-method-budget-coverage

fix/dmg-mounted-root-observations

audit/ci-tests-20261019-round2

release/6.7.0

fix/wabt-cleanup-retry-resolution

fix/electron-fuse-elf-pe-architecture

fix/native-plist-descriptor-ownership

fix/kuna-caller-cleanup-ownership

experiment/atomic-codemode-20261016

review/first-contributor-3776

fix/call-resolution-full-read-cycles

fix/member-mutation-selection-repeat

experiment/atomic-re-tools-20261015

perf/member-mutation-lazy-origins

perf/static-network-mutation-index

fix/hopper-startup-lifecycle

audit/3050-windows-proof-20261015

feat/windows-window-capture-2183

audit/3049-windows-proof-20261015

audit/3735-macos-fixtures-20261015

fix/batch-decompile-null-pseudocode

fix/kuna-inventory-honors-jobs

experiment/browser-codemode-tool-design-20261015

fix/hopper-clean-runtime-argv

codex/review-2049-27f1b367

review-fixes/pr-2787-routing

fix/3360-scoped-this-emitters

fix/3367-replaced-global-effects

fix/3838-compact-any-value-items

test/hopper-download-probe-20261015

codex/windows-runtime-creation-red-green-20261015

codex/windows-readonly-root-red-green-20261015

codex/windows-root-share-red-green-20261015

codex/exp-1685-win-mcp-startup

codex/bug-sweep-20261015

investigate/2190-windows-package-phases

investigate/3543-macos-cli-deadline

perf/3281-reverse-tools-feedback-quality

fix/3406-hopper-doctor-fixture

fix/3341-wrapper-require-test-context

fix/3301-owned-uninstall-fixtures

fix/3164-compiler-input-ownership

fix/pcap-cleanup-stdout-newline-20261014

perf/interface-builder-summary

codex/review-fixes-pr-1977

fix/ghidra-effective-jvm-platform

fix/docs-turkish-rust-link-20261013

fix/main-maintenance-ci-20261010

fix/recover-binary-session-process-effects

codex/review-fixes-pr-2457

codex/ci-required-cancellation-gate

fix/main-format-baseline-20261013

fix/setup-preserve-entry-fields

cursor/restore-main-checks-1ffc

fix/ghidra-bridge-hashmap-import

codex/shared-ci-jadx-json-default-20261013

codex/shared-ci-ghidra-test-groups-20261013

codex/shared-ci-java-fixture-format-20261013

codex/fix-intrinsic-invocation-boundaries

test/release-preflight-reusable-jobs

test/js-parameter-provenance-expectation

fix/linux-hopper-verification-current

test/2419-ghidra-elf-probe-size

followup/pr-1544-native-ida

codex/fold-pr-2230-contribution

docs/readme-responsible-use

fix/issue-2064

fix/issue-2050

fix/issue-2053

fix/issue-1968

fix/issue-1945

experiment/codemode-bridge-20261011

fix/tool-effects-negative-wording-1904-20261012

fix/1842-electron-interop-provenance

feat/recover-javascript-multi-input

refactor/website-i18n-prep

fix/nativeaot-pe-virtual-extent

fix/browser-verifier-ci-hang

fix/pe-resources-input-selection

docs/beginner-friendly-guides

docs/beginner-setup-guide

fix/javascript-analysis-worker-1563

fix/1649-ghidra-duplicate-names

fix/javascript-export-keys-integration-1369

test/maintenance-boundary-contracts-20261011

review/javascript-export-keys-1369

review/process-live-progress-1483

test/javascript-1495-growth-ratio

fix/ci-escape-timing

docs/normalized-terminal-geometry-1450

release/6.3.0

archive/release-6.3.0-pr1381

release/6.2.0

fix/electron-preload-dynamic-override

fix/javascript-self-referential-bundler-edges

release/6.1.0

cursor/grok-client-cherry-pick-0b56

feat/signature-posture

feat/dyld-shared-cache

feat/artifact-integrity-policy

feat/pkg-inventory

release/6.0.0

chore/sync-release-5.0.0

release/5.0.0

cursor/cloud-agent-node-787e

fix/javascript-xhr-open-endpoints

review/pr-711-realpath-fallback-wording

cleanup/replay-confinement

codex/test-suite-performance

codex/issue-foundations

codex/address-open-issues-2026-07-20

agent/javascript-vite-rollup-esbuild-adapters

agent/process-cleanup

agent/triage-integration

agent/unknown-commands-registry

feat/mcp-identity-metadata

morlvps/issue_cleanup

codex/installer-redesign

morl/roadmap-investigation-core

morl/roadmap-investigation-docs

release-please--branches--main--components--rea

rea-agents-6.8.0

rea-agents-6.7.0

rea-agents-6.6.0

experiment/atomic-codemode-wait-runtime-20261016

rea-agents-6.5.0

rea-agents-6.4.0

rea-agents-6.3.0

rea-agents-6.2.0

rea-agents-6.1.0

rea-agents-6.0.0

rea-agents-5.0.0

rea-agents-4.1.0

rea-agents-4.0.1

rea-agents-4.0.0

rea-agents-3.2.1

rea-agents-3.2.0

rea-agents-3.1.0

rea-agents-3.0.0

rea-agents-2.7.0

rea-agents-2.6.0

rea-agents-2.5.1

rea-agents-2.5.0

rea-agents-2.4.0

rea-agents-2.3.0

rea-agents-2.2.0

rea-agents-2.1.0

rea-agents-2.0.0

rea-agents-1.7.0

rea-agents-1.6.0

rea-agents-1.5.0

rea-agents-1.4.0

rea-agents-1.3.0

rea-agents-1.2.0

rea-agents-1.1.0

rea-agents-1.0.0

rea-agents-0.5.0

rea-agents-0.4.0

rea-agents-0.3.0

rea-0.2.1

rea-0.2.0

Labels

Clear labels   

area: bridge

  

area: bridge

  

area: build

  

area: build

  

area: build

  

area: cli

  

area: domain

  

area: evidence

  

area: mcp

  

area: native

  

area: providers

  

area: runtime

  

area: server

  

area: setup

  

area: tests

  

bug

  

design

  

documentation

  

enhancement

  

enhancement

  

enhancement

  

experiment

  

help wanted

  

i18n

  

invalid

  

P0: critical

  

P1: high

  

P2: medium

  

P2: medium

  

P2: medium

  

P3: low

  

performance

  

provider-request

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

roadmap

  

triage

No labels

area: bridge

area: bridge

area: build

area: build

area: build

area: cli

area: domain

area: evidence

area: mcp

area: native

area: providers

area: runtime

area: server

area: setup

area: tests

bug

design

documentation

enhancement

enhancement

enhancement

experiment

help wanted

i18n

invalid

P0: critical

P1: high

P2: medium

P2: medium

P2: medium

P3: low

performance

provider-request

pull-request

question

roadmap

triage

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#6979

No description provided.