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 #3785] [MERGED] fix(hermes): detach aliased server tables before editing #5896

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3785
Author: @CmsChase
Created: 10/15/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: fix/hermes-aliased-server-tables

📝 Commits (2)

  • f4e0ccd fix(hermes): detach aliased server tables before editing
  • 347c6cd test(setup): isolate Hermes flows from host Hopper detection

📊 Changes

3 files changed (+420 additions, -8 deletions)

View changed files

📝 src/application/HermesConfigurationYaml.test.ts (+51 -0)
📝 src/application/HermesConfigurationYaml.ts (+54 -8)
➕ tests/acceptance/setup/hermesAliasedTableSetup.test.ts (+315 -0)

📄 Description

fix(hermes): detach aliased server tables before editing

Summary

Fixes #3320. Allow approved Hermes setup and owned-registration removal to edit an aliased mcp_servers table while preserving its source and other consumers.

Problem and expected behavior

Hermes configuration admission resolves mcp_servers: *servers into a valid mapping, but the YAML writer cannot edit an Alias node as a collection. Setup can create a backup and then fail with needs_human; uninstall of an owned registration in that table also fails. Both operations should edit the selected registration without changing the referenced defaults or unrelated consumers.

Change and scope

Materialize aliased parent mappings along the edit path. Resolve copied references against the original document and remove anchors from private copies, preserving bindings even when anchor names are reused. Retain source formatting and comments; return the original bytes when a successful deletion removes no node. Cyclic and unresolved copied aliases remain rejected.

