devin-ai-integration[bot] 57bead9842 test(e2e): pin end-user and tag attribution from Codex-style headers on /v1/responses (#43093) ... * test(e2e): pin end-user and tag attribution from Codex-style headers on /v1/responses Codex CLI has no body field for the end user, so its config.toml http_headers attach x-litellm-customer-id or x-litellm-end-user-id plus x-litellm-tags to every /v1/responses call. The proxy already honors those headers on the Responses route, but nothing in the e2e stack pinned it. The new case sends that exact wire shape with each standard customer header and fails unless the spend row carries the end user, the tags, the aresponses call type, and a nonzero cost. * test(e2e): assert the customer's /customer/info total matches the header-attributed Responses row --------- Co-authored-by: mateo-berri <277851410+mateo-berri@users.noreply.github.com>		2026-09-24 18:33:49 -07:00
..
budgets	test: expect 422 for budget refusals in unification, e2e and integration suites	2026-09-20 06:33:57 +00:00
ratelimit	fix(proxy): share model rate-limit buckets between a model_group_alias and its target (#42516)	2026-09-22 13:31:58 -07:00
spend_tracking	test(e2e): pin end-user and tag attribution from Codex-style headers on /v1/responses (#43093)	2026-09-24 18:33:49 -07:00