morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #1645] [CLOSED] fix(browser): bound CDP message payloads to the shared protocol budget #4723

New issue
Closed
opened 2026-10-31 00:54:23 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 00:54:23 +00:00
Owner
Copy link

📋 Pull Request Information

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

Base: main ← Head: fix/cdp-default-payload-ceiling

📝 Commits (1)

  • 3d65f3e fix(browser): bound CDP message payloads to the shared protocol budget

📊 Changes

2 files changed (+43 additions, -2 deletions)

View changed files

📝 src/browser/CdpConnection.ts (+8 -2)
📝 tests/boundary/browser/cdpConnection.test.ts (+35 -0)

📄 Description

Summary

CdpConnection.connect is the single transport owner for every CDP WebSocket REA opens, and it defaulted maxPayload to 0. In ws, 0 means unlimited, and because the value is passed explicitly, it also overrides the 100 MiB default ws would otherwise apply, so the receiver guard was off for every connection that did not select a limit. All page-level paths fall into that group: the four CdpBrowserProvider operations (page observation, WebMCP discovery, and their session variants) plus CdpElectronProvider call openCdpTargetSession without limits, which means page-controlled content could deliver a single message of arbitrary size before any of REA's capture accounting saw a byte. This PR makes an omitted selection fall back to WEB_RUNTIME_LIMITS.protocolBytes (64 MiB), the same protocol budget the runtime session already selects explicitly, while explicit per-session budgets stay authoritative and the existing typed payload_limit close reason is unchanged. No issue is linked because this is standalone hardening at the transport owner rather than a report-driven fix.

Problem and expected behavior

Smallest trigger: open a page-scoped CDP connection through openCdpTargetSession without a limits argument, then have the target deliver one message larger than any sane protocol budget. Prior behavior: the message is accepted. This is reproduced on the base revision with a fake CDP reply of WEB_RUNTIME_LIMITS.protocolBytes + 1 bytes: the pending Runtime.enable command resolved with the oversized payload instead of rejecting. The violated invariant: page-controlled content must not decide how much memory the host retains for one message, and an over-budget frame should surface as the same typed transport failure the explicit-limit path already produces. Expected behavior: the receiver refuses the frame, the connection reports payload_limit, and the user-visible message names the selected budget in bytes, exactly like the existing maxPayloadBytes: 512 path does today.

Change and scope

The change is one owner edit in CdpConnection.connect (src/browser/CdpConnection.ts): the selected budget is resolved once as limits?.maxPayloadBytes ?? WEB_RUNTIME_LIMITS.protocolBytes and used for both the ws option and the connection instance, with a comment recording why an explicit 0 must not survive. This fits the architecture by normalizing at the boundary that owns the socket instead of editing five scattered call sites: any future caller that forgets to pass limits is bounded by default, and callers that do pass a budget (runtime sessions at 64 MiB, the V8 inspector at 16 MiB) are untouched. Intentionally not included: no per-operation budget tuning, no change to observation or capture budgets such as WEB_NETWORK_CAPTURE_LIMITS, no edits to CdpBrowserProvider or CdpElectronProvider, and no new configuration knob, because the existing limits parameter remains the override for any session that needs a different ceiling.

Contract and boundary impact

  • Semantic owner and earliest changed stage: browser provider transport, CdpConnection.connect in src/browser/CdpConnection.ts; domain schemas and application workflows untouched.
  • CLI and MCP/tool-catalog contract: none. No tool, schema, annotation, or catalog change; the error surface reuses the existing payload_limit transport reason already projected by BrowserObservationError.
  • Provider, bridge, target-format, or platform compatibility: applies uniformly to Chromium, Electron, and Playwright-managed page sockets through the shared ws receiver guard; no platform-specific code and no bridge change.
  • Evidence, artifact, provenance, or reconstruction contract: none. The refusal happens at frame receipt before message text is parsed or retained, so no identity, digest, or coverage projection changes.
  • Process execution, authorization, cleanup, or containment impact: oversize frames are refused by ws (surfacing as WS_ERR_UNSUPPORTED_MESSAGE_LENGTH, already mapped to payload_limit); no new process, network, or authority surface, and cleanup paths are unchanged.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in skill-src/ and never commit build outputs): none. No contract, catalog, or skill input changed, and no build output is committed.

