[PR #1472] [CLOSED] fix(json): refuse evidence JSON that cannot decode before reading it #2910

New issue

Closed

opened 2026-10-17 21:11:43 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-17 21:11:43 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1472
Author: @DeryFerd
Created: 10/10/2026
Status: ❌ Closed

Base: main ← Head: fix/json-undecodable-input-admission

---

📝 Commits (1)

• 549b68b fix(json): refuse evidence JSON that cannot decode before reading it

📊 Changes

2 files changed (+64 additions, -4 deletions)

View changed files

📝 src/application/JsonFiles.ts (+33 -3)
📝 tests/boundary/filesystem/jsonUtf8Input.test.ts (+31 -1)

📄 Description

Summary

readJsonFile backs evidence bundle imports and analysis snapshot loads, and it used to pull the caller-selected file into memory before anything checked whether the file could ever be accepted. This PR adds an admission check on the stat that the file handle already provides: an input larger than three times the runtime string limit cannot decode under any content, so it is refused immediately with the same typed resource_constraint error the decode path already produces, now carrying the failed bound as max_decodable_input_bytes. No issue is linked because this is a standalone boundary hardening found while reading the JSON input path, not a report-driven fix.

Problem and expected behavior

Smallest trigger: call readJsonFile on a regular file whose size exceeds 3 * constants.MAX_STRING_LENGTH, roughly 1.5 GiB with Node's current ~512 MiB string limit. Prior behavior: the whole file was read into a Buffer first, and only then did parseUtf8Json chunk-decode it and raise AnalysisResourceConstraintError once the decoded length crossed the limit. The violated invariant: a caller should learn that input can never be accepted without the host first paying for every byte of it. On a machine that cannot hold the file, the process can die inside readFile() and the typed error, with its path, byte count, and remediation, never appears. Expected behavior: refuse from the admission stat, report the observed size and both limits, and never read the file's bytes.

Change and scope

The check lives in readJsonFile (src/application/JsonFiles.ts), which now goes through withRegularFile so the size is stat-ed on the same open handle that performs the read; a file that grows after admission still falls back to the existing decode classification, so the refusal can never be the only guard. The bound is 3 * constants.MAX_STRING_LENGTH because UTF-8's smallest ratio is one UTF-16 code unit per three bytes (three-byte BMP sequences), which means anything larger cannot decode within the runtime string limit no matter its content, and anything smaller cannot be rejected on size alone without refusing inputs that work today, including multibyte-heavy files that pass through the chunked decode. Intentionally not included: the CLI streaming reader (readCliJsonFile) already reads in 64 KiB chunks and needs no admission, no configuration knob is added, and no other read path changes.

Contract and boundary impact

• Semantic owner and earliest changed stage: application layer, readJsonFile in src/application/JsonFiles.ts, before UTF-8 decode; domain schemas untouched.
• CLI and MCP/tool-catalog contract: no schema change. The error keeps the existing resource_constraint projection, its details record is an open string-to-JSON map, and no tool is added or removed, so the generated catalog does not move.
• Provider, bridge, target-format, or platform compatibility: none. The path is provider-neutral, and the stat-on-open-handle check behaves the same on POSIX and Windows.
• Evidence, artifact, provenance, or reconstruction contract: accepted inputs produce byte-identical evidence to before; the refusal reports observed input_bytes from the stat plus the derived max_decodable_input_bytes, keeping observed and derived values distinguishable, and reuses the existing remediation text for evidence workflows.
• Process execution, authorization, cleanup, or containment impact: peak resident memory drops for oversized caller-selected inputs because their bytes are never read; the handle is closed by the existing withRegularFile finally path.
• 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. No contract, catalog, or skill input changed, and no build output is committed.

Evidence and regression coverage

• Tests added or updated: one case in tests/boundary/filesystem/jsonUtf8Input.test.ts creates a sparse file of 3 * MAX_STRING_LENGTH + 1 bytes and asserts the typed refusal with operation: "read_evidence_file", resource: "memory", observed input_bytes, max_string_code_units, and max_decodable_input_bytes.
• Base reproduction or other evidence: on the base revision the same file loads the full buffer and reaches the chunked decode loop before reporting a constraint that lacks max_decodable_input_bytes; with this change the case finishes in about 50 ms because only the stat is consulted. The new test fails on the base revision for exactly the missing bound.
• User-visible CLI/MCP output: resource_constraint details for refused oversized inputs now carry max_decodable_input_bytes alongside the existing fields; inputs below the bound are unchanged.
• Remaining proof gaps: a file that is both over the bound and invalid UTF-8 now reports the size constraint instead of the UTF-8 failure, since the bytes are no longer decoded to tell the two apart, and both outcomes refuse the file. No real-provider run applies to this provider-neutral path and none was attempted.

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 tests/boundary/filesystem/jsonUtf8Input.test.ts — 3 passed, including the new admission case.
• npx vitest run tests/boundary/cli/jsonInputSize.test.ts — 3 passed; this suite pins the whole-document string-limit classifications for both readers.
• npx vitest run tests/boundary/filesystem/evidenceBundleFiles.test.ts tests/boundary/filesystem/cliJsonInput.test.ts — 34 passed, 4 skipped, 2 failed; both failures are EPERM inside the tests' own symlink() fixture setup on Windows, before any application read code runs.
• npm run typecheck — exit 0 on the rebased branch.
• npx oxlint on the two changed files — 0 warnings, 0 errors; oxfmt --check on the committed (LF) form — clean.
• Real Hopper/Ghidra, browser, or OS lanes: not run, because no provider, bridge, or platform-specific code is touched.

Compatibility, safety, and release

• Breaking changes or migration steps: none. Inputs that succeeded before still succeed with identical bytes, and inputs that failed before still fail with the same code, resource, and remediation; only files that could never be accepted lose the wasteful read.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable; the Windows-host boundary suites listed above cover the changed path.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: the change shrinks the memory-exhaustion surface for hostile or accidental multi-gigabyte selections, adds no network, process, or authority surface, and does not persist or transmit file content.

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/1472 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/10/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/json-undecodable-input-admission` --- ### 📝 Commits (1) - [`549b68b`](https://github.com/morluto/rea/commit/549b68b8b61bfb4797c87588d7ce0a71abd9409f) fix(json): refuse evidence JSON that cannot decode before reading it ### 📊 Changes **2 files changed** (+64 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/application/JsonFiles.ts` (+33 -3) 📝 `tests/boundary/filesystem/jsonUtf8Input.test.ts` (+31 -1) </details> ### 📄 Description ## Summary `readJsonFile` backs evidence bundle imports and analysis snapshot loads, and it used to pull the caller-selected file into memory before anything checked whether the file could ever be accepted. This PR adds an admission check on the stat that the file handle already provides: an input larger than three times the runtime string limit cannot decode under any content, so it is refused immediately with the same typed `resource_constraint` error the decode path already produces, now carrying the failed bound as `max_decodable_input_bytes`. No issue is linked because this is a standalone boundary hardening found while reading the JSON input path, not a report-driven fix. ## Problem and expected behavior Smallest trigger: call `readJsonFile` on a regular file whose size exceeds `3 * constants.MAX_STRING_LENGTH`, roughly 1.5 GiB with Node's current ~512 MiB string limit. Prior behavior: the whole file was read into a `Buffer` first, and only then did `parseUtf8Json` chunk-decode it and raise `AnalysisResourceConstraintError` once the decoded length crossed the limit. The violated invariant: a caller should learn that input can never be accepted without the host first paying for every byte of it. On a machine that cannot hold the file, the process can die inside `readFile()` and the typed error, with its path, byte count, and remediation, never appears. Expected behavior: refuse from the admission stat, report the observed size and both limits, and never read the file's bytes. ## Change and scope The check lives in `readJsonFile` (`src/application/JsonFiles.ts`), which now goes through `withRegularFile` so the size is stat-ed on the same open handle that performs the read; a file that grows after admission still falls back to the existing decode classification, so the refusal can never be the only guard. The bound is `3 * constants.MAX_STRING_LENGTH` because UTF-8's smallest ratio is one UTF-16 code unit per three bytes (three-byte BMP sequences), which means anything larger cannot decode within the runtime string limit no matter its content, and anything smaller cannot be rejected on size alone without refusing inputs that work today, including multibyte-heavy files that pass through the chunked decode. Intentionally not included: the CLI streaming reader (`readCliJsonFile`) already reads in 64 KiB chunks and needs no admission, no configuration knob is added, and no other read path changes. ## Contract and boundary impact - Semantic owner and earliest changed stage: application layer, `readJsonFile` in `src/application/JsonFiles.ts`, before UTF-8 decode; domain schemas untouched. - CLI and MCP/tool-catalog contract: no schema change. The error keeps the existing `resource_constraint` projection, its `details` record is an open string-to-JSON map, and no tool is added or removed, so the generated catalog does not move. - Provider, bridge, target-format, or platform compatibility: none. The path is provider-neutral, and the stat-on-open-handle check behaves the same on POSIX and Windows. - Evidence, artifact, provenance, or reconstruction contract: accepted inputs produce byte-identical evidence to before; the refusal reports observed `input_bytes` from the stat plus the derived `max_decodable_input_bytes`, keeping observed and derived values distinguishable, and reuses the existing remediation text for evidence workflows. - Process execution, authorization, cleanup, or containment impact: peak resident memory drops for oversized caller-selected inputs because their bytes are never read; the handle is closed by the existing `withRegularFile` finally path. - 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. No contract, catalog, or skill input changed, and no build output is committed. ## Evidence and regression coverage - Tests added or updated: one case in `tests/boundary/filesystem/jsonUtf8Input.test.ts` creates a sparse file of `3 * MAX_STRING_LENGTH + 1` bytes and asserts the typed refusal with `operation: "read_evidence_file"`, `resource: "memory"`, observed `input_bytes`, `max_string_code_units`, and `max_decodable_input_bytes`. - Base reproduction or other evidence: on the base revision the same file loads the full buffer and reaches the chunked decode loop before reporting a constraint that lacks `max_decodable_input_bytes`; with this change the case finishes in about 50 ms because only the stat is consulted. The new test fails on the base revision for exactly the missing bound. - User-visible CLI/MCP output: `resource_constraint` details for refused oversized inputs now carry `max_decodable_input_bytes` alongside the existing fields; inputs below the bound are unchanged. - Remaining proof gaps: a file that is both over the bound and invalid UTF-8 now reports the size constraint instead of the UTF-8 failure, since the bytes are no longer decoded to tell the two apart, and both outcomes refuse the file. No real-provider run applies to this provider-neutral path and none was attempted. 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 tests/boundary/filesystem/jsonUtf8Input.test.ts` — 3 passed, including the new admission case. - `npx vitest run tests/boundary/cli/jsonInputSize.test.ts` — 3 passed; this suite pins the whole-document string-limit classifications for both readers. - `npx vitest run tests/boundary/filesystem/evidenceBundleFiles.test.ts tests/boundary/filesystem/cliJsonInput.test.ts` — 34 passed, 4 skipped, 2 failed; both failures are `EPERM` inside the tests' own `symlink()` fixture setup on Windows, before any application read code runs. - `npm run typecheck` — exit 0 on the rebased branch. - `npx oxlint` on the two changed files — 0 warnings, 0 errors; `oxfmt --check` on the committed (LF) form — clean. - Real Hopper/Ghidra, browser, or OS lanes: not run, because no provider, bridge, or platform-specific code is touched. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Inputs that succeeded before still succeed with identical bytes, and inputs that failed before still fail with the same code, resource, and remediation; only files that could never be accepted lose the wasteful read. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; the Windows-host boundary suites listed above cover the changed path. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the change shrinks the memory-exhaustion surface for hostile or accidental multi-gigabyte selections, adds no network, process, or authority surface, and does not persist or transmit file content. ## 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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-17 21:11:43 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-10-31 01:06:38 +00:00

[PR #2853] [CLOSED] fix(ci): restore reconstruction and formatting checks #5439

bsakaguchi referenced this issue 2026-10-31 01:06:40 +00:00

[PR #2856] [CLOSED] fix(browser): retain optional WebMCP declaration sites #5444

bsakaguchi referenced this issue 2026-10-31 01:06:42 +00:00

[PR #2861] [MERGED] fix(browser): report complete storage key inventory changes #5446

bsakaguchi referenced this issue 2026-10-31 01:07:02 +00:00

[PR #2910] [MERGED] fix: isolate Linux inventory and repair DEX schema regex #5486

bsakaguchi referenced this issue 2026-10-31 01:07:04 +00:00

[PR #2917] [MERGED] test(android): preserve malformed DEX prototype rejection #5491

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

No description provided.