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 #4145] [MERGED] docs(hermes): explain nested-home routing and preview limits #6085

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4145
Author: @hichipli
Created: 10/15/2026
Status: ✅ Merged
Merged: 10/27/2026
Merged by: @morluto

Base: main ← Head: docs/hermes-nested-profile-selection

📝 Commits (6)

  • 7e2fea7 docs(hermes): clarify sticky profiles for nested homes
  • 8b54071 docs(hermes): qualify nested homes beneath default symlinks
  • 8c3e357 docs(hermes): cover canonicalized ancestor paths
  • 788bc16 docs(hermes): clarify both missing-path containment errors
  • e9b1018 docs(hermes): resolve upstream test imports
  • 474d3da docs(hermes): align nested-home guidance with current routing

📊 Changes

2 files changed (+240 additions, -11 deletions)

View changed files

📝 docs/client-configuration.md (+38 -9)
📝 tests/acceptance/setup/hermesClientSetup.test.ts (+202 -2)

📄 Description

Summary

Explain the destinations REA currently previews for nested Hermes homes, warn about a resolver-level difference with pinned Hermes, and cover the documented missing-directory workaround with compiled CLI tests. Refs #3939; this does not close it.

Problem and expected behavior

After main's resolver change in d1fbebb578, a nested HERMES_HOME=~/.hermes/sub with native active_profile=coder selects ~/.hermes/profiles/coder. This PR's previous revision described the older nested destination.

The guide should show the actual configuration and skill paths, explain why creating a missing override can change routing through symlinks, and avoid claiming full Hermes compatibility. At the guide's pinned Hermes commit 748c79a1, resolve_profile_env still resolves a named profile below the configured override.

Change and scope

Refresh against main 9140deae63; update the guide and public CLI acceptance cases to current REA routing. Add both missing-directory symlink controls, including before/after directory creation. Preserve the upstream named-user and existing profile lifecycle coverage. The shared CLI fixture formatting is already on main and drops out of this PR.

Production resolution is unchanged. A separate resolver compatibility decision remains in #3939; these tests describe current REA behavior rather than establish it as the desired upstream contract.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

  • Semantic owner and earliest changed stage: resolveHermesClientHome remains unchanged; this updates user guidance and compiled CLI acceptance coverage.
  • Contribution scope fit and linked maintainer decision: ordinary documentation/tests within existing boundaries; advance scope decision not applicable. Does not settle #3939's resolver contract.
  • CLI and MCP/tool-catalog contract: unchanged.
  • Provider, bridge, target-format, or platform compatibility: no production change; Windows junction behavior remains for CI to verify.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged; dry runs assert fixture configuration, selection files, backups and skills remain untouched.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): tests use disposable homes and local REA CLI dry runs; no analysis target or provider is started.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • 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

  • Tests added or updated: five nested-home cases (native profile missing, native only, both roots populated, no native selection, pre-created symlinked root), plus both missing-directory symlink directions before/after creation. Existing explicit-profile lifecycle coverage is retained.
  • Base reproduction or other evidence: current compiled REA CLI selects native profiles/coder when live, refuses when only the nested coder exists, uses the override without native selection, and bypasses sticky selection for explicit profiles. AST-extracted original Hermes resolver functions at 748c79a1 disagree on the first three named-profile layouts; they agree on no-selection and explicit-profile controls. This runs resolver functions, not a full installed Hermes CLI.
  • User-visible CLI/MCP output (if applicable): setup previews native profiles/coder/config.yaml and its skills/reverse-engineer-anything; a missing native profile returns needs_human with no planned/applied actions. Missing symlinked paths can preview a different root until the override directory exists, as documented.
  • Remaining proof gaps: full installed Hermes and other Hermes versions, Linux/Windows execution, and completion of the hosted compiled-test shards. Hosted Codex review returned an unknown service error on the automatic run and one manual retry; all existing inline threads are resolved. No real analysis-provider verification is claimed.

For boundary fixes, identify the applicable boundary regressions
and lifecycle regressions
covered by the evidence above, and explain relevant gaps.

This is documentation/current-behavior coverage: conflicting path selections and refusal remain visible across the public CLI, and dry runs preserve the fixture files. Existing setup/doctor/uninstall lifecycle cases remain intact.

For evidence-bearing changes:

  • 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

