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 #7470] fix(adb)!: reject malformed package numeric tokens #7859

New issue
Open
opened 2026-11-05 01:48:11 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-05 01:48:11 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7470
Author: @kittimzhe
Created: 10/27/2026
Status: 🔄 Open

Base: main ← Head: fix/adb-attached-letter-ids

📝 Commits (2)

  • c3b54d1 fix(adb): reject package ids with attached text instead of admitting the prefix
  • 552afbc fix(adb)!: preserve malformed version declarations

📊 Changes

5 files changed (+169 additions, -12 deletions)

View changed files

📝 docs/adb-device-analysis.md (+3 -1)
📝 src/adb/AdbShellOutput.test.ts (+37 -0)
📝 src/adb/AdbShellOutput.ts (+14 -4)
📝 src/domain/adb/adbDeviceAnalysis.ts (+15 -7)
📝 tests/acceptance/applications/adbNumericDeclarations.test.ts (+100 -0)

📄 Description

Summary

inspect_adb_package admitted the leading digit run of a userId/appId declaration, so userId=10123abc became user_id: 10123 with no numeric issue and complete coverage, and a malformed declaration before a valid one could decide which id the caller received. The decimal id must now end its token; attached text makes the declaration an invalid_format numeric issue with its original line, and package coverage becomes partial. Fixes #7409.

Problem and expected behavior

Smallest trigger: a dumpsys package section whose only id declaration is userId=10123abc.

Violated invariant: docs/adb-device-analysis.md ("Interpret the result") — malformed declarations before or after a valid value remain in numeric_issues, any issue makes package coverage partial, and user_id is the first valid declaration. parseDumpsysPackageOutput matched ^(\d+) and passed only the digits to the safe-integer check, so the attached text was lost before the validity decision.

Expected: userId=10123abc alone → user_id: null, one invalid_format issue with the original line, coverage partial. With a valid userId=10456 also present → user_id: 10456, the malformed lines retained as issues, coverage partial.

Change and scope

  • src/adb/AdbShellOutput.ts: the id pattern requires the digits to end their token (^(\d+)(?:\s|$)). Whitespace-separated suffixes such as userId=10001 installing=true stay admitted exactly as before; non-numeric, negative and unsafe declarations keep their current reasons.
  • tests/acceptance/applications/adbNumericDeclarations.test.ts: two scenarios in the existing CLI + MCP table — attached text as the only declaration, and attached text on both sides of a valid declaration across both spellings.
  • Not included: no change to first-valid selection for well-formed declarations or to other dumpsys fields.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

  • Semantic owner and earliest changed stage: parseDumpsysPackageOutput, the single parser of Package Manager id declarations; AdbProvider projects its parsed facts unchanged. No superseded path.
  • Contribution scope fit and linked maintainer decision: ordinary fix within the existing parser boundary — not applicable.
  • CLI and MCP/tool-catalog contract: such declarations now appear in numeric_issues (invalid_format) and make coverage partial instead of yielding a prefix id. No schema or tool-catalog change.
  • Provider, bridge, target-format, or platform compatibility: none; the accepted grammar for well-formed declarations is unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: the original raw_line is retained in the issue.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), 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.

Evidence and regression coverage

  • Tests added or updated: two scenarios in tests/acceptance/applications/adbNumericDeclarations.test.ts, run through both CLI and MCP.
  • Base reproduction or other evidence: executed. With the parser change stashed, the new scenario fails on user_id (expected null, received 10123).
  • User-visible CLI/MCP output (if applicable): userId=10123abc alone → user_id: null, numeric_issues.total: 1 (invalid_format, original line), coverage: partial.
  • Remaining proof gaps: synthetic dumpsys text through the existing adb stand-in fixture only; no real Android device or emulator, and no real-device occurrence of the attached-letter shape is claimed.

Boundary regressions covered: malformed-input parsing and first-valid selection with issues on both sides. Lifecycle regressions: not applicable (no new resources).

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

  • npm run test:focused -- tests/acceptance/applications/adbNumericDeclarations.test.ts src/adb/AdbShellOutput.test.ts src/adb/AdbProvider.test.ts — 151 passed.
  • npm run check:fast — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Output that previously admitted a digit prefix now reports user_id: null or the next valid id, with partial coverage.
  • Real Hopper/Ghidra, browser, or OS coverage: none; no real Android device.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Version-code follow-up

