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 #3760] fix(windows): name the missing native artifact and its recovery path on source checkouts #5879

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3760
Author: @Jackzigen
Created: 10/14/2026
Status: 🔄 Open

Base: main ← Head: fix/windows-native-manifest

📝 Commits (10+)

  • 2eaeb63 fix(windows): name the missing native artifact and its recovery path on source checkouts
  • 3ded799 fix(reference): never resolve a directory to an extensionless index (#3789)
  • 90c6922 fix(javascript): keep empty URL path segments significant (#3792)
  • 7a66470 fix(apple): report plist dates the decoder cannot represent as unknown (#3793)
  • af6a998 fix(javascript): keep string Worker paths unresolved without a document base (#3797)
  • 4692bb3 fix(reference): stop attributing overwritten require members to Node (#3801)
  • baad9ee fix(javascript): reject FIFO recovery inputs without blocking (#3788)
  • 847b732 fix(comparison): keep unnamed reference endpoints distinct or unknown (#3809)
  • 0781716 fix(cli): accept --flag=value for global output flags (#3811)
  • 4135c91 fix(javascript): keep recovered invalid templates dynamic in semantic effects (#3815)

📊 Changes

150 files changed (+9587 additions, -747 deletions)

View changed files

📝 docs/cli.md (+3 -1)
📝 docs/installation.md (+31 -0)
📝 docs/javascript-artifact-reconstruction.md (+8 -1)
📝 docs/native-investigation.md (+12 -1)
📝 licenses/npm-dependencies.txt (+6 -1)
📝 licenses/npm-runtime-notices.txt (+175 -1)
📝 package-lock.json (+19 -0)
📝 package.json (+1 -0)
📝 scripts/hopper-demo-x11.py (+12 -10)
📝 scripts/rea.mjs (+6 -4)
📝 scripts/verify-linux-setup-e2e.mjs (+15 -6)
📝 scripts/verify-package-environment.mjs (+9 -0)
📝 scripts/verify-package-platform.mjs (+20 -5)
📝 scripts/verify-real-hopper-fat.mjs (+1 -1)
📝 scripts/verify-real-hopper.mjs (+1 -1)
📝 src/apktool/ApktoolConfiguration.ts (+73 -21)
📝 src/apktool/ApktoolProvider.ts (+65 -4)
➕ src/apktool/ApktoolVersionProbe.lifecycle.test.ts (+107 -0)
➕ src/apktool/ApktoolVersionProbe.test.ts (+147 -0)
📝 src/application/Doctor.fixture.ts (+11 -1)

...and 80 more files

📄 Description

Summary

Fixes #3501.

A git source checkout on Windows failed every provider admission with a bare ENOENT on native/windows/build/manifest.json, because that directory is gitignored (only the Linux cross-compile lane and the npm tarball carry it). rea doctor also gave no artifact-specific remediation. This PR names the missing artifact and gives an actionable recovery path on source checkouts.

Problem and expected behavior

  • Trigger: install from a git clone on Windows, run any provider command (or rea doctor)
  • Old behavior: every provider rejected at admission with bare ENOENT on manifest.json; doctor hinted unsupported_host with no artifact-specific help
  • Expected: the error names the missing native artifact and tells the user how to get it (npm tarball install, or the documented cross-compile lane)

Change and scope

  • Detect the missing per-platform native manifest on Windows source checkouts and produce a ConfigurationError that names the missing file and lists the recovery paths (npm package install or the Linux cross-compile build lane documented in the README)
  • rea doctor surfaces the same artifact-specific remediation instead of a generic host hint

Follow the contribution scope: error-message and doctor improvements within existing boundaries — no target execution, injection, mutation, or protection recovery, so no maintainer scope decision is required (not applicable).

Contract and boundary impact

  • Semantic owner and earliest changed stage: config/admission layer; doctor output downstream
  • Contribution scope fit and linked maintainer decision: not applicable (ordinary fix within existing boundaries)
  • CLI and MCP/tool-catalog contract: no command or tool added or changed; error text improves
  • Provider, bridge, target-format, or platform compatibility: Windows source-checkout installs; npm tarball and Linux lanes unchanged
  • Evidence, artifact, provenance, or reconstruction contract: none
  • Target selection, authority, upstream behavior, and cleanup details: not applicable
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none

Expected effects (check known effects; use documentation-only on its own).

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject into a process or target.
  • Modify a target or its environment.
  • Send data over a network.
  • Modify this repository or workspace files.
  • none / documentation-only

Compatibility, safety, and release

  • Breaking changes or migration steps: none — error text and doctor output only
  • Real Hopper/Ghidra, browser, or OS coverage: Windows source-checkout scenario covered by tests
  • Package or release metadata impact: none
  • Security, privacy, process, or containment review: no new data exposure; errors name file paths only

Author readiness

Human owner: @Jackzigen

  • 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.
  • Related issue is linked: Fixes #3501.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • 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: the new error text naming the missing artifact and recovery paths.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

Problem

A git clone does not contain native/windows/build/ (gitignored by design — the README documents the Linux cross-compile lane), so a Windows source install rejected every provider at admission with a bare ENOENT on manifest.json, and rea doctor surfaced only an unsupported_host-adjacent hint with no artifact-specific remediation. The npm tarball ships both files, but nothing told the user that.

Changes

  • src/windows/WindowsNativeLoader.ts — the catch on artifact load now distinguishes ENOENT: the failure names the missing manifest.json + rea-windows-x64.node pair, explains why they are absent in source installs (gitignored; ship only in the npm package), and gives both recovery paths: npm run build:windows-native or copying the two files from the matching-version npm tarball into native/windows/build/.
  • src/process/WindowsAuthority.ts — the artifact stage remediation now also points source checkouts at native/windows/README.md.
  • native/windows/README.md — new "Source checkouts on Windows" section with the exact npm pack + tar --strip-components=3 command sequence.
  • Non-ENOENT artifact failures (integrity, PE checks, etc.) keep their original diagnostic text — only the missing-artifact case changed.

Safety

Admission still enforces package version, ABI, Node-API compatibility, PE32+ architecture, and SHA-256 after any manual copy — no validation was relaxed. This is a diagnostics-only change.

Verification

  • src/windows/WindowsNativeLoader.test.ts: +2 tests (ENOENT → actionable message, non-ENOENT unchanged); suite 22/22 green
  • src/ghidra/GhidraDoctor.test.ts: 16/16 green (remediation string still matches its stringContaining lock)
  • Full npm run test:fast: 7665 passed | 13 skipped, 0 failed
  • npx oxfmt clean; oxlint on touched files: 0 warnings 0 errors

🔄 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/3760 **Author:** [@Jackzigen](https://github.com/Jackzigen) **Created:** 10/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/windows-native-manifest` --- ### 📝 Commits (10+) - [`2eaeb63`](https://github.com/morluto/rea/commit/2eaeb63f7ed70eac9f88bb6d64d9548cd66ede35) fix(windows): name the missing native artifact and its recovery path on source checkouts - [`3ded799`](https://github.com/morluto/rea/commit/3ded799bc7b9a588404913b4064aff8c1412a045) fix(reference): never resolve a directory to an extensionless index (#3789) - [`90c6922`](https://github.com/morluto/rea/commit/90c69229050cd251f86294a6f3ff5e22abf6912f) fix(javascript): keep empty URL path segments significant (#3792) - [`7a66470`](https://github.com/morluto/rea/commit/7a66470385636e57191f964ca584484e4bd01d34) fix(apple): report plist dates the decoder cannot represent as unknown (#3793) - [`af6a998`](https://github.com/morluto/rea/commit/af6a9980669129aae882c9216766fc8d9f544079) fix(javascript): keep string Worker paths unresolved without a document base (#3797) - [`4692bb3`](https://github.com/morluto/rea/commit/4692bb33300c7cb77b095b6cc0c33da861c1b860) fix(reference): stop attributing overwritten require members to Node (#3801) - [`baad9ee`](https://github.com/morluto/rea/commit/baad9eebe4c4a381be1e69ab0021acfea382f339) fix(javascript): reject FIFO recovery inputs without blocking (#3788) - [`847b732`](https://github.com/morluto/rea/commit/847b7328cf73907511acc71c554613af31a87b5b) fix(comparison): keep unnamed reference endpoints distinct or unknown (#3809) - [`0781716`](https://github.com/morluto/rea/commit/0781716788f553aba739b339560402b3fe8eb0ec) fix(cli): accept --flag=value for global output flags (#3811) - [`4135c91`](https://github.com/morluto/rea/commit/4135c911d3a3414b17fcd8954a15f6c7ec6ae8f4) fix(javascript): keep recovered invalid templates dynamic in semantic effects (#3815) ### 📊 Changes **150 files changed** (+9587 additions, -747 deletions) <details> <summary>View changed files</summary> 📝 `docs/cli.md` (+3 -1) 📝 `docs/installation.md` (+31 -0) 📝 `docs/javascript-artifact-reconstruction.md` (+8 -1) 📝 `docs/native-investigation.md` (+12 -1) 📝 `licenses/npm-dependencies.txt` (+6 -1) 📝 `licenses/npm-runtime-notices.txt` (+175 -1) 📝 `package-lock.json` (+19 -0) 📝 `package.json` (+1 -0) 📝 `scripts/hopper-demo-x11.py` (+12 -10) 📝 `scripts/rea.mjs` (+6 -4) 📝 `scripts/verify-linux-setup-e2e.mjs` (+15 -6) 📝 `scripts/verify-package-environment.mjs` (+9 -0) 📝 `scripts/verify-package-platform.mjs` (+20 -5) 📝 `scripts/verify-real-hopper-fat.mjs` (+1 -1) 📝 `scripts/verify-real-hopper.mjs` (+1 -1) 📝 `src/apktool/ApktoolConfiguration.ts` (+73 -21) 📝 `src/apktool/ApktoolProvider.ts` (+65 -4) ➕ `src/apktool/ApktoolVersionProbe.lifecycle.test.ts` (+107 -0) ➕ `src/apktool/ApktoolVersionProbe.test.ts` (+147 -0) 📝 `src/application/Doctor.fixture.ts` (+11 -1) _...and 80 more files_ </details> ### 📄 Description ## Summary Fixes #3501. A git source checkout on Windows failed every provider admission with a bare `ENOENT` on `native/windows/build/manifest.json`, because that directory is gitignored (only the Linux cross-compile lane and the npm tarball carry it). `rea doctor` also gave no artifact-specific remediation. This PR names the missing artifact and gives an actionable recovery path on source checkouts. ## Problem and expected behavior - **Trigger**: install from a git clone on Windows, run any provider command (or `rea doctor`) - **Old behavior**: every provider rejected at admission with bare `ENOENT` on `manifest.json`; doctor hinted `unsupported_host` with no artifact-specific help - **Expected**: the error names the missing native artifact and tells the user how to get it (npm tarball install, or the documented cross-compile lane) ## Change and scope - Detect the missing per-platform native manifest on Windows source checkouts and produce a `ConfigurationError` that names the missing file and lists the recovery paths (npm package install or the Linux cross-compile build lane documented in the README) - `rea doctor` surfaces the same artifact-specific remediation instead of a generic host hint Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope): error-message and doctor improvements within existing boundaries — no target execution, injection, mutation, or protection recovery, so no maintainer scope decision is required (not applicable). ## Contract and boundary impact - Semantic owner and earliest changed stage: config/admission layer; doctor output downstream - Contribution scope fit and linked maintainer decision: not applicable (ordinary fix within existing boundaries) - CLI and MCP/tool-catalog contract: no command or tool added or changed; error text improves - Provider, bridge, target-format, or platform compatibility: Windows source-checkout installs; npm tarball and Linux lanes unchanged - Evidence, artifact, provenance, or reconstruction contract: none - Target selection, authority, upstream behavior, and cleanup details: not applicable - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none Expected effects (check known effects; use documentation-only on its own). - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject into a process or target. - [ ] Modify a target or its environment. - [ ] Send data over a network. - [ ] Modify this repository or workspace files. - [ ] none / documentation-only ## Compatibility, safety, and release - Breaking changes or migration steps: none — error text and doctor output only - Real Hopper/Ghidra, browser, or OS coverage: Windows source-checkout scenario covered by tests - Package or release metadata impact: none - Security, privacy, process, or containment review: no new data exposure; errors name file paths only ## Author readiness Human owner: @Jackzigen - [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] Related issue is linked: Fixes #3501. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [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: the new error text naming the missing artifact and recovery paths. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- ## Problem A git clone does not contain `native/windows/build/` (gitignored by design — the README documents the Linux cross-compile lane), so a Windows **source** install rejected every provider at admission with a bare `ENOENT` on `manifest.json`, and `rea doctor` surfaced only an `unsupported_host`-adjacent hint with no artifact-specific remediation. The npm tarball ships both files, but nothing told the user that. ## Changes - **`src/windows/WindowsNativeLoader.ts`** — the catch on artifact load now distinguishes `ENOENT`: the failure names the missing `manifest.json` + `rea-windows-x64.node` pair, explains why they are absent in source installs (gitignored; ship only in the npm package), and gives both recovery paths: `npm run build:windows-native` or copying the two files from the matching-version npm tarball into `native/windows/build/`. - **`src/process/WindowsAuthority.ts`** — the `artifact` stage remediation now also points source checkouts at `native/windows/README.md`. - **`native/windows/README.md`** — new "Source checkouts on Windows" section with the exact `npm pack` + `tar --strip-components=3` command sequence. - Non-ENOENT artifact failures (integrity, PE checks, etc.) keep their original diagnostic text — only the missing-artifact case changed. ## Safety Admission still enforces package version, ABI, Node-API compatibility, PE32+ architecture, and SHA-256 after any manual copy — no validation was relaxed. This is a diagnostics-only change. ## Verification - `src/windows/WindowsNativeLoader.test.ts`: +2 tests (ENOENT → actionable message, non-ENOENT unchanged); suite 22/22 green - `src/ghidra/GhidraDoctor.test.ts`: 16/16 green (remediation string still matches its `stringContaining` lock) - Full `npm run test:fast`: **7665 passed | 13 skipped, 0 failed** - `npx oxfmt` clean; `oxlint` on touched files: 0 warnings 0 errors --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#5879
No description provided.