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 #5054] [CLOSED] fix(setup): admit only syntax Gemini CLI loads in settings.json #6762

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5054
Author: @cpruijsen
Created: 10/18/2026
Status: ❌ Closed

Base: main ← Head: fix/setup-gemini-settings-syntax

📝 Commits (2)

  • 9a7c0b2 fix(setup): admit only syntax Gemini CLI loads in settings.json
  • 0dda76a Merge branch 'main' into fix/setup-gemini-settings-syntax

📊 Changes

4 files changed (+31 additions, -4 deletions)

View changed files

📝 src/application/ClientConfigurationDocument.shape.test.ts (+21 -0)
📝 src/application/ClientConfigurationDocument.ts (+6 -1)
📝 src/application/GeminiClientSettings.ts (+2 -2)
📝 src/application/SupportedClients.ts (+2 -1)

📄 Description

Summary

Gemini CLI loads settings.json with JSON.parse after it strips comments. A trailing comma or a UTF-8 BOM makes that parse fail, and Gemini then loads no settings, so no MCP servers, from that file. REA parsed Gemini settings as JSONC that allows trailing commas and a BOM. For such a file, setup reported ready and wrote into it, and doctor reported the registration aligned.

This gives Gemini CLI its own gemini format with the syntax Gemini accepts. It is the same class of fix as #4944 (Claude Code), but Gemini accepts comments, so this format cannot be strict JSON.

No issue is linked. I found this while comparing each client's native settings reader with REA's parser.

Problem and expected behavior

Smallest trigger: ~/.gemini/settings.json containing {"mcpServers": {"peer": {"command": "/usr/bin/true"}},}.

  • Base: rea setup --client gemini_cli --yes returns ready, writes the registration and keeps the trailing comma. rea doctor --client gemini_cli reports aligned. Gemini CLI cannot parse the result.
  • Expected: setup refuses the file as malformed before any backup or write, and doctor reports invalid. A file with comments still configures, because Gemini CLI strips them.

Change and scope

  • SupportedClients.ts: a gemini format value, used by gemini_cli.
  • ClientConfigurationDocument.ts: for gemini, the JSONC parse runs with allowTrailingComma: false, and a leading BOM is refused. Every other format is unchanged.
  • GeminiClientSettings.ts: the defaults, system and workspace settings reads use gemini instead of json, because Gemini CLI loads all of its settings scopes with the same load function.

Not included: Qwen Code, a Gemini CLI fork. I checked its published package (@qwen-code/qwen-code@0.25.2): it parses settings with JSON.parse(stripJsonComments(stripUtf8Bom(content))), so unlike Gemini CLI it accepts a UTF-8 BOM. Giving Qwen the BOM-refusing gemini format would reject files Qwen can load; a Qwen dialect is a separate change. A BOM-only settings.json still counts as empty, as for every other format.

Scope: an ordinary fix inside the existing setup boundary. A maintainer scope decision is not applicable.

What I chose and the alternative: the regression test is a module-level shape test on parseClientConfiguration with the format taken from the real gemini_cli client definition (21 lines), and the end-to-end setup/doctor/uninstall behavior was verified by hand on the CLI (output below). The alternative, a CLI acceptance test mirroring claudeCodeStrictJsonSetup.test.ts from #4944, would add roughly 70-130 lines; I kept the diff minimal. I can add it if you want parity with the precedent.

