Realtime deadlines need active-phase telemetry and a post-detector abort guard

A realtime request can reach its HTTP deadline while a non-cooperative detector is still settling. In that state, a zero detector duration and zero strategy counts mean no detector result completed before terminal emission, not that the detector never started.

Emit a bounded, forward-only phase timeline with monotonic request-relative offsets, preserving the active phase with a null completion time at timeout. Exclude request IDs, images, decoded data, dimensions, URLs, credentials, and raw errors. Check cancellation immediately after detector completion and after strategy planning so late native completion cannot start more work after the client has already received a deadline response.