Use Effect child process for editor launches

[cursor]

What Changed

• Switched editor launch spawning in apps/server/src/open.ts from node:child_process callbacks to Effect's ChildProcessSpawner service.
• Reworked editor target parsing and command resolution helpers to return Option instead of nullable values where applicable.
• Updated open.test.ts to verify launches through a Layer.mock child-process spawner instead of running a real process.

Why

This keeps the open/editor launch path closer to idiomatic Effect: process spawning now flows through Effect dependency injection and tests can mock just the child-process layer while preserving the rest of the runtime behavior.

UI Changes

Not applicable.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

  

Note

Replace open npm package with Effect child process spawning for editor and browser launches

• Removes the open package dependency and replaces it with direct ChildProcessSpawner calls in open.ts, giving the server full control over process lifecycle.
• Adds resolveBrowserLaunch to select the correct URL-open command per platform: open on macOS, PowerShell with -EncodedCommand on Windows, Windows PowerShell via WSL when not in SSH/container, and xdg-open on other Linux.
• Adds launchAndUnref as a shared internal effect that spawns a detached child process, unrefs it, and maps failures to OpenError.
• launchDetached (used for editor launches) now quotes args on Windows and sets detached: true with ignored stdio.
• Behavioral Change: browser and editor processes are now spawned with explicit stdio: ignore and detached: true semantics instead of relying on the open package defaults.

Changes since #2659 opened

• Set detached option to true for Windows browser process launches [78a2cec]
• Renamed contract types and error classes from OpenInEditorInput to LaunchEditorInput and OpenError to ExternalLauncherError in the @t3tools/contracts package, updating the WsShellOpenInEditorRpc RPC definition to use the new payload and error schemas [e6d0166]
• Renamed the service module from Open to ExternalLauncher, including the service tag identifier, interface (OpenShape to ExternalLauncherShape), and layer export (OpenLive to ExternalLauncherLive), with method renames from openBrowser to launchBrowser and openInEditor to launchEditor [e6d0166]
• Renamed the launchDetached function to launchEditorProcess within the external launcher module, updating the Effect.fn label and error mapping while preserving the command availability check, spawn options, and win32 quoting behavior [e6d0166]
• Updated all consumer code across server modules to use ExternalLauncher service, ExternalLauncherShape interface, ExternalLauncherError error class, and launchEditor/launchBrowser method names instead of their previous Open-prefixed counterparts [e6d0166]
• Refactored ExternalLauncher module to use namespace export pattern [9e37f0d]
• Updated all import statements and service access patterns for ExternalLauncher across consuming modules [9e37f0d]

^{Macroscope summarized c0bf391.}

---

Note

Medium Risk
Changes cross-platform process spawning for browser/editor launch and updates the RPC/contracts surface, which could affect startup behavior and client integrations if command resolution or platform detection regresses.

Overview
Replaces the Open module with a new ExternalLauncher service (apps/server/src/process/externalLauncher.ts) that launches browsers and editors via Effect’s ChildProcessSpawner (detached + ignored stdio), and wires it through runtime layers, startup browser auto-open, and the shell.openInEditor websocket RPC.

Removes the open npm dependency and adds explicit, platform-specific browser command resolution (open/xdg-open/PowerShell, including WSL handling). Updates contracts/RPC schemas by renaming OpenInEditorInput → LaunchEditorInput and OpenError → ExternalLauncherError, and adjusts tests to mock the spawner and cover the new browser-launch mapping.

^{Reviewed by Cursor Bugbot for commit 9e37f0d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR replaces the 'open' npm package with a custom browser/editor launch implementation including WSL detection and platform-specific PowerShell encoding. This is a significant runtime behavior change that replaces a mature library with new custom code, warranting human review for cross-platform compatibility.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 78a2cec. Configure here.}