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 #7023] [MERGED] fix(lldb): retain completed trace facts through cleanup failures #7582

New issue
Closed
opened 2026-11-03 13:38:52 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:38:52 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7023
Author: @WenyuChiou
Created: 10/24/2026
Status: ✅ Merged
Merged: 10/24/2026
Merged by: @morluto

Base: main ← Head: fix/5913-completed-trace-retention-20261024

📝 Commits (1)

  • d7a0a98 fix(lldb): retain completed trace facts through cleanup failures

📊 Changes

4 files changed (+314 additions, -25 deletions)

View changed files

📝 src/native/LldbCallTracer.ts (+52 -19)
📝 src/native/NativeCallObservation.ts (+9 -5)
📝 tests/boundary/providers/native/lldbCallTracerFailures.test.ts (+251 -0)
📝 tests/boundary/providers/native/nativeCallObservation.test.ts (+2 -1)

📄 Description

Summary

Fixes #5913's remaining completed-trace retention failures during cleanup. The original output-close cancellation case is already covered upstream; this change addresses the two residual cleanup paths described in the issue follow-up.

Problem and expected behavior

After reading a valid completed LLDB result, process-group cleanup failure or uncertain target termination falls back to journal-only observations. This discards outcome, exit status, elapsed time, launch identity and breakpoints, and replaces final stdout bytes 4096 with the retained abc prefix length 3. Target-only uncertainty also reports tracer-failure instead of cleanup-failure.

Completed observations should survive without treating the producer's termination report as proof of host cleanup.

Change and scope

  • Reuse the existing completed-observation projector and share capture readback with the success path.
  • Keep cleanup failure primary when a capture read also fails; retain sibling captures and other completed facts.
  • Preserve journal-only fallback for missing or invalid completed results.
  • Derive limit-outcome wording from the same conservative termination decision as process.terminated, avoiding “was killed” when termination is unconfirmed.
  • Retain cleanup ownership, replacement blocking and retry behavior.

This is a routine correction within existing LLDB boundaries, not a new execution or mutation capability; a separate advance maintainer scope decision is not applicable. It does not duplicate #4751's descriptor-close ownership work.

Contract and boundary impact

  • Semantic owner: LLDB result readback and native-call observation projection.
  • CLI/MCP schemas, provider selection, target formats and platform support: unchanged.
  • Evidence: retain validated completed facts and final counters; keep capture completeness and host cleanup uncertainty explicit.
  • Target authority and cleanup: unchanged. Producer termination and host confirmation must both hold before reporting termination.
  • Generated metadata, dependencies, package and installation behavior: unchanged.

Expected workflow effects inherited from the existing provider:

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

The checked effects describe the existing debugger workflow and temporary capture/cleanup files, not new authority. Added regressions use synthetic launcher/cleanup fixtures; no real LLDB or target binary was executed.

Evidence and regression coverage

Executed locally on base 397aa62f2e203bc0f8350634752af0339048e81e and the reviewed four-file patch:

  • Before the fix, the clean control passed and both new cleanup regressions failed: completed fields/counters were missing, and target uncertainty had the wrong reason.
  • An added duration-limit/uncertain-termination regression failed on the false “was killed” note, then passed after the projection correction.
  • Seven added cases cover clean/group/target-uncertain/duration-limit-uncertain/group-plus-capture-failure paths and missing/invalid-result fallback. Group cleanup also checks replacement blocking, failed close and successful retry.
  • The existing wording oracle was corrected to exact uncertainty wording while retaining its structured assertions and adding a no-“was killed” assertion; coverage was not weakened.
  • Full final stdout count remains 4096 while retained text remains abc; sibling stderr retains its complete two-byte capture. Capture completeness semantics are unchanged.

The original failing wording-oracle log was overwritten by its passing rerun; only a transcript-derived failure excerpt remains. That excerpt is not represented as a preserved raw log. Automated static review found the wording and combined capture-failure gaps above; both were addressed and re-reviewed. This is not human review.

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved, with the log limitation disclosed above.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

