/restart was declared twice, and one of the two was quietly dropped
2.12.0 added "restart Docksentry itself" as a second Telegram command entry under a name that already meant "restart a container". setMyCommands was handed 29 commands and stored 28 — Telegram deduplicates by name without saying so — leaving the picker showing one description for a command that no longer matched it.
One entry now, covering both: /restart <name> restarts that container, bare /restart restarts Docksentry. The behaviour was right the whole time, by accident of the order the handlers are checked in. The declaration was not, and "right by accident" is not a state to leave something in.
Discord caught up
/restart with no container restarts Docksentry there too, with the same refusal when the container has no restart policy to bring it back. The check is asked of the same code rather than reimplemented, so the two front ends cannot come to different conclusions about when stopping ourselves is safe. A Discord restore now points at it instead of merely mentioning that a restart is needed.