Let a pinned minute read runs from the whole day

/observability/runs gains since/until, so the throughput chart's pin asks
the server for its minute instead of filtering a fixed recent list. This
engine writes ~60 runs a minute, so any minute but the newest read empty.

since is inclusive and until exclusive, matching the minute buckets the
charts are drawn from. Hover stays the client-side preview it was:
scrubbing a day would otherwise be a request per minute rested on.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017MeiWk3Yq12n2pTvnQWYvt

frontend/src/client/sdk.gen.ts

@@ -1147,9 +1147,14 @@ export class ObservabilityService {
     /**
      * Read Runs
      * Recent cascades, newest first.
+     *
+     * ``since`` is inclusive and ``until`` exclusive, so a window of one minute
+     * holds exactly the runs of the minute bucket the charts are drawn from.
      * @param data The data for the request.
      * @param data.flow
      * @param data.status
+     * @param data.since
+     * @param data.until
      * @param data.limit
      * @returns RunRow Successful Response
      * @throws ApiError
@@ -1161,6 +1166,8 @@ export class ObservabilityService {
             query: {
                 flow: data.flow,
                 status: data.status,
+                since: data.since,
+                until: data.until,
                 limit: data.limit
             },
             errors: {

frontend/src/client/types.gen.ts

@@ -1072,7 +1072,9 @@ export type ObservabilityReadFlowRollupsResponse = (Array<FlowRollup>);
 export type ObservabilityReadRunsData = {
     flow?: (string | null);
     limit?: number;
+    since?: (string | null);
     status?: (string | null);
+    until?: (string | null);
 };
 
 export type ObservabilityReadRunsResponse = (Array<RunRow>);