morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 07:47:29 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #4957] [MERGED] fix(setup): edit the duplicate JSON member that clients read #6694

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

📋 Pull Request Information

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

Base: main ← Head: fix/json-duplicate-member-edit

📝 Commits (2)

  • b6bb75d fix(setup): edit the duplicate JSON member that clients read
  • 59eaa2e Merge remote-tracking branch 'origin/main' into fix/json-duplicate-member-edit

📊 Changes

8 files changed (+365 additions, -92 deletions)

View changed files

📝 src/application/ClientConfigurationDocument.capacity.test.ts (+13 -13)
📝 src/application/ClientConfigurationDocument.ts (+143 -54)
📝 src/application/SetupClientConfiguration.ts (+32 -18)
📝 src/application/SetupClients.ts (+2 -0)
📝 src/application/SetupTypes.ts (+6 -0)
📝 src/application/Uninstall.ts (+22 -6)
➕ tests/acceptance/setup/duplicateJsonMemberSetup.test.ts (+144 -0)
📝 tests/boundary/filesystem/clientConfigurationEnvironment.test.ts (+3 -1)

📄 Description

Summary

Fixes #4952. Setup and uninstall now edit the duplicate JSON member that the parsed document and JSON clients read (the last one), and they refuse an uninstall that would make an earlier shadowed duplicate active.

Problem and expected behavior

parseClientConfiguration reads JSON/JSONC with last-member semantics, the same as JSON.parse and native Claude Code. The shared serializer edited text through jsonc-parser's modify and findNodeAtLocation, and both of those pick the first matching property. As a result, setup on {"mcpServers": {...}, "mcpServers": {...}}, or on a repeated rea leaf, wrote into a member nobody reads, and the run ended in needs_human with failed/readback. Uninstall from a repeated parent table failed the same way. In every case the original file was restored.

Expected: edit the member the client reads, and leave shadowed duplicates and comments as they are. If removing the effective owned rea would make an earlier rea active (owned, foreign or unresolved), keep the configuration unchanged and say why.

Change and scope

  • ClientConfigurationDocument.ts now owns a single last-member locator (effectiveJsonProperty), and every JSON text edit goes through editJsonMember. The first-member modify path is gone. Formatting follows modify's own rule: jsonc-parser format runs over the touched lines.
  • serializeClientConfiguration returns Result<string, ClientConfigurationShadowedMember>. Deleting an effective member that has an earlier same-key sibling returns { kind: "shadowed_member", path }.
  • Uninstall serializes before taking a backup. On shadowed_member it reports failed with a specific explanation and writes nothing, not even a backup.
  • Setup serializes before its backup too. The only way setup deletes is OpenCode's legacy mcp.rea beside V2. That case now maps to a new shadowed_member failure reason with its own message.
  • Scope: an ordinary fix inside existing boundaries; no maintainer scope decision is needed. TOML, YAML and DSH serialization are unchanged.

Contract and boundary impact

  • Semantic owner and earliest changed stage: ClientConfigurationDocument JSON text-edit boundary.

  • Contribution scope fit and linked maintainer decision: not applicable (bug fix inside existing setup/uninstall authority).

  • CLI and MCP/tool-catalog contract: setup client results gain failed/shadowed_member with path. Uninstall keeps failed and adds a new detail text. Tool catalog unchanged.

  • Provider, bridge, target-format, or platform compatibility: JSON/JSONC client formats only.

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

  • Target selection, authority, upstream behavior, and cleanup details: shadowed members are never deleted or activated. A refused uninstall leaves the configuration untouched and creates no backup.

  • Generated metadata, package, or installation impact: none.

  • Read existing files or captured data.

  • Change process memory, registers, files, or configuration.

