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 #4616] [CLOSED] fix(mcp): leave shared observation providers to the transport that loads them #6334

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4616
Author: @starterio-dotcom
Created: 10/16/2026
Status: ❌ Closed

Base: main ← Head: claude/elegant-bartik-298d88

📝 Commits (1)

  • ae966ee fix(mcp): leave shared observation providers to the transport that loads them

📊 Changes

7 files changed (+302 additions, -104 deletions)

View changed files

📝 src/application/OptionalObservationProviders.ts (+4 -1)
📝 src/main/transport.ts (+0 -1)
📝 src/server/createServer.ts (+4 -9)
📝 tests/boundary/mcp/browserScenarioMcp.test.ts (+9 -88)
📝 tests/boundary/mcp/serverLifecycleMcp.test.ts (+7 -4)
📝 tests/boundary/process/browserScenarioProbeLifecycle.test.ts (+188 -1)
➕ tests/fixtures/browserScenarioCapture.ts (+90 -0)

📄 Description

Summary

capture_browser_scenario over MCP could fail for the rest of the server process with cleanup_incomplete / "Browser scenario provider is closing." even though no caller had closed anything. The process-shared Playwright scenario provider was being closed by a server instance that did not own it: when the MCP SDK's stdio entry discards its server/discover probe instance for a legacy initialize on the same connection, that instance's provider cleanup closed the shared port, and the pinned replacement instance then answered every scenario call with the closing error. #2205 fixed this for 6.5.0 and #4274 reintroduced a server-side close behind optionalObservationProviderOwner, whose default still closed injected ports. Refs #2195, #4274.

Problem and expected behavior

Trigger: one stdio connection that opens with a modern server/discover and continues with a legacy initialize, then calls capture_browser_scenario. Violated invariant: a resource is released only by its owner. startMcpTransport loads the optional observation ports once per process and hands the same instances to every server instance the SDK constructs, so a server instance must never close them. Expected: scenario calls on the pinned instance succeed, and the shared providers close exactly once at process shutdown.

Change and scope

  • createServer no longer closes the injected browser, browser-scenario, or Electron observation ports; the optionalObservationProviderOwner option is removed because the server never constructs those ports and therefore never owns them.
  • startMcpTransport remains the single owner and closes them once at process shutdown (unchanged behavior, no longer dependent on a flag).
  • The ownership rule is stated on OptionalObservationProviders.
  • The CLI path (capture-browser-scenario) is unchanged: it still creates and closes its own provider per command.

Not included: the Windows run-exclusive wrapper's dependency on the packaged native addon, which surfaced while validating this change, is handled separately.

Contribution scope: ordinary fix within existing lifecycle boundaries; maintainer scope decision not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: startMcpTransport (src/main/transport.ts) owns the loaded optional observation ports; createServer (src/server/createServer.ts) drops its close branch for them.
  • Contribution scope fit and linked maintainer decision: ordinary fix; not applicable.
  • CLI and MCP/tool-catalog contract: unchanged. CreateServerOptions.optionalObservationProviderOwner is removed; it was an internal composition option, not a CLI or MCP contract.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: shared observation providers close only at MCP process shutdown; a discarded probe instance closes only the services it bound itself.
  • Generated metadata, package, or installation impact: none.

Expected effects: lifecycle ownership only; this change adds no target interaction.

  • 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/process/browserScenarioProbeLifecycle.test.ts: new test that drives the production serveStdio entry over an in-memory wire through a modern server/discover probe, a legacy initialize, and a capture_browser_scenario call on the pinned instance, then asserts the provider closes exactly once at process shutdown.
    • tests/boundary/mcp/serverLifecycleMcp.test.ts: the bound-service shutdown test now asserts that an injected scenario port is never closed by server.close().
    • tests/fixtures/browserScenarioCapture.ts: the valid fake capture builder, shared by the scenario MCP tests.
  • Base reproduction or other evidence (executed): against a 6.4.0 build (main at eaf88aca), a raw stdio JSON-RPC script sending server/discover → legacy initialize → tools/call capture_browser_scenario returned:
    {"error":{"code":"cleanup_incomplete","category":"execution_failure","message":"Browser scenario provider is closing.",...,"details":{"operation":"capture_browser_scenario","reason":"cleanup_failed","cleanup":"incomplete","resources":[],"cleanup_reason":"Provider is closing","execution_failure":"unreadable_output"}}}
    With the legacy initialize only, the same call reached the provider. On this branch, temporarily restoring the server-side close of options.browserScenarioCapture made both probe tests fail (expected "vi.fn()" to not be called at all, but actually been called 1 times); with the change they pass.
  • User-visible CLI/MCP output: none changed.
  • Remaining proof gaps: the exact opening exchange Claude Code sent in the originally reported session was not captured; a direct tool call through the same 6.4.0 build in another session did not trip the failure, so the trigger depends on the client's handshake. The new test uses a fake scenario port, not a real browser.

