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 #4855] [MERGED] fix(setup): preserve concurrent client configuration edits #6443

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4855
Author: @abdulwasea89
Created: 10/17/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: fix/setup-configuration-conflicts

📝 Commits (10+)

  • 564a930 fix(setup): preserve concurrent client configuration edits
  • 67ca0df fix(setup): normalize configuration transaction queue paths
  • 11fe0f4 fix(setup): report concurrent snapshot read conflicts
  • 2966037 test(setup): isolate Pi workflows from installed Hopper
  • 9fcaf8f fix(setup): reconcile conflict handling with current main
  • 39bcc4d chore: merge main into setup configuration conflict handling
  • 9cb6dd2 test: align inherited fixtures with current analysis contracts
  • eb732e6 test(ida): assert search recovery instead of diagnostic prose
  • 9960026 chore: merge main into setup configuration conflict handling
  • b87c796 fix(setup): share configuration queue keys across directory aliases

📊 Changes

11 files changed (+752 additions, -56 deletions)

View changed files

📝 docs/installation.md (+9 -0)
📝 src/application/ClientConfigPath.ts (+45 -5)
📝 src/application/ClientConfigurationPublication.ts (+86 -7)
➕ src/application/ClientConfigurationTransaction.ts (+27 -0)
📝 src/application/SetupClientConfiguration.ts (+85 -40)
📝 src/application/SetupClients.ts (+2 -0)
📝 src/application/SetupTypes.ts (+5 -0)
📝 tests/acceptance/setup/piClientSetup.test.ts (+3 -0)
📝 tests/boundary/filesystem/setupConfig.test.ts (+32 -0)
➕ tests/process-global/setupConfigurationConflicts.test.ts (+454 -0)
📝 tests/process-global/setupConfigurationRollback.test.ts (+4 -4)

📄 Description

Summary

When rea setup races with another edit to a client configuration, it reports a typed conflict and asks the user to review the current file and retry. Directory-symlink and real-directory spellings of the same file now share one in-process queue key.

Problem and approach

The original setup flow could take a snapshot, then publish from stale input or misclassify a replacement during readback and recovery. Current main already owns publication and cleanup through ClientConfigurationPublication. This PR uses that owner, carries the initial file identity and content into publication, verifies the selected destination before writing, and classifies confirmed changes as conflict. A path-keyed queue serializes setup operations within this process. The publication owner retains its descriptor, staging file, and failed cleanup for retry. Genuine I/O failures keep their distinct outcomes; first-run cleanup still follows the existing manual-recovery safety rule. Installation docs describe the guarantee and its external-writer limit.

resolveClientConfigTransactionPath now resolves parent-directory aliases for regular and missing files, including absent intermediate directories, before the queue chooses its key. A configuration file symlink still resolves only when the link and its target are owned by the current user. If a parent-directory alias is retargeted after that selection, publication keeps the already chosen canonical file. A configuration symlink that then names a different target still conflicts.

The user-visible message is: Agent configuration changed during setup. Review the current file and rerun setup. No provider, target execution, or network authority changes. The Pi acceptance fixtures select an unavailable Hopper launcher to prevent unrelated local-provider probes from creating cache files in their temporary homes.

Evidence and validation

