The deployment execution fence, read ONCE per pass, or 'none' for a tick
with no database behind it. A drain still dispatches — the thread routes
degrade a wake to a persist there, so the inbox drains without minting —
while migration-locked and proof-only skip the pass entirely: a due row
stays due, so the deployment that takes over dispatches it.
REQUIRED: an unfenced tick keeps delivering into thread DOs a locked
deployment is refusing, which burns the notification's delivery attempts on
a deployment that cannot act on it. See ExecutionFenceWiring.
Optionallimit
limit?:number
Max due rows read per pass. Must be a nonnegative safe integer; zero is an
intentional no-op. Values above 100 are split into route-valid chunks.
The deployment execution fence, read ONCE per pass, or
'none'for a tick with no database behind it. A drain still dispatches — the thread routes degrade a wake to a persist there, so the inbox drains without minting — while migration-locked and proof-only skip the pass entirely: a due row stays due, so the deployment that takes over dispatches it.REQUIRED: an unfenced tick keeps delivering into thread DOs a locked deployment is refusing, which burns the notification's delivery attempts on a deployment that cannot act on it. See ExecutionFenceWiring.