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 #6587] [CLOSED] fix(setup): write the native OpenCode table inherited from any layer #7380

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6587
Author: @kittimzhe
Created: 10/23/2026
Status: ❌ Closed

Base: main ← Head: fix/opencode-inherited-native-table

📝 Commits (1)

  • 5491d3a fix(setup): write the native OpenCode table inherited from any layer

📊 Changes

3 files changed (+166 additions, -65 deletions)

View changed files

📝 src/application/ClientConfigurationDocument.ts (+29 -0)
📝 src/application/SetupClientConfiguration.ts (+15 -2)
📝 tests/acceptance/setup/opencodeV2ClientSetup.test.ts (+122 -63)

📄 Description

Fixes #6573

Summary

Setup decided which OpenCode table to write from the target file's own content, so an upper opencode.json without an mcp table (or a missing upper file) made approved setup write a legacy V1 mcp.rea member while the client loads the native mcp.servers table inherited from a lower layer: configuration reported configured and later already_current, but the effective registration inspection stayed disabled/stale. The write view now promotes a V1 target document to its native V2 view when any applicable layer has the native table.

Problem and expected behavior

  • Smallest trigger (from the issue, reproduced locally before the fix): lower config.json holds a disabled native V2 registration; upper opencode.json holds only {"theme":"system"} or is absent. configureClientConfiguration writes a V1 mcp.rea entry with enabled: true into the upper file, returns configured, and the following inspection reports already_current — while readClientRegistrationInspections reports activation: "disabled", state: "stale". The passing control (upper file with an explicit mcp.servers table) is the shape #3469/#3318 already covered.
  • Violated invariant: setup must produce an enabled effective registration and agree with the registration reader about whether another update is required. Per the documented OpenCode configuration contract, setup uses native V2 tables where present and doctor checks the merged user registration.
  • Root cause: parseClientConfiguration correctly derives each file's dialect from its own content, but the write path used the target file's dialect to choose the table shape, ignoring the effective layered view's precedence (native table from any layer wins over legacy members, per effectiveClientServer).

