The offline-first flow in that sequence diagram is the nice part — serving cached assets immediately while the GET to /assets happens in the background, then writing fresh data back to the cache. Curious why DioApiClient gets separate default/prod interceptors — different auth or logging per environment?