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 #2804] [MERGED] fix(flutter): find snapshot headers that a read chunk boundary splits #5407

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2804
Author: @Dragolone
Created: 10/13/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @morluto

Base: main ← Head: fix/flutter-snapshot-scan-chunk-boundary

📝 Commits (2)

  • c24f744 fix(flutter): find snapshot headers that a read chunk boundary splits
  • 743dbfb refactor(flutter): drop the snapshot scanner cursor the fix superseded

📊 Changes

2 files changed (+37 additions, -14 deletions)

View changed files

📝 src/flutter/FlutterPayloadScan.test.ts (+31 -0)
📝 src/flutter/FlutterPayloadScan.ts (+6 -14)

📄 Description

Summary

identify_flutter_build can omit a Dart snapshot hash, and report coverage: "complete" with a single agreed hash, depending only on where the APK reader's chunk boundaries fall.

Within one chunk, SnapshotHashScanner resumes four bytes after each magic. Across chunks it resumed after the whole 52-byte magic-to-hash record and dropped the carried bytes. A magic starting 49–51 bytes after a rejected (non-hex) record was therefore lost when its four bytes straddled a read boundary. This PR resumes after the magic in both cases.

No issue is linked: I searched issues and PRs for SnapshotHashScanner, FlutterPayloadScan, "snapshot hash chunk boundary", "snapshot magic" and identify_flutter_build and found no report. The #1582 review fixed chunk-boundary cases in the labeled-string scanner, not this one. Open PR #2334 touches DartElf.ts, not this scanner.

Problem and expected behavior

Smallest trigger: a stray magic f5 f5 dc dc whose hash field is not lowercase hex, followed 50 bytes later by a real snapshot section. Fed as one chunk, the scanner finds 1 source. Split at byte 52, it finds 0.

End to end: an APK whose lib/arm64-v8a/libapp.so holds the VM and isolate sections (hash 65817c30…), a stray magic at 65484, and a third section with hash 2222… at 65534. The third section's magic straddles zip.js's 64 KiB read boundary.

Violated contract: docs/flutter-analysis.md says that when snapshot hashes disagree, all candidates are kept, snapshot_hash is null, and coverage is partial rather than silently picking one. With the bug, the conflicting hash is dropped and the result says complete.

Expected: the result does not depend on chunking, so the APK above reports both candidates, a null hash, and partial coverage.

Change and scope

