Fix asyncio warning (#515)

why: pytest-asyncio warns when asyncio_default_fixture_loop_scope is unset in pytester-isolated runs, even when the repo-level pyproject sets it.

what:
- Add asyncio_mode=auto to the generated pytester pytest.ini
- Add asyncio_default_fixture_loop_scope=function to the generated pytester pytest.ini
- Keep test behavior unchanged while removing the deprecation warning

Author: tony

AGENTS.md

@@ -279,7 +279,7 @@ Common commit types:
 
 Examples:
 ```
-cli/add(feat[add_repo]) Add support for custom remote URLs
+cli(add[repo]) Add support for custom remote URLs
 
 why: Enable users to specify alternative remote URLs for repositories
 what:

CHANGES

@@ -33,6 +33,11 @@ $ uvx --from 'vcspull' --prerelease allow vcspull
 _Notes on upcoming releases will be added here_
 <!-- END PLACEHOLDER - ADD NEW CHANGELOG ENTRIES BELOW THIS LINE -->
 
+### Tests
+
+- Fix `pytest-asyncio` deprecation warning in isolated `pytester` runs by
+  setting `asyncio_default_fixture_loop_scope` explicitly (#515)
+
 ## vcspull v1.54.0 (2026-02-08)
 
 ### Breaking changes

tests/test_fixtures.py

@@ -120,6 +120,8 @@ def test_pytester_git_commit_in_isolated_run(
             """
 [pytest]
 addopts=-vv
+asyncio_mode=auto
+asyncio_default_fixture_loop_scope=function
         """.strip(),
         ),
     )