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 #3458] [CLOSED] fix(adb): verify pushes to long device paths #5750

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3458
Author: @HawkForge
Created: 10/14/2026
Status: ❌ Closed

Base: main ← Head: fix/adb-push-digest-budget

📝 Commits (7)

  • d2dc61d fix(adb): verify pushes to long device paths
  • 10d44df Merge remote-tracking branch 'origin/main' into fix/adb-push-digest-budget
  • b79b8bc Merge remote-tracking branch 'origin/main' into fix/adb-push-digest-budget
  • 0bb369c Merge remote-tracking branch 'origin/main' into fix/adb-push-digest-budget
  • 2f69bb7 Keep adbDeviceAnalysis.ts as on main
  • 6f3c1ca Merge remote-tracking branch 'origin/main' into work/3458
  • de75d49 test(adb): keep only the long-path digest test

📊 Changes

2 files changed (+36 additions, -1 deletions)

View changed files

📝 src/adb/AdbProvider.test.ts (+30 -0)
📝 src/adb/AdbProvider.ts (+6 -1)

📄 Description

Summary

Fixes #3369. push-adb-file now verifies a push to a long device path. Previously, a correct sha256sum answer that exceeded the capture budget was reported as device_digest_source: "unavailable". When an answer genuinely cannot be read within its budget, the operation now returns the documented resource_constraint failure instead of an unverified success.

Problem and expected behavior

sha256sum echoes the device path after the digest, but the capture budget was a fixed 1 KiB. For a 1,142-character path, the correct checksum line exceeded it. runAdb returned AnalysisResourceConstraintError, and the push path treated every digest failure as "the device did not answer sha256sum". Callers got the same outcome as a device without sha256sum, and the reason was lost. The issue expects a correct digest to verify the transfer (docs/adb-device-analysis.md), and a capture-budget failure to remain a resource_constraint, distinguishable from an absent command.

Change and scope

In src/adb/AdbProvider.ts (pushFile):

  • The sha256sum capture budget is 1024 + 2 × byteLength(device_path). The factor of two leaves room for a sha256sum that escapes special characters in the echoed path.
  • A digest probe that fails with AnalysisResourceConstraintError is returned as that error instead of becoming "unavailable". Other failures (no sha256sum, protocol errors) keep the existing "unavailable" result and limitation.

Not included: changing what other digest failures (for example cancellation) report.

Ordinary fix within existing boundaries; scope decision not applicable. The push itself and its mutation authority are unchanged.

Contract and boundary impact

  • Semantic owner and earliest changed stage: ADB provider push verification.
  • Contribution scope fit and linked maintainer decision: not applicable (bug fix).
  • CLI and MCP/tool-catalog contract: unchanged schema; an oversized digest answer now yields the existing resource_constraint error code.
  • Provider, bridge, target-format, or platform compatibility: ADB provider only.
  • Evidence, artifact, provenance, or reconstruction contract: long-path pushes report device_sha256 and device_digest_source: "device_sha256sum".
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): same adb commands and arguments; only the capture budget changes.
  • Generated metadata, package, or installation impact: none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

(The checked effects belong to the existing push_adb_file operation, which launches adb and writes the caller's file to the device; this PR doesn't add any.)

Evidence and regression coverage

  • Tests added or updated (src/adb/AdbProvider.test.ts):
    • "verifies the device-side digest for a long device path" — a stub adb answers sha256sum for a 1,132-character path built from 220-character directories (each component within the usual 255-byte limit, per review); expects device_sha256 to equal the local digest with source device_sha256sum.
    • "reports an oversized sha256sum answer as a resource constraint" — a stub answers with 8 KiB; expects a resource_constraint refusal.
  • Base reproduction or other evidence: both tests fail with the source change reverted (the first returns unavailable/null, the second succeeds). A CLI run on base with a stub adb (REA_ADB_PATH) and a 1,142-character path returned device_digest_source: "unavailable", device_sha256: null.
  • User-visible CLI/MCP output (if applicable): after the change, the same CLI run returns device_digest_source: "device_sha256sum" with the correct digest for both a 25-character and a 1,142-character path.
  • Remaining proof gaps: no live Android device or emulator was used; the producer is a local stub, as in the issue's reproduction.

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.

Validation performed

  • New tests with the fix reverted — both fail
  • npx vitest run src/adb tests/boundary/mcp/adbMcp.test.ts — 134 passed
  • npm run check — passed
  • node scripts/rea.mjs push-adb-file probe-device <local> <device-path> --format json with a stub adb, before/after — unavailable → device_sha256sum for the 1,142-character path (macOS arm64, Node 24.13)

Compatibility, safety, and release

  • Breaking changes or migration steps: none. A capture that overflows even the larger budget now fails with resource_constraint after the push has completed; previously it returned success with an unverified digest.
  • Real Hopper/Ghidra, browser, or OS coverage: no real device.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the capture budget grows with the caller-supplied path (bounded by its length); no new commands.

Author readiness

