[PR #1722] [CLOSED] fix(mcp): advertise collection-scoped selectors for analysis views #4777

New issue

Closed

opened 2026-10-31 00:54:56 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 00:54:56 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1722
Author: @DeryFerd
Created: 10/11/2026
Status: ❌ Closed

Base: main ← Head: fix/analysis-view-advertised-selectors

---

📝 Commits (1)

• 7826c56 fix(mcp): advertise collection-scoped selectors for analysis views

📊 Changes

2 files changed (+119 additions, -37 deletions)

View changed files

📝 src/domain/analysisView/analysisView.test.ts (+80 -0)
📝 src/domain/analysisView/analysisView.ts (+39 -37)

📄 Description

Summary

Fixes #1695. inspect_analysis_view validated the collection/selector pairing only through a Zod superRefine, and refinements disappear when the input contract is converted to JSON Schema, so tools/list advertised a four-way selector union for every item collection while the runtime rejected half of those combinations. This PR moves the existing pairing rules into the contract itself: modules are now expressed as a structural alternative that accepts only path or node_id, and sections and symbols as an alternative that accepts only index or name. The converted schema carries the constraints on its own, agents validating against the advertised schema stop constructing requests the server would refuse, and runtime selection semantics stay exactly as they were.

Problem and expected behavior

Smallest trigger: call inspect_analysis_view with an item view whose selector does not match its collection, for example modules with { index: 0 } or sections with { path: "renderer.js" }. Prior behavior: the real advertised schema, compiled with a draft-2020-12 validator, accepted every combination, and the MCP server then rejected the incompatible ones during input validation with view.selector: Module items are selected by exact path or node_id, not index or name. The violated invariant: the advertised input schema and the runtime validation must describe the same accepted set, because clients and agents discover callable arguments only from tools/list. Expected behavior: the converted schema rejects modules + index/name and sections/symbols + path/node_id before any request is sent, the runtime keeps rejecting the same set with the same guidance text, and the four valid pairings plus summary, facet, page, and native views continue to work unchanged.

Change and scope

The owning contract in src/domain/analysisView/analysisView.ts now models the pairing structurally: the single item object with an independent collection enum, a four-way selector union, and a superRefine is replaced by two item alternatives inside the request union, each pairing its collection with its own selector union, and the request union itself becomes a plain union so both item alternatives can carry kind: "item". A Zod 4 error map on each selector union keeps the original guidance strings, and a request-level error map promotes the failing branch's selector message so MCP clients still see a named constraint rather than a generic union failure; CLI-side projection already flattens nested union branch issues, so it surfaces the same messages at view.selector. Intentionally not included: no change to projection layers, result schemas, paging, native views, or Evidence sealing; path ambiguity for shared module paths remains the separate runtime condition that directs callers to node_id.

Contract and boundary impact

• Semantic owner and earliest changed stage: domain contract analysisViewRequestSchema in src/domain/analysisView/analysisView.ts; the advertised input contract is the first and only changed stage, with application workflows and projectors untouched.
• CLI and MCP/tool-catalog contract: inspect_analysis_view input schema shape changes from one item object plus refinement to two structural item alternatives; the advertised JSON Schema now constrains collection/selector pairs; runtime accept/reject sets are identical; the catalog digest moves with the contract because it is computed at runtime from the canonical contracts, and no catalog file is committed.
• Provider, bridge, target-format, or platform compatibility: none; the tool is provider-neutral and no bridge or platform path is involved.
• Evidence, artifact, provenance, or reconstruction contract: none; view results, view_digest sealing, parent Evidence validation, and coverage projections are unchanged.
• Process execution, authorization, cleanup, or containment impact: none; this is schema and validation structure only.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in skill-src/ and never commit build outputs): none committed. .cache/mcp-tool-catalog.json is regenerated test metadata and is not part of the repository; docs/mcp-contracts.md describes the tool in prose and embeds no input schema, so no generated document changes.

Evidence and regression coverage

• Tests added or updated: two cases in src/domain/analysisView/analysisView.test.ts. One compiles the converted input schema with Ajv's draft-2020-12 validator and asserts that modules+index, modules+name, sections+path, and symbols+node_id are rejected while the four valid pairings, summary, and page views are accepted. The other parses the runtime input schema and asserts the unchanged accept/reject sets plus the exact original guidance messages for both directions.
• Base reproduction or other evidence: on base 13e03e94 the advertised-schema case fails because the converted schema accepts modules+index and sections+path; the runtime-semantics case already passes there and stays green after the restructure, which pins that the accepted set did not move.
• User-visible CLI/MCP output: for the four incompatible combinations the guidance text is preserved verbatim; the MCP-rendered prefix becomes view: <guidance> because the constraint is now expressed structurally at the union rather than as a refinement on view.selector. Valid requests produce byte-identical results.
• Remaining proof gaps: a live third-party MCP client was not run manually; the real stdio MCP boundary suite covers the advertised-schema and validation behavior through the pinned SDK client, and the issue's Ajv 8.20.0 draft-2020-12 reproduction is mirrored by the new Ajv2020-based test. No real-provider or browser coverage applies to this contract.

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

