A state lock prevents two operations from writing the same state at the same time when the backend supports locking. It does not prove that a proposed infrastructure change is safe. Read the lock identity, operation and owner before deciding that it is stale.
A slow or disconnected terminal can still have a running operation elsewhere. Force-unlock is a recovery tool for a verified abandoned lock, and it needs the correct lock identifier. Disabling locking to make a job proceed can create conflicting writes. These scenarios focus on evidence and authority rather than encouraging you to unlock another operator’s active work.
Unlock only after verifying that no active writer owns the lock.