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 #4236] [CLOSED] fix(hopper): report a readiness wait as starting instead of idle (#4226) #6139

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

📋 Pull Request Information

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

Base: main ← Head: fix/hopper-starting-readiness-telemetry

📝 Commits (1)

  • 09cf6b9 fix(hopper): report a readiness wait as starting instead of idle

📊 Changes

3 files changed (+129 additions, -17 deletions)

View changed files

📝 src/domain/providerOperationHealth.ts (+2 -0)
📝 src/hopper/HopperClient.ts (+42 -16)
📝 tests/boundary/providers/hopper/hopperClient.startupFailures.test.ts (+85 -1)

📄 Description

Summary

While Hopper's bridge startup is still waiting for readiness, binary_session reported provider_operation_health.state as idle with no active or queued requests. That made a provider whose bridge had never completed its authenticated handshake indistinguishable from an idle, ready provider. This adds a starting state and reports it while a startup promise is outstanding and the bridge is not ready, so a caller can tell a starting provider from a healthy idle one.

Refs #4226.

Problem and expected behavior

The smallest trigger is a Hopper bridge that is still in its readiness wait: the launcher has started, but the authenticated health handshake has not completed. During that window HopperClient.operationHealth() fell through to the idle branch and returned { state: "idle", stage: null, retryAction: null, exitCode: null, requests: [] }, while isReady() was still false. The session status then showed analysis activity idle with no queued work even though a readiness wait was in flight.

The violated invariant is that caller-visible provider telemetry must not report an idle provider while a lifecycle transition is outstanding. The expected behavior is that a provider that is starting is reported as starting with a wait recovery action, and that a genuinely idle provider still reports idle.

Change and scope

src/domain/providerOperationHealth.ts adds starting to PROVIDER_OPERATION_STATES and maps it to the wait retry action, alongside busy. src/hopper/HopperClient.ts reports starting from operationHealth() when #startPromise is outstanding and isReady() is false, with stage: "launch" and no retained requests. A client that has finished starting, or one that never started, still reports idle unchanged.

This is deliberately the smallest slice of #4226 that can be established without a real macOS Hopper. It does not touch pre-handshake recovery, primary-diagnostic retention while cleanup is pending, cleanup-pending telemetry, or close/reopen after positive closure proof. Those remain open in the report and are not addressed here.

