The dashboard stamps its liveness every 5 s; job processes expire leases only while
it serves, and for missing heartbeats only after it served the whole idle window.
After a gap every lease's heartbeat, claim and run start move forward by the gap.
A token's drops count at most once in 10 minutes.
The time limit counts from the first running heartbeat; preparing may last 15 min.
A claim repeated with its request id within 5 minutes gets the same reply (kept in
the dashboard's memory; after a restart the orphaned lease goes back unused).
Ended and requeued leases keep their secret hash, so every lease route answers 410.
ok:false requeues with the next attempt and skips that login; a repeated accepted
submit is accepted again. Cool-off is per login, counts drops and 5 failures in a
row within 30 min, and is cleared by login.