[PR #6632] [CLOSED] fix(mcp): advertise attached-capture incompleteness in compare_web_captures example #7384

New issue

Closed

opened 2026-11-01 21:47:27 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:47:27 +00:00

Owner

Copy link

📋 Pull Request Information

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

Base: main ← Head: fix/compare-web-captures-example

---

📝 Commits (1)

• 15483fe fix(mcp): advertise attached-capture incompleteness in compare_web_captures example

📊 Changes

2 files changed (+45 additions, -4 deletions)

View changed files

📝 src/contracts/browserToolContracts.ts (+23 -2)
📝 tests/boundary/mcp/browserComparisonInput.test.ts (+22 -2)

📄 Description

Summary

The default MCP tools/list input example for compare_web_captures advertised two attached-browser captures (browser.mode: "connect") with completeness.status: "complete", equality_eligible: true, no missing sections, and limitations: []. A connected capture cannot recover pre-attach events, so the producer can never emit that state. The example now mirrors the producer's attached state: capture-wide incomplete, equality_eligible: false, missing_sections: ["events"], and the attachment limitations.

Fixes #5897.

Problem and expected behavior

Smallest trigger: call MCP tools/list, take the advertised compare_web_captures example unchanged, and submit it as before_scenario/after_scenario. It compares as overall_status: "unchanged".

Violated invariant: connected captures always declare missing event coverage. globalCompleteness (src/browser/PlaywrightBrowserScenarioProvider.ts) unconditionally records "events" as missing for mode: "connect", which classifies to {status: "incomplete", equality_eligible: false}, and browserScenarioLimitations (src/browser/BrowserScenarioPartialObservation.ts) always returns a non-empty limitation list, including three attachment-specific strings. The advertised example (complete, equality_eligible: true, limitations: []) is a capture the normal producer cannot emit, so clients reading the catalog get the wrong model of attached capture coverage.

Expected: the advertised example describes a capture the producer can emit, so the example compares as unknown — missing or truncated evidence never proves equality.

Change and scope

• src/contracts/browserToolContracts.ts: the shared exampleScenarioCapture() now uses a new attachedScenarioCompleteness (incomplete, equality_eligible: false, missing_sections: ["events"], truncated_sections: []) and attachedScenarioLimitations (the six unconditional limitation strings plus the three connect-mode strings, with the en-US locale default from browserScenarioEnvironmentSchema) at capture level. This mirrors globalCompleteness and browserScenarioLimitations for this example's shape (no captured response body, no storage seeds, no session event gaps). Per-step completeness stays complete, matching stepCompleteness, which derives only from step artifacts.
• tests/boundary/mcp/browserComparisonInput.test.ts: the boundary test that pinned the scenario example as unchanged now pins unknown (the diff requires both captures to be equality-eligible before claiming equality), with the test name updated; a new focused test pins the advertised capture state (completeness record and the attachment limitation) so the example cannot regress to advertising complete coverage.
• Intentionally not included: no change to the capture schema, the comparison contract, docs/browser-scenario-contract.md (already the correct authority), or any provider behavior. The passive before/after example group is untouched; its example is not a scenario capture.

Follow the contribution scope. Ordinary fix within existing boundaries; no maintainer scope decision required (no new provider or capability; no target execution, injection, mutation, or protection recovery).

Contract and boundary impact

• Semantic owner and earliest changed stage: MCP tool-catalog example metadata owned by src/contracts/browserToolContracts.ts; changed at advertisement time only.
• Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable.
• CLI and MCP/tool-catalog contract: the advertised compare_web_captures input example values change (completeness, limitations); input/output schemas unchanged; ignored catalogs are CI-regenerated.
• Provider, bridge, target-format, or platform compatibility: none; no provider code changes.
• Evidence, artifact, provenance, or reconstruction contract: the example now preserves the incomplete-coverage semantics the contract requires.
• Target selection, authority, upstream behavior, and cleanup details: not applicable.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none authored; CI regenerates ignored catalogs.

Expected effects (check known effects; use documentation-only on its own).

• 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: new focused test compare_web_captures advertised example > advertises the attached scenario capture in the producer's state parses the advertised example and asserts the producer-attached state (fails on the base revision, where the example advertises complete); the boundary test's pinned scenario outcome moved unchanged -> unknown (fails on the base revision).
• Base reproduction or other evidence: executed. The boundary test drives the advertised example through a live in-memory MCP server (client.callTool with examples[0].input) and asserts normalized_result matches the domain comparison; on this branch that comparison returns unknown, observed passing. The producer-side expectations (incomplete, equality_eligible: false, missing_sections: ["events"], attachment limitations present) are asserted by the existing PlaywrightBrowserScenarioProvider.test.ts connect-capture test, which is unchanged and still passes.
• User-visible CLI/MCP output (if applicable): the advertised example published by tools/list for compare_web_captures now contains "completeness": {"status": "incomplete", "equality_eligible": false, "missing_sections": ["events"], "truncated_sections": []} and the nine applicable limitation strings for the attached example capture.
• Remaining proof gaps: limitation strings for the example are source-derived from browserScenarioLimitations for this scenario shape; a live Playwright connect session with popup families, storage seeds, or event-budget drops would additionally carry conditional strings not represented in the synthetic example. No real-browser session was run for this change (the boundary test uses the fake CDP browser; provider connect behavior is covered by its existing simulated-session tests).

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

• npm run test:focused -- tests/boundary/mcp/browserComparisonInput.test.ts — result: 2/2 passed.
• npm run test:focused -- tests/boundary/mcp/toolSchemaValidity.test.ts tests/boundary/mcp/toolInputAdmission.test.ts tests/boundary/mcp/toolResult.test.ts tests/boundary/mcp/optionalProviderIsolation.test.ts tests/boundary/mcp/observationPartialEvidenceDelivery.test.ts tests/boundary/mcp/targetContentFramingMcp.test.ts tests/boundary/mcp/applicationExportShapeMcp.test.ts tests/boundary/mcp/scriptInventoryRace.test.ts tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/browserScenarioMcp.test.ts src/contracts/toolInputReferences.test.ts — result: 103/107 passed; 4 failures were timeouts under 11-file parallel load plus one applicationExportShapeMcp evidence_id assertion that reproduces identically with the change stashed on the clean base (pre-existing, unrelated); the three timeout-prone files re-ran with this change and passed 31/31.
• npm run check:fast — result: typecheck and lint pass (0 errors).

Compatibility, safety, and release

• Breaking changes or migration steps: none; input schemas unchanged, only advertised example values.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable; no target interaction. Browser boundary behavior exercised through the existing fake-CDP tests.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: none; static example metadata.

Author readiness

Human owner: @ashyyhere

• 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 (open issue #5897 with reproduction).
• Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff (not applicable; ordinary fix within existing boundaries).
• The PR has one focused outcome and the title follows type(scope): outcome.
• Related issue is linked.
• 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/6632 **Author:** [@ashyyhere](https://github.com/ashyyhere) **Created:** 10/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/compare-web-captures-example` --- ### 📝 Commits (1) - [`15483fe`](https://github.com/morluto/rea/commit/15483fea8035985b7a6672bb1a9bf8099f0f6774) fix(mcp): advertise attached-capture incompleteness in compare_web_captures example ### 📊 Changes **2 files changed** (+45 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/contracts/browserToolContracts.ts` (+23 -2) 📝 `tests/boundary/mcp/browserComparisonInput.test.ts` (+22 -2) </details> ### 📄 Description ## Summary The default MCP `tools/list` input example for `compare_web_captures` advertised two attached-browser captures (`browser.mode: "connect"`) with `completeness.status: "complete"`, `equality_eligible: true`, no missing sections, and `limitations: []`. A connected capture cannot recover pre-attach events, so the producer can never emit that state. The example now mirrors the producer's attached state: capture-wide `incomplete`, `equality_eligible: false`, `missing_sections: ["events"]`, and the attachment limitations. Fixes #5897. ## Problem and expected behavior Smallest trigger: call MCP `tools/list`, take the advertised `compare_web_captures` example unchanged, and submit it as `before_scenario`/`after_scenario`. It compares as `overall_status: "unchanged"`. Violated invariant: connected captures always declare missing event coverage. `globalCompleteness` (`src/browser/PlaywrightBrowserScenarioProvider.ts`) unconditionally records `"events"` as missing for `mode: "connect"`, which classifies to `{status: "incomplete", equality_eligible: false}`, and `browserScenarioLimitations` (`src/browser/BrowserScenarioPartialObservation.ts`) always returns a non-empty limitation list, including three attachment-specific strings. The advertised example (`complete`, `equality_eligible: true`, `limitations: []`) is a capture the normal producer cannot emit, so clients reading the catalog get the wrong model of attached capture coverage. Expected: the advertised example describes a capture the producer can emit, so the example compares as `unknown` — missing or truncated evidence never proves equality. ## Change and scope - `src/contracts/browserToolContracts.ts`: the shared `exampleScenarioCapture()` now uses a new `attachedScenarioCompleteness` (`incomplete`, `equality_eligible: false`, `missing_sections: ["events"]`, `truncated_sections: []`) and `attachedScenarioLimitations` (the six unconditional limitation strings plus the three connect-mode strings, with the `en-US` locale default from `browserScenarioEnvironmentSchema`) at capture level. This mirrors `globalCompleteness` and `browserScenarioLimitations` for this example's shape (no captured response body, no storage seeds, no session event gaps). Per-step completeness stays `complete`, matching `stepCompleteness`, which derives only from step artifacts. - `tests/boundary/mcp/browserComparisonInput.test.ts`: the boundary test that pinned the scenario example as `unchanged` now pins `unknown` (the diff requires both captures to be equality-eligible before claiming equality), with the test name updated; a new focused test pins the advertised capture state (completeness record and the attachment limitation) so the example cannot regress to advertising complete coverage. - Intentionally not included: no change to the capture schema, the comparison contract, `docs/browser-scenario-contract.md` (already the correct authority), or any provider behavior. The passive `before`/`after` example group is untouched; its example is not a scenario capture. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Ordinary fix within existing boundaries; no maintainer scope decision required (no new provider or capability; no target execution, injection, mutation, or protection recovery). ## Contract and boundary impact - Semantic owner and earliest changed stage: MCP tool-catalog example metadata owned by `src/contracts/browserToolContracts.ts`; changed at advertisement time only. - Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable. - CLI and MCP/tool-catalog contract: the advertised `compare_web_captures` input example values change (`completeness`, `limitations`); input/output schemas unchanged; ignored catalogs are CI-regenerated. - Provider, bridge, target-format, or platform compatibility: none; no provider code changes. - Evidence, artifact, provenance, or reconstruction contract: the example now preserves the incomplete-coverage semantics the contract requires. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none authored; CI regenerates ignored catalogs. Expected effects (check known effects; use documentation-only on its own). - [x] 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: new focused test `compare_web_captures advertised example > advertises the attached scenario capture in the producer's state` parses the advertised example and asserts the producer-attached state (fails on the base revision, where the example advertises `complete`); the boundary test's pinned scenario outcome moved `unchanged` -> `unknown` (fails on the base revision). - Base reproduction or other evidence: executed. The boundary test drives the advertised example through a live in-memory MCP server (`client.callTool` with `examples[0].input`) and asserts `normalized_result` matches the domain comparison; on this branch that comparison returns `unknown`, observed passing. The producer-side expectations (`incomplete`, `equality_eligible: false`, `missing_sections: ["events"]`, attachment limitations present) are asserted by the existing `PlaywrightBrowserScenarioProvider.test.ts` connect-capture test, which is unchanged and still passes. - User-visible CLI/MCP output (if applicable): the advertised example published by `tools/list` for `compare_web_captures` now contains `"completeness": {"status": "incomplete", "equality_eligible": false, "missing_sections": ["events"], "truncated_sections": []}` and the nine applicable limitation strings for the attached example capture. - Remaining proof gaps: limitation strings for the example are source-derived from `browserScenarioLimitations` for this scenario shape; a live Playwright connect session with popup families, storage seeds, or event-budget drops would additionally carry conditional strings not represented in the synthetic example. No real-browser session was run for this change (the boundary test uses the fake CDP browser; provider connect behavior is covered by its existing simulated-session tests). 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 - `npm run test:focused -- tests/boundary/mcp/browserComparisonInput.test.ts` — result: 2/2 passed. - `npm run test:focused -- tests/boundary/mcp/toolSchemaValidity.test.ts tests/boundary/mcp/toolInputAdmission.test.ts tests/boundary/mcp/toolResult.test.ts tests/boundary/mcp/optionalProviderIsolation.test.ts tests/boundary/mcp/observationPartialEvidenceDelivery.test.ts tests/boundary/mcp/targetContentFramingMcp.test.ts tests/boundary/mcp/applicationExportShapeMcp.test.ts tests/boundary/mcp/scriptInventoryRace.test.ts tests/boundary/mcp/browserMcp.test.ts tests/boundary/mcp/browserScenarioMcp.test.ts src/contracts/toolInputReferences.test.ts` — result: 103/107 passed; 4 failures were timeouts under 11-file parallel load plus one `applicationExportShapeMcp` `evidence_id` assertion that reproduces identically with the change stashed on the clean base (pre-existing, unrelated); the three timeout-prone files re-ran with this change and passed 31/31. - `npm run check:fast` — result: typecheck and lint pass (0 errors). ## Compatibility, safety, and release - Breaking changes or migration steps: none; input schemas unchanged, only advertised example values. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; no target interaction. Browser boundary behavior exercised through the existing fake-CDP tests. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none; static example metadata. ## Author readiness Human owner: @ashyyhere - [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 (open issue #5897 with reproduction). - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff (not applicable; ordinary fix within existing boundaries). - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked. - [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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-11-01 21:47:27 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-03 00:29:32 +00:00

[GH-ISSUE #5653] [Tracker] New issue intake by area (October 2026) #3423

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

No description provided.