morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 07:47:29 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #4167] [CLOSED] fix(adb): parse the bare numeric wm density form #6107

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4167
Author: @DeryFerd
Created: 10/15/2026
Status: ❌ Closed

Base: main ← Head: fix/adb-density-bare-number

📝 Commits (1)

  • a38667c fix(adb): parse the bare numeric wm density form

📊 Changes

2 files changed (+29 additions, -2 deletions)

View changed files

📝 src/adb/AdbShellOutput.test.ts (+23 -1)
📝 src/adb/AdbShellOutput.ts (+6 -1)

📄 Description

fix(adb): parse the bare numeric wm density form

Summary

Fixes #3942.

inspect-adb-display reports physical_density: null for devices and builds whose wm density prints the physical density as a bare number with no label, which is the older format the parser's own documentation already recognizes. The command still exits 0 and returns a successful result, so the loss is silent: the caller sees a missing density rather than a failed read. This change reads the bare numeric line and keeps it as the physical density.

Problem and expected behavior

The smallest trigger is a device whose wm density output is exactly 420 followed by a newline. parseWmDensityOutput only matched Physical density: <n> and Override density: <n>, so a bare number matched neither branch and the loop returned { physical: null, override: null }. The CLI projection then showed physical_density: null and override_density: null alongside the correctly parsed physical_size, with exit code 0, ok: true, and empty stderr. The labeled controls (Physical density: 420 and Physical density: 420\nOverride density: 480) returned the expected values, which shows the failure is specific to the unlabeled form and not to density parsing in general.

The violated invariant is that a successful display inspection reports the size and density the device declared, and the parser's documentation already states that older builds print a bare number. Reporting null for a value the device did supply turns an observation into an absence, and because the result is still a success the caller has no signal that anything was dropped.

Expected behavior after the change: 420 yields { physical: 420, override: null }, the labeled single-line form yields { physical: 420, override: null }, the two-line labeled form yields { physical: 420, override: 480 }, and an unlabeled line that is not a plain integer, such as Physical size: 1080x2340, still yields { physical: null, override: null } rather than a fabricated density.

Change and scope

A third pattern, ^(\d+)$, is matched against each trimmed line and its value is held in a separate bare slot. The return keeps the labeled physical density when present and falls back to the bare value otherwise: { physical: physical ?? bare, override }. The labeled form stays authoritative, so a device that prints both cannot have the bare reading override the explicit declaration.

The fallback is applied only to the physical density and never to the override. A bare number carries no label, so the only reading the format supports is the physical density; assigning it to the override would be a guess. The bare pattern requires the entire trimmed line to be digits, so 1080x2340, Physical size: …, or any other non-integer line is left alone. This is the same shape the parser already uses for wm size, where an unrecognized line contributes nothing.

Not included: no change to parseWmSizeOutput, no change to the CLI projection or the result schema, no new field, and no heuristic for guessing an override from an unlabeled value.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/adb/AdbShellOutput.ts owns the device-output parsers; the earliest changed stage is the parse of wm density output.
  • Contribution scope fit and linked maintainer decision: an ordinary fix inside an existing boundary, so not applicable.
  • CLI and MCP/tool-catalog contract: no signature or schema change. inspect-adb-display reports a non-null physical_density where the device declared one.
  • Provider, bridge, target-format, or platform compatibility: the labeled format keeps its existing result, so newer builds are unaffected; older bare-number builds gain the density they always printed.
  • Evidence, artifact, provenance, or reconstruction contract: a declared density is now preserved instead of being reported as absent, which keeps omission and observation distinct.
  • Target selection, authority, upstream behavior, and cleanup details: none, this stage reads command output and issues no device action beyond the observation the command already runs.
  • 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.

Evidence and regression coverage

  • Tests added or updated: src/adb/AdbShellOutput.test.ts gains a parseWmDensityOutput block covering the labeled physical and override declarations, the bare numeric declaration read as the physical density, and an unlabeled non-numeric line that is not treated as a density.

  • Base reproduction or other evidence: the issue records the base CLI returning physical_density: null with exit 0 for the bare declaration and 420 for the labeled controls. The new bare-number test fails on the base and passes on this branch, and the labeled-form test passes on both, which pins the regression to the missing format branch.

  • User-visible CLI/MCP output: the issue shows the base display projection with physical_density: null while physical_size is populated, and the labeled controls with 420 and 480. After the change the bare declaration returns 420 in the same field.
    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.

  • Remaining proof gaps: this session exercised the parser through its unit tests rather than through the CLI. The issue's reproduction used a simulated provider, so it establishes the format-specific loss for that provider and not its frequency on real devices. No real adb binary or physical device was available here, so the end-to-end CLI path and real-device format coverage remain unverified.

Validation performed

  • npm run test:focused -- src/adb/AdbShellOutput.test.ts — all tests passed, including the bare-number case that fails on the base revision.
  • npm run check:fast — typecheck and lint succeeded.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Only previously null results for the bare format change, and they change to the value the device declared.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. No real adb binary or device was available, so this change is not claimed as verified against a physical device.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the change reads one additional line of already-captured command output and issues no new command or device action.

Author readiness

