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 #3803] [MERGED] fix(javascript): preserve case-sensitive Unicode seed identity #5909

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3803
Author: @AdityaKharmaleGoat7
Created: 10/15/2026
Status: ✅ Merged
Merged: 10/17/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/case-sensitive-feature-seed-unicode

📝 Commits (8)

  • 90b8d2d fix(javascript): preserve case-sensitive Unicode seed identity
  • c56e26e Merge remote-tracking branch 'origin/main' into cifix/3803
  • a7fa460 test(javascript): use the contains seed match in the Unicode test
  • e30e68d Merge branch 'main' into fix/case-sensitive-feature-seed-unicode
  • ab56363 Merge branch 'main' into fix/case-sensitive-feature-seed-unicode
  • 500fd8d Merge branch 'main' into fix/case-sensitive-feature-seed-unicode
  • 67af4d7 Merge branch 'main' into fix/case-sensitive-feature-seed-unicode
  • 5177d13 Merge branch 'main' into fix/case-sensitive-feature-seed-unicode

📊 Changes

2 files changed (+59 additions, -1 deletions)

View changed files

📝 src/domain/javascript/javascriptFeatureSeed.ts (+1 -1)
➕ src/domain/javascript/javascriptFeatureSeed.unicode.test.ts (+58 -0)

📄 Description

Fixes #3314

Summary

Preserve compatibility-distinct strings during case-sensitive application feature-seed matching while retaining the existing compatibility fold for explicit case-insensitive matching.

Problem and expected behavior

An exact case-sensitive channel seed for ff currently also selects the distinct ff channel because both query and candidate are normalized with NFKC. Issue #3314 has been independently reproduced on current main, and no existing PR claims it.

Case-sensitive matching should preserve the distinction between compatibility-equivalent strings. Case-insensitive matching should retain the existing NFKC-based query behavior.

Change and scope

  • use NFC rather than NFKC when case_sensitive is true
  • retain NFKC plus lower-casing for explicit case-insensitive matching
  • add focused tests covering exact matching, substring matching, and the existing case-insensitive compatibility fold

Contribution scope fit and linked maintainer decision: ordinary correctness fix inside the existing static feature-seed matcher; no new authority or provider capability.

Contract and boundary impact

  • Semantic owner and earliest changed stage: JavaScript application feature-seed selection.
  • CLI and MCP/tool-catalog contract: unchanged schemas; corrected matching semantics for case-sensitive literal seeds.
  • Provider, bridge, target-format, or platform compatibility: unchanged.
  • Evidence, artifact, provenance, or reconstruction contract: prevents unrelated compatibility-equivalent nodes from entering a selected trace.
  • Target selection, authority, upstream behavior, and cleanup details: no target interaction or execution change.
  • Generated metadata, package, or installation impact: none.

Evidence and regression coverage

  • Tests added: focused unit coverage for ff versus ff under exact case-sensitive, substring case-sensitive, and explicit case-insensitive matching.
  • Base reproduction: issue #3314 was independently reproduced on recent main; current main still uses NFKC for case-sensitive matches.
  • Remaining proof gaps: local repository test execution was unavailable in this environment; CI is the authoritative validation.

Validation performed

  • branch is based directly on upstream main at af6a9980669129aae882c9216766fc8d9f544079
  • branch comparison is 0 commits behind that base
  • diff is limited to one matcher line and focused regression coverage

Compatibility, safety, and release

  • Breaking changes or migration steps: none; this narrows case-sensitive matching to the documented literal identity instead of compatibility-folded identity.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; pure static domain logic.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new process, filesystem, network, or target authority.

Maintainer review update — Linux (17 October 2026)

Reviewed head: ab56363a9230919cff07b4535a2038f027a3d8c9, merged with main 150e996a86f2bec4982ba87f37bf502a8d5e8214. Its whole tree matches the independently computed integration tree; its stable patch ID matches the previously reviewed change, and it does not modify workflows.

52 feature-seed tests pass. Compiled CLI/MCP workflows pass: case-sensitive ff and ff select distinct source identities, substring matching preserves that distinction, insensitive matching selects their union, and absent queries stay empty. Full Evidence agrees between adapters; the source fixture is unchanged and is not executed as Electron.

Historical baseline: the former firmware and three async BinarySessionStatus failures were independently reproduced earlier; both are now repaired upstream. The current-head baseline is recorded below.

Local jobs ran serially on two CPU cores with a 3 GiB Node heap; maximum sampled job-family RSS across this retry was 3.28 GiB, with no resource stop. This is not a measurement of the assistant/shared host total. Model token use, controlled cold/warm comparison and remote resource costs are unmeasured.

Baseline follow-up (2026-10-17)

