[PR #4406] [MERGED] fix(browser): preserve cleanup failure diagnostics #6217

New issue

Closed

opened 2026-10-31 01:12:46 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:12:46 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4406
Author: @N0zoM1z0
Created: 10/16/2026
Status: ✅ Merged
Merged: 10/16/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/browser-cleanup-diagnostics-4403

---

📝 Commits (2)

• 267aa22 fix(browser): preserve cleanup failure diagnostics
• 690c2e5 test(browser): align cleanup diagnostics with owner observations

📊 Changes

4 files changed (+202 additions, -58 deletions)

View changed files

📝 src/browser/PlaywrightElectronActiveProvider.test.ts (+92 -21)
📝 src/browser/PlaywrightElectronActiveProvider.ts (+10 -17)
📝 src/domain/analysisErrorProjection.ts (+24 -20)
📝 tests/conformance/contracts/analysisErrorProjection.test.ts (+76 -0)

📄 Description

Summary

Fixes #4403. Refs #4227 and #4282.

A completed Linux Electron capture could return cleanup_incomplete with execution_failure: unreadable_output and a generic cleanup reason, hiding the observer’s actual failure. Preserve the unavailable-lineage reason, distinguish an unobserved lineage, and classify cleanup failure as execution_failure. Direct typed observation failures now retain primary_reason, matching aggregated failures.

Change and scope

The Electron cleanup owner handles unavailable lineage once across platforms, preserving existing termination decisions and root-cleanup failures. The shared error projection uses an exhaustive browser-reason map, removing the misleading default for future reasons. CLI and MCP continue using that single projection; schemas and Evidence retention are unchanged.

Ordinary correction within existing authority; maintainer scope decision not applicable. Marker-erasing Chromium helper ownership remains unverified (#4282); #4346 separately addresses the Linux exit race. No new cleanup authority or recovery operation.

Contract and boundary impact

• Semantic owners: Electron process cleanup and shared analysis-error projection.
• CLI/MCP: existing cleanup_incomplete, cleanup_reason, execution_failure, and primary_reason fields; readable retained observations are not labeled unreadable.
• Evidence/provenance: completed actions and runtime observations remain in partial_observation; resource identities and uncertainty remain visible.
• Provider/platform: real Linux Electron 44.7.0; Windows cleanup decisions exercised through its narrow injected host, not a real Windows runtime.
• Target selection, permissions, instrumentation, package metadata and installation: unchanged.

Evidence and regression coverage

• On base 2c7583599b9ac1c847bd77b1940930fd8d4594c7, seven new regression cases failed; verified cleanup and existing contract controls passed.
• Review follow-up: reproduced the two stale colocated assertions locally and in the initial Source tests CI log. Updated the existing owner tests, injected the unavailable observation to remove dependence on a host PID, consolidated duplicate cleanup tests, and added unobserved-lineage and root/descendant termination-failure controls. Production code and real-provider measurements are unchanged by this test-only follow-up. Latest-head CI (690c2e5d29) passed: 25 successful / 12 intentionally skipped checks. Codex re-review found no remaining findings; Greptile 5/5; both review threads resolved.
• Real stdio MCP + official Electron in a disposable Ubuntu 24.04 container with authenticated Xvfb: all three actions completed and the IPC file effect was checked independently. The unrelated marked process survived. Capture still returns cleanup_incomplete, now with the observer’s specific reason and execution_failure: execution_failure.
• Direct and AggregateError-wrapped cancellation, timeout and disconnection retain their typed primary reasons. Unavailable/unobserved lineage never authorizes Windows termination; verified cleanup and termination errors retain their prior outcomes.
• 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:focused -- src/browser/PlaywrightElectronActiveProvider.test.ts src/domain/analysisErrorProjection.test.ts tests/conformance/contracts/analysisErrorProjection.test.ts tests/boundary/process/electronLaunchRejections.test.ts tests/process-global/browserScenarioCleanup.test.ts tests/boundary/mcp/toolResult.test.ts — 108 passed across six files.
• npm run check:fast — typecheck and lint passed after review changes; final source rerun (the two owner files + conformance contract) passed 71 tests.
• npm run docs:check — generated documentation/schema/license checks and five README tests passed.
• git diff --cached --check — passed.
• Real stdio MCP/Electron probe plus two paired runs per revision — expected incomplete cleanup, precise diagnostics, completed actions/file effect, and unaffected control verified.

Performance: base/fixed medians across two equivalent fresh-process/profile captures were 8.28/7.99 s elapsed, 7.75/7.34 s CPU, and 1.24/1.26 GiB sampled family RSS. Input + full MCP-result proxy (o200k_base) was 8,257/8,273 tokens; the additional 16 tokens carry the restored diagnostic. No speedup claim from two runs. Node compile cache disabled, OS cache uncontrolled/warm; actual agent billing, initialization traffic and Xvfb/container baseline are unmeasured. Container capped at 4 GiB/two CPUs; heavy local checks ran serially, maximum sampled passing check RSS 4.45 GiB.

No real Windows/macOS claim. Successful cleanup of marker-erasing Linux helpers remains unproven and is not a claim of this PR. Raw local logs and full responses are retained under /tmp/rea-4403-browser-cleanup-20261016/.

Author readiness

Human owner: @N0zoM1z0

The human owner explicitly authorized delegated review, proxy completion of these declarations, ready publication and normal merge. The agent reviewed the diff and evidence; these declarations record that delegation and do not assert a separate manual review.

• I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
• I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
• I declare this PR ready for initial maintainer review.

Before merge

• This PR addresses a concrete problem or an agreed enhancement.
• Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
• The PR has one focused outcome and the title follows type(scope): outcome.
• Related issue is linked, or the reason for not linking one is stated above.
• Tests cover changed observable behavior and meaningful failure paths.
• Owning docs, contracts, and generated metadata are updated where needed.
• User-visible CLI/MCP changes include representative output.
• I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

---

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/4406 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/16/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/browser-cleanup-diagnostics-4403` --- ### 📝 Commits (2) - [`267aa22`](https://github.com/morluto/rea/commit/267aa22cce7f7b7174dcdb7756d773eec50fe3af) fix(browser): preserve cleanup failure diagnostics - [`690c2e5`](https://github.com/morluto/rea/commit/690c2e5d29dd71332b8e4ee32869bbd70cf438c1) test(browser): align cleanup diagnostics with owner observations ### 📊 Changes **4 files changed** (+202 additions, -58 deletions) <details> <summary>View changed files</summary> 📝 `src/browser/PlaywrightElectronActiveProvider.test.ts` (+92 -21) 📝 `src/browser/PlaywrightElectronActiveProvider.ts` (+10 -17) 📝 `src/domain/analysisErrorProjection.ts` (+24 -20) 📝 `tests/conformance/contracts/analysisErrorProjection.test.ts` (+76 -0) </details> ### 📄 Description ## Summary Fixes #4403. Refs #4227 and #4282. A completed Linux Electron capture could return `cleanup_incomplete` with `execution_failure: unreadable_output` and a generic cleanup reason, hiding the observer’s actual failure. Preserve the unavailable-lineage reason, distinguish an unobserved lineage, and classify cleanup failure as `execution_failure`. Direct typed observation failures now retain `primary_reason`, matching aggregated failures. ## Change and scope The Electron cleanup owner handles unavailable lineage once across platforms, preserving existing termination decisions and root-cleanup failures. The shared error projection uses an exhaustive browser-reason map, removing the misleading default for future reasons. CLI and MCP continue using that single projection; schemas and Evidence retention are unchanged. Ordinary correction within existing authority; maintainer scope decision not applicable. Marker-erasing Chromium helper ownership remains unverified (#4282); #4346 separately addresses the Linux exit race. No new cleanup authority or recovery operation. ## Contract and boundary impact - Semantic owners: Electron process cleanup and shared analysis-error projection. - CLI/MCP: existing `cleanup_incomplete`, `cleanup_reason`, `execution_failure`, and `primary_reason` fields; readable retained observations are not labeled unreadable. - Evidence/provenance: completed actions and runtime observations remain in `partial_observation`; resource identities and uncertainty remain visible. - Provider/platform: real Linux Electron 44.7.0; Windows cleanup decisions exercised through its narrow injected host, not a real Windows runtime. - Target selection, permissions, instrumentation, package metadata and installation: unchanged. ## Evidence and regression coverage - On base `2c7583599b9ac1c847bd77b1940930fd8d4594c7`, seven new regression cases failed; verified cleanup and existing contract controls passed. - Review follow-up: reproduced the two stale colocated assertions locally and in the initial Source tests CI log. Updated the existing owner tests, injected the unavailable observation to remove dependence on a host PID, consolidated duplicate cleanup tests, and added unobserved-lineage and root/descendant termination-failure controls. Production code and real-provider measurements are unchanged by this test-only follow-up. Latest-head CI (690c2e5d29dd) passed: 25 successful / 12 intentionally skipped checks. Codex re-review found no remaining findings; Greptile 5/5; both review threads resolved. - Real stdio MCP + official Electron in a disposable Ubuntu 24.04 container with authenticated Xvfb: all three actions completed and the IPC file effect was checked independently. The unrelated marked process survived. Capture still returns `cleanup_incomplete`, now with the observer’s specific reason and `execution_failure: execution_failure`. - Direct and AggregateError-wrapped cancellation, timeout and disconnection retain their typed primary reasons. Unavailable/unobserved lineage never authorizes Windows termination; verified cleanup and termination errors retain their prior outcomes. - [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:focused -- src/browser/PlaywrightElectronActiveProvider.test.ts src/domain/analysisErrorProjection.test.ts tests/conformance/contracts/analysisErrorProjection.test.ts tests/boundary/process/electronLaunchRejections.test.ts tests/process-global/browserScenarioCleanup.test.ts tests/boundary/mcp/toolResult.test.ts` — 108 passed across six files. - `npm run check:fast` — typecheck and lint passed after review changes; final source rerun (the two owner files + conformance contract) passed 71 tests. - `npm run docs:check` — generated documentation/schema/license checks and five README tests passed. - `git diff --cached --check` — passed. - Real stdio MCP/Electron probe plus two paired runs per revision — expected incomplete cleanup, precise diagnostics, completed actions/file effect, and unaffected control verified. Performance: base/fixed medians across two equivalent fresh-process/profile captures were 8.28/7.99 s elapsed, 7.75/7.34 s CPU, and 1.24/1.26 GiB sampled family RSS. Input + full MCP-result proxy (`o200k_base`) was 8,257/8,273 tokens; the additional 16 tokens carry the restored diagnostic. No speedup claim from two runs. Node compile cache disabled, OS cache uncontrolled/warm; actual agent billing, initialization traffic and Xvfb/container baseline are unmeasured. Container capped at 4 GiB/two CPUs; heavy local checks ran serially, maximum sampled passing check RSS 4.45 GiB. No real Windows/macOS claim. Successful cleanup of marker-erasing Linux helpers remains unproven and is not a claim of this PR. Raw local logs and full responses are retained under `/tmp/rea-4403-browser-cleanup-20261016/`. ## Author readiness Human owner: @N0zoM1z0 The human owner explicitly authorized delegated review, proxy completion of these declarations, ready publication and normal merge. The agent reviewed the diff and evidence; these declarations record that delegation and do not assert a separate manual review. - [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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:12:46 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-01 21:46:36 +00:00

[PR #6298] [MERGED] fix(process): propagate comparison contradictions #7265

bsakaguchi referenced this issue 2026-11-01 21:46:39 +00:00

[PR #6307] test(correlation): cover contradictory findings and retained evidence #7271

bsakaguchi referenced this issue 2026-11-03 13:39:11 +00:00

[PR #7076] [MERGED] fix(artifacts): preserve integrity contradictions for one-sided members #7624

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

Subscribe

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#6217

No description provided.