zames_pro 2.82.107 → 2.82.109

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.82.109] - 2026-10-24
+
+### Fixed
+
+- **tui:** a failure phrase inside the output does not mark the call failed
+
+## [2.82.108] - 2026-10-24
+
+### Fixed
+
+- **diagnostics:** a mid-line tsc error is not hidden by a zero banner
+
 ## [2.82.107] - 2026-10-24
 
 ### Fixed

package/dist/diagnostics.js

@@ -34,11 +34,15 @@ export function summarizeDiagnostics(raw, maxChars) {
     // appended a pointless diagnostics block.
     const plain = text.replace(/\x1b\[[0-9;?]*[A-Za-z]/g, '');
     const cleanCheck = plain.replace(/^\[[^\]]*\]\s*/, '');
-    // The banner is only CLEAN when the output carries NO error-looking line:
+    // The banner is only CLEAN when the output carries NO error-looking text:
     // a webpack/build log prints `ERROR in …` AND its own `Found 0 errors`
     // summary, and the old whole-text check reported that run as clean — the
-    // real error never reached the model.
-    const hasErrorLine = /(^|\n)\s*(?:error\b|ERROR\b|✖|✗|TS\d{4}\b)/m.test(cleanCheck);
+    // real error never reached the model. The check is NOT anchored to the
+    // start of a line: a normal tsc failure is `src/a.ts(1,1): error TS2322: …`
+    // and `error` sits MID-LINE; an anchored pattern missed it and a stray
+    // `Found 0 errors` (a watch banner in the same buffer) swallowed the real
+    // error.
+    const hasErrorLine = /\berror\b|✖|✗|TS\d{4}\b/i.test(cleanCheck);
     if (!hasErrorLine) {
         if (/^(?:found\s+)?0\s+errors?\b/im.test(cleanCheck))
             return null;

package/dist/tool-summary.js

@@ -84,11 +84,17 @@ export function looksLikeToolError(result) {
         .toLowerCase();
     if (!head)
         return false;
+    const whole = String(result ?? '').toLowerCase();
     return (head.startsWith('error') ||
         head.startsWith('missing required argument') ||
         head.startsWith('failed') ||
-        head.includes('command failed') ||
-        head.includes('exit code') ||
+        // The run's OWN failure lines are anchored at the start of a line
+        // (`Exit code: N`, the `stdout:/stderr:` blocks follow). A phrase that
+        // merely APPEARS in the output (a log line, a diff, a test summary) is
+        // data, not a failure: a red ✖ on a successful call is just as wrong as a
+        // green ✔ on a refused one.
+        /^exit code\b/m.test(whole) ||
+        /^command failed\b/m.test(whole) ||
         // NOT every failure is a THROWN error: a PreToolUse hook, the permission
         // policy and the operator's denial BLOCK the call and return their message
         // as the result; an unknown tool and an aborted/timed-out run are reported

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zames_pro",
-  "version": "2.82.107",
+  "version": "2.82.109",
   "description": "Terminal coding agent that drives a real browser to chat with DeepSeek, Qwen and other web LLMs — no API key required. Reads and edits files, runs commands, commits to git, like Claude Code / Codex CLI.",
   "type": "module",
   "bin": {