morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #6877] [CLOSED] fix(managed): derive P/Invoke suffix candidates for default and Auto charsets #7429

New issue
Closed
opened 2026-11-01 21:47:48 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:47:48 +00:00
Owner
Copy link

📋 Pull Request Information

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

Base: main ← Head: fix/pinvoke-charset-candidates

📝 Commits (1)

  • 3d1a2cd fix(managed): derive P/Invoke suffix candidates for default and Auto charsets

📊 Changes

3 files changed (+85 additions, -6 deletions)

View changed files

📝 docs/managed-code-analysis.md (+8 -0)
📝 src/domain/managed/managedNativeVerificationMatch.ts (+22 -4)
📝 tests/conformance/providers/managed/managedNativeVerification.test.ts (+55 -2)

📄 Description

Summary

Fixes #6857.

verify-managed-native-boundaries added the A/W entry-point suffix candidate only for an explicit ansi or unicode charset. A default (not-specified) P/Invoke declaration behaves as ANSI, and Auto means Unicode on Windows, so their conventional decorated exports (ExampleA, ExampleW) were dropped and verification reported unresolved / no-native-candidate. They are now retained as inferred / decorated-name-candidate, the same as the explicit-charset controls.

Problem and expected behavior

Smallest trigger: a P/Invoke Example in example.dll with mapping flags 0x0200 (charset unspecified, ExactSpelling false) and supplied PE function Evidence named ExampleA. Before: unresolved, no-native-candidate, no candidates; explicit ANSI (0x0202) returned inferred with ExampleA. Same pattern for Auto (0x0206) with ExampleW versus explicit Unicode.

