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

[GH-ISSUE #117] Add semantic analysis for JavaScript and packaged application bundles #74

New issue
Closed
opened 2026-10-15 18:20:50 +00:00 by bsakaguchi · 1 comment
bsakaguchi commented 2026-10-15 18:20:50 +00:00
Owner
Copy link

Originally created by @morluto on GitHub (Jul 13, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/117

Problem Statement

REA can classify, open, hash, and inventory JavaScript targets, source maps, archives, and Electron application bundles. It can also import JavaScript and TypeScript as historical reference source. It cannot yet recover semantic structure from a shipped bundle.

For a published client distributed as one minified or bundled JavaScript artifact, agents cannot use REA to answer:

  • which logical modules and package versions are present;
  • which code is application-owned, generated, vendored, or runtime scaffolding;
  • how imports, exports, dynamic loads, and cross-chunk references connect;
  • which functions or behaviors changed between releases;
  • whether a source map matches the shipped bytes and what authority it provides;
  • where JavaScript crosses into Electron, Node.js native addons, WebAssembly, or other embedded runtimes.

Native Hopper procedure tools correctly do not claim support for JavaScript. Today agents must combine REA artifact inventory with external source indexing and runtime tests. The missing capability is semantic bundle analysis with REA evidence and comparison contracts.

This is a focused implementation issue under #42, not a replacement for the broader managed-runtime and package-provider roadmap.

Proposed Solution

Add a provider-neutral bundle-analysis capability family backed initially by a JavaScript/package provider. Keep parser, bundler, and runtime-specific code outside the domain and application layers.

Initial targets

  • plain JavaScript, ESM, and CommonJS;
  • Webpack, Rollup, esbuild, Parcel, Browserify, and similar bundles;
  • split chunks and lazy-loaded assets;
  • npm package trees and lockfile-backed distributions;
  • Electron ASAR applications and preload/renderer/main-process bundles;
  • Node.js snapshots or bytecode when a provider can make truthful claims;
  • embedded WebAssembly and native addon boundaries.

Unsupported or ambiguous formats must remain explicit unknowns.

Capability model

Candidate provider operations:

  • identify_bundle
  • inventory_modules
  • inspect_bundle_function
  • resolve_bundle_graph
  • map_source_artifacts
  • compare_bundles
  • trace_runtime_bridge

Public tool names and grouping may differ after contract review. CLI and MCP must expose equivalent behavior.

Required results

Bundle analysis should produce deterministic, bounded records for:

  • artifact digest and exact byte ranges;
  • detected bundler/runtime and confidence;
  • logical module, chunk, and package identities;
  • imports, exports, re-exports, dynamic imports, and loader edges;
  • recovered function identities with byte/line locations;
  • generated, vendored, dependency, and application-owned classifications;
  • package and lockfile provenance where observed;
  • source-map identity, validation status, and mapping authority;
  • JavaScript-to-native, JavaScript-to-WebAssembly, Electron IPC, and preload boundaries;
  • limitations, residual unknowns, and parser/provider versions.

Derived names or reconstructed source must be labeled as inference. Original shipped bytes, validated source maps, imported historical source, runtime observations, and analyst inference must remain distinct authorities.

Evidence and comparison

  • Reuse Evidence v2 identities and artifact graph occurrences rather than creating a separate cache.
  • Anchor every semantic record to the shipped artifact digest and exact location.
  • Make pagination deterministic for large bundles.
  • Compare logical modules and functions without treating missing mappings as equality.
  • Preserve minification, tree-shaking, wrapper, and source-map limitations.
  • Allow large records to become MCP resources through #99.

Discovery and routing

  • Provider capability discovery must state which bundle formats and operations are available.
  • Opening a JavaScript target must not imply native procedure analysis is supported.
  • Tool discovery should expose actionable availability through #101 rather than failing unexpectedly after invocation.
  • Hopper-specific code must not enter the bundle-analysis provider.

Alternatives Considered

  • Artifact inventory only: establishes provenance but cannot recover module or behavioral structure.
  • Treating CodeDB or another source index as the REA provider: useful for readable source, but does not by itself establish shipped-artifact identity, bundle mappings, package provenance, or Evidence v2 authority.
  • Sending JavaScript to Hopper: wrong provider boundary and cannot make truthful JavaScript semantic claims.
  • One bundler-specific parser: too narrow; bundler detection and adapters should sit behind shared provider contracts.

Acceptance Criteria

  • A provider-neutral bundle-analysis contract exists independently of any specific parser or bundler.
  • REA detects supported JavaScript/package bundle families and reports confidence and limitations.
  • Representative plain ESM/CommonJS and at least two bundled formats produce deterministic module/chunk inventories.
  • Recovered modules, functions, and graph edges cite shipped-artifact digests and exact locations.
  • Source maps are integrity-checked before contributing mapped names or source locations.
  • Application-owned, dependency, generated, and vendored classifications remain evidence-backed or explicitly inferred.
  • Dynamic imports, split chunks, and unresolved loader behavior remain distinguishable from absent edges.
  • Electron main, renderer, preload, IPC, native addon, and WebAssembly boundaries are represented when observed.
  • Bundle comparison never reports unchanged when either side lacks required semantic coverage.
  • Results preserve Evidence v2 authority, confidence, provider, limitations, and residual unknowns.
  • CLI and MCP expose equivalent analysis and typed failures.
  • Capability discovery distinguishes artifact inventory, bundle semantic analysis, and native procedure analysis.
  • Parsing, traversal, decompression, source-map, module, graph, output-byte, and time limits are enforced.
  • Tests cover minification, malformed bundles, forged source maps, path traversal, oversized inputs, split chunks, duplicated packages, unsupported wrappers, cancellation, and deterministic pagination.
  • Packaged-artifact tests analyze real generated bundles rather than only hand-authored fixtures.

Non-goals

  • Claiming recovered source is original source.
  • Executing arbitrary bundle code during static analysis.
  • Replacing controlled runtime capture for dynamic behavior.
  • Making every bundler heuristic part of the domain model.
  • Treating source-map presence as proof that it matches shipped bytes.
  • Folding native binary decompilation into the JavaScript provider.

Relationships

  • #42 tracks the broader managed-runtime, bytecode, and package-provider family.
  • #101 governs capability-aware discovery and unavailable-operation explanations.
  • #99 can expose large bundle records as addressable MCP resources.
  • #35 and the reference-source work govern historical-source provenance and mapping.
  • #98 should supply shared progress and cancellation for large bundle analysis.

This should become a focused child of #42 if GitHub issue hierarchy is enabled.

Root capability expansion: source-semantic JavaScript provider

A real-world bundled CLI investigation demonstrates the complete missing surface. REA accepted and hashed a shipped JavaScript artifact, but native providers correctly rejected semantic operations. The agent then had no REA-native route for definition/reference navigation, internal function ownership, minified state-machine recovery, or source-bound comparison.

This issue must deliver a coherent JavaScript semantic provider, not only bundle identification or text search.

Required semantic model

  • Parse JavaScript into an AST without executing it.
  • Preserve exact artifact byte offsets and generated line/column spans.
  • Recover chunks, wrappers, logical modules, functions, closures, classes, properties, constants, and package identities where supportable.
  • Model ESM, CommonJS, bundler registries, re-exports, dynamic imports, require indirection, split chunks, and unresolved loader edges.
  • Build bounded definition, reference, caller, callee, string-owner, constant-owner, property-read/write, protocol-consumer, and state-transition relationships.
  • Distinguish syntax, derived structural edges, source-map claims, runtime observations, and analyst hypotheses.
  • Preserve minifier-generated names as artifact-local identities without claiming they are original.
  • Represent parse holes, computed properties, eval, opaque wrappers, and unsupported syntax as scoped unknowns.

Agent-facing operations

Provide provider-neutral operations for bundle overview, module/function inventory, one-function inspection, literal/property/protocol queries, definition/references/callers/callees, state reads/writes, cross-version comparison, source-map mapping, and bridge tracing into Electron IPC, native addons, child processes, WebAssembly, HTTP/WebSocket, filesystem, and environment boundaries.

Source maps, scale, and evidence

  • Verify maps against exact shipped bytes before granting mapped authority.
  • Preserve generated and original coordinates together.
  • Treat sourcesContent, historical source, and inferred mapping as different authorities.
  • Cache by artifact digest, provider/parser version, analysis profile, and schema.
  • Bound AST nodes, source bytes, modules, functions, edges, query work, output, time, and memory.
  • Propagate cancellation/progress and expose large indexes as MCP resources.
  • Never report unchanged/removed when semantic coverage is incomplete.

Root completion gate

An agent must be able to open a real minified bundle, navigate from a literal to its owning function, inspect callers/callees and state effects, compare it with another version, and receive evidence-linked unknowns for unsupported edges. Tests must use real generated single-file and split-chunk bundles, duplicated packages, ASAR main/preload/renderer graphs, malformed partial parses, dynamic ambiguity, stale maps, native/Wasm bridges, and cross-version minifier renaming.

Originally created by @morluto on GitHub (Jul 13, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/117 ## Problem Statement REA can classify, open, hash, and inventory JavaScript targets, source maps, archives, and Electron application bundles. It can also import JavaScript and TypeScript as historical reference source. It cannot yet recover semantic structure from a shipped bundle. For a published client distributed as one minified or bundled JavaScript artifact, agents cannot use REA to answer: - which logical modules and package versions are present; - which code is application-owned, generated, vendored, or runtime scaffolding; - how imports, exports, dynamic loads, and cross-chunk references connect; - which functions or behaviors changed between releases; - whether a source map matches the shipped bytes and what authority it provides; - where JavaScript crosses into Electron, Node.js native addons, WebAssembly, or other embedded runtimes. Native Hopper procedure tools correctly do not claim support for JavaScript. Today agents must combine REA artifact inventory with external source indexing and runtime tests. The missing capability is semantic bundle analysis with REA evidence and comparison contracts. This is a focused implementation issue under #42, not a replacement for the broader managed-runtime and package-provider roadmap. ## Proposed Solution Add a provider-neutral bundle-analysis capability family backed initially by a JavaScript/package provider. Keep parser, bundler, and runtime-specific code outside the domain and application layers. ### Initial targets - plain JavaScript, ESM, and CommonJS; - Webpack, Rollup, esbuild, Parcel, Browserify, and similar bundles; - split chunks and lazy-loaded assets; - npm package trees and lockfile-backed distributions; - Electron ASAR applications and preload/renderer/main-process bundles; - Node.js snapshots or bytecode when a provider can make truthful claims; - embedded WebAssembly and native addon boundaries. Unsupported or ambiguous formats must remain explicit unknowns. ### Capability model Candidate provider operations: - `identify_bundle` - `inventory_modules` - `inspect_bundle_function` - `resolve_bundle_graph` - `map_source_artifacts` - `compare_bundles` - `trace_runtime_bridge` Public tool names and grouping may differ after contract review. CLI and MCP must expose equivalent behavior. ### Required results Bundle analysis should produce deterministic, bounded records for: - artifact digest and exact byte ranges; - detected bundler/runtime and confidence; - logical module, chunk, and package identities; - imports, exports, re-exports, dynamic imports, and loader edges; - recovered function identities with byte/line locations; - generated, vendored, dependency, and application-owned classifications; - package and lockfile provenance where observed; - source-map identity, validation status, and mapping authority; - JavaScript-to-native, JavaScript-to-WebAssembly, Electron IPC, and preload boundaries; - limitations, residual unknowns, and parser/provider versions. Derived names or reconstructed source must be labeled as inference. Original shipped bytes, validated source maps, imported historical source, runtime observations, and analyst inference must remain distinct authorities. ### Evidence and comparison - Reuse Evidence v2 identities and artifact graph occurrences rather than creating a separate cache. - Anchor every semantic record to the shipped artifact digest and exact location. - Make pagination deterministic for large bundles. - Compare logical modules and functions without treating missing mappings as equality. - Preserve minification, tree-shaking, wrapper, and source-map limitations. - Allow large records to become MCP resources through #99. ### Discovery and routing - Provider capability discovery must state which bundle formats and operations are available. - Opening a JavaScript target must not imply native procedure analysis is supported. - Tool discovery should expose actionable availability through #101 rather than failing unexpectedly after invocation. - Hopper-specific code must not enter the bundle-analysis provider. ## Alternatives Considered - **Artifact inventory only:** establishes provenance but cannot recover module or behavioral structure. - **Treating CodeDB or another source index as the REA provider:** useful for readable source, but does not by itself establish shipped-artifact identity, bundle mappings, package provenance, or Evidence v2 authority. - **Sending JavaScript to Hopper:** wrong provider boundary and cannot make truthful JavaScript semantic claims. - **One bundler-specific parser:** too narrow; bundler detection and adapters should sit behind shared provider contracts. ## Acceptance Criteria - [ ] A provider-neutral bundle-analysis contract exists independently of any specific parser or bundler. - [ ] REA detects supported JavaScript/package bundle families and reports confidence and limitations. - [ ] Representative plain ESM/CommonJS and at least two bundled formats produce deterministic module/chunk inventories. - [ ] Recovered modules, functions, and graph edges cite shipped-artifact digests and exact locations. - [ ] Source maps are integrity-checked before contributing mapped names or source locations. - [ ] Application-owned, dependency, generated, and vendored classifications remain evidence-backed or explicitly inferred. - [ ] Dynamic imports, split chunks, and unresolved loader behavior remain distinguishable from absent edges. - [ ] Electron main, renderer, preload, IPC, native addon, and WebAssembly boundaries are represented when observed. - [ ] Bundle comparison never reports unchanged when either side lacks required semantic coverage. - [ ] Results preserve Evidence v2 authority, confidence, provider, limitations, and residual unknowns. - [ ] CLI and MCP expose equivalent analysis and typed failures. - [ ] Capability discovery distinguishes artifact inventory, bundle semantic analysis, and native procedure analysis. - [ ] Parsing, traversal, decompression, source-map, module, graph, output-byte, and time limits are enforced. - [ ] Tests cover minification, malformed bundles, forged source maps, path traversal, oversized inputs, split chunks, duplicated packages, unsupported wrappers, cancellation, and deterministic pagination. - [ ] Packaged-artifact tests analyze real generated bundles rather than only hand-authored fixtures. ## Non-goals - Claiming recovered source is original source. - Executing arbitrary bundle code during static analysis. - Replacing controlled runtime capture for dynamic behavior. - Making every bundler heuristic part of the domain model. - Treating source-map presence as proof that it matches shipped bytes. - Folding native binary decompilation into the JavaScript provider. ## Relationships - #42 tracks the broader managed-runtime, bytecode, and package-provider family. - #101 governs capability-aware discovery and unavailable-operation explanations. - #99 can expose large bundle records as addressable MCP resources. - #35 and the reference-source work govern historical-source provenance and mapping. - #98 should supply shared progress and cancellation for large bundle analysis. This should become a focused child of #42 if GitHub issue hierarchy is enabled. ## Root capability expansion: source-semantic JavaScript provider A real-world bundled CLI investigation demonstrates the complete missing surface. REA accepted and hashed a shipped JavaScript artifact, but native providers correctly rejected semantic operations. The agent then had no REA-native route for definition/reference navigation, internal function ownership, minified state-machine recovery, or source-bound comparison. This issue must deliver a coherent JavaScript semantic provider, not only bundle identification or text search. ### Required semantic model - Parse JavaScript into an AST without executing it. - Preserve exact artifact byte offsets and generated line/column spans. - Recover chunks, wrappers, logical modules, functions, closures, classes, properties, constants, and package identities where supportable. - Model ESM, CommonJS, bundler registries, re-exports, dynamic imports, require indirection, split chunks, and unresolved loader edges. - Build bounded definition, reference, caller, callee, string-owner, constant-owner, property-read/write, protocol-consumer, and state-transition relationships. - Distinguish syntax, derived structural edges, source-map claims, runtime observations, and analyst hypotheses. - Preserve minifier-generated names as artifact-local identities without claiming they are original. - Represent parse holes, computed properties, eval, opaque wrappers, and unsupported syntax as scoped unknowns. ### Agent-facing operations Provide provider-neutral operations for bundle overview, module/function inventory, one-function inspection, literal/property/protocol queries, definition/references/callers/callees, state reads/writes, cross-version comparison, source-map mapping, and bridge tracing into Electron IPC, native addons, child processes, WebAssembly, HTTP/WebSocket, filesystem, and environment boundaries. ### Source maps, scale, and evidence - Verify maps against exact shipped bytes before granting mapped authority. - Preserve generated and original coordinates together. - Treat sourcesContent, historical source, and inferred mapping as different authorities. - Cache by artifact digest, provider/parser version, analysis profile, and schema. - Bound AST nodes, source bytes, modules, functions, edges, query work, output, time, and memory. - Propagate cancellation/progress and expose large indexes as MCP resources. - Never report unchanged/removed when semantic coverage is incomplete. ### Root completion gate An agent must be able to open a real minified bundle, navigate from a literal to its owning function, inspect callers/callees and state effects, compare it with another version, and receive evidence-linked unknowns for unsupported edges. Tests must use real generated single-file and split-chunk bundles, duplicated packages, ASAR main/preload/renderer graphs, malformed partial parses, dynamic ambiguity, stale maps, native/Wasm bridges, and cross-version minifier renaming.
bsakaguchi 2026-10-15 18:20:50 +00:00
bsakaguchi commented 2026-10-15 18:20:52 +00:00
Author
Owner
Copy link

@morluto commented on GitHub (Jul 20, 2026):

Closing as completed. REA now recovers semantic structure from shipped JavaScript and packaged application bundles without executing them:

  • analyze_javascript_application returns a deterministic JavaScript Application Graph with module/chunk/package identities, import/export/require edges, call relationships, native/Electron/IPC/WebAssembly/managed boundaries, source-map authority, and bounded residual unknowns.
  • trace_application_feature supports literal/property/protocol queries through the graph with direction/depth limits.
  • compare_application_versions and reconcile_javascript_runtime provide cross-version comparison and runtime correlation.
  • The static-analysis pipeline (src/domain/javascriptStaticAnalysis*.ts, src/domain/javascriptSemanticProjection.ts) parses bounded ASTs, resolves bindings, collects callables and module links, detects vendors/bundler registrations, and enforces node/edge/time limits.
  • Tests cover ESM/CommonJS, Webpack/Rspack/Parcel/esbuild/Rollup/Browserify-style bundles, ASAR, Electron main/preload/renderer, native-addon handoffs, minification, malformed sources, source-map handling, and deterministic pagination.

If a dedicated per-function dossier tool is still needed, that can be opened as a focused follow-up.

<!-- gh-comment-id:5023313222 --> @morluto commented on GitHub (Jul 20, 2026): Closing as completed. REA now recovers semantic structure from shipped JavaScript and packaged application bundles without executing them: - `analyze_javascript_application` returns a deterministic JavaScript Application Graph with module/chunk/package identities, import/export/require edges, call relationships, native/Electron/IPC/WebAssembly/managed boundaries, source-map authority, and bounded residual unknowns. - `trace_application_feature` supports literal/property/protocol queries through the graph with direction/depth limits. - `compare_application_versions` and `reconcile_javascript_runtime` provide cross-version comparison and runtime correlation. - The static-analysis pipeline (`src/domain/javascriptStaticAnalysis*.ts`, `src/domain/javascriptSemanticProjection.ts`) parses bounded ASTs, resolves bindings, collects callables and module links, detects vendors/bundler registrations, and enforces node/edge/time limits. - Tests cover ESM/CommonJS, Webpack/Rspack/Parcel/esbuild/Rollup/Browserify-style bundles, ASAR, Electron main/preload/renderer, native-addon handoffs, minification, malformed sources, source-map handling, and deterministic pagination. If a dedicated per-function dossier tool is still needed, that can be opened as a focused follow-up.
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#74
No description provided.