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 #1412] [CLOSED] fix: report oversized JSON input as a runtime string limit #2866

New issue
Closed
opened 2026-10-17 21:11:12 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-17 21:11:12 +00:00
Owner
Copy link

📋 Pull Request Information

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

Base: main ← Head: imjimit07-fix-cli-json-v8-string-limit

📝 Commits (1)

  • 5a6d937 fix: report oversized JSON input as a runtime string limit

📊 Changes

12 files changed (+192 additions, -41 deletions)

View changed files

📝 src/application/JsonFiles.ts (+10 -6)
📝 src/cliJsonInput.ts (+53 -29)
📝 src/cliJsonInputStatus.test.ts (+1 -0)
📝 src/contracts/errorSchemas.ts (+3 -1)
📝 src/domain/analysisErrorPresentation.ts (+4 -0)
📝 src/domain/analysisErrorProjection.test.ts (+1 -0)
📝 src/domain/analysisErrorProjection.ts (+2 -0)
📝 src/domain/evidenceErrors.ts (+7 -1)
📝 src/domain/safeJson.test.ts (+24 -1)
📝 src/domain/safeJson.ts (+42 -0)
📝 tests/boundary/filesystem/jsonUtf8Input.test.ts (+35 -0)
📝 tests/conformance/contracts/analysisErrorProjection.test.ts (+10 -3)

📄 Description

Summary

CLI JSON input files larger than V8's maximum string length (about 512 MiB) were misclassified as invalid-json because every TextDecoder failure was treated as invalid UTF-8. The bytes may be valid JSON, so the real failure is a runtime size constraint. This PR classifies the runtime single-string limit distinctly at both affected boundaries and reports it with observed sizes and remediation. Fixes #1331.

Problem and expected behavior

Smallest trigger: rea trace-application-feature trace.json where trace.json exceeds buffer.constants.MAX_STRING_LENGTH (536,870,888 code units on 64-bit hosts). Decoding throws ERR_STRING_TOO_LONG, which the previous code caught and reported as invalid JSON.

Violated invariant: a decode failure does not imply invalid UTF-8. Node signals the single-string limit as a plain Error with code: "ERR_STRING_TOO_LONG", while invalid UTF-8 raises a TypeError (ERR_ENCODING_INVALID_ENCODED_DATA). A byte-length pre-check cannot distinguish them either, because multi-byte content decodes to fewer code units than bytes (600 MB of 2-byte UTF-8 decodes fine).

Expected behavior: the error names the actual cause, an input too large for the runtime to hold as one string, with a size-specific reason and remediation instead of claiming the JSON is invalid.

Change and scope

  • Added a shared decodeUtf8Json helper in src/domain/safeJson.ts that decodes strict UTF-8 without throws and classifies failures as invalid-utf8 or too-large (by ERR_STRING_TOO_LONG code or the "Cannot create a string longer than" message).
  • CLI boundary (src/cliJsonInput.ts): oversized input now returns input_reason: "input-too-large" with an AnalysisResourceConstraintError projection carrying the input byte size, the single-string code-unit limit, and remediation advice. This mirrors the existing output-side limit handling in src/server/toolResultEncoding.ts.
  • Evidence-file boundary (src/application/JsonFiles.ts): readJsonFile maps the same decode failure to a new too-large reason, projected as resource_constraint instead of evidence_integrity_mismatch.
  • Envelope schema (src/contracts/errorSchemas.ts): the input_reason enum gains input-too-large.

