Route groups share a layout, not a state boundary - that's the trap. The cleanest fix in production: lift state to a root layout provider scoped above the route group, or use Zustand with a slice tied to that layout segment. Context inside the group causes remounts on navigation.