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 #1873] [MERGED] fix(evidence): reject NUL bytes in subject and snapshot paths #4869

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1873
Author: @DeryFerd
Created: 10/11/2026
Status: ✅ Merged
Merged: 10/11/2026
Merged by: @morluto

Base: main ← Head: fix/evidence-subject-nul-path

📝 Commits (1)

  • ed0a1e7 fix(evidence): reject NUL bytes in subject and snapshot paths

📊 Changes

5 files changed (+58 additions, -5 deletions)

View changed files

📝 src/domain/analysisSnapshot.test.ts (+31 -0)
📝 src/domain/analysisSnapshot.ts (+2 -1)
📝 src/domain/evidence.test.ts (+16 -0)
📝 src/domain/evidence.ts (+2 -1)
📝 src/domain/localPath.ts (+7 -3)

📄 Description

Summary

Evidence subject local_path and the analysis-snapshot subject path were plain strings, so an inline Evidence record supplied through a tool input could carry a NUL byte into the observation, the persisted snapshot, and any bundle written from it. Every other selected-path boundary in the repository already refuses NUL through the shared local-path schema, and a harness that exercises the real advertised MCP contracts asserts exactly that; the two Evidence subject schemas were the remaining gap. This PR routes both fields through the shared NUL-free schema, keeping the snapshot's nonempty rule and leaving the Evidence local_path free to be empty because network capture Evidence uses an empty path as a deliberate sentinel.

Problem and expected behavior

Smallest trigger: parse an Evidence record whose subject is { "local_path": "a\u0000b", ... }, for example through an inline source: { kind: "inline", evidence: ... } input on inspect_analysis_view or an imported bundle. Prior behavior: the schema accepted it, and the value flowed into subject.local_path on the observation and into any serialized snapshot or bundle. The violated invariant: a value the caller selects as a local filesystem path should be parsed once at the owning boundary, and NUL is never a valid filesystem path byte on any supported host, so it should be refused there rather than propagated as display data. Expected behavior: evidenceSchema and the snapshot subject schema reject a NUL local_path/path, an ordinary absolute or relative path is still accepted, and an empty Evidence local_path stays accepted because existing producers depend on it.

Change and scope

The NUL-free pattern now lives in src/domain/localPath.ts as nulFreeStringSchema, and localPathStringSchema is composed from it as nulFreeStringSchema.min(1) so the nonempty rule is expressed once instead of duplicated. src/domain/evidence.ts uses nulFreeStringSchema for subject.local_path because that field is legitimately empty for network capture Evidence, and src/domain/analysisSnapshot.ts uses localPathStringSchema for subject.path, which preserves the exact previous nonempty behavior while adding the NUL refusal. Intentionally not included: no change to subject.name, no change to any other string field, no new advertised contract shape, and no attempt to reinterpret the empty network-capture path as an error.

Contract and boundary impact

  • Semantic owner and earliest changed stage: domain contract schemas in src/domain/evidence.ts and src/domain/analysisSnapshot.ts, parsed at the tool-input and snapshot-import boundaries before any observation or bundle is built.
  • CLI and MCP/tool-catalog contract: the advertised JSON Schema for existing localPathStringSchema consumers is unchanged (the emitted pattern and minLength: 1 are byte-identical); the two Evidence subject fields gain the same NUL-rejecting pattern already used on every other path field, which is a validation tightening consistent with the existing boundary contracts.
  • Provider, bridge, target-format, or platform compatibility: none; the schema is provider-neutral and the NUL rule is host-independent.
  • Evidence, artifact, provenance, or reconstruction contract: accepted Evidence keeps byte-identical identity and digests; local_path was already excluded from the semantic identity, so no existing ev_/snapshot identity changes, and the tightening only rejects inputs that were never valid.
  • Process execution, authorization, cleanup, or containment impact: none; this is schema validation only.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in skill-src/ and never commit build outputs): none committed. .cache/mcp-tool-catalog.json is regenerated test metadata and is not part of the repository; the catalog digest moves only because the Evidence subject schema moved.

