[PR #4185] [CLOSED] fix(verifiers): retry transient install-root cleanup on Windows (#4136) #6115

New issue

Closed

opened 2026-10-31 01:11:58 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:11:58 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4185
Author: @DeryFerd
Created: 10/15/2026
Status: ❌ Closed

Base: main ← Head: fix/4136-transient-install-root-cleanup

---

📝 Commits (1)

• 5896459 fix(verifiers): retry transient install-root cleanup on Windows

📊 Changes

4 files changed (+176 additions, -2 deletions)

View changed files

📝 scripts/lib/verifier-cleanup.d.mts (+15 -0)
📝 scripts/lib/verifier-cleanup.mjs (+37 -0)
📝 scripts/verify-packaged-wasm-artifact.mjs (+16 -1)
📝 tests/boundary/process/verifierCleanup.test.ts (+108 -1)

📄 Description

Summary

The packaged-WASM verifier installs the npm artifact into a leased private runtime root and removes it in a bare finally. When a just-exited npm child still holds an installed dependency open without FILE_SHARE_DELETE, the native close fails with Win32 32 and the owned root stays on disk. The finally then replaced the verifier's own result with that cleanup failure and offered no retry, so a passing run could be reported as failed. The verifier now retries only the proven transient sharing/lock conflict with a bounded budget and aggregates any persistent cleanup failure with the primary result instead of masking it.

Fixes #4136.

Problem and expected behavior

The smallest trigger is an owned runtime root that is closed while a child process still holds a file inside it without delete sharing. In the affected lane, the npm install child had already exited and the owning Windows Job had settled at active-process count zero, yet PrivateRuntimeRoot.close() opened an installed dependency (.../node_modules/rea-agents/node_modules/@babel/parser/CHANGELOG.md) relative to its retained directory handle and received Win32 32. Windows can keep a file locked briefly after the holder exits, so a single immediate close is racy.

The violated invariant is that a verifier must not let teardown overwrite its own verification result, and that cleanup of an owned resource must recover from a conflict the owner can prove is transient. The expected behavior is that a proven transient conflict is retried until it clears, and that a genuinely persistent cleanup failure is reported alongside the primary result rather than instead of it.

Change and scope

scripts/lib/verifier-cleanup.mjs gains retryTransientCleanup, which retries a task only when it fails with ERR_REA_WINDOWS_NATIVE and Win32 32 or 33 (sharing or lock), the exact codes the Windows native authority already treats as a transient conflict. Every other failure, including permission errors, missing allocation evidence, and opaque text, propagates unchanged on the first attempt. The retry is bounded and then surfaces the last cause.

scripts/verify-packaged-wasm-artifact.mjs stops closing its root in a bare finally. It captures the primary error, retries the close through the new helper, and routes both through the existing closeVerifierResources aggregator, so a persistent cleanup failure no longer hides the verification outcome. The change is limited to verifier teardown. It does not weaken Windows share or delete semantics, does not add an automatic retry loop elsewhere, and does not touch the native authority or any provider.

Contract and boundary impact

• Semantic owner and earliest changed stage: verifier cleanup in scripts/lib/verifier-cleanup.mjs; the earliest changed stage is packaged-WASM verifier teardown in scripts/verify-packaged-wasm-artifact.mjs.
• Contribution scope fit and linked maintainer decision: ordinary defect fix within existing verifier and cleanup authority; a separate maintainer scope decision is not applicable.
• CLI and MCP/tool-catalog contract: no product CLI, MCP, schema, or catalog change.
• Provider, bridge, target-format, or platform compatibility: Windows-only recovery of an owned-root close; no provider, bridge, or target-format change, and the POSIX path is untouched because the retry predicate requires the Windows native error code.
• Evidence, artifact, provenance, or reconstruction contract: no product Evidence change; the verifier keeps ownership of its leased root until removal succeeds.
• Target selection, authority, upstream behavior, and cleanup details: no change to target selection or execution authority; the retry applies only to the verifier's own leased root and only to a proven transient conflict, with no native sharing or delete behavior relaxed.
• 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.

These are the existing effects of running the package verifier; this change adds no new effect and only bounds how its teardown recovers.

Evidence and regression coverage

• Tests added or updated: tests/boundary/process/verifierCleanup.test.ts gains four cases. One retries a proven sharing conflict until cleanup succeeds and asserts the exact attempt count. One asserts a non-transient failure is not retried. One asserts the last cause surfaces once the bounded budget is exhausted. One asserts closeVerifierResources retains the primary result when a retried cleanup still fails.
• Base reproduction or other evidence: independent reproduction on a real Windows 11 x64 host (Node 24.21.0) with the packaged rea-agents@6.5.0 native addon. A child held a file in a leased root without delete sharing; raw PrivateRuntimeRoot.close() failed with ERR_REA_WINDOWS_NATIVE, Win32 32, and left the root on disk, while the same close succeeded after the holder released. Routing the close through retryTransientCleanup resolved and removed the root without a spurious failure.
• User-visible CLI/MCP output (if applicable): not applicable; this is a verifier teardown boundary.
• Remaining proof gaps: the complete packaged-WASM lane was not run end to end on this host, because it needs a Windows npm install and the WABT toolchain. The cleanup recovery itself was verified directly at the PrivateRuntimeRoot boundary. Local tsc/check:fast did not run because the host ran out of memory during the TypeScript check; the changed .mjs files are outside the tsconfig include set and were checked with oxlint, oxfmt, and the module-boundary verifier instead.

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

• npx vitest run tests/boundary/process/verifierCleanup.test.ts --project process-boundary — 6 passed, including the four new cases.
• npx vitest run tests/boundary/process/verifierCleanup.test.ts tests/boundary/process/verifierRun.test.ts --project process-boundary — 7 passed.
• Red-green check — reverting only scripts/lib/verifier-cleanup.mjs makes the four new cases fail with retryTransientCleanup is not a function; restoring the file makes all six pass.
• npx oxlint scripts/lib/verifier-cleanup.mjs scripts/verify-packaged-wasm-artifact.mjs tests/boundary/process/verifierCleanup.test.ts — 0 warnings, 0 errors.
• npx oxfmt --check on the three changed files — all files use the correct format.
• npm run verify:module-boundaries — 1945 source files checked.
• Real Windows x64 native cleanup boundary — raw close failed Win32 32 and left the root; the retried close resolved and removed it.

Compatibility, safety, and release

• Breaking changes or migration steps: none.
• Real Hopper/Ghidra, browser, or OS coverage: real Windows x64 native runtime-root cleanup boundary exercised with the packaged addon; no provider behavior changed.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: the retry is bounded and fires only for a proven transient sharing or lock conflict on the verifier's own leased root. It does not relax Windows sharing or delete semantics, does not drop ownership, and does not retry permission failures or opaque errors.

Author readiness

Human owner: @DeryFerd

• 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/4185 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/15/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/4136-transient-install-root-cleanup` --- ### 📝 Commits (1) - [`5896459`](https://github.com/morluto/rea/commit/5896459f94955f4521bc88bb30ed1a6c1033f941) fix(verifiers): retry transient install-root cleanup on Windows ### 📊 Changes **4 files changed** (+176 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `scripts/lib/verifier-cleanup.d.mts` (+15 -0) 📝 `scripts/lib/verifier-cleanup.mjs` (+37 -0) 📝 `scripts/verify-packaged-wasm-artifact.mjs` (+16 -1) 📝 `tests/boundary/process/verifierCleanup.test.ts` (+108 -1) </details> ### 📄 Description ## Summary The packaged-WASM verifier installs the npm artifact into a leased private runtime root and removes it in a bare `finally`. When a just-exited npm child still holds an installed dependency open without `FILE_SHARE_DELETE`, the native close fails with Win32 32 and the owned root stays on disk. The `finally` then replaced the verifier's own result with that cleanup failure and offered no retry, so a passing run could be reported as failed. The verifier now retries only the proven transient sharing/lock conflict with a bounded budget and aggregates any persistent cleanup failure with the primary result instead of masking it. Fixes #4136. ## Problem and expected behavior The smallest trigger is an owned runtime root that is closed while a child process still holds a file inside it without delete sharing. In the affected lane, the npm install child had already exited and the owning Windows Job had settled at active-process count zero, yet `PrivateRuntimeRoot.close()` opened an installed dependency (`.../node_modules/rea-agents/node_modules/@babel/parser/CHANGELOG.md`) relative to its retained directory handle and received Win32 32. Windows can keep a file locked briefly after the holder exits, so a single immediate close is racy. The violated invariant is that a verifier must not let teardown overwrite its own verification result, and that cleanup of an owned resource must recover from a conflict the owner can prove is transient. The expected behavior is that a proven transient conflict is retried until it clears, and that a genuinely persistent cleanup failure is reported alongside the primary result rather than instead of it. ## Change and scope `scripts/lib/verifier-cleanup.mjs` gains `retryTransientCleanup`, which retries a task only when it fails with `ERR_REA_WINDOWS_NATIVE` and Win32 32 or 33 (sharing or lock), the exact codes the Windows native authority already treats as a transient conflict. Every other failure, including permission errors, missing allocation evidence, and opaque text, propagates unchanged on the first attempt. The retry is bounded and then surfaces the last cause. `scripts/verify-packaged-wasm-artifact.mjs` stops closing its root in a bare `finally`. It captures the primary error, retries the close through the new helper, and routes both through the existing `closeVerifierResources` aggregator, so a persistent cleanup failure no longer hides the verification outcome. The change is limited to verifier teardown. It does not weaken Windows share or delete semantics, does not add an automatic retry loop elsewhere, and does not touch the native authority or any provider. ## Contract and boundary impact - Semantic owner and earliest changed stage: verifier cleanup in `scripts/lib/verifier-cleanup.mjs`; the earliest changed stage is packaged-WASM verifier teardown in `scripts/verify-packaged-wasm-artifact.mjs`. - Contribution scope fit and linked maintainer decision: ordinary defect fix within existing verifier and cleanup authority; a separate maintainer scope decision is not applicable. - CLI and MCP/tool-catalog contract: no product CLI, MCP, schema, or catalog change. - Provider, bridge, target-format, or platform compatibility: Windows-only recovery of an owned-root close; no provider, bridge, or target-format change, and the POSIX path is untouched because the retry predicate requires the Windows native error code. - Evidence, artifact, provenance, or reconstruction contract: no product Evidence change; the verifier keeps ownership of its leased root until removal succeeds. - Target selection, authority, upstream behavior, and cleanup details: no change to target selection or execution authority; the retry applies only to the verifier's own leased root and only to a proven transient conflict, with no native sharing or delete behavior relaxed. - 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. - [x] Launch or attach to a process. - [x] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. - [x] 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. These are the existing effects of running the package verifier; this change adds no new effect and only bounds how its teardown recovers. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/process/verifierCleanup.test.ts` gains four cases. One retries a proven sharing conflict until cleanup succeeds and asserts the exact attempt count. One asserts a non-transient failure is not retried. One asserts the last cause surfaces once the bounded budget is exhausted. One asserts `closeVerifierResources` retains the primary result when a retried cleanup still fails. - Base reproduction or other evidence: independent reproduction on a real Windows 11 x64 host (Node 24.21.0) with the packaged `rea-agents@6.5.0` native addon. A child held a file in a leased root without delete sharing; raw `PrivateRuntimeRoot.close()` failed with `ERR_REA_WINDOWS_NATIVE`, Win32 32, and left the root on disk, while the same close succeeded after the holder released. Routing the close through `retryTransientCleanup` resolved and removed the root without a spurious failure. - User-visible CLI/MCP output (if applicable): not applicable; this is a verifier teardown boundary. - Remaining proof gaps: the complete packaged-WASM lane was not run end to end on this host, because it needs a Windows npm install and the WABT toolchain. The cleanup recovery itself was verified directly at the `PrivateRuntimeRoot` boundary. Local `tsc`/`check:fast` did not run because the host ran out of memory during the TypeScript check; the changed `.mjs` files are outside the `tsconfig` include set and were checked with oxlint, oxfmt, and the module-boundary verifier instead. 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 - `npx vitest run tests/boundary/process/verifierCleanup.test.ts --project process-boundary` — 6 passed, including the four new cases. - `npx vitest run tests/boundary/process/verifierCleanup.test.ts tests/boundary/process/verifierRun.test.ts --project process-boundary` — 7 passed. - Red-green check — reverting only `scripts/lib/verifier-cleanup.mjs` makes the four new cases fail with `retryTransientCleanup is not a function`; restoring the file makes all six pass. - `npx oxlint scripts/lib/verifier-cleanup.mjs scripts/verify-packaged-wasm-artifact.mjs tests/boundary/process/verifierCleanup.test.ts` — 0 warnings, 0 errors. - `npx oxfmt --check` on the three changed files — all files use the correct format. - `npm run verify:module-boundaries` — 1945 source files checked. - Real Windows x64 native cleanup boundary — raw close failed Win32 32 and left the root; the retried close resolved and removed it. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: real Windows x64 native runtime-root cleanup boundary exercised with the packaged addon; no provider behavior changed. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the retry is bounded and fires only for a proven transient sharing or lock conflict on the verifier's own leased root. It does not relax Windows sharing or delete semantics, does not drop ownership, and does not retry permission failures or opaque errors. ## Author readiness Human owner: @DeryFerd - [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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:11:58 +00:00

• closed this issue
• added the
  pull-request
  label

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

[PR #6143] [MERGED] fix(cancellation): preserve caller abort reasons through late finalization #7158

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#6115

No description provided.