morluto/rea

Fork

You've already forked rea

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 #4010] [MERGED] fix(browser): confirm service-worker cancellation cleanup #5989

New issue

Closed

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

bsakaguchi commented

2026-10-31 01:10:59 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4010
Author: @N0zoM1z0
Created: 10/15/2026
Status: ✅ Merged
Merged: 10/15/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/windows-edge-service-worker-navigation-3816

📝 Commits (10+)

12c6d95 fix(browser): confirm service-worker cancellation cleanup
df7a223 Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816
bfc0545 Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816
912cdd4 fix(browser): restore policy after setup failure
b775324 fix(browser): transfer cancelled navigation cleanup
b900087 Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816
49e03fd fix(browser): retain cancellation ownership across retries
dcd4b85 Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816
a1f1b96 Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816
918bbd1 Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816

📊 Changes

8 files changed (+700 additions, -67 deletions)

View changed files

📝 scripts/lib/browser-scenario-storage-e2e.mjs (+11 -6)
📝 src/browser/CdpConnection.ts (+11 -1)
📝 src/browser/PlaywrightScenarioServiceWorkers.ts (+116 -27)
📝 src/browser/PlaywrightScenarioSession.test.ts (+405 -13)
📝 src/browser/PlaywrightScenarioSession.ts (+20 -4)
📝 src/browser/PlaywrightScenarioStorage.test.ts (+56 -9)
📝 src/browser/PlaywrightScenarioStorage.ts (+17 -7)
📝 tests/boundary/browser/cdpConnection.test.ts (+64 -0)

📄 Description

Summary

Attached Windows browser cancellation could exceed the service-worker owner's cleanup window, race two Page.stopLoading owners, and then turn Chromium's terminal detached-session response into a connection-wide protocol failure. This change gives each side effect and target lifetime one owner, restores the selected realm through its owned CDP session, and makes the real verifier require typed cancellation and close its provider.

Fixes #3816.

Problem and expected behavior

Cancelling a storage seed while Edge was navigating intermittently made the next service-worker scenario fail or stall. Cleanup must confirm restoration within a bounded interval, preserve a typed cancellation result, retain retry ownership on a real cleanup failure, and leave the attached target reusable.

Change and scope

Assign navigation stopping to storage when that owner exists; policy cleanup keeps the no-storage fallback.
Transfer stopping to the policy owner after a failed storage cleanup, once the storage attempt is no longer in flight.
Retain transferred stop ownership across cleanup retries until one owner confirms it, without repeating an already confirmed stop.
Make storage return explicit stop confirmation; transfer to policy when root discovery has not completed or a late stop arrives after storage release.
Track target detach explicitly so vanished iframe initialization cannot hold cleanup open.
After setup failure, clean up effects that were acquired before the failure instead of replaying the rejected setup promise on every retry.
Remove future-document scripts, restore the selected main realm through its owned CDP session, and restore only committed live child realms.
Restore the selected main realm through Playwright when its owned CDP session detaches unexpectedly; keep cleanup retryable when restoration cannot be confirmed.
Preserve Chromium's exact terminal -32001 Session with given id not found. as a command rejection for the matching connection-global command id; keep other missing or foreign session responses fail-closed.
Give the complete policy restoration chain a bounded five-second confirmation interval.
Make the real storage cancellation verifier close its provider and reject unrelated failures.

Contribution scope: ordinary fix within the existing read-only attached-browser capability; no new authority or provider. No maintainer scope decision is required.

Contract and boundary impact

Semantic owner and earliest changed stage: attached browser-session cleanup and the CDP response parser.
Contribution scope fit and linked maintainer decision: existing browser observation and cleanup semantics; not applicable.
CLI and MCP/tool-catalog contract: unchanged.
Provider, bridge, target-format, or platform compatibility: handles an observed Chromium flat-session terminal response; other responses retain strict validation.
Evidence, artifact, provenance, or reconstruction contract: unchanged.
Target selection, authority, upstream behavior, and cleanup details: selected target is unchanged; existing temporary service-worker policy is restored before disconnect, with retained retry ownership on unconfirmed live cleanup.
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: producer stop confirmation with pending root discovery and detach retry, late cancellation after storage release, single stop-loading ownership and failure transfer, retained ownership across session/setup cleanup retries, no duplicate confirmed stop, detached-main Playwright fallback with failed-restoration retry, no-storage fallback, cleanup past 1.1 seconds, setup failure after script acquisition, detach during initialization, empty uncommitted child frame, exact Chromium terminal rejection, and four strict near-miss response cases.
Base reproduction: ordinary-user Windows Edge 154.0.4258.48 reproduced the storage-cancellation to service-worker failure chain; retained diagnostic lanes isolate each boundary.
User-visible CLI/MCP output: no contract or result-shape change.
Remaining proof gaps: real Edge coverage is Windows only; Chrome and other operating systems were not independently rerun for this issue. Agent-token cost was not measured.
Observed, derived, and inferred claims remain distinguishable.
Artifact identity, source provenance, and failed attempts remain preserved.
Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

