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 #2997] [CLOSED] fix(providers): keep failed launches from reporting the version probe output #5547

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

📋 Pull Request Information

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

Base: main ← Head: fix/sigrok-launch-failure-captured-output

📝 Commits (4)

  • f4c04f5 fix(signals): keep a failed launch from reporting the version probe output
  • a23654d fix(captures): keep a failed launch from reporting the version probe output
  • e0db1c5 Merge upstream main into fix/sigrok-launch-failure-captured-output
  • cebd72a fix(wasm): keep a failed wasm2wat launch from reporting wasm-objdump output

📊 Changes

6 files changed (+86 additions, -0 deletions)

View changed files

📝 src/captures/TsharkCaptureProvider.ts (+3 -0)
📝 src/signals/SigrokRecordingProvider.ts (+3 -0)
📝 src/wasm/WabtArtifactProvider.test.ts (+43 -0)
📝 src/wasm/WabtArtifactProvider.ts (+3 -0)
📝 tests/boundary/captures/captureProvider.test.ts (+17 -0)
📝 tests/boundary/signals/recordingProvider.test.ts (+17 -0)

📄 Description

Summary

The sigrok, TShark and WABT providers share one bug. When the main command (sigrok decode or decoder discovery, TShark capture inspection or field discovery, WABT wasm2wat after wasm-objdump) fails to launch after the --version probe succeeded, the resulting error carries the version probe's output as its captured_output. That output is the sigrok-cli 0.7.2 … banner, the version warning and exit_code: 0, so it describes a command that never started.

SigrokRecordingProvider, TsharkCaptureProvider and WabtArtifactProvider each keep one capturedOutput variable for both commands and assigns it only after runOwnedCommand returns. A launcher error thrown before any output (for example a synchronous spawn E2BIG) leaves the probe's value in place, and #failure then attaches it to the final AnalysisOutputError.

No issue is linked: I searched issues and PRs for "E2BIG", "captured output version probe", "stale captured output" and "spawn failure" and found no report. No open PR touches this logic.

Problem and expected behavior

Smallest trigger: a launcher that succeeds for --version and throws spawn E2BIG for the next command. The same thing happens with a real kernel E2BIG: a large inherited environment lets the small version argv fit while a long, budget-valid decoder selector does not. The docs note that "a large inherited environment may still exhaust it".

  • Before: the error's capturedOutput is {"stdout":"sigrok-cli 0.7.2\n\n- libsigrokdecode 0.5.3\n","stderr":"version warning\n","truncated":false,"exit_code":0,"signal":null}, for both decode and discovery.
    TShark capture inspection and field discovery behave the same way, carrying "TShark (Wireshark) …" with exit_code: 0.
  • After: no capturedOutput, because the failed command produced none. The error message still names the launch failure (spawn E2BIG).

Change and scope

In all three providers, execute clears capturedOutput before each command, so captured output always belongs to the most recent command or is absent. Each provider is fixed in its own commit. These are the only providers with a shared captured-output slot (the WABT case came from the Codex review).

Not included: the error's classification. A non-OwnedCommandFailure launch error still becomes AnalysisOutputError. Mapping launch failures to a separate category is a broader contract question I left for maintainers. Bounding the size of captured output, a separate issue, is also not changed here.

Contribution scope: an ordinary evidence-provenance fix within existing boundaries; a maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: execute in src/signals/SigrokRecordingProvider.ts and src/captures/TsharkCaptureProvider.ts and src/wasm/WabtArtifactProvider.ts.
  • Contribution scope fit and linked maintainer decision: in scope; not applicable.
  • CLI and MCP/tool-catalog contract: no schema change; launch failures no longer include another command's captured output.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: captured output is attributed only to the command that produced it.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged; the same commands run with the same limits.
  • 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.