Evidence and regression coverage

  • Tests added or updated: new tests/acceptance/setup/duplicateJsonMemberSetup.test.ts, which runs the public CLI:

    • Claude Code setup with a repeated server table and with a repeated rea leaf succeeds. The shadowed member stays byte-for-byte, the backup matches the original, and a second setup plans nothing and leaves the file unchanged.
    • Cursor JSONC setup with a repeated table keeps the comments and the shadowed table.
    • Uninstall from a repeated parent table succeeds.
    • Uninstall with a foreign rea followed by an owned rea is refused. The file is unchanged and no backup is created.

    Existing serializer callers in ClientConfigurationDocument.capacity.test.ts and clientConfigurationEnvironment.test.ts were updated to the Result return.

  • Base reproduction: on origin/main (2c4338db1) the issue's CLI repro gave exit 1 with failed/readback for duplicate-parent setup and duplicate-leaf setup, and a failed uninstall (original restored) for duplicate-parent and foreign-then-owned. With this branch the same script gave exit 0 configured for both setups, exit 0 removed for duplicate-parent uninstall, and exit 1 failed for foreign-then-owned, with the file unchanged. All 5 new tests fail when run against origin/main sources.

  • User-visible output for the refused uninstall: Configuration repeats the member at ["mcpServers","rea"]; removing the registration the client reads would activate an earlier duplicate, so no change was made. Remove the duplicate members manually, then rerun uninstall.

  • Remaining proof gaps: native Claude Code and other native clients were not run for this change; the issue's native last-member observation is the only native evidence. Not run: Windows/Linux, and the OpenCode legacy shadowed_member setup path (source-derived only, no dedicated test).

