[PR #5265] [MERGED] fix(cli): reject an empty JavaScript application path #6845

New issue

Closed

opened 2026-11-01 21:43:29 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:43:29 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5265
Author: @vishal-tambi
Created: 10/19/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @morluto

Base: main ← Head: fix/5258-javascript-selected-input-path

---

📝 Commits (1)

• 1804fc8 fix(cli): reject an empty JavaScript application path

📊 Changes

2 files changed (+28 additions, -1 deletions)

View changed files

📝 src/cli/electronCommands.ts (+3 -1)
📝 tests/boundary/javascript/javascriptSelectedPathEvidence.test.ts (+25 -0)

📄 Description

Summary

rea analyze-javascript-application "" analyzes the current working directory and returns successful Evidence. This PR makes it reject the empty path as invalid input instead.

This PR is now narrowed to that one change. The #5258 provenance fix is already on main in c4aaf813e: Evidence input_path, CLI path anchoring on both routes, the shared verifier assertions and the docs. Those parts have been dropped from this branch, and it is rebased onto main at b44cb5bd3.

There's no separate issue for the empty path. It came up in review on this PR, and the maintainer asked to keep it here.

Problem and expected behavior

Since c4aaf813e, the dedicated route passes absoluteCallerPath(args.path) into analysis. absoluteCallerPath("") returns the working directory (/cwd/ on POSIX, cwd on Windows). An empty argument therefore becomes a valid directory before the input schema ever sees it. A script that runs rea analyze-javascript-application "$APP_PATH" with an unset variable analyzes whatever directory it happens to run in.

Expected: an empty path is rejected as invalid_request on input_path. That matches MCP with input_path: "", and it matches this route before the anchoring change. rea analyze "" already rejects it, because its argument is declared .min(1).

Change and scope

• src/cli/electronCommands.ts: an empty path is passed through unchanged; every other path is still anchored with absoluteCallerPath, exactly as on main. The existing input schema then rejects "". absoluteElectronFusePath in the same file handles an empty path the same way.
• I didn't add .min(1) to the CLI argument, because that would change this route's error from the domain invalid_request to the argument parser's VALIDATION_ERROR.
• I didn't change absoluteCallerPath itself, because it is shared by many other callers.

Not included: the wasm, sqlite, signal, rust, go, evm, capture and binary-diagnostics CLI commands also call absoluteCallerPath(args.path) on an argument without .min(1). That predates this PR and isn't changed here.

Scope decision: not applicable. This is an input-validation fix in an existing CLI route.

Contract and boundary impact

• Semantic owner and earliest changed stage: the CLI adapter for analyze-javascript-application, before input validation.
• Contribution scope fit and linked maintainer decision: existing CLI behavior. No decision needed.
• CLI and MCP/tool-catalog contract: analyze-javascript-application "" now exits 1 with invalid_request instead of analyzing the working directory. Non-empty paths, rea analyze and the MCP tool are unchanged. No schema changes.
• Provider, bridge, target-format, or platform compatibility: no change.
• Evidence, artifact, provenance, or reconstruction contract: unchanged for valid input. No Evidence is produced for an empty selection.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): an empty argument no longer selects the working directory as the analysis target.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

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

• Read existing files or captured data.
• Launch or attach to a process.
• Inject instrumentation or run scripts/code.
• Change process memory, registers, files, or configuration.
• Contact network services.
• Recover protected code or work around protections.
• Documentation or usability only; no target interaction.
• Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

• Tests added or updated: one parameterized cliTest appended to tests/boundary/javascript/javascriptSelectedPathEvidence.test.ts. It runs each CLI route with "" from a temp directory that contains a JavaScript file:
  • analyze-javascript-application "": exit 1, invalid_request, with an issue on input_path.
  • analyze "": exit 1, VALIDATION_ERROR. This behavior is unchanged; the case is there so both anchored routes are covered.
