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 #1899] [MERGED] fix(web): reject NUL bytes in web tool local path inputs #4893

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

📋 Pull Request Information

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

Base: main ← Head: fix/web-tool-path-nul

📝 Commits (1)

  • 499ac18 fix(web): reject NUL bytes in web tool local path inputs

📊 Changes

7 files changed (+165 additions, -32 deletions)

View changed files

📝 src/domain/webModuleTrace.ts (+7 -8)
📝 src/domain/webNetworkCapture.ts (+4 -4)
📝 src/domain/webScriptArtifacts.ts (+4 -4)
📝 src/domain/webScriptExport.ts (+7 -12)
📝 src/domain/webSourceLocation.ts (+4 -4)
➕ src/domain/webToolPathSchemas.test.ts (+103 -0)
📝 tests/acceptance/tools/localToolContracts.test.ts (+36 -0)

📄 Description

Summary

Four web tools accepted caller-selected local paths as plain strings, so a NUL byte passed contract validation and reached the filesystem layer. The owning services only checked isAbsolute, and isAbsolute admits a NUL, so the byte was carried into a file operation and surfaced there as a raw ERR_INVALID_ARG_VALUE ("path must be a string... without null bytes") rather than as a named input constraint. Every other local-input tool in the repository already refuses NUL through the shared local-path schema, and the existing OS-invalid-local-input harness covers those tools but not these four. This PR routes the seven affected fields through the same shared schema so the refusal happens at the contract boundary, and extends the harness to the tools that were missing from it.

Problem and expected behavior

Smallest trigger: call inspect_web_network_capture with {"capture_path": "/tmp/selected\u0000filename", "format": "har"}, or any of the six sibling cases listed below. Prior behavior: the input schema accepted the value, the service's isAbsolute check passed, and the file read then threw a raw Node error instead of a typed AnalysisInputError, so the caller saw an internal error string rather than the shared "Local filesystem paths cannot contain NUL" constraint the other tools return. 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. Expected behavior: all seven fields reject a NUL with the shared message, an ordinary absolute path is still accepted, and the accepted/rejected set for every other input is unchanged.

Change and scope

The seven caller-facing path fields now use localPathStringSchema instead of z.string().min(1): inspect_web_network_capture.capture_path (src/domain/webNetworkCapture.ts), export_web_scripts.capture_path and output_directory (src/domain/webScriptExport.ts), trace_web_source_location.manifest_path (shared selectedWebScriptInputSchema in src/domain/webScriptArtifacts.ts) and source_map.path (src/domain/webSourceLocation.ts), and trace_web_module_imports.manifest_path and import_map.path (src/domain/webModuleTrace.ts). Each field already required a nonempty string, so localPathStringSchema is a drop-in: the emitted pattern and minLength are identical and only the NUL refusal is added. Intentionally not included: output and derived path fields that REA builds internally from already-validated input are left as-is, no service-level isAbsolute check is removed, no URL field changes, and no tool is added or removed.

Contract and boundary impact

  • Semantic owner and earliest changed stage: domain input contracts for the four web tools, parsed at the tool-input boundary before any file is opened.
  • CLI and MCP/tool-catalog contract: the advertised JSON Schema for the seven fields is unchanged in shape; each keeps its existing minLength: 1 and gains the shared NUL-rejecting pattern already used by every other local-path tool. The catalog digest moves only because the contract moved, and no catalog file is committed.
  • 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: none. Accepted inputs produce byte-identical Evidence; only inputs that were never valid on any host are now refused earlier.
  • Process execution, authorization, cleanup, or containment impact: none; this is schema validation and one harness extension.
  • 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.

