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 #3627] [CLOSED] fix(harmony): retain JavaScript runtime hints #5856

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3627
Author: @eco-null
Created: 10/14/2026
Status: ❌ Closed

Base: main ← Head: fix/harmony-javascript-runtime-hints

📝 Commits (2)

  • e92ff9e fix(harmony): retain JavaScript runtime hints
  • 4d2beb8 chore(harmony): sync PR with current main

📊 Changes

3 files changed (+77 additions, -4 deletions)

View changed files

📝 src/domain/harmony/harmonyApplication.ts (+6 -4)
📝 tests/acceptance/harmonyArtifactJourney.test.ts (+29 -0)
📝 tests/boundary/filesystem/harmony/application.test.ts (+42 -0)

📄 Description

Current status: proposal adapted into main

Maintainer commit fc935d0df incorporates this proposal and its regressions into a broader mobile runtime-component correction. Its commit message explicitly credits @eco-null and PR #3627. Issue #3350 is now closed as completed. This PR itself is still open and has not been merged; its production fix is superseded by that upstream commit, so no duplicate implementation or conflict-resolution push is proposed.

Independent local verification of pinned main fc935d0df on Windows, Node 24.18.0/npm 11.16.0: 27/27 tests passed in three files (tests/boundary/filesystem/harmony/application.test.ts, tests/acceptance/harmonyArtifactJourney.test.ts, tests/acceptance/applications/androidRuntimeComponentHints.test.ts). The two Harmony regression files match this PR's files exactly. The CLI/MCP acceptance workflows use generated fixtures; this is not a new real-package/provider proof or upstream CI result. Existing branch validation below is historical and remains tied to its recorded head.

The original proposal and validation record follow; the existing human readiness declarations are preserved.

Summary

Fixes #3350. HarmonyOS projection now retains the javascript runtime-family hint whenever its authenticated component list contains JavaScript, including .jsx, .ts, .tsx, .mts, and .cts sources.

Problem and expected behavior

The inventory already classifies these source extensions as javascript-bundle, and the projection includes them in components.javascript. A second, narrower filename regex in the runtime summary omitted the same components. An inert HAP with only index.tsx therefore returned a JavaScript component and an empty runtime-family list despite complete inventory coverage.

Change and scope

Derive the JavaScript hint from the already classified component collection and remove the duplicated suffix interpretation. Keep existing path-based fallback behavior and all other runtime-family rules. No schema, provider, or execution authority changes.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Harmony application domain projection, runtime-family derivation.
  • Contribution scope fit and linked maintainer decision: ordinary static-projection bug fix; additional scope decision not applicable.
  • CLI and MCP/tool-catalog contract: same schemas and shared workflow; corrected runtime_families values.
  • Provider, bridge, target-format, or platform compatibility: HAP, HSP, and App Pack projections; no provider/bridge changes.
  • Evidence, artifact, provenance, or reconstruction contract: preserve component paths, hashes, source Evidence and limitations; the projection ID reflects the corrected result.
  • Target selection, authority, upstream behavior, and cleanup: existing authenticated inventory only; no target-code execution or new effects.
  • Generated metadata, package, or installation impact: none; build outputs remain uncommitted.

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

Validated after merging pinned origin/main 5e30969cc5f1255d44ec7a1f1ca8dbac0af5e7c4 on Windows x64 with Node 24.18.0/npm 11.16.0. This incorporates current main's inventory expectation coverage: { scope: "container-entries", status: "complete" } and preserves the original three-file PR scope.

  • With this PR's tests on that main revision and the original production owner restored temporarily, 6 failed / 20 passed: the five .jsx, .ts, .tsx, .mts, .cts runtime hints and the compiled acceptance journey. Fixed source was restored in finally before rebuilding.
  • With the fix restored, 26/26 passed. Boundary cases cover each source extension, deterministic projection and unrelated-content controls. The compiled CLI/stdio MCP journey covers HAP, HSP and App Pack projection parity, session closure and unchanged source bytes.
  • The SHA-pinned real Harmony pipeline HAP passed CLI inspection/projection, stdio MCP parity, closure and unchanged source bytes on this updated tree. That package is an Ark control without the five regression extensions; those are covered by inert owned ZIP fixtures.
  • This independently repeats the before/after result described in the contributor's review comment. Their Linux results are their report, not an independently executed Linux run here.

Validation performed

Executed on the updated tree:

  • npm ci — locked installation passed; audit reported 0 vulnerabilities.

  • npm run test:focused -- tests/boundary/filesystem/harmony/application.test.ts tests/acceptance/harmonyArtifactJourney.test.ts — 26 passed after the six-failure baseline above.

  • npm run check — passed typecheck, lint, formatting, knip, metadata and architecture guards; lint has 0 errors and repository warnings.

  • npm run verify:test-discovery — 1,352 test files discovered exactly once.

  • npm run fixtures:harmony — existing pinned HAP SHA-256 verified.

  • REA_HARMONY_TEST_HAP=<absolute fixture path> npm run verify:harmony — passed (environment set with PowerShell).

  • git diff --check and pre-commit formatting/lint — passed.

  • npm run check:fast — passed through the pre-push hook.

