Does poetry install re-resolve dependencies when poetry.lock is present?
Poetry's documented workflow separates resolution from installation: poetry lock resolves the full dependency graph from pyproject.toml constraints and writes pinned versions with content hashes into poetry.lock , while poetry install is expected to read that file directly. The uncertainty is around drift detection. When pyproject.toml is edited without rege