Evidence and regression coverage

  • Tests added or updated: a unit case in src/domain/evidence.test.ts asserts evidenceSchema accepts an ordinary path and an empty path and rejects a NUL local_path; a unit case in src/domain/analysisSnapshot.test.ts asserts the snapshot schema rejects a NUL subject path.
  • Base reproduction or other evidence: on the base revision both new cases fail because the fields accept any string; after the change the domain suite passes with no other expectation changes.
  • User-visible CLI/MCP output: a request carrying a NUL local path now fails validation at the boundary with the shared "Local filesystem paths cannot contain NUL" message instead of being accepted and later serialized.
  • Remaining proof gaps: no real provider or browser run applies to this schema-only change; the behavior is fully exercised by the unit and boundary suites listed below.

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

  • npx vitest run src/domain/ — 126 files, 1704 tests passed, including the new Evidence and snapshot cases.
  • npx vitest run tests/boundary/mcp/evidenceBundleInline.test.ts tests/boundary/mcp/retainedApplicationEvidenceMcp.test.ts — passed.
  • npx vitest run tests/acceptance/tools/localToolContracts.test.ts — passed, including the existing OS-invalid-local-input harness that rejects NUL through the real advertised MCP contracts.
  • npx vitest run tests/boundary/mcp/toolSchemaValidity.test.ts — 8 passed after npm run mcp-catalog:generate.
  • npm run typecheck — exit 0 after rebasing onto bcd350c36.
  • npx oxlint on the five changed files — 0 errors (the no-control-regex and max-lines warnings are pre-existing on the base); oxfmt --check on the committed (LF) form — clean.
  • Real Hopper/Ghidra, browser, or OS lanes: not applicable; no provider, bridge, or platform-specific code is touched.

