EPIC: Server Lifecycle and Connectivity Reliability #244
Description
Goal: Robust startup and fault handling for real robots and simulators. Scope: 1) detect and handle robot/bot disconnects across TCP/WebSocket; 2) add a readiness gate so server does not accept commands until hardware/sockets are ready; 3) clear client notifications and recovery flows. Key code: src/server/api/socket-manager.ts, src/server/api/tcp-interface.ts, src/server/api/client-manager.ts, src/server/robot/robot-manager.ts, src/server/main.ts, src/server/simulator.ts. Acceptance: Readiness event/flag blocks command intake until ready; disconnects mark robots unavailable, cancel in-flight moves safely, and notify clients; simulator reproduces these flows.