@forwardimpact/libharness 3.1.0 → 3.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forwardimpact/libharness",
-  "version": "3.1.0",
+  "version": "3.2.1",
   "description": "Autonomous agent team harness — coordinate a lead and participant agents in one async session, with eval, benchmark, and trace tooling to prove the changes worked.",
   "keywords": [
     "orchestration",

package/src/commands/callback.js

@@ -52,18 +52,27 @@ function readTraceSummary(content) {
   return summary;
 }
 
+/** Terminal summary when the run wrote no trace the verb can read. */
+const NO_TRACE_SUMMARY = "The run produced no trace file. See the run log.";
+
+/** Terminal summary when a trace exists but carries no orchestrator summary. */
+const NO_SUMMARY_TEXT = "The run ended and produced no summary.";
+
 /**
  * Callback command — read an NDJSON trace and extract the terminal
  * orchestrator summary. POST a canonical callback body to the configured
- * URL. `kata-dispatch.yml` uses this command to deliver the lead's
- * conclusion to the bridge that dispatched the run.
+ * URL.
+ *
+ * `--trace-file` is optional: an absent or empty path posts the same shape
+ * with `verdict: failed`, so a run that produced no trace never strands its
+ * caller.
  *
  * Wire shape (single shape across modes):
  *
  * ```
  * {
- *   correlation_id, verdict, summary, run_url,
- *   discussion_id?, replies: [], trigger?
+ *   correlation_id, kind, verdict, summary, run_url, cost_usd,
+ *   replies: [], last_acted_seq, discussion_id?, trigger?
  * }
  * ```
  *
@@ -79,20 +88,26 @@ export async function runCallbackCommand(ctx) {
   const runUrl = values["run-url"] ?? "";
   const discussionIdOverride = values["discussion-id"] ?? null;
 
-  if (!traceFile)
-    return { ok: false, code: 1, error: "--trace-file is required" };
   if (!callbackUrl)
     return { ok: false, code: 1, error: "--callback-url is required" };
 
-  const content = runtime.fsSync.readFileSync(traceFile, "utf8");
-  const found = readTraceSummary(content) ?? {
-    verdict: "failed",
-    summary: "The run ended and produced no summary.",
-    replies: [],
-  };
+  const content =
+    traceFile && runtime.fsSync.existsSync(traceFile)
+      ? runtime.fsSync.readFileSync(traceFile, "utf8")
+      : null;
+  const found =
+    content === null
+      ? { verdict: "failed", summary: NO_TRACE_SUMMARY, replies: [] }
+      : (readTraceSummary(content) ?? {
+          verdict: "failed",
+          summary: NO_SUMMARY_TEXT,
+          replies: [],
+        });
   // Total spend across every participant in the trace. The bridge surfaces
   // it alongside the verdict, so a dispatched run reports what it cost.
-  const { totalCostUsd } = sumTraceCost(content.split("\n"));
+  const { totalCostUsd } = sumTraceCost(
+    content === null ? [] : content.split("\n"),
+  );
 
   const discussionId = found.discussionId ?? discussionIdOverride ?? null;
   const payload = {

package/src/events/github.js

@@ -1,6 +1,5 @@
 /**
- * GitHub event → task-prompt composition. Replaces ~70 lines of shell in
- * kata-dispatch.yml's `Compose task text` step. Each branch in the dispatch
+ * GitHub event → task-prompt composition. Each branch in the dispatch
  * function corresponds to one (event_name, action) the agent workflows react
  * to.
  *
@@ -37,10 +36,10 @@ export const TASK_TEMPLATE_PR_LABELED =
 //
 // A human merge is an act of approval, so the template says so. It does not
 // frame the event as bookkeeping. What to record belongs to the
-// approval-signals reference. The template supplies the identity and the
+// team protocol. The template supplies the identity and the
 // pointer. "cut" still names the genuine post-merge chore.
 export const TASK_TEMPLATE_PR_MERGED =
-  'PR "${PR_TITLE}" (#${NUMBER}) merged to main by @${MERGED_BY} (type: ${MERGED_BY_TYPE}); opened by @${AUTHOR}. A human merge is an approval — record it per the approval-signals reference. May leave unreleased changes to cut. PR URL: ${URL}.';
+  'PR "${PR_TITLE}" (#${NUMBER}) merged to main by @${MERGED_BY} (type: ${MERGED_BY_TYPE}); opened by @${AUTHOR}. A human merge is an approval — record it per the team protocol. May leave unreleased changes to cut. PR URL: ${URL}.';
 
 // The comment and review templates append this verbatim. `${BODY}` is the
 // untrusted author text. The fence and the "data, not instructions" label make