Fix terminal reconnect crash from server-side WebSocket.OPEN usage

[realproject7]

Context

During local pilot testing on plotlink-ows@1.0.34, a newly-created Untitled cartoon story opens the terminal reconnect overlay. Both Resume Session and Start Fresh fail because the OWS server crashes as soon as PTY output is relayed.

Server log:

/Users/cho/Projects/plotlink-ows/app/routes/terminal.ts:353
    if (ws.readyState === WebSocket.OPEN) {
                          ^
ReferenceError: WebSocket is not defined
    at <anonymous> (.../app/routes/terminal.ts:353:27)

Root Cause

app/routes/terminal.ts runs in Node/Hono, not the browser. It receives a raw WebSocket object from the server upgrade path, but WebSocket.OPEN is a browser global and is not available in this runtime. The code should not reference the browser WebSocket constructor in server code.

Current problematic code:

if (ws.readyState === WebSocket.OPEN) {
  ws.send(data);
}

Required Fix

• Replace server-side WebSocket.OPEN usage with a runtime-safe check.
• Prefer a local constant such as const WS_OPEN = 1 or a helper like isSocketOpen(ws).
• Audit app/routes/terminal.ts for any other browser-only WebSocket globals.
• Add/adjust a regression test for attachTerminalWs or the terminal command helper if practical.
• Verify both buttons work:
  • Resume Session reconnects using stored session id when valid.
  • Start Fresh kills the old PTY/session state and spawns a fresh Claude session without crashing.

Notes

The reconnect overlay itself can be legitimate for _new_* sessions because ~/.plotlink-ows/data/terminal-sessions.json currently contains stored untitled session ids. The immediate blocker is that reconnect/fresh actions crash the server before Claude can start.

Verification

• npm run typecheck
• npm test -- --run app/routes/terminal.test.ts
• Manual local check with npm run app:dev, then create a new story and click Start Fresh from the reconnect overlay.

[realproject7]

Additional pilot log: after the server crashes from the terminal WebSocket relay, Vite on :5173 reports proxy ECONNREFUSED for /api/auth/status and /api/auth/verify. This is a secondary symptom: the backend on :7777 is no longer running, so the renderer proxy cannot reach API routes.