[PR #2451] [CLOSED] test(agent): grade notes export facts against produced evidence #5239

New issue

Closed

opened 2026-10-31 01:05:03 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:05:03 +00:00

Owner

Copy link

📋 Pull Request Information

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

Base: main ← Head: test/notes-export-factual-rubric

---

📝 Commits (3)

• fde35be test(agent): add evidence-backed notes export rubric
• 193f58b Add notes-export analysis task to verify-agent-experience
• 9240420 Add tests for Notes export known-answer evaluation

📊 Changes

3 files changed (+485 additions, -12 deletions)

View changed files

📝 scripts/verify-agent-experience.mjs (+12 -0)
📝 src/evaluation/AgentEvaluationFixtures.ts (+145 -12)
📝 tests/boundary/mcp/agentKnownAnswerMcp.test.ts (+328 -0)

📄 Description

Summary

The Notes export scenario proposed in #1704 checks tool order, answer terms and a produced Evidence ID, but those checks do not establish that the selected facts are correct or supported. Add a guided notes-export scenario with six closed claims checked against fixture expectations and the actual delivered producer Evidence. Refs #1704 and #778.

Problem and expected behavior

A reply containing notes:export and an existing Evidence ID can still give an incorrect API, cite another operation or target, or erase a semantic unknown. The factual gate now requires the exposed API, renderer/main IPC operations, resolved preload, feature-trace source-module set and semantic-query boundary to match their supporting Evidence.

Change and scope

Reuse KnownAnswerEvaluation and the existing source-owned six-file Notes example. Package it as ASAR and independently hash its bytes in the shared fixture factory. Bind analysis claims to the intended path/digest and derived claims to delivered parent analysis, operation, authority/confidence and query semantics.

The channel query accepts REA's effective default exact match as well as explicit exact; a real agent trial exposed the initial overly strict parameter comparison. Contains matching remains rejected. Shared bridge assertions and answer descriptions serve both existing ASAR and Notes fixtures.

This is a three-file evaluation contribution directly against main. #1704 remains open at 7dfd2b6d; its website/demo portfolio is not included here. Its author will need to reconcile the overlapping scenario entry if both PRs proceed.

Contract and boundary impact

• Semantic owner: source-owned evaluation fixtures, selected-fact rubric and verifier scenario.
• Scope decision: not applicable to this change within existing static-analysis/evaluation boundaries.
• CLI/MCP, tool catalog, provider behavior and Evidence schemas: unchanged.
• Target/lifecycle: static analysis of owned packaged bytes; existing MCP harness and isolated verifier cleanup. Electron is not launched.
• Generated metadata, installation and package distribution: unchanged; generated outputs and raw records are excluded from the diff.

Expected effects:

• Read existing files or captured data.
• Launch existing REA/agent verifier processes.
• Create owned fixture/archive files and temporary isolated client configuration.
• Contact the existing model service during the optional live agent verifier.
• No target execution, instrumentation, mutation or protection recovery is added.

Evidence and regression coverage

Two public MCP workflow regressions exercise actual Notes analysis, feature trace and semantic trace. They accept supported claims and reject incorrect values, erased ambiguity, unrelated existing citations, missing parent Evidence, unsupported extra runtime claims, keyword-only prose, contains queries, another artifact path and changed bytes at the same path. The default exact query is explicitly accepted.

Source/module expectations are established from the owned fixture. The semantic claim checks the bounded static-query contract. The module list is the trace's returned source-module set; it is not proof that every module executed.

Validation performed

Windows x64, Node.js 24.18.0 and npm 11.16.0; source baseline ca2d15b3.

• npm ci, npm run build:cached — passed.
• npm run test:focused -- tests/boundary/mcp/agentKnownAnswerMcp.test.ts tests/evaluation/model-evals/knownAnswerEvaluation.test.ts tests/evaluation/model-evals/codexAgentEval.test.ts tests/evaluation/model-evals/agentEvaluationReport.test.ts — 4 files / 69 tests passed.
• npm run check — passed, including typecheck, lint, format, knip, metadata and architecture guards.
• npm run jscpd — passed, 2.98% duplicated lines.
• npm run verify:test-discovery — all 1,004 files discovered exactly once.
• git diff --check — passed.
• Real stdio MCP probe — all three static operations completed against packaged Notes bytes. Windows native controls came from the verified published 6.4.0 artifact; the source checkout itself does not build that addon on Windows.
• Live isolated REA_AGENT_EVAL_SCENARIOS=notes-export npm run verify:agent with Codex CLI 0.161.0 completed three successful REA calls, no invalid or repeated calls, and correct six-claim JSON. The original command's factual gate failed only on omitted match (REA's default exact). After fixing that interpretation, the unchanged original transcript was regraded with an independently regenerated fixture digest: six claims and the existing gate passed. This is replayed grading of that original execution, not a fresh post-fix model run. The original failed report and raw transcript remain local.

