[PR #7161] fix(environment): map id-list elements when a scalar set also changed #7686

New issue

Open

opened 2026-11-03 13:39:38 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-03 13:39:38 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7161
Author: @mhamzasakhi
Created: 10/25/2026
Status: 🔄 Open

Base: main ← Head: fix/compare-id-list-mapping

---

📝 Commits (3)

• 6f4ed55 fix(environment): map id-list elements when a scalar set also changed
• 24a8510 fix(environment): pair id-list survivors by translated identity
• 820fdb2 fix(environment): keep id-list order checks to matched survivors

📊 Changes

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

View changed files

📝 src/application/environment/environmentCompareDiff.test.ts (+93 -0)
📝 src/application/environment/environmentCompareDiff.ts (+69 -11)

📄 Description

Summary

When comparing an answer's scalar id list, a genuinely changed element made the comparison also report the unchanged ids as changed. Comparing live {"ids":[101,102]} with env {"ids":[1,9]} under the learned mapping 101→1, 102→2 reported both /ids/0 (101 vs 1) and the real /ids/1 (102 vs 9), even though 101→1 is the mapping, not a change.

This was surfaced by the automated review of #6530 (a P2 finding on environmentCompareDiff.ts) and reproduced at the source boundary; it is a concrete defect in the environment-compare engine. No separate issue is linked.

Problem and expected behavior

Differ.sameItems maps the whole scalar id list and, when the mapped set equals env, counts the renames and returns. Once one element genuinely changed, or the lengths differed, sameItems returned false and array fell to pairwise comparison. Those element comparisons were passed { own, clockKey } but not the id-list field, so scalar.mapsAsId was false and each element was compared raw.

Expected: each id-list element maps by the probe's mapping, so a renamed element matches (and counts as a normalised id) while only a genuinely different element is reported — with its original live value, not its mapped form.

Change and scope

• For an id list, array pairs survivors by the environment identity they map to (#idListPairs over #translateIdList), then pairs any remaining live and environment items by position. This handles a survivor that shifted position when the set was shortened or changed (review follow-up). The translation is one owner shared with sameItems. Other arrays keep positional pairing.
• Each element's comparison carries an idList flag derived with the same per-element rule sameItems uses (ID_LIST_FIELD on the field, or a learned state reference).
• scalar.mapsAsId honors that flag, so the element maps through IdMap.env. A mapped match increments normalised.ids and reports nothing; a real difference falls through and is reported with the original values, exactly as a singular id field already is.
• value forwards the flag.
• Non-id arrays are unaffected: the flag is false unless the field is an id-list field or the element is a learned state reference.
• The paired comparison passes the original live id to scalar, so a renamed survivor matches and is normalised while a genuine change reports its original value.
• order is computed only from the identity-matched survivor pairs, not the positional fallbacks (review follow-up): a single surviving identity that shifts is a value replacement, not a reorder, so it no longer emits a spurious order. Two or more reordered survivors still report order.
• Not included: object-keyed id comparison (object/keyedByLearnedIds) already maps correctly and is unchanged.

Contribution scope: an ordinary correctness fix within existing boundaries; a maintainer scope decision is not applicable.

Contract and boundary impact

• Semantic owner and earliest changed stage: scalar id-list element comparison in Differ.array/Differ.scalar.

• CLI and MCP/tool-catalog contract: no schema change. compare-application-versions / compare-web-captures now omit the false-positive id differences and count the renames.

• Provider, bridge, target-format, or platform compatibility: none.

• Evidence, artifact, provenance, or reconstruction contract: difference lists become accurate; normalised.ids counts the renamed-but-matching elements.

• Generated metadata, package, or installation impact: none.

• 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 to src/application/environment/environmentCompareDiff.test.ts, in "scalar sets of mapped ids":

  • "maps each id when one element genuinely changed, reporting only the real change": [101,102] vs [1,9] under 101→1,102→2 reports only /ids/1 (102 vs 9) and counts normalised.ids === 1.
  • "maps the surviving ids when the list length also differs": [101,102] vs [1] reports only the length difference and counts normalised.ids === 1.
  • "pairs a surviving id by its mapping when a removal shifts its position" (review follow-up): [101,102] vs [2] reports only the length difference, with no false /ids/0, and counts normalised.ids === 1.
  • "reports a replaced id as a value change, not an order change, when one survivor shifts" (review follow-up): [101,102] vs [2,9] reports only /ids/0 (101 vs 9), with no order.
  • "still reports an order change when two mapped survivors are reordered": [101,102,103] vs [2,1,99] reports order plus /ids/2.

• Base reproduction (executed): with environmentCompareDiff.ts reverted, the new tests fail; the first commit's two tests produce an extra /ids/0, and the shifted-survivor test fails against the first commit (it still emitted a false /ids/0).

• Additional cases checked at the source boundary (all correct after the change): a fully reordered mapped set reports only order; a non-id array (tags) reports only its real element change with no mapping; equal ids with no learned mapping report nothing.

• 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

Run on Ubuntu 24.04 x64 with Node 24.22.1:

• npm run test:local -- src/application/environment/environmentCompareDiff.test.ts: 70 passed. With the fix reverted: the two new tests fail.
• npm run test:focused -- with every test file referencing environment compare or state (60 files): 1517 passed, 1 skipped, 0 failed. The heavy toolSchemaValidity boundary test (~30s, unrelated to this comparison change) timed out at its 30s limit under local load and passes in isolation; it is excluded from that count.
• npm run check:fast: passed. knip reports nothing for the touched module.

Compatibility, safety, and release

• Breaking changes or migration steps: none. Only false-positive id-list differences stop being reported; genuine differences and non-id arrays are unchanged.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable (pure comparison function). Linux only.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: no new reads, execution, or network access.

Author readiness

Human owner: @mhamzasakhi

• 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/7161 **Author:** [@mhamzasakhi](https://github.com/mhamzasakhi) **Created:** 10/25/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/compare-id-list-mapping` --- ### 📝 Commits (3) - [`6f4ed55`](https://github.com/morluto/rea/commit/6f4ed55edc3be5280701a68d10147b2e00ee5aa1) fix(environment): map id-list elements when a scalar set also changed - [`24a8510`](https://github.com/morluto/rea/commit/24a851078c811ce4fa101ac3f2acbe22ba81649a) fix(environment): pair id-list survivors by translated identity - [`820fdb2`](https://github.com/morluto/rea/commit/820fdb2d9ce0a5a47688032f2377ddc6784bdc81) fix(environment): keep id-list order checks to matched survivors ### 📊 Changes **2 files changed** (+162 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `src/application/environment/environmentCompareDiff.test.ts` (+93 -0) 📝 `src/application/environment/environmentCompareDiff.ts` (+69 -11) </details> ### 📄 Description ## Summary When comparing an answer's scalar id list, a genuinely changed element made the comparison also report the *unchanged* ids as changed. Comparing live `{"ids":[101,102]}` with env `{"ids":[1,9]}` under the learned mapping `101→1`, `102→2` reported both `/ids/0` (101 vs 1) and the real `/ids/1` (102 vs 9), even though `101→1` is the mapping, not a change. This was surfaced by the automated review of #6530 (a P2 finding on `environmentCompareDiff.ts`) and reproduced at the source boundary; it is a concrete defect in the environment-compare engine. No separate issue is linked. ## Problem and expected behavior `Differ.sameItems` maps the whole scalar id list and, when the mapped set equals env, counts the renames and returns. Once one element genuinely changed, or the lengths differed, `sameItems` returned false and `array` fell to pairwise comparison. Those element comparisons were passed `{ own, clockKey }` but not the id-list field, so `scalar.mapsAsId` was false and each element was compared raw. Expected: each id-list element maps by the probe's mapping, so a renamed element matches (and counts as a normalised id) while only a genuinely different element is reported — with its original live value, not its mapped form. ## Change and scope - For an id list, `array` pairs survivors by the environment identity they map to (`#idListPairs` over `#translateIdList`), then pairs any remaining live and environment items by position. This handles a survivor that shifted position when the set was shortened or changed (review follow-up). The translation is one owner shared with `sameItems`. Other arrays keep positional pairing. - Each element's comparison carries an `idList` flag derived with the same per-element rule `sameItems` uses (`ID_LIST_FIELD` on the field, or a learned state reference). - `scalar.mapsAsId` honors that flag, so the element maps through `IdMap.env`. A mapped match increments `normalised.ids` and reports nothing; a real difference falls through and is reported with the original values, exactly as a singular id field already is. - `value` forwards the flag. - Non-id arrays are unaffected: the flag is false unless the field is an id-list field or the element is a learned state reference. - The paired comparison passes the original live id to `scalar`, so a renamed survivor matches and is normalised while a genuine change reports its original value. - `order` is computed only from the identity-matched survivor pairs, not the positional fallbacks (review follow-up): a single surviving identity that shifts is a value replacement, not a reorder, so it no longer emits a spurious `order`. Two or more reordered survivors still report `order`. - Not included: object-keyed id comparison (`object`/`keyedByLearnedIds`) already maps correctly and is unchanged. Contribution scope: an ordinary correctness fix within existing boundaries; a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: scalar id-list element comparison in `Differ.array`/`Differ.scalar`. - CLI and MCP/tool-catalog contract: no schema change. `compare-application-versions` / `compare-web-captures` now omit the false-positive id differences and count the renames. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: difference lists become accurate; `normalised.ids` counts the renamed-but-matching elements. - Generated metadata, package, or installation impact: none. - [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. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added to `src/application/environment/environmentCompareDiff.test.ts`, in "scalar sets of mapped ids": - "maps each id when one element genuinely changed, reporting only the real change": `[101,102]` vs `[1,9]` under `101→1,102→2` reports only `/ids/1` (`102` vs `9`) and counts `normalised.ids === 1`. - "maps the surviving ids when the list length also differs": `[101,102]` vs `[1]` reports only the length difference and counts `normalised.ids === 1`. - "pairs a surviving id by its mapping when a removal shifts its position" (review follow-up): `[101,102]` vs `[2]` reports only the length difference, with no false `/ids/0`, and counts `normalised.ids === 1`. - "reports a replaced id as a value change, not an order change, when one survivor shifts" (review follow-up): `[101,102]` vs `[2,9]` reports only `/ids/0` (`101` vs `9`), with no `order`. - "still reports an order change when two mapped survivors are reordered": `[101,102,103]` vs `[2,1,99]` reports `order` plus `/ids/2`. - Base reproduction (executed): with `environmentCompareDiff.ts` reverted, the new tests fail; the first commit's two tests produce an extra `/ids/0`, and the shifted-survivor test fails against the first commit (it still emitted a false `/ids/0`). - Additional cases checked at the source boundary (all correct after the change): a fully reordered mapped set reports only `order`; a non-id array (`tags`) reports only its real element change with no mapping; equal ids with no learned mapping report nothing. - [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 Run on Ubuntu 24.04 x64 with Node 24.22.1: - `npm run test:local -- src/application/environment/environmentCompareDiff.test.ts`: 70 passed. With the fix reverted: the two new tests fail. - `npm run test:focused --` with every test file referencing environment compare or state (60 files): 1517 passed, 1 skipped, 0 failed. The heavy `toolSchemaValidity` boundary test (~30s, unrelated to this comparison change) timed out at its 30s limit under local load and passes in isolation; it is excluded from that count. - `npm run check:fast`: passed. `knip` reports nothing for the touched module. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Only false-positive id-list differences stop being reported; genuine differences and non-id arrays are unchanged. - Real Hopper/Ghidra, browser, or OS coverage: not applicable (pure comparison function). Linux only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new reads, execution, or network access. ## Author readiness Human owner: @mhamzasakhi - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [ ] 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 added the

pull-request

label 2026-11-03 13:39:38 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

codex/procedure-reference-stacked

release-please--branches--main--components--rea-agents

release-please--branches--main--components--rea-agents--release-notes

codex/kuna-independent-retry

codex/byte-search-overlay-coverage

codex/open-failure-target-receipt

codex/kuna-xref-evidence

codex/ghidra-ambiguous-procedure-recovery

codex/function-source-bundle

codex/trace-function-integration-prototype

codex/snapshot-source-closure

codex/recorded-evidence-array-pages

codex/evidence-recovery-redesign

codex/trace-feature-address-scope

codex/call-discovery-scope

codex/ghidra-literal-candidate-evidence

codex/decompile-directory-independent-retry

codex/retry-provenance-base

codex/value-flow-capability-experiment

codex/ghidra-containing-instruction

cursor/readme-discord-button-ef9f

dependabot/github_actions/actions/setup-node-7.1.0

dependabot/github_actions/actions/upload-artifact-7.0.2

dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df

codex/kuna-1989

fix/8559-native-ui-fixture-ownership

fix/8555-go-verifier-mcp-ownership

codex/provider-capability-recovery

fix/8642-rizin-target-stdin

codex/ghidra-memory-effect-scope

codex/ghidra-annotation-entry-selector

codex/ghidra-readonly-recovery

codex/ghidra-regex-verifier-recovery

codex/evidence-discovery-view-guidance

fix/8545-bulk-append-overflow

fix/8428-navigation-refusal-alternatives

codex/address-context-recovery

codex/matching-member-limitations

codex/unknown-scope-contract

codex/evidence-view-guidance

feat/8373-native-trace-views

codex/ghidra-snapshot-verifier-binding

codex/elf-export-visibility

codex/evidence-view-recovery

codex/native-reference-cli-help

codex/provider-candidate-observation-scope

codex/kuna-session-verification

codex/ghidra-switch-lifetime-guidance

codex/pseudocode-paging-discovery

codex/clarify-evidence-view-support

codex/kuna-xrefs-selector-recovery

codex/context-capacity-recovery

codex/evidence-closure-large-links

codex/same-function-evidence-identity

codex/ghidra-verifier-inspected-jdk

codex/audit-guided-workflows

codex/crash-prompt-retained-dossiers

codex/analysis-view-error-recovery

codex/kuna-verifier-target-selection

codex/ghidra-selected-project-call-coverage

codex/docs-native-analysis-scope

codex/ghidra-java-socket-boundary

codex/ghidra-retained-snapshot-verifier

codex/ghidra-search-inventory-facts

fix/8284-zero-argument-parameter-bindings

fix/8198-ui-action-handler-offset

fix/8257-elf-entry-label-identity

fix/8304-deferred-output-schema-projection

fix/8277-call-path-computed-target-uncertainty

fix/pr-8089-conflicts

fix/ci-static-duplicate-export

dependabot/npm_and_yarn/lint-staged-17.6.0

dependabot/github_actions/actions/download-artifact-8.0.2

dependabot/npm_and_yarn/write-file-atomic-8.0.0

dependabot/npm_and_yarn/canonicalize-5.1.0

dependabot/github_actions/actions/cache/restore-6.1.0

dependabot/npm_and_yarn/toon-format/toon-4.4.0

dependabot/github_actions/actions/deploy-pages-5.0.1

codex/review-fixes-pr-2403

codex/review-fixes-pr-2400

codex/process-terminal-width

codex/test-brittleness-cleanup

verify/7167-browser-connect-macos

fix/7167-browser-connect

feat/native-matching-allowance-setting

feat/browser-scenario-dry-run

test/managed-caller-parameters-20261024

codex/parser-fortythird-boundaries

fix/6926-pinvoke-platform-decorations-20261023

fix/6889-har-body-encoding-20261023

fix/6888-sqlite-schema-budget-20261023

fix/dependency-security-gates-6708

cursor/evidence-overwrite-rebase-b4ac

feat/4057-verify-native-exports

fix/windows-acl-observer-overhead-20261022

cursor/erlang-beam-restack-4476

cursor/pe-certificate-review-bf32

fix/6116-javascript-application-fs-errors

fix/6061-unmapped-runtime-script-unknown

feat/browser-scenario-summary

fix/pe-certificates

codex/verify-3407

cursor/rebase-5699

cursor/rebase-5352

cursor/rebase-5600

cursor/fix-cli-schema-omission-10a8

codex/audit-hopper-shutdown-reasons-20261021

fix/demangle-swift-omitted-record

fix/nib-boolean-value-types

cursor/cancellation-partial-observation-a5ac

fix/ib-object-limit-reasons

fix/electron-fuse-limit-advice

fix/kuna-doctor-dangling-cache

fix/fixed-budget-refusal-advice

fix/js-ipc-listener-dedup

fix/js-return-member-provenance

fix/dmg-integrity-retry-advice

fix/ida-doctor-readiness

fix/kuna-version-probe-output-drain

fix/legacy-swift-runtime-name-matching

fix/dylib-lazy-load-commands

fix/browser-scenario-startup-cancel

fix/swift-nested-punycode-classification

fix/compare-unselected-scopes

fix/objc-method-budget-coverage

fix/dmg-mounted-root-observations

audit/ci-tests-20261019-round2

release/6.7.0

fix/wabt-cleanup-retry-resolution

fix/electron-fuse-elf-pe-architecture

fix/native-plist-descriptor-ownership

fix/kuna-caller-cleanup-ownership

experiment/atomic-codemode-20261016

review/first-contributor-3776

fix/call-resolution-full-read-cycles

fix/member-mutation-selection-repeat

experiment/atomic-re-tools-20261015

perf/member-mutation-lazy-origins

perf/static-network-mutation-index

fix/hopper-startup-lifecycle

audit/3050-windows-proof-20261015

feat/windows-window-capture-2183

audit/3049-windows-proof-20261015

audit/3735-macos-fixtures-20261015

fix/batch-decompile-null-pseudocode

fix/kuna-inventory-honors-jobs

experiment/browser-codemode-tool-design-20261015

fix/hopper-clean-runtime-argv

codex/review-2049-27f1b367

review-fixes/pr-2787-routing

fix/3360-scoped-this-emitters

fix/3367-replaced-global-effects

fix/3838-compact-any-value-items

test/hopper-download-probe-20261015

codex/windows-runtime-creation-red-green-20261015

codex/windows-readonly-root-red-green-20261015

codex/windows-root-share-red-green-20261015

codex/exp-1685-win-mcp-startup

codex/bug-sweep-20261015

investigate/2190-windows-package-phases

investigate/3543-macos-cli-deadline

perf/3281-reverse-tools-feedback-quality

fix/3406-hopper-doctor-fixture

fix/3341-wrapper-require-test-context

fix/3301-owned-uninstall-fixtures

fix/3164-compiler-input-ownership

fix/pcap-cleanup-stdout-newline-20261014

perf/interface-builder-summary

codex/review-fixes-pr-1977

fix/ghidra-effective-jvm-platform

fix/docs-turkish-rust-link-20261013

fix/main-maintenance-ci-20261010

fix/recover-binary-session-process-effects

codex/review-fixes-pr-2457

codex/ci-required-cancellation-gate

fix/main-format-baseline-20261013

fix/setup-preserve-entry-fields

cursor/restore-main-checks-1ffc

fix/ghidra-bridge-hashmap-import

codex/shared-ci-jadx-json-default-20261013

codex/shared-ci-ghidra-test-groups-20261013

codex/shared-ci-java-fixture-format-20261013

codex/fix-intrinsic-invocation-boundaries

test/release-preflight-reusable-jobs

test/js-parameter-provenance-expectation

fix/linux-hopper-verification-current

test/2419-ghidra-elf-probe-size

followup/pr-1544-native-ida

codex/fold-pr-2230-contribution

docs/readme-responsible-use

fix/issue-2064

fix/issue-2050

fix/issue-2053

fix/issue-1968

fix/issue-1945

experiment/codemode-bridge-20261011

fix/tool-effects-negative-wording-1904-20261012

fix/1842-electron-interop-provenance

feat/recover-javascript-multi-input

refactor/website-i18n-prep

fix/nativeaot-pe-virtual-extent

fix/browser-verifier-ci-hang

fix/pe-resources-input-selection

docs/beginner-friendly-guides

docs/beginner-setup-guide

fix/javascript-analysis-worker-1563

fix/1649-ghidra-duplicate-names

fix/javascript-export-keys-integration-1369

test/maintenance-boundary-contracts-20261011

review/javascript-export-keys-1369

review/process-live-progress-1483

test/javascript-1495-growth-ratio

fix/ci-escape-timing

docs/normalized-terminal-geometry-1450

release/6.3.0

archive/release-6.3.0-pr1381

release/6.2.0

fix/electron-preload-dynamic-override

fix/javascript-self-referential-bundler-edges

release/6.1.0

cursor/grok-client-cherry-pick-0b56

feat/signature-posture

feat/dyld-shared-cache

feat/artifact-integrity-policy

feat/pkg-inventory

release/6.0.0

chore/sync-release-5.0.0

release/5.0.0

cursor/cloud-agent-node-787e

fix/javascript-xhr-open-endpoints

review/pr-711-realpath-fallback-wording

cleanup/replay-confinement

codex/test-suite-performance

codex/issue-foundations

codex/address-open-issues-2026-07-20

agent/javascript-vite-rollup-esbuild-adapters

agent/process-cleanup

agent/triage-integration

agent/unknown-commands-registry

feat/mcp-identity-metadata

morlvps/issue_cleanup

codex/installer-redesign

morl/roadmap-investigation-core

morl/roadmap-investigation-docs

release-please--branches--main--components--rea

rea-agents-6.8.0

rea-agents-6.7.0

rea-agents-6.6.0

experiment/atomic-codemode-wait-runtime-20261016

rea-agents-6.5.0

rea-agents-6.4.0

rea-agents-6.3.0

rea-agents-6.2.0

rea-agents-6.1.0

rea-agents-6.0.0

rea-agents-5.0.0

rea-agents-4.1.0

rea-agents-4.0.1

rea-agents-4.0.0

rea-agents-3.2.1

rea-agents-3.2.0

rea-agents-3.1.0

rea-agents-3.0.0

rea-agents-2.7.0

rea-agents-2.6.0

rea-agents-2.5.1

rea-agents-2.5.0

rea-agents-2.4.0

rea-agents-2.3.0

rea-agents-2.2.0

rea-agents-2.1.0

rea-agents-2.0.0

rea-agents-1.7.0

rea-agents-1.6.0

rea-agents-1.5.0

rea-agents-1.4.0

rea-agents-1.3.0

rea-agents-1.2.0

rea-agents-1.1.0

rea-agents-1.0.0

rea-agents-0.5.0

rea-agents-0.4.0

rea-agents-0.3.0

rea-0.2.1

rea-0.2.0

Labels

Clear labels   

area: bridge

  

area: bridge

  

area: build

  

area: build

  

area: build

  

area: cli

  

area: domain

  

area: evidence

  

area: mcp

  

area: native

  

area: providers

  

area: runtime

  

area: server

  

area: setup

  

area: tests

  

bug

  

design

  

documentation

  

enhancement

  

enhancement

  

enhancement

  

experiment

  

help wanted

  

i18n

  

invalid

  

P0: critical

  

P1: high

  

P2: medium

  

P2: medium

  

P2: medium

  

P3: low

  

performance

  

provider-request

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

roadmap

  

triage

No labels

area: bridge

area: bridge

area: build

area: build

area: build

area: cli

area: domain

area: evidence

area: mcp

area: native

area: providers

area: runtime

area: server

area: setup

area: tests

bug

design

documentation

enhancement

enhancement

enhancement

experiment

help wanted

i18n

invalid

P0: critical

P1: high

P2: medium

P2: medium

P2: medium

P3: low

performance

provider-request

pull-request

question

roadmap

triage

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

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

No description provided.