feat/login-alerts #86

Merged

nrupard merged 3 commits from feat/login-alerts into main

2026-05-13 20:01:32 +02:00

nrupard commented

2026-05-13 20:01:22 +02:00

Owner

No description provided.

nrupard added 3 commits

2026-05-13 20:01:22 +02:00

feat(account): email user on sign-in from a new device 8178e52906

Adds a "login alerts" notification: the first time an account is signed in
from a given (User-Agent, IP) pair, the server emails the user-on-file
address with the device label, IP, and time, plus a deep-link to the
settings sessions list so a stranger sign-in can be revoked. Repeats from
the same device stay silent. A per-user opt-out toggle ships alongside the
existing digest preference and the dispatch is fire-and-forget so SMTP
latency or failure can't change the login response. Registration pre-seeds
the device so first-login from the same browser does not trigger an alert.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

feat(account): log every login-alert suppression and success f73f15a1c1

Each early-return path inside dispatch_login_alert is a possible "why didn't I get an email?" question. The dispatch runs in a spawned task off the response path, so a silent return is the only signal an operator gets. Log each suppression branch (SMTP unavailable, user opted out, no email on account, user record gone) at info or warn and log the successful send at info so an operator can diagnose without a debugger.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

chore(login-alerts): demote send and suppression logs to debug

Check / clippy + fmt + tests (pull_request) Failing after 12s

Details

b55d2a5154

The dispatch fires on every sign-in, so info-level chatter is too loud for normal operation. Drop the suppression branches and the success line to debug; keep the "user row vanished" branch at warn since it indicates a race the operator should know about.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>