The cross-chunk resume point now matches the in-chunk one: right after the processed magic. After a complete record, the carried tail is shorter than a magic. A pending magic has not been processed yet. So each push can rescan its carried bytes from the start without counting a record twice. That made the absolute cursor (#absoluteScanFrom) and its #base offset unnecessary, and both are removed (thanks to the Codex review). No other scanner behavior changes. Not included: the labeled-string scanner and DartElf.ts.

Contribution scope: an ordinary static format-inspection correctness fix within existing boundaries; a maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: SnapshotHashScanner.push in src/flutter/FlutterPayloadScan.ts.
  • Contribution scope fit and linked maintainer decision: in scope (format inspection, evidence reporting); not applicable.
  • CLI and MCP/tool-catalog contract: no schema change. snapshot_hash_sources, snapshot_hash_candidates, snapshot_hash and coverage now match the single-chunk result for affected inputs.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: fixes a case where a disagreement was silently omitted while coverage said complete.
  • 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: src/flutter/FlutterPayloadScan.test.ts — "finds a section %i bytes after a rejected record at any chunking", run for offsets 49, 50 and 51. It splits the payload at every byte and also feeds it one byte at a time. Every result must equal the single-chunk result.
  • Base reproduction: on 91830f1e0 all three cases fail with AssertionError: split at 52: expected { sources: +0, candidates: [], …(1) } to deeply equal { sources: 1, …(2) }.
  • User-visible output: FlutterBuildProvider identify_flutter_build on the APK described above (a local test that was not committed):
    • Before: { coverage: 'complete', sources: 2, candidates: [ '65817c30a78bb44c3dc3771876b6010a' ], hash: '65817c30a78bb44c3dc3771876b6010a' }
    • After: { coverage: 'partial', sources: 3, candidates: [ '65817c30a78bb44c3dc3771876b6010a', '22222222222222222222222222222222' ], hash: null }
  • Remaining proof gaps: the trigger needs a magic within 49–51 bytes after a rejected record and a read boundary inside the second magic. I have not observed it in a real Flutter APK.

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

macOS (Apple silicon), Node 24.19.0.

  • npx vitest run src/flutter/FlutterPayloadScan.test.ts against the base scanner — the three new cases fail as quoted above (14 others pass).
  • npx vitest run src/flutter/ with the fix — 2 files, 31 tests passed.
  • A local split fuzz (not committed): 50,000 random payloads with clustered magics and valid hashes, each fed in random 1–80-byte chunks and compared with a single push. The base had 1 mismatch; the fix, before and after the cursor removal, had 0.
  • The end-to-end identify_flutter_build comparison above, run against the base and the fix.
  • npm run typecheck — passed.
  • npx oxfmt --check on both changed files — passed.
  • npm run verify:module-boundaries — passed.
  • npm run lint — the only error is tests/boundary/providers/ghidra/ghidraLauncher.test.ts:431 (max-lines-per-function), which this PR does not touch. The changed files have only the existing no-control-regex warnings.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no change; pure in-memory byte scanning.

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/2804 **Author:** [@Dragolone](https://github.com/Dragolone) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/flutter-snapshot-scan-chunk-boundary` --- ### 📝 Commits (2) - [`c24f744`](https://github.com/morluto/rea/commit/c24f7443f3f3faf42cbbf1b1c5734816b62ca808) fix(flutter): find snapshot headers that a read chunk boundary splits - [`743dbfb`](https://github.com/morluto/rea/commit/743dbfb6569a017ea9bbde7c046c06cc52220e29) refactor(flutter): drop the snapshot scanner cursor the fix superseded ### 📊 Changes **2 files changed** (+37 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `src/flutter/FlutterPayloadScan.test.ts` (+31 -0) 📝 `src/flutter/FlutterPayloadScan.ts` (+6 -14) </details> ### 📄 Description ## Summary `identify_flutter_build` can omit a Dart snapshot hash, and report `coverage: "complete"` with a single agreed hash, depending only on where the APK reader's chunk boundaries fall. Within one chunk, `SnapshotHashScanner` resumes four bytes after each magic. Across chunks it resumed after the whole 52-byte magic-to-hash record and dropped the carried bytes. A magic starting 49–51 bytes after a rejected (non-hex) record was therefore lost when its four bytes straddled a read boundary. This PR resumes after the magic in both cases. No issue is linked: I searched issues and PRs for `SnapshotHashScanner`, `FlutterPayloadScan`, "snapshot hash chunk boundary", "snapshot magic" and `identify_flutter_build` and found no report. The #1582 review fixed chunk-boundary cases in the labeled-string scanner, not this one. Open PR #2334 touches `DartElf.ts`, not this scanner. ## Problem and expected behavior Smallest trigger: a stray magic `f5 f5 dc dc` whose hash field is not lowercase hex, followed 50 bytes later by a real snapshot section. Fed as one chunk, the scanner finds 1 source. Split at byte 52, it finds 0. End to end: an APK whose `lib/arm64-v8a/libapp.so` holds the VM and isolate sections (hash `65817c30…`), a stray magic at 65484, and a third section with hash `2222…` at 65534. The third section's magic straddles zip.js's 64 KiB read boundary. Violated contract: `docs/flutter-analysis.md` says that when snapshot hashes disagree, all candidates are kept, `snapshot_hash` is null, and coverage is partial rather than silently picking one. With the bug, the conflicting hash is dropped and the result says complete. Expected: the result does not depend on chunking, so the APK above reports both candidates, a null hash, and partial coverage. ## Change and scope The cross-chunk resume point now matches the in-chunk one: right after the processed magic. After a complete record, the carried tail is shorter than a magic. A pending magic has not been processed yet. So each push can rescan its carried bytes from the start without counting a record twice. That made the absolute cursor (`#absoluteScanFrom`) and its `#base` offset unnecessary, and both are removed (thanks to the Codex review). No other scanner behavior changes. Not included: the labeled-string scanner and `DartElf.ts`. Contribution scope: an ordinary static format-inspection correctness fix within existing boundaries; a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `SnapshotHashScanner.push` in `src/flutter/FlutterPayloadScan.ts`. - Contribution scope fit and linked maintainer decision: in scope (format inspection, evidence reporting); not applicable. - CLI and MCP/tool-catalog contract: no schema change. `snapshot_hash_sources`, `snapshot_hash_candidates`, `snapshot_hash` and `coverage` now match the single-chunk result for affected inputs. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: fixes a case where a disagreement was silently omitted while coverage said complete. - 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: `src/flutter/FlutterPayloadScan.test.ts` — "finds a section %i bytes after a rejected record at any chunking", run for offsets 49, 50 and 51. It splits the payload at every byte and also feeds it one byte at a time. Every result must equal the single-chunk result. - Base reproduction: on `91830f1e0` all three cases fail with `AssertionError: split at 52: expected { sources: +0, candidates: [], …(1) } to deeply equal { sources: 1, …(2) }`. - User-visible output: `FlutterBuildProvider` `identify_flutter_build` on the APK described above (a local test that was not committed): - Before: `{ coverage: 'complete', sources: 2, candidates: [ '65817c30a78bb44c3dc3771876b6010a' ], hash: '65817c30a78bb44c3dc3771876b6010a' }` - After: `{ coverage: 'partial', sources: 3, candidates: [ '65817c30a78bb44c3dc3771876b6010a', '22222222222222222222222222222222' ], hash: null }` - Remaining proof gaps: the trigger needs a magic within 49–51 bytes after a rejected record and a read boundary inside the second magic. I have not observed it in a real Flutter APK. 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 macOS (Apple silicon), Node 24.19.0. - `npx vitest run src/flutter/FlutterPayloadScan.test.ts` against the base scanner — the three new cases fail as quoted above (14 others pass). - `npx vitest run src/flutter/` with the fix — 2 files, 31 tests passed. - A local split fuzz (not committed): 50,000 random payloads with clustered magics and valid hashes, each fed in random 1–80-byte chunks and compared with a single push. The base had 1 mismatch; the fix, before and after the cursor removal, had 0. - The end-to-end `identify_flutter_build` comparison above, run against the base and the fix. - `npm run typecheck` — passed. - `npx oxfmt --check` on both changed files — passed. - `npm run verify:module-boundaries` — passed. - `npm run lint` — the only error is `tests/boundary/providers/ghidra/ghidraLauncher.test.ts:431` (`max-lines-per-function`), which this PR does not touch. The changed files have only the existing `no-control-regex` warnings. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no change; pure in-memory byte scanning. ## 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:06:24 +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#5407
No description provided.