Contract and boundary impact

  • Semantic owner and earliest changed stage: provider-operation telemetry in src/domain/providerOperationHealth.ts; the earliest changed stage is Hopper bridge startup in src/hopper/HopperClient.ts.
  • Contribution scope fit and linked maintainer decision: ordinary bug fix within the existing Hopper adapter and session-status contract; a separate maintainer scope decision is not applicable.
  • CLI and MCP/tool-catalog contract: provider_operation_health.state gains one additional enum value, starting. This is additive to the advertised output schema; the existing values are unchanged and no input contract changes.
  • Provider, bridge, target-format, or platform compatibility: Hopper-only telemetry; no provider protocol, bridge, or target-format change, and the state is produced from existing in-process startup bookkeeping.
  • Evidence, artifact, provenance, or reconstruction contract: no product Evidence change.
  • Target selection, authority, upstream behavior, and cleanup details: no change to target selection, execution authority, or cleanup; the change only reports an already-outstanding startup.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: the generated MCP catalog picks up the new enum value; npm run metadata:check passes.

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/providers/hopper/hopperClient.startupFailures.test.ts gains a readiness-telemetry case that starts a silent launcher whose bridge socket never appears, waits on operationHealth(), and asserts state: "starting", retryAction: "wait", exitCode: null, requests: [], with isReady() false and requestActivity() null.
  • Base reproduction or other evidence: an independent socket-free probe on a real Windows 11 x64 host (Node 24.21.0) showed operationHealth() returning {"state":"idle",...} while isReady() was false during an outstanding readiness wait, matching the report.
  • User-visible CLI/MCP output (if applicable): the change is visible as provider_operation_health.state: "starting" in binary_session while startup is pending. The real macOS stdio MCP session from the report was not re-run.
  • Remaining proof gaps: no real macOS Hopper host was available. The bug and the fix are established at the adapter and session-status boundary with a controlled launcher, not through a real Hopper engine. The remaining items in #4226 (pre-handshake recovery, primary diagnostic retention during cleanup, cleanup-pending telemetry, close/reopen after closure proof) are not covered. Several Hopper boundary tests in this checkout require Unix sockets and do not run on Windows.

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/providers/hopper/hopperClient.startupFailures.test.ts -t "readiness wait as starting" --project boundary — 1 passed.
  • Red-green check — reverting providerOperationHealth.ts and HopperClient.ts makes the new case fail with expected { state: 'idle' } to match { state: 'starting' }; restoring both makes it pass.
  • npx vitest run src/domain/analysisErrorProjection.test.ts src/hopper/HopperProvider.test.ts src/hopper/HopperCleanup.test.ts — 62 passed.
  • npm run metadata:check — passed; the generated MCP catalog accepts the new enum value.
  • npx vitest run tests/boundary/mcp/advertisedPatternsVMode.test.ts --project mcp-boundary — 1 passed.
  • npx vitest run tests/composition/analysis-sessions/binarySession.test.ts --project composition — 42 passed, 1 pre-existing Windows symlink failure (EPERM), identical with the change stashed.
  • npx vitest run tests/boundary/mcp/sessionMcp.test.ts --project mcp-boundary — 8 passed, 1 pre-existing timeout, identical with the change stashed.
  • npx oxlint and npx oxfmt --check on the three changed files — 0 errors, format clean.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. starting is an added value on an output enum; existing values and input contracts are unchanged. Clients that switch exhaustively on the previous set should handle the new value, which the change documents here.
  • Real Hopper/Ghidra, browser, or OS coverage: no real Hopper engine was run; the change is verified with a controlled launcher at the adapter boundary. A real macOS Hopper check remains a gap.
  • Package or release metadata impact: the generated MCP catalog reflects the new enum value; no package or installation change.
  • Security, privacy, process, or containment review: no target execution, injection, mutation, network, or filesystem change. The state is derived from existing in-process startup bookkeeping.

Author readiness