Current head 5177d13f4824ef0aada5f14560edc209d43df888 incorporates main 5b243993872c2bcc70cb00060ffb79b347321370, including the normally merged #4691/#4703 fixture repairs. Exact merge-tree verification and stable patch IDs confirm that this PR's patch is unchanged by the update. Current-head CI: All five built-dependent shards and all required gates passed on unchanged attempt 3. The first worker OOM remains documented below.

Fresh exact-head production build and public static JavaScript workflow pass through 6 CLI and 5 MCP calls: exact and substring case-sensitive identities remain distinct, insensitive matching selects their union, absent selection remains empty, and complete Evidence agrees between adapters. Input source remains unchanged. Completed task: 15.03 s wall, 19.18 s reaped CPU, 1.10 GiB sampled process-family RSS. Hosted shard 5 failed because its existing 384 MiB cli-boundary worker exhausted its heap while running cliIntegerArguments.test.ts; no feature assertion failed. Failure logs are retained. The unchanged rerun passed that shard and the complete required CI gates with the same 384 MiB worker bound. The feature patch does not touch this test or runner configuration; the cause remains unconfirmed and is tracked separately in #4713. No heap/timeout increase, test skip or feature-code change was used.

Local heavy jobs ran serially on two CPU cores with a 3 GiB Node heap. RSS is sampled process-family memory, may double-count shared pages and excludes assistant/shared services; CPU covers reaped descendants. OS/dependency caches were not controlled. Model token use, controlled cold/warm costs and remote resource costs remain unmeasured; no token or speedup claim is inferred. Prior observations above remain tied to their stated revisions. Initial human-owner readiness remains valid and was not supplied on the author's behalf. Available automated reviews have no unresolved findings; Codex explicitly reports repository review-credit exhaustion, so no fresh Codex review is claimed.

Author readiness

