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 #6429] [CLOSED] fix(mcp): publish portable Windows absolute path patterns #7354

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6429
Author: @jokken79
Created: 10/23/2026
Status: ❌ Closed

Base: main ← Head: fix/windows-mcp-path-pattern

📝 Commits (1)

  • b84a41d fix(mcp): publish portable Windows absolute path patterns

📊 Changes

5 files changed (+107 additions, -83 deletions)

View changed files

📝 .github/workflows/ci.yml (+2 -0)
📝 scripts/ci/scopes.mjs (+3 -0)
📝 src/domain/localPath.ts (+3 -1)
📝 tests/boundary/mcp/advertisedPatternsVMode.test.ts (+97 -82)
📝 tests/process-global/curatedWindowsLane.test.ts (+2 -0)

📄 Description

Summary

Windows MCP catalogs advertised an absolute-path pattern that clients compiling JSON Schema patterns with the JavaScript v flag cannot parse. Spell the shared slash as \x2f so tool discovery succeeds while preserving accepted paths.

No linked issue: this is a focused compatibility fix reproduced locally.

Problem and expected behavior

The Windows pattern contains an unescaped / inside a character class. REA's u-mode validation accepts it, but v-mode compilation rejects it; one invalid pattern can prevent a client from accepting the complete tool catalog. Advertised patterns must compile in traditional, u, and v JavaScript modes.

Change and scope

Fix the representation at absoluteLocalPathStringSchema, reused by its contracts, instead of repairing individual tools. Exercise both compact and full input projections with full output schemas, and add path semantics and advertised-pattern tests to the Windows lane and its change-scope selection.

This is an ordinary compatibility correction within the existing contribution scope; a new provider/target-execution scope decision is not applicable.

Contract and boundary impact

  • Semantic owner: src/domain/localPath.ts; earliest change is the shared path schema's regex spelling.
  • CLI/MCP compatibility: identical accepted path values; the advertised Windows schema becomes compatible with v-mode consumers. Existing provider and Evidence semantics are unchanged.
  • Target selection, authority, upstream behavior, and cleanup: no new operations or effects; schema discovery uses a fixture that rejects deep-provider startup.
  • Generated metadata/package impact: regenerated catalogs reflect the schema spelling; no package version or installation changes. Ignored catalogs and build outputs are not committed.

Expected effects: this patch adds no target interaction. Validation starts the local MCP server and reads a synthetic fixture; it does not establish deep-provider behavior.

Evidence and regression coverage

  • Historical local evidence recorded on 2026-10-22, base 2589c0074, fix b84a41d3a, Windows x64 / Node 24.18.0 / npm 11.16.0: the original advertised-pattern test failed with 46 invalid Windows pattern occurrences; the corrected regression compiles every advertised pattern with "", u, and v flags.
  • Historical compiled stdio MCP smoke: compact/full input catalogs each exposed 220 tools, with 1,617/2,123 pattern occurrences respectively. Both analyzed one synthetic safetensors tensor (peso, four F32 parameters), and discovery stayed stable after the call.
  • Static review of the five-file diff found no blocking issue in the shared schema consumers, regression assertions, or Windows lane selection.
  • Current-session Windows verification (2026-10-23): the actual Codex and Claude Code launch registrations each started a fresh stdio server, listed 220 tools, passed v-mode pattern compilation, and answered binary_session.
  • Proof gaps: active desktop sessions were not restarted, remote CI and the full test suite have not run, and JS compilation does not prove every external schema consumer accepts the catalog.

Validation performed

Historical executions recorded on 2026-10-22 (not newly executed during PR-body preparation):

  • npm run test:focused -- tests/boundary/mcp/advertisedPatternsVMode.test.ts before the fix — failed on Windows pattern compilation.
  • npm run test:focused -- src/domain/localPath.test.ts src/domain/absoluteAnalysisInputPaths.test.ts src/contracts/sessionPathInputs.test.ts tests/boundary/mcp/advertisedPatternsVMode.test.ts tests/process-global/curatedWindowsLane.test.ts — 38 tests passed across five files.
  • npm run check:fast — typecheck, lint, and module boundaries passed; existing warnings remained.
  • The owns every explicit native-host test path case from ciChangeScope.test.ts — one test passed; other tests in that file were not run.
  • Compiled SDK client over stdio (scripts/rea.mjs mcp) — both catalog profiles and synthetic analysis passed as described above.
  • git diff --check and commit formatting/lint hooks — passed.