• npx vitest run src/domain/analysisView/analysisView.test.ts — 19 passed, including the new advertised-schema and runtime-guidance cases.
• npx vitest run tests/boundary/mcp/analysisViewMcp.test.ts — 8 passed through the real stdio MCP workflow.
• npx vitest run tests/boundary/mcp/toolSchemaValidity.test.ts — 7 passed after npm run mcp-catalog:generate.
• npx vitest run tests/evaluation/model-evals/codexAgentEval.test.ts — 12 passed.
• npx vitest run tests/boundary/cli/analysisViewCli.test.ts — 6 passed, 1 failed; the portable-bundle workflow failure reproduces identically on the pristine base in this Windows host and is unrelated to this change.
• npx vitest run tests/boundary/mcp/analysisSummaryDetailMcp.test.ts — 2 failures that also reproduce identically on the pristine base (pre-existing on this Windows host); the remaining test passes.
• npm run typecheck — exit 0 after rebasing onto 8be7ad49.
• npx oxlint on both changed files — 0 warnings, 0 errors; oxfmt --check on the committed (LF) form — clean.
• Real Hopper/Ghidra, browser, or OS lanes: not applicable; no provider, bridge, or platform-specific code is touched.

Compatibility, safety, and release

• Breaking changes or migration steps: none for valid callers. Requests that already succeeded keep identical results, and requests that were already rejected at runtime are now also rejected by the advertised schema, which is the intended tightening; clients that validate against tools/list fail earlier with the same guidance instead of after a round trip.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable; the boundary suites above cover the changed contract.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: the change removes a discoverability contradiction between advertised and enforced arguments; it adds no network, process, file, or authority surface and does not alter evidence handling.

Review checklist

