Operator escape hatch: reload gateway config (notably the sender
allowlist) or recover a wedged adapter from chat, with no shell access to
the host.
Start becomes a supervisor loop that relaunches the bot on request, so a
restart is scoped to the gateway: the daemon keeps running and in-flight
agent tasks are untouched. Exiting the process would also have restarted
under the unless-stopped policy, but would have killed running work.
Two failure modes are handled deliberately:
- The handler runs on the very bot the supervisor is about to stop, so it
hands off over a buffered channel and returns instead of tearing down
inline, which would deadlock the restart it just requested. A duplicate
request while one is in flight is dropped, not queued.
- A failed config reload logs and relaunches on the previous settings, so
a bad config edit cannot take chat down permanently -- which would also
remove the means to fix it.
Authorisation is inherited from authorizedMessage: only allowlisted
senders reach any handler, so /restart is admin-only by construction.
main.go supplies Reload, which re-reads config from disk and refreshes
token and allowlist; other fields still need a full daemon restart, since
they are wired at construction.