f07ea70de7
The poll loop swallowed every OSError from the lock syscall as contention, so a filesystem that cannot take advisory locks at all (ENOLCK on some network mounts, EMFILE, ...) stalled for the full 60 s deadline and then blamed a peer. Only EWOULDBLOCK/EAGAIN/EACCES/EDEADLK mean "held by someone else"; anything else now raises RefreshFenceTimeout immediately with the real errno. Still fails closed -- the refresh is never POSTed without ownership -- but the failure is diagnosable and instant. The errno set mirrors cron.scheduler._is_lock_contention_errno; it is duplicated rather than imported because importing the scheduler pulls in the whole cron module graph for a four-value tuple.