Poetry network timeout coverage across dependency resolution and installation

Poetry documents config.virtualenvs.create-timeout for virtual environment creation, but that limit does not cover package downloads or dependency resolution. The resolver has no cooperative cancellation API, so SIGINT during resolution can abort ungracefully while leaving poetry.lock unchanged and the virtual environment partially populated. Because [[tool.poetry.source]] has no dedicated timeout key and HTTP timeouts inherit from underlying library defaults, it is unclear whether one configurable limit governs all PyPI network calls in Poetry 1.x.

• Does Poetry 1.x provide one documented timeout that applies to every PyPI request during poetry install or poetry update?
• If not, which network phases are controlled by virtualenvs.create-timeout versus adapter-level defaults?
• Is cleanup of partial downloads or incomplete environments automatic after a timeout or interrupt?