Router.Replace/Push Restores Stale Hash From Initial URL On Dynamic Param Routes

The initial-load call site in create-initial-router-state.ts derives canonicalUrl via createHrefFromUrl(location), which includes location.hash, and passes it to discoverKnownRoute without stripping the hash. In contrast, the navigation call site in navigation.ts explicitly strips the hash before storing. The poisoned cache entry causes segment-cache/navigation.ts to compute canonicalUrl + url.hash (empty string) as the original hashful URL, which is then used in history.replaceState.

1. Clone repro repo and run: npm install && npm run build && npm run start 2. Open http://localhost:3000/p/123#modal in a new tab 3. Click the button that calls router.replace('/p/123', { scroll: false }) 4. Observe URL remains /p/123#modal instead of /p/123

This one-line change makes initial canonical URLs hashless, consistent with the navigation path. Rollback by reverting the line if initial render logic unexpectedly depends on location.hash in canonicalUrl. Ensure test coverage for direct deep links with hashes on dynamic routes and for subsequent same-route hash navigation (hash should still be appended by the navigation site). No concurrency or threading concerns as this is client-side single-threaded code.