Fixed: normalize ContextInfo telemetry in stream equivalence test

The run-event equivalence test compared ContextInfo byte/token counts
verbatim. serdes-ai-agent derives them from the serialized request, and
request part timestamps render with variable-width fractional seconds,
so two otherwise identical streams could differ by a few bytes
(258 vs 261) and fail the assert intermittently. Zero the telemetry in
normalized_events; presence and ordering stay asserted.

Author: Sewer56

src/reloaded-code-serdesai/src/agent_runtime/stream_events.rs

@@ -1567,6 +1567,12 @@ mod tests {
 
     /// Replaces run ids with a placeholder so event sequences from
     /// separate streams compare equal; run ids are random per run.
+    ///
+    /// `ContextInfo` telemetry is zeroed too: the estimate serializes
+    /// wall-clock part timestamps, whose RFC 3339 fractional-second
+    /// width (0/3/6/9 digits) can differ between the two streams, so
+    /// byte counts drift by a few bytes between otherwise identical
+    /// requests.
     fn normalized_events(events: &[RunEvent]) -> Vec<RunEvent> {
         events
             .iter()
@@ -1578,6 +1584,11 @@ mod tests {
                     run_id: "<run>".into(),
                     messages: messages.clone(),
                 },
+                RunEvent::ContextInfo { context_limit, .. } => RunEvent::ContextInfo {
+                    estimated_tokens: 0,
+                    request_bytes: 0,
+                    context_limit: *context_limit,
+                },
                 other => other.clone(),
             })
             .collect()