[PR #6381] fix(browser): return completed scenario capture when cleanup is unconfirmed #7323

New issue

Open

opened 2026-11-01 21:47:02 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:47:02 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6381
Author: @sx4im
Created: 10/22/2026
Status: 🔄 Open

Base: main ← Head: fix/6166-completed-capture-cleanup

---

📝 Commits (2)

• b8e45c3 fix(browser): return completed scenario capture when cleanup is unconfirmed
• e53eaf8 Merge main into fix/6166-completed-capture-cleanup

📊 Changes

5 files changed (+148 additions, -48 deletions)

View changed files

📝 src/application/BrowserScenarioCaptureService.test.ts (+23 -0)
📝 src/browser/BrowserScenarioPartialObservation.ts (+52 -6)
📝 src/browser/PlaywrightBrowserScenarioProvider.test.ts (+54 -18)
📝 src/browser/PlaywrightBrowserScenarioProvider.ts (+13 -18)
📝 src/domain/browserScenarioCapture.ts (+6 -6)

📄 Description

Summary

Fixes #6166. When every action in a capture_browser_scenario run completed but browser cleanup timed out or could not be confirmed, the tool reported a hard cleanup_incomplete failure (retryable: false) and retained the finished observation only as a raw partial with no evidence_id. The caller lost a capture that had actually succeeded.

Problem and expected behavior

Smallest trigger: a scenario whose steps all complete, followed by a session close that fails or times out (the report shows a 30s cleanup confirmation timeout after the final wait_for_timeout). Violated invariant: a completed observation should stay a completed result; cleanup is a separate outcome. Expected: return the Evidence with its evidence_id, report cleanup status on the capture, and keep the unconfirmed resources visible.

Change and scope

Capture success and cleanup success are now modeled separately:

• browserScenarioCaptureSchema admits cleanup: "incomplete" on a completed capture (the value already existed on retained partial observations; the redundant widened type on BrowserScenarioCaptureData is gone).
• In the Playwright provider, when the operation outcome is ok and every step completed, a cleanup failure returns the completed capture with browser.cleanup: "incomplete" and one limitation naming the cleanup reason and the resources that may remain. The shared completeness classification moved into BrowserScenarioPartialObservation.ts so both return paths use it.
• Nothing changes when the operation itself failed or a step did not complete: the existing cleanup error, partial observation, and live cleanup resolution behave as before. The cleanup lease stays retained in every cleanup failure case, so provider close and the next capture still retry it and surface it if it never settles.

Scope decision: not applicable. This is an ordinary fix inside the existing browser capture workflow; it adds no capability, authority, or target interaction.

Contract and boundary impact

• Semantic owner and earliest changed stage: the capture contract in src/domain/browserScenarioCapture.ts; behavior changes at the provider cleanup stage in src/browser/PlaywrightBrowserScenarioProvider.ts.
• Contribution scope fit and linked maintainer decision: fits the existing browser scenario workflow; no maintainer scope decision required for a bug fix within existing boundaries.
• CLI and MCP/tool-catalog contract: the capture_browser_scenario result schema gains the cleanup value "incomplete". In the case above, CLI and MCP now return a successful Evidence result instead of an error result.
• Provider, bridge, target-format, or platform compatibility: Playwright browser scenario provider only. No bridge, format, or platform change.
• Evidence, artifact, provenance, or reconstruction contract: completed captures in the cleanup-unconfirmed case are now issued as Evidence with an evidence_id, so they can be referenced, exported, and compared like any other result. Provenance fields are unchanged.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): no new authority and no change to target selection. Cleanup ownership is retained exactly as before; unconfirmed resources are named in the capture limitations and retried on provider close.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none committed. CI generates the catalogs; the generated tool schema will show the added enum value.

Expected effects (check known effects; use documentation-only on its own).

• 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:
  • PlaywrightBrowserScenarioProvider.test.ts: new regression test (close fails after every action completed returns the capture with cleanup: "incomplete" and the resource limitation); the cleanup tests that encoded the old hard-failure outcome for completed captures now assert the returned capture plus retained-lease resolution through provider close. Operation-failure and cancellation variants are unchanged.
  • BrowserScenarioCaptureService.test.ts: new test that a completed capture reporting incomplete cleanup is returned as Evidence with an evidence_id.
