Interface EscalationClientConfig

Postgres connection options — used when creating a standalone EscalationClient.

Optional system-event sink. When set, this client calls events.publish post-commit for every escalation lifecycle transition it performs. Fire-and-forget; a publish error never fails the committed operation.

Inject a pre-existing getHotMeshClient function (e.g. from Durable.Client). When provided, the client reuses the caller's engine pool — no extra connections.