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 #4551] [CLOSED] fix(native): filter unlocated Swift symbols from dispatch metadata inspection #6302

New issue
Closed
opened 2026-10-31 01:13:25 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:13:25 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4551
Author: @jayinvers
Created: 10/16/2026
Status: ❌ Closed

Base: main ← Head: fix/swift-symbol-empty-address

📝 Commits (3)

  • e09bc0f fix(native): filter unlocated Swift symbols from dispatch metadata inspection
  • cccbf9d ci: retrigger checks
  • 7b6399f ci: verify checks still trigger

📊 Changes

2 files changed (+63 additions, -10 deletions)

View changed files

📝 src/domain/native/objcSwiftMetadata.test.ts (+44 -0)
📝 src/domain/native/objcSwiftMetadata.ts (+19 -10)

📄 Description

Summary

Fixes #4542.

When inspect_native_dispatch_metadata falls back to a provider's list_names inventory, a Swift-mangled symbol with an empty address ("", unlocated) was pushed into swift_symbols unchanged, and the final objcSwiftMetadataSchema.parse threw an unhandled ZodError (too_small: expected string to have >=1 characters at swift_symbols[0].address). The CLI command and the MCP tool lost the whole result, including every ObjC class and method decoded from the same inventory. Unlocated Swift symbols are now omitted, and the inspection returns the remaining valid metadata.

Problem and expected behavior

Smallest trigger: a list_names inventory containing an entry such as { address: "", name: "$s4Test7MyClassC" }. swiftSymbolSchema.address is z.string().min(1), so the projection crashed at the final parse. The application boundary parses list_names output with addressedValue, whose address is a plain z.string(), so an empty address reaches the domain function unfiltered; EnhancedTools and the CLI command funnel into the same inspectNativeDispatch workflow, so no caller rejects it first. Violated invariant: the domain projection must emit schema-conforming records, not crash on parse when a provider reports an unlocated symbol. Expected behavior (per the issue): unlocated Swift symbols are filtered and the operation returns the rest of the decoded ObjcSwiftMetadata.

Change and scope

In inspectNativeDispatchMetadata (src/domain/native/objcSwiftMetadata.ts):

  • Every examined Swift-mangled name (isSwiftMangledSymbolName(name) || name.startsWith("_Tt")) is still counted, but only entries with a non-empty address are recorded in swift_symbols.
  • The swift_declarations coverage facet keeps the honest examined count (located and unlocated), stays partial when Swift names were observed, and reports unlocated_swift_symbols_omitted_and_names_are_not_demangled when any were dropped, so the omission stays visible instead of silent.

Not included: no schema change (swiftSymbolSchema.address stays z.string().min(1); relaxing it would change the published CLI/MCP output contract), and no ObjC-side change (those address fields are nullable and already accept ""). Inventories whose Swift symbols all have addresses produce byte-identical output to before.

Contribution scope: ordinary fix within existing boundaries; not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: domain symbol-name projection (inspectNativeDispatchMetadata in src/domain/native/objcSwiftMetadata.ts).
  • Contribution scope fit and linked maintainer decision: not applicable (bug fix within the existing read-only inspection boundary).
  • CLI and MCP/tool-catalog contract: no schema change. inspect-native-dispatch-metadata and the matching MCP tool now succeed on inventories containing unlocated Swift symbols instead of throwing. New swift_declarations coverage reason value when symbols are omitted; examined now also counts unlocated Swift names (identical to before when every Swift symbol is located).
  • Provider, bridge, target-format, or platform compatibility: none; provider inputs and adapters are unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged; recorded symbols carry identical evidence, and omitted symbols remain visible through the coverage facet.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable.
  • Generated metadata, package, or installation impact: none.