Human owner: @HawkForge

  • 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/3458 **Author:** [@HawkForge](https://github.com/HawkForge) **Created:** 10/14/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/adb-push-digest-budget` --- ### 📝 Commits (7) - [`d2dc61d`](https://github.com/morluto/rea/commit/d2dc61ddce9d1f53dbecd8e31228a36441ce53bc) fix(adb): verify pushes to long device paths - [`10d44df`](https://github.com/morluto/rea/commit/10d44dfe2e716cadfb48aff38b446de001e77db1) Merge remote-tracking branch 'origin/main' into fix/adb-push-digest-budget - [`b79b8bc`](https://github.com/morluto/rea/commit/b79b8bca7044b581ab8af3f0438024000dc3aef8) Merge remote-tracking branch 'origin/main' into fix/adb-push-digest-budget - [`0bb369c`](https://github.com/morluto/rea/commit/0bb369c8dc8dc41f552458373e395c2cd501ebd9) Merge remote-tracking branch 'origin/main' into fix/adb-push-digest-budget - [`2f69bb7`](https://github.com/morluto/rea/commit/2f69bb798976a5cf6e7f826d1e061da5a37d5607) Keep adbDeviceAnalysis.ts as on main - [`6f3c1ca`](https://github.com/morluto/rea/commit/6f3c1ca191c84b49dc9f8d11da3246dc3483efd5) Merge remote-tracking branch 'origin/main' into work/3458 - [`de75d49`](https://github.com/morluto/rea/commit/de75d490db0caae81aca8a68f715f224df0f0ee5) test(adb): keep only the long-path digest test ### 📊 Changes **2 files changed** (+36 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/adb/AdbProvider.test.ts` (+30 -0) 📝 `src/adb/AdbProvider.ts` (+6 -1) </details> ### 📄 Description ## Summary Fixes #3369. `push-adb-file` now verifies a push to a long device path. Previously, a correct `sha256sum` answer that exceeded the capture budget was reported as `device_digest_source: "unavailable"`. When an answer genuinely cannot be read within its budget, the operation now returns the documented `resource_constraint` failure instead of an unverified success. ## Problem and expected behavior `sha256sum` echoes the device path after the digest, but the capture budget was a fixed 1 KiB. For a 1,142-character path, the correct checksum line exceeded it. `runAdb` returned `AnalysisResourceConstraintError`, and the push path treated every digest failure as "the device did not answer sha256sum". Callers got the same outcome as a device without `sha256sum`, and the reason was lost. The issue expects a correct digest to verify the transfer (docs/adb-device-analysis.md), and a capture-budget failure to remain a `resource_constraint`, distinguishable from an absent command. ## Change and scope In `src/adb/AdbProvider.ts` (`pushFile`): - The `sha256sum` capture budget is `1024 + 2 × byteLength(device_path)`. The factor of two leaves room for a `sha256sum` that escapes special characters in the echoed path. - A digest probe that fails with `AnalysisResourceConstraintError` is returned as that error instead of becoming `"unavailable"`. Other failures (no `sha256sum`, protocol errors) keep the existing `"unavailable"` result and limitation. Not included: changing what other digest failures (for example cancellation) report. Ordinary fix within existing boundaries; scope decision not applicable. The push itself and its mutation authority are unchanged. ## Contract and boundary impact - Semantic owner and earliest changed stage: ADB provider push verification. - Contribution scope fit and linked maintainer decision: not applicable (bug fix). - CLI and MCP/tool-catalog contract: unchanged schema; an oversized digest answer now yields the existing `resource_constraint` error code. - Provider, bridge, target-format, or platform compatibility: ADB provider only. - Evidence, artifact, provenance, or reconstruction contract: long-path pushes report `device_sha256` and `device_digest_source: "device_sha256sum"`. - Target selection, authority, upstream behavior, and cleanup details (if applicable): same adb commands and arguments; only the capture budget changes. - Generated metadata, package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. (The checked effects belong to the existing `push_adb_file` operation, which launches adb and writes the caller's file to the device; this PR doesn't add any.) ## Evidence and regression coverage - Tests added or updated (`src/adb/AdbProvider.test.ts`): - "verifies the device-side digest for a long device path" — a stub adb answers `sha256sum` for a 1,132-character path built from 220-character directories (each component within the usual 255-byte limit, per review); expects `device_sha256` to equal the local digest with source `device_sha256sum`. - "reports an oversized sha256sum answer as a resource constraint" — a stub answers with 8 KiB; expects a `resource_constraint` refusal. - Base reproduction or other evidence: both tests fail with the source change reverted (the first returns `unavailable`/`null`, the second succeeds). A CLI run on base with a stub adb (`REA_ADB_PATH`) and a 1,142-character path returned `device_digest_source: "unavailable"`, `device_sha256: null`. - User-visible CLI/MCP output (if applicable): after the change, the same CLI run returns `device_digest_source: "device_sha256sum"` with the correct digest for both a 25-character and a 1,142-character path. - Remaining proof gaps: no live Android device or emulator was used; the producer is a local stub, as in the issue's reproduction. 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. ## Validation performed - New tests with the fix reverted — both fail - `npx vitest run src/adb tests/boundary/mcp/adbMcp.test.ts` — 134 passed - `npm run check` — passed - `node scripts/rea.mjs push-adb-file probe-device <local> <device-path> --format json` with a stub adb, before/after — `unavailable` → `device_sha256sum` for the 1,142-character path (macOS arm64, Node 24.13) ## Compatibility, safety, and release - Breaking changes or migration steps: none. A capture that overflows even the larger budget now fails with `resource_constraint` after the push has completed; previously it returned success with an unverified digest. - Real Hopper/Ghidra, browser, or OS coverage: no real device. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the capture budget grows with the caller-supplied path (bounded by its length); no new commands. ## Author readiness Human owner: @HawkForge - [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-10-31 01:09:09 +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#5750
No description provided.