Merged main at 7091be291 (#6375), which supplies the current browser storage fingerprint fixtures. Legacy hashed storage without fingerprint_version stays unknown. On Node 24.18.0 and npm 11.16.0:

  • npm run test:focused -- tests/process-global/setupConfigurationConflicts.test.ts tests/process-global/setupConfigurationRollback.test.ts tests/boundary/filesystem/setupConfig.test.ts tests/boundary/filesystem/clientConfigurationTransactions.test.ts tests/boundary/cli/browserCli.test.ts — 109 tests passed, including directory-alias queue serialization and compares reordered scenario storage through the public CLI.
  • npm run test:focused -- tests/boundary/filesystem/clientLifecycle.test.ts tests/boundary/filesystem/clientConfigurationBom.test.ts tests/boundary/filesystem/clientConfigurationDialects.test.ts tests/acceptance/setup/repeatedClientSetup.test.ts — 117 tests passed.
  • npm run check:fast — passed.

Directory-symlink coverage is skipped on Windows. There is no OS-level compare-and-swap or cross-process lock, so an external writer can still race after a filesystem check. Real-provider workflows were not run.

Scope and release

This is an ordinary setup correctness fix within existing configuration authority. The CLI setup result adds an explicit conflict outcome; the MCP catalog, dependencies, generated metadata, and provider contracts are unchanged. No migration is required. Only approved setup configuration writes are involved; no production client settings were edited during validation.

CI follow-up at 84ae10aa4: merged main bea6b98e8, which supplies the current structured integrity-error assertion for malformed mobile inventory Evidence, and formatted the new queue-alias regression. The five-file focused mobile/setup batch passed 102 tests; npm run check:ci:fast passed all five tasks, including formatting and built lint. Hosted validation of the updated head is pending.

Author readiness

Human owner: @abdulwasea89

  • 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.
Open in Web Open in Cursor 

🔄 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/4855 **Author:** [@abdulwasea89](https://github.com/abdulwasea89) **Created:** 10/17/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/setup-configuration-conflicts` --- ### 📝 Commits (10+) - [`564a930`](https://github.com/morluto/rea/commit/564a93081dc2875dbcfbfa9b2a8e1dd5af588eab) fix(setup): preserve concurrent client configuration edits - [`67ca0df`](https://github.com/morluto/rea/commit/67ca0dfde1cb27470c7c17943383a54d03ce0484) fix(setup): normalize configuration transaction queue paths - [`11fe0f4`](https://github.com/morluto/rea/commit/11fe0f40c441b8a1cf5b0de78ba3e06b77d589f2) fix(setup): report concurrent snapshot read conflicts - [`2966037`](https://github.com/morluto/rea/commit/2966037461980ef8e026302c0d5dfb92b852b418) test(setup): isolate Pi workflows from installed Hopper - [`9fcaf8f`](https://github.com/morluto/rea/commit/9fcaf8f17b3f510e40ba865adfb56e4853ab22d7) fix(setup): reconcile conflict handling with current main - [`39bcc4d`](https://github.com/morluto/rea/commit/39bcc4dbf3fa7497a504de002b7a2d82ead75415) chore: merge main into setup configuration conflict handling - [`9cb6dd2`](https://github.com/morluto/rea/commit/9cb6dd2e5c860601c18dcc0b87f985d2ec124a38) test: align inherited fixtures with current analysis contracts - [`eb732e6`](https://github.com/morluto/rea/commit/eb732e63c336540033cb881e92dcd8349502484e) test(ida): assert search recovery instead of diagnostic prose - [`9960026`](https://github.com/morluto/rea/commit/99600264a032f45c4341722ab40b552612983c4d) chore: merge main into setup configuration conflict handling - [`b87c796`](https://github.com/morluto/rea/commit/b87c796f73fec648c5c39a253d3ac875d3584a92) fix(setup): share configuration queue keys across directory aliases ### 📊 Changes **11 files changed** (+752 additions, -56 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+9 -0) 📝 `src/application/ClientConfigPath.ts` (+45 -5) 📝 `src/application/ClientConfigurationPublication.ts` (+86 -7) ➕ `src/application/ClientConfigurationTransaction.ts` (+27 -0) 📝 `src/application/SetupClientConfiguration.ts` (+85 -40) 📝 `src/application/SetupClients.ts` (+2 -0) 📝 `src/application/SetupTypes.ts` (+5 -0) 📝 `tests/acceptance/setup/piClientSetup.test.ts` (+3 -0) 📝 `tests/boundary/filesystem/setupConfig.test.ts` (+32 -0) ➕ `tests/process-global/setupConfigurationConflicts.test.ts` (+454 -0) 📝 `tests/process-global/setupConfigurationRollback.test.ts` (+4 -4) </details> ### 📄 Description ## Summary When `rea setup` races with another edit to a client configuration, it reports a typed conflict and asks the user to review the current file and retry. Directory-symlink and real-directory spellings of the same file now share one in-process queue key. ## Problem and approach The original setup flow could take a snapshot, then publish from stale input or misclassify a replacement during readback and recovery. Current `main` already owns publication and cleanup through `ClientConfigurationPublication`. This PR uses that owner, carries the initial file identity and content into publication, verifies the selected destination before writing, and classifies confirmed changes as `conflict`. A path-keyed queue serializes setup operations within this process. The publication owner retains its descriptor, staging file, and failed cleanup for retry. Genuine I/O failures keep their distinct outcomes; first-run cleanup still follows the existing manual-recovery safety rule. Installation docs describe the guarantee and its external-writer limit. `resolveClientConfigTransactionPath` now resolves parent-directory aliases for regular and missing files, including absent intermediate directories, before the queue chooses its key. A configuration file symlink still resolves only when the link and its target are owned by the current user. If a parent-directory alias is retargeted after that selection, publication keeps the already chosen canonical file. A configuration symlink that then names a different target still conflicts. The user-visible message is: `Agent configuration changed during setup. Review the current file and rerun setup.` No provider, target execution, or network authority changes. The Pi acceptance fixtures select an unavailable Hopper launcher to prevent unrelated local-provider probes from creating cache files in their temporary homes. ## Evidence and validation Merged `main` at `7091be291` (`#6375`), which supplies the current browser storage fingerprint fixtures. Legacy hashed storage without `fingerprint_version` stays `unknown`. On Node 24.18.0 and npm 11.16.0: - `npm run test:focused -- tests/process-global/setupConfigurationConflicts.test.ts tests/process-global/setupConfigurationRollback.test.ts tests/boundary/filesystem/setupConfig.test.ts tests/boundary/filesystem/clientConfigurationTransactions.test.ts tests/boundary/cli/browserCli.test.ts` — 109 tests passed, including directory-alias queue serialization and `compares reordered scenario storage through the public CLI`. - `npm run test:focused -- tests/boundary/filesystem/clientLifecycle.test.ts tests/boundary/filesystem/clientConfigurationBom.test.ts tests/boundary/filesystem/clientConfigurationDialects.test.ts tests/acceptance/setup/repeatedClientSetup.test.ts` — 117 tests passed. - `npm run check:fast` — passed. Directory-symlink coverage is skipped on Windows. There is no OS-level compare-and-swap or cross-process lock, so an external writer can still race after a filesystem check. Real-provider workflows were not run. ## Scope and release This is an ordinary setup correctness fix within existing configuration authority. The CLI setup result adds an explicit `conflict` outcome; the MCP catalog, dependencies, generated metadata, and provider contracts are unchanged. No migration is required. Only approved setup configuration writes are involved; no production client settings were edited during validation. CI follow-up at `84ae10aa4`: merged main `bea6b98e8`, which supplies the current structured integrity-error assertion for malformed mobile inventory Evidence, and formatted the new queue-alias regression. The five-file focused mobile/setup batch passed 102 tests; `npm run check:ci:fast` passed all five tasks, including formatting and built lint. Hosted validation of the updated head is pending. ## Author readiness Human owner: @abdulwasea89 - [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 - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. <div><a href="https://cursor.com/agents/bc-8d7d89dd-f444-50ff-bca8-58370fac76b8?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-8d7d89dd-f444-50ff-bca8-58370fac76b8&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:14:30 +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#6443
No description provided.