Dev server randomly doesn't trigger refresh

Link to the code that reproduces this issue

https://github.com/nmoreaud/next-dev-server-refresh-bug

To Reproduce

pnpm create next-app@latest testnext --yes
cd testnext
pnpm approve-builds
pnpm run dev

Edit global.css, add:

h1 {
  color: #2aaaaa;
}

Then open http://localhost:3000/ in a web browser, and modify the h1 color a few times in global.css.
Approximately once every three modification, the display isn't updated, and the line "✓ Compiled in XXms" doesn't appear in the terminal.

Current vs. Expected behavior

The web browser display isn't up to date, and F5 doesn't fix the problem.
If I stop the dev server and restart it, the modification is taken into account.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 16338
  Available CPU cores: 4
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.22.0
Relevant Packages:
  next: 16.0.2-canary.24 // Latest available version is detected (16.0.2-canary.24).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Turbopack

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

next dev (local)

Additional context

Same pb with Firefox and Chrome.

Very hard to reproduce with npx create-next-app -e reproduction-template, though it happened once.

Start with the linked reproduction repository and run the provided pnpm create-next-app and next dev steps on Windows. Repeatedly edit global.css while Turbopack is active, then confirm that every change triggers compilation and updates the browser without restarting the server.