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 #2642] [CLOSED] fix(javascript): report present non-JavaScript require targets as unavailable #5303

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2642
Author: @cyberpunk47
Created: 10/13/2026
Status: ❌ Closed

Base: main ← Head: fix/javascript-present-non-js-targets

📝 Commits (8)

  • 822e466 fix(javascript): report present non-JavaScript require targets as unavailable
  • d404bbd fix(javascript): preserve opaque target identity through shared resolution
  • 10746e3 fix(javascript): index opaque identities and preserve resolution policy
  • 73534cf fix(javascript): retain partial opaque launch resolution evidence
  • b5ed98b fix(javascript): retain opaque package role candidates
  • 9834235 fix(javascript): retain exact expanded ASAR candidates
  • 97a79c0 Merge branch 'main' into fix/javascript-present-non-js-targets
  • 1366b77 Merge branch 'main' into fix/javascript-present-non-js-targets

📊 Changes

13 files changed (+703 additions, -65 deletions)

View changed files

📝 src/application/javascript/ElectronBoundaryGraphWindows.ts (+40 -8)
📝 src/application/javascript/JavaScriptArtifactGraphBuilder.ts (+1 -0)
📝 src/application/javascript/JavaScriptArtifactGraphContext.ts (+5 -0)
📝 src/application/javascript/JavaScriptArtifactGraphDocuments.ts (+1 -0)
📝 src/application/javascript/JavaScriptArtifactGraphFindings.ts (+40 -19)
📝 src/application/javascript/JavaScriptArtifactGraphStructure.ts (+6 -1)
📝 src/application/javascript/JavaScriptArtifactPathResolution.test.ts (+102 -1)
📝 src/application/javascript/JavaScriptArtifactPathResolution.ts (+66 -33)
📝 src/application/javascript/JavaScriptModuleRelationships.ts (+1 -0)
📝 src/artifacts/javascript/JavaScriptArtifactFiles.ts (+118 -0)
📝 src/domain/artifactInventorySnapshot.ts (+2 -0)
📝 src/domain/javascript/javascriptArtifactFiles.ts (+22 -0)
📝 tests/boundary/filesystem/javascriptRequireLiteralPaths.test.ts (+299 -3)

📄 Description

Summary

Fixes #2641

analyze-javascript-application reported resolution_status: "not-found" for a module target that exists in the analysed artifact when the file is outside the JavaScript-relevant kinds (for example a bytenode .jsc module). The output was identical to a really missing file, and the edge evidence stated that no candidate exists in the inventoried container. This change keeps the inventory identity of such files and reports them as unavailable, with a limitation naming their sha256 and size. Missing files still report not-found.

Problem and expected behavior

Smallest trigger: a directory with main.js containing const core = require("./core.jsc") and a core.jsc file next to it.

  • Before: resolution_status: "not-found", with the limitation "No extension, directory package, or index candidate exists in the inventoried artifact container."
  • After: resolution_status: "unavailable", with the limitation "core.jsc exists in the inventoried artifact container (sha256 …, N bytes) but is not a JavaScript, JSON, HTML, source map, or native add-on file; its contents were not analyzed."

Violated invariant (AGENTS.md): "Unresolved identity or applicability must remain unknown rather than be treated as absent, foreign, or aligned."

Change and scope

  • Producing boundary: src/artifacts/javascript/JavaScriptArtifactFiles.ts skipped inventoried regular files with no relevant kind (if (kind === undefined) continue;) and left no record. It now records them as unanalyzed_files (path, container sha256, sha256, bytes, inventory artifact id) on JavaScriptArtifactFileSet. Their bytes are still never read.
  • JavaScriptArtifactPathResolution.resolveFileCandidates checks those records in the same candidate order as before, keeping the same-container rule. A match returns unavailable instead of falling through to not-found.
  • The graph context carries unanalyzedFilesByPath, and every resolveArtifactPathByContext call built from the context passes it.
  • Not included: no new status value, no contract or schema change, no change to graph-level coverage, and no reading or decoding of bytecode.

Contribution scope: not applicable (routine fix within existing boundaries).

