[PR #4970] docs(companions): propose opt-in integration contract #6702

New issue

Open

opened 2026-11-01 21:42:24 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:42:24 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4970
Author: @ShadowSwaps
Created: 10/18/2026
Status: 🔄 Open

Base: main ← Head: docs/4718-companion-integration-design

---

📝 Commits (2)

• 3c30a6d docs(companions): propose opt-in integration contract
• d8c0f3c docs(companions): clarify update ownership and source references

📊 Changes

3 files changed (+158 additions, -0 deletions)

View changed files

➕ docs/specs/4718-companion-integration/example/instructions.example.md (+5 -0)
➕ docs/specs/4718-companion-integration/example/manifest.json (+13 -0)
➕ docs/specs/4718-companion-integration/spec.md (+140 -0)

📄 Description

Summary

I propose an opt-in companion contract that preserves REA's canonical skill checks.
This PR adds a design note, illustrative manifest and instruction fixture for
feedback on loading, trusted profile binding and installation ownership.

Related to #4718; this design-only proposal does not resolve the issue. Contributor
review feedback is addressed by preserving this full template, clarifying
Companion-owned update settings, and refreshing the pinned source references.

Problem and expected behavior

Adding companion instructions to managed REA skill text causes the canonical-file
conflict described in #4718. I propose a supported opt-in loading route with
separate consent and health reporting; no such integration is implemented here.

Change and scope

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.

Exactly three documentation/example files remain under
docs/specs/4718-companion-integration/: spec.md,
example/manifest.json, and example/instructions.example.md. This local
correction changes only the spec; the fixture bytes and manifest stay unchanged.

My preferred route remains a canonical loading instruction, read-only resolver
and one explicitly selected existing installation. Loader choice, the trusted
client/profile/registry/executable source and installation ownership still need
maintainer agreement. Contributor source review is not that agreement.
Weekly-check opt-in and cooldown are the Companion installer/updater's settings,
not existing REA settings or consent for the proposed integration.

The separate inactive prototype in #6366 is outside this design PR and is not
extended by this correction. No implementation, new command, setup/update/doctor
wiring, migration writer or client-support claim is added here.

Contract and boundary impact

• Semantic owner and earliest changed stage: Design documentation only; any future adapter/registration ownership remains a maintainer decision. No production path or lifecycle changes.
• Contribution scope fit and linked maintainer decision: Documentation-only discussion for #4718; integration scope/authority remains pending, with no linked maintainer acceptance established.
• CLI and MCP/tool-catalog contract: Unchanged; no command or tool added.
• Provider, bridge, target-format, or platform compatibility: Unchanged; no host/client support is established.
• Evidence, artifact, provenance, or reconstruction contract: Illustrative fixture and source provenance only; the proposed runtime contract remains unimplemented.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): No target interaction or runtime changes; the proposal retains scope, consent and cleanup limits.
• 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 in this design diff; no generated metadata, canonical skill or installation is changed.

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: No runtime tests; local documentation/fixture checks are recorded below.
• Base reproduction or other evidence: Source-only recheck of upstream main 1e421242b97a533a5c03458ac074d4353ec17bf3 on 28 October 2026: SetupSkill.ts byte comparison, Doctor.ts canonical predicate, and Update.ts unapplied maintenance plan. No setup/doctor/update sequence was executed. The historical comparison at 6b180783ed04ebc87548c8385c80e05725804c47 is line 437, not line 406.
• User-visible CLI/MCP output (if applicable): Not applicable to documentation-only changes.
• Remaining proof gaps: Maintainer design decisions, trusted host binding, genuine session delivery, package completeness, migration/recovery and production validation remain unestablished by this PR. No #6366 test result is substituted for them.

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

This is a documentation correction, not a production boundary fix. Boundary and
lifecycle regressions remain proposed acceptance requirements; none were run or
waived for this design.

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 -e 'JSON.parse(require("node:fs").readFileSync("docs/specs/4718-companion-integration/example/manifest.json","utf8")); console.log("JSON valid")' — valid JSON.
• node -e 'const fs=require("node:fs"),c=require("node:crypto"),m=JSON.parse(fs.readFileSync("docs/specs/4718-companion-integration/example/manifest.json","utf8")); for(const [p,h] of Object.entries(m.files)){if(c.createHash("sha256").update(fs.readFileSync("docs/specs/4718-companion-integration/example/"+p)).digest("hex")!==h)throw Error("digest mismatch")} console.log("manifest digests match")' — manifest digests match.
• Local document checks — full-template round trip, preserved human declarations,
  fixture/local links, exact pinned source/blob identities, refreshed line targets
  and restricted spec changes passed. The private validation script is not a
  repository addition.