Human owner: @DeryFerd

  • 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/4167 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/15/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/adb-density-bare-number` --- ### 📝 Commits (1) - [`a38667c`](https://github.com/morluto/rea/commit/a38667cb87b0a72b74ad80d1e0d08d4b92d2b2fd) fix(adb): parse the bare numeric wm density form ### 📊 Changes **2 files changed** (+29 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `src/adb/AdbShellOutput.test.ts` (+23 -1) 📝 `src/adb/AdbShellOutput.ts` (+6 -1) </details> ### 📄 Description fix(adb): parse the bare numeric wm density form ## Summary Fixes #3942. `inspect-adb-display` reports `physical_density: null` for devices and builds whose `wm density` prints the physical density as a bare number with no label, which is the older format the parser's own documentation already recognizes. The command still exits 0 and returns a successful result, so the loss is silent: the caller sees a missing density rather than a failed read. This change reads the bare numeric line and keeps it as the physical density. ## Problem and expected behavior The smallest trigger is a device whose `wm density` output is exactly `420` followed by a newline. `parseWmDensityOutput` only matched `Physical density: <n>` and `Override density: <n>`, so a bare number matched neither branch and the loop returned `{ physical: null, override: null }`. The CLI projection then showed `physical_density: null` and `override_density: null` alongside the correctly parsed `physical_size`, with exit code 0, `ok: true`, and empty stderr. The labeled controls (`Physical density: 420` and `Physical density: 420\nOverride density: 480`) returned the expected values, which shows the failure is specific to the unlabeled form and not to density parsing in general. The violated invariant is that a successful display inspection reports the size and density the device declared, and the parser's documentation already states that older builds print a bare number. Reporting `null` for a value the device did supply turns an observation into an absence, and because the result is still a success the caller has no signal that anything was dropped. Expected behavior after the change: `420` yields `{ physical: 420, override: null }`, the labeled single-line form yields `{ physical: 420, override: null }`, the two-line labeled form yields `{ physical: 420, override: 480 }`, and an unlabeled line that is not a plain integer, such as `Physical size: 1080x2340`, still yields `{ physical: null, override: null }` rather than a fabricated density. ## Change and scope A third pattern, `^(\d+)$`, is matched against each trimmed line and its value is held in a separate `bare` slot. The return keeps the labeled physical density when present and falls back to the bare value otherwise: `{ physical: physical ?? bare, override }`. The labeled form stays authoritative, so a device that prints both cannot have the bare reading override the explicit declaration. The fallback is applied only to the physical density and never to the override. A bare number carries no label, so the only reading the format supports is the physical density; assigning it to the override would be a guess. The bare pattern requires the entire trimmed line to be digits, so `1080x2340`, `Physical size: …`, or any other non-integer line is left alone. This is the same shape the parser already uses for `wm size`, where an unrecognized line contributes nothing. Not included: no change to `parseWmSizeOutput`, no change to the CLI projection or the result schema, no new field, and no heuristic for guessing an override from an unlabeled value. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/adb/AdbShellOutput.ts` owns the device-output parsers; the earliest changed stage is the parse of `wm density` output. - Contribution scope fit and linked maintainer decision: an ordinary fix inside an existing boundary, so not applicable. - CLI and MCP/tool-catalog contract: no signature or schema change. `inspect-adb-display` reports a non-null `physical_density` where the device declared one. - Provider, bridge, target-format, or platform compatibility: the labeled format keeps its existing result, so newer builds are unaffected; older bare-number builds gain the density they always printed. - Evidence, artifact, provenance, or reconstruction contract: a declared density is now preserved instead of being reported as absent, which keeps omission and observation distinct. - Target selection, authority, upstream behavior, and cleanup details: none, this stage reads command output and issues no device action beyond the observation the command already runs. - 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. - [ ] 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: `src/adb/AdbShellOutput.test.ts` gains a `parseWmDensityOutput` block covering the labeled physical and override declarations, the bare numeric declaration read as the physical density, and an unlabeled non-numeric line that is not treated as a density. - Base reproduction or other evidence: the issue records the base CLI returning `physical_density: null` with exit 0 for the bare declaration and 420 for the labeled controls. The new bare-number test fails on the base and passes on this branch, and the labeled-form test passes on both, which pins the regression to the missing format branch. - User-visible CLI/MCP output: the issue shows the base display projection with `physical_density: null` while `physical_size` is populated, and the labeled controls with 420 and 480. After the change the bare declaration returns 420 in the same field. 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. - Remaining proof gaps: this session exercised the parser through its unit tests rather than through the CLI. The issue's reproduction used a simulated provider, so it establishes the format-specific loss for that provider and not its frequency on real devices. No real adb binary or physical device was available here, so the end-to-end CLI path and real-device format coverage remain unverified. ## Validation performed - `npm run test:focused -- src/adb/AdbShellOutput.test.ts` — all tests passed, including the bare-number case that fails on the base revision. - `npm run check:fast` — typecheck and lint succeeded. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Only previously null results for the bare format change, and they change to the value the device declared. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. No real adb binary or device was available, so this change is not claimed as verified against a physical device. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the change reads one additional line of already-captured command output and issues no new command or device action. ## Author readiness Human owner: @DeryFerd - [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>
bsakaguchi 2026-10-31 01:11:55 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/procedure-reference-stacked
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#6107
No description provided.