For evidence-bearing changes:

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

Validation performed

  • npm run check:fast — typecheck and lint, 2 tasks successful.
  • npm run test:focused -- tests/boundary/process/browserScenarioProbeLifecycle.test.ts tests/boundary/mcp/serverLifecycleMcp.test.ts tests/boundary/mcp/browserScenarioMcp.test.ts tests/boundary/mcp/shutdown.test.ts tests/boundary/mcp/optionalProviderIsolation.test.ts src/server/shutdownRegistration.test.ts — 6 files, 29 tests passed (Windows 11, Node 24.21.0; the packaged Windows native artifact was restored from the rea-agents@6.5.0 tarball so the build step and SQLite lifecycle cases could run).
  • Runtime reproduction script against the 6.4.0 build — results quoted above.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. CreateServerOptions.optionalObservationProviderOwner is removed; no caller outside src/main/transport.ts passed it.
  • Real Hopper/Ghidra, browser, or OS coverage: no real browser run; the Playwright provider's own close semantics are unchanged.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none required; shared provider cleanup still happens once at process shutdown.

Author readiness

Human owner: @starterio-dotcom

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

🤖 Generated with Claude Code

🔄 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/4616 **Author:** [@starterio-dotcom](https://github.com/starterio-dotcom) **Created:** 10/16/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `claude/elegant-bartik-298d88` --- ### 📝 Commits (1) - [`ae966ee`](https://github.com/morluto/rea/commit/ae966ee238c6eb55c9b0519bf616ae49b960e75a) fix(mcp): leave shared observation providers to the transport that loads them ### 📊 Changes **7 files changed** (+302 additions, -104 deletions) <details> <summary>View changed files</summary> 📝 `src/application/OptionalObservationProviders.ts` (+4 -1) 📝 `src/main/transport.ts` (+0 -1) 📝 `src/server/createServer.ts` (+4 -9) 📝 `tests/boundary/mcp/browserScenarioMcp.test.ts` (+9 -88) 📝 `tests/boundary/mcp/serverLifecycleMcp.test.ts` (+7 -4) 📝 `tests/boundary/process/browserScenarioProbeLifecycle.test.ts` (+188 -1) ➕ `tests/fixtures/browserScenarioCapture.ts` (+90 -0) </details> ### 📄 Description ## Summary `capture_browser_scenario` over MCP could fail for the rest of the server process with `cleanup_incomplete` / "Browser scenario provider is closing." even though no caller had closed anything. The process-shared Playwright scenario provider was being closed by a server instance that did not own it: when the MCP SDK's stdio entry discards its `server/discover` probe instance for a legacy `initialize` on the same connection, that instance's provider cleanup closed the shared port, and the pinned replacement instance then answered every scenario call with the closing error. #2205 fixed this for 6.5.0 and #4274 reintroduced a server-side close behind `optionalObservationProviderOwner`, whose default still closed injected ports. Refs #2195, #4274. ## Problem and expected behavior Trigger: one stdio connection that opens with a modern `server/discover` and continues with a legacy `initialize`, then calls `capture_browser_scenario`. Violated invariant: a resource is released only by its owner. `startMcpTransport` loads the optional observation ports once per process and hands the same instances to every server instance the SDK constructs, so a server instance must never close them. Expected: scenario calls on the pinned instance succeed, and the shared providers close exactly once at process shutdown. ## Change and scope - `createServer` no longer closes the injected browser, browser-scenario, or Electron observation ports; the `optionalObservationProviderOwner` option is removed because the server never constructs those ports and therefore never owns them. - `startMcpTransport` remains the single owner and closes them once at process shutdown (unchanged behavior, no longer dependent on a flag). - The ownership rule is stated on `OptionalObservationProviders`. - The CLI path (`capture-browser-scenario`) is unchanged: it still creates and closes its own provider per command. Not included: the Windows `run-exclusive` wrapper's dependency on the packaged native addon, which surfaced while validating this change, is handled separately. Contribution scope: ordinary fix within existing lifecycle boundaries; maintainer scope decision not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `startMcpTransport` (src/main/transport.ts) owns the loaded optional observation ports; `createServer` (src/server/createServer.ts) drops its close branch for them. - Contribution scope fit and linked maintainer decision: ordinary fix; not applicable. - CLI and MCP/tool-catalog contract: unchanged. `CreateServerOptions.optionalObservationProviderOwner` is removed; it was an internal composition option, not a CLI or MCP contract. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: shared observation providers close only at MCP process shutdown; a discarded probe instance closes only the services it bound itself. - Generated metadata, package, or installation impact: none. Expected effects: lifecycle ownership only; this change adds no target interaction. - [ ] 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/process/browserScenarioProbeLifecycle.test.ts`: new test that drives the production `serveStdio` entry over an in-memory wire through a modern `server/discover` probe, a legacy `initialize`, and a `capture_browser_scenario` call on the pinned instance, then asserts the provider closes exactly once at process shutdown. - `tests/boundary/mcp/serverLifecycleMcp.test.ts`: the bound-service shutdown test now asserts that an injected scenario port is never closed by `server.close()`. - `tests/fixtures/browserScenarioCapture.ts`: the valid fake capture builder, shared by the scenario MCP tests. - Base reproduction or other evidence (executed): against a 6.4.0 build (main at eaf88aca), a raw stdio JSON-RPC script sending `server/discover` → legacy `initialize` → `tools/call capture_browser_scenario` returned: `{"error":{"code":"cleanup_incomplete","category":"execution_failure","message":"Browser scenario provider is closing.",...,"details":{"operation":"capture_browser_scenario","reason":"cleanup_failed","cleanup":"incomplete","resources":[],"cleanup_reason":"Provider is closing","execution_failure":"unreadable_output"}}}` With the legacy `initialize` only, the same call reached the provider. On this branch, temporarily restoring the server-side close of `options.browserScenarioCapture` made both probe tests fail (`expected "vi.fn()" to not be called at all, but actually been called 1 times`); with the change they pass. - User-visible CLI/MCP output: none changed. - Remaining proof gaps: the exact opening exchange Claude Code sent in the originally reported session was not captured; a direct tool call through the same 6.4.0 build in another session did not trip the failure, so the trigger depends on the client's handshake. The new test uses a fake scenario port, not a real browser. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run check:fast` — typecheck and lint, 2 tasks successful. - `npm run test:focused -- tests/boundary/process/browserScenarioProbeLifecycle.test.ts tests/boundary/mcp/serverLifecycleMcp.test.ts tests/boundary/mcp/browserScenarioMcp.test.ts tests/boundary/mcp/shutdown.test.ts tests/boundary/mcp/optionalProviderIsolation.test.ts src/server/shutdownRegistration.test.ts` — 6 files, 29 tests passed (Windows 11, Node 24.21.0; the packaged Windows native artifact was restored from the rea-agents@6.5.0 tarball so the build step and SQLite lifecycle cases could run). - Runtime reproduction script against the 6.4.0 build — results quoted above. ## Compatibility, safety, and release - Breaking changes or migration steps: none. `CreateServerOptions.optionalObservationProviderOwner` is removed; no caller outside `src/main/transport.ts` passed it. - Real Hopper/Ghidra, browser, or OS coverage: no real browser run; the Playwright provider's own close semantics are unchanged. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none required; shared provider cleanup still happens once at process shutdown. ## Author readiness Human owner: @starterio-dotcom - [ ] 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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:13:39 +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#6334
No description provided.