Windows: first jcode launch fails with "Server exited before becoming ready" / named pipe access denied.

Environment: Windows 11, jcode v0.61.1 (438789eb)

Steps to reproduce:

1. Open a fresh PowerShell session (no jcode server currently running)
2. Run jcode from a project directory (e.g. C:\xampp\htdocs)

Observed output:
Starting server...
Error: Server exited before becoming ready (status: exit code: 1). Using Claude (use /model to switch models)
[windows] Named pipe \.\pipe\jcode-5de220f6a505e7ec busy (access denied), retrying without first_pipe_instance
Error: Access is denied. (os error 5)

Actual behavior:
The client reports the server failed to start and exited with code 1. However, a server process did start successfully in the background — confirmed via ~/.jcode/servers.json, which showed a live entry with a valid PID immediately after the failure. Running jcode again immediately afterward (even from a different directory) connects to that server without issue and creates a new session normally.

Expected behavior
The initial jcode invocation should either connect successfully on the first try, or the error message should not claim the server "exited" when it is in fact still running and reachable moments later.

Reproduce the first launch from a fresh PowerShell session on Windows and inspect the server startup and named-pipe handling around the reported access-denied error. Compare the initial invocation with the successful second invocation and the live entry in ~/.jcode/servers.json. Done means the first invocation connects successfully, or reports the server state accurately instead of claiming it exited.