@astralform/js 6.0.2 → 6.0.3

package/dist/index.js

@@ -2711,15 +2711,15 @@ var StreamManager = class {
     try {
       const jobs = await this.session.client.get(`/v1/conversations/${encodeURIComponent(conversationId)}/jobs`);
       if (stopReplay()) return false;
-      const completedJobs = jobs.filter(
-        (j) => j.status === "completed" && j.job_id !== activeJobId
+      const replayableJobs = jobs.filter(
+        (j) => j.job_id !== activeJobId
       );
       const userMessages = this.session.messages.filter(
         (m) => m.role === "user"
       );
       const runningJob = activeJobId ? jobs.find((j) => j.job_id === activeJobId) : void 0;
       const plan = planRestore({
-        completedJobs: completedJobs.map((j) => ({
+        completedJobs: replayableJobs.map((j) => ({
           job_id: j.job_id,
           message_id: j.message_id
         })),
@@ -2727,27 +2727,38 @@ var StreamManager = class {
           job_id: runningJob.job_id,
           message_id: runningJob.message_id
         },
-        // Completed jobs PLUS the ones still going. A send landing in the
-        // probe window has a running job, so its prompt is claimed and does
-        // not read as a steer replayed over the bubble the live send already
-        // rendered. Failed and cancelled jobs are deliberately NOT claimed:
-        // they produce no `turn` step, so claiming them would delete the
-        // user's prompt from the restore entirely rather than show it as a
-        // steer.
-        claimedMessageIds: jobs.filter((j) => j.status !== "failed" && j.status !== "cancelled").map((j) => j.message_id),
+        // EVERY job, which is the same set the replay walk gets. The claim set
+        // answers one question — "will some turn step already draw this prompt?"
+        // — so it is a RESTATEMENT of the walk, and the two drifting apart is
+        // what produces either a missing bubble or a doubled one.
+        //
+        // Failed and cancelled were excluded here for exactly one reason: they
+        // produced no turn step, which is the bug fixed above. Now that they do,
+        // the exclusion has no case left to describe.
+        //
+        // Being precise about what this change does and does not do: it is not
+        // load-bearing TODAY. `planRestore` anchors a prompt at the index its
+        // job links to and advances the cursor past it, so a message claimed by
+        // a job inside the walk is never offered to the steer branch anyway —
+        // the two spellings agree on current inputs. It is here because the
+        // invariant is what keeps them agreeing: narrow the walk again without
+        // narrowing this, and the prompts of the jobs dropped from it go with
+        // them, silently. Deriving both from `jobs` makes that impossible to
+        // get half-right.
+        claimedMessageIds: jobs.map((j) => j.message_id),
         userMessages: userMessages.map((m) => ({
           id: m.id,
           content: m.content
         }))
       });
       const eventLists = await Promise.all(
-        completedJobs.map(
+        replayableJobs.map(
           (job) => this.session.client.getConversationEvents(conversationId, job.job_id).catch(() => [])
         )
       );
       if (stopReplay()) return false;
       const eventsByJobId = new Map(
-        completedJobs.map((job, i) => [job.job_id, eventLists[i] ?? []])
+        replayableJobs.map((job, i) => [job.job_id, eventLists[i] ?? []])
       );
       for (const step of plan) {
         if (stopReplay()) return false;
@@ -2769,11 +2780,14 @@ var StreamManager = class {
         );
       }
       if (stopReplay()) return false;
-      if (completedJobs.length > 0) {
+      const versionCount = replayableJobs.filter(
+        (j) => j.status === "completed"
+      ).length;
+      if (versionCount > 0) {
         this.emit({
           type: "versionsReady",
           conversationId,
-          count: completedJobs.length
+          count: versionCount
         });
       }
     } catch {