shadok-ai 0.16.11 → 0.16.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shadok-ai",
-  "version": "0.16.11",
+  "version": "0.16.13",
   "main": "dist/session.js",
   "scripts": {
     "test": "node --import tsx --test --test-timeout=120000 test/*.ts context/*/test/*.test.mjs",

package/public/index.html

@@ -5273,6 +5273,20 @@
   // source of truth. A new session (e.g. a Telegram /spawn) shows up as a tab
   // live; a renamed channel renames its tab; a channel that left the registry
   // (ended elsewhere) closes its tab.
+  /** Is a group name being TYPED right now, anywhere? The server→client name
+   *  sync must not overwrite the field under the cursor, and there are three
+   *  places to rename a group: its head in the agents column, its row in the
+   *  rail, and — since the column title became editable — that title. Keying
+   *  the guard on the group HEAD alone missed the last two: `inlineRename`
+   *  swaps the span it was given for the input, so the input is wherever the
+   *  gesture started, not inside `headEl`. One query over all three, and the
+   *  name is simply left alone for one poll (4 s), which costs nothing. */
+  function renamingAGroup() {
+    return !!document.querySelector(
+      "#groups input.rename, #railList input.rename, #tabbar .side-label input.rename",
+    );
+  }
+
   let lastChannelIds = new Set();
   async function syncChannels() {
     if (restoring) return;
@@ -5292,7 +5306,7 @@
         if (sg == null || sg.id == null) continue;
         const g = groups.find((x) => x.id === sg.id);
         if (!g) { createGroup(sg); continue; }
-        if (sg.name && sg.name !== g.nameEl.textContent && !g.headEl.querySelector("input"))
+        if (sg.name && sg.name !== g.nameEl.textContent && !renamingAGroup())
           g.nameEl.textContent = sg.name;
         if (sg.icon && sg.icon !== g.icon) g.icon = sg.icon;
       }
@@ -7873,11 +7887,25 @@
         // reloads onto the new build quickly instead of waiting out a backoff.
         reloadExpectedUntil = Date.now() + 90_000;
         break;
-      case "history":
+      case "history": {
         // Full replay from the transcript (source of truth). Clear first so a
         // reconnect (laptop wake / dropped link) rebuilds the transcript instead
         // of appending a second copy of the whole history.
-        t.transcriptEl.innerHTML = "";
+        //
+        // Hold the reader's place across the wipe+rebuild. On a RECONNECT the
+        // transcript already carries the conversation, and tearing it down to
+        // rebuild it snaps the view to the top UNLESS the browser's scroll
+        // anchoring happens to save us — which it does not when the tab was in
+        // the background while the replay ran (anchoring needs a live layout),
+        // and does not in Safari. That is the reported "the chat jumps back up
+        // when I come back". The replay is the same messages in the same order,
+        // appended bottom-first, so we restore deterministically: pinned to the
+        // bottom if they were following live, otherwise holding the same
+        // distance from the bottom so what they were reading stays in view.
+        const el = t.transcriptEl;
+        const wasStick = el._stickBottom !== false;
+        const fromBottom = Math.max(0, el.scrollHeight - el.scrollTop - el.clientHeight);
+        el.innerHTML = "";
         t.unreadSep = null; // the separator element went with the wipe
         addTurn(t, "system", "", "— resumed session history —");
         for (const h of msg.turns) {
@@ -7909,7 +7937,14 @@
             if (h.afterInternal) b.parentElement.classList.add("after-gap");
           }
         }
+        // Restore the reader's place deterministically — never trust the
+        // browser's implicit scroll anchoring for a full teardown.
+        el._stickBottom = wasStick;
+        el.scrollTop = wasStick
+          ? el.scrollHeight
+          : Math.max(0, el.scrollHeight - el.clientHeight - fromBottom);
         break;
+      }
       case "ready":
         // The server just named the instance it is. If it's not the one this
         // page was loaded from, the port was taken over — stop writing, prompt a