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 #5120] [MERGED] fix(setup): keep client and skill setup when the Hopper install fails #6774

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5120
Author: @bercedev
Created: 10/18/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: fix/optional-provider-install-continues

📝 Commits (6)

  • 8ac00a4 fix(setup): keep client and skill setup when the Hopper install fails
  • 47f395e fix(setup): keep the Hopper failure when a client write or the skill install fails too
  • e5e15de fix(setup): keep client and skill setup when the Hopper install fails
  • 79d9c54 fix(setup): keep the Hopper failure when a client write or the skill install fails too
  • 763ac6f fix(setup): reconcile optional Hopper recovery with current main
  • fedcc79 chore: integrate concurrent setup branch refresh

📊 Changes

3 files changed (+100 additions, -54 deletions)

View changed files

📝 docs/installation.md (+6 -4)
📝 src/application/Setup.configuration.test.ts (+57 -14)
📝 src/application/Setup.ts (+37 -36)

📄 Description

Summary

Fixes #5113.

When the optional Hopper package install fails, rea setup now still applies the other approved changes (client registrations and the skill) and reports needs_human with the Hopper failure. Before, runSetup returned at the Hopper step, so a package conflict that only concerns Hopper cost every other change in the plan.

Problem and expected behavior

On Arch Linux and CachyOS, zlib is provided by zlib-ng-compat, and pacman refuses Hopper's versioned zlib dependency. Setup then stopped at the Hopper step: no MCP registration and no skill were written. I hit this myself on CachyOS on 2026-10-14 with rea-agents 6.5.0; nothing from the plan was applied until I reran setup without Hopper. The issue also shows that removing zlib-ng-compat isn't realistic there.

Expected (the second option in the issue): skip Hopper, report it as unavailable, apply the rest.

Change and scope

installHopperAction returns the install failure instead of a finished SetupResult. runSetup records it and carries on with the clients and skill the user approved, without a Hopper launcher in the registrations (the same registrations a plan without Hopper writes). The final result keeps the install's code and remediation, so needs_human and the reason are unchanged for callers; the generic "rerun with --install-hopper" hint is left out in that case, since a rerun would hit the same conflict. The inputs installHopperAction only needed to build the early result are removed.

This changes a tested contract: reports a failed Hopper installation without configuring clients becomes reports a failed Hopper installation and still configures the selected clients. The docs/installation.md paragraph on the package-manager failure says what setup does now and names Arch as well as CachyOS.

Not included: detecting the conflict before running pacman (the first option in the issue), and the Ghidra/IDA install lanes, which the issue left uninvestigated.

Follow the contribution scope. Unresolved scope, authority, side effects, or required verification block integration. Ordinary fix within existing boundaries: not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: runSetup in src/application/Setup.ts, at the Hopper install step.
  • Contribution scope fit and linked maintainer decision: ordinary setup fix, not applicable.
  • CLI and MCP/tool-catalog contract: no tool or catalog change; rea setup writes the approved client and skill changes after a failed Hopper install instead of none.
  • Provider, bridge, target-format, or platform compatibility: Hopper install failure on any platform; most visible on Arch and CachyOS.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable; only changes that were already planned and approved are applied.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: docs/installation.md paragraph updated.

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: Setup.configuration.test.ts, the failed-install case now selects a client and the skill and checks both are applied, with no HOPPER_LAUNCHER_PATH and no installed_hopper, while status, code and remediation stay as before.
  • Base reproduction or other evidence: on main the updated test fails with expected +0 to be 1 (no client configured).
  • User-visible CLI/MCP output (if applicable): source-derived, not captured: the Hopper progress event is still failed, and the client and skill progress follows it instead of setup exiting.
  • Remaining proof gaps: not run end to end against a real pacman conflict; the fix was checked through FakeSetupHost.

Validation performed

In a Node 24.18.0 container with no network, after npm ci:

  • npx vitest run on Setup.configuration, Setup.planning, Setup.recovery, SetupInstallFailure and setupEnvironment tests: 71 passed, 2 failed. The 2 are in setupEnvironment.test.ts and fail the same way on main in the same container.
  • npx tsc --noEmit: no errors.
  • oxlint on the two changed source files: 0 errors, 3 warnings (max-lines, complexity, max-lines-per-function on Setup.ts), the same 3 as on main.
  • oxfmt --check on the changed files: clean.
  • npm run verify:module-boundaries: passed.
  • npm run docs:check: passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; the result shape is unchanged.
  • Real Hopper/Ghidra, browser, or OS coverage: the original failure was observed on CachyOS (rea-agents 6.5.0); the fix was not run against real Hopper.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new writes; it applies writes the user already approved in the plan.

Merge follow-up at 763ac6fd5: integrated main e83e3cead. The recovery composition retains the failed Hopper installation details while using main's single eligibility decision for generic install advice. The existing mixed Hopper/client and Hopper/skill failure regressions remain covered; they now live in their own test group to satisfy lint size limits without weakening assertions. On Node 24.18.0, nine focused setup/CLI/conflict/rollback files passed 162 tests; the final configuration-file rerun passed 24 tests. check:ci:fast passed all five tasks and docs:check passed. No real pacman/Hopper installation or native Windows run was performed; hosted checks are pending.

Author readiness

Human owner: @bercedev

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

Note: I used Claude Code while working on this.