Linux cloud executor, Node 24.22.1 (repository pin), npm 11.9.0 (repository pin is 11.16.0), lockfile-pinned Vitest 5.0.3. Checks ran serially with bounded timeouts.

  • node node_modules/vitest/vitest.mjs run src/native/NativeCallObservation.test.ts tests/boundary/providers/native/nativeCallObservation.test.ts tests/boundary/providers/native/lldbRetainedObservations.test.ts tests/boundary/providers/native/nativeCallTargetCleanup.test.ts tests/boundary/providers/native/lldbCallTracerFailures.test.ts --maxWorkers 1 --no-file-parallelism — 68 passed, 5 files.
  • node scripts/run-typescript.mjs --noEmit --checkers 1 --maxMemory 2G — passed.
  • node scripts/verify-module-boundaries.mjs src/native/LldbCallTracer.ts src/native/NativeCallObservation.ts — passed.
  • node scripts/verify-test-discovery.mjs — passed; 2,422 files discovered exactly once.
  • node scripts/verify/architecture-guards.mjs — passed; 2,031 sources.
  • Focused oxlint on all four changed files — no errors, 13 warnings.
  • Focused oxfmt --check and git diff --check — passed.

Initial fixture type errors and an oversized test callback lint error were corrected before these final checks. No full npm run check, full suite/coverage, package verification, real-provider lane or public CLI/MCP end-to-end run was performed. Real debugger behavior and race frequency remain unverified; CI is separate from this local evidence.

Compatibility, safety, and release

No schema migration, package/release metadata change or expanded target authority. Synthetic fixtures exercise production readback/projection/ownership boundaries, not real LLDB. Existing focused tests include inert Node peers. No performance improvement or real-provider verification is claimed.

The API-published commit has different metadata from local reviewed commit d04294d6697ca1a05e120cd007df00a05193ab9d; its complete tree is identical: b35e7fb30b176d8bfbc295664383b02c1fe88a0b. All four public file blob hashes were verified against the reviewed files before opening this draft.

Author readiness

Human owner: @WenyuChiou

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

The human owner confirmed review completion and authorized recording these declarations.

Before merge

  • Required current-head checks and real-provider verification are satisfied or their gaps are explicitly resolved by maintainers.
  • The human owner has completed the readiness declarations.
  • Material scope and authority questions are resolved.