Full repository checks, documentation build, CI and real setup/runtime workflows
were not run for this local-only correction. No dependencies were installed.
Earlier public CI results describe the existing remote head, not this unpublished
spec revision.

Compatibility, safety, and release

• Breaking changes or migration steps: None implemented; migration remains a design requirement.
• Real Hopper/Ghidra, browser, or OS coverage: Not exercised; source/document review is not runtime or provider proof.
• Package or release metadata impact: None; no release, installer or update action is part of this diff.
• Security, privacy, process, or containment review: The proposal retains explicit per-profile consent, exact content identity, safe reads, inactive recovery and host-delivery limits. Hashes are not publisher authentication or a sandbox. This source/document review establishes no production trust or execution authority.

Author readiness

Human owner: @ShadowSwaps

• 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/4970 **Author:** [@ShadowSwaps](https://github.com/ShadowSwaps) **Created:** 10/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/4718-companion-integration-design` --- ### 📝 Commits (2) - [`3c30a6d`](https://github.com/morluto/rea/commit/3c30a6d9f97251bea2c8aae299469bf591ff9729) docs(companions): propose opt-in integration contract - [`d8c0f3c`](https://github.com/morluto/rea/commit/d8c0f3c4a19ab5b9dbdc7dfa2ca93babea4e86ba) docs(companions): clarify update ownership and source references ### 📊 Changes **3 files changed** (+158 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `docs/specs/4718-companion-integration/example/instructions.example.md` (+5 -0) ➕ `docs/specs/4718-companion-integration/example/manifest.json` (+13 -0) ➕ `docs/specs/4718-companion-integration/spec.md` (+140 -0) </details> ### 📄 Description <!-- PR title: type(optional-scope): imperative outcome The title becomes the squash-merge commit subject and generated changelog entry. --> ## Summary <!-- What user, agent, or maintainer problem does this solve? Link the issue with "Fixes #123" when applicable. Keep the prior behavior, expected contract, and new behavior understandable without private context. --> I propose an opt-in companion contract that preserves REA's canonical skill checks. This PR adds a design note, illustrative manifest and instruction fixture for feedback on loading, trusted profile binding and installation ownership. Related to #4718; this design-only proposal does not resolve the issue. Contributor review feedback is addressed by preserving this full template, clarifying Companion-owned update settings, and refreshing the pinned source references. ## Problem and expected behavior <!-- For fixes, give the smallest trigger and violated invariant. For features, describe the use case and observable outcome. --> Adding companion instructions to managed REA skill text causes the canonical-file conflict described in #4718. I propose a supported opt-in loading route with separate consent and health reporting; no such integration is implemented here. ## Change and scope <!-- Explain the chosen approach, why it fits REA's architecture, and what is intentionally not included. If adding complexity for a speculative or vanishingly unlikely race or security edge case, record the concrete failure mode, likelihood, complexity cost, and the user's buy-in obtained before implementation. Do not silently expand scope for theoretical robustness. --> 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. Exactly three documentation/example files remain under `docs/specs/4718-companion-integration/`: `spec.md`, `example/manifest.json`, and `example/instructions.example.md`. This local correction changes only the spec; the fixture bytes and manifest stay unchanged. My preferred route remains a canonical loading instruction, read-only resolver and one explicitly selected existing installation. Loader choice, the trusted client/profile/registry/executable source and installation ownership still need maintainer agreement. Contributor source review is not that agreement. Weekly-check opt-in and cooldown are the Companion installer/updater's settings, not existing REA settings or consent for the proposed integration. The separate inactive prototype in #6366 is outside this design PR and is not extended by this correction. No implementation, new command, setup/update/doctor wiring, migration writer or client-support claim is added here. ## Contract and boundary impact <!-- Short answers are welcome. Complete applicable lines; mark unresolved facts as "unknown". Use "none" or "not applicable" only when established. --> - Semantic owner and earliest changed stage: Design documentation only; any future adapter/registration ownership remains a maintainer decision. No production path or lifecycle changes. <!-- Name the producer of parsed facts or resources and its affected consumers. Summarize superseded paths removed and any distinct policy, lifecycle, lazy-loading, or compatibility responsibility retained. --> - Contribution scope fit and linked maintainer decision: Documentation-only discussion for #4718; integration scope/authority remains pending, with no linked maintainer acceptance established. - CLI and MCP/tool-catalog contract: Unchanged; no command or tool added. - Provider, bridge, target-format, or platform compatibility: Unchanged; no host/client support is established. - Evidence, artifact, provenance, or reconstruction contract: Illustrative fixture and source provenance only; the proposed runtime contract remains unimplemented. - Target selection, authority, upstream behavior, and cleanup details (if applicable): No target interaction or runtime changes; the proposal retains scope, consent and cleanup limits. - 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 in this design diff; no generated metadata, canonical skill or installation is changed. 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 <!-- State whether evidence is executed, source-derived, or proposed. For fixes, show the original failure and explain how the regression would fail on the affected base revision when practical. Include the most useful proof inline; link long logs or artifacts, or put them in optional details. Documentation-only changes can use source, link, or rendered-document checks. --> - Tests added or updated: No runtime tests; local documentation/fixture checks are recorded below. - Base reproduction or other evidence: Source-only recheck of upstream main `1e421242b97a533a5c03458ac074d4353ec17bf3` on 28 October 2026: [SetupSkill.ts byte comparison](https://github.com/morluto/rea/blob/1e421242b97a533a5c03458ac074d4353ec17bf3/src/application/SetupSkill.ts#L509), [Doctor.ts canonical predicate](https://github.com/morluto/rea/blob/1e421242b97a533a5c03458ac074d4353ec17bf3/src/application/Doctor.ts#L431-L436), and [Update.ts unapplied maintenance plan](https://github.com/morluto/rea/blob/1e421242b97a533a5c03458ac074d4353ec17bf3/src/application/Update.ts#L238-L252). No setup/doctor/update sequence was executed. The historical comparison at `6b180783ed04ebc87548c8385c80e05725804c47` is line 437, not line 406. - User-visible CLI/MCP output (if applicable): Not applicable to documentation-only changes. - Remaining proof gaps: Maintainer design decisions, trusted host binding, genuine session delivery, package completeness, migration/recovery and production validation remain unestablished by this PR. No #6366 test result is substituted for them. 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 a documentation correction, not a production boundary fix. Boundary and lifecycle regressions remain proposed acceptance requirements; none were run or waived for this design. 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 <!-- List only commands that actually ran, with observed results. Include the relevant real-provider or platform workflow, or explain why it was unavailable. Keep these results current after changes; a command without its result is incomplete. --> - `node -e 'JSON.parse(require("node:fs").readFileSync("docs/specs/4718-companion-integration/example/manifest.json","utf8")); console.log("JSON valid")'` — valid JSON. - `node -e 'const fs=require("node:fs"),c=require("node:crypto"),m=JSON.parse(fs.readFileSync("docs/specs/4718-companion-integration/example/manifest.json","utf8")); for(const [p,h] of Object.entries(m.files)){if(c.createHash("sha256").update(fs.readFileSync("docs/specs/4718-companion-integration/example/"+p)).digest("hex")!==h)throw Error("digest mismatch")} console.log("manifest digests match")'` — manifest digests match. - Local document checks — full-template round trip, preserved human declarations, fixture/local links, exact pinned source/blob identities, refreshed line targets and restricted spec changes passed. The private validation script is not a repository addition. Full repository checks, documentation build, CI and real setup/runtime workflows were not run for this local-only correction. No dependencies were installed. Earlier public CI results describe the existing remote head, not this unpublished spec revision. ## Compatibility, safety, and release <!-- Call out breaking changes, migrations, package effects, platform/provider limits, security/privacy/containment implications, and meaningful proof gaps. --> - Breaking changes or migration steps: None implemented; migration remains a design requirement. <!-- For ! / BREAKING CHANGE: show a previously valid call/configuration, its new behavior and migration, and why compatibility/deprecation cannot preserve it. Every release increments minor, including breaking changes; keep breaking markers and migration notes so callers can assess compatibility. See docs/releasing.md. --> - Real Hopper/Ghidra, browser, or OS coverage: Not exercised; source/document review is not runtime or provider proof. - Package or release metadata impact: None; no release, installer or update action is part of this diff. - Security, privacy, process, or containment review: The proposal retains explicit per-profile consent, exact content identity, safe reads, inactive recovery and host-delivery limits. Hashes are not publisher authentication or a sandbox. This source/document review establishes no production trust or execution authority. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @ShadowSwaps - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] 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.}

bsakaguchi added the

pull-request

label 2026-11-01 21:42:24 +00:00

bsakaguchi referenced this issue 2026-11-01 21:47:36 +00:00

[PR #6730] fix(pyinstaller): leave PE carrier binary members unmarked #7402

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

Subscribe

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#6702

No description provided.