Executed on 2026-10-23, same patch revision:

  • npm run check with pinned Node 24.18.0/npm 11.16.0 — all six tasks passed, including typecheck, lint, formatting, knip, metadata and architecture guards. Existing lint warnings remain.
  • npm run docs:check — generated-document checks passed; all nine README consistency tests passed.
  • Fresh SDK clients launched from the actual Codex and Claude Code registrations — both passed discovery, v-mode schema compilation and session-status calls. This does not attest that already-running desktop sessions reconnected.
  • Existing verify-real-ghidra-windows.mjs lane with Ghidra 12.1.4/JDK 21 and the repository-owned x64 PE fixture — 27 provider operations passed, including decompilation; file-offset CLI/MCP parity and source-unchanged/cleanup checks passed. An initial sandbox attempt failed with Win32 access denied while creating the private snapshot; the authorized host execution passed. The verifier-wide process-lineage observation remains unavailable on Windows; provider-owned cleanup checks passed. This is supplemental existing-provider coverage, not a new capability.

Compatibility, safety, and release

  • Breaking changes/migration: none; regex spelling changes, path semantics remain the same.
  • Real platform/provider coverage: Windows x64 stdio MCP and the existing Ghidra verification lane on a synthetic PE fixture, as described above. Hopper, IDA, other PE architectures and active desktop-session reconnection remain unverified.
  • Release impact: no version bump or committed generated outputs.
  • Security/privacy/process impact: no new target execution, mutation, network, persistence, or cleanup capability.

Author readiness