• This PR addresses a concrete problem or an agreed enhancement.
• 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/1722 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/11/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/analysis-view-advertised-selectors` --- ### 📝 Commits (1) - [`7826c56`](https://github.com/morluto/rea/commit/7826c56c74ba290865fef55b48aae6b1653d3354) fix(mcp): advertise collection-scoped selectors for analysis views ### 📊 Changes **2 files changed** (+119 additions, -37 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/analysisView/analysisView.test.ts` (+80 -0) 📝 `src/domain/analysisView/analysisView.ts` (+39 -37) </details> ### 📄 Description ## Summary Fixes #1695. `inspect_analysis_view` validated the collection/selector pairing only through a Zod `superRefine`, and refinements disappear when the input contract is converted to JSON Schema, so `tools/list` advertised a four-way selector union for every item collection while the runtime rejected half of those combinations. This PR moves the existing pairing rules into the contract itself: modules are now expressed as a structural alternative that accepts only `path` or `node_id`, and sections and symbols as an alternative that accepts only `index` or `name`. The converted schema carries the constraints on its own, agents validating against the advertised schema stop constructing requests the server would refuse, and runtime selection semantics stay exactly as they were. ## Problem and expected behavior Smallest trigger: call `inspect_analysis_view` with an item view whose selector does not match its collection, for example `modules` with `{ index: 0 }` or `sections` with `{ path: "renderer.js" }`. Prior behavior: the real advertised schema, compiled with a draft-2020-12 validator, accepted every combination, and the MCP server then rejected the incompatible ones during input validation with `view.selector: Module items are selected by exact path or node_id, not index or name.` The violated invariant: the advertised input schema and the runtime validation must describe the same accepted set, because clients and agents discover callable arguments only from `tools/list`. Expected behavior: the converted schema rejects `modules` + `index`/`name` and `sections`/`symbols` + `path`/`node_id` before any request is sent, the runtime keeps rejecting the same set with the same guidance text, and the four valid pairings plus summary, facet, page, and native views continue to work unchanged. ## Change and scope The owning contract in `src/domain/analysisView/analysisView.ts` now models the pairing structurally: the single item object with an independent `collection` enum, a four-way selector union, and a `superRefine` is replaced by two item alternatives inside the request union, each pairing its collection with its own selector union, and the request union itself becomes a plain union so both item alternatives can carry `kind: "item"`. A Zod 4 error map on each selector union keeps the original guidance strings, and a request-level error map promotes the failing branch's selector message so MCP clients still see a named constraint rather than a generic union failure; CLI-side projection already flattens nested union branch issues, so it surfaces the same messages at `view.selector`. Intentionally not included: no change to projection layers, result schemas, paging, native views, or Evidence sealing; path ambiguity for shared module paths remains the separate runtime condition that directs callers to `node_id`. ## Contract and boundary impact - Semantic owner and earliest changed stage: domain contract `analysisViewRequestSchema` in `src/domain/analysisView/analysisView.ts`; the advertised input contract is the first and only changed stage, with application workflows and projectors untouched. - CLI and MCP/tool-catalog contract: `inspect_analysis_view` input schema shape changes from one item object plus refinement to two structural item alternatives; the advertised JSON Schema now constrains collection/selector pairs; runtime accept/reject sets are identical; the catalog digest moves with the contract because it is computed at runtime from the canonical contracts, and no catalog file is committed. - Provider, bridge, target-format, or platform compatibility: none; the tool is provider-neutral and no bridge or platform path is involved. - Evidence, artifact, provenance, or reconstruction contract: none; view results, `view_digest` sealing, parent Evidence validation, and coverage projections are unchanged. - Process execution, authorization, cleanup, or containment impact: none; this is schema and validation structure only. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `skill-src/` and never commit build outputs): none committed. `.cache/mcp-tool-catalog.json` is regenerated test metadata and is not part of the repository; `docs/mcp-contracts.md` describes the tool in prose and embeds no input schema, so no generated document changes. ## Evidence and regression coverage - Tests added or updated: two cases in `src/domain/analysisView/analysisView.test.ts`. One compiles the converted input schema with Ajv's draft-2020-12 validator and asserts that `modules`+`index`, `modules`+`name`, `sections`+`path`, and `symbols`+`node_id` are rejected while the four valid pairings, summary, and page views are accepted. The other parses the runtime input schema and asserts the unchanged accept/reject sets plus the exact original guidance messages for both directions. - Base reproduction or other evidence: on base `13e03e94` the advertised-schema case fails because the converted schema accepts `modules`+`index` and `sections`+`path`; the runtime-semantics case already passes there and stays green after the restructure, which pins that the accepted set did not move. - User-visible CLI/MCP output: for the four incompatible combinations the guidance text is preserved verbatim; the MCP-rendered prefix becomes `view: <guidance>` because the constraint is now expressed structurally at the union rather than as a refinement on `view.selector`. Valid requests produce byte-identical results. - Remaining proof gaps: a live third-party MCP client was not run manually; the real stdio MCP boundary suite covers the advertised-schema and validation behavior through the pinned SDK client, and the issue's Ajv 8.20.0 draft-2020-12 reproduction is mirrored by the new Ajv2020-based test. No real-provider or browser coverage applies to this contract. 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 - `npx vitest run src/domain/analysisView/analysisView.test.ts` — 19 passed, including the new advertised-schema and runtime-guidance cases. - `npx vitest run tests/boundary/mcp/analysisViewMcp.test.ts` — 8 passed through the real stdio MCP workflow. - `npx vitest run tests/boundary/mcp/toolSchemaValidity.test.ts` — 7 passed after `npm run mcp-catalog:generate`. - `npx vitest run tests/evaluation/model-evals/codexAgentEval.test.ts` — 12 passed. - `npx vitest run tests/boundary/cli/analysisViewCli.test.ts` — 6 passed, 1 failed; the portable-bundle workflow failure reproduces identically on the pristine base in this Windows host and is unrelated to this change. - `npx vitest run tests/boundary/mcp/analysisSummaryDetailMcp.test.ts` — 2 failures that also reproduce identically on the pristine base (pre-existing on this Windows host); the remaining test passes. - `npm run typecheck` — exit 0 after rebasing onto `8be7ad49`. - `npx oxlint` on both changed files — 0 warnings, 0 errors; `oxfmt --check` on the committed (LF) form — clean. - Real Hopper/Ghidra, browser, or OS lanes: not applicable; no provider, bridge, or platform-specific code is touched. ## Compatibility, safety, and release - Breaking changes or migration steps: none for valid callers. Requests that already succeeded keep identical results, and requests that were already rejected at runtime are now also rejected by the advertised schema, which is the intended tightening; clients that validate against `tools/list` fail earlier with the same guidance instead of after a round trip. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; the boundary suites above cover the changed contract. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the change removes a discoverability contradiction between advertised and enforced arguments; it adds no network, process, file, or authority surface and does not alter evidence handling. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 00:54:56 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-10-31 01:14:16 +00:00

[PR #4791] [MERGED] perf(android): filter class pages before bridge serialization #6412

bsakaguchi referenced this issue 2026-10-31 01:14:19 +00:00

[PR #4804] [MERGED] feat(apktool): share one APK resource decode across selected locale tables (#4777) #6416

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

No description provided.