Expected effects:

  • 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: two cases in src/domain/native/objcSwiftMetadata.test.ts:
    • omits unlocated Swift symbols instead of failing the inspection: empty-address $s4Test7MyClassC (mangling-prefix path) and _TtC4Test7MyClassC (legacy _Tt path) mixed with a valid ObjC class symbol, an ObjC method symbol, and a located Swift symbol; asserts only the located Swift symbol is recorded, the class and method still decode, and swift_declarations coverage reports examined: 3.
    • succeeds with empty swift_symbols when no Swift symbol is located: only unlocated Swift symbols; asserts swift_symbols is empty and coverage stays partial with the omission reason.
  • Base reproduction: on the base revision (4838f444 plus only the new tests) both new tests fail with the reported ZodError: Too small: expected string to have >=1 characters at swift_symbols[0].address / swift_symbols[1].address, while the two pre-existing tests pass; with the fix, all four pass.
  • User-visible CLI/MCP output: not captured; no real provider was run (see gaps).
  • Remaining proof gaps: no end-to-end reproduction against a real provider inventory (e.g. Ghidra or Hopper on a real binary); regression coverage is at the domain unit level, which is where the invariant lives.

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

Node 24.18.0 (.nvmrc), Windows. Branch fix/swift-symbol-empty-address off upstream/main at 4838f444.

  • npm run test:local -- src/domain/native/objcSwiftMetadata.test.ts 鈥?before the fix: 2 new tests failed with the reported ZodError, 2 pre-existing passed; after the fix: 4 passed.
  • npm run check:fast 鈥?typecheck and lint both successful (also re-ran clean as the pre-push hook).
  • npx oxfmt --check src/domain/native/objcSwiftMetadata.ts src/domain/native/objcSwiftMetadata.test.ts 鈥?all matched files use the correct format.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; input that previously crashed now succeeds, and published schemas are unchanged.
  • Real Hopper/Ghidra, browser, or OS coverage: none performed; the change is validated at the domain level.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: not applicable; in-process data projection only.

Author readiness

