@hyperdrive.bot/paseo-protocol 0.3.73 → 0.3.74

package/dist/agent-labels.d.ts

@@ -3,6 +3,8 @@ export declare const WORKFLOW_ID_LABEL = "paseo.workflow-id";
 export declare const WORKFLOW_TASK_ID_LABEL = "paseo.workflow-task-id";
 export declare const LOOP_NAME_LABEL = "loop";
 export declare const LOOP_RUN_LABEL = "run";
+export declare const SCHEDULE_ID_LABEL = "paseo.schedule-id";
+export declare const SCHEDULE_RUN_LABEL = "paseo.schedule-run";
 export interface AgentLabelSource {
     labels?: Record<string, unknown> | null;
 }
@@ -23,4 +25,31 @@ export declare function isLoopAgent(agent: AgentLabelSource): boolean;
  * whole HITL story dies. See docs/loops.md.
  */
 export declare function isLoopExecutionAgent(agent: AgentLabelSource): boolean;
+export declare function getScheduleIdFromLabels(labels: Record<string, unknown> | null | undefined): string | null;
+export declare function getScheduleRunFromLabels(labels: Record<string, unknown> | null | undefined): string | null;
+/** Any agent a schedule fired. */
+export declare function isScheduleAgent(agent: AgentLabelSource): boolean;
+/**
+ * A scheduled execution, the set the general session surfaces hide.
+ *
+ * KNOWN LIMIT, stated rather than papered over: schedules have NO adoption escape hatch,
+ * so a scheduled run a human takes over stays hidden. A second adoption mechanism was
+ * deliberately not built, because the loop one (LOOP_ADOPTED_AT_LABEL) is defined and read
+ * but written NOWHERE - shipping a second unwritten escape hatch would double the dead
+ * code, not halve the problem. Wire one adoption path for both, then use it here.
+ */
+export declare function isScheduleExecutionAgent(agent: AgentLabelSource): boolean;
+/**
+ * Anything the machine spawned on its own and no human is waiting inside: a loop tick or
+ * a scheduled firing. This is what the general session surfaces hide.
+ *
+ * Prefer this over `isLoopExecutionAgent` in any LIST filter. Keying on loops alone is the
+ * exact bug this replaced: a new kind of machine agent silently reads as human work, and
+ * the failure is invisible because "more sessions" looks like activity, not a defect.
+ *
+ * Hiding remains a LIST concern only. Attention surfaces (favicon, background activity,
+ * push) must keep counting these, or an automated run blocked on a permission goes silent.
+ * See docs/loops.md.
+ */
+export declare function isMachineExecutionAgent(agent: AgentLabelSource): boolean;
 //# sourceMappingURL=agent-labels.d.ts.map

package/dist/agent-labels.js

@@ -17,6 +17,20 @@ export const WORKFLOW_TASK_ID_LABEL = "paseo.workflow-task-id";
 // tooling/loops/lib/run-agent.sh (`paseo agent run --label loop=<name> --label run=<ts>`).
 export const LOOP_NAME_LABEL = "loop";
 export const LOOP_RUN_LABEL = "run";
