[PR #4323] [MERGED] fix(javascript): resolve relative ESM backslash paths #6172

New issue

Closed

opened 2026-10-31 01:12:25 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:12:25 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4323
Author: @6eanut
Created: 10/16/2026
Status: ✅ Merged
Merged: 10/28/2026
Merged by: @morluto

Base: main ← Head: fix/esm-reference-path-4269

---

📝 Commits (1)

• 361ef67 fix(javascript): resolve relative ESM backslash paths

📊 Changes

3 files changed (+75 additions, -11 deletions)

View changed files

📝 src/application/javascript/JavaScriptArtifactPathResolution.test.ts (+35 -0)
📝 src/application/javascript/JavaScriptArtifactPathResolution.ts (+5 -1)
📝 tests/boundary/filesystem/javascript-applications/javascriptModuleSpecifierPaths.test.ts (+35 -10)

📄 Description

Summary

Narrows this PR to the remaining relative ESM backslash case requested in the maintainer follow-up. Main already resolves #4269 via f2e5fd148; this revision keeps that implementation and drops the superseded source-import changes.

Problem and expected behavior

Node loads a relative import such as ./nested\direct.mjs as nested/direct.mjs, and historical reference lookup already finds it. Artifact analysis rejected the same request before URL parsing, leaving its graph edge unresolved. Both consumers should select the file loaded by Node while preserving the authored specifier.

Change and scope

Normalize raw backslashes inside the existing artifact ESM URL owner, only after the original request satisfies ./ or ../ relative-module admission. Existing URL parsing, encoded-separator/NUL checks and root confinement still own validity. Production changes are confined to one function; there is no replacement source parser or new helper layer.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

• Semantic owner and earliest changed stage: contextualCandidate() in JavaScriptArtifactPathResolution, before canonical-path admission and URL/root checks. Historical import already uses its own URL parser and remains on main's implementation; its distinct inventory-decoding policy is retained.
• Contribution scope fit and linked maintainer decision: ordinary static-analysis fix; a new capability scope decision is not applicable. The requested focus is linked in Summary.
• CLI and MCP/tool-catalog contract: no command/schema change; application graph imports gain the correct resolved_path for valid relative module URLs.
• Provider, bridge, target-format, or platform compatibility: no new provider/bridge behavior. Verified on Linux with Node 24.22.1; Windows execution was not performed.
• Evidence, artifact, provenance, or reconstruction contract: authored declared_path/graph specifiers and existing inventory identities are preserved. Historical source_specifier, literal-backslash filenames and decoding remain governed by main's existing contract.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): no new product execution or cleanup authority. Loader controls execute only self-authored temporary modules.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): no authored metadata, dependency or installation change.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

• 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 or updated: eight resolver cases covering valid relative separators, parent traversal, preserved declarations and invalid inputs. The existing Node-backed matrix now includes static/dynamic raw-backslash controls, literal-name decoys and historical/application graph comparisons.
• Base reproduction or other evidence: before the fix, resolver tests had 3 failures / 298 passes, and the boundary file had 1 failure / 26 passes: Node loaded the target while artifact analysis returned no resolved path. The changed production file is identical between the original tested base 9c9c64ed and final base 25b69bb8.
• User-visible CLI/MCP output (if applicable): no output schema change. Node-backed application graph checks assert both the original specifier and resolved target; compiled historical CLI controls verify retained source semantics.
• Remaining proof gaps: full suite and Windows execution were not run. Full npm run check is blocked by the pre-existing Knip findings listed below.

For boundary fixes, identify the applicable boundary regressions
and lifecycle regressions
covered by the evidence above, and explain relevant gaps.

Covered: format assumptions and raw identity/normalization, including malformed encodings and confinement. Product resource lifecycle is unchanged; fixture cleanup uses the existing scoped helpers and subprocess timeouts.

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

Toolchain: Node 24.22.1, npm 11.16.0; base 25b69bb803.

• npm run test:focused -- src/application/javascript/JavaScriptArtifactPathResolution.test.ts tests/boundary/filesystem/javascript-applications/javascriptModuleSpecifierPaths.test.ts tests/boundary/cli/referenceSourceModuleSemantics.test.ts tests/boundary/cli/referenceSourceUtf8.test.ts — 336 passed, 4 files; includes actual Node static/dynamic loading.
• npm run check:fast — typecheck and lint passed, 2/2 tasks.
• node scripts/run-turbo.mjs run format:check metadata:check — 2/2 tasks passed.
• npm run verify:architecture-guards — passed across 2,152 source files.
• npm run lint:typed — zero errors; 3,762 warnings reported.
• npm run verify:test-discovery — all 2,634 test files discovered exactly once.
• Targeted V8 coverage of the resolver test file — 301 passed; resolver statement coverage 669/761 (87.91%), including execution of the new normalization statements.
• npm run check — failed in Knip: unused staticFileUrlPath and exported type ObjcClassImportBindingCoverage. The same unused declarations are reproducible on an unmodified base; those files are outside this diff. Full check is not claimed as passed.
• npm audit --json — one existing moderate fast-uri entry, zero high/critical; dependency files unchanged.
• git diff --check — passed.

Compatibility, safety, and release

• Breaking changes or migration steps: none.
• Real Hopper/Ghidra, browser, or OS coverage: Linux Node loader, application workflow and historical CLI controls executed. No real provider/browser/Windows workflow was exercised.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: relative module admission precedes separator conversion; encoded separators, NUL and above-root requests remain rejected by the artifact owner. CommonJS/compiler-dependent paths retain their existing handling.

Author readiness

Human owner: @6eanut

• 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/4323 **Author:** [@6eanut](https://github.com/6eanut) **Created:** 10/16/2026 **Status:** ✅ Merged **Merged:** 10/28/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/esm-reference-path-4269` --- ### 📝 Commits (1) - [`361ef67`](https://github.com/morluto/rea/commit/361ef67cc2b45a698011dc7f5e6b840d2d433ed0) fix(javascript): resolve relative ESM backslash paths ### 📊 Changes **3 files changed** (+75 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `src/application/javascript/JavaScriptArtifactPathResolution.test.ts` (+35 -0) 📝 `src/application/javascript/JavaScriptArtifactPathResolution.ts` (+5 -1) 📝 `tests/boundary/filesystem/javascript-applications/javascriptModuleSpecifierPaths.test.ts` (+35 -10) </details> ### 📄 Description <!-- PR title: type(optional-scope): imperative outcome The title becomes the squash-merge commit subject and generated changelog entry. --> ## Summary Narrows this PR to the remaining relative ESM backslash case requested in the [maintainer follow-up](https://github.com/morluto/rea/pull/4323#issuecomment-6427983034). Main already resolves #4269 via f2e5fd148; this revision keeps that implementation and drops the superseded source-import changes. <!-- What user, agent, or maintainer problem does this solve? Link the issue with "Fixes #123" when applicable. Keep the prior behavior, expected contract, and new behavior understandable without private context. --> ## Problem and expected behavior Node loads a relative import such as `./nested\direct.mjs` as `nested/direct.mjs`, and historical reference lookup already finds it. Artifact analysis rejected the same request before URL parsing, leaving its graph edge unresolved. Both consumers should select the file loaded by Node while preserving the authored specifier. <!-- For fixes, give the smallest trigger and violated invariant. For features, describe the use case and observable outcome. --> ## Change and scope Normalize raw backslashes inside the existing artifact ESM URL owner, only after the original request satisfies `./` or `../` relative-module admission. Existing URL parsing, encoded-separator/NUL checks and root confinement still own validity. Production changes are confined to one function; there is no replacement source parser or new helper layer. <!-- Explain the chosen approach, why it fits REA's architecture, and what is intentionally not included. If adding complexity for a speculative or vanishingly unlikely race or security edge case, record the concrete failure mode, likelihood, complexity cost, and the user's buy-in obtained before implementation. Do not silently expand scope for theoretical robustness. --> Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact <!-- Short answers are welcome. Complete applicable lines; mark unresolved facts as "unknown". Use "none" or "not applicable" only when established. --> - Semantic owner and earliest changed stage: `contextualCandidate()` in `JavaScriptArtifactPathResolution`, before canonical-path admission and URL/root checks. Historical import already uses its own URL parser and remains on main's implementation; its distinct inventory-decoding policy is retained. <!-- Name the producer of parsed facts or resources and its affected consumers. Summarize superseded paths removed and any distinct policy, lifecycle, lazy-loading, or compatibility responsibility retained. --> - Contribution scope fit and linked maintainer decision: ordinary static-analysis fix; a new capability scope decision is not applicable. The requested focus is linked in Summary. - CLI and MCP/tool-catalog contract: no command/schema change; application graph imports gain the correct `resolved_path` for valid relative module URLs. - Provider, bridge, target-format, or platform compatibility: no new provider/bridge behavior. Verified on Linux with Node 24.22.1; Windows execution was not performed. - Evidence, artifact, provenance, or reconstruction contract: authored `declared_path`/graph specifiers and existing inventory identities are preserved. Historical `source_specifier`, literal-backslash filenames and decoding remain governed by main's existing contract. - Target selection, authority, upstream behavior, and cleanup details (if applicable): no new product execution or cleanup authority. Loader controls execute only self-authored temporary modules. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): no authored metadata, dependency or installation change. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [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 <!-- State whether evidence is executed, source-derived, or proposed. For fixes, show the original failure and explain how the regression would fail on the affected base revision when practical. Include the most useful proof inline; link long logs or artifacts, or put them in optional details. Documentation-only changes can use source, link, or rendered-document checks. --> - Tests added or updated: eight resolver cases covering valid relative separators, parent traversal, preserved declarations and invalid inputs. The existing Node-backed matrix now includes static/dynamic raw-backslash controls, literal-name decoys and historical/application graph comparisons. - Base reproduction or other evidence: before the fix, resolver tests had 3 failures / 298 passes, and the boundary file had 1 failure / 26 passes: Node loaded the target while artifact analysis returned no resolved path. The changed production file is identical between the original tested base 9c9c64ed and final base 25b69bb8. - User-visible CLI/MCP output (if applicable): no output schema change. Node-backed application graph checks assert both the original specifier and resolved target; compiled historical CLI controls verify retained source semantics. - Remaining proof gaps: full suite and Windows execution were not run. Full `npm run check` is blocked by the pre-existing Knip findings listed below. For boundary fixes, identify the applicable [boundary regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#boundary-regressions) and [lifecycle regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#lifecycle-regressions) covered by the evidence above, and explain relevant gaps. Covered: format assumptions and raw identity/normalization, including malformed encodings and confinement. Product resource lifecycle is unchanged; fixture cleanup uses the existing scoped helpers and subprocess timeouts. 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 <!-- List only commands that actually ran, with observed results. Include the relevant real-provider or platform workflow, or explain why it was unavailable. Keep these results current after changes; a command without its result is incomplete. --> Toolchain: Node 24.22.1, npm 11.16.0; base 25b69bb803ffe337cca705629ec88cd220ca09a7. - `npm run test:focused -- src/application/javascript/JavaScriptArtifactPathResolution.test.ts tests/boundary/filesystem/javascript-applications/javascriptModuleSpecifierPaths.test.ts tests/boundary/cli/referenceSourceModuleSemantics.test.ts tests/boundary/cli/referenceSourceUtf8.test.ts` — **336 passed**, 4 files; includes actual Node static/dynamic loading. - `npm run check:fast` — typecheck and lint passed, 2/2 tasks. - `node scripts/run-turbo.mjs run format:check metadata:check` — 2/2 tasks passed. - `npm run verify:architecture-guards` — passed across 2,152 source files. - `npm run lint:typed` — zero errors; 3,762 warnings reported. - `npm run verify:test-discovery` — all 2,634 test files discovered exactly once. - Targeted V8 coverage of the resolver test file — 301 passed; resolver statement coverage **669/761 (87.91%)**, including execution of the new normalization statements. - `npm run check` — failed in Knip: unused `staticFileUrlPath` and exported type `ObjcClassImportBindingCoverage`. The same unused declarations are reproducible on an unmodified base; those files are outside this diff. Full check is **not** claimed as passed. - `npm audit --json` — one existing moderate `fast-uri` entry, zero high/critical; dependency files unchanged. - `git diff --check` — passed. ## Compatibility, safety, and release <!-- Call out breaking changes, migrations, package effects, platform/provider limits, security/privacy/containment implications, and meaningful proof gaps. --> - Breaking changes or migration steps: none. <!-- For ! / BREAKING CHANGE: show a previously valid call/configuration, its new behavior and migration, and why compatibility/deprecation cannot preserve it. Every release increments minor, including breaking changes; keep breaking markers and migration notes so callers can assess compatibility. See docs/releasing.md. --> - Real Hopper/Ghidra, browser, or OS coverage: Linux Node loader, application workflow and historical CLI controls executed. No real provider/browser/Windows workflow was exercised. - Package or release metadata impact: none. - Security, privacy, process, or containment review: relative module admission precedes separator conversion; encoded separators, NUL and above-root requests remain rejected by the artifact owner. CommonJS/compiler-dependent paths retain their existing handling. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @6eanut - [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 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] 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.}

bsakaguchi 2026-10-31 01:12:25 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-01 21:45:58 +00:00

[PR #6172] [MERGED] fix(artifacts): name the ASAR header admission budget #7180

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

Subscribe

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#6172

No description provided.