Human owner: @jayinvers

  • 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/4551 **Author:** [@jayinvers](https://github.com/jayinvers) **Created:** 10/16/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/swift-symbol-empty-address` --- ### 📝 Commits (3) - [`e09bc0f`](https://github.com/morluto/rea/commit/e09bc0f8da548b1bd6c77986d49656cbc4814da5) fix(native): filter unlocated Swift symbols from dispatch metadata inspection - [`cccbf9d`](https://github.com/morluto/rea/commit/cccbf9d977e1b985c2b6af41be733235777adfc9) ci: retrigger checks - [`7b6399f`](https://github.com/morluto/rea/commit/7b6399f404bd3329c6fb040b44cd324354c7f21c) ci: verify checks still trigger ### 📊 Changes **2 files changed** (+63 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/native/objcSwiftMetadata.test.ts` (+44 -0) 📝 `src/domain/native/objcSwiftMetadata.ts` (+19 -10) </details> ### 📄 Description ## Summary Fixes #4542. When `inspect_native_dispatch_metadata` falls back to a provider's `list_names` inventory, a Swift-mangled symbol with an empty address (`""`, unlocated) was pushed into `swift_symbols` unchanged, and the final `objcSwiftMetadataSchema.parse` threw an unhandled `ZodError` (`too_small: expected string to have >=1 characters at swift_symbols[0].address`). The CLI command and the MCP tool lost the whole result, including every ObjC class and method decoded from the same inventory. Unlocated Swift symbols are now omitted, and the inspection returns the remaining valid metadata. ## Problem and expected behavior Smallest trigger: a `list_names` inventory containing an entry such as `{ address: "", name: "$s4Test7MyClassC" }`. `swiftSymbolSchema.address` is `z.string().min(1)`, so the projection crashed at the final `parse`. The application boundary parses `list_names` output with `addressedValue`, whose `address` is a plain `z.string()`, so an empty address reaches the domain function unfiltered; `EnhancedTools` and the CLI command funnel into the same `inspectNativeDispatch` workflow, so no caller rejects it first. Violated invariant: the domain projection must emit schema-conforming records, not crash on `parse` when a provider reports an unlocated symbol. Expected behavior (per the issue): unlocated Swift symbols are filtered and the operation returns the rest of the decoded `ObjcSwiftMetadata`. ## Change and scope In `inspectNativeDispatchMetadata` (`src/domain/native/objcSwiftMetadata.ts`): - Every examined Swift-mangled name (`isSwiftMangledSymbolName(name) || name.startsWith("_Tt")`) is still counted, but only entries with a non-empty address are recorded in `swift_symbols`. - The `swift_declarations` coverage facet keeps the honest `examined` count (located and unlocated), stays `partial` when Swift names were observed, and reports `unlocated_swift_symbols_omitted_and_names_are_not_demangled` when any were dropped, so the omission stays visible instead of silent. Not included: no schema change (`swiftSymbolSchema.address` stays `z.string().min(1)`; relaxing it would change the published CLI/MCP output contract), and no ObjC-side change (those address fields are nullable and already accept `""`). Inventories whose Swift symbols all have addresses produce byte-identical output to before. Contribution scope: ordinary fix within existing boundaries; not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: domain symbol-name projection (`inspectNativeDispatchMetadata` in `src/domain/native/objcSwiftMetadata.ts`). - Contribution scope fit and linked maintainer decision: not applicable (bug fix within the existing read-only inspection boundary). - CLI and MCP/tool-catalog contract: no schema change. `inspect-native-dispatch-metadata` and the matching MCP tool now succeed on inventories containing unlocated Swift symbols instead of throwing. New `swift_declarations` coverage reason value when symbols are omitted; `examined` now also counts unlocated Swift names (identical to before when every Swift symbol is located). - Provider, bridge, target-format, or platform compatibility: none; provider inputs and adapters are unchanged. - Evidence, artifact, provenance, or reconstruction contract: unchanged; recorded symbols carry identical evidence, and omitted symbols remain visible through the coverage facet. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none. Expected effects: - [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: two cases in `src/domain/native/objcSwiftMetadata.test.ts`: - `omits unlocated Swift symbols instead of failing the inspection`: empty-address `$s4Test7MyClassC` (mangling-prefix path) and `_TtC4Test7MyClassC` (legacy `_Tt` path) mixed with a valid ObjC class symbol, an ObjC method symbol, and a located Swift symbol; asserts only the located Swift symbol is recorded, the class and method still decode, and `swift_declarations` coverage reports `examined: 3`. - `succeeds with empty swift_symbols when no Swift symbol is located`: only unlocated Swift symbols; asserts `swift_symbols` is empty and coverage stays `partial` with the omission reason. - Base reproduction: on the base revision (4838f444 plus only the new tests) both new tests fail with the reported `ZodError: Too small: expected string to have >=1 characters` at `swift_symbols[0].address` / `swift_symbols[1].address`, while the two pre-existing tests pass; with the fix, all four pass. - User-visible CLI/MCP output: not captured; no real provider was run (see gaps). - Remaining proof gaps: no end-to-end reproduction against a real provider inventory (e.g. Ghidra or Hopper on a real binary); regression coverage is at the domain unit level, which is where the invariant lives. 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 Node 24.18.0 (`.nvmrc`), Windows. Branch `fix/swift-symbol-empty-address` off `upstream/main` at 4838f444. - `npm run test:local -- src/domain/native/objcSwiftMetadata.test.ts` 鈥?before the fix: 2 new tests failed with the reported ZodError, 2 pre-existing passed; after the fix: 4 passed. - `npm run check:fast` 鈥?typecheck and lint both successful (also re-ran clean as the pre-push hook). - `npx oxfmt --check src/domain/native/objcSwiftMetadata.ts src/domain/native/objcSwiftMetadata.test.ts` 鈥?all matched files use the correct format. ## Compatibility, safety, and release - Breaking changes or migration steps: none; input that previously crashed now succeeds, and published schemas are unchanged. - Real Hopper/Ghidra, browser, or OS coverage: none performed; the change is validated at the domain level. - Package or release metadata impact: none. - Security, privacy, process, or containment review: not applicable; in-process data projection only. ## Author readiness Human owner: @jayinvers - [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 - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:13:25 +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#6302
No description provided.