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 #6276] [CLOSED] fix(browser): start coverage at domain enablement #7249

New issue
Closed
opened 2026-11-01 21:46:28 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:46:28 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6276
Author: @sachinkr7368
Created: 10/22/2026
Status: ❌ Closed

Base: main ← Head: fix/6232-coverage-start

📝 Commits (1)

  • 5abcff3 fix(browser): start coverage at domain enablement

📊 Changes

3 files changed (+105 additions, -10 deletions)

View changed files

📝 docs/browser-observation.md (+1 -1)
📝 src/browser/CdpPageCapture.ts (+15 -9)
➕ tests/boundary/mcp/coverageStart.test.ts (+89 -0)

📄 Description

Summary

inspect_web_page now reports network.coverage_started_at and console.coverage_started_at from the moment REA dispatches the corresponding CDP domain-enable command, instead of reusing capture_window.started_at from before attach and setup. Events delivered while a domain is being enabled therefore remain inside that section's reported coverage boundary. Fixes #6232.

Problem and expected behavior

On the base revision, normalizedInspection set both section timestamps to state.startedAt, which is captured before Page.enable, the authorized-main-frame check and enableObservationDomains. A successful MCP request against the repository's loopback CDP fake therefore returned:

  • network.coverage_started_at === capture_window.started_at, and
  • console.coverage_started_at === capture_window.started_at,

even though Runtime.enable and Network.enable had not been dispatched yet. CDP can deliver events after a command is dispatched but before its reply, and the capture already ingests those events; reporting a start later than their delivery would place retained events outside their own coverage window.

Expected: each section's coverage start reflects when observation of that domain becomes available, and an event delivered while a domain is being enabled remains represented within the boundary. capture_window.started_at and prior_activity_available: false are unchanged.

Change and scope

  • src/browser/CdpPageCapture.ts: add networkCoverageStartedAt / consoleCoverageStartedAt to CaptureState; record each immediately before dispatching Network.enable / Runtime.enable; report them in the two section objects.
  • tests/boundary/mcp/coverageStart.test.ts: MCP regression with deterministic 25 ms reply barriers for Page.enable, Runtime.enable and Network.enable, a Network.enable event delivered before its reply, and assertions that both starts are later than capture entry, at/after the Page.enable reply, at/before their enable command reaches the fake, and that the pre-reply request remains present. The per-command barriers make a timestamp recorded after an enable reply fail the test.
  • docs/browser-observation.md: clarify that coverage starts when REA begins enabling the domains and includes events delivered during enablement.

Not included: no change to event filtering or retention, capture_window, prior_activity_available, the scripts/workers/storage sections, or CDP command order. This is an ordinary fix inside the existing inspect_web_page boundary; no new capability or maintainer scope decision is required.

