When fetching updated runs since the last fetch cycle, the /runs API will fetch the run matching the "since" parameter, not just ones after that. This means extra data is sent every time, extra CPU/network hit.

Trivial change here: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/JobExt.java#L121

The catch is we need to ensure tests handle this correctly, and the UI does too. Possible issues of API compat, but I think likely safe.