🔄 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/5120 **Author:** [@bercedev](https://github.com/bercedev) **Created:** 10/18/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/optional-provider-install-continues` --- ### 📝 Commits (6) - [`8ac00a4`](https://github.com/morluto/rea/commit/8ac00a4aec32472c37fd278e9914f2c894679bc4) fix(setup): keep client and skill setup when the Hopper install fails - [`47f395e`](https://github.com/morluto/rea/commit/47f395ee4a894d39699305ca8d2b19dcad56c4e3) fix(setup): keep the Hopper failure when a client write or the skill install fails too - [`e5e15de`](https://github.com/morluto/rea/commit/e5e15de915df56b226545d3b66bdcae8cec28bb9) fix(setup): keep client and skill setup when the Hopper install fails - [`79d9c54`](https://github.com/morluto/rea/commit/79d9c54a88837ff44c80ce44e5ef3a7d56a0faaa) fix(setup): keep the Hopper failure when a client write or the skill install fails too - [`763ac6f`](https://github.com/morluto/rea/commit/763ac6fd5d539fa461413043da19451b4a2ba9f2) fix(setup): reconcile optional Hopper recovery with current main - [`fedcc79`](https://github.com/morluto/rea/commit/fedcc792382910a9406f4a51333881ee48747daa) chore: integrate concurrent setup branch refresh ### 📊 Changes **3 files changed** (+100 additions, -54 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+6 -4) 📝 `src/application/Setup.configuration.test.ts` (+57 -14) 📝 `src/application/Setup.ts` (+37 -36) </details> ### 📄 Description ## Summary Fixes #5113. When the optional Hopper package install fails, `rea setup` now still applies the other approved changes (client registrations and the skill) and reports `needs_human` with the Hopper failure. Before, `runSetup` returned at the Hopper step, so a package conflict that only concerns Hopper cost every other change in the plan. ## Problem and expected behavior On Arch Linux and CachyOS, `zlib` is provided by `zlib-ng-compat`, and pacman refuses Hopper's versioned `zlib` dependency. Setup then stopped at the Hopper step: no MCP registration and no skill were written. I hit this myself on CachyOS on 2026-10-14 with rea-agents 6.5.0; nothing from the plan was applied until I reran setup without Hopper. The issue also shows that removing `zlib-ng-compat` isn't realistic there. Expected (the second option in the issue): skip Hopper, report it as unavailable, apply the rest. ## Change and scope `installHopperAction` returns the install failure instead of a finished `SetupResult`. `runSetup` records it and carries on with the clients and skill the user approved, without a Hopper launcher in the registrations (the same registrations a plan without Hopper writes). The final result keeps the install's `code` and `remediation`, so `needs_human` and the reason are unchanged for callers; the generic "rerun with --install-hopper" hint is left out in that case, since a rerun would hit the same conflict. The inputs `installHopperAction` only needed to build the early result are removed. This changes a tested contract: `reports a failed Hopper installation without configuring clients` becomes `reports a failed Hopper installation and still configures the selected clients`. The `docs/installation.md` paragraph on the package-manager failure says what setup does now and names Arch as well as CachyOS. Not included: detecting the conflict before running pacman (the first option in the issue), and the Ghidra/IDA install lanes, which the issue left uninvestigated. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Ordinary fix within existing boundaries: not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `runSetup` in `src/application/Setup.ts`, at the Hopper install step. - Contribution scope fit and linked maintainer decision: ordinary setup fix, not applicable. - CLI and MCP/tool-catalog contract: no tool or catalog change; `rea setup` writes the approved client and skill changes after a failed Hopper install instead of none. - Provider, bridge, target-format, or platform compatibility: Hopper install failure on any platform; most visible on Arch and CachyOS. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable; only changes that were already planned and approved are applied. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: `docs/installation.md` paragraph updated. 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. - [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: `Setup.configuration.test.ts`, the failed-install case now selects a client and the skill and checks both are applied, with no `HOPPER_LAUNCHER_PATH` and no `installed_hopper`, while `status`, `code` and `remediation` stay as before. - Base reproduction or other evidence: on `main` the updated test fails with `expected +0 to be 1` (no client configured). - User-visible CLI/MCP output (if applicable): source-derived, not captured: the Hopper progress event is still `failed`, and the client and skill progress follows it instead of setup exiting. - Remaining proof gaps: not run end to end against a real pacman conflict; the fix was checked through `FakeSetupHost`. ## Validation performed In a Node 24.18.0 container with no network, after `npm ci`: - `npx vitest run` on `Setup.configuration`, `Setup.planning`, `Setup.recovery`, `SetupInstallFailure` and `setupEnvironment` tests: 71 passed, 2 failed. The 2 are in `setupEnvironment.test.ts` and fail the same way on `main` in the same container. - `npx tsc --noEmit`: no errors. - `oxlint` on the two changed source files: 0 errors, 3 warnings (`max-lines`, `complexity`, `max-lines-per-function` on `Setup.ts`), the same 3 as on `main`. - `oxfmt --check` on the changed files: clean. - `npm run verify:module-boundaries`: passed. - `npm run docs:check`: passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none; the result shape is unchanged. - Real Hopper/Ghidra, browser, or OS coverage: the original failure was observed on CachyOS (rea-agents 6.5.0); the fix was not run against real Hopper. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new writes; it applies writes the user already approved in the plan. Merge follow-up at `763ac6fd5`: integrated main `e83e3cead`. The recovery composition retains the failed Hopper installation details while using main's single eligibility decision for generic install advice. The existing mixed Hopper/client and Hopper/skill failure regressions remain covered; they now live in their own test group to satisfy lint size limits without weakening assertions. On Node 24.18.0, nine focused setup/CLI/conflict/rollback files passed 162 tests; the final configuration-file rerun passed 24 tests. `check:ci:fast` passed all five tasks and `docs:check` passed. No real pacman/Hopper installation or native Windows run was performed; hosted checks are pending. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @bercedev - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] 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. Note: I used Claude Code while working on this. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:42:56 +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#6774
No description provided.