MEE6 replacement audit — enumerate current MEE6 features on the 7Cav guild

[SyniRon]

Prerequisite for scoping the broader MEE6 → CavBot2 migration. The first concrete ask (temporary voice channels, filed separately) is one slice; before committing to that work in earnest, we need a feature inventory of everything else MEE6 currently does for 7Cav.

Audit checklist:

• Leveling / XP
• Welcome messages
• Auto-roles
• Moderation actions (warn, mute, kick, ban triggers)
• Custom commands
• Reaction roles
• Anything else on the MEE6 dashboard

Output: per-feature replace / skip / defer recommendation, with rationale for any "replace" entry covering rough scope.

Size: ~1 hour.

[SyniRon]

This was generated by AI during triage.

Human Brief

Category: enhancement (audit, scoping prerequisite)
Summary: Inventory MEE6's currently-enabled features on the 7Cav guild and produce a per-feature replace / skip / defer recommendation as the scoping basis for the broader MEE6 → cavbot2 migration.

Why this is ready-for-human and not ready-for-agent:

• Requires logged-in access to the MEE6 admin dashboard (maintainer-only credentials).
• The replace / skip / defer calls hinge on regiment priorities and which MEE6 features anyone actually uses — agent judgment can't substitute for the maintainer's view here.
• Output is a scoping doc, not code.

Deliverable:
A comment on this issue (or a short doc at docs/mee6-replacement-audit.md if you'd rather track it in-repo for future reference) covering each item in the audit checklist:

• Leveling / XP
• Welcome messages
• Auto-roles
• Moderation actions (warn, mute, kick, ban triggers)
• Custom commands
• Reaction roles
• Anything else surfaced on the dashboard

For each: replace / skip / defer plus a one-line rationale. For every replace entry, add a rough scope sketch (think: would this be a single command, a background job, a whole subsystem?).

Acceptance:

• Every dashboard-enabled MEE6 feature has a row in the audit.
• Each row carries one of replace / skip / defer and a rationale.
• replace rows get a scope sketch sufficient to file a follow-up issue (or to extend MEE6 replacement — temporary voice channels (hub → personal VC, cleanup) #100's scope, if that ends up being the right shape).
• When the audit is done, file follow-up ready-for-agent issues for each replace entry (or note in the audit if a single combined issue makes more sense).

Related:

• MEE6 replacement — temporary voice channels (hub → personal VC, cleanup) #100 — MEE6 replacement: temporary voice channels (the first concrete slice that prompted this audit).
• Add recurring report for recent joiners with Star Citizen role #98 — Star Citizen joiner report (parallel foothold work toward the broader Discord analytics roadmap).