• Base reproduction or other evidence: executed. On the base revision the new provider test failed with the reported behavior (a cleanup_incomplete BrowserObservationError; the completed steps sat in partial_observation as a raw capture with no evidence_id), and the new service test failed because the degraded capture was rejected. Both pass with this change.
• User-visible CLI/MCP output (if applicable): no real-browser run was available in the build environment, so no CLI transcript is attached; the unit and contract tests above cover the returned shapes.
• Remaining proof gaps: real Playwright verification (npm run verify:browser) not run; see Validation performed for the unrelated main build break that also blocks built boundary tests.

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:local -- src/browser/PlaywrightBrowserScenarioProvider.test.ts src/application/BrowserScenarioCaptureService.test.ts: 42 passed. The 2 new regression tests fail on the base revision and pass here.
• npm run test:local on 13 related files (capture schema, scenario diff inputs, analysis-view scenario records, environment scenario/source/state, scenario browser, execution boundary, provider operation execution, error projection, tool effects) : 247 passed.
• npm run test:local -- src/browser/PlaywrightScenarioSession.test.ts src/browser/PlaywrightScenarioStorage.test.ts src/browser/history/CaptureFailures.test.ts src/browser/assets/ScriptCaptureAdapters.test.ts: 69 passed.
• npm run verify:module-boundaries: passed (2,728 source files).
• npx tsc -p tsconfig.build.json --noEmit: no errors from this change. Two errors in src/application/ReconstructionObligationCandidates.ts (uniqueBy is not defined) are present on clean main as well and are unrelated; they also block test:focused built boundary tests in this environment.
• src/domain/browserScenarioDiff.test.ts has 4 storage canonicalization failures that are identical on clean main; unrelated to this change.
• oxlint and oxfmt on the touched files: no errors, format clean.
• CI on this PR: Source tests, Static checks, Docs Generation, Build package, and browser / real-browser passed. Test shard (7/8) and Portable tests failed; the other shards were cancelled by fail-fast. Check annotations do not name the failing test. Locally, the only failure I can reproduce is ReconstructionObligationCandidates.semantic.test.ts (1 test), which fails identically on clean main in the same area as the uniqueBy break above, and a peer PR on the same base failed Portable tests and a different shard the same evening. Every test covering this change passes locally and in the Source tests job.

Compatibility, safety, and release

• Breaking changes or migration steps: one behavior change. A capture whose actions all completed but whose cleanup is unconfirmed previously returned a cleanup_incomplete error; it now returns a successful Evidence result with browser.cleanup: "incomplete". Callers that keyed on the error code for this case should read browser.cleanup instead. No input, configuration, or stored-data migration.
• Real Hopper/Ghidra, browser, or OS coverage: none; fake-session provider tests and contract tests only. npm run verify:browser was not available in this environment.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: no new process, network, or file authority. Cleanup ownership of a possibly running browser and its profile stays with the provider lease until a retry confirms it, as before.

Author readiness

Human owner: @sx4im

