🤖 refactor: migrate IPC layer to ORPC for type-safe RPC

[ThomasK33]

Summary

Replaces the custom IPC layer with oRPC for type-safe RPC between browser/renderer and backend processes.

Key Changes

Architecture

• New ORPC router (src/node/orpc/router.ts) - Central router defining all RPC endpoints with Zod schemas
• Schema definitions (src/common/orpc/schemas.ts) - Shared Zod schemas for request/response validation
• ServiceContainer (src/node/services/serviceContainer.ts) - Dependency injection container for all backend services
• React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC() hook for frontend

Transport

• Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
• Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
• Auth middleware with timing-safe token comparison for server mode

Subscriptions

Streaming endpoints (chat events, metadata updates, terminal output) use async generators:

// Router
handler: async function* ({ context, input }) {
  const unsubscribe = service.onEvent(push);
  try {
    while (!ended) { yield queue.shift() ?? await nextEvent(); }
  } finally { unsubscribe(); }
}

// Client
for await (const event of client.workspace.onChat({ workspaceId })) {
  handleEvent(event);
}

Removed

• src/browser/api.ts (old HTTP/WS client)
• src/node/services/ipcMain.ts (old IPC handler registration)
• src/desktop/preload.ts IPC method definitions (now just MessagePort forwarding)
• tests/ipcMain/ directory (migrated to tests/integration/)

Testing

• All existing tests migrated to use ORPC test client
• New StreamCollector utility for testing async generator subscriptions
• Server endpoint tests for HTTP and WebSocket transports

Migration Notes

• Frontend components now use useORPC() hook instead of window.api
• Stores receive client via setClient() during app initialization
• Type safety is enforced at compile time via Zod schema inference

---

Generated with mux

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".