@threadbase-sh/streamer 1.23.0 → 1.23.1

package/dist/cli.cjs

@@ -137289,7 +137289,10 @@ var ConversationCache = class _ConversationCache {
           model         = excluded.model,
           account       = excluded.account,
           branch        = excluded.branch,
-          message_count = excluded.message_count,
+          -- message_count is incremented by live tailing but recounted from
+          -- scratch by a scanner rescan; a stale rescan must not carry a live
+          -- session's count backwards, so take the max instead of overwriting.
+          message_count = MAX(conversation_meta.message_count, excluded.message_count),
           last_activity = excluded.last_activity,
           first_message = excluded.first_message,
           last_message  = excluded.last_message,
@@ -137566,6 +137569,7 @@ var ConversationCache = class _ConversationCache {
           fileSize = s3.size;
         } catch {
         }
+        const seq = ++this.tailSeq;
         this.stmts.upsertFull.run({
           id,
           file_path: m2.filePath,
@@ -137580,7 +137584,7 @@ var ConversationCache = class _ConversationCache {
           first_message: m2.firstMessage ? JSON.stringify(m2.firstMessage) : null,
           last_message: m2.lastMessage ? JSON.stringify(m2.lastMessage) : null,
           preview: m2.preview ?? null,
-          updated_at: 0,
+          updated_at: seq,
           mtime_ms: mtimeMs,
           file_size: fileSize,
           provider: m2.provider ?? CLAUDE_CODE_PROVIDER2
@@ -137797,9 +137801,25 @@ var ConversationCache = class _ConversationCache {
       this.fileIndex.clear();
     }
   }
-  invalidateByFilePath(filePath) {
+  /**
+   * Drop the cached row for a file. Two callers with opposite intent:
+   *  - a directory-watch "change" event (the file was appended to) — pass
+   *    `skipIfTailed: true`. A cached tail means the row is being actively
+   *    maintained from the file's real content by the live-tail
+   *    (updateFromLines) or warm-up path, fresher than any scanner-derived
+   *    view. Both watchers fire on the same append with no ordering guarantee;
+   *    without this guard the invalidate can land after the tail write and wipe
+   *    the just-cached row, flickering the conversation out of
+   *    /api/conversations on nearly every message (CRITICAL #2). The debounced
+   *    rescan still re-derives metadata, so skipping the eager drop loses
+   *    nothing.
+   *  - a genuine unlink (the file is gone) — leave `skipIfTailed` false so the
+   *    row is always removed, otherwise a deleted session ghosts in the cache.
+   */
+  invalidateByFilePath(filePath, opts) {
     const row = this.stmts.getIdByFilePath.get(filePath);
     if (!row) return null;
+    if (opts?.skipIfTailed && this.stmts.hasTail.get(row.id)) return null;
     this.invalidate(row.id);
     return row.id;
   }
@@ -142044,7 +142064,7 @@ var StreamerServer = class {
         }
       },
       onConversationChanged: (filePath) => {
-        this.cache?.invalidateByFilePath(filePath);
+        this.cache?.invalidateByFilePath(filePath, { skipIfTailed: true });
         this.markScannerStaleDebounced();
         this.log.debug?.(`Scanner invalidated by directory event: ${filePath}`, {
           filePath,