[PR #5250] [CLOSED] fix(managed): keep operand-free instructions in CIL anchors #6838

New issue

Closed

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

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

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5250
Author: @akushonkamen
Created: 10/19/2026
Status: ❌ Closed

Base: main ← Head: fix/5147-managed-anchors-operand-free

---

📝 Commits (1)

• fd8e098 fix(managed): keep operand-free instructions in CIL anchors

📊 Changes

3 files changed (+88 additions, -9 deletions)

View changed files

📝 src/dotnet/ManagedMemberInspector.test.ts (+70 -1)
📝 src/dotnet/ManagedMethodBodyReader.ts (+11 -8)
📝 tests/boundary/providers/managed/managedMemberComparisonFromMetadata.test.ts (+7 -0)

📄 Description

Summary

inspect-managed-members dropped every operand-free instruction from body.anchors, so branch comparison constants like the 4 in ldloc.s 4; ldc.i4.4; bne.un were unrecoverable from the result. Fixes #5147.

Problem and expected behavior

src/dotnet/ManagedMethodBodyReader.ts built body.anchors with a .filter((instruction) => instruction.operandKind !== "none"). Operand-free opcodes (ldc.i4.N, dup, pop, ldarg.N, ldloc.N, stloc.N, ret, …) vanished from anchors while opcode_counts and the normalized decode hash still counted them — on the issue's example (token 0x060029f5), instruction_count 208 but only 132 anchors. Expected behavior, per the maintainer endorsement on the issue: anchors retain every decoded instruction, so a branch reports the constant it compares against.

Change and scope

Anchors now cover every decoded instruction: the operandKind !== "none" filter is removed in src/dotnet/ManagedMethodBodyReader.ts and a comment records why operand-free anchors must stay. No schema change is needed (managedInstructionAnchorSchema already allows operand_kind: "none"). Consumers are unaffected: call edges and field accesses (ManagedMemberRows.ts), ldstr literal collection (ManagedUserStrings.ts), and MethodSpec resolution (ManagedMethodSpecs.ts) all filter anchors by opcode or operand kind and guard null operands; the decode budget charges anchors by retained JSON size, so bounds still hold. Intentionally not included: sister issue #5146 and any documentation rewrite (docs never described anchors as operand-only).

Follow the contribution scope. Maintainer scope decision: not applicable — ordinary fix within the existing managed-metadata inspection boundary; no new provider, execution, injection, or protection recovery.

Contract and boundary impact

• Semantic owner and earliest changed stage: ManagedMethodBodyReader (managed CIL body decode) — the producing boundary for anchors.
• Contribution scope fit and linked maintainer decision: not applicable, see above.
• CLI and MCP/tool-catalog contract: inspect-managed-members output gains anchor entries for operand-free instructions; schema unchanged (operand_kind enum already includes "none").
• Provider, bridge, target-format, or platform compatibility: none — pure decode-side change.
• Evidence, artifact, provenance, or reconstruction contract: normalized_il_sha256 and il_sha256 unchanged (already covered all instructions); structuralKey comparison hashes now span the same anchor set they already spanned via opcode_counts.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

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: new regression test in src/dotnet/ManagedMemberInspector.test.ts ("managed method body anchors") builds the IL ldloc.s 4; ldc.i4.4; bne.un.s +0; ret and asserts the exact anchors including { il_offset: 2, opcode: "ldc.i4.4", operand_kind: "none", operand: null } and the ret anchor; existing anchor expectations updated to the complete lists in src/dotnet/ManagedMemberInspector.test.ts and tests/boundary/providers/managed/managedMemberComparisonFromMetadata.test.ts.
• Base reproduction or other evidence: executed. Red on base 3ea0d9489 — the new test failed with anchors missing the ldc.i4.4 and ret entries; green after the one-line filter removal.
• User-visible CLI/MCP output (if applicable): body.anchors now lists operand-free instructions alongside operand-bearing ones.
• Remaining proof gaps: the full --project boundary suite was attempted twice but did not finish within a 900 s budget on a machine running several concurrent builds; the relevant managed subsets (below) and the DMG file whose failure fragment appeared under that load (nativeDmgArtifactReader.test.ts, 48/48 in isolation) all pass. On CI, the PR's red lanes (Test shard (1-5/5), Portable tests) fail on setup/acceptance/provider tests (Gemini workspace trust, HOME fallback, kuna verifier) with no managed or anchor test among them; the base commit 3ea0d948 fails the same lanes on its own main CI run (39254713979, plus Real Apple artifact E2E, recorded_crash, darwin native baselines), so those lanes are pre-existing red, not introduced here. The PR readiness check stays red until the human owner completes the Author readiness declarations below — intentionally left to a human per the template.

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/dotnet/ManagedMemberInspector.test.ts -t "operand-free" — red before the fix (anchors lacked ldc.i4.4, ret); passes after.
• npx vitest run src/dotnet — 14 files, 344/344 passed.
• npx vitest run tests/boundary/providers/managed src/domain/managed — 10 files, 118/118 passed.
• npx vitest run src/dotnet tests/boundary/providers/managed src/domain/managed — 24 files, 462/462 passed.
• npx vitest run tests/boundary/providers/native/nativeDmgArtifactReader.test.ts — 48/48 passed in isolation.
• npm run typecheck — clean after a standalone npm ci (the shared node_modules was missing openpgp).
• npm run check:fast — typecheck + lint, 2/2 tasks successful.
• npx oxlint / oxfmt --check on the three touched files — no new findings (baseline files already carry pre-existing warnings).
• CI on this PR: Static checks, Source tests, Build package, Build bundled Windows x64 native controls, Native package baseline (linux x64), Classify changes, Conventional PR title, Greptile Review all pass; the failing lanes match pre-existing main failures (see Remaining proof gaps).

Compatibility, safety, and release

• Breaking changes or migration steps: none. body.anchors grows (output contract change endorsed in the issue); schema already accepted the shape, so older readers of newer output are unaffected and newer readers of older Evidence see the previous lists as-is.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable — no provider interaction; covered by unit/boundary tests.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: none — read-only decode of already-opened artifact bytes.

Author readiness

Human owner:

• 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/5250 **Author:** [@akushonkamen](https://github.com/akushonkamen) **Created:** 10/19/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/5147-managed-anchors-operand-free` --- ### 📝 Commits (1) - [`fd8e098`](https://github.com/morluto/rea/commit/fd8e0983ce8993e198bf3625cd7fe4eaf642f137) fix(managed): keep operand-free instructions in CIL anchors ### 📊 Changes **3 files changed** (+88 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `src/dotnet/ManagedMemberInspector.test.ts` (+70 -1) 📝 `src/dotnet/ManagedMethodBodyReader.ts` (+11 -8) 📝 `tests/boundary/providers/managed/managedMemberComparisonFromMetadata.test.ts` (+7 -0) </details> ### 📄 Description ## Summary `inspect-managed-members` dropped every operand-free instruction from `body.anchors`, so branch comparison constants like the `4` in `ldloc.s 4; ldc.i4.4; bne.un` were unrecoverable from the result. Fixes #5147. ## Problem and expected behavior `src/dotnet/ManagedMethodBodyReader.ts` built `body.anchors` with a `.filter((instruction) => instruction.operandKind !== "none")`. Operand-free opcodes (`ldc.i4.N`, `dup`, `pop`, `ldarg.N`, `ldloc.N`, `stloc.N`, `ret`, …) vanished from anchors while `opcode_counts` and the normalized decode hash still counted them — on the issue's example (token `0x060029f5`), `instruction_count` 208 but only 132 anchors. Expected behavior, per the maintainer endorsement on the issue: anchors retain every decoded instruction, so a branch reports the constant it compares against. ## Change and scope Anchors now cover every decoded instruction: the `operandKind !== "none"` filter is removed in `src/dotnet/ManagedMethodBodyReader.ts` and a comment records why operand-free anchors must stay. No schema change is needed (`managedInstructionAnchorSchema` already allows `operand_kind: "none"`). Consumers are unaffected: call edges and field accesses (`ManagedMemberRows.ts`), ldstr literal collection (`ManagedUserStrings.ts`), and MethodSpec resolution (`ManagedMethodSpecs.ts`) all filter anchors by opcode or operand kind and guard null operands; the decode budget charges anchors by retained JSON size, so bounds still hold. Intentionally not included: sister issue #5146 and any documentation rewrite (docs never described anchors as operand-only). Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Maintainer scope decision: not applicable — ordinary fix within the existing managed-metadata inspection boundary; no new provider, execution, injection, or protection recovery. ## Contract and boundary impact - Semantic owner and earliest changed stage: `ManagedMethodBodyReader` (managed CIL body decode) — the producing boundary for anchors. - Contribution scope fit and linked maintainer decision: not applicable, see above. - CLI and MCP/tool-catalog contract: `inspect-managed-members` output gains anchor entries for operand-free instructions; schema unchanged (`operand_kind` enum already includes `"none"`). - Provider, bridge, target-format, or platform compatibility: none — pure decode-side change. - Evidence, artifact, provenance, or reconstruction contract: `normalized_il_sha256` and `il_sha256` unchanged (already covered all instructions); `structuralKey` comparison hashes now span the same anchor set they already spanned via `opcode_counts`. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [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 or updated: new regression test in `src/dotnet/ManagedMemberInspector.test.ts` ("managed method body anchors") builds the IL `ldloc.s 4; ldc.i4.4; bne.un.s +0; ret` and asserts the exact anchors including `{ il_offset: 2, opcode: "ldc.i4.4", operand_kind: "none", operand: null }` and the `ret` anchor; existing anchor expectations updated to the complete lists in `src/dotnet/ManagedMemberInspector.test.ts` and `tests/boundary/providers/managed/managedMemberComparisonFromMetadata.test.ts`. - Base reproduction or other evidence: executed. Red on base `3ea0d9489` — the new test failed with anchors missing the `ldc.i4.4` and `ret` entries; green after the one-line filter removal. - User-visible CLI/MCP output (if applicable): `body.anchors` now lists operand-free instructions alongside operand-bearing ones. - Remaining proof gaps: the full `--project boundary` suite was attempted twice but did not finish within a 900 s budget on a machine running several concurrent builds; the relevant managed subsets (below) and the DMG file whose failure fragment appeared under that load (`nativeDmgArtifactReader.test.ts`, 48/48 in isolation) all pass. On CI, the PR's red lanes (`Test shard (1-5/5)`, `Portable tests`) fail on setup/acceptance/provider tests (Gemini workspace trust, HOME fallback, kuna verifier) with no managed or anchor test among them; the base commit `3ea0d948` fails the same lanes on its own `main` CI run (39254713979, plus `Real Apple artifact E2E`, `recorded_crash`, darwin native baselines), so those lanes are pre-existing red, not introduced here. The `PR readiness` check stays red until the human owner completes the Author readiness declarations below — intentionally left to a human per the template. 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/dotnet/ManagedMemberInspector.test.ts -t "operand-free"` — red before the fix (anchors lacked `ldc.i4.4`, `ret`); passes after. - `npx vitest run src/dotnet` — 14 files, 344/344 passed. - `npx vitest run tests/boundary/providers/managed src/domain/managed` — 10 files, 118/118 passed. - `npx vitest run src/dotnet tests/boundary/providers/managed src/domain/managed` — 24 files, 462/462 passed. - `npx vitest run tests/boundary/providers/native/nativeDmgArtifactReader.test.ts` — 48/48 passed in isolation. - `npm run typecheck` — clean after a standalone `npm ci` (the shared `node_modules` was missing `openpgp`). - `npm run check:fast` — typecheck + lint, 2/2 tasks successful. - `npx oxlint` / `oxfmt --check` on the three touched files — no new findings (baseline files already carry pre-existing warnings). - CI on this PR: `Static checks`, `Source tests`, `Build package`, `Build bundled Windows x64 native controls`, `Native package baseline (linux x64)`, `Classify changes`, `Conventional PR title`, `Greptile Review` all pass; the failing lanes match pre-existing `main` failures (see Remaining proof gaps). ## Compatibility, safety, and release - Breaking changes or migration steps: none. `body.anchors` grows (output contract change endorsed in the issue); schema already accepted the shape, so older readers of newer output are unaffected and newer readers of older Evidence see the previous lists as-is. - Real Hopper/Ghidra, browser, or OS coverage: not applicable — no provider interaction; covered by unit/boundary tests. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none — read-only decode of already-opened artifact bytes. ## 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: <!-- @GitHub-handle --> - [ ] 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 <!-- 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 2026-11-01 21:43:24 +00:00

• closed this issue
• added the
  pull-request
  label

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

[PR #6910] [CLOSED] fix(cli): enumerate setup and doctor client choices #7441

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

No description provided.