Node 24.22.1 / npm 11.16.0, macOS arm64:

  • npm run test:focused -- tests/acceptance/setup/hermesClientSetup.test.ts tests/boundary/filesystem/hermesClientConfiguration.test.ts tests/boundary/filesystem/skillSelectionProvenance.test.ts tests/conformance/providers/managed/managedNativeVerification.test.ts — 101 passed: 23 CLI acceptance, 37 Hermes/skill boundary and 41 managed verification tests.
  • npm run check — passed typecheck, formatting, lint (0 errors), unused-code, metadata, module boundaries and architecture guards.
  • npm run docs:check — passed generated-document/license checks and 9 consistency tests.
  • npm run docs:build — VitePress build/render passed.
  • Pinned Hermes resolver / actual REA CLI comparison — five asserted layouts completed; three named-profile routing differences and two matching controls recorded above.
  • npm run verify:test-discovery — all 2,451 test files discovered exactly once.
  • Hosted checks at 474d3daba, checked 2026-10-24 23:16 UTC — PR title, readiness, static checks, package build, documentation and source tests passed; eight compiled-test shards are still running in CI run 40141466065. Greptile completed with no actionable findings.
  • git diff --check — passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none in this PR; existing main behavior is documented. Users can select a profile directly while #3939's compatibility decision remains open.
  • Real Hopper/Ghidra, browser, or OS coverage: actual compiled CLI on macOS; full installed Hermes and Windows/Linux execution unavailable. Providers/browser not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no runtime changes; isolated dry runs assert no configuration/skill writes. Both missing-path containment directions are documented and tested.

Author readiness

Human owner: @hichipli

