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 #1987] [MERGED] fix(targets): remove path advice for format refusals #4951

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1987
Author: @Ha1baraA11
Created: 10/11/2026
Status: ✅ Merged
Merged: 10/12/2026
Merged by: @N0zoM1z0

Base: main ← Head: pr/rea-1979

📝 Commits (4)

  • 420e956 fix(targets): remove path advice for format refusals
  • 2d2860f chore: sync main into target format guidance
  • a21d828 test(targets): group executable format refusals
  • 4fce039 chore: sync verified MIPS16 support into target diagnostics

📊 Changes

4 files changed (+91 additions, -9 deletions)

View changed files

📝 src/application/BinaryTargetResolver.ts (+19 -3)
📝 src/domain/analysisErrorPresentation.ts (+10 -2)
📝 src/domain/configurationErrors.ts (+2 -1)
📝 tests/boundary/filesystem/targetDiagnostics.test.ts (+60 -3)

📄 Description

Summary

A readable executable rejected by format parsing now reports its format reason without misleading path advice. CLI/MCP and rea doctor classify the refusal as an unsupported target; actual missing-path and permission diagnostics retain their own guidance.

Fixes #1979

Refs #1852

Problem and expected behavior

A readable MZ image with an NE, LE, or LX header is correctly refused, but the current message and remediation.action also advise checking whether the path exists and is readable. The path is valid, so that advice sends users toward the wrong cause. Format refusals should explain that the selected file is unsupported or malformed; path and access errors should retain their path-specific guidance.

Change and scope

  • Mark format-parser, raw-binary admission, and DOS COM admission failures with the typed file_format_rejected constraint after the file has been read.
  • Render the parser reason without generic path advice and give a format-specific remediation action.
  • Classify these results as unsupported_target in the shared CLI/MCP projection and rea doctor; preserve the existing directory, missing-path, permission and WASM static-inspection routes.
  • Add synthetic NE, LE, and LX fixture tests through target parsing, error projection, and Doctor diagnostics.

Contract and boundary impact

  • Semantic owner and earliest changed stage: BinaryTargetResolver identifies a readable file whose format is rejected; shared error presentation serves CLI and MCP, and Doctor reports the typed target classification.
  • CLI and MCP/tool-catalog contract: No tool or schema registration changes. code and details.reason remain stable; details.constraint gains the additive value file_format_rejected. Example: message: "Cannot open artifact: unsupported NE executable in MZ image."; remediation.action: "Review the reported file-format reason and select a supported, well-formed target.".
  • Provider, bridge, target-format, or platform compatibility: Applies to parser refusals and explicit raw-binary/DOS COM admission failures. Supported format admission and provider selection are unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: No artifact bytes, identity, evidence, or provenance are changed; the original reason and selected path remain available in details.
  • Process execution, authorization, cleanup, or containment impact: None; format rejection still occurs before provider startup.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: None; no generated output or package files change.

Evidence and regression coverage

  • Tests added or updated: tests/boundary/filesystem/targetDiagnostics.test.ts writes readable MZ images with NE, LE, and LX headers and checks the projected message, remediation, reason, constraint, and Doctor classification; existing directory and permission cases remain covered.
  • Base reproduction or other evidence: All three new format-refusal assertions failed on the exact unmodified PR base because the message and remediation included generic path advice and no typed format constraint; both existing directory and permission tests passed. On the patch, all five focused boundary tests pass.
  • User-visible CLI/MCP output (if applicable): message is Cannot open artifact: unsupported NE executable in MZ image.; remediation.action is Review the reported file-format reason and select a supported, well-formed target.; details.reason remains unsupported NE executable in MZ image.
  • Remaining proof gaps: Actual compiled CLI and fresh stdio MCP replay verified all three refusals, exact canonical projection parity, unchanged file bytes, service responsiveness and a missing-path control. A real native-provider session is unnecessary for these pre-startup refusals; Windows execution of the follow-up remains unverified.

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.

Follow-up verification

  • Integrated current main, preserving the merged WASM recovery route and source metadata inspection.
  • Added strict shared-error category and non-retryable assertions; the NE/LE/LX category checks failed before the follow-up and passed afterward.
  • Preserved malformed-header, missing-path and real filesystem permission checks; separated the format test group to keep the existing lint gate.
  • Focused parser/projection/Doctor/raw-binary/DOS COM/WASM checks: 103 tests across nine files passed on the final integrated head.
  • Real Linux x64 public CLI/MCP replay: three NE/LE/LX controls and a missing-path control passed with exact canonical error parity and unchanged source bytes.
  • npm run check:ci passed all eight static tasks and architecture guards on the integrated head.
  • npm run docs:check passed on the final integrated head.

Validation performed

  • npm run test:focused -- tests/boundary/filesystem/targetDiagnostics.test.ts — passed (5 tests).
  • npm run check:fast — passed (typecheck and lint).