Contract and boundary impact

  • Semantic owner and earliest changed stage: JavaScript artifact file projection (JavaScriptArtifactFiles), then path resolution
  • Contribution scope fit and linked maintainer decision: routine evidence-correctness fix; not applicable
  • CLI and MCP/tool-catalog contract: no schema change; the existing unavailable status is now used for this case
  • Provider, bridge, target-format, or platform compatibility: none
  • Evidence, artifact, provenance, or reconstruction contract: present-but-unanalysed targets keep their inventory identity in the limitation instead of being reported absent
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none

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

  • Tests added or updated:
    • src/application/javascript/JavaScriptArtifactPathResolution.test.ts: require and import targets present outside the projection give unavailable; a target in another container stays not-found; a missing target stays not-found.
    • tests/boundary/filesystem/javascriptRequireLiteralPaths.test.ts: real directory analysis; a present .jsc gives unavailable with its sha256 and size, and the same layout without the file gives not-found.
  • Base reproduction or other evidence: with only the test changes applied to the base revision, the boundary test and both unavailable unit tests fail; the two not-found guard tests pass.
  • User-visible CLI/MCP output (if applicable): see the before/after limitation text above.
  • Remaining proof gaps: graph-level coverage.status remains complete; whether it should change is left to maintainer preference (asked in the issue).

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

  • npx vitest run src/application/javascript src/artifacts src/domain/javascript: 76 files, 1547 tests passed
  • npm run test:focused -- <43 JavaScript boundary test files>: 565 passed, 1 skipped, 1 failed. The failure (packageImportAliases.test.ts, "matches literal imports keys containing path-like bytes in both Node loaders") fails identically on the unmodified base under Node 22.22 (Node returns ERR_INVALID_MODULE_SPECIFIER) and is unrelated to this change.
  • npm run check:fast: typecheck and lint passed
  • oxfmt --check on changed files: passed
  • Manual CLI run on the issue's sample: ./core.jsc reports unavailable; with the file deleted it reports not-found.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Consumers that treat every non-resolved status as unresolved are unaffected; consumers matching not-found specifically will now see unavailable for present, unanalysed targets.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable (static JavaScript analysis only); verified on Linux x64 with Node.js 22.22 and 22.23.
  • Package or release metadata impact: none
  • Security, privacy, process, or containment review: no new reads of file contents and no execution; only inventory metadata the artifact inventory already holds (path, sha256, size) is reported.

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/2642 **Author:** [@cyberpunk47](https://github.com/cyberpunk47) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/javascript-present-non-js-targets` --- ### 📝 Commits (8) - [`822e466`](https://github.com/morluto/rea/commit/822e46606615195881b01542bd99502e25d70f3c) fix(javascript): report present non-JavaScript require targets as unavailable - [`d404bbd`](https://github.com/morluto/rea/commit/d404bbdfac78b1e4172a9ad098b49955a94aafc0) fix(javascript): preserve opaque target identity through shared resolution - [`10746e3`](https://github.com/morluto/rea/commit/10746e3c3fe8a571bb3757cd3d1d350a9951f767) fix(javascript): index opaque identities and preserve resolution policy - [`73534cf`](https://github.com/morluto/rea/commit/73534cf2d4b831f02b298cedbb37339c40813303) fix(javascript): retain partial opaque launch resolution evidence - [`b5ed98b`](https://github.com/morluto/rea/commit/b5ed98b02922ac595a4a027606f088959871ef55) fix(javascript): retain opaque package role candidates - [`9834235`](https://github.com/morluto/rea/commit/9834235c1c981e933d4556bfd89f7eec8d0c548a) fix(javascript): retain exact expanded ASAR candidates - [`97a79c0`](https://github.com/morluto/rea/commit/97a79c05d1b6d2a73756e0135a40f9f33f91fd21) Merge branch 'main' into fix/javascript-present-non-js-targets - [`1366b77`](https://github.com/morluto/rea/commit/1366b773809f7b7c5c66717845d805b4162b89b2) Merge branch 'main' into fix/javascript-present-non-js-targets ### 📊 Changes **13 files changed** (+703 additions, -65 deletions) <details> <summary>View changed files</summary> 📝 `src/application/javascript/ElectronBoundaryGraphWindows.ts` (+40 -8) 📝 `src/application/javascript/JavaScriptArtifactGraphBuilder.ts` (+1 -0) 📝 `src/application/javascript/JavaScriptArtifactGraphContext.ts` (+5 -0) 📝 `src/application/javascript/JavaScriptArtifactGraphDocuments.ts` (+1 -0) 📝 `src/application/javascript/JavaScriptArtifactGraphFindings.ts` (+40 -19) 📝 `src/application/javascript/JavaScriptArtifactGraphStructure.ts` (+6 -1) 📝 `src/application/javascript/JavaScriptArtifactPathResolution.test.ts` (+102 -1) 📝 `src/application/javascript/JavaScriptArtifactPathResolution.ts` (+66 -33) 📝 `src/application/javascript/JavaScriptModuleRelationships.ts` (+1 -0) 📝 `src/artifacts/javascript/JavaScriptArtifactFiles.ts` (+118 -0) 📝 `src/domain/artifactInventorySnapshot.ts` (+2 -0) 📝 `src/domain/javascript/javascriptArtifactFiles.ts` (+22 -0) 📝 `tests/boundary/filesystem/javascriptRequireLiteralPaths.test.ts` (+299 -3) </details> ### 📄 Description ## Summary Fixes #2641 `analyze-javascript-application` reported `resolution_status: "not-found"` for a module target that exists in the analysed artifact when the file is outside the JavaScript-relevant kinds (for example a bytenode `.jsc` module). The output was identical to a really missing file, and the edge evidence stated that no candidate exists in the inventoried container. This change keeps the inventory identity of such files and reports them as `unavailable`, with a limitation naming their sha256 and size. Missing files still report `not-found`. ## Problem and expected behavior Smallest trigger: a directory with `main.js` containing `const core = require("./core.jsc")` and a `core.jsc` file next to it. - Before: `resolution_status: "not-found"`, with the limitation "No extension, directory package, or index candidate exists in the inventoried artifact container." - After: `resolution_status: "unavailable"`, with the limitation "core.jsc exists in the inventoried artifact container (sha256 …, N bytes) but is not a JavaScript, JSON, HTML, source map, or native add-on file; its contents were not analyzed." Violated invariant (AGENTS.md): "Unresolved identity or applicability must remain unknown rather than be treated as absent, foreign, or aligned." ## Change and scope - Producing boundary: `src/artifacts/javascript/JavaScriptArtifactFiles.ts` skipped inventoried regular files with no relevant kind (`if (kind === undefined) continue;`) and left no record. It now records them as `unanalyzed_files` (path, container sha256, sha256, bytes, inventory artifact id) on `JavaScriptArtifactFileSet`. Their bytes are still never read. - `JavaScriptArtifactPathResolution.resolveFileCandidates` checks those records in the same candidate order as before, keeping the same-container rule. A match returns `unavailable` instead of falling through to `not-found`. - The graph context carries `unanalyzedFilesByPath`, and every `resolveArtifactPathByContext` call built from the context passes it. - Not included: no new status value, no contract or schema change, no change to graph-level coverage, and no reading or decoding of bytecode. Contribution scope: not applicable (routine fix within existing boundaries). ## Contract and boundary impact - Semantic owner and earliest changed stage: JavaScript artifact file projection (`JavaScriptArtifactFiles`), then path resolution - Contribution scope fit and linked maintainer decision: routine evidence-correctness fix; not applicable - CLI and MCP/tool-catalog contract: no schema change; the existing `unavailable` status is now used for this case - Provider, bridge, target-format, or platform compatibility: none - Evidence, artifact, provenance, or reconstruction contract: present-but-unanalysed targets keep their inventory identity in the limitation instead of being reported absent - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none 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 - Tests added or updated: - `src/application/javascript/JavaScriptArtifactPathResolution.test.ts`: require and import targets present outside the projection give `unavailable`; a target in another container stays `not-found`; a missing target stays `not-found`. - `tests/boundary/filesystem/javascriptRequireLiteralPaths.test.ts`: real directory analysis; a present `.jsc` gives `unavailable` with its sha256 and size, and the same layout without the file gives `not-found`. - Base reproduction or other evidence: with only the test changes applied to the base revision, the boundary test and both `unavailable` unit tests fail; the two `not-found` guard tests pass. - User-visible CLI/MCP output (if applicable): see the before/after limitation text above. - Remaining proof gaps: graph-level `coverage.status` remains `complete`; whether it should change is left to maintainer preference (asked in the issue). 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 - `npx vitest run src/application/javascript src/artifacts src/domain/javascript`: 76 files, 1547 tests passed - `npm run test:focused -- <43 JavaScript boundary test files>`: 565 passed, 1 skipped, 1 failed. The failure (`packageImportAliases.test.ts`, "matches literal imports keys containing path-like bytes in both Node loaders") fails identically on the unmodified base under Node 22.22 (Node returns `ERR_INVALID_MODULE_SPECIFIER`) and is unrelated to this change. - `npm run check:fast`: typecheck and lint passed - `oxfmt --check` on changed files: passed - Manual CLI run on the issue's sample: `./core.jsc` reports `unavailable`; with the file deleted it reports `not-found`. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Consumers that treat every non-`resolved` status as unresolved are unaffected; consumers matching `not-found` specifically will now see `unavailable` for present, unanalysed targets. - Real Hopper/Ghidra, browser, or OS coverage: not applicable (static JavaScript analysis only); verified on Linux x64 with Node.js 22.22 and 22.23. - Package or release metadata impact: none - Security, privacy, process, or containment review: no new reads of file contents and no execution; only inventory metadata the artifact inventory already holds (path, sha256, size) is reported. ## 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. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:05:34 +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#5303
No description provided.