Intentionally not included: streaming or incremental JSON parsing and Evidence-reference indirection (the issue's "ideally" suggestion). Those are a feature change; this PR fixes the misclassification.

Contract and boundary impact

  • Semantic owner and earliest changed stage: domain (safeJson decode classification), then application (evidence file reads), then the CLI adapter (JSON input parsing).
  • CLI and MCP/tool-catalog contract: the CLI error envelope gains input_reason: "input-too-large". The canonical projection union is unchanged; the new case reuses the existing resource_constraint code. The MCP tool catalog is unchanged.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: EvidenceFileError gains the "too-large" reason, projected as resource_constraint with a size-specific message.
  • Process execution, authorization, cleanup, or containment impact: none.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none. analysisErrorJsonSchema covers only the projection union, so docs/error-contract.schema.json is unaffected; no catalog or skill sources changed.

Evidence and regression coverage

  • Tests added or updated:
    • tests/boundary/filesystem/jsonUtf8Input.test.ts adds a real beyond-limit regression: it writes a MAX_STRING_LENGTH + 1 byte file and asserts both readJsonFile and parseCliJsonInput report the size constraint (runs in about 1.2 s).
    • src/domain/safeJson.test.ts covers decode classification (valid multi-byte UTF-8; invalid UTF-8 reported as invalid-utf8 with the TypeError cause).
    • src/cliJsonInputStatus.test.ts, src/domain/analysisErrorProjection.test.ts, and tests/conformance/contracts/analysisErrorProjection.test.ts enumerate the new reason.
  • Base reproduction: on the base revision the new boundary test fails because both boundaries report invalid-json / evidence_integrity_mismatch for the same file.
  • User-visible CLI/MCP output: the CLI now emits code: "resource_constraint", category: "resource_constraint", retryable: false, input_path, input_reason: "input-too-large", a message naming the byte count and the code-unit limit, details.reported_limits with input_bytes and max_string_code_units, and a remediation action advising a smaller subset.
  • Remaining proof gaps: none for this classification. The streaming-parse feature remains unimplemented by design.

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

  • node node_modules/vitest/vitest.mjs run src/domain/safeJson.test.ts src/cliJsonInputStatus.test.ts src/domain/analysisErrorProjection.test.ts tests/conformance/contracts/analysisErrorProjection.test.ts tests/boundary/filesystem/jsonUtf8Input.test.ts tests/boundary/filesystem/cliJsonInput.test.ts tests/boundary/filesystem/evidenceBundleFiles.test.ts — 98 passed; 2 pre-existing Windows failures (fs.symlink EPERM without Developer Mode), verified identical on the clean tree via stash.
  • node node_modules/vitest/vitest.mjs run tests/boundary/cli/jsonInputStatus.test.ts tests/process-global/cliJsonInputStatus.test.ts tests/boundary/mcp/oversizedErrorDeliveryMcp.test.ts src/application/UpdateRuntime.release.test.ts plus other consumer suites — passed after npm run compile; 3 pre-existing Windows failures in tests/boundary/cli/jsonInputStatus.test.ts (assertions expect raw backslash paths inside JSON-serialized output), verified identical on the clean tree.
  • npm run check:fast — typecheck and lint pass.
  • npm run compile — dist build succeeds.
  • npx oxfmt on the changed files — no modifications; the pre-commit hook (oxfmt + oxlint) also made no changes at commit time.

npm run test:focused could not run on this Windows host due to a pre-existing spawn bug in scripts/run-exclusive-command.mjs (shell: true splits C:\Program Files\nodejs\node.exe), so vitest and tsc were invoked directly. Real Hopper/Ghidra verification: not applicable, no provider code changed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. The input_reason enum gains a value; the same input previously produced invalid-json, and no previously valid call changes behavior.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; no provider or platform behavior changed.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none; local file reads only, no new data persisted or transmitted.

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/1412 **Author:** [@imjimit07](https://github.com/imjimit07) **Created:** 10/10/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `imjimit07-fix-cli-json-v8-string-limit` --- ### 📝 Commits (1) - [`5a6d937`](https://github.com/morluto/rea/commit/5a6d9375b47db92c71980568583f28ebfaff420d) fix: report oversized JSON input as a runtime string limit ### 📊 Changes **12 files changed** (+192 additions, -41 deletions) <details> <summary>View changed files</summary> 📝 `src/application/JsonFiles.ts` (+10 -6) 📝 `src/cliJsonInput.ts` (+53 -29) 📝 `src/cliJsonInputStatus.test.ts` (+1 -0) 📝 `src/contracts/errorSchemas.ts` (+3 -1) 📝 `src/domain/analysisErrorPresentation.ts` (+4 -0) 📝 `src/domain/analysisErrorProjection.test.ts` (+1 -0) 📝 `src/domain/analysisErrorProjection.ts` (+2 -0) 📝 `src/domain/evidenceErrors.ts` (+7 -1) 📝 `src/domain/safeJson.test.ts` (+24 -1) 📝 `src/domain/safeJson.ts` (+42 -0) 📝 `tests/boundary/filesystem/jsonUtf8Input.test.ts` (+35 -0) 📝 `tests/conformance/contracts/analysisErrorProjection.test.ts` (+10 -3) </details> ### 📄 Description ## Summary CLI JSON input files larger than V8's maximum string length (about 512 MiB) were misclassified as `invalid-json` because every `TextDecoder` failure was treated as invalid UTF-8. The bytes may be valid JSON, so the real failure is a runtime size constraint. This PR classifies the runtime single-string limit distinctly at both affected boundaries and reports it with observed sizes and remediation. Fixes #1331. ## Problem and expected behavior Smallest trigger: `rea trace-application-feature trace.json` where `trace.json` exceeds `buffer.constants.MAX_STRING_LENGTH` (536,870,888 code units on 64-bit hosts). Decoding throws `ERR_STRING_TOO_LONG`, which the previous code caught and reported as invalid JSON. Violated invariant: a decode failure does not imply invalid UTF-8. Node signals the single-string limit as a plain `Error` with `code: "ERR_STRING_TOO_LONG"`, while invalid UTF-8 raises a `TypeError` (`ERR_ENCODING_INVALID_ENCODED_DATA`). A byte-length pre-check cannot distinguish them either, because multi-byte content decodes to fewer code units than bytes (600 MB of 2-byte UTF-8 decodes fine). Expected behavior: the error names the actual cause, an input too large for the runtime to hold as one string, with a size-specific reason and remediation instead of claiming the JSON is invalid. ## Change and scope - Added a shared `decodeUtf8Json` helper in `src/domain/safeJson.ts` that decodes strict UTF-8 without throws and classifies failures as `invalid-utf8` or `too-large` (by `ERR_STRING_TOO_LONG` code or the "Cannot create a string longer than" message). - CLI boundary (`src/cliJsonInput.ts`): oversized input now returns `input_reason: "input-too-large"` with an `AnalysisResourceConstraintError` projection carrying the input byte size, the single-string code-unit limit, and remediation advice. This mirrors the existing output-side limit handling in `src/server/toolResultEncoding.ts`. - Evidence-file boundary (`src/application/JsonFiles.ts`): `readJsonFile` maps the same decode failure to a new `too-large` reason, projected as `resource_constraint` instead of `evidence_integrity_mismatch`. - Envelope schema (`src/contracts/errorSchemas.ts`): the `input_reason` enum gains `input-too-large`. Intentionally not included: streaming or incremental JSON parsing and Evidence-reference indirection (the issue's "ideally" suggestion). Those are a feature change; this PR fixes the misclassification. ## Contract and boundary impact - Semantic owner and earliest changed stage: domain (`safeJson` decode classification), then application (evidence file reads), then the CLI adapter (JSON input parsing). - CLI and MCP/tool-catalog contract: the CLI error envelope gains `input_reason: "input-too-large"`. The canonical projection union is unchanged; the new case reuses the existing `resource_constraint` code. The MCP tool catalog is unchanged. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: `EvidenceFileError` gains the `"too-large"` reason, projected as `resource_constraint` with a size-specific message. - Process execution, authorization, cleanup, or containment impact: none. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. `analysisErrorJsonSchema` covers only the projection union, so `docs/error-contract.schema.json` is unaffected; no catalog or skill sources changed. ## Evidence and regression coverage - Tests added or updated: - `tests/boundary/filesystem/jsonUtf8Input.test.ts` adds a real beyond-limit regression: it writes a `MAX_STRING_LENGTH + 1` byte file and asserts both `readJsonFile` and `parseCliJsonInput` report the size constraint (runs in about 1.2 s). - `src/domain/safeJson.test.ts` covers decode classification (valid multi-byte UTF-8; invalid UTF-8 reported as `invalid-utf8` with the `TypeError` cause). - `src/cliJsonInputStatus.test.ts`, `src/domain/analysisErrorProjection.test.ts`, and `tests/conformance/contracts/analysisErrorProjection.test.ts` enumerate the new reason. - Base reproduction: on the base revision the new boundary test fails because both boundaries report `invalid-json` / `evidence_integrity_mismatch` for the same file. - User-visible CLI/MCP output: the CLI now emits `code: "resource_constraint"`, `category: "resource_constraint"`, `retryable: false`, `input_path`, `input_reason: "input-too-large"`, a message naming the byte count and the code-unit limit, `details.reported_limits` with `input_bytes` and `max_string_code_units`, and a remediation action advising a smaller subset. - Remaining proof gaps: none for this classification. The streaming-parse feature remains unimplemented by design. 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 - `node node_modules/vitest/vitest.mjs run src/domain/safeJson.test.ts src/cliJsonInputStatus.test.ts src/domain/analysisErrorProjection.test.ts tests/conformance/contracts/analysisErrorProjection.test.ts tests/boundary/filesystem/jsonUtf8Input.test.ts tests/boundary/filesystem/cliJsonInput.test.ts tests/boundary/filesystem/evidenceBundleFiles.test.ts` — 98 passed; 2 pre-existing Windows failures (`fs.symlink` EPERM without Developer Mode), verified identical on the clean tree via stash. - `node node_modules/vitest/vitest.mjs run tests/boundary/cli/jsonInputStatus.test.ts tests/process-global/cliJsonInputStatus.test.ts tests/boundary/mcp/oversizedErrorDeliveryMcp.test.ts src/application/UpdateRuntime.release.test.ts` plus other consumer suites — passed after `npm run compile`; 3 pre-existing Windows failures in `tests/boundary/cli/jsonInputStatus.test.ts` (assertions expect raw backslash paths inside JSON-serialized output), verified identical on the clean tree. - `npm run check:fast` — typecheck and lint pass. - `npm run compile` — dist build succeeds. - `npx oxfmt` on the changed files — no modifications; the pre-commit hook (oxfmt + oxlint) also made no changes at commit time. `npm run test:focused` could not run on this Windows host due to a pre-existing spawn bug in `scripts/run-exclusive-command.mjs` (`shell: true` splits `C:\Program Files\nodejs\node.exe`), so vitest and tsc were invoked directly. Real Hopper/Ghidra verification: not applicable, no provider code changed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. The `input_reason` enum gains a value; the same input previously produced `invalid-json`, and no previously valid call changes behavior. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; no provider or platform behavior changed. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none; local file reads only, no new data persisted or transmitted. ## 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-17 21:11:12 +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#2866
No description provided.