The Kuma account has two-factor login, so a password login always ends
in tokenRequired. Prod config now holds a Kuma session token instead
(uptime_kuma = {url, token, maintenance_id}).
- Sign in with loginByToken; a refusal says the token was rejected
(Kuma password changed?). username/password stay as a fallback for an
account without two-factor login.
- Wait for Kuma's first 'info' event before emitting: Kuma registers
its handlers only after sending it, so an earlier emit is dropped and
times out now and then.
- configured() needs url, maintenance_id and a token (or username and
password).
Tested from prod against Kuma 2.5.5: signed in and paused window 7,
which was already paused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>