@polka-codes/cli 0.9.37 → 0.9.38

package/dist/index.js

@@ -25374,7 +25374,7 @@ var require_dist3 = __commonJS((exports) => {
       req.emit("proxyConnect", connect);
       this.emit("proxyConnect", connect, req);
       if (connect.statusCode === 200) {
-        req.once("socket", resume);
+        req.once("socket", resume2);
         if (opts.secureEndpoint) {
           debug("Upgrading socket connection to TLS");
           return tls.connect({
@@ -25398,7 +25398,7 @@ var require_dist3 = __commonJS((exports) => {
   }
   HttpsProxyAgent.protocols = ["http", "https"];
   exports.HttpsProxyAgent = HttpsProxyAgent;
-  function resume(socket) {
+  function resume2(socket) {
     socket.resume();
   }
   function omit2(obj, ...keys) {
@@ -58608,7 +58608,7 @@ var {
   Help
 } = import__.default;
 // package.json
-var version = "0.9.37";
+var version = "0.9.38";
 
 // src/commands/chat.ts
 import { readFile as readFile3 } from "node:fs/promises";
@@ -87178,7 +87178,13 @@ var makeAgentStepSpecHandler = (getModelFn) => ({
           const handleExitReason = async (reason) => {
             switch (reason.type) {
               case "Pause":
-                return { type: "paused", state: { messages: agent.messages } };
+                return {
+                  type: "paused",
+                  state: {
+                    messages: agent.messages,
+                    usage: usageMeter.usage
+                  }
+                };
               case "UsageExceeded":
                 return { type: "error", error: new Error("Usage limit exceeded") };
               case "Exit" /* Exit */: {
@@ -87287,6 +87293,13 @@ class StepsBuilder {
       step
     });
   }
+  loop(id, config2) {
+    return this.step({
+      ...config2,
+      id,
+      type: "loop"
+    });
+  }
   custom(idOrSpec, run) {
     if (typeof idOrSpec === "string") {
       if (!run) {
@@ -87300,6 +87313,13 @@ class StepsBuilder {
     }
     return this.step(idOrSpec);
   }
+  workflow(id, config2) {
+    return this.step({
+      ...config2,
+      id,
+      type: "workflow"
+    });
+  }
   agent(id, spec2) {
     return this.step({
       ...spec2,
@@ -87307,6 +87327,13 @@ class StepsBuilder {
       type: "agent"
     });
   }
+  branch(id, config2) {
+    return this.step({
+      ...config2,
+      id,
+      type: "branch"
+    });
+  }
 }
 var builder = () => {
   return new StepsBuilder;
@@ -87340,6 +87367,29 @@ var runStep = async (step, input, context, resumedState, allOutputs) => {
   }
 };
 
+// ../core/src/workflow/workflow.ts
+var run = async (workflow, context, handler15, input) => {
+  const rootStep = handler15(workflow.step, handler15);
+  const result = await runStep(rootStep, input, context, undefined, {});
+  switch (result.type) {
+    case "paused":
+      return {
+        type: "paused",
+        state: result.state
+      };
+    case "error":
+      return {
+        type: "error",
+        error: result.error
+      };
+    case "success":
+      return {
+        type: "success",
+        output: result.output
+      };
+  }
+};
+
 // ../core/src/workflow/steps.ts
 var combineHandlers = (...handlers) => {
   const allHandlers = {};
@@ -87403,28 +87453,6 @@ var customStepSpecHandler = {
     };
   }
 };
-// ../core/src/workflow/workflow.ts
-var run = async (workflow, context, handler15, input) => {
-  const rootStep = handler15(workflow.step, handler15);
-  const result = await runStep(rootStep, input, context, undefined, {});
-  switch (result.type) {
-    case "paused":
-      return {
-        type: "paused",
-        state: result.state
-      };
-    case "error":
-      return {
-        type: "error",
-        error: result.error
-      };
-    case "success":
-      return {
-        type: "success",
-        output: result.output
-      };
-  }
-};
 // src/commands/chat.ts
 var import_lodash6 = __toESM(require_lodash(), 1);
 
@@ -106610,6 +106638,7 @@ Core Objective
 - Extract and report ONLY the key lines that communicate failures, warnings, and actionable issues.
 - Ignore routine noise: progress bars, spinners, timestamps, banners, environment echoes, compilation start/finish messages, and other benign status lines.
 - Prefer brevity and accuracy. Do not ask questions. Do not repeat yourself.
+- Preserve the minimal set of surrounding lines (command headers, "Traceback" prologues, "Caused by" chains) required to fully understand each surfaced error or warning.
 
 General Rules
 1) Preprocessing
@@ -106635,7 +106664,8 @@ General Rules
      - Notes:
    - Within each section, use compact bullet points ("- ").
    - Quote key lines verbatim when they carry the signal (file:line:col, codes, rule names, assertion diffs).
-   - Never include large code blocks; include at most 1-2 context lines around a key message when indispensable, marked with "...".
+   - When a diagnostic spans multiple lines or relies on nearby context (command invocation, "Traceback", "Caused by"), keep the contiguous block together in the bullet. Indent continuation lines with two spaces. Only elide middle lines if the block exceeds ~20 lines; show the start and end with "..." when doing so.
+   - Never include unrelated large code blocks; when context is long, limit it to the diagnostic itself and collapse the middle with "..." if needed.
 
 4) What to Include vs Ignore (by tool/type)
    A) Test Runners (jest, mocha, vitest, pytest, nose, unittest, go test, rspec, junit, maven-surefire, gradle test)
@@ -106674,6 +106704,7 @@ General Rules
         - Error type/name and message.
         - Top 1-3 stack frames in user code; include "Caused by" chains.
         - Non-zero exit status if visible.
+        - Immediate context like the command that failed, "Traceback" introductions, and leading log lines that explain the failure.
       Ignore:
         - Long internal/framework stacks unless they are the only frames available.
       Example bullet:
@@ -106720,7 +106751,7 @@ General Rules
    - When possible, group by file or rule to reduce noise.
 
 6) Stack Traces
-   - Keep only the topmost relevant frames pointing to project files (e.g., paths under src/, app/, lib/).
+   - Keep the Traceback/exception header and the topmost relevant frames pointing to project files (e.g., paths under src/, app/, lib/); retain tail frames when they convey the ultimate cause.
    - Omit frames from node:internal, <anonymous>, site-packages/dist-packages unless they are the only frames.
 
 7) Timeouts/Resource Failures
@@ -106736,8 +106767,6 @@ General Rules
    - Use short bullets; avoid prose paragraphs.
    - ASCII only; no emojis; no tables.
 
-10) Optional Next Actions
-   - If and only if issues exist, append a short "Next actions:" section with up to 3 bullets of direct, obvious steps derived from the messages (e.g., "Fix missing import in src/foo.ts line 12").
 
 Detection Heuristics (non-exhaustive)
 - Errors: lines containing "error", "ERR!", "E ", "fatal", "Traceback", "Exception", "undefined reference", "cannot find symbol", "not found", "Segmentation fault", "panic:", "stack overflow".
@@ -106759,12 +106788,6 @@ Output Template
   Warnings:
   - <file:line:col> <rule/code>: <short message>
 
-  Notes:
-  - <concise note if indispensable>
-
-  Next actions:
-  - <up to 3 short, concrete steps>
-
 Final Requirements
 - Be concise, avoid repeating the same information.
 - Ensure accuracy; never invent details not present in the input.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polka-codes/cli",
-  "version": "0.9.37",
+  "version": "0.9.38",
   "license": "AGPL-3.0",
   "author": "github@polka.codes",
   "type": "module",