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 #6010] [MERGED] fix(adb): report an unparsed push checksum as unverified #7119

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6010
Author: @kaoru0822-kitauji
Created: 10/21/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @kaoru0822-kitauji

Base: main ← Head: fix/5924-adb-push-digest-source

📝 Commits (1)

  • 6b4cc55 fix(adb): derive push digest source from the parsed device digest

📊 Changes

4 files changed (+136 additions, -40 deletions)

View changed files

📝 docs/adb-device-analysis.md (+3 -1)
📝 src/adb/AdbProvider.test.ts (+69 -25)
📝 src/adb/AdbProvider.ts (+56 -14)
📝 src/adb/AdbShellOutput.ts (+8 -0)

📄 Description

What broke: after a successful push_adb_file, a sha256sum that exited 0 with no recognizable digest produced device_sha256: null with device_digest_source: "device_sha256sum" and dropped the "not device-side verified" limitation.
Fix: the push receipt takes one tagged device digest (digest + source together), derived from a single sha256sum parser, so unparsed output reports "unavailable", the unverified limitation, and the raw command output.
Risk: low; ADB push receipt only, output schema unchanged. GNU-escaped (\-prefixed) checksum lines now verify instead of being treated as unrecognized.

Summary

Fixes #5924. push_adb_file now reports device_digest_source: "device_sha256sum" only when a device digest was actually parsed. A zero-exit sha256sum with empty or unrecognizable output is reported like a missing command: device_sha256: null, device_digest_source: "unavailable", and a limitation stating the transfer is not device-side verified. The unrecognized output is kept in raw_result.device_sha256sum.

Problem and expected behavior

