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 #6175] [MERGED] fix(model): keep host I/O failures distinct from unavailable model targets #7184

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

📋 Pull Request Information

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

Base: main ← Head: fix/6004-model-host-io-errors

📝 Commits (1)

  • 9adee5c fix(model): keep host I/O failures distinct from unavailable model targets

📊 Changes

3 files changed (+157 additions, -2 deletions)

View changed files

📝 docs/model-artifacts.md (+4 -1)
📝 src/model/ModelArtifactProvider.ts (+16 -1)
➕ tests/process-global/modelHostReadFailure.test.ts (+137 -0)

📄 Description

Summary

inspect_model_artifact reported host I/O and resource failures on a valid selected model (for example EMFILE at open or EIO at header read) as target_unavailable / unavailable, with advice to check that the path exists and is readable. Those failures now reach the provider's existing execution_failure fallback with the selected path and the original reason. Errors about the selected path itself keep their target refusal.

Fixes #6004

Problem and expected behavior

ModelArtifactProvider handled its typed and permission cases, then turned every remaining Error with a code property into BinaryTargetError. Any errno, including descriptor exhaustion or a device read error, was reported as a selected-path problem. The issue's expected behavior is that host failures stay distinct from selected-path or format refusal, while missing-path, access-denied and format refusals keep their own semantics.

Change and scope