• 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/6381 **Author:** [@sx4im](https://github.com/sx4im) **Created:** 10/22/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/6166-completed-capture-cleanup` --- ### 📝 Commits (2) - [`b8e45c3`](https://github.com/morluto/rea/commit/b8e45c3c65bf173e9bb57ac0fd58c8710f215880) fix(browser): return completed scenario capture when cleanup is unconfirmed - [`e53eaf8`](https://github.com/morluto/rea/commit/e53eaf85061a4e6560947c17d27a3bf81dd83c53) Merge main into fix/6166-completed-capture-cleanup ### 📊 Changes **5 files changed** (+148 additions, -48 deletions) <details> <summary>View changed files</summary> 📝 `src/application/BrowserScenarioCaptureService.test.ts` (+23 -0) 📝 `src/browser/BrowserScenarioPartialObservation.ts` (+52 -6) 📝 `src/browser/PlaywrightBrowserScenarioProvider.test.ts` (+54 -18) 📝 `src/browser/PlaywrightBrowserScenarioProvider.ts` (+13 -18) 📝 `src/domain/browserScenarioCapture.ts` (+6 -6) </details> ### 📄 Description ## Summary Fixes #6166. When every action in a `capture_browser_scenario` run completed but browser cleanup timed out or could not be confirmed, the tool reported a hard `cleanup_incomplete` failure (`retryable: false`) and retained the finished observation only as a raw partial with no `evidence_id`. The caller lost a capture that had actually succeeded. ## Problem and expected behavior Smallest trigger: a scenario whose steps all complete, followed by a session close that fails or times out (the report shows a 30s cleanup confirmation timeout after the final `wait_for_timeout`). Violated invariant: a completed observation should stay a completed result; cleanup is a separate outcome. Expected: return the Evidence with its `evidence_id`, report cleanup status on the capture, and keep the unconfirmed resources visible. ## Change and scope Capture success and cleanup success are now modeled separately: - `browserScenarioCaptureSchema` admits `cleanup: "incomplete"` on a completed capture (the value already existed on retained partial observations; the redundant widened type on `BrowserScenarioCaptureData` is gone). - In the Playwright provider, when the operation outcome is ok and every step completed, a cleanup failure returns the completed capture with `browser.cleanup: "incomplete"` and one limitation naming the cleanup reason and the resources that may remain. The shared completeness classification moved into `BrowserScenarioPartialObservation.ts` so both return paths use it. - Nothing changes when the operation itself failed or a step did not complete: the existing cleanup error, partial observation, and live cleanup resolution behave as before. The cleanup lease stays retained in every cleanup failure case, so provider close and the next capture still retry it and surface it if it never settles. Scope decision: not applicable. This is an ordinary fix inside the existing browser capture workflow; it adds no capability, authority, or target interaction. ## Contract and boundary impact - Semantic owner and earliest changed stage: the capture contract in `src/domain/browserScenarioCapture.ts`; behavior changes at the provider cleanup stage in `src/browser/PlaywrightBrowserScenarioProvider.ts`. - Contribution scope fit and linked maintainer decision: fits the existing browser scenario workflow; no maintainer scope decision required for a bug fix within existing boundaries. - CLI and MCP/tool-catalog contract: the `capture_browser_scenario` result schema gains the `cleanup` value `"incomplete"`. In the case above, CLI and MCP now return a successful Evidence result instead of an error result. - Provider, bridge, target-format, or platform compatibility: Playwright browser scenario provider only. No bridge, format, or platform change. - Evidence, artifact, provenance, or reconstruction contract: completed captures in the cleanup-unconfirmed case are now issued as Evidence with an `evidence_id`, so they can be referenced, exported, and compared like any other result. Provenance fields are unchanged. - Target selection, authority, upstream behavior, and cleanup details (if applicable): no new authority and no change to target selection. Cleanup ownership is retained exactly as before; unconfirmed resources are named in the capture limitations and retried on provider close. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none committed. CI generates the catalogs; the generated tool schema will show the added enum value. Expected effects (check known effects; use documentation-only on its own). - [ ] Read existing files or captured data. - [x] 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: - `PlaywrightBrowserScenarioProvider.test.ts`: new regression test (close fails after every action completed returns the capture with `cleanup: "incomplete"` and the resource limitation); the cleanup tests that encoded the old hard-failure outcome for completed captures now assert the returned capture plus retained-lease resolution through provider close. Operation-failure and cancellation variants are unchanged. - `BrowserScenarioCaptureService.test.ts`: new test that a completed capture reporting incomplete cleanup is returned as Evidence with an `evidence_id`. - Base reproduction or other evidence: executed. On the base revision the new provider test failed with the reported behavior (a `cleanup_incomplete` `BrowserObservationError`; the completed steps sat in `partial_observation` as a raw capture with no `evidence_id`), and the new service test failed because the degraded capture was rejected. Both pass with this change. - User-visible CLI/MCP output (if applicable): no real-browser run was available in the build environment, so no CLI transcript is attached; the unit and contract tests above cover the returned shapes. - Remaining proof gaps: real Playwright verification (`npm run verify:browser`) not run; see Validation performed for the unrelated `main` build break that also blocks built boundary tests. 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:local -- src/browser/PlaywrightBrowserScenarioProvider.test.ts src/application/BrowserScenarioCaptureService.test.ts`: 42 passed. The 2 new regression tests fail on the base revision and pass here. - `npm run test:local` on 13 related files (capture schema, scenario diff inputs, analysis-view scenario records, environment scenario/source/state, scenario browser, execution boundary, provider operation execution, error projection, tool effects) : 247 passed. - `npm run test:local -- src/browser/PlaywrightScenarioSession.test.ts src/browser/PlaywrightScenarioStorage.test.ts src/browser/history/CaptureFailures.test.ts src/browser/assets/ScriptCaptureAdapters.test.ts`: 69 passed. - `npm run verify:module-boundaries`: passed (2,728 source files). - `npx tsc -p tsconfig.build.json --noEmit`: no errors from this change. Two errors in `src/application/ReconstructionObligationCandidates.ts` (`uniqueBy` is not defined) are present on clean `main` as well and are unrelated; they also block `test:focused` built boundary tests in this environment. - `src/domain/browserScenarioDiff.test.ts` has 4 storage canonicalization failures that are identical on clean `main`; unrelated to this change. - oxlint and oxfmt on the touched files: no errors, format clean. - CI on this PR: Source tests, Static checks, Docs Generation, Build package, and browser / real-browser passed. Test shard (7/8) and Portable tests failed; the other shards were cancelled by fail-fast. Check annotations do not name the failing test. Locally, the only failure I can reproduce is `ReconstructionObligationCandidates.semantic.test.ts` (1 test), which fails identically on clean `main` in the same area as the `uniqueBy` break above, and a peer PR on the same base failed Portable tests and a different shard the same evening. Every test covering this change passes locally and in the Source tests job. ## Compatibility, safety, and release - Breaking changes or migration steps: one behavior change. A capture whose actions all completed but whose cleanup is unconfirmed previously returned a `cleanup_incomplete` error; it now returns a successful Evidence result with `browser.cleanup: "incomplete"`. Callers that keyed on the error code for this case should read `browser.cleanup` instead. No input, configuration, or stored-data migration. - Real Hopper/Ghidra, browser, or OS coverage: none; fake-session provider tests and contract tests only. `npm run verify:browser` was not available in this environment. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new process, network, or file authority. Cleanup ownership of a possibly running browser and its profile stays with the provider lease until a retry confirms it, as before. ## Author readiness Human owner: @sx4im - [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. - [ ] User-visible CLI/MCP changes include representative output. - [x] 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 added the

pull-request

label 2026-11-01 21:47:02 +00:00

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

[GH-ISSUE #5653] [Tracker] New issue intake by area (October 2026) #3423

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

No description provided.