The packaged fixture SHA-256 is a8f3fe3170ca3332e6bc4708c9cdcb07ce69c01433694d8b26a43636323cc07c; the original transcript SHA-256 is 0939640bfb0bbc40d53ced38333cbf3666873b73451d463eeb581163c24e3781. An earlier attempt with the installed Codex CLI 0.154.0 did not start a model task because it lacks --no-daemon.

Compatibility, safety, and release

This guided fixture does not grade arbitrary free-form factual correctness, autonomous IPC discovery, CSV formatter correctness, actual Downloads resolution or runtime clicks/writes. It adds no AISOP/AISP runtime or dependency. No performance advantage is claimed: the one live trial reported 298,309 input tokens (231,552 cached) and 1,119 output tokens; CPU, peak process-family memory and model identity were not independently established.

Existing public contracts and historical ASAR/parser rubrics are preserved. Linux/macOS model workflows, Electron runtime execution and the full local check:pr suite were not run. CI and maintainer review remain pending.

Before merge

• One focused evaluation outcome and conventional title.
• Existing related work and overlap are identified.
• Changed behavior and meaningful failure paths are covered.
• Observed, derived, inferred and unknown boundaries remain explicit.
• Final diff excludes credentials, generated files, raw records and unrelated cleanup.
• Maintainer review and current-head CI complete.

---