npm run test:focused -- src/browser/PlaywrightScenarioStorage.test.ts src/browser/PlaywrightScenarioSession.test.ts tests/boundary/browser/cdpConnection.test.ts tests/boundary/process/browserEnvironmentVerifier.test.ts — 57/57 passed on final latest-main head c45901a28ca25f296415178a481161da46ba9cf9, based on main c7697595d8e1b54ab04ba661f98ad595d0993c34.
npm run check:fast — typecheck and lint passed.
Ordinary-user Windows Edge storage→service-worker production workflow on exact head dcd4b85a5aeba08705c76c6544907376bd00e6b0 — all storage and service-worker assertions passed, including stalled image/frame cancellation, navigation during restoration, OOPIF policy setup, target reuse, and strict typed cancellation; cleanup left zero Job processes. The preceding r21 reached the service-worker phase without an assertion failure but exhausted its 420-second wall budget and terminated with zero Job processes.
The subsequent main refresh to c9f9b83c6 changed only exported-binding test fixtures and Kuna implementation, tests, verifier, skill, and documentation. Browser sources, verifier inputs, package inputs, and their blobs remained identical on intermediate head 918bbd1afb29c5cf284aaac9ba3055e9d7381233; 45/45 focused tests and check:fast passed there.
After the explicit storage-confirmation review fix, ordinary-user Windows Edge r23 passed on exact head ae9155c6ae4c42f9ee26d7c04a57c7ce64d72859: all storage and service-worker assertions passed and cleanup left Job process count zero.
Main then changed the real browser fixture and scenario limitations. After merging it, exact latest-main head c45901a28ca25f296415178a481161da46ba9cf9 passed ordinary-user Windows Edge r24 with every production assertion true and Job0.

The exact-head r22 workflow used 347.91 seconds of Job wall time with 295.80 sampled family CPU seconds, 1,020,522,496-byte peak Job commit, 1,237,225,472-byte peak sampled family working set, and Job process count zero. It used two logical CPUs, BelowNormal priority, and a 2 GiB Job limit. Focused traces measured the removed uncommitted-frame wait at about 10.4 seconds and direct main-realm CDP restoration at roughly 2–6 ms; passing runs have varied from about 203 to 370 seconds, so whole-run host variance does not support a speedup claim.

The final r23 workflow used 458.18 seconds of Job wall time with 482.72 sampled family CPU seconds, 1,240,961,024-byte peak Job commit, 1,379,008,512-byte peak sampled family working set, and Job process count zero under the same two logical CPUs, BelowNormal priority, and 2 GiB Job limit. The expanded timing range is reported as variance; no whole-task speedup is claimed.

The exact latest-main r24 workflow used 154.51 seconds of Job wall time with 130.69 sampled family CPU seconds, 1,137,291,264-byte peak Job commit, 1,331,421,184-byte peak sampled family working set, and Job process count zero under the same limits. This single faster run remains within the observed host variance and is not a speedup claim.

Compatibility, safety, and release

Breaking changes or migration steps: none.
Real Hopper/Ghidra, browser, or OS coverage: Windows Edge only for this change; no Hopper/Ghidra path is affected.
Package or release metadata impact: none.
Security, privacy, process, or containment review: no new target authority; exact target selection and cleanup ownership are preserved, and uncertain cleanup remains retryable.

Author readiness