pushFile built its receipt from two independent arguments: the regex match (or null) and a hard-coded "device_sha256sum" source on every zero-exit path. Any successful exit therefore claimed sha256sum as the digest source, even with no digest parsed, and skipped the unverified-transfer limitation that the nonzero-exit branch adds. Expected: a successful exit alone does not establish that a checksum was obtained or compared (issue #5924).

Change and scope

  • src/adb/AdbProvider.ts: the receipt takes a tagged AdbDeviceDigest ({device_sha256: string, source: "device_sha256sum"} or {device_sha256: null, source: "unavailable", reason}). Source, digest and the unverified limitation can no longer disagree. The unparsed branch keeps the command's stdout/stderr as rawResult, following the existing start_adb_activity pattern.
  • src/adb/AdbShellOutput.ts: parseSha256sumOutput owns the sha256sum FILE line format alongside the other shell-output parsers. It requires the <digest> <space|*> separator and accepts GNU's leading backslash, which marks an escaped echoed name; the digest itself is never escaped. This replaces the inline /^([a-f0-9]{64})\s/ regex.
  • docs/adb-device-analysis.md: documents the unavailable outcome.
  • The advertised output schema (device_sha256 nullable + device_digest_source enum) is unchanged. I kept it that way rather than making it a discriminated union, which would change the published JSON Schema.
  • Related ADB paths checked: pull, bugreport, screencap and package pull use host-side digests (digest_status). Install has no digest. Push is the only device-side digest reader.
  • Not included: the capture budget for long device paths (#3369, open PR #3458 touches the neighbouring lines; whichever lands second needs a small rebase).

Ordinary fix within existing boundaries; scope decision not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: ADB provider push verification (AdbShellOutput parser → pushFile receipt).
  • Contribution scope fit and linked maintainer decision: not applicable (bug fix).
  • CLI and MCP/tool-catalog contract: schema unchanged; field values for unparseable checksum output change as described.
  • Provider, bridge, target-format, or platform compatibility: ADB provider only.
  • Evidence, artifact, provenance, or reconstruction contract: unparsed checksum output now adds a raw_result with device_sha256sum.stdout/stderr and the unverified limitation.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): same adb commands, arguments and limits.
  • Generated metadata, package, or installation impact: none.

Expected effects (these belong to the existing push_adb_file operation; this PR adds none):

  • 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/AdbProvider.test.ts "derives the push digest source from …" is a table through the production AdbProvider with a simulated adb executable. Cases: valid line, GNU-escaped line, empty stdout, malformed line (63 hex chars), nonzero exit (127). It asserts digest/source, the unverified limitation, and rawResult. It replaces the single-case "pushes a file and verifies the device-side digest" test.
  • Base reproduction: on 6d356b843 the new table failed for escaped, empty and malformed (3 failed, 2 passed). The issue's repro test through AdbDeviceAnalysisService on this branch: valid, empty and missing pass. escaped now reports a verified digest (device_sha256sum) instead of the issue's expected unavailable, by design (see Change).
  • User-visible output (from the issue repro, empty case): {"device_sha256":null,"device_digest_source":"unavailable","limitations":[…,"The device's sha256sum output contained no recognizable digest, so the transfer is not device-side verified"]}.
  • Remaining proof gaps: no real Android device or emulator was contacted. Toybox sha256sum output was not observed directly; the parser accepts its documented <digest> <name> form.

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:local -- src/adb/*.test.ts src/application/adb/*.test.ts src/contracts/toolEffects.test.ts: 8 files, 201 tests passed
  • Issue #5924 repro test (temporary, removed): valid/empty/missing passed; escaped intentionally differs as described
  • npm run check:fast: passed
  • npm run format:check: passed
  • npm run docs:check: passed

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Callers that already treated a null device_sha256 as unverified are unaffected.
  • Real Hopper/Ghidra, browser, or OS coverage: macOS with a simulated adb; no device.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: raw_result holds at most the existing 1 KiB capture of sha256sum output for the caller-selected device path.

Author readiness

Human owner: @kaoru0822-kitauji

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

🤖 Generated with Claude Code

🔄 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/6010 **Author:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Base:** `main` ← **Head:** `fix/5924-adb-push-digest-source` --- ### 📝 Commits (1) - [`6b4cc55`](https://github.com/morluto/rea/commit/6b4cc5594880c5cf18b0203b4041acf8204fd871) fix(adb): derive push digest source from the parsed device digest ### 📊 Changes **4 files changed** (+136 additions, -40 deletions) <details> <summary>View changed files</summary> 📝 `docs/adb-device-analysis.md` (+3 -1) 📝 `src/adb/AdbProvider.test.ts` (+69 -25) 📝 `src/adb/AdbProvider.ts` (+56 -14) 📝 `src/adb/AdbShellOutput.ts` (+8 -0) </details> ### 📄 Description **What broke:** after a successful `push_adb_file`, a `sha256sum` that exited 0 with no recognizable digest produced `device_sha256: null` with `device_digest_source: "device_sha256sum"` and dropped the "not device-side verified" limitation. **Fix:** the push receipt takes one tagged device digest (digest + source together), derived from a single `sha256sum` parser, so unparsed output reports `"unavailable"`, the unverified limitation, and the raw command output. **Risk:** low; ADB push receipt only, output schema unchanged. GNU-escaped (`\`-prefixed) checksum lines now verify instead of being treated as unrecognized. ## Summary Fixes #5924. `push_adb_file` now reports `device_digest_source: "device_sha256sum"` only when a device digest was actually parsed. A zero-exit `sha256sum` with empty or unrecognizable output is reported like a missing command: `device_sha256: null`, `device_digest_source: "unavailable"`, and a limitation stating the transfer is not device-side verified. The unrecognized output is kept in `raw_result.device_sha256sum`. ## Problem and expected behavior `pushFile` built its receipt from two independent arguments: the regex match (or `null`) and a hard-coded `"device_sha256sum"` source on every zero-exit path. Any successful exit therefore claimed `sha256sum` as the digest source, even with no digest parsed, and skipped the unverified-transfer limitation that the nonzero-exit branch adds. Expected: a successful exit alone does not establish that a checksum was obtained or compared (issue #5924). ## Change and scope - `src/adb/AdbProvider.ts`: the receipt takes a tagged `AdbDeviceDigest` (`{device_sha256: string, source: "device_sha256sum"}` or `{device_sha256: null, source: "unavailable", reason}`). Source, digest and the unverified limitation can no longer disagree. The unparsed branch keeps the command's stdout/stderr as `rawResult`, following the existing `start_adb_activity` pattern. - `src/adb/AdbShellOutput.ts`: `parseSha256sumOutput` owns the `sha256sum FILE` line format alongside the other shell-output parsers. It requires the `<digest> <space|*>` separator and accepts GNU's leading backslash, which marks an escaped echoed name; the digest itself is never escaped. This replaces the inline `/^([a-f0-9]{64})\s/` regex. - `docs/adb-device-analysis.md`: documents the unavailable outcome. - The advertised output schema (`device_sha256` nullable + `device_digest_source` enum) is unchanged. I kept it that way rather than making it a discriminated union, which would change the published JSON Schema. - Related ADB paths checked: pull, bugreport, screencap and package pull use host-side digests (`digest_status`). Install has no digest. Push is the only device-side digest reader. - Not included: the capture budget for long device paths (#3369, open PR #3458 touches the neighbouring lines; whichever lands second needs a small rebase). Ordinary fix within existing boundaries; scope decision not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: ADB provider push verification (`AdbShellOutput` parser → `pushFile` receipt). - Contribution scope fit and linked maintainer decision: not applicable (bug fix). - CLI and MCP/tool-catalog contract: schema unchanged; field values for unparseable checksum output change as described. - Provider, bridge, target-format, or platform compatibility: ADB provider only. - Evidence, artifact, provenance, or reconstruction contract: unparsed checksum output now adds a `raw_result` with `device_sha256sum.stdout/stderr` and the unverified limitation. - Target selection, authority, upstream behavior, and cleanup details (if applicable): same adb commands, arguments and limits. - Generated metadata, package, or installation impact: none. Expected effects (these belong to the existing `push_adb_file` operation; this PR adds none): - [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. ## Evidence and regression coverage - Tests added or updated: `src/adb/AdbProvider.test.ts` "derives the push digest source from …" is a table through the production `AdbProvider` with a simulated adb executable. Cases: valid line, GNU-escaped line, empty stdout, malformed line (63 hex chars), nonzero exit (127). It asserts digest/source, the unverified limitation, and `rawResult`. It replaces the single-case "pushes a file and verifies the device-side digest" test. - Base reproduction: on `6d356b843` the new table failed for escaped, empty and malformed (3 failed, 2 passed). The issue's repro test through `AdbDeviceAnalysisService` on this branch: valid, empty and missing pass. `escaped` now reports a verified digest (`device_sha256sum`) instead of the issue's expected `unavailable`, by design (see Change). - User-visible output (from the issue repro, empty case): `{"device_sha256":null,"device_digest_source":"unavailable","limitations":[…,"The device's sha256sum output contained no recognizable digest, so the transfer is not device-side verified"]}`. - Remaining proof gaps: no real Android device or emulator was contacted. Toybox `sha256sum` output was not observed directly; the parser accepts its documented `<digest> <name>` form. 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:local -- src/adb/*.test.ts src/application/adb/*.test.ts src/contracts/toolEffects.test.ts`: 8 files, 201 tests passed - Issue #5924 repro test (temporary, removed): valid/empty/missing passed; escaped intentionally differs as described - `npm run check:fast`: passed - `npm run format:check`: passed - `npm run docs:check`: passed ## Compatibility, safety, and release - Breaking changes or migration steps: none. Callers that already treated a null `device_sha256` as unverified are unaffected. - Real Hopper/Ghidra, browser, or OS coverage: macOS with a simulated adb; no device. - Package or release metadata impact: none. - Security, privacy, process, or containment review: `raw_result` holds at most the existing 1 KiB capture of `sha256sum` output for the caller-selected device path. ## Author readiness Human owner: @kaoru0822-kitauji - [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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:45:30 +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#7119
No description provided.