_{🔄 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/2451 **Author:** [@optimization2026](https://github.com/optimization2026) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `test/notes-export-factual-rubric` --- ### 📝 Commits (3) - [`fde35be`](https://github.com/morluto/rea/commit/fde35be10ade0bbcb12cc8409b8e9e9af632cb43) test(agent): add evidence-backed notes export rubric - [`193f58b`](https://github.com/morluto/rea/commit/193f58bb4449fd2223c1e2aea40ce17072e0ef5b) Add notes-export analysis task to verify-agent-experience - [`9240420`](https://github.com/morluto/rea/commit/92404209a458c6e9c15ecd821ab51160be78ee57) Add tests for Notes export known-answer evaluation ### 📊 Changes **3 files changed** (+485 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `scripts/verify-agent-experience.mjs` (+12 -0) 📝 `src/evaluation/AgentEvaluationFixtures.ts` (+145 -12) 📝 `tests/boundary/mcp/agentKnownAnswerMcp.test.ts` (+328 -0) </details> ### 📄 Description ## Summary The Notes export scenario proposed in #1704 checks tool order, answer terms and a produced Evidence ID, but those checks do not establish that the selected facts are correct or supported. Add a guided `notes-export` scenario with six closed claims checked against fixture expectations and the actual delivered producer Evidence. Refs #1704 and #778. ## Problem and expected behavior A reply containing `notes:export` and an existing Evidence ID can still give an incorrect API, cite another operation or target, or erase a semantic unknown. The factual gate now requires the exposed API, renderer/main IPC operations, resolved preload, feature-trace source-module set and semantic-query boundary to match their supporting Evidence. ## Change and scope Reuse `KnownAnswerEvaluation` and the existing source-owned six-file Notes example. Package it as ASAR and independently hash its bytes in the shared fixture factory. Bind analysis claims to the intended path/digest and derived claims to delivered parent analysis, operation, authority/confidence and query semantics. The channel query accepts REA's effective default exact match as well as explicit exact; a real agent trial exposed the initial overly strict parameter comparison. Contains matching remains rejected. Shared bridge assertions and answer descriptions serve both existing ASAR and Notes fixtures. This is a three-file evaluation contribution directly against main. #1704 remains open at `7dfd2b6d`; its website/demo portfolio is not included here. Its author will need to reconcile the overlapping scenario entry if both PRs proceed. ## Contract and boundary impact - Semantic owner: source-owned evaluation fixtures, selected-fact rubric and verifier scenario. - Scope decision: not applicable to this change within existing static-analysis/evaluation boundaries. - CLI/MCP, tool catalog, provider behavior and Evidence schemas: unchanged. - Target/lifecycle: static analysis of owned packaged bytes; existing MCP harness and isolated verifier cleanup. Electron is not launched. - Generated metadata, installation and package distribution: unchanged; generated outputs and raw records are excluded from the diff. Expected effects: - [x] Read existing files or captured data. - [x] Launch existing REA/agent verifier processes. - [x] Create owned fixture/archive files and temporary isolated client configuration. - [x] Contact the existing model service during the optional live agent verifier. - No target execution, instrumentation, mutation or protection recovery is added. ## Evidence and regression coverage Two public MCP workflow regressions exercise actual Notes analysis, feature trace and semantic trace. They accept supported claims and reject incorrect values, erased ambiguity, unrelated existing citations, missing parent Evidence, unsupported extra runtime claims, keyword-only prose, contains queries, another artifact path and changed bytes at the same path. The default exact query is explicitly accepted. Source/module expectations are established from the owned fixture. The semantic claim checks the bounded static-query contract. The module list is the trace's returned source-module set; it is not proof that every module executed. ## Validation performed Windows x64, Node.js 24.18.0 and npm 11.16.0; source baseline `ca2d15b3`. - `npm ci`, `npm run build:cached` — passed. - `npm run test:focused -- tests/boundary/mcp/agentKnownAnswerMcp.test.ts tests/evaluation/model-evals/knownAnswerEvaluation.test.ts tests/evaluation/model-evals/codexAgentEval.test.ts tests/evaluation/model-evals/agentEvaluationReport.test.ts` — 4 files / 69 tests passed. - `npm run check` — passed, including typecheck, lint, format, knip, metadata and architecture guards. - `npm run jscpd` — passed, 2.98% duplicated lines. - `npm run verify:test-discovery` — all 1,004 files discovered exactly once. - `git diff --check` — passed. - Real stdio MCP probe — all three static operations completed against packaged Notes bytes. Windows native controls came from the verified published 6.4.0 artifact; the source checkout itself does not build that addon on Windows. - Live isolated `REA_AGENT_EVAL_SCENARIOS=notes-export npm run verify:agent` with Codex CLI 0.161.0 completed three successful REA calls, no invalid or repeated calls, and correct six-claim JSON. The original command's factual gate failed only on omitted `match` (REA's default exact). After fixing that interpretation, the unchanged original transcript was regraded with an independently regenerated fixture digest: six claims and the existing gate passed. This is replayed grading of that original execution, not a fresh post-fix model run. The original failed report and raw transcript remain local. The packaged fixture SHA-256 is `a8f3fe3170ca3332e6bc4708c9cdcb07ce69c01433694d8b26a43636323cc07c`; the original transcript SHA-256 is `0939640bfb0bbc40d53ced38333cbf3666873b73451d463eeb581163c24e3781`. An earlier attempt with the installed Codex CLI 0.154.0 did not start a model task because it lacks `--no-daemon`. ## Compatibility, safety, and release This guided fixture does not grade arbitrary free-form factual correctness, autonomous IPC discovery, CSV formatter correctness, actual Downloads resolution or runtime clicks/writes. It adds no AISOP/AISP runtime or dependency. No performance advantage is claimed: the one live trial reported 298,309 input tokens (231,552 cached) and 1,119 output tokens; CPU, peak process-family memory and model identity were not independently established. Existing public contracts and historical ASAR/parser rubrics are preserved. Linux/macOS model workflows, Electron runtime execution and the full local `check:pr` suite were not run. CI and maintainer review remain pending. ## Before merge - [x] One focused evaluation outcome and conventional title. - [x] Existing related work and overlap are identified. - [x] Changed behavior and meaningful failure paths are covered. - [x] Observed, derived, inferred and unknown boundaries remain explicit. - [x] Final diff excludes credentials, generated files, raw records and unrelated cleanup. - [ ] Maintainer review and current-head CI complete. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:05:03 +00:00

• closed this issue
• added the
  pull-request
  label

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

[GH-ISSUE #5654] [Tracker] Open PRs that can't merge yet: conflicts and red CI (October 2026) #3425

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

[PR #5239] [CLOSED] fix(evm): clarify worker address space as profile ceiling in limitations #6831

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

No description provided.