thinkpool-pair 0.7.89 → 0.7.91

package/bridge.mjs

@@ -579,7 +579,7 @@ const announce = () =>
       // the chosen label instead of defaulting to Normal / unnamed. `spawned` (set
       // when an agent Dispatched this lane via spawn_terminal) lets the client keep
       // it OUT of the top tab strip and show it only in the Ensemble menu.
-      ...[...sessions.entries()].map(([id, s]) => ({ id, cmd: s.cmd, kind: 'structured', alive: true, commands: s.commands, mode: s.mode || undefined, name: termNames[id] || undefined, ...(s.spawnedBy ? { spawned: true } : {}) })),
+      ...[...sessions.entries()].map(([id, s]) => ({ id, cmd: s.cmd, kind: 'structured', alive: true, commands: s.commands, mode: s.mode || undefined, name: termNames[id] || undefined, ...(s.spawnedBy ? { spawned: true, spawnedBy: s.spawnedBy } : {}) })),
     ],
   })
 

package/event-id.mjs

@@ -98,10 +98,20 @@ export function capReplayEvents(events, budget = REPLAY_BYTE_BUDGET) {
 // no event in the recent window is lost (capReplayEvents truncates; this doesn't). Each
 // returned chunk is broadcast as its own `code-replay` — seqDedup.classifyReplay applies
 // them in order (each chunk is contiguous and seq > seqHi), so the client rebuilds the
-// whole window across frames. We keep the MOST RECENT `maxChunks * budget` bytes (older
-// history is the DB transcript snapshot's job) so a giant log doesn't fan out 30+ frames.
+// whole window across frames. We keep the MOST RECENT `maxChunks * budget` bytes.
+//
+// 6 → 14 (2026-06-29): 6 chunks = 900KB, but a real session's full log routinely
+// exceeds that (measured: a forge thread = 1.0MB / 7 chunks, a maxed 2000-event
+// lane = 1.7MB / 12 chunks), so the OLDEST turns — incl. the user's first prompt —
+// were dropped on replay and never reached the client ("not seeing full history of
+// terminal N", Max 2026-06-29). The DB transcript snapshot can't cover the gap: it's
+// capped at 200 tx events AND the client can only persist what it received, so the
+// head only ever lived in this in-memory log. The bridge already hard-caps the log at
+// STRUCTURED_LOG_MAX (2000) events ≈ 2.1MB worst case, so 14 chunks (2.1MB) sends the
+// WHOLE retained log on a fresh (cursor-0) replay — chunkReplayEvents still only emits
+// as many chunks as the log needs, so small sessions are unaffected.
 // Returns an array of event-arrays, oldest chunk first; [] when there's nothing to send.
-export const REPLAY_MAX_CHUNKS = 6
+export const REPLAY_MAX_CHUNKS = 14
 export function chunkReplayEvents(events, budget = REPLAY_BYTE_BUDGET, maxChunks = REPLAY_MAX_CHUNKS) {
   if (!Array.isArray(events) || events.length === 0) return []
   // Walk newest→oldest accumulating into the current chunk; start a new chunk when the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "thinkpool-pair",
-  "version": "0.7.89",
+  "version": "0.7.91",
   "description": "Share a local coding-agent CLI (Claude Code, Codex, Gemini, Aider, …) into a ThinkPool Code room, live.",
   "type": "module",
   "bin": {