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 #2639] [CLOSED] fix(native): retain partial metadata when a protocol-list slot is unmapped #5300

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2639
Author: @sx4im
Created: 10/13/2026
Status: ❌ Closed

Base: main ← Head: fix/2610-native-protocol-list-unmapped-partial

📝 Commits (10+)

  • c0b7781 fix(native): retain partial metadata when a protocol-list slot is unmapped
  • 9a80fb3 fix(native): bound failed class-list slots by the record budget
  • 794b734 fix(native): admit each failed objc list slot exactly once
  • 7b9b666 refactor(native): own failed Objective-C slot accounting once
  • 31137e5 fix(native): bound every Objective-C list slot attempt
  • 22b76ee fix(native): scope Objective-C list scan truncation
  • 92f72f4 fix(native): retain class-dependent scan coverage limits
  • 40e0de4 fix(native): give each Objective-C list scan its own slot bound
  • 05f9b3a fix(native): retain unresolved pointer coverage reasons
  • 98f985b refactor(test): split Apple dispatch budget cases

📊 Changes

5 files changed (+334 additions, -28 deletions)

View changed files

📝 src/native/AppleDispatchCoverage.ts (+19 -14)
📝 src/native/AppleDispatchMetadata.test.ts (+215 -0)
📝 src/native/AppleDispatchMetadata.ts (+18 -9)
📝 src/native/AppleObjcDispatchFacets.ts (+78 -5)
📝 src/native/AppleSwiftVtables.test.ts (+4 -0)

📄 Description

Summary

Fixes #2610.

A Mach-O image with valid Objective-C class metadata and an unmapped __objc_protolist slot failed its entire static dispatch-metadata decode. The class-list loop already records per-slot mapping failures into partial coverage, but the protocol-list loop read its slot pointer unguarded, so the same unmapped pointer aborted the whole decode before protocolReader.record could handle the record. Now the protocol-list slot uses the same guard as the class-list slot: the failure is recorded, the objc_class_method_ivar_metadata facet coverage becomes partial with a reason naming the mapping failure, and the independently decodable class is retained.

Problem and expected behavior

Smallest trigger: build the 4096-byte fixture from the issue with the protocol-list section address pointing at an unmapped page (base + 0x9000). The decode throws RangeError: Unmapped or ambiguous metadata pointer 0x100009000 out of decodeObjcDispatchFacets at the protolist loop (AppleObjcDispatchFacets.ts:203). Expected: partial coverage with a reason identifying the mapping failure while RetainedClass and its coverage records still reach the caller, matching the existing behavior for an unmapped class-list slot.

Change and scope

Wrapped the per-slot pointer read in the __objc_protolist loop in the same try/catch shape the __objc_classlist loop already uses in the same function: the field address is hoisted, the failure is pushed to failures as <field>: <message>, and the loop continues. pushDispatchCoverage already turns those failure strings into partial facet coverage with a reason, so no other code changes were needed. Added three regression tests in src/native/AppleDispatchMetadata.test.ts using the fixture from the issue verbatim (controls neither, class, protocol).