Evidence and regression coverage

  • Tests added or updated: one new case in tests/boundary/browser/cdpConnection.test.ts ("bounds command payloads to the shared protocol budget when no limits are selected") connects without limits, receives a reply of WEB_RUNTIME_LIMITS.protocolBytes + 1 bytes from the fake CDP browser, and asserts rejection with reason: "payload_limit" and a user message containing 67108864 byte protocol budget. The payload-budget tests now live in their own describe block so the callback stays within the repository's 150-line function limit, and the existing explicit-512 case is unchanged as the regression guard for the override path.
  • Base reproduction or other evidence: on base 0fa0b046 the new case fails with "promise resolved instead of rejecting", proving the default path accepted the oversize frame; after the change the same case passes and the full cdpConnection.test.ts file reports 11/11.
  • User-visible CLI/MCP output: unchanged in shape. Default connections now emit the same payload_limit failure the explicit path already produces, and the message names the 67108864-byte budget when the shared default is what refused the frame.
  • Remaining proof gaps: no real Chrome or Electron run was performed locally, and the ceiling reuses the maintainer-selected WEB_RUNTIME_LIMITS.protocolBytes value rather than a measurement from a live browser; realistic CDP messages such as screenshots and DOM snapshots sit far below that budget.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npx vitest run tests/boundary/browser/cdpConnection.test.ts — 11 passed, including the new default-ceiling case, after rebasing onto be75ed5e.
  • npx vitest run tests/boundary/browser/ — 35 files passed; browserProcessStartup.test.ts, historicalCaptureDecoder.test.ts, and historicalWebCapture.test.ts fail 17 tests on this Windows host identically with and without the change (verified by stashing the diff and re-running the pristine base), so they are environmental and pre-existing.
  • npm run typecheck — exit 0 on the rebased branch.
  • npx oxlint on both changed files — 0 warnings, 0 errors; oxfmt --check on the committed (LF) form — clean.
  • Real browser lane (npm run verify:browser): not run locally because no Chrome runtime is available here; the fake-CDP boundary suite covers the changed connection path instead.

