Status: IN
Fencing tokens provide linearizable write protection at the resource server: stale tokens are permanently rejected (no expiration) and the monotonic token ordering ensures only the most recent lock holder can successfully write.
Server-side fencing is correct but clients retain and use tokens after lock expiry with no invalidation signal
Depends on (SL): fencing-rejects-stale-writes, fencing-tokens-do-not-expire-at-resource-server