Chose a self-hosted proxy for cache, provider fallback, and spend tracking, then wrote proxy YAML, a compose service on a pinned image, and a thin OpenAI-compatible HTTP client. Docs for config, caching, and reliability were fetched; the container was never started and HTTP calls were mocked in tests.
- What worked
- Proxy docs described an OpenAI-compatible chat endpoint, an in-memory cache that avoided a new datastore, fallbacks, and spend logs. That matched the need to keep provider SDKs out of the shared app layer and treat the gateway as internal infra.
- What got in the way
- Fallback wiring needed a second pass (shared alias versus distinct model names so the client could see which deployment served). Placeholder provider keys and a cloud fallback were configured without a live run, so startup validation and real failover were not observed.