Compatibility, safety, and release

  • Breaking changes or migration steps: none for realistic traffic. Single messages above 64 MiB on connections that previously had no ceiling now fail with the typed payload_limit error instead of loading, which is the intended behavior change; sessions that need another ceiling already pass limits explicitly.
  • Real Hopper/Ghidra, browser, or OS coverage: not performed; the change is transport-level and platform-neutral, and the Windows-host boundary suites above exercised it.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the change removes a page-controlled memory amplification path on the host that serves MCP clients, adds no network, process, or authority surface, and does not persist or transmit frame content.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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/1645 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/10/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/cdp-default-payload-ceiling` --- ### 📝 Commits (1) - [`3d65f3e`](https://github.com/morluto/rea/commit/3d65f3e09d3d8543df9c1dc58d6e638af908cf0f) fix(browser): bound CDP message payloads to the shared protocol budget ### 📊 Changes **2 files changed** (+43 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `src/browser/CdpConnection.ts` (+8 -2) 📝 `tests/boundary/browser/cdpConnection.test.ts` (+35 -0) </details> ### 📄 Description ## Summary `CdpConnection.connect` is the single transport owner for every CDP WebSocket REA opens, and it defaulted `maxPayload` to `0`. In `ws`, `0` means unlimited, and because the value is passed explicitly, it also overrides the 100 MiB default `ws` would otherwise apply, so the receiver guard was off for every connection that did not select a limit. All page-level paths fall into that group: the four `CdpBrowserProvider` operations (page observation, WebMCP discovery, and their session variants) plus `CdpElectronProvider` call `openCdpTargetSession` without `limits`, which means page-controlled content could deliver a single message of arbitrary size before any of REA's capture accounting saw a byte. This PR makes an omitted selection fall back to `WEB_RUNTIME_LIMITS.protocolBytes` (64 MiB), the same protocol budget the runtime session already selects explicitly, while explicit per-session budgets stay authoritative and the existing typed `payload_limit` close reason is unchanged. No issue is linked because this is standalone hardening at the transport owner rather than a report-driven fix. ## Problem and expected behavior Smallest trigger: open a page-scoped CDP connection through `openCdpTargetSession` without a `limits` argument, then have the target deliver one message larger than any sane protocol budget. Prior behavior: the message is accepted. This is reproduced on the base revision with a fake CDP reply of `WEB_RUNTIME_LIMITS.protocolBytes + 1` bytes: the pending `Runtime.enable` command resolved with the oversized payload instead of rejecting. The violated invariant: page-controlled content must not decide how much memory the host retains for one message, and an over-budget frame should surface as the same typed transport failure the explicit-limit path already produces. Expected behavior: the receiver refuses the frame, the connection reports `payload_limit`, and the user-visible message names the selected budget in bytes, exactly like the existing `maxPayloadBytes: 512` path does today. ## Change and scope The change is one owner edit in `CdpConnection.connect` (`src/browser/CdpConnection.ts`): the selected budget is resolved once as `limits?.maxPayloadBytes ?? WEB_RUNTIME_LIMITS.protocolBytes` and used for both the `ws` option and the connection instance, with a comment recording why an explicit `0` must not survive. This fits the architecture by normalizing at the boundary that owns the socket instead of editing five scattered call sites: any future caller that forgets to pass `limits` is bounded by default, and callers that do pass a budget (runtime sessions at 64 MiB, the V8 inspector at 16 MiB) are untouched. Intentionally not included: no per-operation budget tuning, no change to observation or capture budgets such as `WEB_NETWORK_CAPTURE_LIMITS`, no edits to `CdpBrowserProvider` or `CdpElectronProvider`, and no new configuration knob, because the existing `limits` parameter remains the override for any session that needs a different ceiling. ## Contract and boundary impact - Semantic owner and earliest changed stage: browser provider transport, `CdpConnection.connect` in `src/browser/CdpConnection.ts`; domain schemas and application workflows untouched. - CLI and MCP/tool-catalog contract: none. No tool, schema, annotation, or catalog change; the error surface reuses the existing `payload_limit` transport reason already projected by `BrowserObservationError`. - Provider, bridge, target-format, or platform compatibility: applies uniformly to Chromium, Electron, and Playwright-managed page sockets through the shared `ws` receiver guard; no platform-specific code and no bridge change. - Evidence, artifact, provenance, or reconstruction contract: none. The refusal happens at frame receipt before message text is parsed or retained, so no identity, digest, or coverage projection changes. - Process execution, authorization, cleanup, or containment impact: oversize frames are refused by `ws` (surfacing as `WS_ERR_UNSUPPORTED_MESSAGE_LENGTH`, already mapped to `payload_limit`); no new process, network, or authority surface, and cleanup paths are unchanged. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `skill-src/` and never commit build outputs): none. No contract, catalog, or skill input changed, and no build output is committed. ## Evidence and regression coverage - Tests added or updated: one new case in `tests/boundary/browser/cdpConnection.test.ts` ("bounds command payloads to the shared protocol budget when no limits are selected") connects without `limits`, receives a reply of `WEB_RUNTIME_LIMITS.protocolBytes + 1` bytes from the fake CDP browser, and asserts rejection with `reason: "payload_limit"` and a user message containing `67108864 byte protocol budget`. The payload-budget tests now live in their own `describe` block so the callback stays within the repository's 150-line function limit, and the existing explicit-`512` case is unchanged as the regression guard for the override path. - Base reproduction or other evidence: on base `0fa0b046` the new case fails with "promise resolved instead of rejecting", proving the default path accepted the oversize frame; after the change the same case passes and the full `cdpConnection.test.ts` file reports 11/11. - User-visible CLI/MCP output: unchanged in shape. Default connections now emit the same `payload_limit` failure the explicit path already produces, and the message names the 67108864-byte budget when the shared default is what refused the frame. - Remaining proof gaps: no real Chrome or Electron run was performed locally, and the ceiling reuses the maintainer-selected `WEB_RUNTIME_LIMITS.protocolBytes` value rather than a measurement from a live browser; realistic CDP messages such as screenshots and DOM snapshots sit far below that budget. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npx vitest run tests/boundary/browser/cdpConnection.test.ts` — 11 passed, including the new default-ceiling case, after rebasing onto `be75ed5e`. - `npx vitest run tests/boundary/browser/` — 35 files passed; `browserProcessStartup.test.ts`, `historicalCaptureDecoder.test.ts`, and `historicalWebCapture.test.ts` fail 17 tests on this Windows host identically with and without the change (verified by stashing the diff and re-running the pristine base), so they are environmental and pre-existing. - `npm run typecheck` — exit 0 on the rebased branch. - `npx oxlint` on both changed files — 0 warnings, 0 errors; `oxfmt --check` on the committed (LF) form — clean. - Real browser lane (`npm run verify:browser`): not run locally because no Chrome runtime is available here; the fake-CDP boundary suite covers the changed connection path instead. ## Compatibility, safety, and release - Breaking changes or migration steps: none for realistic traffic. Single messages above 64 MiB on connections that previously had no ceiling now fail with the typed `payload_limit` error instead of loading, which is the intended behavior change; sessions that need another ceiling already pass `limits` explicitly. - Real Hopper/Ghidra, browser, or OS coverage: not performed; the change is transport-level and platform-neutral, and the Windows-host boundary suites above exercised it. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the change removes a page-controlled memory amplification path on the host that serves MCP clients, adds no network, process, or authority surface, and does not persist or transmit frame content. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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 00:54:23 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#4723
No description provided.