“Expiry changes the coordinator's view of authority; it does not physically stop the process.”

Not coding-specific (examples are webhooks, shipments), so lower evidence weight, but it names the failure that file-lock and lease tools for coding agents (symlock, Agentlocks, Concord) have to answer: a paused agent can wake after its lease is reassigned and still land its change. The proposed remedy is a fencing check at the point of acceptance (reject writes from a stale generation), not a better lock. Also: 'The model should not decide whether it owns the task from a conversational message. The durable claim result is the authority.' Worth testing whether any of the coding-agent lock tools implement generation checks on write.