Validation performed

  • npm run build:cached — passed
  • Issue repro script (setup/uninstall with isolated HOME/CLAUDE_CONFIG_DIR) on main and on this branch — results as above
  • npm run test:focused -- tests/acceptance/setup/duplicateJsonMemberSetup.test.ts on origin/main sources — 5 failed (expected)
  • npm run test:focused -- the related setup and client-configuration tests (44 files in tests/acceptance/setup and tests/boundary/filesystem, plus src/application/ClientConfigurationDocument.{capacity,shape}.test.ts and src/application/Setup.{configuration,recovery,planning,initialSnapshot}.test.ts) — 50 files, 738 passed, 2 skipped
  • npm run check:fast — passed
  • npx oxfmt --check on changed files — clean after formatting

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Configurations without duplicate members are edited as before.
  • Real Hopper/Ghidra, browser, or OS coverage: macOS only; native Claude Code not run.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the fix narrows mutation. It never removes or activates a shadowed member.

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/4957 **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/json-duplicate-member-edit` --- ### 📝 Commits (2) - [`b6bb75d`](https://github.com/morluto/rea/commit/b6bb75dfe8f3659152fced1b4550bef06bca25d4) fix(setup): edit the duplicate JSON member that clients read - [`59eaa2e`](https://github.com/morluto/rea/commit/59eaa2edc96aaa8b4c111765ed3befcf8f713fae) Merge remote-tracking branch 'origin/main' into fix/json-duplicate-member-edit ### 📊 Changes **8 files changed** (+365 additions, -92 deletions) <details> <summary>View changed files</summary> 📝 `src/application/ClientConfigurationDocument.capacity.test.ts` (+13 -13) 📝 `src/application/ClientConfigurationDocument.ts` (+143 -54) 📝 `src/application/SetupClientConfiguration.ts` (+32 -18) 📝 `src/application/SetupClients.ts` (+2 -0) 📝 `src/application/SetupTypes.ts` (+6 -0) 📝 `src/application/Uninstall.ts` (+22 -6) ➕ `tests/acceptance/setup/duplicateJsonMemberSetup.test.ts` (+144 -0) 📝 `tests/boundary/filesystem/clientConfigurationEnvironment.test.ts` (+3 -1) </details> ### 📄 Description ## Summary Fixes #4952. Setup and uninstall now edit the duplicate JSON member that the parsed document and JSON clients read (the last one), and they refuse an uninstall that would make an earlier shadowed duplicate active. ## Problem and expected behavior `parseClientConfiguration` reads JSON/JSONC with last-member semantics, the same as `JSON.parse` and native Claude Code. The shared serializer edited text through jsonc-parser's `modify` and `findNodeAtLocation`, and both of those pick the **first** matching property. As a result, setup on `{"mcpServers": {...}, "mcpServers": {...}}`, or on a repeated `rea` leaf, wrote into a member nobody reads, and the run ended in `needs_human` with `failed/readback`. Uninstall from a repeated parent table failed the same way. In every case the original file was restored. Expected: edit the member the client reads, and leave shadowed duplicates and comments as they are. If removing the effective owned `rea` would make an earlier `rea` active (owned, foreign or unresolved), keep the configuration unchanged and say why. ## Change and scope - `ClientConfigurationDocument.ts` now owns a single last-member locator (`effectiveJsonProperty`), and every JSON text edit goes through `editJsonMember`. The first-member `modify` path is gone. Formatting follows `modify`'s own rule: jsonc-parser `format` runs over the touched lines. - `serializeClientConfiguration` returns `Result<string, ClientConfigurationShadowedMember>`. Deleting an effective member that has an earlier same-key sibling returns `{ kind: "shadowed_member", path }`. - Uninstall serializes before taking a backup. On `shadowed_member` it reports `failed` with a specific explanation and writes nothing, not even a backup. - Setup serializes before its backup too. The only way setup deletes is OpenCode's legacy `mcp.rea` beside V2. That case now maps to a new `shadowed_member` failure reason with its own message. - Scope: an ordinary fix inside existing boundaries; no maintainer scope decision is needed. TOML, YAML and DSH serialization are unchanged. ## Contract and boundary impact - Semantic owner and earliest changed stage: `ClientConfigurationDocument` JSON text-edit boundary. - Contribution scope fit and linked maintainer decision: not applicable (bug fix inside existing setup/uninstall authority). - CLI and MCP/tool-catalog contract: setup client results gain `failed/shadowed_member` with `path`. Uninstall keeps `failed` and adds a new detail text. Tool catalog unchanged. - Provider, bridge, target-format, or platform compatibility: JSON/JSONC client formats only. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: shadowed members are never deleted or activated. A refused uninstall leaves the configuration untouched and creates no backup. - Generated metadata, package, or installation impact: none. - [x] Read existing files or captured data. - [x] Change process memory, registers, files, or configuration. ## Evidence and regression coverage - Tests added or updated: new `tests/acceptance/setup/duplicateJsonMemberSetup.test.ts`, which runs the public CLI: - Claude Code setup with a repeated server table and with a repeated `rea` leaf succeeds. The shadowed member stays byte-for-byte, the backup matches the original, and a second setup plans nothing and leaves the file unchanged. - Cursor JSONC setup with a repeated table keeps the comments and the shadowed table. - Uninstall from a repeated parent table succeeds. - Uninstall with a foreign `rea` followed by an owned `rea` is refused. The file is unchanged and no backup is created. Existing serializer callers in `ClientConfigurationDocument.capacity.test.ts` and `clientConfigurationEnvironment.test.ts` were updated to the `Result` return. - Base reproduction: on `origin/main` (`2c4338db1`) the issue's CLI repro gave exit 1 with `failed/readback` for duplicate-parent setup and duplicate-leaf setup, and a failed uninstall (original restored) for duplicate-parent and foreign-then-owned. With this branch the same script gave exit 0 `configured` for both setups, exit 0 `removed` for duplicate-parent uninstall, and exit 1 `failed` for foreign-then-owned, with the file unchanged. All 5 new tests fail when run against `origin/main` sources. - User-visible output for the refused uninstall: `Configuration repeats the member at ["mcpServers","rea"]; removing the registration the client reads would activate an earlier duplicate, so no change was made. Remove the duplicate members manually, then rerun uninstall.` - Remaining proof gaps: native Claude Code and other native clients were **not** run for this change; the issue's native last-member observation is the only native evidence. Not run: Windows/Linux, and the OpenCode legacy `shadowed_member` setup path (source-derived only, no dedicated test). ## Validation performed - `npm run build:cached` — passed - Issue repro script (setup/uninstall with isolated `HOME`/`CLAUDE_CONFIG_DIR`) on main and on this branch — results as above - `npm run test:focused -- tests/acceptance/setup/duplicateJsonMemberSetup.test.ts` on `origin/main` sources — 5 failed (expected) - `npm run test:focused --` the related setup and client-configuration tests (44 files in `tests/acceptance/setup` and `tests/boundary/filesystem`, plus `src/application/ClientConfigurationDocument.{capacity,shape}.test.ts` and `src/application/Setup.{configuration,recovery,planning,initialSnapshot}.test.ts`) — 50 files, 738 passed, 2 skipped - `npm run check:fast` — passed - `npx oxfmt --check` on changed files — clean after formatting ## Compatibility, safety, and release - Breaking changes or migration steps: none. Configurations without duplicate members are edited as before. - Real Hopper/Ghidra, browser, or OS coverage: macOS only; native Claude Code not run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the fix narrows mutation. It never removes or activates a shadowed member. ## 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:20 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/procedure-reference-stacked
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#6694
No description provided.