<Link> doesn't navigate to the intercepted route in specific scenario

[Neutrlno]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/great-lumiere-lgkkyj

To Reproduce

1. Click link to signin
2. Click "to secondary"
3. Click "back to signin"

Current vs. Expected behavior

Current: On step 3 the only thing that chages is the address bar. If "back to signin" button would be router.push("/signin") router.refresh() it would work as expected.
Expected: navigate to "/signin".

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.3.0-canary.26 // There is a newer canary version (14.3.0-canary.29) available, please upgrade! 
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3

Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

Additional context

Pages Router label added by mistake

_NEXT-3257

[Neutrlno]

closing it as a likely duplicate of the issue above (which is resolved by using [...catchAll] method)

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.