🔄 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/7023 **Author:** [@WenyuChiou](https://github.com/WenyuChiou) **Created:** 10/24/2026 **Status:** ✅ Merged **Merged:** 10/24/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/5913-completed-trace-retention-20261024` --- ### 📝 Commits (1) - [`d7a0a98`](https://github.com/morluto/rea/commit/d7a0a98a870e1da72b445fabec1fb19de09b173e) fix(lldb): retain completed trace facts through cleanup failures ### 📊 Changes **4 files changed** (+314 additions, -25 deletions) <details> <summary>View changed files</summary> 📝 `src/native/LldbCallTracer.ts` (+52 -19) 📝 `src/native/NativeCallObservation.ts` (+9 -5) 📝 `tests/boundary/providers/native/lldbCallTracerFailures.test.ts` (+251 -0) 📝 `tests/boundary/providers/native/nativeCallObservation.test.ts` (+2 -1) </details> ### 📄 Description ## Summary Fixes #5913's remaining completed-trace retention failures during cleanup. The original output-close cancellation case is already covered upstream; this change addresses the two residual cleanup paths described in [the issue follow-up](https://github.com/morluto/rea/issues/5913#issuecomment-6380896456). ## Problem and expected behavior After reading a valid completed LLDB result, process-group cleanup failure or uncertain target termination falls back to journal-only observations. This discards outcome, exit status, elapsed time, launch identity and breakpoints, and replaces final stdout bytes `4096` with the retained `abc` prefix length `3`. Target-only uncertainty also reports `tracer-failure` instead of `cleanup-failure`. Completed observations should survive without treating the producer's termination report as proof of host cleanup. ## Change and scope - Reuse the existing completed-observation projector and share capture readback with the success path. - Keep cleanup failure primary when a capture read also fails; retain sibling captures and other completed facts. - Preserve journal-only fallback for missing or invalid completed results. - Derive limit-outcome wording from the same conservative termination decision as `process.terminated`, avoiding “was killed” when termination is unconfirmed. - Retain cleanup ownership, replacement blocking and retry behavior. This is a routine correction within existing LLDB boundaries, not a new execution or mutation capability; a separate advance maintainer scope decision is not applicable. It does not duplicate #4751's descriptor-close ownership work. ## Contract and boundary impact - Semantic owner: LLDB result readback and native-call observation projection. - CLI/MCP schemas, provider selection, target formats and platform support: unchanged. - Evidence: retain validated completed facts and final counters; keep capture completeness and host cleanup uncertainty explicit. - Target authority and cleanup: unchanged. Producer termination and host confirmation must both hold before reporting termination. - Generated metadata, dependencies, package and installation behavior: unchanged. Expected workflow effects inherited from the existing provider: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [x] 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. The checked effects describe the existing debugger workflow and temporary capture/cleanup files, not new authority. Added regressions use synthetic launcher/cleanup fixtures; no real LLDB or target binary was executed. ## Evidence and regression coverage Executed locally on base `397aa62f2e203bc0f8350634752af0339048e81e` and the reviewed four-file patch: - Before the fix, the clean control passed and both new cleanup regressions failed: completed fields/counters were missing, and target uncertainty had the wrong reason. - An added duration-limit/uncertain-termination regression failed on the false “was killed” note, then passed after the projection correction. - Seven added cases cover clean/group/target-uncertain/duration-limit-uncertain/group-plus-capture-failure paths and missing/invalid-result fallback. Group cleanup also checks replacement blocking, failed close and successful retry. - The existing wording oracle was corrected to exact uncertainty wording while retaining its structured assertions and adding a no-“was killed” assertion; coverage was not weakened. - Full final stdout count remains `4096` while retained text remains `abc`; sibling stderr retains its complete two-byte capture. Capture completeness semantics are unchanged. The original failing wording-oracle log was overwritten by its passing rerun; only a transcript-derived failure excerpt remains. That excerpt is not represented as a preserved raw log. Automated static review found the wording and combined capture-failure gaps above; both were addressed and re-reviewed. This is not human review. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved, with the log limitation disclosed above. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed Linux cloud executor, Node 24.22.1 (repository pin), npm 11.9.0 (repository pin is 11.16.0), lockfile-pinned Vitest 5.0.3. Checks ran serially with bounded timeouts. - `node node_modules/vitest/vitest.mjs run src/native/NativeCallObservation.test.ts tests/boundary/providers/native/nativeCallObservation.test.ts tests/boundary/providers/native/lldbRetainedObservations.test.ts tests/boundary/providers/native/nativeCallTargetCleanup.test.ts tests/boundary/providers/native/lldbCallTracerFailures.test.ts --maxWorkers 1 --no-file-parallelism` — **68 passed, 5 files**. - `node scripts/run-typescript.mjs --noEmit --checkers 1 --maxMemory 2G` — passed. - `node scripts/verify-module-boundaries.mjs src/native/LldbCallTracer.ts src/native/NativeCallObservation.ts` — passed. - `node scripts/verify-test-discovery.mjs` — passed; 2,422 files discovered exactly once. - `node scripts/verify/architecture-guards.mjs` — passed; 2,031 sources. - Focused `oxlint` on all four changed files — no errors, 13 warnings. - Focused `oxfmt --check` and `git diff --check` — passed. Initial fixture type errors and an oversized test callback lint error were corrected before these final checks. No full `npm run check`, full suite/coverage, package verification, real-provider lane or public CLI/MCP end-to-end run was performed. Real debugger behavior and race frequency remain unverified; CI is separate from this local evidence. ## Compatibility, safety, and release No schema migration, package/release metadata change or expanded target authority. Synthetic fixtures exercise production readback/projection/ownership boundaries, not real LLDB. Existing focused tests include inert Node peers. No performance improvement or real-provider verification is claimed. The API-published commit has different metadata from local reviewed commit `d04294d6697ca1a05e120cd007df00a05193ab9d`; its complete tree is identical: `b35e7fb30b176d8bfbc295664383b02c1fe88a0b`. All four public file blob hashes were verified against the reviewed files before opening this draft. ## Author readiness Human owner: @WenyuChiou - [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. The human owner confirmed review completion and authorized recording these declarations. ## Before merge - [ ] Required current-head checks and real-provider verification are satisfied or their gaps are explicitly resolved by maintainers. - [ ] The human owner has completed the readiness declarations. - [ ] Material scope and authority questions are resolved. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-03 13:38:52 +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#7582
No description provided.