When running mkdocs serve, changes in the documentation files are not automatically reloaded in the browser unless the --livereload flag is explicitly passed.

In previous versions, or as documented, mkdocs serve should enable livereload by default.
Currently, it only works if I run:
mkdocs serve --livereload
Without that flag, the local server runs correctly but does not detect or reload changes automatically.

Steps to reproduce:
Run mkdocs serve in a standard MkDocs project.
Modify any .md file in the docs/ folder.
Observe that the browser does not refresh.

Run the same command with:
mkdocs serve --livereload
Now live reload works as expected.

Expected behavior:
mkdocs serve should enable live reload by default (without requiring the --livereload argument), or documentation should clarify if this default behavior has changed intentionally.

Impact on tests:
This issue also causes automated tests and CI pipelines that rely on the default livereload behavior to fail or hang, because the reload server is not triggered unless the flag is explicitly provided.
This leads to inconsistent test behavior across environments that expect the default live-reload to be active