Contract and boundary impact

  • Semantic owner and earliest changed stage: browser observation normalization in src/browser/CdpPageCapture.ts; no new capture stage.
  • Contribution scope fit and linked maintainer decision: existing inspect_web_page behavior; not applicable (no new capability).
  • CLI and MCP/tool-catalog contract: the inspect_web_page output schema is unchanged; the two timestamps now reflect domain enablement. CLI projection carries the same corrected timestamps.
  • Provider, bridge, target-format, or platform compatibility: none; CDP command order and transport are unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged; raw headers, bodies, cookies, storage values and console objects remain unretained.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged; authorized-main-frame, origin checks and capture cleanup are untouched.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: tests/boundary/mcp/coverageStart.test.ts exercises the registered MCP tool and production CDP provider against the loopback fake, with a 25 ms Page.enable reply barrier and a Network.enable event sent before its reply.
  • Base reproduction: with the source fix reverted and the regression kept, npm run test:boundary -- tests/boundary/mcp/coverageStart.test.ts failed at expect(networkStart).toBeGreaterThan(captureStart) with expected 1792652942473 to be greater than 1792652942473; the same test passes with the fix. This shows coverage previously started at capture entry rather than at domain enablement.
  • Forward check: a temporary implementation that recorded both timestamps after the enable replies failed the same test with expected 1792654033686 to be less than or equal to 1792654033654, confirming the barriers distinguish dispatch from reply. The mutation was reverted.
  • User-visible CLI/MCP output (if applicable): inspect_web_page now returns network.coverage_started_at and console.coverage_started_at after capture_window.started_at, at or before the corresponding Network.enable / Runtime.enable dispatch. All other output is unchanged.
  • Remaining proof gaps: no real browser was run; ordering is exercised against the repository's loopback CDP fake, which models command latency and pre-reply events deterministically. The change is platform-neutral and has no OS-specific branches.

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

  • Base reproduction with the source fix reverted — 1 file, 1 failed (networkStart === captureStart).
  • Temporary post-reply timestamp mutation (reverted) — 1 file, 1 failed (networkStart exceeded the Network.enable receipt time).
  • npm run test:boundary -- tests/boundary/mcp/coverageStart.test.ts — 1 file, 1 test passed with the fix.
  • npm run test:boundary -- tests/boundary/mcp/browserMcp.test.ts tests/boundary/browser/ — 60 passed | 1 skipped (61 files), 792 passed | 6 skipped (798 tests).
  • npm run test:local -- <all 56 src/browser/**/*.test.ts files> — 56 files, 744 tests passed.
  • npm run typecheck — exit 0.
  • npm run check — pass (Turbo tasks and architecture guards across 1,785 source files).
  • npm run docs:check — 9 tests passed.
  • npx oxfmt --check src/browser/CdpPageCapture.ts tests/boundary/mcp/coverageStart.test.ts docs/browser-observation.md — pass.
  • git diff --check — clean.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. The timestamps are descriptive metadata within the existing schema.
  • Real Hopper/Ghidra, browser, or OS coverage: no real browser was used; the production CDP provider was exercised against the suite's loopback HTTP/WebSocket fake. See the proof gaps above.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none. The change only moves two timestamps later within an already-reported capture window; no new data is retained.

Author readiness

Human owner: @sachinkr7368

  • 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.

