Context — caveats they want you to know

Good for infrequently changing data (theme, locale, auth user id).
Every context change can re-render all consumers — split contexts by update frequency or pass stable values + dispatch (e.g. useReducer pattern).
Not a replacement for Redux/Zustand for high-frequency updates unless structured carefully.