Server Action hangs when called via setTimeout immediately after router.push in next dev mode

### Link to the code that reproduces this issue https://codesandbox.io/p/devbox/awesome-bird-yzvqtv ### To Reproduce There is an issue where a Server Action’s Promise does not resolve when called shortly after a navigation event. 1. Start the application in development (next dev) 2. Navigate to /page2 from /page1 via `Link` 3. In /page2, a ClientComponent runs router.push("?asdf") inside useEffect 4. Immediately after, it invokes a Server Action(`getServerNow`) via setTimeout(..., 0) 5. The Server Action promise never resolves or rejects (in dev mode) ✅ Increasing the setTimeout delay (e.g., to 1000ms) allows the Server Action to resolve normally. ✅ This issue does not occur in production builds. ### Current vs. Expected behavior Expected: The Server Action should resolve (or reject) properly even when invoked via setTimeout(..., 0) after router.push(). Actual (in next dev): The Promise from the Server Action hangs—then() or catch() are never called. ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023 Available memory (MB): 4242 Available CPU cores: 2 Binaries: Node: 20.9.0 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.10.2 Relevant Packages: next: 15.4.0-canary.28 // Latest available version is detected (15.4.0-canary.28). eslint-config-next: N/A react: 19.1.0 react-dom: 19.1.0 typescript: 5.3.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Server Actions ### Which stage(s) are affected? (Select all that apply) next dev (local) ### Additional context This issue only occurs in next dev mode. It does not occur after next build && next start.