AI-assisted: the diff and evidence were prepared by an AI coding agent. The human owner directed that this PR be marked ready for initial review and dictated the readiness declarations above.

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/6276 **Author:** [@sachinkr7368](https://github.com/sachinkr7368) **Created:** 10/22/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/6232-coverage-start` --- ### 📝 Commits (1) - [`5abcff3`](https://github.com/morluto/rea/commit/5abcff327182b4a218f55717cb247e454d9a9994) fix(browser): start coverage at domain enablement ### 📊 Changes **3 files changed** (+105 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `docs/browser-observation.md` (+1 -1) 📝 `src/browser/CdpPageCapture.ts` (+15 -9) ➕ `tests/boundary/mcp/coverageStart.test.ts` (+89 -0) </details> ### 📄 Description ## Summary `inspect_web_page` now reports `network.coverage_started_at` and `console.coverage_started_at` from the moment REA dispatches the corresponding CDP domain-enable command, instead of reusing `capture_window.started_at` from before attach and setup. Events delivered while a domain is being enabled therefore remain inside that section's reported coverage boundary. Fixes #6232. ## Problem and expected behavior On the base revision, `normalizedInspection` set both section timestamps to `state.startedAt`, which is captured before `Page.enable`, the authorized-main-frame check and `enableObservationDomains`. A successful MCP request against the repository's loopback CDP fake therefore returned: - `network.coverage_started_at === capture_window.started_at`, and - `console.coverage_started_at === capture_window.started_at`, even though `Runtime.enable` and `Network.enable` had not been dispatched yet. CDP can deliver events after a command is dispatched but before its reply, and the capture already ingests those events; reporting a start later than their delivery would place retained events outside their own coverage window. Expected: each section's coverage start reflects when observation of that domain becomes available, and an event delivered while a domain is being enabled remains represented within the boundary. `capture_window.started_at` and `prior_activity_available: false` are unchanged. ## Change and scope - `src/browser/CdpPageCapture.ts`: add `networkCoverageStartedAt` / `consoleCoverageStartedAt` to `CaptureState`; record each immediately before dispatching `Network.enable` / `Runtime.enable`; report them in the two section objects. - `tests/boundary/mcp/coverageStart.test.ts`: MCP regression with deterministic 25 ms reply barriers for `Page.enable`, `Runtime.enable` and `Network.enable`, a `Network.enable` event delivered before its reply, and assertions that both starts are later than capture entry, at/after the `Page.enable` reply, at/before their enable command reaches the fake, and that the pre-reply request remains present. The per-command barriers make a timestamp recorded after an enable reply fail the test. - `docs/browser-observation.md`: clarify that coverage starts when REA begins enabling the domains and includes events delivered during enablement. Not included: no change to event filtering or retention, `capture_window`, `prior_activity_available`, the scripts/workers/storage sections, or CDP command order. This is an ordinary fix inside the existing `inspect_web_page` boundary; no new capability or maintainer scope decision is required. ## Contract and boundary impact - Semantic owner and earliest changed stage: browser observation normalization in `src/browser/CdpPageCapture.ts`; no new capture stage. - Contribution scope fit and linked maintainer decision: existing `inspect_web_page` behavior; not applicable (no new capability). - CLI and MCP/tool-catalog contract: the `inspect_web_page` output schema is unchanged; the two timestamps now reflect domain enablement. CLI projection carries the same corrected timestamps. - Provider, bridge, target-format, or platform compatibility: none; CDP command order and transport are unchanged. - Evidence, artifact, provenance, or reconstruction contract: unchanged; raw headers, bodies, cookies, storage values and console objects remain unretained. - Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged; authorized-main-frame, origin checks and capture cleanup are untouched. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] 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: `tests/boundary/mcp/coverageStart.test.ts` exercises the registered MCP tool and production CDP provider against the loopback fake, with a 25 ms `Page.enable` reply barrier and a `Network.enable` event sent before its reply. - Base reproduction: with the source fix reverted and the regression kept, `npm run test:boundary -- tests/boundary/mcp/coverageStart.test.ts` failed at `expect(networkStart).toBeGreaterThan(captureStart)` with `expected 1792652942473 to be greater than 1792652942473`; the same test passes with the fix. This shows coverage previously started at capture entry rather than at domain enablement. - Forward check: a temporary implementation that recorded both timestamps after the enable replies failed the same test with `expected 1792654033686 to be less than or equal to 1792654033654`, confirming the barriers distinguish dispatch from reply. The mutation was reverted. - User-visible CLI/MCP output (if applicable): `inspect_web_page` now returns `network.coverage_started_at` and `console.coverage_started_at` after `capture_window.started_at`, at or before the corresponding `Network.enable` / `Runtime.enable` dispatch. All other output is unchanged. - Remaining proof gaps: no real browser was run; ordering is exercised against the repository's loopback CDP fake, which models command latency and pre-reply events deterministically. The change is platform-neutral and has no OS-specific branches. 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 - Base reproduction with the source fix reverted — 1 file, 1 failed (`networkStart === captureStart`). - Temporary post-reply timestamp mutation (reverted) — 1 file, 1 failed (`networkStart` exceeded the `Network.enable` receipt time). - `npm run test:boundary -- tests/boundary/mcp/coverageStart.test.ts` — 1 file, 1 test passed with the fix. - `npm run test:boundary -- tests/boundary/mcp/browserMcp.test.ts tests/boundary/browser/` — 60 passed | 1 skipped (61 files), 792 passed | 6 skipped (798 tests). - `npm run test:local -- <all 56 src/browser/**/*.test.ts files>` — 56 files, 744 tests passed. - `npm run typecheck` — exit 0. - `npm run check` — pass (Turbo tasks and architecture guards across 1,785 source files). - `npm run docs:check` — 9 tests passed. - `npx oxfmt --check src/browser/CdpPageCapture.ts tests/boundary/mcp/coverageStart.test.ts docs/browser-observation.md` — pass. - `git diff --check` — clean. ## Compatibility, safety, and release - Breaking changes or migration steps: none. The timestamps are descriptive metadata within the existing schema. - Real Hopper/Ghidra, browser, or OS coverage: no real browser was used; the production CDP provider was exercised against the suite's loopback HTTP/WebSocket fake. See the proof gaps above. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. The change only moves two timestamps later within an already-reported capture window; no new data is retained. ## Author readiness Human owner: @sachinkr7368 - [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. _AI-assisted: the diff and evidence were prepared by an AI coding agent. The human owner directed that this PR be marked ready for initial review and dictated the readiness declarations above._ ## 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:46:28 +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#7249
No description provided.