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 #4807] fix(cli): stream default TOON results past the string limit #6419

New issue
Open
opened 2026-10-31 01:14:19 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:14:19 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4807
Author: @AniketR10
Created: 10/17/2026
Status: 🔄 Open

Base: main ← Head: fix/cli-stream-toon-output

📝 Commits (5)

  • ab00d03 fix(cli): stream default TOON results past the string limit
  • bf0f07b fix(cli): format non-object TOON values with Incur
  • 44e66ac fix(cli): keep human terminal TOON on Incur's renderer
  • 61f0b27 Merge remote-tracking branch 'upstream/main' into fix/cli-stream-toon-output
  • 9a3fb67 fix(cli): stream oversized TOON results from capacity recovery

📊 Changes

5 files changed (+364 additions, -14 deletions)

View changed files

📝 package-lock.json (+1 -0)
📝 package.json (+1 -0)
📝 scripts/rea.mjs (+3 -1)
📝 src/cli/cliResultOutput.ts (+100 -12)
📝 tests/boundary/cli/jsonOutput.test.ts (+259 -1)

📄 Description

Summary

Refs #4806

Main answers a TOON result that cannot fit in one runtime string with a typed resource_constraint (fd6da7092). This PR adds the remaining streaming behavior for successful results: when Incur's one-string TOON formatting hits the limit, capacity recovery writes the result line by line instead of the failure. All other output, including every result that fits, is unchanged.

Problem and expected behavior

Incur formats TOON with encode(), which joins every line into one string. Above buffer.constants.MAX_STRING_LENGTH that throws, and main's recoverFormattingFailure replaces the result with a small typed failure. JSON already streams past the limit; a successful default-TOON result could not be delivered at all.

Expected: such a result is written completely as the bytes Incur's formatter would produce, while everything else keeps main's path and encoding cost.

Change and scope

  • src/cli/cliResultOutput.ts:
    • writeResult keeps main's flow. It only records the TOON document that recovery may stream. The delegation check moves after the document is built so it can record it; there is no other branch change.
    • A result is recorded only when all of these hold:
      • the format is TOON and the result is successful (no operation failure or logged failure);
      • there is no --token-count, --token-limit or --token-offset;
      • Incur is not rendering for a human (--format/--json explicit, or stdout not a terminal).
    • recoverFormattingFailure: for a recorded document, lines are encoded with encodeLines from @toon-format/toon 2.3.1, the version and function Incur's formatter uses. Up to the limit they are encoded before anything is written. If a line cannot be built by then, recovery writes main's typed failure. Otherwise it streams the lines through the existing 64 KiB bufferedJsonParts and sets recoveredByStreaming.
  • scripts/rea.mjs: after a streamed recovery the launcher keeps the command's exit status instead of forcing 1. Failures already set their status through logCliCommand.
  • Unchanged:
    • Results that fit are still encoded once, by Incur, with no added work.
    • Failures and full-output failure envelopes, terminal rendering, token windows and counts, YAML, Markdown, JSON and JSONL keep main's behavior, including the compact capacity failure.
  • @toon-format/toon becomes a direct dependency at 2.3.1, the version already resolved through incur. The lockfile changes by one line.
  • Known gap, by design: if more than one runtime string of TOON has already streamed and a later single line cannot be built (over 1 GB of TOON), output is partial. Handling that would need buffering beyond the limit.