+// Scheduled runs (paseo schedules: cron/interval prompts the daemon fires on its own).
+// A scheduled execution carries paseo.schedule-id for the owning schedule and
+// paseo.schedule-run for the individual firing. Producer: the daemon's scheduler, not a
+// human and not a loop.
+//
+// These were invisible to every list filter until 2026-08-29, because the filters keyed
+// on `loop` alone and a scheduled run carries no `loop` label. Measured on one box over
+// two days: 882 scheduled runs (517 Sentry incident-responder, 222 fleet watcher, 128 a
+// WhatsApp poller) sat in Sessions indistinguishable from human work, against 125 loop
+// runs correctly hidden. The gap was predicted in docs when the loop filter shipped -
+// "any count keyed on `loop` alone will silently fold them into human work" - and it was
+// 9 rows then, 517 now.
+export const SCHEDULE_ID_LABEL = "paseo.schedule-id";
+export const SCHEDULE_RUN_LABEL = "paseo.schedule-run";
 export function getParentAgentIdFromLabels(labels) {
     const parentAgentId = labels?.[PARENT_AGENT_ID_LABEL];
     return typeof parentAgentId === "string" && parentAgentId.trim().length > 0
@@ -62,4 +76,43 @@ export function isLoopAgent(agent) {
 export function isLoopExecutionAgent(agent) {
     return isLoopAgent(agent) && getLoopAdoptedAtFromLabels(agent.labels) === null;
 }
+export function getScheduleIdFromLabels(labels) {
+    const scheduleId = labels?.[SCHEDULE_ID_LABEL];
+    return typeof scheduleId === "string" && scheduleId.trim().length > 0 ? scheduleId.trim() : null;
+}
+export function getScheduleRunFromLabels(labels) {
+    const run = labels?.[SCHEDULE_RUN_LABEL];
+    return typeof run === "string" && run.trim().length > 0 ? run.trim() : null;
+}
+/** Any agent a schedule fired. */
+export function isScheduleAgent(agent) {
+    return getScheduleIdFromLabels(agent.labels) !== null;
+}
+/**
+ * A scheduled execution, the set the general session surfaces hide.
+ *
+ * KNOWN LIMIT, stated rather than papered over: schedules have NO adoption escape hatch,
+ * so a scheduled run a human takes over stays hidden. A second adoption mechanism was
+ * deliberately not built, because the loop one (LOOP_ADOPTED_AT_LABEL) is defined and read
+ * but written NOWHERE - shipping a second unwritten escape hatch would double the dead
+ * code, not halve the problem. Wire one adoption path for both, then use it here.
+ */
+export function isScheduleExecutionAgent(agent) {
+    return isScheduleAgent(agent);
+}
+/**
+ * Anything the machine spawned on its own and no human is waiting inside: a loop tick or
+ * a scheduled firing. This is what the general session surfaces hide.
+ *
+ * Prefer this over `isLoopExecutionAgent` in any LIST filter. Keying on loops alone is the
+ * exact bug this replaced: a new kind of machine agent silently reads as human work, and
+ * the failure is invisible because "more sessions" looks like activity, not a defect.
+ *
+ * Hiding remains a LIST concern only. Attention surfaces (favicon, background activity,
+ * push) must keep counting these, or an automated run blocked on a permission goes silent.
+ * See docs/loops.md.
+ */
+export function isMachineExecutionAgent(agent) {
+    return isLoopExecutionAgent(agent) || isScheduleExecutionAgent(agent);
+}
 //# sourceMappingURL=agent-labels.js.map

package/dist/generated/validation/ws-outbound.aot.js

@@ -53073,6 +53073,11 @@ export const WSOutboundMessageSchema = /* @__PURE__ */ (() => {
                                                     }
                                                 }
                                             }
+                                            if (__o_3505["adopted"] !== undefined) {
+                                                if (typeof __o_3505["adopted"] !== "boolean") {
+                                                    _e.push({ code: "invalid_type", expected: "boolean", input: __o_3505["adopted"], path: ["message"].concat("payload").concat("adopted") });
+                                                }
+                                            }
                                             if (__o_3505["error"] !== undefined) {
                                                 if (typeof __o_3505["error"] !== "string") {
                                                     _e.push({ code: "invalid_type", expected: "string", input: __o_3505["error"], path: ["message"].concat("payload").concat("error") });

package/dist/messages.d.ts

@@ -3659,6 +3659,7 @@ export declare const EditMessageResponseMessageSchema: z.ZodObject<{
         agentId: z.ZodString;
         newSessionId: z.ZodOptional<z.ZodString>;
         linesCopied: z.ZodOptional<z.ZodNumber>;
+        adopted: z.ZodOptional<z.ZodBoolean>;
         error: z.ZodOptional<z.ZodString>;
         errorCode: z.ZodOptional<z.ZodString>;
     }, z.core.$strip>;
@@ -21919,6 +21920,7 @@ export declare const SessionOutboundMessageSchema: z.ZodDiscriminatedUnion<[z.Zo
         agentId: z.ZodString;
         newSessionId: z.ZodOptional<z.ZodString>;
         linesCopied: z.ZodOptional<z.ZodNumber>;
+        adopted: z.ZodOptional<z.ZodBoolean>;
         error: z.ZodOptional<z.ZodString>;
         errorCode: z.ZodOptional<z.ZodString>;
     }, z.core.$strip>;
@@ -32441,6 +32443,7 @@ export declare const WSSessionOutboundSchema: z.ZodObject<{
             agentId: z.ZodString;
             newSessionId: z.ZodOptional<z.ZodString>;
             linesCopied: z.ZodOptional<z.ZodNumber>;
+            adopted: z.ZodOptional<z.ZodBoolean>;
             error: z.ZodOptional<z.ZodString>;
             errorCode: z.ZodOptional<z.ZodString>;
         }, z.core.$strip>;
@@ -42621,6 +42624,7 @@ export declare const WSOutboundMessageSchema: z.ZodDiscriminatedUnion<[z.ZodObje
             agentId: z.ZodString;
             newSessionId: z.ZodOptional<z.ZodString>;
             linesCopied: z.ZodOptional<z.ZodNumber>;
+            adopted: z.ZodOptional<z.ZodBoolean>;
             error: z.ZodOptional<z.ZodString>;
             errorCode: z.ZodOptional<z.ZodString>;
         }, z.core.$strip>;

package/dist/messages.js

@@ -2536,6 +2536,12 @@ export const EditMessageResponseMessageSchema = z.object({
         agentId: z.string(),
         newSessionId: z.string().optional(),
         linesCopied: z.number().int().nonnegative().optional(),
+        /**
+         * True when the daemon repointed THIS agent at the forked transcript, so the client
+         * should rewind in place. False means the fork exists but the agent still runs the old
+         * session, and the client must not pretend the conversation moved.
+         */
+        adopted: z.boolean().optional(),
         error: z.string().optional(),
         errorCode: z.string().optional(),
     }),

package/dist/validation/ws-outbound-schema-metadata.d.ts

@@ -8019,6 +8019,7 @@ export declare const WSOutboundMessageSchema: {
                 agentId: import("zod").ZodString;
                 newSessionId: import("zod").ZodOptional<import("zod").ZodString>;
                 linesCopied: import("zod").ZodOptional<import("zod").ZodNumber>;
+                adopted: import("zod").ZodOptional<import("zod").ZodBoolean>;
                 error: import("zod").ZodOptional<import("zod").ZodString>;
                 errorCode: import("zod").ZodOptional<import("zod").ZodString>;
             }, import("zod/v4/core").$strip>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperdrive.bot/paseo-protocol",
-  "version": "0.3.73",
+  "version": "0.3.74",
   "description": "Paseo shared protocol schemas and wire types",
   "files": [
     "dist",