(The launch effect is the provider's existing sigrok invocation; this PR does not add or change any launch.)

Evidence and regression coverage

  • Tests added or updated: tests/boundary/signals/recordingProvider.test.ts and tests/boundary/captures/captureProvider.test.ts each add a launch-failure fixture mode, in which the launcher throws spawn E2BIG for every command except --version. Each adds "does not attribute the version probe's output to a %s command that fails to launch" for decode/discovery and capture/fields respectively. src/wasm/WabtArtifactProvider.test.ts adds "does not attribute wasm-objdump output to a wasm2wat launch failure".
  • Base reproduction: with each provider's change reverted, its two cases fail with expected { …(5) } to be undefined (the version probe's captured output).
  • User-visible CLI/MCP output: not captured separately; this affects only the captured_output of a launch failure.
  • Remaining proof gaps: the committed test injects the launch error; a real-kernel E2BIG reproduction was run separately during investigation but is too host-dependent to commit.

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.

  • npm run build:cached && npx vitest run tests/boundary/signals/recordingProvider.test.ts -t "fails to launch" on the base — both cases fail as quoted.
  • With both fixes, rebased on current main: the signal test files plus tests/boundary/captures and src/captures — 100 passed, 19 skipped (Linux-only cases).
  • npx tsc --noEmit — passed (0 errors).
  • npx oxfmt --check and npx oxlint on both changed files — passed, no errors.
  • npm run verify:module-boundaries — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: macOS with the repository's command-boundary simulator; sigrok-cli itself not installed.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no change to limits, process ownership or cleanup.

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/2997 **Author:** [@Dragolone](https://github.com/Dragolone) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/sigrok-launch-failure-captured-output` --- ### 📝 Commits (4) - [`f4c04f5`](https://github.com/morluto/rea/commit/f4c04f518b097822280beff9be5bf41f4173d625) fix(signals): keep a failed launch from reporting the version probe output - [`a23654d`](https://github.com/morluto/rea/commit/a23654d193de4d29b5555e64985be36041943b98) fix(captures): keep a failed launch from reporting the version probe output - [`e0db1c5`](https://github.com/morluto/rea/commit/e0db1c576110fd1e29e63411e29ab4f54566d15b) Merge upstream main into fix/sigrok-launch-failure-captured-output - [`cebd72a`](https://github.com/morluto/rea/commit/cebd72a2e7deea89906821f1d6d7df2dae31e744) fix(wasm): keep a failed wasm2wat launch from reporting wasm-objdump output ### 📊 Changes **6 files changed** (+86 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/captures/TsharkCaptureProvider.ts` (+3 -0) 📝 `src/signals/SigrokRecordingProvider.ts` (+3 -0) 📝 `src/wasm/WabtArtifactProvider.test.ts` (+43 -0) 📝 `src/wasm/WabtArtifactProvider.ts` (+3 -0) 📝 `tests/boundary/captures/captureProvider.test.ts` (+17 -0) 📝 `tests/boundary/signals/recordingProvider.test.ts` (+17 -0) </details> ### 📄 Description ## Summary The sigrok, TShark and WABT providers share one bug. When the main command (sigrok decode or decoder discovery, TShark capture inspection or field discovery, WABT `wasm2wat` after `wasm-objdump`) fails to launch after the `--version` probe succeeded, the resulting error carries the version probe's output as its `captured_output`. That output is the `sigrok-cli 0.7.2 …` banner, the version warning and `exit_code: 0`, so it describes a command that never started. `SigrokRecordingProvider`, `TsharkCaptureProvider` and `WabtArtifactProvider` each keep one `capturedOutput` variable for both commands and assigns it only after `runOwnedCommand` returns. A launcher error thrown before any output (for example a synchronous `spawn E2BIG`) leaves the probe's value in place, and `#failure` then attaches it to the final `AnalysisOutputError`. No issue is linked: I searched issues and PRs for "E2BIG", "captured output version probe", "stale captured output" and "spawn failure" and found no report. No open PR touches this logic. ## Problem and expected behavior Smallest trigger: a launcher that succeeds for `--version` and throws `spawn E2BIG` for the next command. The same thing happens with a real kernel `E2BIG`: a large inherited environment lets the small version argv fit while a long, budget-valid decoder selector does not. The docs note that "a large inherited environment may still exhaust it". - Before: the error's `capturedOutput` is `{"stdout":"sigrok-cli 0.7.2\n\n- libsigrokdecode 0.5.3\n","stderr":"version warning\n","truncated":false,"exit_code":0,"signal":null}`, for both decode and discovery. TShark capture inspection and field discovery behave the same way, carrying `"TShark (Wireshark) …"` with `exit_code: 0`. - After: no `capturedOutput`, because the failed command produced none. The error message still names the launch failure (`spawn E2BIG`). ## Change and scope In all three providers, `execute` clears `capturedOutput` before each command, so captured output always belongs to the most recent command or is absent. Each provider is fixed in its own commit. These are the only providers with a shared captured-output slot (the WABT case came from the Codex review). Not included: the error's classification. A non-`OwnedCommandFailure` launch error still becomes `AnalysisOutputError`. Mapping launch failures to a separate category is a broader contract question I left for maintainers. Bounding the size of captured output, a separate issue, is also not changed here. Contribution scope: an ordinary evidence-provenance fix within existing boundaries; a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `execute` in `src/signals/SigrokRecordingProvider.ts` and `src/captures/TsharkCaptureProvider.ts` and `src/wasm/WabtArtifactProvider.ts`. - Contribution scope fit and linked maintainer decision: in scope; not applicable. - CLI and MCP/tool-catalog contract: no schema change; launch failures no longer include another command's captured output. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: captured output is attributed only to the command that produced it. - Target selection, authority, upstream behavior, and cleanup details (if applicable): unchanged; the same commands run with the same limits. - 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. - [x] 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 launch effect is the provider's existing sigrok invocation; this PR does not add or change any launch.) ## Evidence and regression coverage - Tests added or updated: `tests/boundary/signals/recordingProvider.test.ts` and `tests/boundary/captures/captureProvider.test.ts` each add a `launch-failure` fixture mode, in which the launcher throws `spawn E2BIG` for every command except `--version`. Each adds "does not attribute the version probe's output to a %s command that fails to launch" for `decode`/`discovery` and `capture`/`fields` respectively. `src/wasm/WabtArtifactProvider.test.ts` adds "does not attribute wasm-objdump output to a wasm2wat launch failure". - Base reproduction: with each provider's change reverted, its two cases fail with `expected { …(5) } to be undefined` (the version probe's captured output). - User-visible CLI/MCP output: not captured separately; this affects only the `captured_output` of a launch failure. - Remaining proof gaps: the committed test injects the launch error; a real-kernel `E2BIG` reproduction was run separately during investigation but is too host-dependent to commit. 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. - `npm run build:cached && npx vitest run tests/boundary/signals/recordingProvider.test.ts -t "fails to launch"` on the base — both cases fail as quoted. - With both fixes, rebased on current `main`: the signal test files plus `tests/boundary/captures` and `src/captures` — 100 passed, 19 skipped (Linux-only cases). - `npx tsc --noEmit` — passed (0 errors). - `npx oxfmt --check` and `npx oxlint` on both changed files — passed, no errors. - `npm run verify:module-boundaries` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: macOS with the repository's command-boundary simulator; sigrok-cli itself not installed. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no change to limits, process ownership or cleanup. ## 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:07:29 +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#5547
No description provided.