@kangentic/protocol 0.21.0 → 0.22.0

package/dist/events/payloads.d.ts

@@ -182,9 +182,10 @@ export interface SessionUsageWire {
  * task, which is what makes it meaningful for a completed one: a task worked
  * across five `--resume` legs has five session rows, and reporting only the
  * final leg would under-report everything. The desktop's getSummaryForTask
- * owns those aggregation rules (SUM cost/duration/tool calls/lines, MAX files
- * changed, and tokens taken as the latest row per session lineage so a
- * resumed session is not double-counted) - they are not re-derived here.
+ * owns those aggregation rules - they are not re-derived here. Cost, duration
+ * and tokens are each conversation's cumulative reading, so they count once per
+ * session lineage and add across lineages; tool calls and lines SUM; files
+ * changed takes the MAX.
  *
  * `sessionId` is the transcript ANCHOR, not a live session: it resolves
  * through the desktop's session records, which outlive the agent, so it reads
@@ -465,6 +466,34 @@ export interface BoardTaskWire {
      * key from every real wire response.
      */
     pausable?: boolean | null;
+    /**
+     * True when column automations are off for this task: no On task enter, On
+     * agent turn end or On task exit row runs for it in any column, and a move
+     * types no column message. Column settings, a hand's moves and the task's own
+     * first command are untouched. It is the fact the desktop card's "Automations
+     * disabled" strip reads, and the desktop menu's Enable or Disable automations
+     * row flips it.
+     *
+     * There is no verb for it. A phone flips it with the `board-tool-write`
+     * `update_task` call, whose param is camelCase: `automationsDisabled: true`
+     * or `false`, never `automations_disabled`. A workflow task always reads
+     * false, because its workflow's Pause holds it, and `update_task` refuses
+     * `true` for one. Hide the control while `workflow` is non-null, as the
+     * desktop menu does.
+     *
+     * The desktop also clears it by itself: when the task leaves Done (a rollback
+     * of a failed move excepted), when it is restored from the archive, and when
+     * it joins a workflow. Every change, by any hand, reaches the phone as a
+     * `task-updated` board event, after which the next snapshot carries the new
+     * value.
+     *
+     * Null or absent means a desktop that predates the field (pre-0.22.0). A
+     * client offers no control then, since it cannot read the switch's state.
+     *
+     * Declared OPTIONAL (`?`) like `pausable`; `parseBoardTaskWire` populates the
+     * key from every real wire response.
+     */
+    automations_disabled?: boolean | null;
     /**
      * The workflow the task belongs to (a set of linked tasks that runs through
      * its boards by itself), or null for an ordinary task. Absent from desktops

package/dist/index.cjs

@@ -5511,6 +5511,7 @@ function parseBoardTaskWire(value) {
     resumable: nullableBoolean(value, "resumable"),
     paused: nullableBoolean(value, "paused"),
     pausable: nullableBoolean(value, "pausable"),
+    automations_disabled: nullableBoolean(value, "automations_disabled"),
     workflow: parseBoardTaskWorkflowWire(value.workflow)
   };
 }

package/dist/index.mjs

@@ -5371,6 +5371,7 @@ function parseBoardTaskWire(value) {
     resumable: nullableBoolean(value, "resumable"),
     paused: nullableBoolean(value, "paused"),
     pausable: nullableBoolean(value, "pausable"),
+    automations_disabled: nullableBoolean(value, "automations_disabled"),
     workflow: parseBoardTaskWorkflowWire(value.workflow)
   };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kangentic/protocol",
-  "version": "0.21.0",
+  "version": "0.22.0",
   "description": "Kangentic mobile bridge wire protocol: framing, Noise-based pairing and session handshakes, signed device roster, and capability verbs shared between desktop and mobile.",
   "main": "dist/index.cjs",
   "module": "dist/index.mjs",