Change and scope

  • src/application/ClientConfigurationDocument.ts exports opencodeNativeClientConfiguration, the native V2 view of a V1 document (native mcp.servers table, V1 members kept as legacy so withClientServers removes REA's legacy entry beside the native table). It lives beside the dialect derivation it mirrors.
  • src/application/SetupClientConfiguration.ts (configureClientDocument): when any source in files.value has dialect opencode_v2, the write view promotes the parsed target document (and the pre-parse existing view used for policy evaluation). The promoted dialect makes the desired entry take the existing opencode_v2 generation path, so the written entry carries disabled: false (the #3318 inherited-flag override).
  • Reading semantics (effectiveClientConfiguration, inspection) are unchanged; fresh setups where no layer has a native table keep writing the V1 member exactly as before; only the inherited-native-table scenario changes shape. The JSONC writer path and backup behavior are untouched.
  • Intentionally not included: changing the default table shape for brand-new OpenCode setups (no layers with native tables) — that is a behavior decision beyond this report's scope; the issue's workaround-equivalent cases are the inherited-table ones fixed here.
  • Contribution scope: ordinary fix within existing boundaries — no maintainer scope decision required ("not applicable").

Contract and boundary impact

  • Semantic owner and earliest changed stage: the setup write plan (src/application/SetupClientConfiguration.ts) consuming the dialect owner's new V2 view (src/application/ClientConfigurationDocument.ts).
  • CLI and MCP/tool-catalog contract: rea setup --client opencode now writes mcp.servers.rea with disabled: false when any applicable layer has a native table; doctor reports aligned/enabled after setup instead of stale/disabled. No schema or tool changes.
  • Provider, bridge, target-format, or platform compatibility: OpenCode only; other clients untouched.
  • Evidence, artifact, provenance contract: none.
  • Generated metadata: none.

Expected effects:

  • Read existing files or captured data. (the probe reads and writes synthetic user configurations only)
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration. (synthetic isolated HOME fixtures only; no real client configuration is modified)
  • 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

  • RED (executed on this machine, current main 45a411e8f before the fix): the issue's production-function probe ran in three isolated HOMEs with locked dependencies and Node 24.22.1. plain and missing modes reproduced the report exactly — setup wrote V1 mcp.rea with enabled: true, returned configured, inspection already_current, while effective registration reported stale/disabled; v2-control passed.
  • GREEN (executed after the fix): all three modes report aligned/enabled; the upper file receives the native mcp.servers.rea with disabled: false; theme and the lower file remain byte-identical.
  • Tests added (tests/acceptance/setup/opencodeV2ClientSetup.test.ts): the layered matrix extends to an upper file without a native table (plain) across the existing disabled×JSONC combinations, plus a missing upper-file case asserting the native write, idempotent re-run, and doctor aligned. All run through the real CLI (rea setup --client opencode --skill=false --yes --json).
  • Base reproduction: the issue's probe and source analysis were rechecked against current main before fixing; the parse-side dialect derivation and the #3318 disabled override are unchanged.
  • Remaining proof gaps: Linux and Windows hosts were not executed here (the fixtures are platform-neutral JSON handling); a real OpenCode session loading the written configuration was not run.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable. (executed probe vs source-derived reasoning is labeled)
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm ci — locked dependencies, Node 24.22.1 (.nvmrc), macOS 14 arm64.
  • Issue's probe (three isolated HOME trials), before and after the fix — RED/GREEN output quoted above.
  • npm run test:focused -- tests/acceptance/setup/opencodeV2ClientSetup.test.ts — 10 passed (8 matrix + missing + the pre-existing malformed-lower case).
  • npm run test:focused -- tests/acceptance/setup/duplicateJsonMemberSetup.test.ts tests/acceptance/setup/clientConfigurationDiagnosticsCli.test.ts tests/boundary/filesystem/clientConfigurationEnvironment.test.ts tests/boundary/filesystem/clientLifecycle.test.ts — 121 passed, 10 skipped.
  • npm run check:fast — typecheck + lint pass (uncached).

Compatibility, safety, and release

  • Breaking changes or migration steps: none. The write-shape change only fires when an inherited native table exists; existing native-table setups were already written natively.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable — no provider is launched; HOPPER_LAUNCHER_PATH points at an absent path in the fixtures.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @kittimzhe

  • 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: Fixes #6573.
  • Tests cover changed observable behavior and meaningful failure paths. (plain/missing matrix through the real CLI, idempotence, doctor alignment, plus the pre-existing malformed-lower guard)
  • Owning docs, contracts, and generated metadata are updated where needed. (the documented native-table contract is what this restores; no doc enumerates the write-shape decision)
  • User-visible CLI/MCP changes include representative output. (RED/GREEN probe output quoted in Evidence)
  • 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/6587 **Author:** [@kittimzhe](https://github.com/kittimzhe) **Created:** 10/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/opencode-inherited-native-table` --- ### 📝 Commits (1) - [`5491d3a`](https://github.com/morluto/rea/commit/5491d3ac969447d6585c3c169e591b30568863a4) fix(setup): write the native OpenCode table inherited from any layer ### 📊 Changes **3 files changed** (+166 additions, -65 deletions) <details> <summary>View changed files</summary> 📝 `src/application/ClientConfigurationDocument.ts` (+29 -0) 📝 `src/application/SetupClientConfiguration.ts` (+15 -2) 📝 `tests/acceptance/setup/opencodeV2ClientSetup.test.ts` (+122 -63) </details> ### 📄 Description Fixes #6573 ## Summary Setup decided which OpenCode table to write from the target file's own content, so an upper `opencode.json` without an `mcp` table (or a missing upper file) made approved setup write a legacy V1 `mcp.rea` member while the client loads the native `mcp.servers` table inherited from a lower layer: configuration reported `configured` and later `already_current`, but the effective registration inspection stayed `disabled`/`stale`. The write view now promotes a V1 target document to its native V2 view when any applicable layer has the native table. ## Problem and expected behavior - Smallest trigger (from the issue, reproduced locally before the fix): lower `config.json` holds a disabled native V2 registration; upper `opencode.json` holds only `{"theme":"system"}` or is absent. `configureClientConfiguration` writes a V1 `mcp.rea` entry with `enabled: true` into the upper file, returns `configured`, and the following inspection reports `already_current` — while `readClientRegistrationInspections` reports `activation: "disabled"`, `state: "stale"`. The passing control (upper file with an explicit `mcp.servers` table) is the shape #3469/#3318 already covered. - Violated invariant: setup must produce an enabled effective registration and agree with the registration reader about whether another update is required. Per the documented OpenCode configuration contract, setup uses native V2 tables where present and doctor checks the merged user registration. - Root cause: `parseClientConfiguration` correctly derives each file's dialect from its own content, but the write path used the target file's dialect to choose the table shape, ignoring the effective layered view's precedence (native table from any layer wins over legacy members, per `effectiveClientServer`). ## Change and scope - `src/application/ClientConfigurationDocument.ts` exports `opencodeNativeClientConfiguration`, the native V2 view of a V1 document (native `mcp.servers` table, V1 members kept as legacy so `withClientServers` removes REA's legacy entry beside the native table). It lives beside the dialect derivation it mirrors. - `src/application/SetupClientConfiguration.ts` (`configureClientDocument`): when any source in `files.value` has dialect `opencode_v2`, the write view promotes the parsed target document (and the pre-parse `existing` view used for policy evaluation). The promoted dialect makes the desired entry take the existing `opencode_v2` generation path, so the written entry carries `disabled: false` (the #3318 inherited-flag override). - Reading semantics (`effectiveClientConfiguration`, inspection) are unchanged; fresh setups where no layer has a native table keep writing the V1 member exactly as before; only the inherited-native-table scenario changes shape. The JSONC writer path and backup behavior are untouched. - Intentionally not included: changing the default table shape for brand-new OpenCode setups (no layers with native tables) — that is a behavior decision beyond this report's scope; the issue's workaround-equivalent cases are the inherited-table ones fixed here. - Contribution scope: ordinary fix within existing boundaries — no maintainer scope decision required ("not applicable"). ## Contract and boundary impact - Semantic owner and earliest changed stage: the setup write plan (`src/application/SetupClientConfiguration.ts`) consuming the dialect owner's new V2 view (`src/application/ClientConfigurationDocument.ts`). - CLI and MCP/tool-catalog contract: `rea setup --client opencode` now writes `mcp.servers.rea` with `disabled: false` when any applicable layer has a native table; `doctor` reports `aligned`/enabled after setup instead of `stale`/disabled. No schema or tool changes. - Provider, bridge, target-format, or platform compatibility: OpenCode only; other clients untouched. - Evidence, artifact, provenance contract: none. - Generated metadata: none. Expected effects: - [x] Read existing files or captured data. *(the probe reads and writes synthetic user configurations only)* - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. *(synthetic isolated HOME fixtures only; no real client configuration is modified)* - [ ] 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 - RED (executed on this machine, current main `45a411e8f` before the fix): the issue's production-function probe ran in three isolated HOMEs with locked dependencies and Node 24.22.1. `plain` and `missing` modes reproduced the report exactly — setup wrote V1 `mcp.rea` with `enabled: true`, returned `configured`, inspection `already_current`, while effective registration reported `stale`/`disabled`; `v2-control` passed. - GREEN (executed after the fix): all three modes report `aligned`/`enabled`; the upper file receives the native `mcp.servers.rea` with `disabled: false`; `theme` and the lower file remain byte-identical. - Tests added (`tests/acceptance/setup/opencodeV2ClientSetup.test.ts`): the layered matrix extends to an upper file without a native table (`plain`) across the existing disabled×JSONC combinations, plus a `missing` upper-file case asserting the native write, idempotent re-run, and doctor `aligned`. All run through the real CLI (`rea setup --client opencode --skill=false --yes --json`). - Base reproduction: the issue's probe and source analysis were rechecked against current main before fixing; the parse-side dialect derivation and the #3318 disabled override are unchanged. - Remaining proof gaps: Linux and Windows hosts were not executed here (the fixtures are platform-neutral JSON handling); a real OpenCode session loading the written configuration was not run. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. *(executed probe vs source-derived reasoning is labeled)* - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm ci` — locked dependencies, Node 24.22.1 (`.nvmrc`), macOS 14 arm64. - Issue's probe (three isolated HOME trials), before and after the fix — RED/GREEN output quoted above. - `npm run test:focused -- tests/acceptance/setup/opencodeV2ClientSetup.test.ts` — 10 passed (8 matrix + missing + the pre-existing malformed-lower case). - `npm run test:focused -- tests/acceptance/setup/duplicateJsonMemberSetup.test.ts tests/acceptance/setup/clientConfigurationDiagnosticsCli.test.ts tests/boundary/filesystem/clientConfigurationEnvironment.test.ts tests/boundary/filesystem/clientLifecycle.test.ts` — 121 passed, 10 skipped. - `npm run check:fast` — typecheck + lint pass (uncached). ## Compatibility, safety, and release - Breaking changes or migration steps: none. The write-shape change only fires when an inherited native table exists; existing native-table setups were already written natively. - Real Hopper/Ghidra, browser, or OS coverage: not applicable — no provider is launched; `HOPPER_LAUNCHER_PATH` points at an absent path in the fixtures. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @kittimzhe - [ ] 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. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked: Fixes #6573. - [x] Tests cover changed observable behavior and meaningful failure paths. *(plain/missing matrix through the real CLI, idempotence, doctor alignment, plus the pre-existing malformed-lower guard)* - [x] Owning docs, contracts, and generated metadata are updated where needed. *(the documented native-table contract is what this restores; no doc enumerates the write-shape decision)* - [x] User-visible CLI/MCP changes include representative output. *(RED/GREEN probe output quoted in Evidence)* - [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:47:27 +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#7380
No description provided.