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 #1862] [MERGED] feat(javascript): resolve exact package import aliases #4858

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1862
Author: @mvanhorn
Created: 10/11/2026
Status: ✅ Merged
Merged: 10/11/2026
Merged by: @morluto

Base: main ← Head: fix/package-imports-aliases

📝 Commits (7)

  • 6bed757 feat(javascript): resolve exact package import aliases
  • 208c404 fix(javascript): keep nested import aliases in CLI graphs
  • 5492780 fix(javascript): resolve literal package import keys before path admission
  • 5603a4d fix(javascript): preserve import keys and invalid-target fallback
  • cfc07f6 fix(javascript): preserve unmatched package target arrays
  • 2f97b2a fix(javascript): retain package target refusal evidence
  • e4ccc23 test(browser): match real verifier startup budget

📊 Changes

10 files changed (+1838 additions, -83 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/references/javascript-applications.md (+4 -1)
📝 docs/javascript-artifact-reconstruction.md (+20 -0)
📝 src/application/javascript/JavaScriptArtifactPathResolution.test.ts (+368 -0)
📝 src/application/javascript/JavaScriptArtifactPathResolution.ts (+238 -80)
➕ src/domain/javascript/javascriptPackageImportAliases.test.ts (+147 -0)
➕ src/domain/javascript/javascriptPackageImportAliases.ts (+98 -0)
➕ tests/acceptance/applications/packageImportAliasesCli.test.ts (+251 -0)
📝 tests/boundary/browser/cdpSvgXlinkHref.test.ts (+9 -2)
📝 tests/boundary/javascript/packageConditionalExports.test.ts (+49 -0)
➕ tests/boundary/javascript/packageImportAliases.test.ts (+654 -0)

📄 Description

Summary

Static JavaScript application analysis now resolves exact package-private #alias specifiers against the importer's enclosing package.json imports map. Inventoried local files become resolved application-graph edges instead of external unknowns, and missing, blocked, or out-of-scope aliases keep an unresolved edge with a precise reason.

Fixes #1838

Demo

demo

The sample is a generated local application, not third-party code.

Problem and expected behavior

A package that declares {"imports":{"#config":"./config.cjs"}} and requires #config leaves a real dependency out of the static application graph. On 0b4ce836, that specifier is resolved_path: null, resolution_status: "external", with the limitation "The bare specifier is a Node builtin, package import map, or invalid package name." Node's resolver selects config.cjs.

The graph should resolve exact #alias keys through the nearest enclosing same-container package.json, stopping at a node_modules directory so a nested package cannot inherit an ancestor's map. Selected targets are package-local ./ files with no extension or index fallback. A missing key, explicit null, or out-of-scope alias reports that reason and does not fall through to files, indexes, or another package's map.

Change and scope

Domain lookup classifies # specifiers and exact imports keys. Application path resolution walks the importer's enclosing package scope, then reuses the existing condition, array, and null target selection. Shared CLI and MCP adapters already thread those resolver outcomes into analyze-javascript-application / analyze_javascript_application graphs; no new tool is added.

  • Exact #alias keys resolve relative to the owning package root.
  • Nested node_modules packages use their own imports map.
  • ESM #config is treated as an import alias, not a URL fragment.
  • Wildcard keys (#internal/*), recursive # targets, and external-package import targets remain unresolved with that limitation.

Out of scope: wildcard expansion, recursive alias chasing, external-package targets, TypeScript paths, browser import maps, package installation, network access, and target execution.

Contract and boundary impact

  • Semantic owner and earliest changed stage: domain src/domain/javascript/javascriptPackageImportAliases.ts, then application JavaScriptArtifactPathResolution, before graph relationship construction.
  • CLI and MCP/tool-catalog contract: none. Existing analyze_javascript_application / analyze-javascript-application schemas, names, and adapters are unchanged; resolution outcomes flow through the current resolution_status / resolved_path / limitations fields.
  • Provider, bridge, target-format, or platform compatibility: static JavaScript artifacts only; no Hopper, Ghidra, IDA, or browser provider changes.
  • Evidence, artifact, provenance, or reconstruction contract: original specifier, source path, artifact digest, source range, and container identity are preserved. Unsupported alias forms stay explicit unknowns rather than guessed files.
  • Process execution, authorization, cleanup, or containment impact: none. Resolution reads the inventoried file map only; artifact-root confinement remains enforced.
  • 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): authored skill reference javascript-applications.md and docs/javascript-artifact-reconstruction.md updated. Catalog is regenerated by the repo build and is not committed.

Evidence and regression coverage

  • Tests added or updated: domain specifier/lookup/target classification; application enclosing-scope, conditions, arrays, exact-file, missing-key, explicit-null, wildcard, recursive, external-package, reserved #, and foreign-container refusals; Node import/require oracle comparisons including nested packages without an imports field; compiled CLI and stdio MCP graphs on an owned fixture.
  • Base reproduction or other evidence: on 0b4ce836, #config against the fixture above is external with the builtin/import-map limitation. After this change the same specifier is resolved_path: "config.cjs", resolution_status: "resolved".
  • User-visible CLI/MCP output (if applicable): generated local fixture. Root #config → config.cjs (resolved); nested node_modules/fixture #config → node_modules/fixture/local.cjs (resolved); #missing → resolved_path: null, resolution_status: "external", limitation "Package metadata package.json does not define package import alias #missing; it declares #config."
  • Remaining proof gaps: wildcard, recursive, and external-package import targets are intentionally unresolved. Real Hopper/Ghidra and browser lanes do not apply. This host did not rerun a Windows package.

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

  • npm ci — pass (377 packages added, 378 audited, 0 vulnerabilities)
  • npm run test:focused -- src/domain/javascript/javascriptPackageImportAliases.test.ts src/application/javascript/JavaScriptArtifactPathResolution.test.ts tests/boundary/javascript/packageImportAliases.test.ts tests/acceptance/applications/packageImportAliasesCli.test.ts — pass (4 files, 111 tests; CLI 1255 ms, stdio MCP 3863 ms)
  • npm run check:fast — pass
  • npm run check — pass (typecheck, lint, format:check, knip, metadata:check; 6/6 turbo tasks; architecture guards across 1138 source files; lint 753 warnings, 0 errors)
  • npm run docs:check — pass
  • npm run verify:test-discovery — pass (“Discovered all 839 test files exactly once.”)

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Additive resolution inside the existing application-graph contract. # specifiers that previously stayed external now resolve when an exact enclosing imports key selects an inventoried ./ file; unsupported forms remain unresolved.
  • Real Hopper/Ghidra, browser, or OS coverage: not run. This change is static JavaScript path resolution. CLI/MCP and Node resolver comparisons ran on Linux with Node 24.18.0.
  • Package or release metadata impact: none. No new tool, skill version, or package identity change.
  • Security, privacy, process, or containment review: caller-selected inputs and source evidence remain intact. Same-container package-scope checks and artifact-root confinement are preserved. No network, installation, or target execution is introduced.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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/1862 **Author:** [@mvanhorn](https://github.com/mvanhorn) **Created:** 10/11/2026 **Status:** ✅ Merged **Merged:** 10/11/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/package-imports-aliases` --- ### 📝 Commits (7) - [`6bed757`](https://github.com/morluto/rea/commit/6bed757006f2128dbe82a77ba01ca480180cd242) feat(javascript): resolve exact package import aliases - [`208c404`](https://github.com/morluto/rea/commit/208c40463c772a891dc42b29325c1e347537889a) fix(javascript): keep nested import aliases in CLI graphs - [`5492780`](https://github.com/morluto/rea/commit/5492780737ee7b445b203f1f2dfcf86b7bd1af04) fix(javascript): resolve literal package import keys before path admission - [`5603a4d`](https://github.com/morluto/rea/commit/5603a4d84273bd2ba38d56c73da4bc993432ae90) fix(javascript): preserve import keys and invalid-target fallback - [`cfc07f6`](https://github.com/morluto/rea/commit/cfc07f6cc5c0adea77505812df0d1780128263c6) fix(javascript): preserve unmatched package target arrays - [`2f97b2a`](https://github.com/morluto/rea/commit/2f97b2a757ac34ccf49ce7ee1c3f670d1dde9880) fix(javascript): retain package target refusal evidence - [`e4ccc23`](https://github.com/morluto/rea/commit/e4ccc234029f9abc7e31cc61cd534e835c72bc1d) test(browser): match real verifier startup budget ### 📊 Changes **10 files changed** (+1838 additions, -83 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/references/javascript-applications.md` (+4 -1) 📝 `docs/javascript-artifact-reconstruction.md` (+20 -0) 📝 `src/application/javascript/JavaScriptArtifactPathResolution.test.ts` (+368 -0) 📝 `src/application/javascript/JavaScriptArtifactPathResolution.ts` (+238 -80) ➕ `src/domain/javascript/javascriptPackageImportAliases.test.ts` (+147 -0) ➕ `src/domain/javascript/javascriptPackageImportAliases.ts` (+98 -0) ➕ `tests/acceptance/applications/packageImportAliasesCli.test.ts` (+251 -0) 📝 `tests/boundary/browser/cdpSvgXlinkHref.test.ts` (+9 -2) 📝 `tests/boundary/javascript/packageConditionalExports.test.ts` (+49 -0) ➕ `tests/boundary/javascript/packageImportAliases.test.ts` (+654 -0) </details> ### 📄 Description ## Summary Static JavaScript application analysis now resolves exact package-private `#alias` specifiers against the importer's enclosing `package.json` `imports` map. Inventoried local files become resolved application-graph edges instead of external unknowns, and missing, blocked, or out-of-scope aliases keep an unresolved edge with a precise reason. Fixes #1838 ## Demo ![demo](https://raw.githubusercontent.com/mvanhorn/pr-demo-assets/main/rea/package-imports-aliases/demo.gif) <video src="https://raw.githubusercontent.com/mvanhorn/pr-demo-assets/main/rea/package-imports-aliases/demo.mp4" controls width="720"></video> The sample is a generated local application, not third-party code. ## Problem and expected behavior A package that declares `{"imports":{"#config":"./config.cjs"}}` and requires `#config` leaves a real dependency out of the static application graph. On `0b4ce836`, that specifier is `resolved_path: null`, `resolution_status: "external"`, with the limitation "The bare specifier is a Node builtin, package import map, or invalid package name." Node's resolver selects `config.cjs`. The graph should resolve exact `#alias` keys through the nearest enclosing same-container `package.json`, stopping at a `node_modules` directory so a nested package cannot inherit an ancestor's map. Selected targets are package-local `./` files with no extension or index fallback. A missing key, explicit null, or out-of-scope alias reports that reason and does not fall through to files, indexes, or another package's map. ## Change and scope Domain lookup classifies `#` specifiers and exact `imports` keys. Application path resolution walks the importer's enclosing package scope, then reuses the existing condition, array, and null target selection. Shared CLI and MCP adapters already thread those resolver outcomes into `analyze-javascript-application` / `analyze_javascript_application` graphs; no new tool is added. - Exact `#alias` keys resolve relative to the owning package root. - Nested `node_modules` packages use their own `imports` map. - ESM `#config` is treated as an import alias, not a URL fragment. - Wildcard keys (`#internal/*`), recursive `#` targets, and external-package import targets remain unresolved with that limitation. Out of scope: wildcard expansion, recursive alias chasing, external-package targets, TypeScript `paths`, browser import maps, package installation, network access, and target execution. ## Contract and boundary impact - Semantic owner and earliest changed stage: domain `src/domain/javascript/javascriptPackageImportAliases.ts`, then application `JavaScriptArtifactPathResolution`, before graph relationship construction. - CLI and MCP/tool-catalog contract: none. Existing `analyze_javascript_application` / `analyze-javascript-application` schemas, names, and adapters are unchanged; resolution outcomes flow through the current `resolution_status` / `resolved_path` / limitations fields. - Provider, bridge, target-format, or platform compatibility: static JavaScript artifacts only; no Hopper, Ghidra, IDA, or browser provider changes. - Evidence, artifact, provenance, or reconstruction contract: original specifier, source path, artifact digest, source range, and container identity are preserved. Unsupported alias forms stay explicit unknowns rather than guessed files. - Process execution, authorization, cleanup, or containment impact: none. Resolution reads the inventoried file map only; artifact-root confinement remains enforced. - 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): authored skill reference `javascript-applications.md` and `docs/javascript-artifact-reconstruction.md` updated. Catalog is regenerated by the repo build and is not committed. ## Evidence and regression coverage - Tests added or updated: domain specifier/lookup/target classification; application enclosing-scope, conditions, arrays, exact-file, missing-key, explicit-null, wildcard, recursive, external-package, reserved `#`, and foreign-container refusals; Node import/require oracle comparisons including nested packages without an `imports` field; compiled CLI and stdio MCP graphs on an owned fixture. - Base reproduction or other evidence: on `0b4ce836`, `#config` against the fixture above is external with the builtin/import-map limitation. After this change the same specifier is `resolved_path: "config.cjs"`, `resolution_status: "resolved"`. - User-visible CLI/MCP output (if applicable): generated local fixture. Root `#config` → `config.cjs` (`resolved`); nested `node_modules/fixture` `#config` → `node_modules/fixture/local.cjs` (`resolved`); `#missing` → `resolved_path: null`, `resolution_status: "external"`, limitation "Package metadata package.json does not define package import alias #missing; it declares #config." - Remaining proof gaps: wildcard, recursive, and external-package import targets are intentionally unresolved. Real Hopper/Ghidra and browser lanes do not apply. This host did not rerun a Windows package. 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 - `npm ci` — pass (377 packages added, 378 audited, 0 vulnerabilities) - `npm run test:focused -- src/domain/javascript/javascriptPackageImportAliases.test.ts src/application/javascript/JavaScriptArtifactPathResolution.test.ts tests/boundary/javascript/packageImportAliases.test.ts tests/acceptance/applications/packageImportAliasesCli.test.ts` — pass (4 files, 111 tests; CLI 1255 ms, stdio MCP 3863 ms) - `npm run check:fast` — pass - `npm run check` — pass (typecheck, lint, format:check, knip, metadata:check; 6/6 turbo tasks; architecture guards across 1138 source files; lint 753 warnings, 0 errors) - `npm run docs:check` — pass - `npm run verify:test-discovery` — pass (“Discovered all 839 test files exactly once.”) ## Compatibility, safety, and release - Breaking changes or migration steps: none. Additive resolution inside the existing application-graph contract. `#` specifiers that previously stayed external now resolve when an exact enclosing `imports` key selects an inventoried `./` file; unsupported forms remain unresolved. - Real Hopper/Ghidra, browser, or OS coverage: not run. This change is static JavaScript path resolution. CLI/MCP and Node resolver comparisons ran on Linux with Node 24.18.0. - Package or release metadata impact: none. No new tool, skill version, or package identity change. - Security, privacy, process, or containment review: caller-selected inputs and source evidence remain intact. Same-container package-scope checks and artifact-root confinement are preserved. No network, installation, or target execution is introduced. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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. - [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 00:56:06 +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#4858
No description provided.