Update Translations Without Redeploying: Runtime Loading, Caching, and Why Users See Stale Strings

How to change the text of a web or mobile app without shipping a new release: load translations at runtime instead of bundling them, and understand the caches (browser, service worker, localStorage, CDN) that decide when users actually see the change. Covers i18next backends, Cache-Control, the usual reasons translations do not update after a deploy, and when bundling is still the right call.