• Base reproduction or other evidence:
  • With main's electronCommands.ts (0e62094b6), the dedicated-route case fails: exit code 0 instead of 1. The analyze case and the existing selected-path test pass.
  • An earlier manual run of the same anchoring code returned Evidence whose subject.local_path and parameters.input_path were the working directory.
• User-visible CLI/MCP output (if applicable): with this change, analyze-javascript-application "" --json prints the invalid_request error document with an issue on input_path and exits 1. Output for non-empty paths is unchanged.
• Remaining proof gaps:
  • macOS and Linux were not run.
  • The full CI suite was not run locally.

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

All on Windows 11 with Node 24.18.0 and npm 11.16.0. Unless noted, these ran on main at 0e62094b6 plus this commit.

CI on the previous head (44610ab32) failed two tests in shard 4/5: applicationWorkflowCli and applicationExportShapeMcp, both relative-path Evidence ID parity checks. main's own CI at 0e62094b6 failed the same two tests, and b44cb5bd3 fixes them on main, so I rebased onto it. After the rebase:

• npm run test:focused -- with the seven files listed below plus applicationWorkflowCli and applicationExportShapeMcp: 86 passed, 1 failed, 2 skipped.
  • The failure is applicationExportShapeMcp > "compares exact parser export shapes with inline Evidence".
  • It fails the same way on clean main at b44cb5bd3 on this machine. The checkout is on D: and the temp directory is on C:, so path.relative returns an absolute path. The "relative" selection then equals the absolute one, and the two Evidence IDs match.
  • It is unrelated to this change.
• npm run check:fast: passed, also as the pre-push hook.

Earlier runs, on 0e62094b6:

• npm run test:focused -- tests/boundary/javascript/javascriptSelectedPathEvidence.test.ts, with main's electronCommands.ts swapped in: 1 failed (dedicated route, exit 0) and 2 passed.
• npm run test:focused -- with javascriptSelectedPathEvidence, javascriptAnalysisLimits, javascriptApplicationJsonOutput, electronCli, javascriptApplicationInputSelection, javascriptApplicationCancellation and javascriptClientVerifier: 45 passed, 2 skipped (both platform-guarded).
• npm run test:focused -- with 111 JavaScript, Electron CLI/MCP and Evidence-parsing boundary/acceptance files: 872 passed, 62 failed, 29 skipped.
  • The same 62 tests (61 unique names, in the same 9 files) also fail on clean main at 0e62094b6 on this machine.
  • All 62 are Windows host limits:
    • fixture filenames containing ?, # or a tab;
    • EPERM creating file symlinks without the privilege;
    • "Safe no-follow file opens are unavailable", because a source checkout has no Windows native addon;
    • one spawn ENAMETOOLONG.
  • None of them comes from this change.
• npm run check: exit 0 (typecheck; lint with 0 errors and 1,761 warnings, none in the changed files; oxfmt; knip; metadata; module boundaries; architecture guards).
• npm run docs:check: passed.
• npm run verify:test-discovery: 1,668 test files, each assigned once.
• npm run format:check and git diff --check: passed.
• npm run check:fast: passed as the pre-push hook.

