When an unauthenticated user hits a protected route, they are correctly redirected to the sign-in page. However, after signing in, there's no built-in way to send them back to the page they were originally trying to access. Proposal: The protected route mechanism should automatically "remember" the user's intended destination. After the user successfully signs in, the router should check for this stored destination and redirect them back to it. This provides a "redirect with memory" flow, similar to the common ?redirect= search param pattern on the web. While this is possible to build manually with useLocalSearchParams, it feels like a core part of an auth flow that should be integrated directly into the protected routes feature.