The same parser now rejects attached text in versionCode (#7534), preserving the first valid signed decimal token exactly and recording malformed lines as version_code numeric issues. This adds a field variant to the output schema and changes malformed-output coverage, so exhaustive consumers need to handle it.

Validation on the updated branch: 48 parser and built CLI/MCP tests passed, including malformed declarations before and after a valid large signed value; check:fast and git diff --check passed. The adb responses are fixtures; no real device was tested.

Author readiness

Human owner: @kittimzhe

  • 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/7470 **Author:** [@kittimzhe](https://github.com/kittimzhe) **Created:** 10/27/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/adb-attached-letter-ids` --- ### 📝 Commits (2) - [`c3b54d1`](https://github.com/morluto/rea/commit/c3b54d1b12101208d9deddafa2bc7ee8056f873c) fix(adb): reject package ids with attached text instead of admitting the prefix - [`552afbc`](https://github.com/morluto/rea/commit/552afbc42604ee082bbc56727f19af9e68f2bb72) fix(adb)!: preserve malformed version declarations ### 📊 Changes **5 files changed** (+169 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `docs/adb-device-analysis.md` (+3 -1) 📝 `src/adb/AdbShellOutput.test.ts` (+37 -0) 📝 `src/adb/AdbShellOutput.ts` (+14 -4) 📝 `src/domain/adb/adbDeviceAnalysis.ts` (+15 -7) 📝 `tests/acceptance/applications/adbNumericDeclarations.test.ts` (+100 -0) </details> ### 📄 Description ## Summary `inspect_adb_package` admitted the leading digit run of a `userId`/`appId` declaration, so `userId=10123abc` became `user_id: 10123` with no numeric issue and complete coverage, and a malformed declaration before a valid one could decide which id the caller received. The decimal id must now end its token; attached text makes the declaration an `invalid_format` numeric issue with its original line, and package coverage becomes partial. Fixes #7409. ## Problem and expected behavior Smallest trigger: a `dumpsys package` section whose only id declaration is `userId=10123abc`. Violated invariant: `docs/adb-device-analysis.md` ("Interpret the result") — malformed declarations before or after a valid value remain in `numeric_issues`, any issue makes package coverage partial, and `user_id` is the first *valid* declaration. `parseDumpsysPackageOutput` matched `^(\d+)` and passed only the digits to the safe-integer check, so the attached text was lost before the validity decision. Expected: `userId=10123abc` alone → `user_id: null`, one `invalid_format` issue with the original line, coverage partial. With a valid `userId=10456` also present → `user_id: 10456`, the malformed lines retained as issues, coverage partial. ## Change and scope - `src/adb/AdbShellOutput.ts`: the id pattern requires the digits to end their token (`^(\d+)(?:\s|$)`). Whitespace-separated suffixes such as `userId=10001 installing=true` stay admitted exactly as before; non-numeric, negative and unsafe declarations keep their current reasons. - `tests/acceptance/applications/adbNumericDeclarations.test.ts`: two scenarios in the existing CLI + MCP table — attached text as the only declaration, and attached text on both sides of a valid declaration across both spellings. - Not included: no change to first-valid selection for well-formed declarations or to other `dumpsys` fields. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: `parseDumpsysPackageOutput`, the single parser of Package Manager id declarations; `AdbProvider` projects its parsed facts unchanged. No superseded path. - Contribution scope fit and linked maintainer decision: ordinary fix within the existing parser boundary — not applicable. - CLI and MCP/tool-catalog contract: such declarations now appear in `numeric_issues` (`invalid_format`) and make `coverage` partial instead of yielding a prefix id. No schema or tool-catalog change. - Provider, bridge, target-format, or platform compatibility: none; the accepted grammar for well-formed declarations is unchanged. - Evidence, artifact, provenance, or reconstruction contract: the original `raw_line` is retained in the issue. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), 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. - [ ] 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. ## Evidence and regression coverage - Tests added or updated: two scenarios in `tests/acceptance/applications/adbNumericDeclarations.test.ts`, run through both CLI and MCP. - Base reproduction or other evidence: executed. With the parser change stashed, the new scenario fails on `user_id` (expected `null`, received `10123`). - User-visible CLI/MCP output (if applicable): `userId=10123abc` alone → `user_id: null`, `numeric_issues.total: 1` (`invalid_format`, original line), `coverage: partial`. - Remaining proof gaps: synthetic `dumpsys` text through the existing adb stand-in fixture only; no real Android device or emulator, and no real-device occurrence of the attached-letter shape is claimed. Boundary regressions covered: malformed-input parsing and first-valid selection with issues on both sides. Lifecycle regressions: not applicable (no new resources). 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 - `npm run test:focused -- tests/acceptance/applications/adbNumericDeclarations.test.ts src/adb/AdbShellOutput.test.ts src/adb/AdbProvider.test.ts` — 151 passed. - `npm run check:fast` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Output that previously admitted a digit prefix now reports `user_id: null` or the next valid id, with partial coverage. - Real Hopper/Ghidra, browser, or OS coverage: none; no real Android device. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Version-code follow-up The same parser now rejects attached text in `versionCode` (#7534), preserving the first valid signed decimal token exactly and recording malformed lines as `version_code` numeric issues. This adds a field variant to the output schema and changes malformed-output coverage, so exhaustive consumers need to handle it. Validation on the updated branch: 48 parser and built CLI/MCP tests passed, including malformed declarations before and after a valid large signed value; `check:fast` and `git diff --check` passed. The adb responses are fixtures; no real device was tested. ## Author readiness Human owner: @kittimzhe - [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 - [ ] 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>
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#7859
No description provided.