@taico/events 0.2.8 → 0.2.9

package/dist/index.d.ts

@@ -1,4 +1,3 @@
 export * from './types/task-events.js';
 export * from './types/thread-events.js';
-export * from './types/worker-events.js';
 export * from './types/execution-events.js';

package/dist/index.js

@@ -1,4 +1,3 @@
 export * from './types/task-events.js';
 export * from './types/thread-events.js';
-export * from './types/worker-events.js';
 export * from './types/execution-events.js';

package/dist/types/execution-events.d.ts

@@ -20,6 +20,8 @@ export declare const ExecutionWireEvents: {
     readonly EXECUTION_ACTIVITY: "execution.activity";
     readonly EXECUTION_ACTIVITY_POST: "execution.activity.post";
     readonly EXECUTION_HEARTBEAT_POST: "execution.heartbeat.post";
+    readonly WORKER_HEARTBEAT_POST: "worker.heartbeat.post";
+    readonly WORKER_HARNESSES_REPORT_REQUESTED: "worker.harnesses.report.requested";
 };
 export type ExecutionWireEventName = (typeof ExecutionWireEvents)[keyof typeof ExecutionWireEvents];
 /**

package/dist/types/execution-events.js

@@ -19,6 +19,8 @@ export const ExecutionWireEvents = {
     EXECUTION_ACTIVITY: 'execution.activity',
     EXECUTION_ACTIVITY_POST: 'execution.activity.post',
     EXECUTION_HEARTBEAT_POST: 'execution.heartbeat.post',
+    WORKER_HEARTBEAT_POST: 'worker.heartbeat.post',
+    WORKER_HARNESSES_REPORT_REQUESTED: 'worker.harnesses.report.requested',
 };
 /**
  * Type guards for event identification

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taico/events",
-  "version": "0.2.8",
+  "version": "0.2.9",
   "type": "module",
   "private": false,
   "license": "MIT",

package/dist/types/worker-events.d.ts

@@ -1,112 +0,0 @@
-/**
- * Worker Wire Event Types for WebSocket Communication
- *
- * These types define the structure of events sent between backend and workers
- * via WebSocket for the Workers domain. They serve as a contract between the
- * backend gateway and worker clients.
- *
- * Import these types in both backend (for emission/reception) and worker (for emission/reception)
- * to ensure type safety across the wire protocol.
- */
-/**
- * Wire event names for Workers domain
- * These are the stable, external event identifiers sent over the wire protocol.
- */
-export declare const WorkerWireEvents: {
-    readonly WORKER_HELLO: "worker.hello";
-    readonly WORKER_HEARTBEAT: "worker.heartbeat";
-    readonly RUN_STARTED: "run.started";
-    readonly RUN_COMPLETED: "run.completed";
-    readonly RUN_FAILED: "run.failed";
-    readonly RUN_ASSIGNED: "run.assigned";
-    readonly STOP_REQUESTED: "stop.requested";
-};
-export type WorkerWireEventName = (typeof WorkerWireEvents)[keyof typeof WorkerWireEvents];
-/**
- * Worker hello message payload
- * Sent by worker on connection to register itself with metadata
- */
-export interface WorkerHelloPayload {
-    hostname?: string;
-    pid?: number;
-    version?: string;
-    capabilities?: string[];
-}
-/**
- * Worker heartbeat message payload
- * Sent periodically by worker to indicate it's still alive
- */
-export interface WorkerHeartbeatPayload {
-    sessionId: string;
-    timestamp: number;
-}
-/**
- * Run started message payload
- * Sent by worker when it begins executing a task
- */
-export interface RunStartedPayload {
-    executionId: string;
-    sessionId: string;
-    startedAt: string;
-}
-/**
- * Run completed message payload
- * Sent by worker when task execution finishes successfully
- */
-export interface RunCompletedPayload {
-    executionId: string;
-    sessionId: string;
-    completedAt: string;
-}
-/**
- * Run failed message payload
- * Sent by worker when task execution fails
- */
-export interface RunFailedPayload {
-    executionId: string;
-    sessionId: string;
-    failedAt: string;
-    reason?: string;
-}
-/**
- * Run assigned wire event
- * Sent by backend to worker when a task execution is assigned
- */
-export interface RunAssignedWireEvent {
-    executionId: string;
-    taskId: string;
-    agentActorId: string;
-    triggerReason?: string;
-}
-/**
- * Stop requested wire event
- * Sent by backend to worker to request stopping a running execution
- */
-export interface StopRequestedWireEvent {
-    executionId: string;
-    taskId: string;
-    reason?: string;
-}
-/**
- * Worker hello wire event
- * Response sent by backend after successful registration
- */
-export interface WorkerHelloResponse {
-    sessionId: string;
-    serverTime: number;
-}
-/**
- * Worker heartbeat wire event
- * Response sent by backend after processing heartbeat
- */
-export interface WorkerHeartbeatResponse {
-    ok: boolean;
-    serverTime: number;
-}
-/**
- * Generic acknowledgment for run lifecycle events
- */
-export interface RunLifecycleAck {
-    ok: boolean;
-    executionId: string;
-}

package/dist/types/worker-events.js

@@ -1,25 +0,0 @@
-/**
- * Worker Wire Event Types for WebSocket Communication
- *
- * These types define the structure of events sent between backend and workers
- * via WebSocket for the Workers domain. They serve as a contract between the
- * backend gateway and worker clients.
- *
- * Import these types in both backend (for emission/reception) and worker (for emission/reception)
- * to ensure type safety across the wire protocol.
- */
-/**
- * Wire event names for Workers domain
- * These are the stable, external event identifiers sent over the wire protocol.
- */
-export const WorkerWireEvents = {
-    // Worker -> Backend
-    WORKER_HELLO: 'worker.hello',
-    WORKER_HEARTBEAT: 'worker.heartbeat',
-    RUN_STARTED: 'run.started',
-    RUN_COMPLETED: 'run.completed',
-    RUN_FAILED: 'run.failed',
-    // Backend -> Worker
-    RUN_ASSIGNED: 'run.assigned',
-    STOP_REQUESTED: 'stop.requested',
-};