feat: add notification audit log tab to settings

[Copilot]

No historical record existed for notifications sent via QLAPI.systemNotify — users had no visibility into what was sent, when, via which channel, or whether it succeeded.

Backend

• back/data/system.ts: Added notifyLog to AuthDataType, new NotifyStatus enum, and NotifyLogInfo interface (timestamp, title, content, status, notifyType).
• back/services/system.ts: notify() now resolves the active notification channel (from notificationInfo or system config) and writes a log entry to the DB after each send attempt. Added getNotifyLog() returning the 200 most recent entries, newest first, with DB-level cleanup of older records.
• back/api/system.ts: New GET /system/notify-log endpoint.

Frontend

• src/pages/setting/notifyLog.tsx: New table component — columns: send time, title, content (truncated at 100 chars), channel, status (colored tag).
• src/pages/setting/index.tsx: Wires up data fetching and adds a 通知日志 tab between 登录日志 and 依赖设置.

Logged fields per notification:

{
  timestamp: number,   // ms epoch
  title: string,
  content: string,
  notifyType: string,  // e.g. "bark", "telegramBot"
  status: 0 | 1,      // 0 = success, 1 = fail
}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
qinglong	Ready	Preview, Comment	Apr 25, 2026 7:02am
qinglong-back	Error		Apr 25, 2026 7:02am