Compatibility, safety, and release

  • Breaking changes or migration steps: None; target_unavailable and details.reason remain stable, with an additive constraint value and clearer text.
  • Real Hopper/Ghidra, browser, or OS coverage: No engine or browser was started; macOS arm64 boundary tests passed.
  • Package or release metadata impact: None.
  • Security, privacy, process, or containment review: No new authority, external process, or persistent file access; regression fixtures are created in a temporary test directory.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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/1987 **Author:** [@Ha1baraA11](https://github.com/Ha1baraA11) **Created:** 10/11/2026 **Status:** ✅ Merged **Merged:** 10/12/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `pr/rea-1979` --- ### 📝 Commits (4) - [`420e956`](https://github.com/morluto/rea/commit/420e9567f9d52ed1e55b8609ed62db06ecdf9e32) fix(targets): remove path advice for format refusals - [`2d2860f`](https://github.com/morluto/rea/commit/2d2860f6c4f781380be1e623541e236b83c51de9) chore: sync main into target format guidance - [`a21d828`](https://github.com/morluto/rea/commit/a21d828b06f5d94835110b40632ac56b99b36403) test(targets): group executable format refusals - [`4fce039`](https://github.com/morluto/rea/commit/4fce03901f4b940a0f190d052981adfa865fc7bb) chore: sync verified MIPS16 support into target diagnostics ### 📊 Changes **4 files changed** (+91 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `src/application/BinaryTargetResolver.ts` (+19 -3) 📝 `src/domain/analysisErrorPresentation.ts` (+10 -2) 📝 `src/domain/configurationErrors.ts` (+2 -1) 📝 `tests/boundary/filesystem/targetDiagnostics.test.ts` (+60 -3) </details> ### 📄 Description ## Summary A readable executable rejected by format parsing now reports its format reason without misleading path advice. CLI/MCP and `rea doctor` classify the refusal as an unsupported target; actual missing-path and permission diagnostics retain their own guidance. Fixes #1979 Refs #1852 ## Problem and expected behavior A readable MZ image with an NE, LE, or LX header is correctly refused, but the current `message` and `remediation.action` also advise checking whether the path exists and is readable. The path is valid, so that advice sends users toward the wrong cause. Format refusals should explain that the selected file is unsupported or malformed; path and access errors should retain their path-specific guidance. ## Change and scope - Mark format-parser, raw-binary admission, and DOS COM admission failures with the typed `file_format_rejected` constraint after the file has been read. - Render the parser reason without generic path advice and give a format-specific remediation action. - Classify these results as `unsupported_target` in the shared CLI/MCP projection and `rea doctor`; preserve the existing directory, missing-path, permission and WASM static-inspection routes. - Add synthetic NE, LE, and LX fixture tests through target parsing, error projection, and Doctor diagnostics. ## Contract and boundary impact - Semantic owner and earliest changed stage: `BinaryTargetResolver` identifies a readable file whose format is rejected; shared error presentation serves CLI and MCP, and Doctor reports the typed target classification. - CLI and MCP/tool-catalog contract: No tool or schema registration changes. `code` and `details.reason` remain stable; `details.constraint` gains the additive value `file_format_rejected`. Example: `message: "Cannot open artifact: unsupported NE executable in MZ image."`; `remediation.action: "Review the reported file-format reason and select a supported, well-formed target."`. - Provider, bridge, target-format, or platform compatibility: Applies to parser refusals and explicit raw-binary/DOS COM admission failures. Supported format admission and provider selection are unchanged. - Evidence, artifact, provenance, or reconstruction contract: No artifact bytes, identity, evidence, or provenance are changed; the original reason and selected path remain available in details. - Process execution, authorization, cleanup, or containment impact: None; format rejection still occurs before provider startup. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: None; no generated output or package files change. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/filesystem/targetDiagnostics.test.ts` writes readable MZ images with NE, LE, and LX headers and checks the projected message, remediation, reason, constraint, and Doctor classification; existing directory and permission cases remain covered. - Base reproduction or other evidence: All three new format-refusal assertions failed on the exact unmodified PR base because the message and remediation included generic path advice and no typed format constraint; both existing directory and permission tests passed. On the patch, all five focused boundary tests pass. - User-visible CLI/MCP output (if applicable): `message` is `Cannot open artifact: unsupported NE executable in MZ image.`; `remediation.action` is `Review the reported file-format reason and select a supported, well-formed target.`; `details.reason` remains `unsupported NE executable in MZ image`. - Remaining proof gaps: Actual compiled CLI and fresh stdio MCP replay verified all three refusals, exact canonical projection parity, unchanged file bytes, service responsiveness and a missing-path control. A real native-provider session is unnecessary for these pre-startup refusals; Windows execution of the follow-up remains unverified. 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. ## Follow-up verification - Integrated current main, preserving the merged WASM recovery route and source metadata inspection. - Added strict shared-error category and non-retryable assertions; the NE/LE/LX category checks failed before the follow-up and passed afterward. - Preserved malformed-header, missing-path and real filesystem permission checks; separated the format test group to keep the existing lint gate. - Focused parser/projection/Doctor/raw-binary/DOS COM/WASM checks: 103 tests across nine files passed on the final integrated head. - Real Linux x64 public CLI/MCP replay: three NE/LE/LX controls and a missing-path control passed with exact canonical error parity and unchanged source bytes. - `npm run check:ci` passed all eight static tasks and architecture guards on the integrated head. - `npm run docs:check` passed on the final integrated head. ## Validation performed - `npm run test:focused -- tests/boundary/filesystem/targetDiagnostics.test.ts` — passed (5 tests). - `npm run check:fast` — passed (typecheck and lint). ## Compatibility, safety, and release - Breaking changes or migration steps: None; `target_unavailable` and `details.reason` remain stable, with an additive constraint value and clearer text. - Real Hopper/Ghidra, browser, or OS coverage: No engine or browser was started; macOS arm64 boundary tests passed. - Package or release metadata impact: None. - Security, privacy, process, or containment review: No new authority, external process, or persistent file access; regression fixtures are created in a temporary test directory. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 00:57:19 +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#4951
No description provided.