Drop a navigation guard that never fired

It compared a copy of a parameter against the parameter it was copied from,
so the condition was never true. Its job — keeping a superseded navigation
from acting on its own props — is done by the ABANDONED response instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: pleek91

src/services/createRouter.ts

@@ -165,7 +165,7 @@ export function createRouter<
     }
 
     if (!isExternal(url)) {
-      setPropsAndUpdateRoute(navigationId, to, from)
+      setPropsAndUpdateRoute(to, from)
     }
 
     const afterResponse = await hooks.runAfterRouteHooks({ to, from })
@@ -192,15 +192,9 @@ export function createRouter<
     history.startListening()
   }
 
-  function setPropsAndUpdateRoute(navigationId: string, to: ResolvedRoute, from: ResolvedRoute | null): void {
-    const currentNavigationId = navigationId
-
+  function setPropsAndUpdateRoute(to: ResolvedRoute, from: ResolvedRoute | null): void {
     propStore.setProps(to)
       .then((response) => {
-        if (currentNavigationId !== navigationId) {
-          return
-        }
-
         switch (response.status) {
           case 'SUCCESS':
           case 'ABANDONED':