[PR #1611] [CLOSED] fix(browser): redact escaped scenario artifact secrets #3004

New issue

Closed

opened 2026-10-17 21:12:47 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-17 21:12:47 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1611
Author: @Aliciawque
Created: 10/10/2026
Status: ❌ Closed

Base: main ← Head: fix/redact-escaped-browser-artifacts-2026-10-10

---

📝 Commits (2)

• a5872d4 fix(browser): redact escaped scenario artifact secrets
• d2e3d5c fix(browser): integrate upstream redaction hardening

📊 Changes

5 files changed (+320 additions, -2 deletions)

View changed files

📝 docs/browser-scenario-contract.md (+13 -0)
📝 src/browser/BrowserScenario.test.ts (+107 -0)
📝 src/browser/BrowserScenarioSecrets.ts (+100 -0)
📝 src/browser/PlaywrightScenarioArtifacts.test.ts (+98 -0)
📝 src/browser/PlaywrightScenarioArtifacts.ts (+2 -2)

📄 Description

Integration update (2026-10-11 00:02 UTC)

Published head: d2e3d5ce1f7a125e065287b873d0203aeb9d1825. This is a non-force, two-parent integration commit retaining the original head and upstream c9168508527302ac57bc86385ccf0d824697b5dc. The reviewed remote tree is d8c698cfe77c672936ab264bcd56465db4e3ca4a.

Resolve the two conflicts in BrowserScenarioSecrets.ts and PlaywrightScenarioArtifacts.test.ts by retaining upstream #1590's safe-marker/raw/URL/byte behavior and storage sanitization, alongside this PR's artifact matcher and both test sets. Add four artifact-marker integration cases. The delta against the integrated upstream remains five files; #1612's complementary accessibility quoting/whitespace behavior is not included or claimed combined-tested.

Validation on Linux, Node 24.18.0/npm 11.16.0:

• Six focused browser suites: 82 tests passed, including marker and storage regressions
• CLI/MCP boundary suites: 3 tests passed (85 focused tests total)
• npm run check, npm run docs:check, npm run build:cached, and git diff --check: passed; 664 existing nonfatal lint warnings remain
• npm run verify:test-discovery: all 794 test files discovered exactly once, not a full-suite execution
• Independent review of this exact merged source: 187 assertions across 51 synthetic spellings passed, including marker fallbacks, reconstructed-secret fail-closed behavior, retained bytes/SHA-256, binary preservation, and combined cookie/storage sanitization
• Fresh supported npm run verify:browser with /usr/bin/chromium and sandbox enabled: blocked before page load by Chromium process socket() EPERM/SIGABRT, with a crashpad directory error. Cleanup ran; no security bypass or local live-browser success is claimed
• Exact-head CI and real-browser verification: action_required, awaiting maintainer approval, zero checks executed

CassieFox23's external reproduction reports that original head a5872d44a fixes the original leaks on Linux/Chromium 154 and that its focused tests pass on Node 22/24/26. Those are third-party results on the original head, not this integration's CI or locally executed browser evidence. Their later main-branch check also distinguishes #1590's marker/storage scope from these escaped artifact spellings.

Upstream advanced to 5485483f7da2f6cb66441bb784aaf2a1a5f8731a during verification, changing only JavaScript export analysis and its tests. Local results above are specifically for integration base c9168508; GitHub reports this PR mergeable after the push. The PR remains a draft.

Summary

Fixes #1608.

Remove declared secrets from DOM and accessibility artifact text when the browser represents them using standard HTML or URI/form escaping. Preserve unrelated evidence and compute artifact identity from the retained, redacted text.

Problem and expected behavior

A declared synthetic value such as SECRET-a&b-7f3a appears in page.content() as SECRET-a&b-7f3a; SECRET c8 7f3a can appear in both DOM and accessibility link URLs as SECRET%20c8%207f3a. Raw-string replacement misses these spellings, contrary to the declared-secret redaction contract.

The executed mocked-artifact regression reproduces these misses on main 0d89978333a7f139c53f35f1bb622d08eb73affa. The actual browser reproduction reported in the issue is external evidence; local live-browser execution was blocked as described below.

Change and scope

Add an artifact-specific matcher owned by BrowserScenarioSecrets, used only by the DOM and accessibility capture paths. It recognizes raw values, browser HTML text/attribute serialization, URI/component/form serialization, and URI spellings inside HTML. Hexadecimal percent-escape digits can use either case; literal letters remain case-sensitive.

Match original snapshot spans, prefer the longest match at the same position, and use a stable secret ID for ties. Do not decode or normalize surrounding evidence or rematch inserted markers. Empty declarations are ignored; lone surrogates do not prevent raw/HTML redaction.

Marker creation stays with the existing raw-redaction policy. A final supported-spelling check retains empty text if replacement reconstructs a declared secret across a marker boundary. The artifact byte count and SHA-256 describe that empty retained representation. This small guard was required by an independently reproduced interaction with the exact #1590 patch; no marker-selection, cookie, or storage changes from that PR are included here.

Contract and boundary impact

• Semantic owner and earliest changed stage: declared-secret matching in the browser scenario owner, before DOM/accessibility text artifact hashing
• CLI and MCP/tool-catalog contract: no schema or tool changes; both adapters receive the shared artifact representation
• Provider, bridge, target-format, or platform compatibility: Playwright DOM/accessibility snapshots; no bridge or browser-lifecycle changes
• Evidence, artifact, provenance, or reconstruction contract: unrelated snapshot text is preserved; bytes and SHA-256 identify retained redacted text, including documented empty fail-closed output
• Process execution, authorization, cleanup, or containment impact: none
• Generated metadata, package, or installation impact: none; no version bump or generated output is committed

Evidence and regression coverage

• Tests added or updated: HTML text/attributes, URI/component/form and mixed hex case, Unicode and lone surrogates, newlines, regex punctuation, empty/no-secret controls, overlapping/colliding spellings, ordinary-suffix preservation, residual reconstruction, and retained/empty artifact identity
• Base reproduction or other evidence: the new mocked Playwright artifact regression fails on original main (one new failure; two prior tests pass), then passes with the patch; independent review also tests the exact #1590 composition
• User-visible CLI/MCP output: production-owner regression observes DOM text such as <p>seen [REDACTED:text_token]</p> and accessibility /url: /next?t=[REDACTED:link_token]&plain=kept; these are executed adapter outputs, not claimed live CLI captures
• Remaining proof gaps: live browser execution, external-connect mode, full repository test suite, and other operating systems were not verified

For evidence-bearing changes:

• Observed, derived, and inferred claims remain distinguishable
• Artifact identity is verified against the retained representation; provenance and failed-capture paths are unchanged
• Unavailable coverage and bounded redaction behavior are documented

Original submission validation

Final base: c1217e711b7260a04a75f58d46c97e1320595153. Linux, repository-pinned Node 24.18.0 and npm 11.16.0.

• npm run test:focused -- src/browser/BrowserScenario.test.ts src/browser/PlaywrightScenarioArtifacts.test.ts src/browser/PlaywrightScenarioEvents.test.ts: 38 tests passed
• npm run check: passed, including typecheck, lint/module boundaries, formatting, knip, metadata, and architecture guards; repository-wide nonfatal lint warnings remain
• npm run docs:check: passed
• npm run verify:test-discovery: all 766 test files discovered exactly once
• git diff --check: passed
• Independent synthetic validation: 17 tests passed, including 1,467 bounded spellings across 256 invented secrets and both exact-#1590 composition regressions
• Local Chromium 154.0.8037.57 CLI fixture, with invented secrets, localhost, and disposable profiles: attempted on baseline and patched code, but Chromium's required process socket fails with EPERM before page load, including through the supported elevated execution route; no live-browser success is claimed

Compatibility, safety, and release

• Breaking changes or migration steps: none
• Real Hopper/Ghidra, browser, or OS coverage: native analysis providers are not affected; Linux source/static checks passed; the real-browser lane was unavailable and macOS/Windows were not run
• Package or release metadata impact: none
• Security, privacy, process, or containment review: only explicitly declared synthetic secrets were used. This is bounded spelling matching, not general-purpose sanitization. Arbitrary entities, repeated encoding, base64, page-defined transformations, and additional accessibility quoting/whitespace normalization are outside scope. Raw, URL, byte, cookie, and storage behavior outside these artifacts remains unchanged.

Review checklist

• This PR addresses a concrete problem
• The PR has one focused outcome and the title follows type(scope): outcome
• Related issue is linked
• Tests cover changed observable behavior and meaningful failure paths
• Owning documentation is updated; generated metadata changes are not needed
• Live user-visible CLI/MCP output verified; browser startup is blocked as documented
• Final diff checked 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/1611 **Author:** [@Aliciawque](https://github.com/Aliciawque) **Created:** 10/10/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/redact-escaped-browser-artifacts-2026-10-10` --- ### 📝 Commits (2) - [`a5872d4`](https://github.com/morluto/rea/commit/a5872d44a92e18dae999dcecb4ee5d409845628c) fix(browser): redact escaped scenario artifact secrets - [`d2e3d5c`](https://github.com/morluto/rea/commit/d2e3d5ce1f7a125e065287b873d0203aeb9d1825) fix(browser): integrate upstream redaction hardening ### 📊 Changes **5 files changed** (+320 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/browser-scenario-contract.md` (+13 -0) 📝 `src/browser/BrowserScenario.test.ts` (+107 -0) 📝 `src/browser/BrowserScenarioSecrets.ts` (+100 -0) 📝 `src/browser/PlaywrightScenarioArtifacts.test.ts` (+98 -0) 📝 `src/browser/PlaywrightScenarioArtifacts.ts` (+2 -2) </details> ### 📄 Description ## Integration update (2026-10-11 00:02 UTC) Published head: `d2e3d5ce1f7a125e065287b873d0203aeb9d1825`. This is a non-force, two-parent integration commit retaining the original head and upstream `c9168508527302ac57bc86385ccf0d824697b5dc`. The reviewed remote tree is `d8c698cfe77c672936ab264bcd56465db4e3ca4a`. Resolve the two conflicts in `BrowserScenarioSecrets.ts` and `PlaywrightScenarioArtifacts.test.ts` by retaining upstream #1590's safe-marker/raw/URL/byte behavior and storage sanitization, alongside this PR's artifact matcher and both test sets. Add four artifact-marker integration cases. The delta against the integrated upstream remains five files; #1612's complementary accessibility quoting/whitespace behavior is not included or claimed combined-tested. Validation on Linux, Node 24.18.0/npm 11.16.0: - Six focused browser suites: 82 tests passed, including marker and storage regressions - CLI/MCP boundary suites: 3 tests passed (85 focused tests total) - `npm run check`, `npm run docs:check`, `npm run build:cached`, and `git diff --check`: passed; 664 existing nonfatal lint warnings remain - `npm run verify:test-discovery`: all 794 test files discovered exactly once, not a full-suite execution - Independent review of this exact merged source: 187 assertions across 51 synthetic spellings passed, including marker fallbacks, reconstructed-secret fail-closed behavior, retained bytes/SHA-256, binary preservation, and combined cookie/storage sanitization - Fresh supported `npm run verify:browser` with `/usr/bin/chromium` and sandbox enabled: blocked before page load by Chromium process `socket()` EPERM/SIGABRT, with a crashpad directory error. Cleanup ran; no security bypass or local live-browser success is claimed - Exact-head [CI](https://github.com/morluto/rea/actions/runs/38097056922) and [real-browser verification](https://github.com/morluto/rea/actions/runs/38097056902): `action_required`, awaiting maintainer approval, zero checks executed CassieFox23's [external reproduction](https://github.com/morluto/rea/issues/1608#issuecomment-6101125011) reports that original head `a5872d44a` fixes the original leaks on Linux/Chromium 154 and that its focused tests pass on Node 22/24/26. Those are third-party results on the original head, not this integration's CI or locally executed browser evidence. Their [later main-branch check](https://github.com/morluto/rea/issues/1608#issuecomment-6103413411) also distinguishes #1590's marker/storage scope from these escaped artifact spellings. Upstream advanced to `5485483f7da2f6cb66441bb784aaf2a1a5f8731a` during verification, changing only JavaScript export analysis and its tests. Local results above are specifically for integration base `c9168508`; GitHub reports this PR mergeable after the push. The PR remains a draft. ## Summary Fixes #1608. Remove declared secrets from DOM and accessibility artifact text when the browser represents them using standard HTML or URI/form escaping. Preserve unrelated evidence and compute artifact identity from the retained, redacted text. ## Problem and expected behavior A declared synthetic value such as `SECRET-a&b-7f3a` appears in `page.content()` as `SECRET-a&amp;b-7f3a`; `SECRET c8 7f3a` can appear in both DOM and accessibility link URLs as `SECRET%20c8%207f3a`. Raw-string replacement misses these spellings, contrary to the declared-secret redaction contract. The executed mocked-artifact regression reproduces these misses on main `0d89978333a7f139c53f35f1bb622d08eb73affa`. The actual browser reproduction reported in the issue is external evidence; local live-browser execution was blocked as described below. ## Change and scope Add an artifact-specific matcher owned by `BrowserScenarioSecrets`, used only by the DOM and accessibility capture paths. It recognizes raw values, browser HTML text/attribute serialization, URI/component/form serialization, and URI spellings inside HTML. Hexadecimal percent-escape digits can use either case; literal letters remain case-sensitive. Match original snapshot spans, prefer the longest match at the same position, and use a stable secret ID for ties. Do not decode or normalize surrounding evidence or rematch inserted markers. Empty declarations are ignored; lone surrogates do not prevent raw/HTML redaction. Marker creation stays with the existing raw-redaction policy. A final supported-spelling check retains empty text if replacement reconstructs a declared secret across a marker boundary. The artifact byte count and SHA-256 describe that empty retained representation. This small guard was required by an independently reproduced interaction with the exact #1590 patch; no marker-selection, cookie, or storage changes from that PR are included here. ## Contract and boundary impact - Semantic owner and earliest changed stage: declared-secret matching in the browser scenario owner, before DOM/accessibility text artifact hashing - CLI and MCP/tool-catalog contract: no schema or tool changes; both adapters receive the shared artifact representation - Provider, bridge, target-format, or platform compatibility: Playwright DOM/accessibility snapshots; no bridge or browser-lifecycle changes - Evidence, artifact, provenance, or reconstruction contract: unrelated snapshot text is preserved; bytes and SHA-256 identify retained redacted text, including documented empty fail-closed output - Process execution, authorization, cleanup, or containment impact: none - Generated metadata, package, or installation impact: none; no version bump or generated output is committed ## Evidence and regression coverage - Tests added or updated: HTML text/attributes, URI/component/form and mixed hex case, Unicode and lone surrogates, newlines, regex punctuation, empty/no-secret controls, overlapping/colliding spellings, ordinary-suffix preservation, residual reconstruction, and retained/empty artifact identity - Base reproduction or other evidence: the new mocked Playwright artifact regression fails on original main (one new failure; two prior tests pass), then passes with the patch; independent review also tests the exact #1590 composition - User-visible CLI/MCP output: production-owner regression observes DOM text such as `<p>seen [REDACTED:text_token]</p>` and accessibility `/url: /next?t=[REDACTED:link_token]&plain=kept`; these are executed adapter outputs, not claimed live CLI captures - Remaining proof gaps: live browser execution, external-connect mode, full repository test suite, and other operating systems were not verified For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable - [x] Artifact identity is verified against the retained representation; provenance and failed-capture paths are unchanged - [x] Unavailable coverage and bounded redaction behavior are documented ## Original submission validation Final base: `c1217e711b7260a04a75f58d46c97e1320595153`. Linux, repository-pinned Node 24.18.0 and npm 11.16.0. - `npm run test:focused -- src/browser/BrowserScenario.test.ts src/browser/PlaywrightScenarioArtifacts.test.ts src/browser/PlaywrightScenarioEvents.test.ts`: 38 tests passed - `npm run check`: passed, including typecheck, lint/module boundaries, formatting, knip, metadata, and architecture guards; repository-wide nonfatal lint warnings remain - `npm run docs:check`: passed - `npm run verify:test-discovery`: all 766 test files discovered exactly once - `git diff --check`: passed - Independent synthetic validation: 17 tests passed, including 1,467 bounded spellings across 256 invented secrets and both exact-#1590 composition regressions - Local Chromium 154.0.8037.57 CLI fixture, with invented secrets, localhost, and disposable profiles: attempted on baseline and patched code, but Chromium's required process socket fails with `EPERM` before page load, including through the supported elevated execution route; no live-browser success is claimed ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: native analysis providers are not affected; Linux source/static checks passed; the real-browser lane was unavailable and macOS/Windows were not run - Package or release metadata impact: none - Security, privacy, process, or containment review: only explicitly declared synthetic secrets were used. This is bounded spelling matching, not general-purpose sanitization. Arbitrary entities, repeated encoding, base64, page-defined transformations, and additional accessibility quoting/whitespace normalization are outside scope. Raw, URL, byte, cookie, and storage behavior outside these artifacts remains unchanged. ## Review checklist - [x] This PR addresses a concrete problem - [x] The PR has one focused outcome and the title follows `type(scope): outcome` - [x] Related issue is linked - [x] Tests cover changed observable behavior and meaningful failure paths - [x] Owning documentation is updated; generated metadata changes are not needed - [ ] Live user-visible CLI/MCP output verified; browser startup is blocked as documented - [x] Final diff checked 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-17 21:12:47 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-10-31 00:40:20 +00:00

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

bsakaguchi referenced this issue 2026-10-31 01:07:32 +00:00

[PR #3004] feat(adb): add UI Automator discovery, waits and actions #5555

bsakaguchi referenced this issue 2026-10-31 01:10:35 +00:00

[PR #3840] feat(android): add boot wait and resource-id to code tracing #5939

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

No description provided.