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 #5246] [MERGED] fix(rizin): bound recent history frames by UTF-8 byte budget #6834

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5246
Author: @Sarthak-Pandey
Created: 10/19/2026
Status: ✅ Merged
Merged: 10/19/2026
Merged by: @gensokyo-dev

Base: main ← Head: fix/rizin-cjk-recent-output-budget

📝 Commits (3)

  • 4f2234a fix(rizin): bound recent history frames by UTF-8 byte budget
  • d3ce950 chore(rizin): sync latest main for history validation
  • a2f346a fix(rizin): share bounded UTF-8 prefixes across captures

📊 Changes

3 files changed (+125 additions, -32 deletions)

View changed files

📝 docs/reverse-engineering-tools.md (+2 -0)
📝 src/rizin/RizinDebugSessionManager.ts (+17 -22)
📝 tests/boundary/providers/RizinDebugSessionCoverage.part4.test.ts (+106 -10)

📄 Description

Summary

Fixes #5091 and #5242. Rizin recent history used UTF-16 positions for a 16 KiB UTF-8 budget. Real Rizin 0.9.1 reproduced 49,176 B retained for a 60,000 B CJK frame, a split emoji surrogate, and 18,000 B of decoded replacement characters from a 6,000 B invalid frame.

History now retains a complete UTF-8 prefix of at most 16 KiB plus the existing 24 B marker. Full decoded command output, per-command invalid-UTF-8 Evidence, session uncertainty, wire-byte queue accounting and ownership/cleanup policy are preserved.

Problem and expected behavior

Keep bounded recent history without shortening complete command Evidence. Exact CJK/emoji/invalid-byte prefixes are verified independently of the truncation implementation. Status history is still capped at 64 protocol frames; this change adds no query surface or cache.

Change and scope

Reuse the manager's truncateUtf8 for history, startup diagnostics and capped command output. Encode directly into a budget-sized buffer using Node's complete-character Buffer.write, avoiding duplicate boundary walkers and whole-frame temporary UTF-8 buffers for a small history prefix. Protocol assembly and full command Evidence still consume memory separately.

Replace the fixed-delay history tests with nine deterministic injected-stream cases, checking exact prefixes, truncation/decoding flags, complete command Evidence and unsolicited frames. Preserve oversized-frame, ring-capacity, cancellation and lifecycle coverage. Document the existing history budget.

Ordinary fix within the existing provider boundary; no new execution authority, dependency, installer or generated contract change.

Contract and boundary impact

  • Owner: RizinDebugSessionManager decoded-text prefix retention.
  • CLI/MCP schemas and tool catalog: unchanged.
  • Real verification: Linux x86-64, official Rizin 0.9.1 static build; other platforms unverified. Persistent Rizin debugging remains Linux-only.
  • Source-controlled sleep/exit executable used for lifecycle control; controlled CJK/emoji/invalid-byte files were read through native Rizin !cat. This is real-provider conformance, not a claim about complex-software investigation quality.

Expected effects:

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

The patch changes capture retention only; real-provider verification exercised existing launch/console/close operations.

Evidence and regression coverage

Executed on a2f346a36, integrating latest main b44cb5bd3:

  • npm run test:focused -- the 13 Rizin provider/MCP files: 151 passed, 1 skipped.
  • npm run check: all six tasks and architecture guards passed.
  • Rechecked the two upstream JavaScript CI regression files after main's fix: 42 passed; no unrelated test changes in this PR.
  • npm run docs:check: six tasks and five README tests passed.
  • Actual stdio MCP: four command/status cases, verified full decoded raw/normalized command output, loss flags, launch provenance, close and complete retained Evidence; actual CLI CJK output matched. Target digest unchanged, owned process-family cleanup verified, OOM kills 0.

Real CJK history: 49,176 → 16,407 B; emoji history now well-formed; invalid UTF-8 expansion is also bounded. A short-lived /usr/bin/true close attempt on unchanged main failed and recovered on explicit retry; recorded separately in #4227, excluded from the completed comparison.

Validation performed

Follow-up implementation/review and measurements by @gensokyo-dev; original author readiness declaration below is retained.

One matched before/after verification pair (fresh SDK/server, warm OS file cache, CPU1): elapsed 19.257 → 19.906 s, CPU 15.703 → 16.542 s, process-family peak 820.4 → 800.3 MiB. These observations do not establish a general speedup or memory improvement. All jobs used an 8 GiB maximum (public proofs 2 GiB); largest validation peak 4.51 GiB. Counters were observed at payload exit while the observer remained alive, not final whole-scope counters.

tiktoken 0.12.0 / cl100k_base estimates: first CJK status raw SDK reply 65,767 → 22,091; whole recorded MCP sequence including discovery, requests/replies, all four statuses and complete Evidence 1,447,088 → 1,272,043. The unchanged discovery alone is 807,510. Text/structured duplication is counted; protocol/init framing, actual client rendering and actual model usage are unmeasured. CLI conformance is separate from this token estimate.

Compatibility, safety, and release

No breaking API or package metadata changes. Buffer decoding uses only initialized bytes; raw wire queue charges and full command-result semantics remain unchanged. No new cache or retained inventory.

Author readiness

