fix: prevent spurious 'session not found' warns on session close (#26)

When closing the only session, the WebSocket \onclose\ reconnect handler
races with \ emoveSession()\ cleanup. The reconnect fires, opens a new
WS, and sends \�ttach\ for the already-deleted session — producing two
spurious warn logs.

**Fix:** Set \ms.exited = true\ and clear the reconnect timer *before*
closing the WebSocket in \ emoveSession()\, so the \onclose\ handler
skips reconnection.

---

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: dorlugasigal

public/terminal.html

@@ -1350,12 +1350,16 @@ <h3>
       }
 
       async function removeSession(id) {
-        try { await fetch('/api/sessions/' + encodeURIComponent(id), { method: 'DELETE' }); } catch {}
-
         const ms = managed.get(id);
         if (ms) {
+          ms.exited = true;
+          if (ms.reconnectTimer) { clearTimeout(ms.reconnectTimer); ms.reconnectTimer = null; }
           if (ms.ws) try { ms.ws.close(); } catch {}
-          if (ms.reconnectTimer) clearTimeout(ms.reconnectTimer);
+        }
+
+        try { await fetch('/api/sessions/' + encodeURIComponent(id), { method: 'DELETE' }); } catch {}
+
+        if (ms) {
           ms.term.dispose();
           ms.container.remove();
           managed.delete(id);
@@ -2169,8 +2173,9 @@ <h3>
             for (const id of [...managed.keys()]) {
               if (!serverIds.has(id)) {
                 const ms = managed.get(id);
+                ms.exited = true;
+                if (ms.reconnectTimer) { clearTimeout(ms.reconnectTimer); ms.reconnectTimer = null; }
                 if (ms.ws) try { ms.ws.close(); } catch {}
-                if (ms.reconnectTimer) clearTimeout(ms.reconnectTimer);
                 ms.term.dispose();
                 ms.container.remove();
                 managed.delete(id);