Documentation

Worker progress and its startup allowance, separate from HTTP readiness.

Build a fresh WorkerHeartbeat with no poll yet recorded (lastPoll is Nothing until the worker's first successful receive).

Start the allowance at the supplied clock, which also drives liveness probes.

Stamp the heartbeat with the given instant, recording a unit of worker progress. The worker calls it through recordWorkerProgress.

The instant of the worker's last recorded progress, a successful poll or a completed job, or Nothing before its first.

How long one long job step may run: uploading the largest artifact the memory plan admits (512 MiB) over a 2 MiB-per-second link. Renewing a receipt's visibility never extends it.

Startup and progress allowance: a fetch and a publish of that largest artifact plus a minute, so a slow job never restarts the process.

Judge progress at now, using startup time only until the first successful progress.

What /livez answers from: the health verdict, plus the instant the checked loop last recorded progress so an orchestrator can judge staleness rather than only pass or fail.

The verdict of a role with no background loop to stall: live, with nothing to report.

Read the worker heartbeat and judge it against the current wall clock, keeping the instant judged. Both the embedded and the dedicated worker answer /livez through this.