Human owner: @DeryFerd

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/4236 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/15/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/hopper-starting-readiness-telemetry` --- ### 📝 Commits (1) - [`09cf6b9`](https://github.com/morluto/rea/commit/09cf6b9b2bd2bda37edf175495599d607a8dfc93) fix(hopper): report a readiness wait as starting instead of idle ### 📊 Changes **3 files changed** (+129 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/providerOperationHealth.ts` (+2 -0) 📝 `src/hopper/HopperClient.ts` (+42 -16) 📝 `tests/boundary/providers/hopper/hopperClient.startupFailures.test.ts` (+85 -1) </details> ### 📄 Description ## Summary While Hopper's bridge startup is still waiting for readiness, `binary_session` reported `provider_operation_health.state` as `idle` with no active or queued requests. That made a provider whose bridge had never completed its authenticated handshake indistinguishable from an idle, ready provider. This adds a `starting` state and reports it while a startup promise is outstanding and the bridge is not ready, so a caller can tell a starting provider from a healthy idle one. Refs #4226. ## Problem and expected behavior The smallest trigger is a Hopper bridge that is still in its readiness wait: the launcher has started, but the authenticated `health` handshake has not completed. During that window `HopperClient.operationHealth()` fell through to the idle branch and returned `{ state: "idle", stage: null, retryAction: null, exitCode: null, requests: [] }`, while `isReady()` was still `false`. The session status then showed analysis activity idle with no queued work even though a readiness wait was in flight. The violated invariant is that caller-visible provider telemetry must not report an idle provider while a lifecycle transition is outstanding. The expected behavior is that a provider that is starting is reported as starting with a wait recovery action, and that a genuinely idle provider still reports idle. ## Change and scope `src/domain/providerOperationHealth.ts` adds `starting` to `PROVIDER_OPERATION_STATES` and maps it to the `wait` retry action, alongside `busy`. `src/hopper/HopperClient.ts` reports `starting` from `operationHealth()` when `#startPromise` is outstanding and `isReady()` is false, with `stage: "launch"` and no retained requests. A client that has finished starting, or one that never started, still reports `idle` unchanged. This is deliberately the smallest slice of #4226 that can be established without a real macOS Hopper. It does not touch pre-handshake recovery, primary-diagnostic retention while cleanup is pending, cleanup-pending telemetry, or close/reopen after positive closure proof. Those remain open in the report and are not addressed here. ## Contract and boundary impact - Semantic owner and earliest changed stage: provider-operation telemetry in `src/domain/providerOperationHealth.ts`; the earliest changed stage is Hopper bridge startup in `src/hopper/HopperClient.ts`. - Contribution scope fit and linked maintainer decision: ordinary bug fix within the existing Hopper adapter and session-status contract; a separate maintainer scope decision is not applicable. - CLI and MCP/tool-catalog contract: `provider_operation_health.state` gains one additional enum value, `starting`. This is additive to the advertised output schema; the existing values are unchanged and no input contract changes. - Provider, bridge, target-format, or platform compatibility: Hopper-only telemetry; no provider protocol, bridge, or target-format change, and the state is produced from existing in-process startup bookkeeping. - Evidence, artifact, provenance, or reconstruction contract: no product Evidence change. - Target selection, authority, upstream behavior, and cleanup details: no change to target selection, execution authority, or cleanup; the change only reports an already-outstanding startup. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: the generated MCP catalog picks up the new enum value; `npm run metadata:check` passes. 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. - [x] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/providers/hopper/hopperClient.startupFailures.test.ts` gains a readiness-telemetry case that starts a silent launcher whose bridge socket never appears, waits on `operationHealth()`, and asserts `state: "starting"`, `retryAction: "wait"`, `exitCode: null`, `requests: []`, with `isReady()` false and `requestActivity()` null. - Base reproduction or other evidence: an independent socket-free probe on a real Windows 11 x64 host (Node 24.21.0) showed `operationHealth()` returning `{"state":"idle",...}` while `isReady()` was `false` during an outstanding readiness wait, matching the report. - User-visible CLI/MCP output (if applicable): the change is visible as `provider_operation_health.state: "starting"` in `binary_session` while startup is pending. The real macOS stdio MCP session from the report was not re-run. - Remaining proof gaps: no real macOS Hopper host was available. The bug and the fix are established at the adapter and session-status boundary with a controlled launcher, not through a real Hopper engine. The remaining items in #4226 (pre-handshake recovery, primary diagnostic retention during cleanup, cleanup-pending telemetry, close/reopen after closure proof) are not covered. Several Hopper boundary tests in this checkout require Unix sockets and do not run on Windows. 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/providers/hopper/hopperClient.startupFailures.test.ts -t "readiness wait as starting" --project boundary` — 1 passed. - Red-green check — reverting `providerOperationHealth.ts` and `HopperClient.ts` makes the new case fail with `expected { state: 'idle' } to match { state: 'starting' }`; restoring both makes it pass. - `npx vitest run src/domain/analysisErrorProjection.test.ts src/hopper/HopperProvider.test.ts src/hopper/HopperCleanup.test.ts` — 62 passed. - `npm run metadata:check` — passed; the generated MCP catalog accepts the new enum value. - `npx vitest run tests/boundary/mcp/advertisedPatternsVMode.test.ts --project mcp-boundary` — 1 passed. - `npx vitest run tests/composition/analysis-sessions/binarySession.test.ts --project composition` — 42 passed, 1 pre-existing Windows symlink failure (`EPERM`), identical with the change stashed. - `npx vitest run tests/boundary/mcp/sessionMcp.test.ts --project mcp-boundary` — 8 passed, 1 pre-existing timeout, identical with the change stashed. - `npx oxlint` and `npx oxfmt --check` on the three changed files — 0 errors, format clean. ## Compatibility, safety, and release - Breaking changes or migration steps: none. `starting` is an added value on an output enum; existing values and input contracts are unchanged. Clients that switch exhaustively on the previous set should handle the new value, which the change documents here. - Real Hopper/Ghidra, browser, or OS coverage: no real Hopper engine was run; the change is verified with a controlled launcher at the adapter boundary. A real macOS Hopper check remains a gap. - Package or release metadata impact: the generated MCP catalog reflects the new enum value; no package or installation change. - Security, privacy, process, or containment review: no target execution, injection, mutation, network, or filesystem change. The state is derived from existing in-process startup bookkeeping. ## Author readiness Human owner: @DeryFerd - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] 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-10-31 01:12:09 +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#6139
No description provided.