Update commit: 4d2beb84476923727d5fad446ce3cae843bc1780 merges the pinned main revision without rewriting the original contribution commit. The PR diff remains three files (77 additions / 4 deletions).

The commands above are local results. Upstream CI run 38787800875 subsequently completed successfully for head 4d2beb84476923727d5fad446ce3cae843bc1780, including static checks, source tests, package build, documentation generation, all five test shards, bundled Windows x64 native controls, Linux native package baseline, Portable tests and the CI required aggregate. Conditional provider/platform jobs marked skipped do not establish real-provider coverage. Greptile's 5/5 code review is separate from CI.

Compatibility, safety, and release

No breaking schema or migration changes. Static inventory inference remains an inference, not evidence of target execution. No target scripts were executed; no HarmonyOS SDK, browser or native analysis engine was used. Local macOS/Linux runs, the complete local deterministic gate and controlled performance/token measurements were not run; upstream CI results are recorded above; no performance improvement is claimed.

Author readiness

Human owner: @eco-null

AI-assisted contribution. Human owner @eco-null reports reviewing the final diff and validation evidence and has completed all three initial-readiness declarations.

AI-assisted technical review checked the three-file diff against updated main, including the shared component classification owner, runtime-family derivation, regression proof and validation limits. No unrelated change or remaining duplicate JavaScript suffix interpretation was found in the touched projection. This is an agent technical review; the human owner's previously completed initial-readiness declarations remain below.

  • 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 (existing documented behavior is restored; schemas and catalog are unchanged).
  • User-visible CLI/MCP changes include representative output.
  • AI-assisted technical review checked the final diff for secrets, unrelated cleanup, and unsupported claims; the human owner has completed the readiness declarations above.