On 2026-10-15, @hichipli confirmed review of the initially submitted diff, validation evidence and limitations, accepted responsibility, and explicitly declared this PR ready for initial maintainer review. Subsequent review fixes keep the description and validation current; the repository policy retains that initial readiness declaration.

  • 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/4145 **Author:** [@hichipli](https://github.com/hichipli) **Created:** 10/15/2026 **Status:** ✅ Merged **Merged:** 10/27/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `docs/hermes-nested-profile-selection` --- ### 📝 Commits (6) - [`7e2fea7`](https://github.com/morluto/rea/commit/7e2fea7af9f1ef2714e30660c1decdfa05bfc402) docs(hermes): clarify sticky profiles for nested homes - [`8b54071`](https://github.com/morluto/rea/commit/8b5407130e4020261dc0f961ea9d3d56c328032b) docs(hermes): qualify nested homes beneath default symlinks - [`8c3e357`](https://github.com/morluto/rea/commit/8c3e3574801e27af458e02e41286448c03c1404c) docs(hermes): cover canonicalized ancestor paths - [`788bc16`](https://github.com/morluto/rea/commit/788bc164f75159f38d7da915d6cd5d26f6446f2f) docs(hermes): clarify both missing-path containment errors - [`e9b1018`](https://github.com/morluto/rea/commit/e9b1018760e7cd12157f8b4da352fca549cc08b4) docs(hermes): resolve upstream test imports - [`474d3da`](https://github.com/morluto/rea/commit/474d3daba53c0fd7ffa4f40ebf412bff8942e645) docs(hermes): align nested-home guidance with current routing ### 📊 Changes **2 files changed** (+240 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+38 -9) 📝 `tests/acceptance/setup/hermesClientSetup.test.ts` (+202 -2) </details> ### 📄 Description ## Summary Explain the destinations REA currently previews for nested Hermes homes, warn about a resolver-level difference with pinned Hermes, and cover the documented missing-directory workaround with compiled CLI tests. Refs #3939; this does not close it. ## Problem and expected behavior After main's resolver change in d1fbebb578, a nested `HERMES_HOME=~/.hermes/sub` with native `active_profile=coder` selects `~/.hermes/profiles/coder`. This PR's previous revision described the older nested destination. The guide should show the actual configuration and skill paths, explain why creating a missing override can change routing through symlinks, and avoid claiming full Hermes compatibility. At the guide's pinned Hermes commit `748c79a1`, `resolve_profile_env` still resolves a named profile below the configured override. ## Change and scope Refresh against main `9140deae63`; update the guide and public CLI acceptance cases to current REA routing. Add both missing-directory symlink controls, including before/after directory creation. Preserve the upstream named-user and existing profile lifecycle coverage. The shared CLI fixture formatting is already on main and drops out of this PR. Production resolution is unchanged. A separate resolver compatibility decision remains in #3939; these tests describe current REA behavior rather than establish it as the desired upstream contract. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: `resolveHermesClientHome` remains unchanged; this updates user guidance and compiled CLI acceptance coverage. - Contribution scope fit and linked maintainer decision: ordinary documentation/tests within existing boundaries; advance scope decision not applicable. Does not settle #3939's resolver contract. - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: no production change; Windows junction behavior remains for CI to verify. - Evidence, artifact, provenance, or reconstruction contract: unchanged; dry runs assert fixture configuration, selection files, backups and skills remain untouched. - Target selection, authority, upstream behavior, and cleanup details (if applicable): tests use disposable homes and local REA CLI dry runs; no analysis target or provider is started. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [ ] 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. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: five nested-home cases (native profile missing, native only, both roots populated, no native selection, pre-created symlinked root), plus both missing-directory symlink directions before/after creation. Existing explicit-profile lifecycle coverage is retained. - Base reproduction or other evidence: current compiled REA CLI selects native `profiles/coder` when live, refuses when only the nested `coder` exists, uses the override without native selection, and bypasses sticky selection for explicit profiles. AST-extracted original Hermes resolver functions at `748c79a1` disagree on the first three named-profile layouts; they agree on no-selection and explicit-profile controls. This runs resolver functions, not a full installed Hermes CLI. - User-visible CLI/MCP output (if applicable): setup previews native `profiles/coder/config.yaml` and its `skills/reverse-engineer-anything`; a missing native profile returns `needs_human` with no planned/applied actions. Missing symlinked paths can preview a different root until the override directory exists, as documented. - Remaining proof gaps: full installed Hermes and other Hermes versions, Linux/Windows execution, and completion of the hosted compiled-test shards. Hosted Codex review returned an unknown service error on the automatic run and one manual retry; all existing inline threads are resolved. No real analysis-provider verification is claimed. For boundary fixes, identify the applicable [boundary regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#boundary-regressions) and [lifecycle regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#lifecycle-regressions) covered by the evidence above, and explain relevant gaps. This is documentation/current-behavior coverage: conflicting path selections and refusal remain visible across the public CLI, and dry runs preserve the fixture files. Existing setup/doctor/uninstall lifecycle cases remain intact. For evidence-bearing changes: - [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 Node 24.22.1 / npm 11.16.0, macOS arm64: - `npm run test:focused -- tests/acceptance/setup/hermesClientSetup.test.ts tests/boundary/filesystem/hermesClientConfiguration.test.ts tests/boundary/filesystem/skillSelectionProvenance.test.ts tests/conformance/providers/managed/managedNativeVerification.test.ts` — 101 passed: 23 CLI acceptance, 37 Hermes/skill boundary and 41 managed verification tests. - `npm run check` — passed typecheck, formatting, lint (0 errors), unused-code, metadata, module boundaries and architecture guards. - `npm run docs:check` — passed generated-document/license checks and 9 consistency tests. - `npm run docs:build` — VitePress build/render passed. - Pinned Hermes resolver / actual REA CLI comparison — five asserted layouts completed; three named-profile routing differences and two matching controls recorded above. - `npm run verify:test-discovery` — all 2,451 test files discovered exactly once. - Hosted checks at `474d3daba`, checked 2026-10-24 23:16 UTC — PR title, readiness, static checks, package build, documentation and source tests passed; eight compiled-test shards are still running in [CI run 40141466065](https://github.com/morluto/rea/actions/runs/40141466065). Greptile completed with no actionable findings. - `git diff --check` — passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none in this PR; existing main behavior is documented. Users can select a profile directly while #3939's compatibility decision remains open. - Real Hopper/Ghidra, browser, or OS coverage: actual compiled CLI on macOS; full installed Hermes and Windows/Linux execution unavailable. Providers/browser not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no runtime changes; isolated dry runs assert no configuration/skill writes. Both missing-path containment directions are documented and tested. ## Author readiness Human owner: @hichipli On 2026-10-15, @hichipli confirmed review of the initially submitted diff, validation evidence and limitations, accepted responsibility, and explicitly declared this PR ready for initial maintainer review. Subsequent review fixes keep the description and validation current; the repository policy retains that initial readiness declaration. - [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-10-31 01:11:43 +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#6085
No description provided.