[PR #2471] [MERGED] fix(process): resolve POSIX backslash basenames through PATH #5254

New issue

Closed

opened 2026-10-31 01:05:11 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:05:11 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2471
Author: @rudycelekli
Created: 10/13/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @morluto

Base: main ← Head: fix/posix-backslash-executable

📝 Commits (2)

aa5d3e3 fix(process): resolve POSIX backslash basenames through PATH
9a641ab fix(process): reconcile POSIX executable lookup with main

📊 Changes

3 files changed (+55 additions, -2 deletions)

View changed files

📝 src/process/capture/ProcessScenarioRuntimeValidation.test.ts (+22 -0)
📝 src/process/capture/ProcessScenarioRuntimeValidation.ts (+4 -2)
📝 tests/boundary/process/processCaptureNormalization.test.ts (+29 -0)

📄 Description

A POSIX executable basename may contain a literal backslash. REA currently treats it as a directory separator and skips the caller-selected PATH, returning invalid input even when that executable exists. Classify backslash as a separator only on hosts where it is one; preserve explicit slash paths and the selected executable spelling.

Validation: a real filesystem resolver test and native process-capture regression fail on the original implementation. The fix passes the resolver suite and five native PTY cases (two Linux-only cases skipped), including successful invocation and verified owned-process cleanup. npm run check passes with Node 24.18.0/npm 11.16.0; independent automated review passed on aa5d3e3f1.

AI assistance: OpenAI Codex authored and reviewed the analysis, implementation, regressions and description. No human review is claimed.

_{🔄 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/2471 **Author:** [@rudycelekli](https://github.com/rudycelekli) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/posix-backslash-executable` --- ### 📝 Commits (2) - [`aa5d3e3`](https://github.com/morluto/rea/commit/aa5d3e3f1e6d9095dedf9b9e2510bd0aa1cc6e00) fix(process): resolve POSIX backslash basenames through PATH - [`9a641ab`](https://github.com/morluto/rea/commit/9a641ab2a8e349622475709ebefb756220be87dc) fix(process): reconcile POSIX executable lookup with main ### 📊 Changes **3 files changed** (+55 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `src/process/capture/ProcessScenarioRuntimeValidation.test.ts` (+22 -0) 📝 `src/process/capture/ProcessScenarioRuntimeValidation.ts` (+4 -2) 📝 `tests/boundary/process/processCaptureNormalization.test.ts` (+29 -0) </details> ### 📄 Description A POSIX executable basename may contain a literal backslash. REA currently treats it as a directory separator and skips the caller-selected PATH, returning invalid input even when that executable exists. Classify backslash as a separator only on hosts where it is one; preserve explicit slash paths and the selected executable spelling. Validation: a real filesystem resolver test and native process-capture regression fail on the original implementation. The fix passes the resolver suite and five native PTY cases (two Linux-only cases skipped), including successful invocation and verified owned-process cleanup. `npm run check` passes with Node 24.18.0/npm 11.16.0; independent automated review passed on aa5d3e3f1. AI assistance: OpenAI Codex authored and reviewed the analysis, implementation, regressions and description. No human review is claimed. --- <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:11 +00:00