🔄 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/3627 **Author:** [@eco-null](https://github.com/eco-null) **Created:** 10/14/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/harmony-javascript-runtime-hints` --- ### 📝 Commits (2) - [`e92ff9e`](https://github.com/morluto/rea/commit/e92ff9e1c4f89f1011d6f5858e70839f226477ee) fix(harmony): retain JavaScript runtime hints - [`4d2beb8`](https://github.com/morluto/rea/commit/4d2beb84476923727d5fad446ce3cae843bc1780) chore(harmony): sync PR with current main ### 📊 Changes **3 files changed** (+77 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/harmony/harmonyApplication.ts` (+6 -4) 📝 `tests/acceptance/harmonyArtifactJourney.test.ts` (+29 -0) 📝 `tests/boundary/filesystem/harmony/application.test.ts` (+42 -0) </details> ### 📄 Description ## Current status: proposal adapted into main Maintainer commit [fc935d0df](https://github.com/morluto/rea/commit/fc935d0df3d7589363242e9e5718c94a4262f1d4) incorporates this proposal and its regressions into a broader mobile runtime-component correction. Its commit message explicitly credits @eco-null and PR #3627. Issue #3350 is now closed as completed. This PR itself is still open and has not been merged; its production fix is superseded by that upstream commit, so no duplicate implementation or conflict-resolution push is proposed. Independent local verification of pinned main `fc935d0df` on Windows, Node 24.18.0/npm 11.16.0: **27/27 tests passed in three files** (`tests/boundary/filesystem/harmony/application.test.ts`, `tests/acceptance/harmonyArtifactJourney.test.ts`, `tests/acceptance/applications/androidRuntimeComponentHints.test.ts`). The two Harmony regression files match this PR's files exactly. The CLI/MCP acceptance workflows use generated fixtures; this is not a new real-package/provider proof or upstream CI result. Existing branch validation below is historical and remains tied to its recorded head. The original proposal and validation record follow; the existing human readiness declarations are preserved. --- ## Summary Fixes #3350. HarmonyOS projection now retains the `javascript` runtime-family hint whenever its authenticated component list contains JavaScript, including `.jsx`, `.ts`, `.tsx`, `.mts`, and `.cts` sources. ## Problem and expected behavior The inventory already classifies these source extensions as `javascript-bundle`, and the projection includes them in `components.javascript`. A second, narrower filename regex in the runtime summary omitted the same components. An inert HAP with only `index.tsx` therefore returned a JavaScript component and an empty runtime-family list despite complete inventory coverage. ## Change and scope Derive the JavaScript hint from the already classified component collection and remove the duplicated suffix interpretation. Keep existing path-based fallback behavior and all other runtime-family rules. No schema, provider, or execution authority changes. ## Contract and boundary impact - Semantic owner and earliest changed stage: Harmony application domain projection, runtime-family derivation. - Contribution scope fit and linked maintainer decision: ordinary static-projection bug fix; additional scope decision not applicable. - CLI and MCP/tool-catalog contract: same schemas and shared workflow; corrected `runtime_families` values. - Provider, bridge, target-format, or platform compatibility: HAP, HSP, and App Pack projections; no provider/bridge changes. - Evidence, artifact, provenance, or reconstruction contract: preserve component paths, hashes, source Evidence and limitations; the projection ID reflects the corrected result. - Target selection, authority, upstream behavior, and cleanup: existing authenticated inventory only; no target-code execution or new effects. - Generated metadata, package, or installation impact: none; build outputs remain uncommitted. 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 Validated after merging pinned `origin/main` `5e30969cc5f1255d44ec7a1f1ca8dbac0af5e7c4` on Windows x64 with Node 24.18.0/npm 11.16.0. This incorporates current main's inventory expectation `coverage: { scope: "container-entries", status: "complete" }` and preserves the original three-file PR scope. - With this PR's tests on that main revision and the original production owner restored temporarily, **6 failed / 20 passed**: the five `.jsx`, `.ts`, `.tsx`, `.mts`, `.cts` runtime hints and the compiled acceptance journey. Fixed source was restored in `finally` before rebuilding. - With the fix restored, **26/26 passed**. Boundary cases cover each source extension, deterministic projection and unrelated-content controls. The compiled CLI/stdio MCP journey covers HAP, HSP and App Pack projection parity, session closure and unchanged source bytes. - The SHA-pinned real Harmony pipeline HAP passed CLI inspection/projection, stdio MCP parity, closure and unchanged source bytes on this updated tree. That package is an Ark control without the five regression extensions; those are covered by inert owned ZIP fixtures. - This independently repeats the before/after result described in the [contributor's review comment](https://github.com/morluto/rea/pull/3627#issuecomment-6199278013). Their Linux results are their report, not an independently executed Linux run here. ## Validation performed Executed on the updated tree: - `npm ci` — locked installation passed; audit reported 0 vulnerabilities. - `npm run test:focused -- tests/boundary/filesystem/harmony/application.test.ts tests/acceptance/harmonyArtifactJourney.test.ts` — **26 passed** after the six-failure baseline above. - `npm run check` — passed typecheck, lint, formatting, knip, metadata and architecture guards; lint has 0 errors and repository warnings. - `npm run verify:test-discovery` — **1,352 test files** discovered exactly once. - `npm run fixtures:harmony` — existing pinned HAP SHA-256 verified. - `REA_HARMONY_TEST_HAP=<absolute fixture path> npm run verify:harmony` — passed (environment set with PowerShell). - `git diff --check` and pre-commit formatting/lint — passed. - `npm run check:fast` — passed through the pre-push hook. Update commit: `4d2beb84476923727d5fad446ce3cae843bc1780` merges the pinned main revision without rewriting the original contribution commit. The PR diff remains three files (77 additions / 4 deletions). The commands above are local results. Upstream [CI run 38787800875](https://github.com/morluto/rea/actions/runs/38787800875) subsequently completed successfully for head `4d2beb84476923727d5fad446ce3cae843bc1780`, including static checks, source tests, package build, documentation generation, all five test shards, bundled Windows x64 native controls, Linux native package baseline, Portable tests and the `CI required` aggregate. Conditional provider/platform jobs marked skipped do not establish real-provider coverage. Greptile's 5/5 code review is separate from CI. ## Compatibility, safety, and release No breaking schema or migration changes. Static inventory inference remains an inference, not evidence of target execution. No target scripts were executed; no HarmonyOS SDK, browser or native analysis engine was used. Local macOS/Linux runs, the complete local deterministic gate and controlled performance/token measurements were not run; upstream CI results are recorded above; no performance improvement is claimed. ## Author readiness Human owner: @eco-null AI-assisted contribution. Human owner @eco-null reports reviewing the final diff and validation evidence and has completed all three initial-readiness declarations. AI-assisted technical review checked the three-file diff against updated main, including the shared component classification owner, runtime-family derivation, regression proof and validation limits. No unrelated change or remaining duplicate JavaScript suffix interpretation was found in the touched projection. This is an agent technical review; the human owner's previously completed initial-readiness declarations remain below. - [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 (existing documented behavior is restored; schemas and catalog are unchanged). - [x] User-visible CLI/MCP changes include representative output. - [x] AI-assisted technical review checked the final diff for secrets, unrelated cleanup, and unsupported claims; the human owner has completed the readiness declarations above. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:09:58 +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#5856
No description provided.