CleanerBot Changelog

Preventive hardening to protect guilds from misuse, compromised admins, and accidental misconfiguration while keeping Auto-Kick transparent and predictable.
Most guardrails trigger when Auto-Kick is enabled or when inactivity/decay settings change while Auto-Kick is on.
Auto-Kick now enters a pending state on enable: a 24h cooldown, then a manual confirm. If nobody confirms, it expires after 7 days and stays off.
If impact can't be estimated (for example during cache rebuilding), Auto-Kick runs only in Safe Mode with tiny caps until impact is known.
Hard throughput caps (per run/hour/day) scale by server size. Hitting a cap pauses Auto-Kick and routes remaining cases to manual review.
Servers with 100+ managed members require two eligible admins for high-risk confirmations; single-admin fallback requires a delayed re-confirm.
Permissions are checked at action time (Owner/Admin/CleanerBot admin role). If someone loses eligibility mid-flow, another eligible admin must finish it.
Critical toggle spam is rate-limited, but staff still see blocked attempts with who/what/why and the remaining cooldown.

New command: /config history shows recent config and Auto-Kick audit entries for quick review.