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 #4937] [MERGED] fix(setup): read signed 64-bit TOML integers losslessly #6681

New issue
Closed
opened 2026-11-01 21:42:16 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:42:16 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4937
Author: @kaoru0822-kitauji
Created: 10/18/2026
Status: ✅ Merged
Merged: 10/18/2026
Merged by: @kaoru0822-kitauji

Base: main ← Head: fix/codex-toml-int64

📝 Commits (1)

  • 3cbb879 fix(setup): read signed 64-bit TOML integers losslessly

📊 Changes

4 files changed (+163 additions, -7 deletions)

View changed files

📝 src/application/ClientConfigurationDocument.ts (+32 -3)
📝 src/application/ClientRegistrationStatus.ts (+10 -3)
📝 src/application/SetupClientConfiguration.ts (+3 -1)
➕ tests/acceptance/setup/tomlConfigurationIntegerRangeCli.test.ts (+118 -0)

📄 Description

Summary

Fixes #4917

Codex and Grok Build setup, doctor and uninstall rejected valid TOML files whose integers were outside JavaScript's safe Number range, such as [history] max_bytes = 9223372036854775807. They reported the file as malformed (integer value cannot be represented losslessly) even though Codex itself accepts it. With this change those integers are read exactly and preserved. Values outside signed Int64 are still rejected before any write.

Problem and expected behavior

  • Trigger: any Codex/Grok config.toml integer with magnitude above 2^53 - 1, for example 9007199254740993 or 9223372036854775807.
  • Violated invariant: TOML 1.0 requires lossless signed 64-bit integers, and setup must preserve unrelated configuration. Instead, ClientConfigurationDocument called smol-toml parse with its default options, and that reader throws on any integer beyond the safe Number range.
  • Expected: Int64 values parse, setup adds REA's entry while keeping them byte-for-byte, and 9223372036854775808 / -9223372036854775809 fail before writes.

Change and scope

  • ClientConfigurationDocument.ts now owns a single parseClientToml reader. It calls parse(text, { integersAsBigInt: "asNeeded" }), so safe integers stay number and larger ones become exact bigint. It then walks the parsed tree iteratively, without argument spreads, and throws a SyntaxError for any bigint outside [-2^63, 2^63 - 1]. smol-toml does not enforce that bound itself.
  • Every TOML parse in this owner now uses that reader: the document read, inline string decoding, and the tomlTextHolds check that compares an edited document against the original values. Without that last one, a preserving edit could fall back to a whole-document rewrite.
  • The inline-table writer (tomlInlineValue) writes bigint values exactly. Before, it wrote them as "".
  • Consumers that see the new value type: setup's positiveTimeout keeps a positive bigint startup_timeout_sec/tool_timeout_sec instead of replacing it with the default. Doctor's registration schema accepts a positive bigint for those two Codex keys, and the timeout advisory compares via Number(...). That comparison is safe because any bigint value is above 2^53 and so above the allowance.
  • Not included: Kimi timeouts are JSON and never bigint, so they are unchanged. There is no dependency, schema, registration identity, transaction or backup change.
  • Contribution scope: ordinary fix within existing boundaries. A maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/application/ClientConfigurationDocument.ts TOML parse, the boundary where client config text is read.
  • Contribution scope fit and linked maintainer decision: in scope for existing setup behavior. Not applicable.
  • CLI and MCP/tool-catalog contract: unchanged. Setup now returns planned/ready instead of needs_human for these valid files. The out-of-range diagnostic now reads integer N is outside the signed 64-bit range.
  • Provider, bridge, target-format, or platform compatibility: Codex and Grok Build TOML clients. Other formats are unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • 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. (Existing setup/uninstall client config writes. The writes themselves are unchanged.)
  • 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 added: tests/acceptance/setup/tomlConfigurationIntegerRangeCli.test.ts runs the real CLI:
    • Int64 max, Int64 min and an underscored hex value under [history]. Covers the setup dry-run (planned, file unchanged), apply (exact backup, original prefix kept), a repeated apply with no actions and identical bytes, and uninstall restoring the original bytes.
    • An inline mcp_servers table holding a foreign 9007199254740993 and an existing REA entry with tool_timeout_sec = 9223372036854775807. The comment and both exact integers are kept, and REA's command is replaced.
    • 9223372036854775808 and -9223372036854775809 produce needs_human with the Int64 diagnostic, exit 1, and leave the file unchanged.
  • Base reproduction: with this PR's three source files reverted to origin/main and the new test kept, all 4 tests failed. The valid cases failed with needs_human. The out-of-range cases still failed closed on main, but with the old "losslessly" diagnostic rather than the Int64 range message.
  • Remaining proof gaps: no native Codex or Grok binary was run here. Doctor's bigint timeout path is covered by type checking and the existing doctor boundary tests, but no new doctor test targets it.