Human owner: @AdityaKharmaleGoat7

  • 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.
  • 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/3803 **Author:** [@AdityaKharmaleGoat7](https://github.com/AdityaKharmaleGoat7) **Created:** 10/15/2026 **Status:** ✅ Merged **Merged:** 10/17/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/case-sensitive-feature-seed-unicode` --- ### 📝 Commits (8) - [`90b8d2d`](https://github.com/morluto/rea/commit/90b8d2ddffd5b1326c706925c5518394c0f23126) fix(javascript): preserve case-sensitive Unicode seed identity - [`c56e26e`](https://github.com/morluto/rea/commit/c56e26e227214891f538371410ed033d9fd8a55f) Merge remote-tracking branch 'origin/main' into cifix/3803 - [`a7fa460`](https://github.com/morluto/rea/commit/a7fa46037a671443eb81af1aeb6bb642ea9164c9) test(javascript): use the contains seed match in the Unicode test - [`e30e68d`](https://github.com/morluto/rea/commit/e30e68d1f5a505130708ed2c22193d96abf639db) Merge branch 'main' into fix/case-sensitive-feature-seed-unicode - [`ab56363`](https://github.com/morluto/rea/commit/ab56363a9230919cff07b4535a2038f027a3d8c9) Merge branch 'main' into fix/case-sensitive-feature-seed-unicode - [`500fd8d`](https://github.com/morluto/rea/commit/500fd8d7654ace8547838eda637a2c6c56826a59) Merge branch 'main' into fix/case-sensitive-feature-seed-unicode - [`67af4d7`](https://github.com/morluto/rea/commit/67af4d7fb70dc5a20cda46955e3fa7dd2dc5b061) Merge branch 'main' into fix/case-sensitive-feature-seed-unicode - [`5177d13`](https://github.com/morluto/rea/commit/5177d13f4824ef0aada5f14560edc209d43df888) Merge branch 'main' into fix/case-sensitive-feature-seed-unicode ### 📊 Changes **2 files changed** (+59 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/javascript/javascriptFeatureSeed.ts` (+1 -1) ➕ `src/domain/javascript/javascriptFeatureSeed.unicode.test.ts` (+58 -0) </details> ### 📄 Description Fixes #3314 ## Summary Preserve compatibility-distinct strings during case-sensitive application feature-seed matching while retaining the existing compatibility fold for explicit case-insensitive matching. ## Problem and expected behavior An exact case-sensitive channel seed for `ff` currently also selects the distinct `ff` channel because both query and candidate are normalized with NFKC. Issue #3314 has been independently reproduced on current main, and no existing PR claims it. Case-sensitive matching should preserve the distinction between compatibility-equivalent strings. Case-insensitive matching should retain the existing NFKC-based query behavior. ## Change and scope - use NFC rather than NFKC when `case_sensitive` is true - retain NFKC plus lower-casing for explicit case-insensitive matching - add focused tests covering exact matching, substring matching, and the existing case-insensitive compatibility fold Contribution scope fit and linked maintainer decision: ordinary correctness fix inside the existing static feature-seed matcher; no new authority or provider capability. ## Contract and boundary impact - Semantic owner and earliest changed stage: JavaScript application feature-seed selection. - CLI and MCP/tool-catalog contract: unchanged schemas; corrected matching semantics for case-sensitive literal seeds. - Provider, bridge, target-format, or platform compatibility: unchanged. - Evidence, artifact, provenance, or reconstruction contract: prevents unrelated compatibility-equivalent nodes from entering a selected trace. - Target selection, authority, upstream behavior, and cleanup details: no target interaction or execution change. - Generated metadata, package, or installation impact: none. ## Evidence and regression coverage - Tests added: focused unit coverage for `ff` versus `ff` under exact case-sensitive, substring case-sensitive, and explicit case-insensitive matching. - Base reproduction: issue #3314 was independently reproduced on recent main; current main still uses NFKC for case-sensitive matches. - Remaining proof gaps: local repository test execution was unavailable in this environment; CI is the authoritative validation. ## Validation performed - branch is based directly on upstream `main` at `af6a9980669129aae882c9216766fc8d9f544079` - branch comparison is 0 commits behind that base - diff is limited to one matcher line and focused regression coverage ## Compatibility, safety, and release - Breaking changes or migration steps: none; this narrows case-sensitive matching to the documented literal identity instead of compatibility-folded identity. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; pure static domain logic. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new process, filesystem, network, or target authority. ### Maintainer review update — Linux (17 October 2026) Reviewed head: `ab56363a9230919cff07b4535a2038f027a3d8c9`, merged with main `150e996a86f2bec4982ba87f37bf502a8d5e8214`. Its whole tree matches the independently computed integration tree; its stable patch ID matches the previously reviewed change, and it does not modify workflows. 52 feature-seed tests pass. Compiled CLI/MCP workflows pass: case-sensitive `ff` and `ff` select distinct source identities, substring matching preserves that distinction, insensitive matching selects their union, and absent queries stay empty. Full Evidence agrees between adapters; the source fixture is unchanged and is not executed as Electron. Historical baseline: the former firmware and three async BinarySessionStatus failures were independently reproduced earlier; both are now repaired upstream. The current-head baseline is recorded below. Local jobs ran serially on two CPU cores with a 3 GiB Node heap; maximum sampled job-family RSS across this retry was 3.28 GiB, with no resource stop. This is not a measurement of the assistant/shared host total. Model token use, controlled cold/warm comparison and remote resource costs are unmeasured. ## Baseline follow-up (2026-10-17) Current head `5177d13f4824ef0aada5f14560edc209d43df888` incorporates main `5b243993872c2bcc70cb00060ffb79b347321370`, including the normally merged #4691/#4703 fixture repairs. Exact merge-tree verification and stable patch IDs confirm that this PR's patch is unchanged by the update. [Current-head CI](https://github.com/morluto/rea/actions/runs/39011262277): All five built-dependent shards and all required gates passed on unchanged attempt 3. The first worker OOM remains documented below. Fresh exact-head production build and public static JavaScript workflow pass through 6 CLI and 5 MCP calls: exact and substring case-sensitive identities remain distinct, insensitive matching selects their union, absent selection remains empty, and complete Evidence agrees between adapters. Input source remains unchanged. Completed task: 15.03 s wall, 19.18 s reaped CPU, 1.10 GiB sampled process-family RSS. Hosted shard 5 failed because its existing 384 MiB cli-boundary worker exhausted its heap while running cliIntegerArguments.test.ts; no feature assertion failed. Failure logs are retained. The unchanged rerun passed that shard and the complete required CI gates with the same 384 MiB worker bound. The feature patch does not touch this test or runner configuration; the cause remains unconfirmed and is tracked separately in #4713. No heap/timeout increase, test skip or feature-code change was used. Local heavy jobs ran serially on two CPU cores with a 3 GiB Node heap. RSS is sampled process-family memory, may double-count shared pages and excludes assistant/shared services; CPU covers reaped descendants. OS/dependency caches were not controlled. Model token use, controlled cold/warm costs and remote resource costs remain unmeasured; no token or speedup claim is inferred. Prior observations above remain tied to their stated revisions. Initial human-owner readiness remains valid and was not supplied on the author's behalf. Available automated reviews have no unresolved findings; Codex explicitly reports repository review-credit exhaustion, so no fresh Codex review is claimed. ## Author readiness Human owner: @AdityaKharmaleGoat7 - [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. - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:10:21 +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#5909
No description provided.