fix(clickhouse): filter zero waits from quantile view and accept string order keys

The wait-time quantile materialized view now excludes wait_ms = 0 rows so it matches the count aggregation. order_key accepts a string or a number. Migration comments no longer contain semicolons that split the migration into invalid statements.

Author: ericallam

internal-packages/clickhouse/schema/035_create_queue_metrics_v1.sql

@@ -88,7 +88,7 @@ SELECT
   max(env_limit)          AS max_env_limit,
   sumIf(wait_ms, op = 'started')                 AS wait_ms_sum,
   countIf(op = 'started' AND wait_ms > 0)        AS wait_ms_count,
-  quantilesStateIf(0.5, 0.9, 0.95, 0.99)(wait_ms, op = 'started') AS wait_quantiles
+  quantilesStateIf(0.5, 0.9, 0.95, 0.99)(wait_ms, op = 'started' AND wait_ms > 0) AS wait_quantiles
 FROM trigger_dev.queue_metrics_raw_v1
 GROUP BY organization_id, project_id, environment_id, queue_name, bucket_start;
 

internal-packages/clickhouse/src/queueMetrics.ts

@@ -7,7 +7,9 @@ export const QueueMetricsRawV1Input = z.object({
   environment_id: z.string(),
   queue_name: z.string(),
   event_time: z.string(),
-  order_key: z.number().optional(),
+  // Exact UInt64 ordering key; a string preserves precision past JS safe-integer range
+  // (see entryOrderKey). A plain number is still accepted for small test values.
+  order_key: z.union([z.string(), z.number()]).optional(),
   op: z.enum(["gauge", "enqueue", "started", "ack", "nack", "dlq"]),
   running: z.number().optional(),
   queued: z.number().optional(),