CLNR Changelog

New

Recovered candidates in Manual Kick Review give admins more context when a member became active during an inactivity path before staff acted.
- Every saved Manual Kick Review can open a private live review that shows the current kick threshold and separates Eligible for removal from Recovered candidates.
- Eligible members still meet the server's normal kick rules. Recovered candidates are currently below the kick threshold, but CLNR recorded that their activity previously moved them back below a warning, inactive, or kick threshold and estimates that they would have reached the current kick threshold under unchanged decay conditions.
- Each recovered candidate shows when the recovery was recorded, which threshold was crossed, the score before recovery, current Decay Score, compact counts of detected activity signals, latest detected activity, and an ~ estimated score without that recovery.
- The estimated score is clearly marked as review context. It is never treated as the member's actual Decay Score or as automatic kick eligibility.
- Apply-to-all Kick, Snooze, and Exempt actions continue to cover currently eligible members only. Recovered candidates start unselected and must be chosen individually by an admin.
- Selecting a recovered candidate for removal triggers an additional danger confirmation that separates currently eligible members from recovered candidates and names the recovered members selected.
- Before any removal, CLNR rechecks the live review, membership, exemptions, snoozes, current score, recovery evidence, permissions, Discord role hierarchy, and review validity. If the evidence or member state has changed, the removal is stopped and staff must review the updated state again.
- Recovery records start with this release and are not reconstructed from older activity history. CLNR keeps only the latest recovery cycle per member for up to 90 days and invalidates the estimate when relevant decay settings or member conditions change.
- Each recovery cycle can appear in one actionable Manual Kick Review. If a bounded review page cannot show every qualifying candidate, CLNR tells staff that more remain and keeps those candidates available for a later review.
- CLNR stores only compact detected-signal counters for this feature - not message content, channel IDs, or a detailed activity timeline. Recovered candidates never become automatically eligible for kicks, scans, DMs, or inactivity reminders.
- The optional Manual Review Recovery Staff Advisory explains how recovered candidates work, what evidence and estimates mean, the default action scope, safety checks, privacy, retention, and limitations without changing any inactivity setting.
Staff Removal Approval adds an optional, free approval workflow for sensitive kicks and bans. It is off by default, separate from inactivity automation, and requires one requester plus two other authorized staff members before CLNR acts.
- Admins choose one removal staff role for the workflow. The server owner, Discord Administrators, and members with the configured CLNR admin role can also participate without giving removal staff broader access to CLNR settings.
- /removal config sets the removal staff role and optional access, saves selections immediately, and shows setup blockers, channel readiness, and missing CLNR permissions before staff begin using the workflow.
- /removal request guides staff privately through the member, Kick or Ban action, required reason, and optional choices before posting an approval request to the manual kick review channel or the configured staff-channel fallback.
- Ban requests can explicitly choose how much recent message history Discord should remove: none, 1 hour, 6 hours, 24 hours, 3 days, or 7 days. Member DMs are optional, and kick DMs can optionally include the configured reinvite link.
- The requester cannot approve their own request. Two different, currently authorized people must approve before CLNR acts; one denial closes the request, open requests expire after 24 hours, and /removal list links staff directly to pending requests.
- Before any removal, CLNR checks current staff authority, target membership and eligibility, inactivity-exempt role protection, its own Kick or Ban permission, Discord role hierarchy, and the request deadline again.
- Approval cards keep the current status and approval progress easy to scan while preserving the request, decisions, failures, safety checks, and final outcome for staff review.
- Admins can separately allow removal staff to contribute to existing manual inactivity kick reviews through a two-person Confirm flow. This does not give them Snooze, Exempt, configuration access, or personal Kick Members permission, and the existing admin review path remains available.
- /removal status and the Staff Removal Approval page in /config show explain readiness, channel routing, role access, permissions, and the fixed approval policy. The optional Removal Approval Staff Advisory can introduce the workflow without enabling it.

Improvements

Admins can now clear the configured CLNR admin role with /config remove admin_role, and /config show links directly to both the set and remove options.
The /event analytics command group has been removed, while scheduled-event RSVPs can still count as a normal activity signal when enabled.
Voice activity can now be recovered when a member leaves voice after CLNR missed the original join event, improving activity recognition after downtime or moderation-related interruptions.
Community Casefile Stage Cards now show the selected theme pack's hero image when one is available.
Border Challenge collection and missing-country results opened from the active card can now also be shared with the channel when a member chooses to post them publicly.

Fixes

Border Challenge inactivity reminders no longer repeat after CLNR restarts.
Pro and Scale server owners and purchasers now receive the permanent CLNR Supporter role when they are present in the Support Community, even when a different admin contact is stored for the server.
Check-In setup screens and Community Pulse previews now handle expired Discord interactions and already-deleted messages more quietly.