Human owner: @Sarthak-Pandey

  • 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/5246 **Author:** [@Sarthak-Pandey](https://github.com/Sarthak-Pandey) **Created:** 10/19/2026 **Status:** ✅ Merged **Merged:** 10/19/2026 **Merged by:** [@gensokyo-dev](https://github.com/gensokyo-dev) **Base:** `main` ← **Head:** `fix/rizin-cjk-recent-output-budget` --- ### 📝 Commits (3) - [`4f2234a`](https://github.com/morluto/rea/commit/4f2234ab4138ecd54ccdabc8c7c61296a9848198) fix(rizin): bound recent history frames by UTF-8 byte budget - [`d3ce950`](https://github.com/morluto/rea/commit/d3ce9502ce7585fffe65da48554fab33f9834d1c) chore(rizin): sync latest main for history validation - [`a2f346a`](https://github.com/morluto/rea/commit/a2f346a3622bc70c7d5e27f24419f4b8ab0b2377) fix(rizin): share bounded UTF-8 prefixes across captures ### 📊 Changes **3 files changed** (+125 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `docs/reverse-engineering-tools.md` (+2 -0) 📝 `src/rizin/RizinDebugSessionManager.ts` (+17 -22) 📝 `tests/boundary/providers/RizinDebugSessionCoverage.part4.test.ts` (+106 -10) </details> ### 📄 Description ## Summary Fixes #5091 and #5242. Rizin recent history used UTF-16 positions for a 16 KiB UTF-8 budget. Real Rizin 0.9.1 reproduced 49,176 B retained for a 60,000 B CJK frame, a split emoji surrogate, and 18,000 B of decoded replacement characters from a 6,000 B invalid frame. History now retains a complete UTF-8 prefix of at most 16 KiB plus the existing 24 B marker. Full decoded command output, per-command invalid-UTF-8 Evidence, session uncertainty, wire-byte queue accounting and ownership/cleanup policy are preserved. ## Problem and expected behavior Keep bounded recent history without shortening complete command Evidence. Exact CJK/emoji/invalid-byte prefixes are verified independently of the truncation implementation. Status history is still capped at 64 protocol frames; this change adds no query surface or cache. ## Change and scope Reuse the manager's `truncateUtf8` for history, startup diagnostics and capped command output. Encode directly into a budget-sized buffer using Node's complete-character `Buffer.write`, avoiding duplicate boundary walkers and whole-frame temporary UTF-8 buffers for a small history prefix. Protocol assembly and full command Evidence still consume memory separately. Replace the fixed-delay history tests with nine deterministic injected-stream cases, checking exact prefixes, truncation/decoding flags, complete command Evidence and unsolicited frames. Preserve oversized-frame, ring-capacity, cancellation and lifecycle coverage. Document the existing history budget. Ordinary fix within the existing provider boundary; no new execution authority, dependency, installer or generated contract change. ## Contract and boundary impact - Owner: `RizinDebugSessionManager` decoded-text prefix retention. - CLI/MCP schemas and tool catalog: unchanged. - Real verification: Linux x86-64, official Rizin 0.9.1 static build; other platforms unverified. Persistent Rizin debugging remains Linux-only. - Source-controlled sleep/exit executable used for lifecycle control; controlled CJK/emoji/invalid-byte files were read through native Rizin `!cat`. This is real-provider conformance, not a claim about complex-software investigation quality. Expected effects: - [x] 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. The patch changes capture retention only; real-provider verification exercised existing launch/console/close operations. ## Evidence and regression coverage Executed on `a2f346a36`, integrating latest main `b44cb5bd3`: - `npm run test:focused --` the 13 Rizin provider/MCP files: **151 passed, 1 skipped**. - `npm run check`: all six tasks and architecture guards passed. - Rechecked the two upstream JavaScript CI regression files after main's fix: **42 passed**; no unrelated test changes in this PR. - `npm run docs:check`: six tasks and five README tests passed. - Actual stdio MCP: four command/status cases, verified full decoded raw/normalized command output, loss flags, launch provenance, close and complete retained Evidence; actual CLI CJK output matched. Target digest unchanged, owned process-family cleanup verified, OOM kills 0. Real CJK history: **49,176 → 16,407 B**; emoji history now well-formed; invalid UTF-8 expansion is also bounded. A short-lived `/usr/bin/true` close attempt on unchanged main failed and recovered on explicit retry; recorded separately in [#4227](https://github.com/morluto/rea/issues/4227#issuecomment-6273199435), excluded from the completed comparison. ## Validation performed Follow-up implementation/review and measurements by @gensokyo-dev; original author readiness declaration below is retained. One matched before/after verification pair (fresh SDK/server, warm OS file cache, CPU1): elapsed **19.257 → 19.906 s**, CPU **15.703 → 16.542 s**, process-family peak **820.4 → 800.3 MiB**. These observations do **not** establish a general speedup or memory improvement. All jobs used an 8 GiB maximum (public proofs 2 GiB); largest validation peak 4.51 GiB. Counters were observed at payload exit while the observer remained alive, not final whole-scope counters. `tiktoken 0.12.0 / cl100k_base` estimates: first CJK status raw SDK reply **65,767 → 22,091**; whole recorded MCP sequence including discovery, requests/replies, all four statuses and complete Evidence **1,447,088 → 1,272,043**. The unchanged discovery alone is 807,510. Text/structured duplication is counted; protocol/init framing, actual client rendering and actual model usage are unmeasured. CLI conformance is separate from this token estimate. ## Compatibility, safety, and release No breaking API or package metadata changes. Buffer decoding uses only initialized bytes; raw wire queue charges and full command-result semantics remain unchanged. No new cache or retained inventory. ## Author readiness Human owner: @Sarthak-Pandey - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:43:22 +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#6834
No description provided.