Asset-loading error gets swallowed by same-url invariant after `router.push(window.location.href)`

### Link to the code that reproduces this issue https://github.com/zachkirsch/nextjs-asset-loading-error-repro ### To Reproduce 1. `npm install` 1. `npm run dev` 1. Open Google Chrome and go to `localhost:3000` 1. Open the network tab 1. Click the button that says `router.push(window.location.href)` 1. In the network tab, right click on the request labeled `index.json` and click `Block request URL`. (This simulates an asset failing to load) 1. Click the button that says `router.push(window.location.href)` again 1. See error:  Full repro: https://github.com/user-attachments/assets/8c07cd25-8317-4fcb-88bd-53e559717d56 ### Current vs. Expected behavior Expected behavior: an error that `index.json` failed to load Actual behavior: cryptic `Invariant: attempted to hard navigate to the same URL` error ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:29 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6030 Available memory (MB): 36864 Available CPU cores: 11 Binaries: Node: 24.0.1 npm: 11.3.0 Yarn: 1.22.22 pnpm: N/A Relevant Packages: next: 15.4.0-canary.62 // Latest available version is detected (15.4.0-canary.62). eslint-config-next: N/A react: 19.1.0 react-dom: 19.1.0 typescript: 5.8.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Linking and Navigating ### Which stage(s) are affected? (Select all that apply) next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed) ### Additional context `router.push(window.location.href)` is being run as a way to force middleware to re-run: https://github.com/clerk/javascript/blob/45eb6eb2e22e4d424129c5a3f6a7552fd60f4c3f/packages/nextjs/src/pages/ClerkProvider.tsx#L30-L35 Asset-loading failures aren't uncommon for us - since we're self hosted and…