fix(ui-v2): use expected_start_time for dashboard flow runs filtering

[devin-ai-integration]

Closes #18041

Overview

The V2 dashboard was filtering flow runs by start_time and sorting by START_TIME_DESC. This meant scheduled and paused flow runs (which have no start_time yet) were invisible in the dashboard time window. The V1 dashboard correctly uses expected_start_time / EXPECTED_START_TIME_DESC.

This PR switches the V2 dashboard to use expected_start_time for filtering and EXPECTED_START_TIME_DESC for sorting, matching V1 behavior.

Changes

All changes are in ui-v2/:

File	Change
src/routes/dashboard.tsx	buildFlowRunsFilterFromSearch: filter field + sort; loader prefetch sort
src/components/dashboard/flow-runs-card/index.tsx	Filter field (expected_start_time) + sort
src/components/dashboard/flow-runs-accordion/index.tsx	Base filter sort
src/components/dashboard/flow-runs-accordion/flow-runs-accordion-content.tsx	Pagination sort
src/components/dashboard/flow-runs-accordion/flow-runs-accordion-header.tsx	Last-run query sort; timestamp fallback to expected_start_time

Test files updated to match new query keys/filters.

Intentionally unchanged: Task runs card and work pools card remain on start_time (matching V1).

Additional: biome lint fixes

Applied biome useOptionalChain auto-fixes in unrelated files that were flagged by the updated biome 2.4.10 linter in CI. Also corrected indentation in dashboard.tsx from merge conflict resolution.

File	Fix
src/components/deployments/deployment-details-runs-tab.tsx	useOptionalChain
src/components/events/events-line-chart/events-line-chart.tsx	useOptionalChain
src/components/ui/flow-run-activity-bar-graph/index.tsx	useOptionalChain (×2)

Human review checklist

1. Accordion header timestamp fallback — The header now renders lastFlowRun?.start_time ?? lastFlowRun?.expected_start_time. For scheduled/paused runs this will show the expected time rather than nothing, which is an improvement but changes what the timestamp represents. The as string cast on the inner expression is guarded by the outer truthiness check. Verify this is the desired UX.
2. Scope — Confirm work pools card and task runs count filters should stay on start_time.
3. Biome auto-fixes — The useOptionalChain changes are mechanical but touch unrelated files. Verify no subtle behavioral change (e.g., the !data || !data[0] → !data?.[0] rewrite in deployment-details-runs-tab.tsx is safe because data is an array from a query).

Checklist

• This pull request references any related issue by including "closes <link to issue>"
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

Link to Devin session: https://app.devin.ai/sessions/5e605d2779f440d9ba197db2d2498dbd
Requested by: @desertaxle

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 42aa0f2849

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Render header timestamp from expected start when sorting by it

Sorting the header query by EXPECTED_START_TIME_DESC can now select scheduled/paused runs whose start_time is null, but the header only renders a timestamp when lastFlowRun.start_time is present. In the SCHEDULED/PAUSED tab (or any flow whose newest run has not started), this regresses the header to showing no “last run” time even though a run exists. Consider falling back to expected_start_time (or selecting the most recent run with a non-null start_time) so the header remains informative.

Useful? React with 👍 / 👎.

[devin-ai-integration]

Good catch — addressed in a379b12. The header now falls back to expected_start_time when start_time is null, so scheduled/paused runs still show a timestamp.