For evidence-bearing changes: not applicable (setup configuration only).

Validation performed

  • npm run test:focused -- tests/acceptance/setup/tomlConfigurationIntegerRangeCli.test.ts tests/acceptance/setup/tomlConfigurationCapacityCli.test.ts src/application/ClientConfigurationDocument.capacity.test.ts src/application/ClientConfigurationDocument.shape.test.ts tests/boundary/filesystem/clientRegistrationStatus.test.ts tests/boundary/filesystem/clientLifecycle.test.ts: 6 files, 99 tests passed (includes the build).
  • The same new test file run against the origin/main sources: 4 failed (expected).
  • npm run check:fast (typecheck + lint): passed.
  • npx oxfmt --check on the changed files: passed. npx oxlint on the changed files: no errors, only existing size/complexity warnings.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. Tested on macOS arm64 only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: out-of-range input still fails before any write. There is no new I/O.

Author readiness

Human owner:

  • 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.

🤖 Generated with Claude Code

🔄 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/4937 **Author:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Created:** 10/18/2026 **Status:** ✅ Merged **Merged:** 10/18/2026 **Merged by:** [@kaoru0822-kitauji](https://github.com/kaoru0822-kitauji) **Base:** `main` ← **Head:** `fix/codex-toml-int64` --- ### 📝 Commits (1) - [`3cbb879`](https://github.com/morluto/rea/commit/3cbb8793ff9352b33cfc7f81177f250a866e7274) fix(setup): read signed 64-bit TOML integers losslessly ### 📊 Changes **4 files changed** (+163 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `src/application/ClientConfigurationDocument.ts` (+32 -3) 📝 `src/application/ClientRegistrationStatus.ts` (+10 -3) 📝 `src/application/SetupClientConfiguration.ts` (+3 -1) ➕ `tests/acceptance/setup/tomlConfigurationIntegerRangeCli.test.ts` (+118 -0) </details> ### 📄 Description ## Summary Fixes #4917 Codex and Grok Build setup, doctor and uninstall rejected valid TOML files whose integers were outside JavaScript's safe Number range, such as `[history] max_bytes = 9223372036854775807`. They reported the file as malformed (`integer value cannot be represented losslessly`) even though Codex itself accepts it. With this change those integers are read exactly and preserved. Values outside signed Int64 are still rejected before any write. ## Problem and expected behavior - Trigger: any Codex/Grok `config.toml` integer with magnitude above 2^53 - 1, for example `9007199254740993` or `9223372036854775807`. - Violated invariant: TOML 1.0 requires lossless signed 64-bit integers, and setup must preserve unrelated configuration. Instead, `ClientConfigurationDocument` called `smol-toml` `parse` with its default options, and that reader throws on any integer beyond the safe Number range. - Expected: Int64 values parse, setup adds REA's entry while keeping them byte-for-byte, and `9223372036854775808` / `-9223372036854775809` fail before writes. ## Change and scope - `ClientConfigurationDocument.ts` now owns a single `parseClientToml` reader. It calls `parse(text, { integersAsBigInt: "asNeeded" })`, so safe integers stay `number` and larger ones become exact `bigint`. It then walks the parsed tree iteratively, without argument spreads, and throws a `SyntaxError` for any bigint outside `[-2^63, 2^63 - 1]`. smol-toml does not enforce that bound itself. - Every TOML parse in this owner now uses that reader: the document read, inline string decoding, and the `tomlTextHolds` check that compares an edited document against the original values. Without that last one, a preserving edit could fall back to a whole-document rewrite. - The inline-table writer (`tomlInlineValue`) writes `bigint` values exactly. Before, it wrote them as `""`. - Consumers that see the new value type: setup's `positiveTimeout` keeps a positive bigint `startup_timeout_sec`/`tool_timeout_sec` instead of replacing it with the default. Doctor's registration schema accepts a positive bigint for those two Codex keys, and the timeout advisory compares via `Number(...)`. That comparison is safe because any bigint value is above 2^53 and so above the allowance. - Not included: Kimi timeouts are JSON and never bigint, so they are unchanged. There is no dependency, schema, registration identity, transaction or backup change. - Contribution scope: ordinary fix within existing boundaries. A maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/application/ClientConfigurationDocument.ts` TOML parse, the boundary where client config text is read. - Contribution scope fit and linked maintainer decision: in scope for existing setup behavior. Not applicable. - CLI and MCP/tool-catalog contract: unchanged. Setup now returns `planned`/`ready` instead of `needs_human` for these valid files. The out-of-range diagnostic now reads `integer N is outside the signed 64-bit range`. - Provider, bridge, target-format, or platform compatibility: Codex and Grok Build TOML clients. Other formats are unchanged. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none. Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. (Existing setup/uninstall client config writes. The writes themselves are unchanged.) - [ ] 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 added: `tests/acceptance/setup/tomlConfigurationIntegerRangeCli.test.ts` runs the real CLI: - Int64 max, Int64 min and an underscored hex value under `[history]`. Covers the setup dry-run (`planned`, file unchanged), apply (exact backup, original prefix kept), a repeated apply with no actions and identical bytes, and uninstall restoring the original bytes. - An inline `mcp_servers` table holding a foreign `9007199254740993` and an existing REA entry with `tool_timeout_sec = 9223372036854775807`. The comment and both exact integers are kept, and REA's command is replaced. - `9223372036854775808` and `-9223372036854775809` produce `needs_human` with the Int64 diagnostic, exit 1, and leave the file unchanged. - Base reproduction: with this PR's three source files reverted to `origin/main` and the new test kept, all 4 tests failed. The valid cases failed with `needs_human`. The out-of-range cases still failed closed on main, but with the old "losslessly" diagnostic rather than the Int64 range message. - Remaining proof gaps: no native Codex or Grok binary was run here. Doctor's bigint timeout path is covered by type checking and the existing doctor boundary tests, but no new doctor test targets it. For evidence-bearing changes: not applicable (setup configuration only). ## Validation performed - `npm run test:focused -- tests/acceptance/setup/tomlConfigurationIntegerRangeCli.test.ts tests/acceptance/setup/tomlConfigurationCapacityCli.test.ts src/application/ClientConfigurationDocument.capacity.test.ts src/application/ClientConfigurationDocument.shape.test.ts tests/boundary/filesystem/clientRegistrationStatus.test.ts tests/boundary/filesystem/clientLifecycle.test.ts`: 6 files, 99 tests passed (includes the build). - The same new test file run against the `origin/main` sources: 4 failed (expected). - `npm run check:fast` (typecheck + lint): passed. - `npx oxfmt --check` on the changed files: passed. `npx oxlint` on the changed files: no errors, only existing size/complexity warnings. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. Tested on macOS arm64 only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: out-of-range input still fails before any write. There is no new I/O. ## Author readiness Human owner: - [ ] 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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:42:16 +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#6681
No description provided.