fix(mcp-common): support workflow eventType in observability schema (#361)

Add 'workflow' to the eventType enum and make wallTimeMs/cpuTimeMs
optional on zCloudflareEvent. Cloudflare Workflow events emit
eventType: "workflow" and do not always carry the time fields, so the
workers-observability MCP's query_worker_observability tool was
rejecting any response that contained a workflow event with a Zod
validation error, returning no data to the caller.

Made-with: Cursor

Author: danieltroger

.changeset/fix-workers-observability-workflow-event-type.md

@@ -0,0 +1,9 @@
+---
+'@repo/mcp-common': patch
+---
+
+fix(mcp-common): allow `workflow` `eventType` and treat `wallTimeMs`/`cpuTimeMs` as optional in observability response schema
+
+The Workers Observability response schema (`zCloudflareMiniEvent` / `zCloudflareEvent` in `packages/mcp-common/src/types/workers-logs.types.ts`) was missing `'workflow'` from the `eventType` enum, and `zCloudflareEvent` re-declared `cpuTimeMs` / `wallTimeMs` as required. Cloudflare Workflow events emit `eventType: "workflow"` and do not always include the time fields, so the workers-observability MCP's `query_worker_observability` tool would reject any response containing a workflow event with a Zod validation error and return no data to the caller.
+
+This left the MCP unable to surface logs from any Worker built on Cloudflare Workflows. Adding `'workflow'` to the enum and making the time fields optional unblocks those queries.

packages/mcp-common/src/types/workers-logs.types.ts

@@ -259,6 +259,7 @@ export const zCloudflareMiniEvent = z.object({
 		'tail',
 		'rpc',
 		'websocket',
+		'workflow',
 		'unknown',
 	]),
 	entrypoint: z.string().optional(),
@@ -287,8 +288,8 @@ export const zCloudflareEvent = zCloudflareMiniEvent.extend({
 		)
 		.optional(),
 	dispatchNamespace: z.string().optional(),
-	wallTimeMs: z.number(),
-	cpuTimeMs: z.number(),
+	wallTimeMs: z.number().optional(),
+	cpuTimeMs: z.number().optional(),
 })
 
 const zSourceSchema = z.object({