Contribution scope: ordinary output fix; maintainer scope decision not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: the shared CLI result output boundary (cliResultOutput.ts) and its launcher recovery hook.
  • Contribution scope fit and linked maintainer decision: fits existing scope; not applicable.
  • CLI and MCP/tool-catalog contract: a successful TOON result above the string limit, whose lines fit, outside terminal and token modes, is written completely with exit 0 instead of the typed capacity failure. Every other CLI output is unchanged. MCP is unaffected.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: one new direct dependency, already installed transitively at the same version.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests in tests/boundary/cli/jsonOutput.test.ts:
    • Results that fit:
      • for default format, --format toon and --full-output, output equals Incur's own output for a nested object, an empty object, null, "", false, 0 and a multiline string;
      • owned --filter-output projections keep main's text and trailing newline, including an empty selection.
    • Above the limit:
      • a successful tabular result whose Incur formatting throws RangeError is streamed by recovery, exactly as the launcher drives it. Byte count and SHA-256 match the expected TOON, with no typed error.
    • Main's typed capacity failure kept:
      • an oversized full-output failure envelope;
      • oversized TOON on a default-format terminal;
      • oversized TOON with --token-count;
      • a document with one TOON line longer than the limit.
    • tests/boundary/cli/formattingRecovery.test.ts (main's recovery tests) passes unchanged.
  • Base reproduction (executed): with cliResultOutput.ts from main, only the streaming test fails (1 failed, 55 passed in the file).
  • Not executed: the launcher exit-status change is source-derived; no real CLI run produced over 512 MB of TOON. No real large application was run.

Validation performed

  • npm run test:focused -- tests/boundary/cli/jsonOutput.test.ts tests/boundary/cli/formattingRecovery.test.ts tests/boundary/cli/dispatcher.test.ts tests/boundary/cli/cliSetup.test.ts: 4 files, 93 tests passed.
  • Same jsonOutput.test.ts with main's cliResultOutput.ts: 1 failed (the streaming test), 55 passed.
  • npm run check: typecheck, lint, format and metadata pass. knip reports one unused export and three unused types in untouched files (javascriptStaticAnalysisHelpers.ts, androidJniLibraryFacts.ts, androidManifestComponents.ts, objcSwiftMetadata.ts), also present on main.
  • npm run docs:check: passed on the previous revision; this revision changes no documentation or contracts.
  • Earlier full npx vitest run --project cli-boundary on this branch: 6 failures. The five in analyzeFunctionDetail, electronCli and ghidraJavaDoctor fail identically with main's cliResultOutput.ts on this host; the npx setup case depends on the npm registry.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Only a successful TOON result that currently becomes a capacity failure changes.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; Linux only.
  • Package or release metadata impact: new direct dependency @toon-format/toon@2.3.1, already shipped through incur.
  • Security, privacy, process, or containment review: output formatting only; no new I/O or side effects.

Author readiness

Human owner: @AniketR10

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • 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/4807 **Author:** [@AniketR10](https://github.com/AniketR10) **Created:** 10/17/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/cli-stream-toon-output` --- ### 📝 Commits (5) - [`ab00d03`](https://github.com/morluto/rea/commit/ab00d03b2c4e41da326ef2e7f860d1e7fe1723ec) fix(cli): stream default TOON results past the string limit - [`bf0f07b`](https://github.com/morluto/rea/commit/bf0f07b619f5377aa6961b34e4e9fe3ff3a0e8c3) fix(cli): format non-object TOON values with Incur - [`44e66ac`](https://github.com/morluto/rea/commit/44e66acd98d9cadb1c0e29a58d95aa276d38744c) fix(cli): keep human terminal TOON on Incur's renderer - [`61f0b27`](https://github.com/morluto/rea/commit/61f0b273fa97e072d2e633999d6b7e140dde64ad) Merge remote-tracking branch 'upstream/main' into fix/cli-stream-toon-output - [`9a3fb67`](https://github.com/morluto/rea/commit/9a3fb672a8f7901387beedf5bb1ea453595d98d1) fix(cli): stream oversized TOON results from capacity recovery ### 📊 Changes **5 files changed** (+364 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+1 -0) 📝 `package.json` (+1 -0) 📝 `scripts/rea.mjs` (+3 -1) 📝 `src/cli/cliResultOutput.ts` (+100 -12) 📝 `tests/boundary/cli/jsonOutput.test.ts` (+259 -1) </details> ### 📄 Description ## Summary Refs #4806 Main answers a TOON result that cannot fit in one runtime string with a typed `resource_constraint` (fd6da7092). This PR adds the remaining streaming behavior for successful results: when Incur's one-string TOON formatting hits the limit, capacity recovery writes the result line by line instead of the failure. All other output, including every result that fits, is unchanged. ## Problem and expected behavior Incur formats TOON with `encode()`, which joins every line into one string. Above `buffer.constants.MAX_STRING_LENGTH` that throws, and main's `recoverFormattingFailure` replaces the result with a small typed failure. JSON already streams past the limit; a successful default-TOON result could not be delivered at all. Expected: such a result is written completely as the bytes Incur's formatter would produce, while everything else keeps main's path and encoding cost. ## Change and scope - `src/cli/cliResultOutput.ts`: - `writeResult` keeps main's flow. It only records the TOON document that recovery may stream. The delegation check moves after the document is built so it can record it; there is no other branch change. - A result is recorded only when all of these hold: - the format is TOON and the result is successful (no operation failure or logged failure); - there is no `--token-count`, `--token-limit` or `--token-offset`; - Incur is not rendering for a human (`--format`/`--json` explicit, or stdout not a terminal). - `recoverFormattingFailure`: for a recorded document, lines are encoded with `encodeLines` from `@toon-format/toon` 2.3.1, the version and function Incur's formatter uses. Up to the limit they are encoded before anything is written. If a line cannot be built by then, recovery writes main's typed failure. Otherwise it streams the lines through the existing 64 KiB `bufferedJsonParts` and sets `recoveredByStreaming`. - `scripts/rea.mjs`: after a streamed recovery the launcher keeps the command's exit status instead of forcing 1. Failures already set their status through `logCliCommand`. - Unchanged: - Results that fit are still encoded once, by Incur, with no added work. - Failures and full-output failure envelopes, terminal rendering, token windows and counts, YAML, Markdown, JSON and JSONL keep main's behavior, including the compact capacity failure. - `@toon-format/toon` becomes a direct dependency at 2.3.1, the version already resolved through `incur`. The lockfile changes by one line. - Known gap, by design: if more than one runtime string of TOON has already streamed and a later single line cannot be built (over 1 GB of TOON), output is partial. Handling that would need buffering beyond the limit. Contribution scope: ordinary output fix; maintainer scope decision not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: the shared CLI result output boundary (`cliResultOutput.ts`) and its launcher recovery hook. - Contribution scope fit and linked maintainer decision: fits existing scope; not applicable. - CLI and MCP/tool-catalog contract: a successful TOON result above the string limit, whose lines fit, outside terminal and token modes, is written completely with exit 0 instead of the typed capacity failure. Every other CLI output is unchanged. MCP is unaffected. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: one new direct dependency, already installed transitively at the same version. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests in `tests/boundary/cli/jsonOutput.test.ts`: - Results that fit: - for default format, `--format toon` and `--full-output`, output equals Incur's own output for a nested object, an empty object, `null`, `""`, `false`, `0` and a multiline string; - owned `--filter-output` projections keep main's text and trailing newline, including an empty selection. - Above the limit: - a successful tabular result whose Incur formatting throws `RangeError` is streamed by recovery, exactly as the launcher drives it. Byte count and SHA-256 match the expected TOON, with no typed error. - Main's typed capacity failure kept: - an oversized full-output failure envelope; - oversized TOON on a default-format terminal; - oversized TOON with `--token-count`; - a document with one TOON line longer than the limit. - `tests/boundary/cli/formattingRecovery.test.ts` (main's recovery tests) passes unchanged. - Base reproduction (executed): with `cliResultOutput.ts` from main, only the streaming test fails (1 failed, 55 passed in the file). - Not executed: the launcher exit-status change is source-derived; no real CLI run produced over 512 MB of TOON. No real large application was run. ## Validation performed - `npm run test:focused -- tests/boundary/cli/jsonOutput.test.ts tests/boundary/cli/formattingRecovery.test.ts tests/boundary/cli/dispatcher.test.ts tests/boundary/cli/cliSetup.test.ts`: 4 files, 93 tests passed. - Same `jsonOutput.test.ts` with main's `cliResultOutput.ts`: 1 failed (the streaming test), 55 passed. - `npm run check`: typecheck, lint, format and metadata pass. `knip` reports one unused export and three unused types in untouched files (`javascriptStaticAnalysisHelpers.ts`, `androidJniLibraryFacts.ts`, `androidManifestComponents.ts`, `objcSwiftMetadata.ts`), also present on main. - `npm run docs:check`: passed on the previous revision; this revision changes no documentation or contracts. - Earlier full `npx vitest run --project cli-boundary` on this branch: 6 failures. The five in `analyzeFunctionDetail`, `electronCli` and `ghidraJavaDoctor` fail identically with main's `cliResultOutput.ts` on this host; the npx setup case depends on the npm registry. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Only a successful TOON result that currently becomes a capacity failure changes. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; Linux only. - Package or release metadata impact: new direct dependency `@toon-format/toon@2.3.1`, already shipped through `incur`. - Security, privacy, process, or containment review: output formatting only; no new I/O or side effects. ## Author readiness Human owner: @AniketR10 - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#6419
No description provided.