Scope decision: not applicable. This is a routine fix inside the existing decode boundary; no new providers, no target execution, no new scope.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Apple dispatch metadata decode (decodeObjcDispatchFacets, src/native/AppleObjcDispatchFacets.ts).
  • Contribution scope fit and linked maintainer decision: routine bug fix within existing boundaries; no scope expansion.
  • CLI and MCP/tool-catalog contract: none; no tool or contract changes.
  • Provider, bridge, target-format, or platform compatibility: Mach-O arm64 static decode only; fully mapped images decode exactly as before.
  • Evidence, artifact, provenance, or reconstruction contract: the coverage reason now names the unmapped protocol slot instead of the whole decode failing with no result.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • 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: 3 tests in src/native/AppleDispatchMetadata.test.ts ("Apple dispatch unmapped protocol-list slot"), fixture builder taken verbatim from the issue.
  • Base reproduction or other evidence: on the base revision the bad-protocol control threw RangeError: Unmapped or ambiguous metadata pointer 0x100009000 (new test failed red); after the fix the same control returns RetainedClass with the facet coverage partial and the reason containing 0x100009000. The neither control still returns the class with complete coverage, and the class control still yields partial coverage as before.
  • User-visible CLI/MCP output: not applicable.
  • Remaining proof gaps: the issue's NativeMacOSProvider provider-level repro was not exercised; the decoder test covers the root cause directly and the provider path only wraps this decoder.

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/native/AppleDispatchMetadata.test.ts - 25/25 passed (22 existing + 3 new; the protocol control failed before the fix, passed after)
  • npm run test:local -- src/native/AppleSwiftVtables.test.ts - 3/3 passed (only other test file importing this code path)
  • npm run check:fast - typecheck + lint green
  • npm run verify:test-discovery - all 1024 test files discovered exactly once

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: none; source tests exercise the Mach-O decode path directly.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none; decode-only change, no new execution paths.

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/2639 **Author:** [@sx4im](https://github.com/sx4im) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/2610-native-protocol-list-unmapped-partial` --- ### 📝 Commits (10+) - [`c0b7781`](https://github.com/morluto/rea/commit/c0b7781bb1bf1a0d95ec4a33bab1d0d9d335100d) fix(native): retain partial metadata when a protocol-list slot is unmapped - [`9a80fb3`](https://github.com/morluto/rea/commit/9a80fb3d9714a0ba0fe2bdb8c154543fa66eee63) fix(native): bound failed class-list slots by the record budget - [`794b734`](https://github.com/morluto/rea/commit/794b7346c39e1d295898bb7fd744e7e45a8c9717) fix(native): admit each failed objc list slot exactly once - [`7b9b666`](https://github.com/morluto/rea/commit/7b9b666548a930a40655ee10e1b858f6118a317c) refactor(native): own failed Objective-C slot accounting once - [`31137e5`](https://github.com/morluto/rea/commit/31137e5ea88f9dd4bba9fed6fb392e02b766ae7c) fix(native): bound every Objective-C list slot attempt - [`22b76ee`](https://github.com/morluto/rea/commit/22b76eec963e28b78e4dfd56daf77f7d453dd434) fix(native): scope Objective-C list scan truncation - [`92f72f4`](https://github.com/morluto/rea/commit/92f72f4d0848b6731417f3699ceff8613cf60c4b) fix(native): retain class-dependent scan coverage limits - [`40e0de4`](https://github.com/morluto/rea/commit/40e0de4f2fdd80645687593fe9caa03acf7b264e) fix(native): give each Objective-C list scan its own slot bound - [`05f9b3a`](https://github.com/morluto/rea/commit/05f9b3aaf04c0d20d684605015e11d0db9451f1b) fix(native): retain unresolved pointer coverage reasons - [`98f985b`](https://github.com/morluto/rea/commit/98f985b2ddf4e22100feb5fb988f49748ac2f0a7) refactor(test): split Apple dispatch budget cases ### 📊 Changes **5 files changed** (+334 additions, -28 deletions) <details> <summary>View changed files</summary> 📝 `src/native/AppleDispatchCoverage.ts` (+19 -14) 📝 `src/native/AppleDispatchMetadata.test.ts` (+215 -0) 📝 `src/native/AppleDispatchMetadata.ts` (+18 -9) 📝 `src/native/AppleObjcDispatchFacets.ts` (+78 -5) 📝 `src/native/AppleSwiftVtables.test.ts` (+4 -0) </details> ### 📄 Description ## Summary Fixes #2610. A Mach-O image with valid Objective-C class metadata and an unmapped `__objc_protolist` slot failed its entire static dispatch-metadata decode. The class-list loop already records per-slot mapping failures into partial coverage, but the protocol-list loop read its slot pointer unguarded, so the same unmapped pointer aborted the whole decode before `protocolReader.record` could handle the record. Now the protocol-list slot uses the same guard as the class-list slot: the failure is recorded, the `objc_class_method_ivar_metadata` facet coverage becomes partial with a reason naming the mapping failure, and the independently decodable class is retained. ## Problem and expected behavior Smallest trigger: build the 4096-byte fixture from the issue with the protocol-list section address pointing at an unmapped page (`base + 0x9000`). The decode throws `RangeError: Unmapped or ambiguous metadata pointer 0x100009000` out of `decodeObjcDispatchFacets` at the protolist loop (AppleObjcDispatchFacets.ts:203). Expected: partial coverage with a reason identifying the mapping failure while `RetainedClass` and its coverage records still reach the caller, matching the existing behavior for an unmapped class-list slot. ## Change and scope Wrapped the per-slot pointer read in the `__objc_protolist` loop in the same try/catch shape the `__objc_classlist` loop already uses in the same function: the field address is hoisted, the failure is pushed to `failures` as `<field>: <message>`, and the loop continues. `pushDispatchCoverage` already turns those failure strings into partial facet coverage with a reason, so no other code changes were needed. Added three regression tests in `src/native/AppleDispatchMetadata.test.ts` using the fixture from the issue verbatim (controls `neither`, `class`, `protocol`). Scope decision: not applicable. This is a routine fix inside the existing decode boundary; no new providers, no target execution, no new scope. ## Contract and boundary impact - Semantic owner and earliest changed stage: Apple dispatch metadata decode (`decodeObjcDispatchFacets`, `src/native/AppleObjcDispatchFacets.ts`). - Contribution scope fit and linked maintainer decision: routine bug fix within existing boundaries; no scope expansion. - CLI and MCP/tool-catalog contract: none; no tool or contract changes. - Provider, bridge, target-format, or platform compatibility: Mach-O arm64 static decode only; fully mapped images decode exactly as before. - Evidence, artifact, provenance, or reconstruction contract: the coverage reason now names the unmapped protocol slot instead of the whole decode failing with no result. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none. Expected effects: - [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: 3 tests in `src/native/AppleDispatchMetadata.test.ts` ("Apple dispatch unmapped protocol-list slot"), fixture builder taken verbatim from the issue. - Base reproduction or other evidence: on the base revision the bad-protocol control threw `RangeError: Unmapped or ambiguous metadata pointer 0x100009000` (new test failed red); after the fix the same control returns `RetainedClass` with the facet coverage `partial` and the reason containing `0x100009000`. The `neither` control still returns the class with complete coverage, and the `class` control still yields partial coverage as before. - User-visible CLI/MCP output: not applicable. - Remaining proof gaps: the issue's `NativeMacOSProvider` provider-level repro was not exercised; the decoder test covers the root cause directly and the provider path only wraps this decoder. 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/native/AppleDispatchMetadata.test.ts` - 25/25 passed (22 existing + 3 new; the protocol control failed before the fix, passed after) - `npm run test:local -- src/native/AppleSwiftVtables.test.ts` - 3/3 passed (only other test file importing this code path) - `npm run check:fast` - typecheck + lint green - `npm run verify:test-discovery` - all 1024 test files discovered exactly once ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: none; source tests exercise the Mach-O decode path directly. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none; decode-only change, no new execution paths. ## 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:05:33 +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#5300
No description provided.