zames_pro 2.95.2 → 2.95.3

package/CHANGELOG.md

@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.95.3] - 2026-11-04
+
+### Fixed
+
+- **deepseek:** an appended answer is not a dead turn
+- slow start
+
 ## [2.95.2] - 2026-11-04
 
 ### Changed

package/dist/browser.js

@@ -2297,11 +2297,15 @@ export class DeepSeekBrowser {
         // Wait for the start: either Stop appeared, or the answer text changed,
         // or the page grew (a new answer node / longer last answer). In parallel we
         // catch the rate-limit toast (only toasts, not the whole body).
-        // MEASURED live: an answer either starts within a few seconds or the send
-        // did not go out at all. The old 30s + 20s windows meant FIFTY seconds of
-        // a frozen "generating" status on every missed start; 12s + 10s is
-        // plenty for DeepSeek to show the Stop button or start streaming.
-        const startDeadline = Date.now() + 12_000;
+        //
+        // MEASURED on 90 live turns: the server needs a MEDIAN of ~16s to deliver a
+        // completion body (min 11.7s, max 25.8s), so the old 12s window was shorter
+        // than a NORMAL turn. The loop then declared "the send did not go out" and
+        // pressed Enter AGAIN — a DUPLICATE turn that ended in "Messages too
+        // frequent". The window only has to cover the SEND (the input clearing, the
+        // Stop button appearing), not the answer, so 30s is generous without
+        // delaying a real miss by minutes.
+        const startDeadline = Date.now() + 30_000;
         // A CHEAP growth signal (message-node count + last-answer length)
         // instead of document.body.innerText.length, which walked the whole page.
         const startSignal = await this._chatSignal();
@@ -2314,6 +2318,7 @@ export class DeepSeekBrowser {
         // the text has been stable for a couple of ticks.
         let settledTicks = 0;
         let lastStartCur = '';
+        let stopTicks = 0;
         while (Date.now() < startDeadline) {
             if (this._abort || this._askCancelled)
                 return '(прервано пользователем)';
@@ -2441,7 +2446,20 @@ export class DeepSeekBrowser {
             // 'changed' can stay false for a while — without this check ask() used
             // to hang until the full timeout and the agent appeared to "stop".
             const netStarted = !!this._netCapture && this._netCaptureAt >= this._lastSentAt;
-            if (changed || netStarted || grew) {
+            // The Stop button is the SERVER's own "a turn is running" signal, and it
+            // appears long before the first token reaches the DOM or the completion
+            // body is complete (measured: the body lands a median 16s after the
+            // send, while Stop shows up within a second). Without it a SLOW network
+            // looked like a failed send: the loop hit the start deadline and pressed
+            // Enter again, producing a duplicate turn. A lingering Stop from the
+            // previous generation is ruled out by requiring TWO consecutive ticks
+            // with the button visible, so a single stray paint does not start us.
+            const stopVisible = await this._isGenerating();
+            if (stopVisible)
+                stopTicks++;
+            else
+                stopTicks = 0;
+            if (changed || netStarted || grew || stopTicks >= 2) {
                 started = true;
                 this._askDebug('STARTED changed=' +
                     changed +

package/dist/net-capture.js

@@ -257,13 +257,16 @@ export function isFinishedWithoutAnswer(body) {
     const finished = FINISHED_STATUS_RE.test(b);
     if (!finished)
         return false;
-    // A RESPONSE fragment with real content means the model DID answer.
-    const len = responseContentLength(b);
-    if (len >= MIN_REAL_ANSWER_CHARS)
-        return false;
-    // No RESPONSE fragment at all (len === -1) or only a truncated head:
-    // treat the absence of a real answer as "no answer produced".
-    return true;
+    // MEASURED live: `responseContentLength` only sees the SNAPSHOT fragment
+    // (`v.response.fragments[]`), while DeepSeek appends the REAL answer through
+    // bare `data: {"v":...}` chunks. A live body with a `\n\n` snapshot and
+    // 1121 chars of appended text measured 2 chars, so 18 of 71 healthy bodies
+    // were classified as "finished WITHOUT an answer" — the finish loop then
+    // threw `GenerationIncompleteError` (no Continue button), ask() resent the
+    // task and the operator saw "DeepSeek оборвал ответ" on a perfectly good
+    // turn. The DECODED answer is the truth: use the real extractor.
+    const text = extractAnswer(b).trim();
+    return text === '' || TRUNCATED_HEAD_RE.test(text);
 }
 /**
  * True when a FINISHED body still carries NO complete answer — its only

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zames_pro",
-  "version": "2.95.2",
+  "version": "2.95.3",
   "description": "Terminal coding agent that drives a real browser to chat with DeepSeek, Qwen or GLM — no API key required. Reads and edits files, runs commands, commits to git, like Claude Code / Codex CLI.",
   "type": "module",
   "bin": {
@@ -20,7 +20,7 @@
   ],
   "scripts": {
     "start": "node ./dist/index.js",
-    "dev": "ZAMES_NET_DEBUG=1 tsx ./src/index.ts --dev --headed",
+    "dev": "ZAMES_NET_DEBUG=1 ZAMES_ASK_DEBUG=1 tsx ./src/index.ts --dev --headed",
     "clean": "tsx scripts/clean-dist.mts",
     "build": "tsx scripts/clean-dist.mts && tsc -p tsconfig.build.json",
     "coverage:gate": "tsx scripts/coverage-gate.mts",