Human owner: @N0zoM1z0

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/4010 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/15/2026 **Status:** ✅ Merged **Merged:** 10/15/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/windows-edge-service-worker-navigation-3816` --- ### 📝 Commits (10+) - [`12c6d95`](https://github.com/morluto/rea/commit/12c6d9549055fb3de13afbb162ee50b224da64cb) fix(browser): confirm service-worker cancellation cleanup - [`df7a223`](https://github.com/morluto/rea/commit/df7a223f2879d2c7c15fb47f579bf7a4cf0d63a6) Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816 - [`bfc0545`](https://github.com/morluto/rea/commit/bfc0545b1b641edf7194909443e7ed300cf4c7df) Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816 - [`912cdd4`](https://github.com/morluto/rea/commit/912cdd49d537930adfed0f5a49816b8b0db6b4f5) fix(browser): restore policy after setup failure - [`b775324`](https://github.com/morluto/rea/commit/b775324ead8f8fb216a9c2ffa0f852803183fc05) fix(browser): transfer cancelled navigation cleanup - [`b900087`](https://github.com/morluto/rea/commit/b900087bf1818802accf725168231a0b1e429d42) Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816 - [`49e03fd`](https://github.com/morluto/rea/commit/49e03fd49ae0643c0c3a9f7c8f127849a482bbb9) fix(browser): retain cancellation ownership across retries - [`dcd4b85`](https://github.com/morluto/rea/commit/dcd4b85a5aeba08705c76c6544907376bd00e6b0) Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816 - [`a1f1b96`](https://github.com/morluto/rea/commit/a1f1b96a2999ded42c47d9a0dfbe742f4b1d1a79) Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816 - [`918bbd1`](https://github.com/morluto/rea/commit/918bbd1afb29c5cf284aaac9ba3055e9d7381233) Merge remote-tracking branch 'origin/main' into fix/windows-edge-service-worker-navigation-3816 ### 📊 Changes **8 files changed** (+700 additions, -67 deletions) <details> <summary>View changed files</summary> 📝 `scripts/lib/browser-scenario-storage-e2e.mjs` (+11 -6) 📝 `src/browser/CdpConnection.ts` (+11 -1) 📝 `src/browser/PlaywrightScenarioServiceWorkers.ts` (+116 -27) 📝 `src/browser/PlaywrightScenarioSession.test.ts` (+405 -13) 📝 `src/browser/PlaywrightScenarioSession.ts` (+20 -4) 📝 `src/browser/PlaywrightScenarioStorage.test.ts` (+56 -9) 📝 `src/browser/PlaywrightScenarioStorage.ts` (+17 -7) 📝 `tests/boundary/browser/cdpConnection.test.ts` (+64 -0) </details> ### 📄 Description ## Summary Attached Windows browser cancellation could exceed the service-worker owner's cleanup window, race two `Page.stopLoading` owners, and then turn Chromium's terminal detached-session response into a connection-wide protocol failure. This change gives each side effect and target lifetime one owner, restores the selected realm through its owned CDP session, and makes the real verifier require typed cancellation and close its provider. Fixes #3816. ## Problem and expected behavior Cancelling a storage seed while Edge was navigating intermittently made the next service-worker scenario fail or stall. Cleanup must confirm restoration within a bounded interval, preserve a typed cancellation result, retain retry ownership on a real cleanup failure, and leave the attached target reusable. ## Change and scope - Assign navigation stopping to storage when that owner exists; policy cleanup keeps the no-storage fallback. - Transfer stopping to the policy owner after a failed storage cleanup, once the storage attempt is no longer in flight. - Retain transferred stop ownership across cleanup retries until one owner confirms it, without repeating an already confirmed stop. - Make storage return explicit stop confirmation; transfer to policy when root discovery has not completed or a late stop arrives after storage release. - Track target detach explicitly so vanished iframe initialization cannot hold cleanup open. - After setup failure, clean up effects that were acquired before the failure instead of replaying the rejected setup promise on every retry. - Remove future-document scripts, restore the selected main realm through its owned CDP session, and restore only committed live child realms. - Restore the selected main realm through Playwright when its owned CDP session detaches unexpectedly; keep cleanup retryable when restoration cannot be confirmed. - Preserve Chromium's exact terminal `-32001 Session with given id not found.` as a command rejection for the matching connection-global command id; keep other missing or foreign session responses fail-closed. - Give the complete policy restoration chain a bounded five-second confirmation interval. - Make the real storage cancellation verifier close its provider and reject unrelated failures. Contribution scope: ordinary fix within the existing read-only attached-browser capability; no new authority or provider. No maintainer scope decision is required. ## Contract and boundary impact - Semantic owner and earliest changed stage: attached browser-session cleanup and the CDP response parser. - Contribution scope fit and linked maintainer decision: existing browser observation and cleanup semantics; not applicable. - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: handles an observed Chromium flat-session terminal response; other responses retain strict validation. - Evidence, artifact, provenance, or reconstruction contract: unchanged. - Target selection, authority, upstream behavior, and cleanup details: selected target is unchanged; existing temporary service-worker policy is restored before disconnect, with retained retry ownership on unconfirmed live cleanup. - Generated metadata, package, or installation impact: none. Expected effects: - [ ] 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. - [ ] 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: producer stop confirmation with pending root discovery and detach retry, late cancellation after storage release, single stop-loading ownership and failure transfer, retained ownership across session/setup cleanup retries, no duplicate confirmed stop, detached-main Playwright fallback with failed-restoration retry, no-storage fallback, cleanup past 1.1 seconds, setup failure after script acquisition, detach during initialization, empty uncommitted child frame, exact Chromium terminal rejection, and four strict near-miss response cases. - Base reproduction: ordinary-user Windows Edge 154.0.4258.48 reproduced the storage-cancellation to service-worker failure chain; retained diagnostic lanes isolate each boundary. - User-visible CLI/MCP output: no contract or result-shape change. - Remaining proof gaps: real Edge coverage is Windows only; Chrome and other operating systems were not independently rerun for this issue. Agent-token cost was not measured. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run test:focused -- src/browser/PlaywrightScenarioStorage.test.ts src/browser/PlaywrightScenarioSession.test.ts tests/boundary/browser/cdpConnection.test.ts tests/boundary/process/browserEnvironmentVerifier.test.ts` — 57/57 passed on final latest-main head `c45901a28ca25f296415178a481161da46ba9cf9`, based on main `c7697595d8e1b54ab04ba661f98ad595d0993c34`. - `npm run check:fast` — typecheck and lint passed. - Ordinary-user Windows Edge storage→service-worker production workflow on exact head `dcd4b85a5aeba08705c76c6544907376bd00e6b0` — all storage and service-worker assertions passed, including stalled image/frame cancellation, navigation during restoration, OOPIF policy setup, target reuse, and strict typed cancellation; cleanup left zero Job processes. The preceding r21 reached the service-worker phase without an assertion failure but exhausted its 420-second wall budget and terminated with zero Job processes. - The subsequent main refresh to `c9f9b83c6` changed only exported-binding test fixtures and Kuna implementation, tests, verifier, skill, and documentation. Browser sources, verifier inputs, package inputs, and their blobs remained identical on intermediate head `918bbd1afb29c5cf284aaac9ba3055e9d7381233`; 45/45 focused tests and `check:fast` passed there. - After the explicit storage-confirmation review fix, ordinary-user Windows Edge r23 passed on exact head `ae9155c6ae4c42f9ee26d7c04a57c7ce64d72859`: all storage and service-worker assertions passed and cleanup left Job process count zero. - Main then changed the real browser fixture and scenario limitations. After merging it, exact latest-main head `c45901a28ca25f296415178a481161da46ba9cf9` passed ordinary-user Windows Edge r24 with every production assertion true and Job0. The exact-head r22 workflow used 347.91 seconds of Job wall time with 295.80 sampled family CPU seconds, 1,020,522,496-byte peak Job commit, 1,237,225,472-byte peak sampled family working set, and Job process count zero. It used two logical CPUs, BelowNormal priority, and a 2 GiB Job limit. Focused traces measured the removed uncommitted-frame wait at about 10.4 seconds and direct main-realm CDP restoration at roughly 2–6 ms; passing runs have varied from about 203 to 370 seconds, so whole-run host variance does not support a speedup claim. The final r23 workflow used 458.18 seconds of Job wall time with 482.72 sampled family CPU seconds, 1,240,961,024-byte peak Job commit, 1,379,008,512-byte peak sampled family working set, and Job process count zero under the same two logical CPUs, BelowNormal priority, and 2 GiB Job limit. The expanded timing range is reported as variance; no whole-task speedup is claimed. The exact latest-main r24 workflow used 154.51 seconds of Job wall time with 130.69 sampled family CPU seconds, 1,137,291,264-byte peak Job commit, 1,331,421,184-byte peak sampled family working set, and Job process count zero under the same limits. This single faster run remains within the observed host variance and is not a speedup claim. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: Windows Edge only for this change; no Hopper/Ghidra path is affected. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new target authority; exact target selection and cleanup ownership are preserved, and uncertain cleanup remains retryable. ## Author readiness Human owner: @N0zoM1z0 - [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-10-31 01:10:59 +00:00

closed this issue
added the
pull-request
label

No Branch/Tag specified

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

Mirrored from GitHub Pull Request

No labels

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

Reference in a new issue

Repository

morluto/rea

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns