v1.23.8

Added

Startup notification now says why Docksentry restarted (#2, reported by @famewolf).

Three of his hosts reboot at midnight and each Docksentry came back with the generic 🚀 Docksentry started banner — making it look like Docksentry restarted itself, when an external signal (host reboot / docker restart / Docker daemon restart) stopped it and the restart policy brought it back.

The SIGTERM/SIGINT handler now records the exit cause, and the next boot appends a line to the startup message:

↻ Restart followed an external stop signal (SIGTERM) — Docksentry did not restart itself.

With cron 0 18 * * * + auto-selfupdate off there is no code path that restarts the process, so this cleanly separates external restarts from self-updates. Absent marker (first boot or an unclean SIGKILL/OOM/power loss) adds no suffix. Translated into all 17 languages.