osborn 0.9.74 → 0.9.76

package/dist/index.js

@@ -10,7 +10,7 @@ initializeLogger({ pretty: true, level: 'info' });
 import { setMaxListeners } from 'node:events';
 setMaxListeners(50);
 import { createServer } from 'http';
-import { existsSync, readdirSync, readFileSync, mkdirSync, writeFileSync, mkdtempSync, cpSync, rmSync, statSync, createWriteStream } from 'node:fs';
+import { existsSync, readdirSync, readFileSync, mkdirSync, writeFileSync, mkdtempSync, cpSync, rmSync, statSync, utimesSync, createWriteStream } from 'node:fs';
 import { dirname, join } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { spawn } from 'node:child_process';
@@ -603,6 +603,18 @@ function startApiServer(workingDir, port) {
                             // the only structural change; file contents are immutable historical
                             // record and must roundtrip cleanly between environments.
                             cpSync(sp, dp, { force: true });
+                            // 0.9.75: preserve the source mtime on the copy. cpSync stamps the
+                            // destination with "now", which scrambled session ordering after
+                            // every sync — the frontend's auto-resume picks most-recent-by-mtime,
+                            // so a fresh import made a random tar-order file (often a tiny
+                            // months-old session) look newest, and users kept "resuming" into
+                            // stale June sessions (confirmed in prod 2026-07-27, 3× in a row).
+                            // The tarball carries original mtimes; copying must not discard them.
+                            try {
+                                const srcStat = statSync(sp);
+                                utimesSync(dp, srcStat.atime, srcStat.mtime);
+                            }
+                            catch { /* best-effort — ordering degrades gracefully */ }
                             filesWritten++;
                         }
                         // skip symlinks, sockets, etc.
@@ -1302,7 +1314,18 @@ async function main() {
                 console.log(`🧟 [ZOMBIE-WATCHDOG] room empty for ${emptyPolls} consecutive polls (${emptyForMs / 1000}s) — forcing leave`);
                 emptyPolls = 0;
                 intentionalLeave = true;
-                room.disconnect().catch((e) => console.error('watchdog room.disconnect failed:', e));
+                // Update state FIRST, don't wait for the Disconnected event — a zombie
+                // WS is precisely the case where that event never arrives. Observed
+                // 2026-07-27: after a forced leave the status stayed 'connected', so
+                // /health lied, /connect-room no-op'd, and the next user joined a room
+                // the agent wasn't in (UI stuck at "Connecting..."). Setting idle here
+                // makes the next /connect-room actually rejoin. If the Disconnected
+                // event does fire later, its handler sets the same state — idempotent.
+                livekitState.status = 'idle';
+                const disconnectWatch = setTimeout(() => console.error('🧟 [ZOMBIE-WATCHDOG] room.disconnect() still pending after 10s — WS likely zombied; idle-exit timer is the backstop'), 10_000);
+                room.disconnect()
+                    .then(() => { clearTimeout(disconnectWatch); console.log('🧟 [ZOMBIE-WATCHDOG] forced leave completed'); })
+                    .catch((e) => { clearTimeout(disconnectWatch); console.error('watchdog room.disconnect failed:', e); });
                 // Belt-and-suspenders: if the WS is zombied the Disconnected event may
                 // never fire (so the idle-exit arm in that handler won't run). Arm here too.
                 armIdleExitTimer('zombie-watchdog forced leave');
@@ -4724,6 +4747,16 @@ async function main() {
             return; // already in the room — no-op
         console.log('🔌 /connect-room — joining LiveKit for incoming user');
         await connectWithRetry();
+        // Join-race fix: ParticipantConnected only fires for participants who join
+        // AFTER us. If the user's browser won the race (its token mint + WebRTC
+        // handshake finished before our rejoin), they're already in the room when
+        // we arrive — no event, no voice session, UI hangs at "Connecting...".
+        // Re-emit the event for every pre-existing participant so the session is
+        // created exactly as if they had joined after us.
+        for (const p of room.remoteParticipants.values()) {
+            console.log(`👥 Participant already in room at join: ${p.identity} — adopting (re-emitting ParticipantConnected)`);
+            room.emit(RoomEvent.ParticipantConnected, p);
+        }
     };
     // 0.9.73: explicit frontend leave should also start the idle-exit countdown —
     // the user is done; the machine shouldn't idle-bill waiting for a maybe-return.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "osborn",
-  "version": "0.9.74",
+  "version": "0.9.76",
   "description": "Voice AI coding assistant - local agent that connects to Osborn frontend",
   "type": "module",
   "bin": {