v1.44.0

• /selfupdate no longer kills a running container-update batch (#2, @famewolf). Issued mid-batch, it restarted Docksentry and aborted the running updates — and could have orphaned a container caught mid-recreate. Self-updates now coordinate with every other flow through the shared update mutex: they queue behind a running batch (and start automatically when it finishes), hold the lock through their own pull+swap so no batch can start mid-restart, AUTO_SELFUPDATE skips busy cycles, and Web UI single-container updates take the same mutex (they used to run uncoordinated).

New i18n keys selfupdate_queued / selfupdate_dequeued.