chore(ui): rebuild Next.js bundle on rc/1.94.0 so the Cost Optimization page ships

[yuneng-berri]

Relevant issues

Follow-up to #34215, which backported #33810 and #33733 onto rc/1.94.0 but left the Next.js bundle stale.

The proxy serves the prebuilt bundle out of litellm/proxy/_experimental/out/, and nothing in the request path ever runs next build, so the Cost Optimization page and its left-nav entry that #33810 added existed as source on the branch but were absent from what a deployed image actually serves. This rebuilds the bundle on the line so the shipped artifact matches the shipped source.

Built from the tip of rc/1.94.0 (8423efc5fa) with a clean tree and no other changes, via ui/litellm-dashboard/build_release_ui.sh on node v20.20.2, which is the same node version as the previous artifacts commit on this branch. The single commit is the script's own output and is confined entirely to litellm/proxy/_experimental/out/.

Linear ticket

Pre-Submission checklist

• I have added meaningful tests
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review

No tests accompany this because it carries no source changes; it is generated build output, and the tests that cover the underlying feature landed with #34215.

What is included

One commit, chore: update Next.js build artifacts (2026-07-22 02:58 UTC, node v20.20.2), 513 files, all under litellm/proxy/_experimental/out/. Most of it is routine chunk-hash churn from a fresh build. The part that matters is the new route:

litellm/proxy/_experimental/out/cost-optimization/index.html
litellm/proxy/_experimental/out/cost-optimization/index.txt
litellm/proxy/_experimental/out/cost-optimization/__next._tree.txt
...

and the new daily-activity fields compiled into the chunks:

$ grep -oE 'compression_savings_spend|prompt_caching_savings_spend' \
    litellm/proxy/_experimental/out/_next/static/chunks/*.js | head -3
_next/static/chunks/09ohauhq1hwo1.js:compression_savings_spend
_next/static/chunks/09ohauhq1hwo1.js:prompt_caching_savings_spend
_next/static/chunks/09ohauhq1hwo1.js:compression_savings_spend

Neither the route nor those field names existed in the bundle before this commit, which is what confirms the rebuild actually picked up the backported page rather than just reshuffling hashes.

Screenshots / Proof of Fix

To confirm the served bundle, not the dev server, run a proxy off this branch against a database that has the #34215 migrations applied, then:

1. Open http://localhost:4000/ui/ and look for Cost Optimization in the left nav under Observability. On rc/1.94.0 as it stands today that entry is missing, because the bundle predates the page
2. Click it, or go straight to http://localhost:4000/ui/?page=cost-optimization
3. Expect the page to render with a Total saved card, per-driver Compression and Prompt caching cards, a savings-over-time area chart, and a savings-by-driver donut. On a database with no compression or caching activity every figure is zero, which is the correct empty state rather than an error
4. As a served-artifact check that does not depend on the browser, curl -s http://localhost:4000/ui/cost-optimization/index.html | head should return the page rather than a 404

The underlying read path was already exercised live on #34215; a real completion produced total_spend: 0.000135 across 3 requests and /user/daily/activity returned total_compression_saved_tokens, total_compression_savings_spend, and total_prompt_caching_savings_spend. This PR is what makes that data reachable from the dashboard.

Type

🚄 Infrastructure

Changes

Generated build output only. No source, no dependency, and no schema changes.

[greptile-apps]

Too many files changed for review. (513 files found, 100 file limit)