Compatibility, safety, and release

  • Breaking changes or migration steps: none for valid callers. An input that carried a NUL path was already invalid on every host, so it now fails earlier with a named constraint; all previously accepted valid paths, including the empty network-capture path, still parse identically.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; the boundary suites above cover the changed schemas.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the change closes a small boundary inconsistency where an OS-invalid byte could be carried into retained Evidence and bundle output; it adds no network, process, or authority surface.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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/1873 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/11/2026 **Status:** ✅ Merged **Merged:** 10/11/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/evidence-subject-nul-path` --- ### 📝 Commits (1) - [`ed0a1e7`](https://github.com/morluto/rea/commit/ed0a1e76cde5b06c25bbcad96fe814dc868e43d1) fix(evidence): reject NUL bytes in subject and snapshot paths ### 📊 Changes **5 files changed** (+58 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/analysisSnapshot.test.ts` (+31 -0) 📝 `src/domain/analysisSnapshot.ts` (+2 -1) 📝 `src/domain/evidence.test.ts` (+16 -0) 📝 `src/domain/evidence.ts` (+2 -1) 📝 `src/domain/localPath.ts` (+7 -3) </details> ### 📄 Description ## Summary Evidence subject `local_path` and the analysis-snapshot subject `path` were plain strings, so an inline Evidence record supplied through a tool input could carry a NUL byte into the observation, the persisted snapshot, and any bundle written from it. Every other selected-path boundary in the repository already refuses NUL through the shared local-path schema, and a harness that exercises the real advertised MCP contracts asserts exactly that; the two Evidence subject schemas were the remaining gap. This PR routes both fields through the shared NUL-free schema, keeping the snapshot's nonempty rule and leaving the Evidence `local_path` free to be empty because network capture Evidence uses an empty path as a deliberate sentinel. ## Problem and expected behavior Smallest trigger: parse an Evidence record whose subject is `{ "local_path": "a\u0000b", ... }`, for example through an inline `source: { kind: "inline", evidence: ... }` input on `inspect_analysis_view` or an imported bundle. Prior behavior: the schema accepted it, and the value flowed into `subject.local_path` on the observation and into any serialized snapshot or bundle. The violated invariant: a value the caller selects as a local filesystem path should be parsed once at the owning boundary, and NUL is never a valid filesystem path byte on any supported host, so it should be refused there rather than propagated as display data. Expected behavior: `evidenceSchema` and the snapshot subject schema reject a NUL `local_path`/`path`, an ordinary absolute or relative path is still accepted, and an empty Evidence `local_path` stays accepted because existing producers depend on it. ## Change and scope The NUL-free pattern now lives in `src/domain/localPath.ts` as `nulFreeStringSchema`, and `localPathStringSchema` is composed from it as `nulFreeStringSchema.min(1)` so the nonempty rule is expressed once instead of duplicated. `src/domain/evidence.ts` uses `nulFreeStringSchema` for `subject.local_path` because that field is legitimately empty for network capture Evidence, and `src/domain/analysisSnapshot.ts` uses `localPathStringSchema` for `subject.path`, which preserves the exact previous nonempty behavior while adding the NUL refusal. Intentionally not included: no change to `subject.name`, no change to any other string field, no new advertised contract shape, and no attempt to reinterpret the empty network-capture path as an error. ## Contract and boundary impact - Semantic owner and earliest changed stage: domain contract schemas in `src/domain/evidence.ts` and `src/domain/analysisSnapshot.ts`, parsed at the tool-input and snapshot-import boundaries before any observation or bundle is built. - CLI and MCP/tool-catalog contract: the advertised JSON Schema for existing `localPathStringSchema` consumers is unchanged (the emitted `pattern` and `minLength: 1` are byte-identical); the two Evidence subject fields gain the same NUL-rejecting `pattern` already used on every other path field, which is a validation tightening consistent with the existing boundary contracts. - Provider, bridge, target-format, or platform compatibility: none; the schema is provider-neutral and the NUL rule is host-independent. - Evidence, artifact, provenance, or reconstruction contract: accepted Evidence keeps byte-identical identity and digests; `local_path` was already excluded from the semantic identity, so no existing `ev_`/snapshot identity changes, and the tightening only rejects inputs that were never valid. - Process execution, authorization, cleanup, or containment impact: none; this is schema validation only. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `skill-src/` and never commit build outputs): none committed. `.cache/mcp-tool-catalog.json` is regenerated test metadata and is not part of the repository; the catalog digest moves only because the Evidence subject schema moved. ## Evidence and regression coverage - Tests added or updated: a unit case in `src/domain/evidence.test.ts` asserts `evidenceSchema` accepts an ordinary path and an empty path and rejects a NUL `local_path`; a unit case in `src/domain/analysisSnapshot.test.ts` asserts the snapshot schema rejects a NUL subject `path`. - Base reproduction or other evidence: on the base revision both new cases fail because the fields accept any string; after the change the domain suite passes with no other expectation changes. - User-visible CLI/MCP output: a request carrying a NUL local path now fails validation at the boundary with the shared "Local filesystem paths cannot contain NUL" message instead of being accepted and later serialized. - Remaining proof gaps: no real provider or browser run applies to this schema-only change; the behavior is fully exercised by the unit and boundary suites listed below. 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 - `npx vitest run src/domain/` — 126 files, 1704 tests passed, including the new Evidence and snapshot cases. - `npx vitest run tests/boundary/mcp/evidenceBundleInline.test.ts tests/boundary/mcp/retainedApplicationEvidenceMcp.test.ts` — passed. - `npx vitest run tests/acceptance/tools/localToolContracts.test.ts` — passed, including the existing OS-invalid-local-input harness that rejects NUL through the real advertised MCP contracts. - `npx vitest run tests/boundary/mcp/toolSchemaValidity.test.ts` — 8 passed after `npm run mcp-catalog:generate`. - `npm run typecheck` — exit 0 after rebasing onto `bcd350c36`. - `npx oxlint` on the five changed files — 0 errors (the `no-control-regex` and `max-lines` warnings are pre-existing on the base); `oxfmt --check` on the committed (LF) form — clean. - Real Hopper/Ghidra, browser, or OS lanes: not applicable; no provider, bridge, or platform-specific code is touched. ## Compatibility, safety, and release - Breaking changes or migration steps: none for valid callers. An input that carried a NUL path was already invalid on every host, so it now fails earlier with a named constraint; all previously accepted valid paths, including the empty network-capture path, still parse identically. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; the boundary suites above cover the changed schemas. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the change closes a small boundary inconsistency where an OS-invalid byte could be carried into retained Evidence and bundle output; it adds no network, process, or authority surface. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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 00:56:13 +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#4869
No description provided.