Expected (per the issue and Microsoft's Charsets and marshalling / Specifying a character set): the default charset probes the A name, Auto probes W on Windows, and ExactSpelling suppresses suffixes. This stays a static candidate inference, not proof of binding.

Change and scope

The charset parser already preserved not-specified and auto correctly; the gap was in candidate enumeration (candidateNames in src/domain/managed/managedNativeVerificationMatch.ts). It now resolves an effective charset per native module:

  • not-specified → ANSI (adds A) for every module format;
  • auto → Unicode (adds W) when the supplied native Evidence's module format is pe, and unknown (no suffix candidate) for other formats, because Auto means UTF-8 off Windows and the supplied Evidence does not establish suffix probing there;
  • ansi/unicode and ExactSpelling (no_mangle) behave exactly as before.

Candidates are computed per native symbol, since only the symbol's Evidence knows its module format; the existing moduleFormatsByEvidenceId map already carried that fact. docs/managed-code-analysis.md now states the entry-point rule next to the existing module-name rules.

Not changed: stdcall _Name@N decorations, module matching, and verification status semantics.

Contribution scope: ordinary correctness fix within the existing static-verification boundary; no scope decision needed.

Contract and boundary impact

  • Semantic owner and earliest changed stage: P/Invoke candidate enumeration in managedNativeVerificationMatch.ts.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: no schema change; affected declarations now return the existing inferred / decorated-name-candidate state.
  • Provider, bridge, target-format, or platform compatibility: the Auto suffix applies only to PE modules; ELF, Mach-O and unknown formats get no Auto suffix candidate.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged; matches remain inferences with the supplied native Evidence retained.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable.
  • Generated metadata, package, or installation impact: none; npm run docs:check passed with no generated changes.

Evidence and regression coverage

  • Tests added or updated: tests/conformance/providers/managed/managedNativeVerification.test.ts, with 10 table cases covering default/ANSI/Unicode/Auto on PE and ELF, wrong-suffix controls, and ExactSpelling suppression. The nativeFunctionEvidence helper takes a function name, and inputWithImportScope takes a charset/ExactSpelling override.
  • Base reproduction: with the src/ change stashed, exactly the 3 bug cases fail (default→A on PE, default→A on ELF, Auto→W on PE); the 7 controls pass on both revisions.
  • Public CLI: the issue's six-case verify-managed-native-boundaries script (adapted for a Windows host), run with the fix: default-ansi-suffix and auto-unicode-suffix now return inferred / decorated-name-candidate with ExampleA / ExampleW; explicit controls unchanged; auto-exact-control stays verified / exact-function-name; exactspelling-control stays unresolved / no-native-candidate.
  • Real Windows binding behavior (supports the rule; not committed). The issue notes it did not run a live Windows binding test, so I ran DllImport probes on Windows 11 x64 (.NET Framework 4.8 via PowerShell Add-Type) against system DLLs:
    • shell32!CommandLineToArgv, which is exported only as CommandLineToArgvW: Auto and Unicode bind; default, Ansi, and Auto + ExactSpelling throw EntryPointNotFoundException.
    • kernel32!GetModuleHandle, which is exported only as GetModuleHandleA / GetModuleHandleW: the default charset binds (so it resolves GetModuleHandleA, since the default never probed W above); default + ExactSpelling throws EntryPointNotFoundException.
  • Remaining proof gaps: modern .NET (Core) on Windows was not probed live (Microsoft documents the same name matching); non-Windows Auto behavior is deliberately left unknown rather than asserted.

Validation performed

Windows 11 x64, Node.js 24.22.1 (pinned), locked dependencies.

  • npm run test:focused -- tests/conformance/providers/managed/managedNativeVerification.test.ts — 30/30 passed; with src/ stashed, 3 failed / 27 passed (the three bug cases).
  • npm run test:focused -- tests/boundary/mcp/managedNativeVerificationAdapters.test.ts tests/boundary/mcp/outputSchemaSemanticConstraints.test.ts — 4/4 passed.
  • npm run build:cached then the issue's CLI reproduction — results above.
  • npm run check:fast — passed.
  • npm run docs:check — passed; no generated changes.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Some declarations that previously reported unresolved / no-native-candidate now report inferred / decorated-name-candidate.
  • Real Hopper/Ghidra, browser, or OS coverage: Windows binding probes only (above); no native analysis engine involved.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: static metadata comparison only; no target is loaded or executed.

Author readiness

Human owner: @AmmarJamil23

  • 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.

🤖 Generated with Claude Code

🔄 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/6877 **Author:** [@AmmarJamil23](https://github.com/AmmarJamil23) **Created:** 10/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/pinvoke-charset-candidates` --- ### 📝 Commits (1) - [`3d1a2cd`](https://github.com/morluto/rea/commit/3d1a2cd39ed021e26cd4401c82d4f5602b923281) fix(managed): derive P/Invoke suffix candidates for default and Auto charsets ### 📊 Changes **3 files changed** (+85 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `docs/managed-code-analysis.md` (+8 -0) 📝 `src/domain/managed/managedNativeVerificationMatch.ts` (+22 -4) 📝 `tests/conformance/providers/managed/managedNativeVerification.test.ts` (+55 -2) </details> ### 📄 Description ## Summary Fixes #6857. `verify-managed-native-boundaries` added the `A`/`W` entry-point suffix candidate only for an explicit `ansi` or `unicode` charset. A default (`not-specified`) P/Invoke declaration behaves as ANSI, and `Auto` means Unicode on Windows, so their conventional decorated exports (`ExampleA`, `ExampleW`) were dropped and verification reported `unresolved / no-native-candidate`. They are now retained as `inferred / decorated-name-candidate`, the same as the explicit-charset controls. ## Problem and expected behavior Smallest trigger: a P/Invoke `Example` in `example.dll` with mapping flags `0x0200` (charset unspecified, ExactSpelling false) and supplied PE function Evidence named `ExampleA`. Before: `unresolved`, `no-native-candidate`, no candidates; explicit ANSI (`0x0202`) returned `inferred` with `ExampleA`. Same pattern for `Auto` (`0x0206`) with `ExampleW` versus explicit Unicode. Expected (per the issue and Microsoft's [Charsets and marshalling](https://learn.microsoft.com/en-us/dotnet/standard/native-interop/charset) / [Specifying a character set](https://learn.microsoft.com/en-us/dotnet/standard/native-interop/specifying-a-character-set)): the default charset probes the `A` name, `Auto` probes `W` on Windows, and ExactSpelling suppresses suffixes. This stays a static candidate inference, not proof of binding. ## Change and scope The charset parser already preserved `not-specified` and `auto` correctly; the gap was in candidate enumeration (`candidateNames` in `src/domain/managed/managedNativeVerificationMatch.ts`). It now resolves an effective charset per native module: - `not-specified` → ANSI (adds `A`) for every module format; - `auto` → Unicode (adds `W`) when the supplied native Evidence's module format is `pe`, and `unknown` (no suffix candidate) for other formats, because `Auto` means UTF-8 off Windows and the supplied Evidence does not establish suffix probing there; - `ansi`/`unicode` and ExactSpelling (`no_mangle`) behave exactly as before. Candidates are computed per native symbol, since only the symbol's Evidence knows its module format; the existing `moduleFormatsByEvidenceId` map already carried that fact. `docs/managed-code-analysis.md` now states the entry-point rule next to the existing module-name rules. Not changed: stdcall `_Name@N` decorations, module matching, and verification status semantics. Contribution scope: ordinary correctness fix within the existing static-verification boundary; no scope decision needed. ## Contract and boundary impact - Semantic owner and earliest changed stage: P/Invoke candidate enumeration in `managedNativeVerificationMatch.ts`. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: no schema change; affected declarations now return the existing `inferred / decorated-name-candidate` state. - Provider, bridge, target-format, or platform compatibility: the `Auto` suffix applies only to PE modules; ELF, Mach-O and unknown formats get no `Auto` suffix candidate. - Evidence, artifact, provenance, or reconstruction contract: unchanged; matches remain inferences with the supplied native Evidence retained. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none; `npm run docs:check` passed with no generated changes. ## Evidence and regression coverage - Tests added or updated: `tests/conformance/providers/managed/managedNativeVerification.test.ts`, with 10 table cases covering default/ANSI/Unicode/Auto on PE and ELF, wrong-suffix controls, and ExactSpelling suppression. The `nativeFunctionEvidence` helper takes a function name, and `inputWithImportScope` takes a charset/ExactSpelling override. - Base reproduction: with the `src/` change stashed, exactly the 3 bug cases fail (default→`A` on PE, default→`A` on ELF, Auto→`W` on PE); the 7 controls pass on both revisions. - Public CLI: the issue's six-case `verify-managed-native-boundaries` script (adapted for a Windows host), run with the fix: `default-ansi-suffix` and `auto-unicode-suffix` now return `inferred / decorated-name-candidate` with `ExampleA` / `ExampleW`; explicit controls unchanged; `auto-exact-control` stays `verified / exact-function-name`; `exactspelling-control` stays `unresolved / no-native-candidate`. - Real Windows binding behavior (supports the rule; not committed). The issue notes it did not run a live Windows binding test, so I ran `DllImport` probes on Windows 11 x64 (.NET Framework 4.8 via PowerShell `Add-Type`) against system DLLs: - `shell32!CommandLineToArgv`, which is exported only as `CommandLineToArgvW`: `Auto` and `Unicode` bind; default, `Ansi`, and `Auto` + ExactSpelling throw `EntryPointNotFoundException`. - `kernel32!GetModuleHandle`, which is exported only as `GetModuleHandleA` / `GetModuleHandleW`: the default charset binds (so it resolves `GetModuleHandleA`, since the default never probed `W` above); default + ExactSpelling throws `EntryPointNotFoundException`. - Remaining proof gaps: modern .NET (Core) on Windows was not probed live (Microsoft documents the same name matching); non-Windows `Auto` behavior is deliberately left unknown rather than asserted. ## Validation performed Windows 11 x64, Node.js 24.22.1 (pinned), locked dependencies. - `npm run test:focused -- tests/conformance/providers/managed/managedNativeVerification.test.ts` — 30/30 passed; with `src/` stashed, 3 failed / 27 passed (the three bug cases). - `npm run test:focused -- tests/boundary/mcp/managedNativeVerificationAdapters.test.ts tests/boundary/mcp/outputSchemaSemanticConstraints.test.ts` — 4/4 passed. - `npm run build:cached` then the issue's CLI reproduction — results above. - `npm run check:fast` — passed. - `npm run docs:check` — passed; no generated changes. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Some declarations that previously reported `unresolved / no-native-candidate` now report `inferred / decorated-name-candidate`. - Real Hopper/Ghidra, browser, or OS coverage: Windows binding probes only (above); no native analysis engine involved. - Package or release metadata impact: none. - Security, privacy, process, or containment review: static metadata comparison only; no target is loaded or executed. ## Author readiness Human owner: @AmmarJamil23 - [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. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:47:48 +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
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#7429
No description provided.