Not run: the native client verifiers (this change doesn't touch them), macOS, Linux and the full CI suite.

Compatibility, safety, and release

• Breaking changes or migration steps: none for valid input. analyze-javascript-application "" now fails instead of analyzing the working directory. A caller that relied on that behavior should pass . explicitly.
• Real Hopper/Ghidra, browser, or OS coverage: no provider is involved. Only Windows was run.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: this stops an empty argument from silently selecting the working directory for analysis.

Author readiness

Human owner: @vishal-tambi

• I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
• I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
• I declare this PR ready for initial maintainer review.

Before merge

• This PR addresses a concrete problem or an agreed enhancement.
• Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
• The PR has one focused outcome and the title follows type(scope): outcome.
• Related issue is linked, or the reason for not linking one is stated above.
• Tests cover changed observable behavior and meaningful failure paths.
• Owning docs, contracts, and generated metadata are updated where needed.
• User-visible CLI/MCP changes include representative output.
• I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

---

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5265 **Author:** [@vishal-tambi](https://github.com/vishal-tambi) **Created:** 10/19/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/5258-javascript-selected-input-path` --- ### 📝 Commits (1) - [`1804fc8`](https://github.com/morluto/rea/commit/1804fc82a44bde716741d1eb0a0505103c2915bb) fix(cli): reject an empty JavaScript application path ### 📊 Changes **2 files changed** (+28 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/cli/electronCommands.ts` (+3 -1) 📝 `tests/boundary/javascript/javascriptSelectedPathEvidence.test.ts` (+25 -0) </details> ### 📄 Description ## Summary `rea analyze-javascript-application ""` analyzes the current working directory and returns successful Evidence. This PR makes it reject the empty path as invalid input instead. This PR is now narrowed to that one change. The #5258 provenance fix is already on `main` in c4aaf813e: Evidence `input_path`, CLI path anchoring on both routes, the shared verifier assertions and the docs. Those parts have been dropped from this branch, and it is rebased onto `main` at b44cb5bd3. There's no separate issue for the empty path. It came up in review on this PR, and the maintainer asked to keep it here. ## Problem and expected behavior Since c4aaf813e, the dedicated route passes `absoluteCallerPath(args.path)` into analysis. `absoluteCallerPath("")` returns the working directory (`/cwd/` on POSIX, `cwd` on Windows). An empty argument therefore becomes a valid directory before the input schema ever sees it. A script that runs `rea analyze-javascript-application "$APP_PATH"` with an unset variable analyzes whatever directory it happens to run in. Expected: an empty path is rejected as `invalid_request` on `input_path`. That matches MCP with `input_path: ""`, and it matches this route before the anchoring change. `rea analyze ""` already rejects it, because its argument is declared `.min(1)`. ## Change and scope - `src/cli/electronCommands.ts`: an empty path is passed through unchanged; every other path is still anchored with `absoluteCallerPath`, exactly as on `main`. The existing input schema then rejects `""`. `absoluteElectronFusePath` in the same file handles an empty path the same way. - I didn't add `.min(1)` to the CLI argument, because that would change this route's error from the domain `invalid_request` to the argument parser's `VALIDATION_ERROR`. - I didn't change `absoluteCallerPath` itself, because it is shared by many other callers. Not included: the wasm, sqlite, signal, rust, go, evm, capture and binary-diagnostics CLI commands also call `absoluteCallerPath(args.path)` on an argument without `.min(1)`. That predates this PR and isn't changed here. Scope decision: not applicable. This is an input-validation fix in an existing CLI route. ## Contract and boundary impact - Semantic owner and earliest changed stage: the CLI adapter for `analyze-javascript-application`, before input validation. - Contribution scope fit and linked maintainer decision: existing CLI behavior. No decision needed. - CLI and MCP/tool-catalog contract: `analyze-javascript-application ""` now exits 1 with `invalid_request` instead of analyzing the working directory. Non-empty paths, `rea analyze` and the MCP tool are unchanged. No schema changes. - Provider, bridge, target-format, or platform compatibility: no change. - Evidence, artifact, provenance, or reconstruction contract: unchanged for valid input. No Evidence is produced for an empty selection. - Target selection, authority, upstream behavior, and cleanup details (if applicable): an empty argument no longer selects the working directory as the analysis target. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [x] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. - [x] Contact network services. - [x] Recover protected code or work around protections. - [x] Documentation or usability only; no target interaction. - [x] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: one parameterized `cliTest` appended to `tests/boundary/javascript/javascriptSelectedPathEvidence.test.ts`. It runs each CLI route with `""` from a temp directory that contains a JavaScript file: - `analyze-javascript-application ""`: exit 1, `invalid_request`, with an issue on `input_path`. - `analyze ""`: exit 1, `VALIDATION_ERROR`. This behavior is unchanged; the case is there so both anchored routes are covered. - Base reproduction or other evidence: - With `main`'s `electronCommands.ts` (0e62094b6), the dedicated-route case fails: exit code 0 instead of 1. The `analyze` case and the existing selected-path test pass. - An earlier manual run of the same anchoring code returned Evidence whose `subject.local_path` and `parameters.input_path` were the working directory. - User-visible CLI/MCP output (if applicable): with this change, `analyze-javascript-application "" --json` prints the `invalid_request` error document with an issue on `input_path` and exits 1. Output for non-empty paths is unchanged. - Remaining proof gaps: - macOS and Linux were not run. - The full CI suite was not run locally. 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 All on Windows 11 with Node 24.18.0 and npm 11.16.0. Unless noted, these ran on `main` at 0e62094b6 plus this commit. CI on the previous head (44610ab32) failed two tests in shard 4/5: `applicationWorkflowCli` and `applicationExportShapeMcp`, both relative-path Evidence ID parity checks. `main`'s own CI at 0e62094b6 failed the same two tests, and b44cb5bd3 fixes them on `main`, so I rebased onto it. After the rebase: - `npm run test:focused --` with the seven files listed below plus `applicationWorkflowCli` and `applicationExportShapeMcp`: 86 passed, 1 failed, 2 skipped. - The failure is `applicationExportShapeMcp` > "compares exact parser export shapes with inline Evidence". - It fails the same way on clean `main` at b44cb5bd3 on this machine. The checkout is on `D:` and the temp directory is on `C:`, so `path.relative` returns an absolute path. The "relative" selection then equals the absolute one, and the two Evidence IDs match. - It is unrelated to this change. - `npm run check:fast`: passed, also as the pre-push hook. Earlier runs, on 0e62094b6: - `npm run test:focused -- tests/boundary/javascript/javascriptSelectedPathEvidence.test.ts`, with `main`'s `electronCommands.ts` swapped in: 1 failed (dedicated route, exit 0) and 2 passed. - `npm run test:focused --` with `javascriptSelectedPathEvidence`, `javascriptAnalysisLimits`, `javascriptApplicationJsonOutput`, `electronCli`, `javascriptApplicationInputSelection`, `javascriptApplicationCancellation` and `javascriptClientVerifier`: 45 passed, 2 skipped (both platform-guarded). - `npm run test:focused --` with 111 JavaScript, Electron CLI/MCP and Evidence-parsing boundary/acceptance files: 872 passed, 62 failed, 29 skipped. - The same 62 tests (61 unique names, in the same 9 files) also fail on clean `main` at 0e62094b6 on this machine. - All 62 are Windows host limits: - fixture filenames containing `?`, `#` or a tab; - `EPERM` creating file symlinks without the privilege; - "Safe no-follow file opens are unavailable", because a source checkout has no Windows native addon; - one `spawn ENAMETOOLONG`. - None of them comes from this change. - `npm run check`: exit 0 (typecheck; lint with 0 errors and 1,761 warnings, none in the changed files; oxfmt; knip; metadata; module boundaries; architecture guards). - `npm run docs:check`: passed. - `npm run verify:test-discovery`: 1,668 test files, each assigned once. - `npm run format:check` and `git diff --check`: passed. - `npm run check:fast`: passed as the pre-push hook. Not run: the native client verifiers (this change doesn't touch them), macOS, Linux and the full CI suite. ## Compatibility, safety, and release - Breaking changes or migration steps: none for valid input. `analyze-javascript-application ""` now fails instead of analyzing the working directory. A caller that relied on that behavior should pass `.` explicitly. - Real Hopper/Ghidra, browser, or OS coverage: no provider is involved. Only Windows was run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: this stops an empty argument from silently selecting the working directory for analysis. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @vishal-tambi - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] 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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-11-01 21:43:29 +00:00

• closed this issue
• added the
  pull-request
  label

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

codex/procedure-reference-stacked

release-please--branches--main--components--rea-agents

release-please--branches--main--components--rea-agents--release-notes

codex/kuna-independent-retry

codex/byte-search-overlay-coverage

codex/open-failure-target-receipt

codex/kuna-xref-evidence

codex/ghidra-ambiguous-procedure-recovery

codex/function-source-bundle

codex/trace-function-integration-prototype

codex/snapshot-source-closure

codex/recorded-evidence-array-pages

codex/evidence-recovery-redesign

codex/trace-feature-address-scope

codex/call-discovery-scope

codex/ghidra-literal-candidate-evidence

codex/decompile-directory-independent-retry

codex/retry-provenance-base

codex/value-flow-capability-experiment

codex/ghidra-containing-instruction

cursor/readme-discord-button-ef9f

dependabot/github_actions/actions/setup-node-7.1.0

dependabot/github_actions/actions/upload-artifact-7.0.2

dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df

codex/kuna-1989

fix/8559-native-ui-fixture-ownership

fix/8555-go-verifier-mcp-ownership

codex/provider-capability-recovery

fix/8642-rizin-target-stdin

codex/ghidra-memory-effect-scope

codex/ghidra-annotation-entry-selector

codex/ghidra-readonly-recovery

codex/ghidra-regex-verifier-recovery

codex/evidence-discovery-view-guidance

fix/8545-bulk-append-overflow

fix/8428-navigation-refusal-alternatives

codex/address-context-recovery

codex/matching-member-limitations

codex/unknown-scope-contract

codex/evidence-view-guidance

feat/8373-native-trace-views

codex/ghidra-snapshot-verifier-binding

codex/elf-export-visibility

codex/evidence-view-recovery

codex/native-reference-cli-help

codex/provider-candidate-observation-scope

codex/kuna-session-verification

codex/ghidra-switch-lifetime-guidance

codex/pseudocode-paging-discovery

codex/clarify-evidence-view-support

codex/kuna-xrefs-selector-recovery

codex/context-capacity-recovery

codex/evidence-closure-large-links

codex/same-function-evidence-identity

codex/ghidra-verifier-inspected-jdk

codex/audit-guided-workflows

codex/crash-prompt-retained-dossiers

codex/analysis-view-error-recovery

codex/kuna-verifier-target-selection

codex/ghidra-selected-project-call-coverage

codex/docs-native-analysis-scope

codex/ghidra-java-socket-boundary

codex/ghidra-retained-snapshot-verifier

codex/ghidra-search-inventory-facts

fix/8284-zero-argument-parameter-bindings

fix/8198-ui-action-handler-offset

fix/8257-elf-entry-label-identity

fix/8304-deferred-output-schema-projection

fix/8277-call-path-computed-target-uncertainty

fix/pr-8089-conflicts

fix/ci-static-duplicate-export

dependabot/npm_and_yarn/lint-staged-17.6.0

dependabot/github_actions/actions/download-artifact-8.0.2

dependabot/npm_and_yarn/write-file-atomic-8.0.0

dependabot/npm_and_yarn/canonicalize-5.1.0

dependabot/github_actions/actions/cache/restore-6.1.0

dependabot/npm_and_yarn/toon-format/toon-4.4.0

dependabot/github_actions/actions/deploy-pages-5.0.1

codex/review-fixes-pr-2403

codex/review-fixes-pr-2400

codex/process-terminal-width

codex/test-brittleness-cleanup

verify/7167-browser-connect-macos

fix/7167-browser-connect

feat/native-matching-allowance-setting

feat/browser-scenario-dry-run

test/managed-caller-parameters-20261024

codex/parser-fortythird-boundaries

fix/6926-pinvoke-platform-decorations-20261023

fix/6889-har-body-encoding-20261023

fix/6888-sqlite-schema-budget-20261023

fix/dependency-security-gates-6708

cursor/evidence-overwrite-rebase-b4ac

feat/4057-verify-native-exports

fix/windows-acl-observer-overhead-20261022

cursor/erlang-beam-restack-4476

cursor/pe-certificate-review-bf32

fix/6116-javascript-application-fs-errors

fix/6061-unmapped-runtime-script-unknown

feat/browser-scenario-summary

fix/pe-certificates

codex/verify-3407

cursor/rebase-5699

cursor/rebase-5352

cursor/rebase-5600

cursor/fix-cli-schema-omission-10a8

codex/audit-hopper-shutdown-reasons-20261021

fix/demangle-swift-omitted-record

fix/nib-boolean-value-types

cursor/cancellation-partial-observation-a5ac

fix/ib-object-limit-reasons

fix/electron-fuse-limit-advice

fix/kuna-doctor-dangling-cache

fix/fixed-budget-refusal-advice

fix/js-ipc-listener-dedup

fix/js-return-member-provenance

fix/dmg-integrity-retry-advice

fix/ida-doctor-readiness

fix/kuna-version-probe-output-drain

fix/legacy-swift-runtime-name-matching

fix/dylib-lazy-load-commands

fix/browser-scenario-startup-cancel

fix/swift-nested-punycode-classification

fix/compare-unselected-scopes

fix/objc-method-budget-coverage

fix/dmg-mounted-root-observations

audit/ci-tests-20261019-round2

release/6.7.0

fix/wabt-cleanup-retry-resolution

fix/electron-fuse-elf-pe-architecture

fix/native-plist-descriptor-ownership

fix/kuna-caller-cleanup-ownership

experiment/atomic-codemode-20261016

review/first-contributor-3776

fix/call-resolution-full-read-cycles

fix/member-mutation-selection-repeat

experiment/atomic-re-tools-20261015

perf/member-mutation-lazy-origins

perf/static-network-mutation-index

fix/hopper-startup-lifecycle

audit/3050-windows-proof-20261015

feat/windows-window-capture-2183

audit/3049-windows-proof-20261015

audit/3735-macos-fixtures-20261015

fix/batch-decompile-null-pseudocode

fix/kuna-inventory-honors-jobs

experiment/browser-codemode-tool-design-20261015

fix/hopper-clean-runtime-argv

codex/review-2049-27f1b367

review-fixes/pr-2787-routing

fix/3360-scoped-this-emitters

fix/3367-replaced-global-effects

fix/3838-compact-any-value-items

test/hopper-download-probe-20261015

codex/windows-runtime-creation-red-green-20261015

codex/windows-readonly-root-red-green-20261015

codex/windows-root-share-red-green-20261015

codex/exp-1685-win-mcp-startup

codex/bug-sweep-20261015

investigate/2190-windows-package-phases

investigate/3543-macos-cli-deadline

perf/3281-reverse-tools-feedback-quality

fix/3406-hopper-doctor-fixture

fix/3341-wrapper-require-test-context

fix/3301-owned-uninstall-fixtures

fix/3164-compiler-input-ownership

fix/pcap-cleanup-stdout-newline-20261014

perf/interface-builder-summary

codex/review-fixes-pr-1977

fix/ghidra-effective-jvm-platform

fix/docs-turkish-rust-link-20261013

fix/main-maintenance-ci-20261010

fix/recover-binary-session-process-effects

codex/review-fixes-pr-2457

codex/ci-required-cancellation-gate

fix/main-format-baseline-20261013

fix/setup-preserve-entry-fields

cursor/restore-main-checks-1ffc

fix/ghidra-bridge-hashmap-import

codex/shared-ci-jadx-json-default-20261013

codex/shared-ci-ghidra-test-groups-20261013

codex/shared-ci-java-fixture-format-20261013

codex/fix-intrinsic-invocation-boundaries

test/release-preflight-reusable-jobs

test/js-parameter-provenance-expectation

fix/linux-hopper-verification-current

test/2419-ghidra-elf-probe-size

followup/pr-1544-native-ida

codex/fold-pr-2230-contribution

docs/readme-responsible-use

fix/issue-2064

fix/issue-2050

fix/issue-2053

fix/issue-1968

fix/issue-1945

experiment/codemode-bridge-20261011

fix/tool-effects-negative-wording-1904-20261012

fix/1842-electron-interop-provenance

feat/recover-javascript-multi-input

refactor/website-i18n-prep

fix/nativeaot-pe-virtual-extent

fix/browser-verifier-ci-hang

fix/pe-resources-input-selection

docs/beginner-friendly-guides

docs/beginner-setup-guide

fix/javascript-analysis-worker-1563

fix/1649-ghidra-duplicate-names

fix/javascript-export-keys-integration-1369

test/maintenance-boundary-contracts-20261011

review/javascript-export-keys-1369

review/process-live-progress-1483

test/javascript-1495-growth-ratio

fix/ci-escape-timing

docs/normalized-terminal-geometry-1450

release/6.3.0

archive/release-6.3.0-pr1381

release/6.2.0

fix/electron-preload-dynamic-override

fix/javascript-self-referential-bundler-edges

release/6.1.0

cursor/grok-client-cherry-pick-0b56

feat/signature-posture

feat/dyld-shared-cache

feat/artifact-integrity-policy

feat/pkg-inventory

release/6.0.0

chore/sync-release-5.0.0

release/5.0.0

cursor/cloud-agent-node-787e

fix/javascript-xhr-open-endpoints

review/pr-711-realpath-fallback-wording

cleanup/replay-confinement

codex/test-suite-performance

codex/issue-foundations

codex/address-open-issues-2026-07-20

agent/javascript-vite-rollup-esbuild-adapters

agent/process-cleanup

agent/triage-integration

agent/unknown-commands-registry

feat/mcp-identity-metadata

morlvps/issue_cleanup

codex/installer-redesign

morl/roadmap-investigation-core

morl/roadmap-investigation-docs

release-please--branches--main--components--rea

rea-agents-6.8.0

rea-agents-6.7.0

rea-agents-6.6.0

experiment/atomic-codemode-wait-runtime-20261016

rea-agents-6.5.0

rea-agents-6.4.0

rea-agents-6.3.0

rea-agents-6.2.0

rea-agents-6.1.0

rea-agents-6.0.0

rea-agents-5.0.0

rea-agents-4.1.0

rea-agents-4.0.1

rea-agents-4.0.0

rea-agents-3.2.1

rea-agents-3.2.0

rea-agents-3.1.0

rea-agents-3.0.0

rea-agents-2.7.0

rea-agents-2.6.0

rea-agents-2.5.1

rea-agents-2.5.0

rea-agents-2.4.0

rea-agents-2.3.0

rea-agents-2.2.0

rea-agents-2.1.0

rea-agents-2.0.0

rea-agents-1.7.0

rea-agents-1.6.0

rea-agents-1.5.0

rea-agents-1.4.0

rea-agents-1.3.0

rea-agents-1.2.0

rea-agents-1.1.0

rea-agents-1.0.0

rea-agents-0.5.0

rea-agents-0.4.0

rea-agents-0.3.0

rea-0.2.1

rea-0.2.0

Labels

Clear labels   

area: bridge

  

area: bridge

  

area: build

  

area: build

  

area: build

  

area: cli

  

area: domain

  

area: evidence

  

area: mcp

  

area: native

  

area: providers

  

area: runtime

  

area: server

  

area: setup

  

area: tests

  

bug

  

design

  

documentation

  

enhancement

  

enhancement

  

enhancement

  

experiment

  

help wanted

  

i18n

  

invalid

  

P0: critical

  

P1: high

  

P2: medium

  

P2: medium

  

P2: medium

  

P3: low

  

performance

  

provider-request

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

roadmap

  

triage

No labels

area: bridge

area: bridge

area: build

area: build

area: build

area: cli

area: domain

area: evidence

area: mcp

area: native

area: providers

area: runtime

area: server

area: setup

area: tests

bug

design

documentation

enhancement

enhancement

enhancement

experiment

help wanted

i18n

invalid

P0: critical

P1: high

P2: medium

P2: medium

P2: medium

P3: low

performance

provider-request

pull-request

question

roadmap

triage

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#6845

No description provided.