Interface ConversationLock

All Known Implementing Classes:
InMemoryConversationLock

public interface ConversationLock
Per-conversation distributed lock SPI.

Holder identity (typically "{nodeId}/{thread}/{turnSeq}", see design §7.3) is opaque to the lock; the lock uses it for diagnostics and reentrancy decisions. A ConversationLock.LockHandle carries a monotonically-increasing fencingToken so the manager can detect stale handles when extending or releasing.

Failure semantics (design §10.1):