CRITICAL: litellm-community v1.83.14 fork patches never active — Dockerfile patches /app/litellm, proxy imports site-packages #125

Found while debugging #119: docker/litellm-community-spend-fix/v1.83.14/Dockerfile applies the fork patches under /app/litellm/..., but the running proxy imports litellm from /app/.venv/lib/python3.13/site-packages/, which is left unpatched.

Checked read-only on the prod pods (1.83.14-spend-fix.4):

• StatusWithOpenAICode is missing from site-packages, so the #641 code falls back to code "400".
• The spend-update deadlock patch and the SpendLogs surrogate/body patch are also absent from site-packages: 0 matches, against 5 and 1 in /app/litellm.

So none of the community 1.83.14 fork patches have been active, and this very likely goes back to spend-fix.1. The 1.102.1 Dockerfile patches the real site-packages path, which is why litellm-test works.

Fix: patch the site-packages that is actually imported, or pip install the patched tree. Add a build-time guard that imports litellm the way the proxy does and asserts that each patch marker is present, then bump the tag and roll out.

⚠ Rolling this out activates the deadlock and surrogate patches in community for the first time. Rehearse on litellm-test at 1.83.14 or in a canary pod first, and watch the spend writer, DB locks and SpendLogs writes.

🤖 Generated with Claude Code