Evidence and regression coverage

  • Tests added or updated: a new src/domain/webToolPathSchemas.test.ts rejects a NUL in all seven fields and accepts ordinary absolute paths as a control; tests/acceptance/tools/localToolContracts.test.ts adds the four tools to its OS-invalid-local-input harness so they are exercised through the real advertised MCP contracts.
  • Base reproduction or other evidence: on the base revision the new schema case fails for all seven fields because each accepted a NUL, and the harness cases fail because the tools did not reject it; after the change both pass.
  • User-visible CLI/MCP output: a request carrying a NUL local path now fails at the boundary with the shared "Local filesystem paths cannot contain NUL" message instead of a raw filesystem error.
  • Remaining proof gaps: no real provider or browser run applies to this schema-only change; the behavior is fully exercised by the schema and MCP 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/webToolPathSchemas.test.ts — 8 passed, including the seven NUL-rejection cases and the accepted-path control.
  • npx vitest run tests/acceptance/tools/localToolContracts.test.ts — passed, including the four newly added tools through the real advertised MCP contracts.
  • npx vitest run tests/boundary/mcp/toolSchemaValidity.test.ts — 8 passed after npm run mcp-catalog:generate.
  • npx vitest run tests/boundary/filesystem/webScriptExport.test.ts — 2 failures that reproduce identically with this change stashed (a symlink EPERM and a private-runtime-root-authority-unavailable case on this Windows host), so they are environmental and pre-existing.
  • npm run typecheck — exit 0.
  • npx oxlint on the changed files — 0 warnings, 0 errors; 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. A NUL path was already invalid on every host, so it now fails earlier with a named constraint; all previously accepted valid paths still parse identically and the advertised schema keeps the same shape.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; the schema and MCP boundary suites above cover the changed contracts.
  • 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 reach a filesystem call and surface as an untyped internal error; 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/1899 **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/web-tool-path-nul` --- ### 📝 Commits (1) - [`499ac18`](https://github.com/morluto/rea/commit/499ac180115de7c9de3f1adc55159ffa6e9bb40e) fix(web): reject NUL bytes in web tool local path inputs ### 📊 Changes **7 files changed** (+165 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/webModuleTrace.ts` (+7 -8) 📝 `src/domain/webNetworkCapture.ts` (+4 -4) 📝 `src/domain/webScriptArtifacts.ts` (+4 -4) 📝 `src/domain/webScriptExport.ts` (+7 -12) 📝 `src/domain/webSourceLocation.ts` (+4 -4) ➕ `src/domain/webToolPathSchemas.test.ts` (+103 -0) 📝 `tests/acceptance/tools/localToolContracts.test.ts` (+36 -0) </details> ### 📄 Description ## Summary Four web tools accepted caller-selected local paths as plain strings, so a NUL byte passed contract validation and reached the filesystem layer. The owning services only checked `isAbsolute`, and `isAbsolute` admits a NUL, so the byte was carried into a file operation and surfaced there as a raw `ERR_INVALID_ARG_VALUE` ("path must be a string... without null bytes") rather than as a named input constraint. Every other local-input tool in the repository already refuses NUL through the shared local-path schema, and the existing OS-invalid-local-input harness covers those tools but not these four. This PR routes the seven affected fields through the same shared schema so the refusal happens at the contract boundary, and extends the harness to the tools that were missing from it. ## Problem and expected behavior Smallest trigger: call `inspect_web_network_capture` with `{"capture_path": "/tmp/selected\u0000filename", "format": "har"}`, or any of the six sibling cases listed below. Prior behavior: the input schema accepted the value, the service's `isAbsolute` check passed, and the file read then threw a raw Node error instead of a typed `AnalysisInputError`, so the caller saw an internal error string rather than the shared "Local filesystem paths cannot contain NUL" constraint the other tools return. 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. Expected behavior: all seven fields reject a NUL with the shared message, an ordinary absolute path is still accepted, and the accepted/rejected set for every other input is unchanged. ## Change and scope The seven caller-facing path fields now use `localPathStringSchema` instead of `z.string().min(1)`: `inspect_web_network_capture.capture_path` (`src/domain/webNetworkCapture.ts`), `export_web_scripts.capture_path` and `output_directory` (`src/domain/webScriptExport.ts`), `trace_web_source_location.manifest_path` (shared `selectedWebScriptInputSchema` in `src/domain/webScriptArtifacts.ts`) and `source_map.path` (`src/domain/webSourceLocation.ts`), and `trace_web_module_imports.manifest_path` and `import_map.path` (`src/domain/webModuleTrace.ts`). Each field already required a nonempty string, so `localPathStringSchema` is a drop-in: the emitted `pattern` and `minLength` are identical and only the NUL refusal is added. Intentionally not included: output and derived path fields that REA builds internally from already-validated input are left as-is, no service-level `isAbsolute` check is removed, no URL field changes, and no tool is added or removed. ## Contract and boundary impact - Semantic owner and earliest changed stage: domain input contracts for the four web tools, parsed at the tool-input boundary before any file is opened. - CLI and MCP/tool-catalog contract: the advertised JSON Schema for the seven fields is unchanged in shape; each keeps its existing `minLength: 1` and gains the shared NUL-rejecting `pattern` already used by every other local-path tool. The catalog digest moves only because the contract moved, and no catalog file is committed. - 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: none. Accepted inputs produce byte-identical Evidence; only inputs that were never valid on any host are now refused earlier. - Process execution, authorization, cleanup, or containment impact: none; this is schema validation and one harness extension. - 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. ## Evidence and regression coverage - Tests added or updated: a new `src/domain/webToolPathSchemas.test.ts` rejects a NUL in all seven fields and accepts ordinary absolute paths as a control; `tests/acceptance/tools/localToolContracts.test.ts` adds the four tools to its OS-invalid-local-input harness so they are exercised through the real advertised MCP contracts. - Base reproduction or other evidence: on the base revision the new schema case fails for all seven fields because each accepted a NUL, and the harness cases fail because the tools did not reject it; after the change both pass. - User-visible CLI/MCP output: a request carrying a NUL local path now fails at the boundary with the shared "Local filesystem paths cannot contain NUL" message instead of a raw filesystem error. - Remaining proof gaps: no real provider or browser run applies to this schema-only change; the behavior is fully exercised by the schema and MCP 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/webToolPathSchemas.test.ts` — 8 passed, including the seven NUL-rejection cases and the accepted-path control. - `npx vitest run tests/acceptance/tools/localToolContracts.test.ts` — passed, including the four newly added tools through the real advertised MCP contracts. - `npx vitest run tests/boundary/mcp/toolSchemaValidity.test.ts` — 8 passed after `npm run mcp-catalog:generate`. - `npx vitest run tests/boundary/filesystem/webScriptExport.test.ts` — 2 failures that reproduce identically with this change stashed (a symlink `EPERM` and a `private-runtime-root-authority-unavailable` case on this Windows host), so they are environmental and pre-existing. - `npm run typecheck` — exit 0. - `npx oxlint` on the changed files — 0 warnings, 0 errors; `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. A NUL path was already invalid on every host, so it now fails earlier with a named constraint; all previously accepted valid paths still parse identically and the advertised schema keeps the same shape. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; the schema and MCP boundary suites above cover the changed contracts. - 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 reach a filesystem call and surface as an untyped internal error; 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:30 +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#4893
No description provided.