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 #4039] feat(clients): register ggcode during setup #6010

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4039
Author: @topcheer
Created: 10/15/2026
Status: 🔄 Open

Base: main ← Head: feat/ggcode-client-upstream

📝 Commits (10+)

  • 4b696ac feat(clients): register ggcode during setup
  • 63383f1 fix(clients): harden ggcode legacy fallback, migration and validation
  • 1ae062e Merge branch 'morluto:main' into feat/ggcode-client-upstream
  • b13e8ea Merge branch 'morluto:main' into feat/ggcode-client-upstream
  • 70bb97e Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream
  • 814ebcd fix(clients): resolve aliased ggcode names and report the legacy path
  • a164fa9 Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream
  • ea5e5a9 Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream
  • 28fe064 Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream
  • 574ba9c chore(clients): drop unrelated import shuffles from the ggcode PR

📊 Changes

13 files changed (+1288 additions, -12 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/references/connection-and-recovery.md (+1 -1)
📝 docs/client-configuration.md (+13 -0)
📝 docs/installation.md (+1 -0)
📝 src/application/ClientConfigurationDocument.ts (+74 -0)
📝 src/application/ClientConfigurationFiles.ts (+44 -1)
📝 src/application/ClientRegistration.ts (+8 -2)
📝 src/application/ClientRegistrationStatus.ts (+3 -1)
➕ src/application/GgcodeConfigurationYaml.ts (+316 -0)
📝 src/application/SetupClientConfiguration.ts (+94 -3)
📝 src/application/SupportedClients.ts (+60 -1)
📝 src/application/Uninstall.ts (+21 -3)
📝 tests/boundary/filesystem/clientLifecycle.test.ts (+1 -0)
➕ tests/boundary/filesystem/ggcodeClientConfiguration.test.ts (+652 -0)

📄 Description

Summary

Setup now registers REA with ggcode, so
npx rea-agents setup (or rea setup --client ggcode) writes the REA MCP
registration and installs the bundled reverse-engineering skill for ggcode
users, with the same plan-approve-apply flow and backups as every other
supported client.

Problem and expected behavior

ggcode users had to hand-register REA. After this change, setup detects
ggcode from ~/.ggcode and registers the rea stdio server in ggcode's
standalone MCP configuration, reporting aligned/stale/missing in doctor like
other clients.

Change and scope

ggcode reads MCP servers from ~/.ggcode/mcp_servers.yaml, a top-level YAML
sequence of named entries (- name: rea with type/command/args/env;
an empty type connects as stdio). It auto-migrates a legacy mcp_servers
section of the main ~/.ggcode/ggcode.yaml into that standalone file and
honors the section only while the file is absent.

  • SupportedClients: ggcode definition with a new ggcode YAML-sequence
    format. ~/.ggcode/ggcode.yaml is a lower-precedence read layer (so a
    legacy in-main registration reports correctly) and, via the new
    supersededConfigPath, the seed source for a freshly created standalone
    file — mirroring ggcode's own migration instead of suppressing
    hand-configured servers. ggcode has no home-directory override.
  • GgcodeConfigurationYaml (new): parses both layouts into the synthetic
    mcp_servers server table; upserts/deletes one named sequence entry while
    retaining formatting, order, and comments; malformed items fail closed.
  • ClientConfigurationDocument: parse/serialize wiring and a stdio
    registration entry. ClientRegistrationStatus treats a non-stdio type
    as stale/invalid, like the other type-carrying dialects.
  • SetupClientConfiguration: seeds a freshly created standalone file with
    the superseded in-main servers. An existing target is never reseeded, so a
    deleted entry cannot resurrect from the inert legacy section.
  • Skill installs to ~/.ggcode/skills, which ggcode discovers (it also reads
    the shared ~/.agents/skills destination).
  • Docs: installation client table, client-configuration ggcode section,
    bundled skill's supported client list.

Intentionally not included: writing to ~/.ggcode/ggcode.yaml (REA only ever
writes the standalone file), and real-client verification beyond the local
run described below.

Contract and boundary impact

  • Semantic owner and earliest changed stage: setup/doctor client
    registration (src/application), same boundary as all client dialects.
  • Contribution scope fit and linked maintainer decision: not applicable —
    ordinary client registration within existing setup boundaries, following
    the droid/qoder precedent.
  • CLI and MCP/tool-catalog contract: new --client ggcode selection and
    doctor client entry; no tool-catalog change.
  • Provider, bridge, target-format, or platform compatibility: none; POSIX and
    Windows paths resolve through the existing ClientPathContext.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged.
  • Target selection, authority, upstream behavior, and cleanup details (if
    applicable): setup writes only ~/.ggcode/mcp_servers.yaml with a
    .rea.backup recovery backup; uninstall removes only the rea entry.
  • Generated metadata: no authored-contract change; .agents/skills source
    updated, generated outputs untouched.

Expected effects:

  • Read existing files or captured data. (reads ~/.ggcode/*.yaml during doctor/setup)
  • 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.

(The registered server launches REA itself when ggcode connects, same as
every other stdio client registration.)

Evidence and regression coverage

  • Tests added or updated: tests/boundary/filesystem/ggcodeClientConfiguration.test.ts
    (10 tests: path resolution, skills directory, create/upsert/empty-file
    registration, comment+order preservation, legacy seeding, no-resurrect
    beside an existing file, legacy-layer aligned status, malformed YAML
    rejected untouched, uninstall); clientLifecycle.test.ts client list.
  • Base reproduction or other evidence: real run on macOS against a live
    ~/.ggcode (ggcode installed at /opt/homebrew/bin/ggcode): setup appended
    rea to an existing mcp_servers.yaml with four unrelated servers
    preserved, ggcode mcp list loads the entry, rea doctor --json reports
    {"client": "ggcode", "state": "aligned"}, and a raw stdio initialize
    handshake against the registered command returns REA's capabilities.
  • User-visible CLI/MCP output (if applicable): dry-run plan shows
    configure_client:ggcode → /Users/zhanju/.ggcode/mcp_servers.yaml
    (operation update, backup .../mcp_servers.yaml.rea.backup) and
    install_skill:ggcode → ~/.ggcode/skills/reverse-engineer-anything.
  • Remaining proof gaps: no Windows host verification (path cases covered in
    unit tests); no ggcode version matrix (verified against the locally
    installed ggcode build only). The observed skill stale state after a
    from-source setup run is shared with other clients and unrelated to this
    change (skill fingerprint is produced by the packaged build).

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

On the PR branch (single commit on top of upstream main @ e45eb33f0):

  • npx tsc --noEmit — clean.
  • npm run check — pass (typecheck, lint, format, knip, metadata freshness,
    architecture guards across 1425 source files).
  • npm run check:fast — pass.
  • npm run docs:check — pass (5/5).
  • npx vitest run tests/boundary/filesystem/ggcodeClientConfiguration.test.ts tests/boundary/filesystem/clientLifecycle.test.ts — 66/66 pass.
  • npx vitest run tests/boundary/filesystem/{hermes,kimi,droid,qoder}ClientConfiguration.test.ts tests/boundary/filesystem/clientConfigurationEnvironment.test.ts — 97/97 pass.
  • npx vitest run src/application/Setup.planning.test.ts src/application/Doctor.test.ts src/application/HermesConfigurationYaml.test.ts — 63/63 pass.
  • npm run verify:package — pass (setup planned-then-idempotent with backup
    readback, repository skill bundle verified, 207 MCP tools listed).
  • npm pack --dry-run — 1687 files, no unexpected additions.
  • node scripts/rea.mjs setup --client ggcode --dry-run --json — planned
    update of ~/.ggcode/mcp_servers.yaml with backup, plus skill install.
  • node scripts/rea.mjs setup --client ggcode --yes --json — status: ready;
    existing servers preserved, backup written.
  • ggcode mcp list — lists rea [stdio] alongside the four pre-existing servers.
  • node scripts/rea.mjs doctor --json — ggcode registration state: aligned.
  • stdio initialize against the registered command — REA capabilities returned.
  • Pre-existing, environment-dependent failures on this machine
    (tests/acceptance/setup/*, several JavaScript/Apple artifact boundary
    suites, qwenClientConfiguration, setupSkill) reproduce identically on
    unmodified main; they are unrelated to this change.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Existing ggcode users keep their
    configuration; setup only appends/updates the rea entry with a backup.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; no analysis
    provider behavior changed.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: writes are confined to
    ggcode's user configuration with atomic writes and .rea.backup recovery;
    the registered entry carries no environment beyond explicitly configured
    values; the seeding path never deletes or rewrites the legacy
    ggcode.yaml.

Author readiness

Human owner: @topcheer

  • 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. (No issue filed; direct enhancement following the droid/qoder client-addition precedent.)
  • 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/4039 **Author:** [@topcheer](https://github.com/topcheer) **Created:** 10/15/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/ggcode-client-upstream` --- ### 📝 Commits (10+) - [`4b696ac`](https://github.com/morluto/rea/commit/4b696ac4057fb0d65ed61ef404d6f007eb7f55f5) feat(clients): register ggcode during setup - [`63383f1`](https://github.com/morluto/rea/commit/63383f11cacdd3aa5e855e94a9f31583e2e88e62) fix(clients): harden ggcode legacy fallback, migration and validation - [`1ae062e`](https://github.com/morluto/rea/commit/1ae062e6fb33af35ea8c8b56de7f8861736079e5) Merge branch 'morluto:main' into feat/ggcode-client-upstream - [`b13e8ea`](https://github.com/morluto/rea/commit/b13e8ea18f8dcaf012596848d6fc6b0b8cbbdfbd) Merge branch 'morluto:main' into feat/ggcode-client-upstream - [`70bb97e`](https://github.com/morluto/rea/commit/70bb97e4287b008bc450100af81d94ff6dccdceb) Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream - [`814ebcd`](https://github.com/morluto/rea/commit/814ebcd682068f0a0d00614c7c8fb8b90ed3e10d) fix(clients): resolve aliased ggcode names and report the legacy path - [`a164fa9`](https://github.com/morluto/rea/commit/a164fa946f1e54820ea985fb19c57d41edb06d51) Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream - [`ea5e5a9`](https://github.com/morluto/rea/commit/ea5e5a93feb67cc581798d3f013e8951195dad01) Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream - [`28fe064`](https://github.com/morluto/rea/commit/28fe06497a080d6f8ec9ab409f3e7260e2d48bde) Merge remote-tracking branch 'upstream/main' into feat/ggcode-client-upstream - [`574ba9c`](https://github.com/morluto/rea/commit/574ba9cc5f048b2cbf649cc196efa42897a08a93) chore(clients): drop unrelated import shuffles from the ggcode PR ### 📊 Changes **13 files changed** (+1288 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md` (+1 -1) 📝 `docs/client-configuration.md` (+13 -0) 📝 `docs/installation.md` (+1 -0) 📝 `src/application/ClientConfigurationDocument.ts` (+74 -0) 📝 `src/application/ClientConfigurationFiles.ts` (+44 -1) 📝 `src/application/ClientRegistration.ts` (+8 -2) 📝 `src/application/ClientRegistrationStatus.ts` (+3 -1) ➕ `src/application/GgcodeConfigurationYaml.ts` (+316 -0) 📝 `src/application/SetupClientConfiguration.ts` (+94 -3) 📝 `src/application/SupportedClients.ts` (+60 -1) 📝 `src/application/Uninstall.ts` (+21 -3) 📝 `tests/boundary/filesystem/clientLifecycle.test.ts` (+1 -0) ➕ `tests/boundary/filesystem/ggcodeClientConfiguration.test.ts` (+652 -0) </details> ### 📄 Description ## Summary Setup now registers REA with [ggcode](https://github.com/topcheer/ggcode), so `npx rea-agents setup` (or `rea setup --client ggcode`) writes the REA MCP registration and installs the bundled reverse-engineering skill for ggcode users, with the same plan-approve-apply flow and backups as every other supported client. ## Problem and expected behavior ggcode users had to hand-register REA. After this change, setup detects ggcode from `~/.ggcode` and registers the `rea` stdio server in ggcode's standalone MCP configuration, reporting aligned/stale/missing in doctor like other clients. ## Change and scope ggcode reads MCP servers from `~/.ggcode/mcp_servers.yaml`, a top-level YAML sequence of named entries (`- name: rea` with `type`/`command`/`args`/`env`; an empty `type` connects as stdio). It auto-migrates a legacy `mcp_servers` section of the main `~/.ggcode/ggcode.yaml` into that standalone file and honors the section only while the file is absent. - `SupportedClients`: ggcode definition with a new `ggcode` YAML-sequence format. `~/.ggcode/ggcode.yaml` is a lower-precedence read layer (so a legacy in-main registration reports correctly) and, via the new `supersededConfigPath`, the seed source for a freshly created standalone file — mirroring ggcode's own migration instead of suppressing hand-configured servers. ggcode has no home-directory override. - `GgcodeConfigurationYaml` (new): parses both layouts into the synthetic `mcp_servers` server table; upserts/deletes one named sequence entry while retaining formatting, order, and comments; malformed items fail closed. - `ClientConfigurationDocument`: parse/serialize wiring and a stdio registration entry. `ClientRegistrationStatus` treats a non-stdio `type` as stale/invalid, like the other type-carrying dialects. - `SetupClientConfiguration`: seeds a freshly created standalone file with the superseded in-main servers. An existing target is never reseeded, so a deleted entry cannot resurrect from the inert legacy section. - Skill installs to `~/.ggcode/skills`, which ggcode discovers (it also reads the shared `~/.agents/skills` destination). - Docs: installation client table, client-configuration ggcode section, bundled skill's supported client list. Intentionally not included: writing to `~/.ggcode/ggcode.yaml` (REA only ever writes the standalone file), and real-client verification beyond the local run described below. ## Contract and boundary impact - Semantic owner and earliest changed stage: setup/doctor client registration (`src/application`), same boundary as all client dialects. - Contribution scope fit and linked maintainer decision: not applicable — ordinary client registration within existing setup boundaries, following the droid/qoder precedent. - CLI and MCP/tool-catalog contract: new `--client ggcode` selection and doctor client entry; no tool-catalog change. - Provider, bridge, target-format, or platform compatibility: none; POSIX and Windows paths resolve through the existing `ClientPathContext`. - Evidence, artifact, provenance, or reconstruction contract: unchanged. - Target selection, authority, upstream behavior, and cleanup details (if applicable): setup writes only `~/.ggcode/mcp_servers.yaml` with a `.rea.backup` recovery backup; uninstall removes only the `rea` entry. - Generated metadata: no authored-contract change; `.agents/skills` source updated, generated outputs untouched. Expected effects: - [x] Read existing files or captured data. (reads `~/.ggcode/*.yaml` during doctor/setup) - [ ] 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. (The registered server launches REA itself when ggcode connects, same as every other stdio client registration.) ## Evidence and regression coverage - Tests added or updated: `tests/boundary/filesystem/ggcodeClientConfiguration.test.ts` (10 tests: path resolution, skills directory, create/upsert/empty-file registration, comment+order preservation, legacy seeding, no-resurrect beside an existing file, legacy-layer aligned status, malformed YAML rejected untouched, uninstall); `clientLifecycle.test.ts` client list. - Base reproduction or other evidence: real run on macOS against a live `~/.ggcode` (ggcode installed at /opt/homebrew/bin/ggcode): setup appended `rea` to an existing `mcp_servers.yaml` with four unrelated servers preserved, `ggcode mcp list` loads the entry, `rea doctor --json` reports `{"client": "ggcode", "state": "aligned"}`, and a raw stdio `initialize` handshake against the registered command returns REA's capabilities. - User-visible CLI/MCP output (if applicable): dry-run plan shows `configure_client:ggcode` → `/Users/zhanju/.ggcode/mcp_servers.yaml` (operation update, backup `.../mcp_servers.yaml.rea.backup`) and `install_skill:ggcode` → `~/.ggcode/skills/reverse-engineer-anything`. - Remaining proof gaps: no Windows host verification (path cases covered in unit tests); no ggcode version matrix (verified against the locally installed ggcode build only). The observed skill `stale` state after a from-source setup run is shared with other clients and unrelated to this change (skill fingerprint is produced by the packaged build). 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 On the PR branch (single commit on top of upstream `main` @ e45eb33f0): - `npx tsc --noEmit` — clean. - `npm run check` — pass (typecheck, lint, format, knip, metadata freshness, architecture guards across 1425 source files). - `npm run check:fast` — pass. - `npm run docs:check` — pass (5/5). - `npx vitest run tests/boundary/filesystem/ggcodeClientConfiguration.test.ts tests/boundary/filesystem/clientLifecycle.test.ts` — 66/66 pass. - `npx vitest run tests/boundary/filesystem/{hermes,kimi,droid,qoder}ClientConfiguration.test.ts tests/boundary/filesystem/clientConfigurationEnvironment.test.ts` — 97/97 pass. - `npx vitest run src/application/Setup.planning.test.ts src/application/Doctor.test.ts src/application/HermesConfigurationYaml.test.ts` — 63/63 pass. - `npm run verify:package` — pass (setup planned-then-idempotent with backup readback, repository skill bundle verified, 207 MCP tools listed). - `npm pack --dry-run` — 1687 files, no unexpected additions. - `node scripts/rea.mjs setup --client ggcode --dry-run --json` — planned update of `~/.ggcode/mcp_servers.yaml` with backup, plus skill install. - `node scripts/rea.mjs setup --client ggcode --yes --json` — `status: ready`; existing servers preserved, backup written. - `ggcode mcp list` — lists `rea [stdio]` alongside the four pre-existing servers. - `node scripts/rea.mjs doctor --json` — ggcode registration `state: aligned`. - stdio `initialize` against the registered command — REA capabilities returned. - Pre-existing, environment-dependent failures on this machine (`tests/acceptance/setup/*`, several JavaScript/Apple artifact boundary suites, `qwenClientConfiguration`, `setupSkill`) reproduce identically on unmodified `main`; they are unrelated to this change. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Existing ggcode users keep their configuration; setup only appends/updates the `rea` entry with a backup. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; no analysis provider behavior changed. - Package or release metadata impact: none. - Security, privacy, process, or containment review: writes are confined to ggcode's user configuration with atomic writes and `.rea.backup` recovery; the registered entry carries no environment beyond explicitly configured values; the seeding path never deletes or rewrites the legacy `ggcode.yaml`. ## Author readiness Human owner: @topcheer - [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. (No issue filed; direct enhancement following the droid/qoder client-addition precedent.) - [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>
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#6010
No description provided.