v0.5.3

Streams no longer skew response times.

Changed: a streaming response counts as traffic, not as a duration

When rollups are on, every request's wall time (PHP start to shutdown) feeds the console's duration histograms. A server-sent-events response (Content-Type: text/event-stream) is held open for as long as the browser listens, so its wall time measured the subscription rather than the work — every stream landed in the slowest bucket, and a single SSE endpoint could own the site's average response time in the console's STATS and PERFORMANCE views.

Such a response now still counts as a request — status, method, route and logged-in split are unchanged — but contributes no duration. Detection is the media type the response declares (any case, with or without a charset), so nothing needs configuring. Sites without SSE endpoints see no difference.

The same rule ships in every ovos/console sender (php-library, the CMS senders, the node client). The bundled console-client.js is unchanged in this release.