Human owner: @jokken79

  • 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/6429 **Author:** [@jokken79](https://github.com/jokken79) **Created:** 10/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/windows-mcp-path-pattern` --- ### 📝 Commits (1) - [`b84a41d`](https://github.com/morluto/rea/commit/b84a41d3ac8d4c4e1c71beb37a9c575ec34657a1) fix(mcp): publish portable Windows absolute path patterns ### 📊 Changes **5 files changed** (+107 additions, -83 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/ci.yml` (+2 -0) 📝 `scripts/ci/scopes.mjs` (+3 -0) 📝 `src/domain/localPath.ts` (+3 -1) 📝 `tests/boundary/mcp/advertisedPatternsVMode.test.ts` (+97 -82) 📝 `tests/process-global/curatedWindowsLane.test.ts` (+2 -0) </details> ### 📄 Description ## Summary Windows MCP catalogs advertised an absolute-path pattern that clients compiling JSON Schema patterns with the JavaScript `v` flag cannot parse. Spell the shared slash as `\x2f` so tool discovery succeeds while preserving accepted paths. No linked issue: this is a focused compatibility fix reproduced locally. ## Problem and expected behavior The Windows pattern contains an unescaped `/` inside a character class. REA's `u`-mode validation accepts it, but `v`-mode compilation rejects it; one invalid pattern can prevent a client from accepting the complete tool catalog. Advertised patterns must compile in traditional, `u`, and `v` JavaScript modes. ## Change and scope Fix the representation at `absoluteLocalPathStringSchema`, reused by its contracts, instead of repairing individual tools. Exercise both compact and full input projections with full output schemas, and add path semantics and advertised-pattern tests to the Windows lane and its change-scope selection. This is an ordinary compatibility correction within the existing [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope); a new provider/target-execution scope decision is not applicable. ## Contract and boundary impact - Semantic owner: `src/domain/localPath.ts`; earliest change is the shared path schema's regex spelling. - CLI/MCP compatibility: identical accepted path values; the advertised Windows schema becomes compatible with `v`-mode consumers. Existing provider and Evidence semantics are unchanged. - Target selection, authority, upstream behavior, and cleanup: no new operations or effects; schema discovery uses a fixture that rejects deep-provider startup. - Generated metadata/package impact: regenerated catalogs reflect the schema spelling; no package version or installation changes. Ignored catalogs and build outputs are not committed. Expected effects: this patch adds no target interaction. Validation starts the local MCP server and reads a synthetic fixture; it does not establish deep-provider behavior. ## Evidence and regression coverage - Historical local evidence recorded on 2026-10-22, base `2589c0074`, fix `b84a41d3a`, Windows x64 / Node 24.18.0 / npm 11.16.0: the original advertised-pattern test failed with 46 invalid Windows pattern occurrences; the corrected regression compiles every advertised pattern with `""`, `u`, and `v` flags. - Historical compiled stdio MCP smoke: compact/full input catalogs each exposed 220 tools, with 1,617/2,123 pattern occurrences respectively. Both analyzed one synthetic safetensors tensor (`peso`, four F32 parameters), and discovery stayed stable after the call. - Static review of the five-file diff found no blocking issue in the shared schema consumers, regression assertions, or Windows lane selection. - Current-session Windows verification (2026-10-23): the actual Codex and Claude Code launch registrations each started a fresh stdio server, listed 220 tools, passed `v`-mode pattern compilation, and answered `binary_session`. - Proof gaps: active desktop sessions were not restarted, remote CI and the full test suite have not run, and JS compilation does not prove every external schema consumer accepts the catalog. ## Validation performed Historical executions recorded on 2026-10-22 (not newly executed during PR-body preparation): - `npm run test:focused -- tests/boundary/mcp/advertisedPatternsVMode.test.ts` before the fix — failed on Windows pattern compilation. - `npm run test:focused -- src/domain/localPath.test.ts src/domain/absoluteAnalysisInputPaths.test.ts src/contracts/sessionPathInputs.test.ts tests/boundary/mcp/advertisedPatternsVMode.test.ts tests/process-global/curatedWindowsLane.test.ts` — 38 tests passed across five files. - `npm run check:fast` — typecheck, lint, and module boundaries passed; existing warnings remained. - The `owns every explicit native-host test path` case from `ciChangeScope.test.ts` — one test passed; other tests in that file were not run. - Compiled SDK client over stdio (`scripts/rea.mjs mcp`) — both catalog profiles and synthetic analysis passed as described above. - `git diff --check` and commit formatting/lint hooks — passed. Executed on 2026-10-23, same patch revision: - `npm run check` with pinned Node 24.18.0/npm 11.16.0 — all six tasks passed, including typecheck, lint, formatting, knip, metadata and architecture guards. Existing lint warnings remain. - `npm run docs:check` — generated-document checks passed; all nine README consistency tests passed. - Fresh SDK clients launched from the actual Codex and Claude Code registrations — both passed discovery, `v`-mode schema compilation and session-status calls. This does not attest that already-running desktop sessions reconnected. - Existing `verify-real-ghidra-windows.mjs` lane with Ghidra 12.1.4/JDK 21 and the repository-owned x64 PE fixture — 27 provider operations passed, including decompilation; file-offset CLI/MCP parity and source-unchanged/cleanup checks passed. An initial sandbox attempt failed with Win32 access denied while creating the private snapshot; the authorized host execution passed. The verifier-wide process-lineage observation remains unavailable on Windows; provider-owned cleanup checks passed. This is supplemental existing-provider coverage, not a new capability. ## Compatibility, safety, and release - Breaking changes/migration: none; regex spelling changes, path semantics remain the same. - Real platform/provider coverage: Windows x64 stdio MCP and the existing Ghidra verification lane on a synthetic PE fixture, as described above. Hopper, IDA, other PE architectures and active desktop-session reconnection remain unverified. - Release impact: no version bump or committed generated outputs. - Security/privacy/process impact: no new target execution, mutation, network, persistence, or cleanup capability. ## Author readiness Human owner: @jokken79 - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:47:16 +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#7354
No description provided.