umputun / tg-spam / 25035848305

83%

Build Type

push

github

Committed by web-flow

Commit Message

Add warn auto-ban for repeated admin /warn commands (#398)

* add plan: warn-auto-ban

* feat: add Warnings storage layer for warn auto-ban

Add per-event log table tracking admin /warn commands per (gid, user_id).
Mirrors the Reports storage pattern with Add/CountWithin methods and
opportunistic cleanup of rows older than 1 year. Tests cover both SQLite
and Postgres engines.

Related to #71

* feat: add Warnings consumer interface and moq mock

Adds the Warnings interface to the events package next to the Reports
interface, generates the moq mock, and threads the warnings/warnThreshold/
warnWindow fields onto the admin struct so they can be wired in Task 4
and consumed in Task 5.

* feat: wire warn auto-ban CLI flags and settings

Adds --warn.threshold and --warn.window flags (env: WARN_THRESHOLD,
WARN_WINDOW) and a corresponding WarnSettings substruct on the top-level
Settings model. Maps options through optToSettings and registers
Warn.Threshold in zeroAwarePaths so 0 ("disabled") survives DB-backed
config loads. Adds startup validation that rejects threshold>0 with
non-positive window, extracted into a testable validateSettings helper.

* feat: wire warnings storage through TelegramListener to admin

Add WarnThreshold, WarnWindow, and Warnings fields to TelegramListener
and pass them into the admin handler literal. Construct the warnings
storage in main.go when --warn.threshold > 0 and populate the listener
fields from settings.Warn.

The admin handler still gates on warnThreshold == 0 || warnings == nil,
so the wiring is inert until Task 5 extends DirectWarnReport to use it.

* feat: implement warn auto-ban in DirectWarnReport

When warn threshold is configured, DirectWarnReport now records each warn
and bans the user or channel once the count within the configured window
reaches the threshold. The new executeWarnBan helper respects dry,
training, and soft-ban modes, posts an admin-chat notification, and uses
the existing banUserOrChannel primiti... (continued)

Coverage Stats

182 of 205 new or added lines in 6 files covered. (88.78%)

1 existing line in 1 file now uncovered.

8355 of 10033 relevant lines covered (83.28%)

228.83 hits per line