[PR #5384] [CLOSED] fix(verify): compare dsh lane evidence against the resolved target path #6914

New issue

Closed

opened 2026-11-01 21:44:01 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:44:01 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5384
Author: @kittimzhe
Created: 10/20/2026
Status: ❌ Closed

Base: main ← Head: fix/verify-client-macos-realpath

---

📝 Commits (1)

• dffcb78 fix(verify): compare dsh lane evidence against the resolved target path

📊 Changes

1 file changed (+13 additions, -2 deletions)

View changed files

📝 scripts/verify-deepseek-client.mjs (+13 -2)

📄 Description

Summary

npm run verify:deepseek-client fails on macOS at the Evidence identity assertion: the lane asserts evidence.subject.local_path === target, but the analyzer resolves its input through realpath before recording Evidence (resolveSelectedInput in src/application/javascript/JavaScriptArtifactReconstruction.ts), and the macOS tmpdir() prefix is a symlink (/var/folders/... → /private/var/folders/...). The lane completes the entire lifecycle — setup, idempotent setup, doctor, headless chat, skill load, full tool catalog, real analyze_javascript_application execution — and then dies comparing two spellings of the same path. The lane's expectation was the only wrong side; the analyzer's resolved-path recording is correct and enforced upstream by assertApplicationSubject. The assertion now compares against the resolved path.

Problem and expected behavior

• Smallest trigger: run the lane on macOS with a dsh CLI that supports --profile headless --json (verified with 0.2.1-rc.2).
• Violated invariant: a verification lane must verify what the client actually records, not a spelling the caller used. Evidence records the resolved identity of what was analyzed; the lane compared it to the unresolved caller-facing path.
• Expected: the lane passes on macOS. The same failure was reported in the #4402 discussion (unmodified main, macOS): "The lane still ends passed: false on a macOS-only /private/var versus /var mismatch in its local_path assertion". No dedicated issue exists; that comment is the closest report.

Change and scope

• const resolvedTarget = await realpath(target) computed once after the fixture directories exist; the assertion compares against it.
• The caller-facing input_path sent to the tool and the prompt text keep the original unresolved path, so the lane still covers the symlink-resolution step end to end.
• The same pattern (assert.equal(evidence.subject.local_path, target) over a mkdtemp(tmpdir(), ...) target) exists in the other client lanes (claude, gemini, grok, copilot, qwen, omp, opencode, commandcode, native-agent). Only the deepseek lane is executable on this machine (the only client CLI installed here), so this PR fixes the lane it can verify and leaves the identical mechanical change in the others to maintainer direction.
• Contribution scope: verification tooling fix within existing boundaries — no maintainer scope decision required ("not applicable").

Contract and boundary impact

• Semantic owner and earliest changed stage: the verification lane's expectation in scripts/; no runtime code touched.
• CLI and MCP/tool-catalog contract: none.
• Provider, bridge, target-format, or platform compatibility: none.
• Evidence, artifact, provenance contract: none — the analyzer's resolved-path recording is unchanged.
• Generated metadata: none.

Expected effects:

• Read existing files or captured data. (the lane reads its own lab fixtures; its process launches — local model fixture, dsh headless — are pre-existing behavior unchanged by this PR)
• 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

• RED (before, same revision): lifecycle reached ["dry-run","setup","idempotent-setup","doctor"], the real analysis completed (analyze_javascript_application, ~1.1 s, status ok), Evidence was recorded, and the lane failed with AssertionError: '+ /private/var/folders/.../fixture α测试' - '/var/folders/.../fixture α测试' — the exact mismatch reported in the #4402 discussion.
• GREEN (after): lifecycle ["dry-run","setup","idempotent-setup","doctor","native-tool-invocation","uninstall"], receipt passed: true, exit 0.
• Tests: the lane is the verification artifact itself; scripts/ has no colocated unit tests to update.
• Remaining proof gaps: the other nine client lanes were not executed (no CLIs installed on this machine); Windows is out of scope (the lane asserts non-win32).

For evidence-bearing changes:

• Observed, derived, and inferred claims remain distinguishable. (RED/GREEN runs are executed; the other-lane pattern is source-derived and labeled as such)
• Artifact identity, source provenance, and failed attempts remain preserved.
• Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

• npm ci — locked dependencies, Node 24.18.0 (.nvmrc), macOS 14 arm64.
• npm run verify:deepseek-client (before the fix) — fails at the Evidence local_path assertion after completing setup, idempotent setup, doctor, headless chat, skill load, catalog validation, and the real analysis.
• npm run verify:deepseek-client (after the fix) — passes: full lifecycle through native-tool-invocation and uninstall, receipt passed: true.
• npm run check:fast — typecheck + lint pass (uncached).
• Environment notes for other macOS contributors: the lane needs (1) a dsh CLI with headless JSON mode (REA_VERIFY_DEEPSEEK_COMMAND can point at a local install; the 0.1.5-rc.3 on this machine predates --profile headless --json), and (2) a working Swift toolchain for the Darwin ownership helper — stock CLT 16.2 on macOS 14 ships duplicate SwiftBridging definitions in usr/include/swift/module.modulemap and bridging.modulemap that break every import Foundation compile; removing the duplicate block from module.modulemap restores it. Both were local environment fixes, stated here because they are undeclared prerequisites of the lane.

Compatibility, safety, and release

• Breaking changes or migration steps: none — verification script only.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable; the lane's local model fixture is unchanged.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: none.

Author readiness

Human owner: @kittimzhe

• 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. (no dedicated issue; the failure report in the #4402 discussion is cited in Problem)
• Tests cover changed observable behavior and meaningful failure paths. (the lane itself is the executable check; RED/GREEN receipts recorded above)
• Owning docs, contracts, and generated metadata are updated where needed. (no docs describe the lane's assertion internals)
• User-visible CLI/MCP changes include representative output. (verification tooling only; the RED/GREEN receipts are included above)
• 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/5384 **Author:** [@kittimzhe](https://github.com/kittimzhe) **Created:** 10/20/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/verify-client-macos-realpath` --- ### 📝 Commits (1) - [`dffcb78`](https://github.com/morluto/rea/commit/dffcb788b6a745729dc60030d9648f2d10f76891) fix(verify): compare dsh lane evidence against the resolved target path ### 📊 Changes **1 file changed** (+13 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `scripts/verify-deepseek-client.mjs` (+13 -2) </details> ### 📄 Description ## Summary `npm run verify:deepseek-client` fails on macOS at the Evidence identity assertion: the lane asserts `evidence.subject.local_path === target`, but the analyzer resolves its input through `realpath` before recording Evidence (`resolveSelectedInput` in `src/application/javascript/JavaScriptArtifactReconstruction.ts`), and the macOS `tmpdir()` prefix is a symlink (`/var/folders/...` → `/private/var/folders/...`). The lane completes the entire lifecycle — setup, idempotent setup, doctor, headless chat, skill load, full tool catalog, real `analyze_javascript_application` execution — and then dies comparing two spellings of the same path. The lane's expectation was the only wrong side; the analyzer's resolved-path recording is correct and enforced upstream by `assertApplicationSubject`. The assertion now compares against the resolved path. ## Problem and expected behavior - Smallest trigger: run the lane on macOS with a dsh CLI that supports `--profile headless --json` (verified with 0.2.1-rc.2). - Violated invariant: a verification lane must verify what the client actually records, not a spelling the caller used. Evidence records the resolved identity of what was analyzed; the lane compared it to the unresolved caller-facing path. - Expected: the lane passes on macOS. The same failure was reported in the #4402 discussion (unmodified main, macOS): "The lane still ends passed: false on a macOS-only /private/var versus /var mismatch in its local_path assertion". No dedicated issue exists; that comment is the closest report. ## Change and scope - `const resolvedTarget = await realpath(target)` computed once after the fixture directories exist; the assertion compares against it. - The caller-facing `input_path` sent to the tool and the prompt text keep the original unresolved path, so the lane still covers the symlink-resolution step end to end. - The same pattern (`assert.equal(evidence.subject.local_path, target)` over a `mkdtemp(tmpdir(), ...)` target) exists in the other client lanes (claude, gemini, grok, copilot, qwen, omp, opencode, commandcode, native-agent). Only the deepseek lane is executable on this machine (the only client CLI installed here), so this PR fixes the lane it can verify and leaves the identical mechanical change in the others to maintainer direction. - Contribution scope: verification tooling fix within existing boundaries — no maintainer scope decision required ("not applicable"). ## Contract and boundary impact - Semantic owner and earliest changed stage: the verification lane's expectation in `scripts/`; no runtime code touched. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance contract: none — the analyzer's resolved-path recording is unchanged. - Generated metadata: none. Expected effects: - [x] Read existing files or captured data. *(the lane reads its own lab fixtures; its process launches — local model fixture, dsh headless — are pre-existing behavior unchanged by this PR)* - [ ] 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 - RED (before, same revision): lifecycle reached `["dry-run","setup","idempotent-setup","doctor"]`, the real analysis completed (`analyze_javascript_application`, ~1.1 s, status ok), Evidence was recorded, and the lane failed with `AssertionError: '+ /private/var/folders/.../fixture α测试' - '/var/folders/.../fixture α测试'` — the exact mismatch reported in the #4402 discussion. - GREEN (after): lifecycle `["dry-run","setup","idempotent-setup","doctor","native-tool-invocation","uninstall"]`, receipt `passed: true`, exit 0. - Tests: the lane is the verification artifact itself; `scripts/` has no colocated unit tests to update. - Remaining proof gaps: the other nine client lanes were not executed (no CLIs installed on this machine); Windows is out of scope (the lane asserts non-win32). For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. *(RED/GREEN runs are executed; the other-lane pattern is source-derived and labeled as such)* - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm ci` — locked dependencies, Node 24.18.0 (`.nvmrc`), macOS 14 arm64. - `npm run verify:deepseek-client` (before the fix) — fails at the Evidence `local_path` assertion after completing setup, idempotent setup, doctor, headless chat, skill load, catalog validation, and the real analysis. - `npm run verify:deepseek-client` (after the fix) — passes: full lifecycle through `native-tool-invocation` and `uninstall`, receipt `passed: true`. - `npm run check:fast` — typecheck + lint pass (uncached). - Environment notes for other macOS contributors: the lane needs (1) a dsh CLI with headless JSON mode (`REA_VERIFY_DEEPSEEK_COMMAND` can point at a local install; the 0.1.5-rc.3 on this machine predates `--profile headless --json`), and (2) a working Swift toolchain for the Darwin ownership helper — stock CLT 16.2 on macOS 14 ships duplicate `SwiftBridging` definitions in `usr/include/swift/module.modulemap` and `bridging.modulemap` that break every `import Foundation` compile; removing the duplicate block from `module.modulemap` restores it. Both were local environment fixes, stated here because they are undeclared prerequisites of the lane. ## Compatibility, safety, and release - Breaking changes or migration steps: none — verification script only. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; the lane's local model fixture is unchanged. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @kittimzhe - [ ] 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. - [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. *(no dedicated issue; the failure report in the #4402 discussion is cited in Problem)* - [x] Tests cover changed observable behavior and meaningful failure paths. *(the lane itself is the executable check; RED/GREEN receipts recorded above)* - [x] Owning docs, contracts, and generated metadata are updated where needed. *(no docs describe the lane's assertion internals)* - [ ] User-visible CLI/MCP changes include representative output. *(verification tooling only; the RED/GREEN receipts are included above)* - [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-11-01 21:44:01 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-03 00:29:32 +00:00

[GH-ISSUE #3796] [Tracker] Open feature requests by area (October 2026) #1471

bsakaguchi referenced this issue 2026-11-03 00:29:32 +00:00

[GH-ISSUE #5653] [Tracker] New issue intake by area (October 2026) #3423

bsakaguchi referenced this issue 2026-11-03 07:16:59 +00:00

[GH-ISSUE #7522] [Bug] Automatic setup selects Grok Bot even though its connector requires manual registration #4469

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

[PR #7004] feat(doctor): report the configured workflow beside an audit-wide result #7566

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

No description provided.