@sweny-ai/core 0.1.95 → 0.1.96

package/dist/cli/verbose-observer.d.ts

@@ -1,19 +1,19 @@
 import type { Observer } from "../types.js";
 /**
- * Create an observer that prints each tool call's input and output to stderr
- * in a human-readable form. Useful when debugging a node that fails or routes
- * unexpectedly — the default human output only shows step transitions,
- * leaving "why" invisible.
+ * Create an observer that prints, on `node:exit`:
+ *   1. Every tool call's input and output (truncated).
+ *   2. The node's structured output (`result.data`) — the payload that
+ *      conditional edges route on. Without this, "validate → notify_halt"
+ *      with no failing checks looks like a paradox; with it, you can see
+ *      that the node emitted `{ status: "fail" }` and root-cause the wrong
+ *      decision.
  *
- * Emission strategy: print the full call list on `node:exit` rather than per
- * `tool:call`/`tool:result` event. The reason: the executor's tool:call and
- * tool:result events fire only for skill-registered tools, not for the
- * Claude Code subprocess's built-in tools (Bash, Read, Edit, etc.). Those
- * built-in tools — the ones agents actually use most — land in
- * `result.toolCalls` only after the node completes. Walking result.toolCalls
- * on node:exit covers both kinds and avoids partial visibility.
+ * Both kinds of tools are covered (skill-registered AND Claude Code's
+ * built-in Bash/Read/Edit/Write), because `result.toolCalls` is populated
+ * after the node completes regardless of how the call was dispatched.
  *
- * Inputs and outputs are truncated; use `--stream` for full untruncated
- * NDJSON.
+ * Truncation defaults to 4000 chars per side. Override with the
+ * `SWENY_VERBOSE_TRUNCATE` env var for ad-hoc debugging. Use `--stream` for
+ * the full untruncated NDJSON.
  */
 export declare function createVerboseToolObserver(): Observer;

package/dist/cli/verbose-observer.js

@@ -1,5 +1,8 @@
 import chalk from "chalk";
-const TRUNCATE = 1200;
+// Default truncation, large enough to fit a 14-item validation checklist JSON
+// without losing the bottom (passed/failed totals). Overridable via env var
+// for ad-hoc debugging when even this isn't enough.
+const TRUNCATE = Number.parseInt(process.env.SWENY_VERBOSE_TRUNCATE ?? "4000", 10) || 4000;
 function truncate(s) {
     return s.length > TRUNCATE
         ? `${s.slice(0, TRUNCATE)}\n      ${chalk.dim(`… [${s.length - TRUNCATE} more chars]`)}`
@@ -29,33 +32,39 @@ function printCall(call) {
     process.stderr.write(`    ${chalk.dim("←")} ${chalk.cyan(call.tool)} ${status}\n`);
     process.stderr.write(`      ${chalk.dim(indent(truncate(fmt(call.output))))}\n`);
 }
+function printData(node, data) {
+    if (!data || Object.keys(data).length === 0)
+        return;
+    process.stderr.write(`    ${chalk.bold.dim(`${node}: output`)}\n`);
+    process.stderr.write(`      ${chalk.dim(indent(truncate(fmt(data))))}\n`);
+}
 /**
- * Create an observer that prints each tool call's input and output to stderr
- * in a human-readable form. Useful when debugging a node that fails or routes
- * unexpectedly — the default human output only shows step transitions,
- * leaving "why" invisible.
+ * Create an observer that prints, on `node:exit`:
+ *   1. Every tool call's input and output (truncated).
+ *   2. The node's structured output (`result.data`) — the payload that
+ *      conditional edges route on. Without this, "validate → notify_halt"
+ *      with no failing checks looks like a paradox; with it, you can see
+ *      that the node emitted `{ status: "fail" }` and root-cause the wrong
+ *      decision.
  *
- * Emission strategy: print the full call list on `node:exit` rather than per
- * `tool:call`/`tool:result` event. The reason: the executor's tool:call and
- * tool:result events fire only for skill-registered tools, not for the
- * Claude Code subprocess's built-in tools (Bash, Read, Edit, etc.). Those
- * built-in tools — the ones agents actually use most — land in
- * `result.toolCalls` only after the node completes. Walking result.toolCalls
- * on node:exit covers both kinds and avoids partial visibility.
+ * Both kinds of tools are covered (skill-registered AND Claude Code's
+ * built-in Bash/Read/Edit/Write), because `result.toolCalls` is populated
+ * after the node completes regardless of how the call was dispatched.
  *
- * Inputs and outputs are truncated; use `--stream` for full untruncated
- * NDJSON.
+ * Truncation defaults to 4000 chars per side. Override with the
+ * `SWENY_VERBOSE_TRUNCATE` env var for ad-hoc debugging. Use `--stream` for
+ * the full untruncated NDJSON.
  */
 export function createVerboseToolObserver() {
     return (event) => {
         if (event.type !== "node:exit")
             return;
         const calls = event.result.toolCalls;
-        if (calls.length === 0)
-            return;
-        process.stderr.write(`    ${chalk.bold.dim(`${event.node}: ${calls.length} tool call${calls.length === 1 ? "" : "s"}`)}\n`);
-        for (const call of calls) {
-            printCall(call);
+        if (calls.length > 0) {
+            process.stderr.write(`    ${chalk.bold.dim(`${event.node}: ${calls.length} tool call${calls.length === 1 ? "" : "s"}`)}\n`);
+            for (const call of calls)
+                printCall(call);
         }
+        printData(event.node, event.result.data);
     };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sweny-ai/core",
-  "version": "0.1.95",
+  "version": "0.1.96",
   "type": "module",
   "bin": {
     "sweny": "./dist/cli/main.js"