Contract and boundary impact

  • Semantic owner and earliest changed stage: client configuration parsing (parseDocument in ClientConfigurationDocument.ts), before planning.

  • Contribution scope fit and linked maintainer decision: not applicable (ordinary fix, follows #4944).

  • CLI and MCP/tool-catalog contract: setup's client format for Gemini CLI changes from "json" to "gemini". For a trailing comma or a BOM, setup and uninstall now return needs_human / failed with a malformed remediation. No tool catalog changes.

  • Provider, bridge, target-format, or platform compatibility: Gemini CLI on every platform.

  • Evidence, artifact, provenance, or reconstruction contract: none.

  • Target selection, authority, upstream behavior, and cleanup details: not applicable.

  • Generated metadata: the generated product catalog's setup_clients[].format for gemini_cli becomes "gemini" (regenerated, not committed). npm run docs:check passes.

  • Read existing files or captured data.

  • Change process memory, registers, files, or configuration. (Setup now refuses a write it used to make.)

Evidence and regression coverage

  • Tests added or updated: src/application/ClientConfigurationDocument.shape.test.ts gets a "Gemini CLI settings syntax" block. It takes the format from the real gemini_cli client definition and checks that comments parse and that a trailing comma and a BOM throw SyntaxError.
  • Base reproduction: with the three src/ files at the merge base and the test file kept, the trailing-comma and BOM cases fail (AssertionError: expected function to throw an error, but it didn't) and the other 8 tests pass. With the change, 10 of 10 pass.
  • End-to-end CLI checks on this change (isolated HOME, macOS): a trailing-comma file and a BOM file each make setup return needs_human with exit 1, leave the file byte-identical, create no .rea.backup, and make doctor report invalid; a comment-only file configures, keeps the comment, and reports aligned; a BOM-only file counts as empty and configures; a trailing comma in the system settings file (via GEMINI_CLI_SYSTEM_SETTINGS_PATH) makes setup refuse and name the system file; uninstall with a malformed user file reports failed and does not change it.
  • Gemini CLI reader (verified against @google/gemini-cli@0.64.0 from npm, the latest on 2026-10-18): one settings load function reads each file with readFileSync(filePath, "utf-8") and parses it with JSON.parse(stripJsonComments(content)); user and workspace scopes call it directly, and system and system-defaults reach it through loadSystemFile. On a parse error it records a settings error and loads {} for that file, so no MCP servers. The bundled strip-json-comments has no trailing-comma option. Running that bundled function: a comment is accepted, a trailing comma fails with "Expected double-quoted property name", and a BOM fails with "Unexpected token".
  • Remaining proof gaps: I did not run the Gemini CLI binary against a file that REA wrote; the client behavior above is source-derived from the published package. The system, defaults and workspace read change has no dedicated new test; the existing workspace-trust and profile suites below exercise those reads. Tests ran on macOS only.

Validation performed

  • npm run test:focused -- src/application/ClientConfigurationDocument.shape.test.ts: 10 passed. With the src/ change at the merge base (isolated worktree, test file kept): 2 failed, 8 passed.
  • npx vitest run --testTimeout=180000 on clientRegistrationStatus, clientLifecycle, setupClientConfigCleanupOwnership, clientConfigurationBom, clientConfigurationDialects (boundary/filesystem), clientProfiles, clientProfileLifecycle (boundary/cli), geminiWorkspaceTrust and clientConfigurationDiagnosticsCli (acceptance): all pass. A first combined run had 4 timeout failures (Test process exceeded its 20000ms deadline from the process fixture, on a loaded machine); each affected file passed in an isolated re-run (clientProfiles 15/15, clientProfileLifecycle 5/5, geminiWorkspaceTrust 5/5).
  • npm run check:fast: passed, re-run uncached with npx turbo run typecheck lint --force.
  • npm run verify:test-discovery: passed.
  • npm run docs:check: passed.
  • npx oxfmt --check on the changed files: passed.
  • Platform: macOS (arm64), Node 26.

Compatibility, safety, and release

  • Breaking changes or migration steps: none for files Gemini CLI can load. A Gemini settings file with a trailing comma or a BOM was already unreadable by Gemini CLI. Setup now asks the user to fix it instead of writing into it.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. Tests ran on macOS only.
  • Package or release metadata impact: the generated product catalog format value for gemini_cli changes (regenerated, not committed).
  • Security, privacy, process, or containment review: none. The change only refuses a write.

Author readiness

Human owner: @cpruijsen

  • 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/5054 **Author:** [@cpruijsen](https://github.com/cpruijsen) **Created:** 10/18/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/setup-gemini-settings-syntax` --- ### 📝 Commits (2) - [`9a7c0b2`](https://github.com/morluto/rea/commit/9a7c0b27a99d14a9a6c7bc0e21bca0c6199eb1dd) fix(setup): admit only syntax Gemini CLI loads in settings.json - [`0dda76a`](https://github.com/morluto/rea/commit/0dda76a38eca35858cae918d733b57baff0a4816) Merge branch 'main' into fix/setup-gemini-settings-syntax ### 📊 Changes **4 files changed** (+31 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/application/ClientConfigurationDocument.shape.test.ts` (+21 -0) 📝 `src/application/ClientConfigurationDocument.ts` (+6 -1) 📝 `src/application/GeminiClientSettings.ts` (+2 -2) 📝 `src/application/SupportedClients.ts` (+2 -1) </details> ### 📄 Description ## Summary Gemini CLI loads `settings.json` with `JSON.parse` after it strips comments. A trailing comma or a UTF-8 BOM makes that parse fail, and Gemini then loads no settings, so no MCP servers, from that file. REA parsed Gemini settings as JSONC that allows trailing commas and a BOM. For such a file, setup reported `ready` and wrote into it, and doctor reported the registration `aligned`. This gives Gemini CLI its own `gemini` format with the syntax Gemini accepts. It is the same class of fix as #4944 (Claude Code), but Gemini accepts comments, so this format cannot be strict JSON. No issue is linked. I found this while comparing each client's native settings reader with REA's parser. ## Problem and expected behavior Smallest trigger: `~/.gemini/settings.json` containing `{"mcpServers": {"peer": {"command": "/usr/bin/true"}},}`. - Base: `rea setup --client gemini_cli --yes` returns `ready`, writes the registration and keeps the trailing comma. `rea doctor --client gemini_cli` reports `aligned`. Gemini CLI cannot parse the result. - Expected: setup refuses the file as malformed before any backup or write, and doctor reports `invalid`. A file with comments still configures, because Gemini CLI strips them. ## Change and scope - `SupportedClients.ts`: a `gemini` format value, used by `gemini_cli`. - `ClientConfigurationDocument.ts`: for `gemini`, the JSONC parse runs with `allowTrailingComma: false`, and a leading BOM is refused. Every other format is unchanged. - `GeminiClientSettings.ts`: the defaults, system and workspace settings reads use `gemini` instead of `json`, because Gemini CLI loads all of its settings scopes with the same `load` function. Not included: Qwen Code, a Gemini CLI fork. I checked its published package (`@qwen-code/qwen-code@0.25.2`): it parses settings with `JSON.parse(stripJsonComments(stripUtf8Bom(content)))`, so unlike Gemini CLI it accepts a UTF-8 BOM. Giving Qwen the BOM-refusing `gemini` format would reject files Qwen can load; a Qwen dialect is a separate change. A BOM-only `settings.json` still counts as empty, as for every other format. Scope: an ordinary fix inside the existing setup boundary. A maintainer scope decision is not applicable. What I chose and the alternative: the regression test is a module-level shape test on `parseClientConfiguration` with the format taken from the real `gemini_cli` client definition (21 lines), and the end-to-end setup/doctor/uninstall behavior was verified by hand on the CLI (output below). The alternative, a CLI acceptance test mirroring `claudeCodeStrictJsonSetup.test.ts` from #4944, would add roughly 70-130 lines; I kept the diff minimal. I can add it if you want parity with the precedent. ## Contract and boundary impact - Semantic owner and earliest changed stage: client configuration parsing (`parseDocument` in `ClientConfigurationDocument.ts`), before planning. - Contribution scope fit and linked maintainer decision: not applicable (ordinary fix, follows #4944). - CLI and MCP/tool-catalog contract: setup's client `format` for Gemini CLI changes from `"json"` to `"gemini"`. For a trailing comma or a BOM, setup and uninstall now return `needs_human` / `failed` with a `malformed` remediation. No tool catalog changes. - Provider, bridge, target-format, or platform compatibility: Gemini CLI on every platform. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata: the generated product catalog's `setup_clients[].format` for `gemini_cli` becomes `"gemini"` (regenerated, not committed). `npm run docs:check` passes. - [x] Read existing files or captured data. - [x] Change process memory, registers, files, or configuration. (Setup now refuses a write it used to make.) ## Evidence and regression coverage - Tests added or updated: `src/application/ClientConfigurationDocument.shape.test.ts` gets a "Gemini CLI settings syntax" block. It takes the format from the real `gemini_cli` client definition and checks that comments parse and that a trailing comma and a BOM throw `SyntaxError`. - Base reproduction: with the three `src/` files at the merge base and the test file kept, the trailing-comma and BOM cases fail (`AssertionError: expected function to throw an error, but it didn't`) and the other 8 tests pass. With the change, 10 of 10 pass. - End-to-end CLI checks on this change (isolated HOME, macOS): a trailing-comma file and a BOM file each make setup return `needs_human` with exit 1, leave the file byte-identical, create no `.rea.backup`, and make doctor report `invalid`; a comment-only file configures, keeps the comment, and reports `aligned`; a BOM-only file counts as empty and configures; a trailing comma in the system settings file (via `GEMINI_CLI_SYSTEM_SETTINGS_PATH`) makes setup refuse and name the system file; uninstall with a malformed user file reports `failed` and does not change it. - Gemini CLI reader (verified against `@google/gemini-cli@0.64.0` from npm, the latest on 2026-10-18): one settings `load` function reads each file with `readFileSync(filePath, "utf-8")` and parses it with `JSON.parse(stripJsonComments(content))`; user and workspace scopes call it directly, and system and system-defaults reach it through `loadSystemFile`. On a parse error it records a settings error and loads `{}` for that file, so no MCP servers. The bundled strip-json-comments has no trailing-comma option. Running that bundled function: a comment is accepted, a trailing comma fails with "Expected double-quoted property name", and a BOM fails with "Unexpected token". - Remaining proof gaps: I did not run the Gemini CLI binary against a file that REA wrote; the client behavior above is source-derived from the published package. The system, defaults and workspace read change has no dedicated new test; the existing workspace-trust and profile suites below exercise those reads. Tests ran on macOS only. ## Validation performed - `npm run test:focused -- src/application/ClientConfigurationDocument.shape.test.ts`: 10 passed. With the `src/` change at the merge base (isolated worktree, test file kept): 2 failed, 8 passed. - `npx vitest run --testTimeout=180000` on `clientRegistrationStatus`, `clientLifecycle`, `setupClientConfigCleanupOwnership`, `clientConfigurationBom`, `clientConfigurationDialects` (boundary/filesystem), `clientProfiles`, `clientProfileLifecycle` (boundary/cli), `geminiWorkspaceTrust` and `clientConfigurationDiagnosticsCli` (acceptance): all pass. A first combined run had 4 timeout failures (`Test process exceeded its 20000ms deadline` from the process fixture, on a loaded machine); each affected file passed in an isolated re-run (clientProfiles 15/15, clientProfileLifecycle 5/5, geminiWorkspaceTrust 5/5). - `npm run check:fast`: passed, re-run uncached with `npx turbo run typecheck lint --force`. - `npm run verify:test-discovery`: passed. - `npm run docs:check`: passed. - `npx oxfmt --check` on the changed files: passed. - Platform: macOS (arm64), Node 26. ## Compatibility, safety, and release - Breaking changes or migration steps: none for files Gemini CLI can load. A Gemini settings file with a trailing comma or a BOM was already unreadable by Gemini CLI. Setup now asks the user to fix it instead of writing into it. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. Tests ran on macOS only. - Package or release metadata impact: the generated product catalog format value for `gemini_cli` changes (regenerated, not committed). - Security, privacy, process, or containment review: none. The change only refuses a write. ## Author readiness Human owner: @cpruijsen - [x] 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. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [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-11-01 21:42:51 +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#6762
No description provided.