chore(ci): sync main into internal staging

[yuneng-berri]

TLDR

Problem this solves:

• Main-only hotfix history blocks the staging promotion
• test(e2e): bound the post-/model/new servable wait at 40s #35012 never carried test(e2e): bound the post-/model/new servable wait at 40s #35020 into internal staging

How it solves it:

• Back-merges current main into internal staging
• Reconciles model readiness without adding a second propagation wait

User Flow

Before: a maintainer promoting internal staging is blocked by a branch conflict

1. They open chore(ci): promote internal staging to main #36286
2. GitHub reports conflicts and disables the merge action

After: the same promotion can proceed with main included in staging's ancestry

1. They open chore(ci): promote internal staging to main #36286 after this sync merges
2. GitHub recognizes the synchronized ancestry and allows the promotion to proceed

Relevant issues

Unblocks #36286

Carries #35020 into internal staging, replacing the unmerged staging counterpart #35012

Linear ticket

Pre-Submission checklist

• I have added meaningful tests
• My PR passes all CI/CD checks
• My PR's scope is as isolated as possible
• I have received a Greptile Confidence Score of at least 4/5

Screenshots / Proof of Fix

No screenshots apply to this branch-ancestry repair

At commit 09323fcc4a, the merge parents are current internal staging 4d9defd573 and current main 714fff696a

Validation completed at 09323fcc4a:

make pre-commit
0 errors, 0 warnings, 0 notes
tests/e2e raw HTTP client check passed

Type

Infrastructure

Changes

This back-merges current main into litellm_internal_staging, making the current main head part of staging's ancestry

The E2E harness conflict keeps #35020's 40-second first-listing deadline and per-request timeout. Staging's newer propagation barrier remains responsible for replica convergence, while the older continuous polling window is disabled to avoid waiting twice

QA runbook

• ProxyClient.create_model - model creation keeps the bounded readiness check and waits once for replica propagation
  • Start a multi-replica proxy with STORE_MODEL_IN_DB=True and a reachable database
  • Create a real deployment through /model/new and immediately invoke it through /chat/completions
  • Expect the model creation to return after the configured propagation budget and the invocation to return 200
  • Break model reload and expect model creation to fail near the 40-second first-listing deadline
  • Sanity check: the readiness poll and replica barrier run sequentially without duplicating the propagation wait

Final Attestation

• The tests check the right things, including edge cases, and regressions in the respective real-world use cases are not possible after this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[greptile-apps]

Greptile Summary

This PR reconciles the E2E model-readiness logic while back-merging main into internal staging.

• Adds a bounded, deadline-aware poll for newly created models to appear on the data plane.
• Preserves the separate propagation barrier used for multi-replica convergence.
• Adds per-call GET timeout overrides throughout the shared E2E transport abstraction.

Confidence Score: 5/5

The PR appears safe to merge, with the readiness deadline and transport timeout propagated consistently through all reachable E2E paths.

The changed polling path preserves first-listing validation and the write-relative replica propagation barrier, while every reachable transport implementation supports the new timeout argument.

Important Files Changed

Filename	Overview
tests/e2e/proxy_client.py	Introduces typed model-servability outcomes and bounded polling before the existing propagation barrier; no actionable changed-code defect was established.
tests/e2e/transport.py	Adds an optional GET timeout override consistently across the protocol, split transport, concrete transport, and underlying HTTP call.

_{Reviews (1): Last reviewed commit: "chore(ci): sync main into internal stagi..." | Re-trigger Greptile}