Durably pause the workflow for delta under the stable name userStep. On the first encounter this arms a deterministic keiro_timers row and suspends the run; the suspension resolves when a timer worker fires the row (see workflowSleepFireAction) and journals the sleep's completion, after which a later run replays past the sleep without re-arming.

The arming action is idempotent (a resumed workflow re-runs it until the sleep resolves): it inserts with a deterministic sleepTimerId only when the row is absent, so the first fire_at persists across every resume pass.

Durably pause the workflow for delta under an ordinal name (the Nth sleep in a run becomes sleep:N). Convenient but its determinism is conditional — see the module header. Prefer sleepNamed for anything that must survive a code change mid-flight.

The fire action for workflow-sleep timers. For a TimerRow whose payload is a workflow-sleep discriminator, reconstruct the workflow identity from the row's processManagerName (= workflow name) and correlationId (= workflow id), resolve the generation that armed the timer, append a StepRecorded completion (result = null) to that generation's journal, and return the deterministic EventId so the worker marks the timer Fired. Returns Nothing for a row whose payload is not a workflow sleep, or for a sleep owned by a terminal workflow (whose timer is cancelled), so a mixed worker can delegate that row to its process-manager fire action.

Idempotent: prepareJournalAppend pre-checks the generation-scoped step and the event id is deterministic, so at-least-once timer firing yields exactly-once journaling even after the workflow has rotated.

A timer worker pass that handles both workflow-sleep timers and ordinary process-manager timers. For each claimed timer: if its payload is a workflow sleep, wake the workflow; otherwise delegate to the supplied process-manager fire action.

A deployment that runs only workflows can pass \_ -> pure Nothing as the fallback (or use workflowSleepFireAction directly with runTimerWorker). A deployment that mixes process-manager timers and workflow sleeps passes its existing PM fire action so one worker drains both kinds.

runWorkflowTimerWorker over a whole batch: drain up to limit due timers in one pass, routing each to the workflow-sleep fire action or the supplied process-manager fallback exactly as the single-claim worker does.

This is what a deployment wants when many sleeps come due together. The single-claim worker drains a backlog of K due sleeps at one per poll tick, so the last sleeping workflow waits K ticks to wake; one drain pass with a large enough limit wakes them all. Per-timer semantics are unchanged (drainDueTimersWith), so a sleep still fires at-least-once and still pins to the generation that armed it.

The deterministic timer id for a sleep. Generation 0 keeps the legacy v5 UUID over ("keiro":"workflow-sleep":name:id:fullStep) so in-flight pre-change timers remain signalable. Generations 1 and later include the generation component so a sleep after continueAsNew never collides with a prior generation's terminal timer row.

The seed is hashed as UTF-8 bytes (identitySeedBytes), which is byte-identical to the original codepoint encoding for ASCII seeds and collision-free for the rest; see docs/adr/0024-deterministic-ids-hash-utf-8-seed-bytes-and-are-frozen-replay-identity.md.

The durable journal step name for a sleep: the user's suffix prefixed with sleepStepPrefix. sleepStepName (StepName "cool") == "sleep:cool". The prefix keeps the journal self-describing — an operator scanning it sees sleep: and knows the entry is a durable wait, not an ordinary step.

Build the JSON payload carried on a workflow-sleep timer row. The first argument is the generation that armed the timer; the second is the full "sleep:<suffix>" journal step name the firing will record.

Recognise and extract a workflow-sleep payload. The result contains the full step name and the generation when the payload records one. Nothing in the generation slot denotes a legacy workflow-sleep payload written before generation pinning; an overall Nothing denotes any other timer (for example, a process manager's).

Recover the generation represented by a deterministic workflow-sleep timer id. Candidate generations from currentGen down to zero are tested against sleepTimerId; this lets a new worker pin legacy payloads that do not carry an explicit generation. Returns Nothing only for an operator-crafted or otherwise non-matching timer id.

The payload "kind" tag that marks a keiro_timers row as a workflow sleep, distinguishing it from an ordinary process-manager timer so a single timer worker can route each correctly.