Composing Server Functions that call `revalidatePath` with `router.push` in a Client Action leads to the old page (before navigating) being revalidated.

### Link to the code that reproduces this issue https://github.com/schimi-dev/router-push-after-delete-404 ### To Reproduce 1. Start the application in development mode 2. Go to http://localhost:3000 3. Add an item via the "Add Item" form 4. Navigate to the details page of that item via the link 5. Delete the item via the button that says: "Delete with client-side router.push - Bug" ### Current vs. Expected behavior Current behavior: The details page of the item (the page.tsx Server Component) is executed and all queries are refetched, although `router.push` navigates away from that page. Expected behavior: When navigating away from a page via `router.push` in the same Action that calls `revalidatePath`, the old page should not be revalidated. ### Provide environment information ```bash Operating System: Platform: win32 Arch: x64 Version: Windows 11 Pro Available memory (MB): 16113 Available CPU cores: 8 Binaries: Node: 22.12.0 npm: 11.5.1 Yarn: 1.22.19 pnpm: 8.7.0 Relevant Packages: next: 15.5.1-canary.24 // Latest available version is detected (15.5.1-canary.24). eslint-config-next: 15.5.1-canary.24 react: 19.1.0 react-dom: 19.1.0 typescript: 5.9.2 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Server Actions, Linking and Navigating ### Which stage(s) are affected? (Select all that apply) next dev (local), next start (local) ### Additional context _No response_