The final coded-error branch now applies only to codes that describe the selected path: ENOENT, ENOTDIR, ELOOP, ENAMETOOLONG (the same set GoBinaryProvider's failureForPrimary treats as path errors), plus the codes RegularFile itself raises for the selected file: EISDIR and ENOTFILE (NonRegularFileReadError) and ESTALE (RegularFileChangedError). Every other coded error falls through to the ProviderAdapterError branch that uncoded errors already used. Permission (EACCES/EPERM), format, cancellation, integrity, limit, cleanup and partial-observation handling are unchanged.

docs/model-artifacts.md gains one sentence describing the split.

Not included: GpuCodeObjectsProvider has the same catch-all branch and is left for its own issue. The binary-target resolver's own stat classification (classifyBinaryTargetFilesystemFailure) also maps EIO to target_unavailable, and the issue lists other producers (#5953, #5970, #5991, #5997). Those are separate boundaries and are left alone.

Contribution scope: ordinary fix within an existing boundary, no maintainer scope decision needed.

Contract and boundary impact

  • Semantic owner and earliest changed stage: ModelArtifactProvider failure mapping, after file admission and header read.
  • Contribution scope fit and linked maintainer decision: not applicable, error classification only.
  • CLI and MCP/tool-catalog contract: no schema change. Non-path host errors from model inspection now project as execution_failure with details.provider_id and details.diagnostics.{path,reason} instead of target_unavailable.
  • Provider, bridge, target-format, or platform compatibility: none. Path errno values were checked on macOS (below); Linux uses the same codes for these cases per the reviewer's source trace, not executed.
  • Evidence, artifact, provenance, or reconstruction contract: none. Cleanup-failure wrapping and partial-observation retention run after the error is chosen, so they apply to the new branch unchanged.
  • Target selection, authority, upstream behavior, and cleanup details: unchanged.
  • Generated metadata, package, or installation impact: none.

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/process-global/modelHostReadFailure.test.ts. Through the production MCP registration and in-memory transport, for both GGUF and safetensors, it injects EMFILE at open and EIO at the first read and expects execution_failure with path and reason, no path advice, closed handles and a successful inspection after each fault. It also injects each of the seven selected-path codes and inspects a really missing path, and expects target_unavailable for all of them. It lives in tests/process-global/ because it mocks node:fs/promises, per docs/testing.md.
  • Base reproduction (executed): with the production change stashed on base 01788bac8, npm run test:focused -- tests/process-global/modelHostReadFailure.test.ts: 2 failed, both expected { code: 'target_unavailable', … } to match object { code: 'execution_failure', … } for the EMFILE open fault.
  • Mutation checks (executed, npm run test:focused on the new and boundary model tests): removing the code filter, removing each of the seven codes individually, and emptying the set each made the run fail with assertion errors (9 of 9 mutants caught).
  • User-visible CLI output (executed, built CLI node scripts/rea.mjs inspect-model-artifact <path> --json on macOS): a missing file, a directory, a path under a regular file, a symlink and a FIFO all still return target_unavailable / unavailable.
  • Remaining proof gaps: host faults are injected through a mocked node:fs/promises; real descriptor exhaustion and device failures were not produced. Windows was not run (there a locked file's EBUSY would now be execution_failure). If a socket path disappears between the failed open and nonRegularOpenFailure's follow-up lstat, the raw ENXIO/EOPNOTSUPP now reports execution_failure instead of target_unavailable; this is a narrow race and was left as is.

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

Run on macOS 27 arm64, Node from .nvmrc, base 01788bac8. After a rebase onto green main 166fb0820, the focused tests, check:fast, test:changed and docs:check were run again and passed.

  • npm run test:focused -- tests/process-global/modelHostReadFailure.test.ts tests/boundary/model/modelArtifact.test.ts tests/acceptance/modelArtifactCli.test.ts: 3 files, 76 tests passed.
  • Same new test with the production change stashed: 2 failed (base reproduction above).
  • Mutation run over the new and boundary model tests: 9 of 9 mutants failed with assertion errors.
  • npm run check:fast: 2 of 2 tasks successful.
  • npm run test:changed -- --base 01788bac8: 2 files, 3 tests passed. Rerun after the rebase with --base 166fb0820: 3 files, 4 tests passed.
  • npm run verify:test-discovery: discovered all 1930 test files exactly once.
  • npm run check: exit 0, module boundaries checked in 2483 source files, architecture guards passed across 1727 source files.
  • node scripts/rea.mjs inspect-model-artifact <path> --json after npm run build:cached: missing file, directory, path under a regular file, symlink and FIFO each returned target_unavailable / unavailable.
  • Independent adversarial review (read-only, own worktree): no blocking findings. It traced every coded error that can reach the branch, confirmed on macOS that symlink, symlink loop, directory, FIFO, Unix socket, missing file, ENOTDIR, a 300-character name and /dev/null still produce BinaryTargetError, and confirmed no test, doc or contract expects target_unavailable for non-path host errors. It reported the socket race listed under proof gaps.
  • npm run docs:check: exit 0.
  • Automated code review (high effort) on the working-tree diff, each finding checked by hand:
    • The open-stage handle assertion was vacuous when no handle was opened. Fixed: the read stage now also asserts a handle was captured.
    • The public error split was undocumented. Fixed: one sentence in docs/model-artifacts.md.
    • It claimed the new execution_failure is retryable. Not so: the test now pins retryable: false, matching the issue's uncoded control.
    • src/gpu/GpuCodeObjectsProvider.ts:181 has the same catch-all coded-error branch. Confirmed, but outside this issue; left for a separate issue.
    • Suggestions not taken: remapping ESTALE (RegularFileChangedError) to the artifact-changed error and rewording ELOOP (both unchanged from base), a typed resource error for EMFILE/ENFILE, and moving classification into the shared BinaryTargetResolver classifier (which would change other callers). Each is a separate behavior change.
    • After these changes the base run, mutation run, focused tests, check:fast, test:changed, docs:check and npm run check were all rerun with the results above.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Callers that branched on target_unavailable for non-path host errors from model inspection now see execution_failure, which is the outcome the issue asks for.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. The model provider parses local files directly; the real provider was exercised through the built CLI on macOS 27 arm64.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new reads, paths or processes. Reported reasons are the same host messages that were already returned.

Author readiness

Human owner: @amyanger

  • 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/6175 **Author:** [@amyanger](https://github.com/amyanger) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/6004-model-host-io-errors` --- ### 📝 Commits (1) - [`9adee5c`](https://github.com/morluto/rea/commit/9adee5ca98cee40f57aae80ce491faf33ec05e06) fix(model): keep host I/O failures distinct from unavailable model targets ### 📊 Changes **3 files changed** (+157 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/model-artifacts.md` (+4 -1) 📝 `src/model/ModelArtifactProvider.ts` (+16 -1) ➕ `tests/process-global/modelHostReadFailure.test.ts` (+137 -0) </details> ### 📄 Description ## Summary `inspect_model_artifact` reported host I/O and resource failures on a valid selected model (for example `EMFILE` at open or `EIO` at header read) as `target_unavailable` / `unavailable`, with advice to check that the path exists and is readable. Those failures now reach the provider's existing `execution_failure` fallback with the selected path and the original reason. Errors about the selected path itself keep their target refusal. Fixes #6004 ## Problem and expected behavior `ModelArtifactProvider` handled its typed and permission cases, then turned every remaining `Error` with a `code` property into `BinaryTargetError`. Any errno, including descriptor exhaustion or a device read error, was reported as a selected-path problem. The issue's expected behavior is that host failures stay distinct from selected-path or format refusal, while missing-path, access-denied and format refusals keep their own semantics. ## Change and scope The final coded-error branch now applies only to codes that describe the selected path: `ENOENT`, `ENOTDIR`, `ELOOP`, `ENAMETOOLONG` (the same set `GoBinaryProvider`'s `failureForPrimary` treats as path errors), plus the codes `RegularFile` itself raises for the selected file: `EISDIR` and `ENOTFILE` (`NonRegularFileReadError`) and `ESTALE` (`RegularFileChangedError`). Every other coded error falls through to the `ProviderAdapterError` branch that uncoded errors already used. Permission (`EACCES`/`EPERM`), format, cancellation, integrity, limit, cleanup and partial-observation handling are unchanged. `docs/model-artifacts.md` gains one sentence describing the split. Not included: `GpuCodeObjectsProvider` has the same catch-all branch and is left for its own issue. The binary-target resolver's own stat classification (`classifyBinaryTargetFilesystemFailure`) also maps `EIO` to `target_unavailable`, and the issue lists other producers (#5953, #5970, #5991, #5997). Those are separate boundaries and are left alone. Contribution scope: ordinary fix within an existing boundary, no maintainer scope decision needed. ## Contract and boundary impact - Semantic owner and earliest changed stage: `ModelArtifactProvider` failure mapping, after file admission and header read. - Contribution scope fit and linked maintainer decision: not applicable, error classification only. - CLI and MCP/tool-catalog contract: no schema change. Non-path host errors from model inspection now project as `execution_failure` with `details.provider_id` and `details.diagnostics.{path,reason}` instead of `target_unavailable`. - Provider, bridge, target-format, or platform compatibility: none. Path errno values were checked on macOS (below); Linux uses the same codes for these cases per the reviewer's source trace, not executed. - Evidence, artifact, provenance, or reconstruction contract: none. Cleanup-failure wrapping and partial-observation retention run after the error is chosen, so they apply to the new branch unchanged. - Target selection, authority, upstream behavior, and cleanup details: unchanged. - Generated metadata, package, or installation impact: none. 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/process-global/modelHostReadFailure.test.ts`. Through the production MCP registration and in-memory transport, for both GGUF and safetensors, it injects `EMFILE` at open and `EIO` at the first read and expects `execution_failure` with path and reason, no path advice, closed handles and a successful inspection after each fault. It also injects each of the seven selected-path codes and inspects a really missing path, and expects `target_unavailable` for all of them. It lives in `tests/process-global/` because it mocks `node:fs/promises`, per `docs/testing.md`. - Base reproduction (executed): with the production change stashed on base `01788bac8`, `npm run test:focused -- tests/process-global/modelHostReadFailure.test.ts`: 2 failed, both `expected { code: 'target_unavailable', … } to match object { code: 'execution_failure', … }` for the `EMFILE` open fault. - Mutation checks (executed, `npm run test:focused` on the new and boundary model tests): removing the code filter, removing each of the seven codes individually, and emptying the set each made the run fail with assertion errors (9 of 9 mutants caught). - User-visible CLI output (executed, built CLI `node scripts/rea.mjs inspect-model-artifact <path> --json` on macOS): a missing file, a directory, a path under a regular file, a symlink and a FIFO all still return `target_unavailable` / `unavailable`. - Remaining proof gaps: host faults are injected through a mocked `node:fs/promises`; real descriptor exhaustion and device failures were not produced. Windows was not run (there a locked file's `EBUSY` would now be `execution_failure`). If a socket path disappears between the failed open and `nonRegularOpenFailure`'s follow-up `lstat`, the raw `ENXIO`/`EOPNOTSUPP` now reports `execution_failure` instead of `target_unavailable`; this is a narrow race and was left as is. 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 Run on macOS 27 arm64, Node from `.nvmrc`, base `01788bac8`. After a rebase onto green main `166fb0820`, the focused tests, `check:fast`, `test:changed` and `docs:check` were run again and passed. - `npm run test:focused -- tests/process-global/modelHostReadFailure.test.ts tests/boundary/model/modelArtifact.test.ts tests/acceptance/modelArtifactCli.test.ts`: 3 files, 76 tests passed. - Same new test with the production change stashed: 2 failed (base reproduction above). - Mutation run over the new and boundary model tests: 9 of 9 mutants failed with assertion errors. - `npm run check:fast`: 2 of 2 tasks successful. - `npm run test:changed -- --base 01788bac8`: 2 files, 3 tests passed. Rerun after the rebase with `--base 166fb0820`: 3 files, 4 tests passed. - `npm run verify:test-discovery`: discovered all 1930 test files exactly once. - `npm run check`: exit 0, module boundaries checked in 2483 source files, architecture guards passed across 1727 source files. - `node scripts/rea.mjs inspect-model-artifact <path> --json` after `npm run build:cached`: missing file, directory, path under a regular file, symlink and FIFO each returned `target_unavailable` / `unavailable`. - Independent adversarial review (read-only, own worktree): no blocking findings. It traced every coded error that can reach the branch, confirmed on macOS that symlink, symlink loop, directory, FIFO, Unix socket, missing file, `ENOTDIR`, a 300-character name and `/dev/null` still produce `BinaryTargetError`, and confirmed no test, doc or contract expects `target_unavailable` for non-path host errors. It reported the socket race listed under proof gaps. - `npm run docs:check`: exit 0. - Automated code review (high effort) on the working-tree diff, each finding checked by hand: - The open-stage handle assertion was vacuous when no handle was opened. Fixed: the read stage now also asserts a handle was captured. - The public error split was undocumented. Fixed: one sentence in `docs/model-artifacts.md`. - It claimed the new `execution_failure` is retryable. Not so: the test now pins `retryable: false`, matching the issue's uncoded control. - `src/gpu/GpuCodeObjectsProvider.ts:181` has the same catch-all coded-error branch. Confirmed, but outside this issue; left for a separate issue. - Suggestions not taken: remapping `ESTALE` (`RegularFileChangedError`) to the artifact-changed error and rewording `ELOOP` (both unchanged from base), a typed resource error for `EMFILE`/`ENFILE`, and moving classification into the shared `BinaryTargetResolver` classifier (which would change other callers). Each is a separate behavior change. - After these changes the base run, mutation run, focused tests, `check:fast`, `test:changed`, `docs:check` and `npm run check` were all rerun with the results above. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Callers that branched on `target_unavailable` for non-path host errors from model inspection now see `execution_failure`, which is the outcome the issue asks for. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. The model provider parses local files directly; the real provider was exercised through the built CLI on macOS 27 arm64. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new reads, paths or processes. Reported reasons are the same host messages that were already returned. ## Author readiness Human owner: @amyanger - [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:58 +00:00
bsakaguchi changed title from [PR #6175] [MERGED] fix(model): keep host I/O failures distinct from unavailable model targets to [PR #6175] fix(model): keep host I/O failures distinct from unavailable model targets 2026-11-04 16:32:38 +00:00
bsakaguchi changed title from [PR #6175] fix(model): keep host I/O failures distinct from unavailable model targets to [PR #6175] [MERGED] fix(model): keep host I/O failures distinct from unavailable model targets 2026-11-04 17:28:42 +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#7184
No description provided.