This is an ordinary configuration fix within the existing setup/uninstall boundary; an advance maintainer scope decision is not applicable. The separate anchored-registration-leaf problem in explicit tables (#3325) remains outside this change.

Contract and boundary impact

  • Semantic owner and earliest changed stage: HermesConfigurationYaml, YAML AST editing after configuration admission.
  • Contribution scope fit and linked maintainer decision: ordinary existing client configuration behavior; not applicable.
  • CLI and MCP/tool-catalog contract: aliased-table setup can reach ready/aligned, repeated setup plans no actions, and owned uninstall succeeds. No command, schema or catalog change.
  • Provider, bridge, target-format, or platform compatibility: Hermes YAML 1.1 and explicit 1.2 covered on Windows x64; no installed Hermes loader or POSIX verification.
  • Evidence, artifact, provenance, or reconstruction contract: source mappings, shared consumers, comments, exact backups and successful no-op bytes are covered; no analysis-evidence change.
  • Target selection, authority, upstream behavior, and cleanup details: existing approved setup and owned-registration uninstall determine writes. Missing registrations still skip public uninstall without a backup.
  • Generated metadata, package, or installation impact: no dependency, metadata, package-layout or installation-policy changes.

Expected effects of the changed configuration workflow:

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

Evidence and regression coverage

  • Twelve real CLI cases cover add/refresh, repeated setup, doctor, uninstall/repeated uninstall, exact backups, comments, foreign consumers, shadowed anchors and invalid-input refusal across both YAML versions. On unmodified 9a44fea3479a2ad463fdad2b14e86b412717f771, seven fail and five pass; with the fix, all twelve pass.

  • Twenty YAML owner tests pass, including ten exact-byte no-op cases for aliased/nested tables, shadowed anchors, shared consumers and explicit CRLF flow mappings. The implementation without the no-op guard fails all ten byte assertions. Upstream direct alias deletion instead throws a collection error; upstream explicit-map deletion normalizes formatting.

  • Actual CLI replay confirms aliased-table setup/repeat/doctor exits change from 1/1/1 to 0/0/0, with ready/aligned diagnostics. Eight additional baseline/fixed absent-registration uninstall calls all return exit 0 and skipped, preserving bytes without creating backups.

  • The same fixed owner/CLI selection passes 32/32 on the separately tested main revision 2a9252e4e6e04d8f24dda816ea61b76c75005e39.

  • Remaining proof gaps: installed Hermes/Python loader, real providers, POSIX, full suite/CI and complete installed-package verification.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

Windows x64, Node 24.18.0, npm 11.16.0, locked dependencies:

  • npm run test:focused -- src/application/HermesConfigurationYaml.test.ts tests/acceptance/setup/hermesAliasedTableSetup.test.ts — 32 passed. The final test-group-only split was independently rerun: owner 20/20 passed.
  • npm run test:focused -- src/application/HermesConfigurationYaml.test.ts tests/boundary/filesystem/hermesClientConfiguration.test.ts tests/acceptance/setup/hermesClientSetup.test.ts — fixed 62 passed / 2 failed, including twelve new owner cases; unmodified baseline 50 passed / the same 2 failed. Complete failure assertions match: Windows drive-prefix expectations (D:\custom\agent versus \custom\agent, and D:\srv\hermes\config.yaml versus \srv\hermes\config.yaml). Existing Hermes CLI tests pass 13/13 on both.
  • npm run check — passed: typecheck, formatting, lint, knip, metadata, module boundaries and architecture guards; 0 lint errors, with only the same pre-existing timestamp-parser warning in changed files.
  • npm run verify:test-discovery — 1299 test files discovered exactly once.
  • git diff --check and the normal staged formatting/lint commit hook — passed. The committed changes are byte-identical to the reviewed diff.
  • Earlier npm run verify:package / npm run verify:package:windows runs on baseline and fixed code were blocked by Windows spawn npm ENOENT and the absent native/windows/build/manifest.json, respectively. These were not rerun after the YAML-only no-op correction; complete package verification remains unavailable.

Compatibility, safety, and release

  • Breaking changes or migration steps: none intended; valid aliased tables become editable and successful empty deletions preserve source bytes.
  • Real Hopper/Ghidra, browser, or OS coverage: isolated Windows REA CLI configurations; no installed Hermes client, live provider or POSIX claim.
  • Package or release metadata impact: unchanged; packaging limitations are recorded above.
  • Security, privacy, process, or containment review: existing admission/approval/ownership checks remain in force; invalid copied references still fail before publishing an update. No new target execution or network capability.

Author readiness

Human owner: @CmsChase

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

Maintainer blocker verification

The public Hermes acceptance comparison did not reproduce the earlier timeout concern. On this host, current main passed 7/12 cases; the prior PR passed 10/12, with the two remaining failures caused by ambient Hopper autodetection in setup. The test fixture now supplies HOPPER_LAUNCHER_PATH=process.execPath, isolating the intended setup input without changing production code. All 12 acceptance cases then passed (14.31s), as did npm run check:fast.

These are local CLI/configuration acceptance results, not installed Hermes-client or real-provider verification. Earlier Windows packaging gaps remain unverified by this pass. The former integration hold based on an unexplained timeout is superseded by the completed functional comparison.

🔄 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/3785 **Author:** [@CmsChase](https://github.com/CmsChase) **Created:** 10/15/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/hermes-aliased-server-tables` --- ### 📝 Commits (2) - [`f4e0ccd`](https://github.com/morluto/rea/commit/f4e0ccd1d15cdba4d8727080ef4995dfe6da9773) fix(hermes): detach aliased server tables before editing - [`347c6cd`](https://github.com/morluto/rea/commit/347c6cd294ac3df540c8eef42ba055866df20071) test(setup): isolate Hermes flows from host Hopper detection ### 📊 Changes **3 files changed** (+420 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `src/application/HermesConfigurationYaml.test.ts` (+51 -0) 📝 `src/application/HermesConfigurationYaml.ts` (+54 -8) ➕ `tests/acceptance/setup/hermesAliasedTableSetup.test.ts` (+315 -0) </details> ### 📄 Description # fix(hermes): detach aliased server tables before editing ## Summary Fixes #3320. Allow approved Hermes setup and owned-registration removal to edit an aliased `mcp_servers` table while preserving its source and other consumers. ## Problem and expected behavior Hermes configuration admission resolves `mcp_servers: *servers` into a valid mapping, but the YAML writer cannot edit an Alias node as a collection. Setup can create a backup and then fail with `needs_human`; uninstall of an owned registration in that table also fails. Both operations should edit the selected registration without changing the referenced defaults or unrelated consumers. ## Change and scope Materialize aliased parent mappings along the edit path. Resolve copied references against the original document and remove anchors from private copies, preserving bindings even when anchor names are reused. Retain source formatting and comments; return the original bytes when a successful deletion removes no node. Cyclic and unresolved copied aliases remain rejected. This is an ordinary configuration fix within the existing setup/uninstall boundary; an advance maintainer scope decision is not applicable. The separate anchored-registration-leaf problem in explicit tables (#3325) remains outside this change. ## Contract and boundary impact - Semantic owner and earliest changed stage: `HermesConfigurationYaml`, YAML AST editing after configuration admission. - Contribution scope fit and linked maintainer decision: ordinary existing client configuration behavior; not applicable. - CLI and MCP/tool-catalog contract: aliased-table setup can reach `ready`/`aligned`, repeated setup plans no actions, and owned uninstall succeeds. No command, schema or catalog change. - Provider, bridge, target-format, or platform compatibility: Hermes YAML 1.1 and explicit 1.2 covered on Windows x64; no installed Hermes loader or POSIX verification. - Evidence, artifact, provenance, or reconstruction contract: source mappings, shared consumers, comments, exact backups and successful no-op bytes are covered; no analysis-evidence change. - Target selection, authority, upstream behavior, and cleanup details: existing approved setup and owned-registration uninstall determine writes. Missing registrations still skip public uninstall without a backup. - Generated metadata, package, or installation impact: no dependency, metadata, package-layout or installation-policy changes. Expected effects of the changed configuration workflow: - [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. - [ ] 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 - Twelve real CLI cases cover add/refresh, repeated setup, doctor, uninstall/repeated uninstall, exact backups, comments, foreign consumers, shadowed anchors and invalid-input refusal across both YAML versions. On unmodified `9a44fea3479a2ad463fdad2b14e86b412717f771`, seven fail and five pass; with the fix, all twelve pass. - Twenty YAML owner tests pass, including ten exact-byte no-op cases for aliased/nested tables, shadowed anchors, shared consumers and explicit CRLF flow mappings. The implementation without the no-op guard fails all ten byte assertions. Upstream direct alias deletion instead throws a collection error; upstream explicit-map deletion normalizes formatting. - Actual CLI replay confirms aliased-table setup/repeat/doctor exits change from `1/1/1` to `0/0/0`, with `ready`/`aligned` diagnostics. Eight additional baseline/fixed absent-registration uninstall calls all return exit 0 and `skipped`, preserving bytes without creating backups. - The same fixed owner/CLI selection passes 32/32 on the separately tested main revision `2a9252e4e6e04d8f24dda816ea61b76c75005e39`. - Remaining proof gaps: installed Hermes/Python loader, real providers, POSIX, full suite/CI and complete installed-package verification. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed Windows x64, Node 24.18.0, npm 11.16.0, locked dependencies: - `npm run test:focused -- src/application/HermesConfigurationYaml.test.ts tests/acceptance/setup/hermesAliasedTableSetup.test.ts` — 32 passed. The final test-group-only split was independently rerun: owner 20/20 passed. - `npm run test:focused -- src/application/HermesConfigurationYaml.test.ts tests/boundary/filesystem/hermesClientConfiguration.test.ts tests/acceptance/setup/hermesClientSetup.test.ts` — fixed 62 passed / 2 failed, including twelve new owner cases; unmodified baseline 50 passed / the same 2 failed. Complete failure assertions match: Windows drive-prefix expectations (`D:\custom\agent` versus `\custom\agent`, and `D:\srv\hermes\config.yaml` versus `\srv\hermes\config.yaml`). Existing Hermes CLI tests pass 13/13 on both. - `npm run check` — passed: typecheck, formatting, lint, knip, metadata, module boundaries and architecture guards; 0 lint errors, with only the same pre-existing timestamp-parser warning in changed files. - `npm run verify:test-discovery` — 1299 test files discovered exactly once. - `git diff --check` and the normal staged formatting/lint commit hook — passed. The committed changes are byte-identical to the reviewed diff. - Earlier `npm run verify:package` / `npm run verify:package:windows` runs on baseline and fixed code were blocked by Windows `spawn npm ENOENT` and the absent `native/windows/build/manifest.json`, respectively. These were not rerun after the YAML-only no-op correction; complete package verification remains unavailable. ## Compatibility, safety, and release - Breaking changes or migration steps: none intended; valid aliased tables become editable and successful empty deletions preserve source bytes. - Real Hopper/Ghidra, browser, or OS coverage: isolated Windows REA CLI configurations; no installed Hermes client, live provider or POSIX claim. - Package or release metadata impact: unchanged; packaging limitations are recorded above. - Security, privacy, process, or containment review: existing admission/approval/ownership checks remain in force; invalid copied references still fail before publishing an update. No new target execution or network capability. ## Author readiness Human owner: @CmsChase - [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 - [ ] 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. <!-- maintainer-blocker-review --> ### Maintainer blocker verification The public Hermes acceptance comparison did not reproduce the earlier timeout concern. On this host, current main passed 7/12 cases; the prior PR passed 10/12, with the two remaining failures caused by ambient Hopper autodetection in setup. The test fixture now supplies `HOPPER_LAUNCHER_PATH=process.execPath`, isolating the intended setup input without changing production code. All 12 acceptance cases then passed (14.31s), as did `npm run check:fast`. These are local CLI/configuration acceptance results, not installed Hermes-client or real-provider verification. Earlier Windows packaging gaps remain unverified by this pass. The former integration hold based on an unexplained timeout is superseded by the completed functional comparison. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:10: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#5896
No description provided.