Usage limit can stop a session mid-operation and leave a half-applied state

Problem

if a usage limit lands in the middle of a multi-step operation - a release, a migration, a large rename - the session stops with the work half applied. some files written, some not. once the session is gone it's often not possible to tell which half you're in.

starting the operation was my call. but humans are fallible and always will be, so the question is whether the provider carries any duty of care at that boundary, or whether it sits entirely with the user.

Context

originally raised as #78480, closed as auto-filed from a session-limit notice. it wasn't auto-filed, so re-filing here so the question can be looked at on its own.

distinct from #90230, which asks for a small continuity allowance after a hard stop. this one is about the stop landing mid-operation in the first place.

Environment

platform: linux
version: 2.1.250